abi>>forums

abi>>forums (http://www.anythingbutipod.com/forum/index.php)
-   Sansa e200 General (http://www.anythingbutipod.com/forum/forumdisplay.php?f=79)
-   -   Got Into Manufacturing Mode, Can't Get Out :0 (http://www.anythingbutipod.com/forum/showthread.php?t=26340)

DiSS 02-17-2008 02:38 AM

Got Into Manufacturing Mode, Can't Get Out :0
 
Hi. It is not included
Help please.
I have switched on mode Recovecy mode. Has copied casually some files.
Now the player is not included
What to me to do? Whether is what reset at a level of ?

cpchan 02-17-2008 03:54 AM

Quote:

Originally Posted by DiSS (Post 218302)
I have switched on mode Recovecy mode. Has copied casually some files.
Now the player is not included
What to me to do? Whether is what reset at a level of ?

I am sorry to tell you that by copying random files in Recovery mode essentially bricks your player. Try and see if you can get back into Recovery mode, connect the player, and copy a firmware file to the device. If that doesn't work, your only hope at this point is to try e200tool:

http://daniel.haxx.se/sansa/e200tool.html

in Manufacturing Mode first. If that doesn't work, your last hope is to try to restore the i2c drivers in pre-boot mode. Details here:

http://www.rockbox.org/twiki/bin/vie...nsaE200Unbrick

That being said, I presume you are using Window, very few people have got it working under that OS.

Charles

DiSS 02-17-2008 04:35 AM

Quote:

Originally Posted by cpchan (Post 218315)
I am sorry to tell you that by copying random files in Recovery mode essentially bricks your player. Your only hope at this point is to try e200tool:

http://daniel.haxx.se/sansa/e200tool.html

in Manufacturing Mode first. If that doesn't work, your last hope is to try to restore the i2c drivers in pre-boot mode. Details here:

http://www.rockbox.org/twiki/bin/vie...nsaE200Unbrick

That being said, I presume you are using Window, very few people have got it working under that OS.

Charles

I shall excuse pardon for my English language.
Yes I work on Windows.
Tried enter mode Recovery mode. The monitor on a player is not lit. Shines only buttons. The computer does not see a player.
Can eat reset at a level of iron?

advcomp2019 02-17-2008 05:45 AM

That is manufacturing mode since the screen is not on, but the wheel light is on.

I am trying to figure out "Can eat reset at a level of iron?" still.

Nemethyst 03-01-2008 05:11 PM

hard boot?

rtech 03-02-2008 09:57 AM

Quote:

Originally Posted by advcomp2019 (Post 218324)
I am trying to figure out "Can eat reset at a level of iron?" still.

Me too, but wouldn't that be a great song title? :D

DiSS 03-10-2008 06:04 AM

1 Attachment(s)
Greetings, All
What to me to do{make} with a player? To stop the attempts to restore it{him}?
When I insert a cable in usb port. Windows defines{determines} new USB the device. But I do not have drivers.
Attachment 4465
http://www.anythingbutipod.com/forum...1&d=1205147485
I apologize for English.

advcomp2019 03-10-2008 07:02 AM

OK, there is a driver in the e200tool that might have, but the e200tool for Windows is in a way buggy. So the best bet is to use Linux with the e200tool.

Windows e200tool: http://www.rockbox.org/twiki/bin/vie...Sansae200Tools

Cpchan's post has the Linux version.

DiSS 03-10-2008 08:04 AM

e200tool for Windows has not helped.
It is necessary to establish on my computer Linux.
Only I do not know which distribution kit Linux to me to put as I beginning{starting} in Linux.
Prompt please.

advcomp2019 03-10-2008 08:45 AM

You can use an Ubuntu LiveCD. Then there is already a thread with step on how to fix it.

Edit: Here is the thread: http://www.anythingbutipod.com/forum...ad.php?t=22253

DiSS 03-10-2008 05:34 PM

ubuntu@ubuntu:~$ 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 8 found!
Write at 0x10601d88
Control message (-71, Protocol error)
ubuntu@ubuntu:~$

In what there can be a problem?

advcomp2019 03-10-2008 06:18 PM

You holding the REC button long enough?

DiSS 03-11-2008 09:04 PM

1. The player - has switched off
2. Mode Hold - on
3. Has pressed and kept button "Select" 10 s.
4. Insert USB cable
5. Not releasing{Not letting off} button "Select" has pressed and kept button "REC" - 10 s.
5. Has started the terminal and has entered the command.

advcomp2019 03-11-2008 09:08 PM

You hold the REC while "sudo ./e200tool recover BL_SD_boardSupportSD.rom" is going you never let off of the REC till it gets done.

DiSS 03-12-2008 03:39 PM

Quote:

You hold the REC while "sudo ./e200tool recover BL_SD_boardSupportSD.rom" is going you never let off of the REC till it gets done.
Ок. So all also has made.
The code was executed up to the end.
...
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!"

BUT the disk 16 MGb has not appeared. I for a long time waited.
Has released{Has let off} all buttons. Also has repeated process from the very beginning.
Quote:

  • with your bricked sansa off, switch on hold, press and hold the select button with your thumb as though you are using it with your LEFT HAND! If you are right handed. After holding the select button for more than 5 seconds, connect the sansa to your computers USB port, the wheel lights up still holding it, don’t let go.
  • now. Using your right hand to operate the mouse, paste the lines sudo ./e200tool……etc. into terminal
  • on your left hand, using your index finger and press and hold the record button on your sansa as well as continue to press the select button. (this is awkward, I discovered that it works better this way), from here hold it in this position until I tell u to let go.
  • now, after 5 seconds, use you free right hand. Press ENTER on keyboard after the lines of text
  • the process should start and see the following:

The same result.

ubuntu@ubuntu:~$ 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 8 found!
Write at 0x10601d88
Control message (-71, Protocol error)
ubuntu@ubuntu:~$

I shall search for "donor" ROM of a microcircuit and I shall replace her{it}.

chrisjs162216 03-15-2008 06:42 PM

It seems as if it's timing out halfway through.

Try doing
----
sudo ./e200tool init; sudo ./e200tool i2cprogram i2c-e280.bin
----
that should allow run one right after the other, which should give you enough time.

HurricaneAK 03-17-2008 07:22 PM

Quote:

Originally Posted by DiSS (Post 226117)
Ок. So all also has made.
The code was executed up to the end.
...
Write done!
Running from address 0x10600000
Searching for device 6666:e200 ... found!
Execution started!"

BUT the disk 16 MGb has not appeared. I for a long time waited.
Has released{Has let off} all buttons. Also has repeated process from the very beginning.

The same result.

ubuntu@ubuntu:~$ 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 8 found!
Write at 0x10601d88
Control message (-71, Protocol error)
ubuntu@ubuntu:~$

I shall search for "donor" ROM of a microcircuit and I shall replace her{it}.

Although this is a pretty mediocre answer, I had the same issue and discovered the way to fix it was... merely to keep repeatedly doing it. I mean not three times, but maybe 100 times. Shockingly this just randomly worked for me (without any other conditions/changes applied), and I have managed to recover my sansa to original condition.

Othello 09-27-2008 11:06 AM

Wrong bootloader perhaps
 
My e280 is bricked and I've followed the instructions carefully to bring it back to the Recovery mode but I did not get the automounted disk.

Unfortunately according to the lsusb output it's not what I expected:
$ lsusb
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 012: ID 0781:0720 SanDisk Corp. Sansa C200 series in recovery mode
Bus 001 Device 002: ID 0e0f:0002
Bus 001 Device 001: ID 0000:0000

With some more searching I came across an apparently different bootloader package:

e200 392248 2008-09-27 04:09 BL_SD_boardSupportSD.rom
c200? 393624 2008-06-21 23:59 BL_SD_BOARDSUPPORTSD.ROM

So the bootloaders are not alike! I may have flashed my e280 with c200 bootloader. When I attempt to reflash it using the e200tool I get the same protocol error message seen earlier in this thread:

$ sudo ./e200tool recover BL_SD_boardSupportSD.rom
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 7 6 5 found!
Write at 0x1060be7a
Control message (-71, Protocol error)

When you see this message then your USB device has been reset to the 6666:e200 device so recover will not work until you power cycle. You can, however, attempt to rewrite the i2c rom because that function in e200tool looks in the 6666 address:

$ sudo ./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 ... found!
Uploading at 0x2000
Uploading done!
Programming, please wait...
Programming failed (-71, Protocol error)
*DANGER*, player might not be bootable now! Please retry!

And that's where I'm stuck. I've got an e280 flashed with a c200 bootloader and while it's recognized by Ubuntu as a USB device:
[ 5013.527796] usb 1-1: new full speed USB device using uhci_hcd and address 8
[ 5013.711683] usb 1-1: configuration #1 chosen from 1 choice

It's not recognized as an MSC device to mount its disk and fix it directly. If the e200tool could switch the e280 to that mode then I think I could do some good.

Suggestions welcome.

Othello 09-27-2008 11:22 AM

md5sums from the two files:
af26eb02fc3454f5264bb028107a2700 BL_SD_boardSupportSD.rom
6a10d79a2e13f6b4a7c8243f422e5608 BL_SD_BOARDSUPPORTSD.ROM

The second one matches what I've seen elsewhere as coming from the e200v101.02.24a.zip file, but that same file describes itself as a C200 boot loader when in use?

A followup to the e200tool failed flash: The lsusb shows this after the e200tool recover fails:
$ lsusb
Bus 002 Device 009: ID 6666:e200 Prototype product Vendor ID
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0e0f:0002
Bus 001 Device 001: ID 0000:0000

advcomp2019 09-27-2008 02:43 PM

Othello, you need to use the e200 bootloader and firmware on the e200 and the c200 bootloader and firmware on the c200. It still shows up as an e200. You might have to manually put it into manufacture mode after disconnecting it.


All times are GMT -5. The time now is 10:28 AM.