Third Party > Repairing and Upgrading Rockbox Capable Players
Sansa E200 Bricked by Recovery Mode
qtip:
--- Quote from: Eisbaer on March 03, 2008, 01:08:34 AM ---
--- Quote from: zajacattack on March 02, 2008, 03:27:00 PM ---1) Have you tried programming the i2c rom WITHOUT running ./e200tool recover BL_SD_boardSupportSD.rom first?
2) Do you have a different USB port and/or computer that you could try using?
--- End quote ---
1) Yes, no change.
2) Yes, also no change :'(
--- End quote ---
I have got exactly the same problem the usb is no longer detected, the blue ring comes on but there is no device showing up in the usb list I have tried three different PCs 2 different OS but it will not show up.. any ideas ??
Abdullah85:
hi
first of all I wanna let you know that I am using linux fedora 8 and also I have Win xp in my laptop
I was able to get recovery mode 2 days ago ,,, because I was whenever start my sansa I get go to recovery mode ! message
and then I went to sansalinux.com then I downloaded their files to put it in my sansa in recovery mode
but the I got that the files that I am trying to put in is bigger size than the recovery mode
so I unmount the driver and I unplug the device so gave message reading ,,, writting
and then I held down power off button and I got it turned off
NOW ,,
whenever I start my sansa I get blue ring and No lights on my screen
I read in many forums that there is manufacturing mode and pre-boot mode
Now I dont know what mode I got
in fedora 8 when I use the script of e200tool I get this
--- Quote ---[root@localhost s]# sudo ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 found!
Write at 0x1065fc38
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!
--- End quote ---
but I think I should get this
--- Quote ---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 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!
--- End quote ---
I tried to use unbutu live cd and use command lsusb I get this :
--- Quote ---ubuntu@ubuntu:~/Desktop/sansa/e200tool$ lsusb
Bus 005 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 004 Device 011: ID 0b70:0003 PortalPlayer, Inc.
Bus 004 Device 001: ID 0000:0000
--- End quote ---
--- Quote ---ubuntu@ubuntu:~/Desktop/sansa/e200tool$ ./e200tool i2cprogram i2c-e280.bin
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Programming i2c rom (address=87) range 0x0000-0x2000 from 'i2c-e280.bin'
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
ubuntu@ubuntu:~/Desktop/sansa/e200tool$ ./e200tool init
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Failed to claim the interface (-1, Operation not permitted)
--- End quote ---
and I dont get this
(ID 0781:0720 SanDisk Corp)
so I think the device is not recognized by fedora and unbutu live cd.
so what can I do
and thanks in advance :)
gevaerts:
You need root rights for e200tool, so use sudo (also for lsusb)
Abdullah85:
same problem I get this
--- Quote ---[root@localhost e200tool]# ./e200tool recover BL_SD_boardSupportSD.rom
e200tool v0.2.3-alpha (c) by MrH 2006, 2007
Searching for device 0781:0720 ... 9 8 7 6 5 4 3 2 1 0 not found!
Searching for device 0b70:0003 ... found!
Initializing USB stub (4780 bytes) ... done!
Writing 'BL_SD_boardSupportSD.rom' to address 0x10600000
Searching for device 6666:e200 ... 9 8 7 6 5 4 3 2 1 0 not found!
--- End quote ---
and it should be like this
--- Quote ---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 found!
Write at 0x10660198
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!
--- End quote ---
I also tried in my fedora this one
--- Quote ---[root@localhost e200tool]# /sbin/lsusb
Bus 001 Device 001: ID 0000:0000
Bus 005 Device 016: ID 0b70:0003 PortalPlayer, Inc.
Bus 005 Device 004: ID 0781:a3a4 SanDisk Corp.
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
--- End quote ---
and I think it should be ID 0781:0720
zajacattack:
Yes, see you are in pre-boot mode. Here's what you do:
1. Connect your players to the computer (without holding and buttons, and in Linux of course)
2. Go to http://daniel.haxx.se/sansa/e200tool.html and download e200tool
3. Download the latest firmware and bootloader files for your Sansa and put them in the same folder as e200tool
4. As well, download the i2c rom file for your player from http://daniel.haxx.se/sansa/e200tool.html
5. Connect your Sansa if you haven't already and run "./e200tool init" followed by "./e200tool i2cprogram I2CROM.bin", where "I2CROM.bin" is whatever you named the i2c rom file when you downloaded it
6. When and only when it finishes, disconnect your Sansa, and reconnect it in manufacturing mode
7. Run "./e200tool recover BL_SD_boardSupportSD.rom" while holding RECORD on your player
8. Once the player has booted to recovery mode, copy the bootloader and firmware files over to it
9. Disconnect your Sansa, it should be fixed
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version