Third Party > Repairing and Upgrading Rockbox Capable Players
Sansa E200 Bricked by Recovery Mode
ItzBACON:
I can't get it to go into recovery mode. When I run the recover command with the boardsupport.rom it still stays in manufacturing mode, or so I'm guessing. I'm ASSUMING that it's in pre-boot mode, but since I'm still new at this I could be wrong. But the fact that it's not showing up as 0781:0720 and only as a "PortalPlayer, Inc." on 0b70:0003 or as "Prototype product vendor ID" on 6666:e200 makes me assume that it's not working the way it should. I've tried loading the i2c on it but I just get the "Failed to claim the interface (-1, Operation not permitted)" error. I waited as long as possible to post about it hoping that I could figure it out, but I'm pretty much out of ideas.
zajacattack:
Yes, it is in pre-boot mode. You need to run "sudo ./e200tool init" (without quotes) and then run "sudo ./e200tool i2cprogram i2c-e280.bin" (without quotes) you cannot get into recovery mode without first repairing the i2c rom.
ItzBACON:
Awesome guys, got it working again. I guess I was just doing some steps out of sequence or something, but after I did what you said zajacattack, it was able to recognize it as a Sansa again or so lsusb said. After that it wasn't too difficult to get it back going. Again, thanks guys, I REALLY appreciate all your help and what all you guys have done to figure this stuff out.
aLexx:
I supposed I got a new serious Problem. I really missed it up when I deleted (sic) the partitions with fdisk! Now the e250 hängs as by everybody: nothing on the screen and only the circle is lighted up.
I am running ubuntu 64bit and compiled the e200tool by myself (I also tried the binary, but same result). I followed all the solutions in the thread until today but I always get the same mistake:
I try to connect in Manufactory Mode and lsusb give back:
Bus 002 Device 009: ID 0781:0720 SanDisk Corp.
When I do "./e200tool recover BL_SD_BOARDSUPPORTSD.ROM" I get
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.ROM' to address 0x10600000
Searching for device 6666:e200 ... 9 8 found!
Write at 0x1060279f
Control message (-71, Protocol error)
and the lsusb give: Bus 005 Device 019: ID 6666:e200 Prototype product Vendor ID
I then tried: "./e200tool init" and I get: e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... found!
Initializing USB stub (4780 bytes) ... done!
But when I do: "./e200tool i2cprogram i2c.bin"
I get:e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c.bin'
Searching for device 6666:e200 ... found!
Uploading at 0x2000
Uploading done!
Programming, please wait...
Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!
Does anybody knows how to solve this Problem, or what does "Programming failed (-71, Protocol error)" means???
Thx in advance
aLexx:
Thanks to ALL the people with their problems and suggestions!!!! After an unsleepy night and thinking of giving up... I got a light and succedded in unbrick my SANSA-e250.
This is the REAL Bible to unbrick the SANSA: http://www.rockbox.org/twiki/bin/view/Main/SansaE200Unbrick
Thanks again to all, who contributed to it!
Only one thing was driving me crazy: I was trying the whole with ubuntu amd64 (no problem with the system), but I stop getting "Programming failed (-71, Protocol error)" only when under the BIOS switched the USB Ports to USB1.1!
With USB2.0 I never succeded in wrinting the whole BL_SD_BOARDSUPPORTSD.ROM, but as soon as I tried with USB1.1 I had no programming problems at all.
Another important thing for those who deleted the partions (like I did), you NEED to copy also sansa.fmt to the recovery partition thogether with the *.mi4 and the *.rom files.
Thanks again!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version