Third Party > Repairing and Upgrading Rockbox Capable Players

e250r bricked [SOLVED]

<< < (2/2)

gevaerts:
OK. I think your sansa is in manufacturing mode (because the partition table is gone). If so, the instructions on http://www.rockbox.org/wiki/SansaE200Unbrick#Manufacturing_Mode should help.

Don't use e200tool in any other way than for "e200tool recover". Recover is safe, but some of the other options can really brick devices if not used properly.

NorthboundTrain:
Because I've got an e250r I should use the .btl file right, not the .rom file?

(edit)

Tried it, no dice:


--- Code: ---</opt/product/Rockbox> $ ./e200tool recover BL_SD_boardSupportSD.btl
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Failed to claim the interface (-1, Operation not permitted)
Searching for device 0b70:0003 ... 9 8 7 6 5 4 3 2 1 0 not found!

</opt/product/Rockbox> $ lsusb
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 005: ID 0781:0720 SanDisk Corp. Sansa C200 series in recovery mode
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

--- End code ---

Thanks for the help!

mc2739:
If you don't mind losing the "r" firmware, you can just use the standard e200 firmware.  The e200 and e200r use the same hardware.  Just follow the instructions for the e200tool using the e200 firmware.

If you want to reinstall the "r" firmware, the process becomes much more difficult.  I did this once on my e270r, but unfortunately I did not document the process when I did it.  If I remember correctly, it involved renaming the files to match the standard e200 file names while using the e200tool and then using the files with the proper "r" names when you get into the recovery mode.

gevaerts:
e200tool uses raw USB access, and therefore needs root permissions

NorthboundTrain:
I'm getting much closer!

The only way I can get into Recovery Mode is by running the 'sudo ./e200tool recover' mode:


--- Code: ---</opt/product/Rockbox> $ sudo ./e200tool recover BL_SD_boardSupportSD.btl
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.btl' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x1065f958
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!

--- End code ---

Doing the thing with holding down the 'record button' does not work.  I had to do the whole process (copy .btl file, copy .mi4 file and create the sansa.fmt file) for it to do anything when it restarts.  I got a Sansa logo (yeah!) and then the message:


--- Code: ---Load main image failed
Switch to Recovery mode

--- End code ---

I can now go into Recovery mode with the 'record' button!  I reloaded the .mi4 file and the same message came up when it restarted (Load main image failed).

I tried the e200 .mi4 file, and when I downloaded it I noticed that it was named PP5022.mi4 instead of pp5022.mi4 -- maybe that's why the first one didn't work?  Regardless, the second one works and I have an MP3 player again -- thanks, everyone!

Navigation

[0] Message Index

[*] Previous page