Third Party > Repairing and Upgrading Rockbox Capable Players
Sansa E200 Bricked by Recovery Mode
illa:
Thanks...
A word of caution
Only copy .mi4 files to the recovery partition.
Do not format this 16MB drive
Do not copy anything except one .mi4 file to the recovery partition. This might turn your shiny toy into a paperweight!
Do not copy .rom files to that partition unless you know exactly what you are doing. Again: You might brick your player!
Do not try anything else unless you have to. Again: You might brick your player!
Wow... I'm 5 for 5
illa:
one of the no no's I did was formatting the 16meg partition. I did this on a Windows XP machine through Windows explorer... Is it possible the reason the firmware wont reload correctly in recovery mode is because my partitions are ruined?
I have a e260...
hmm...
[root@smtp e200]# dmesg | grep "Sansa"
Vendor: SanDisk Model: Sansa e250 Rev:
-then my partitons
[root@smtp e200]# fdisk /dev/sdb
Command (m for help): p
Disk /dev/sdb: 16 MB, 16777728 bytes
1 heads, 33 sectors/track, 993 cylinders
Units = cylinders of 33 * 512 = 16896 bytes
This doesn't look like a partition table
Probably you selected the wrong device.
Device Boot Start End Blocks Id System
/dev/sdb1 ? 23579877 58171077 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(23579876, 0, 1)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(58171076, 0, 31)
Partition 1 does not end on cylinder boundary.
/dev/sdb2 ? 5111804 63779327 968014120 65 Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(5111803, 0, 24)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(63779326, 0, 4)
Partition 2 does not end on cylinder boundary.
/dev/sdb3 ? 56663075 115330596 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(56663074, 0, 24)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(115330595, 0, 22)
Partition 3 does not end on cylinder boundary.
/dev/sdb4 ? 1 110218985 1818613248 d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(110218984, 0, 24)
Partition 4 does not end on cylinder boundary.
Partition table entries are not in disk order
*****************
This looks dirty compared to what I see on http://daniel.haxx.se/sansa/e200.html
Bagder:
If putting back the original mi4 in recovery mode doesn't work, I suggest you go further down the hackery lane and invoke the manufacturing mode and go e200tool to restore the BL and hope that fixes your problem.
illa:
yah i've tried 20-30 times with etools recovery.. different roms, once etools copies it over, hold down rec and tried various mi4's, everytime i unplug usb cable...it says firmware upgrade finishes, restarts to a blackscreen
Hawks-SOAD:
can someone plz make a guide with all the steps to unbrick my sansa im dumb
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version