Third Party > Repairing and Upgrading Rockbox Capable Players
Sansa E200 Bricked by Recovery Mode
Gravian:
--- Quote from: danymag on May 07, 2007, 10:16:42 PM ---First of all a big thanks to you guys for providing this much information and help to everybody.
Now, my problem:
Model: sansa e270 europe (http://epaun.com/e200/1.jpg)
Dumb action : Formated drive & unplugged
Cry for help : Followed the tutorial several times. After dumping both .rom and .mi4 files on the new available partition, unplugged usb cable. When trying to power on, the same blue ring.
After trying this several times, with all bootloader versions (us & eu & c200, btw when using c200 the whole screen was blank) now when I try it I get an error message after unplugging the cable. Even checked the files on nuclearscripting. I checked the CRC most of the times and it seemd ok.
Debug info : screen capture of e200 tool at work (http://epaun.com/e200/2.jpg)
Right after e200tool prints Execution started, this shows up on my sansa : http://epaun.com/e200/3.jpg
Recovery mode starts just fine : http://epaun.com/e200/4.jpg
Hold rec + drop the .rom & .mi4 files
After that hit safely unplug : http://epaun.com/e200/5.jpg
After unplugging the error message appears : http://epaun.com/e200/6.jpg
Then, in shuts down and restarts with the blue ring.
Do you think this is salvageable ? If not I have a friend that's looking for a color screen for his electronics project, I am sure he would be happy with the one on my Sansa but I would rather not give him the satisfaction.
--- End quote ---
=================================
Ok, here we go:
After several months of shelving my Sansa e250 2gig (regular, not rhapsody) I had just about given up hope on fixing it, but since I had just installed SuSE out of geeky curiosity I decided I would try and give unbricking it another go with e200tool.
Now what had happened was the same as the user above, except a little different, my Sansa was hanging on startup and all the official fixes didn't work so I decided to take a chance and wipe the whole thing clean using OS X, since it can see the hidden partition. The idea was to wipe it clean and fresh install with e200tool and then install rockbox, but when I went to reinstall the files in recovery mode via e200tool they would not write, instead, the exact thing the above user described happened.
*Once in recovery mode via e200tool* Heres what I did, first I made an empty text file called Sansa.fmt, now as everyone should know that formats the player, (mind you it seems a little below the point with the current problem, but I figured since I tried EVERYTHING else) then I copied over the bootloader file and the main rom file like before, selected remove safely from the right click menu and unplugged it.
Now the text was a little different this time and it went by too fast to read, but this time it booted into the sansa screen w/o needing to be plugged into the computer useing e200tool to load the bootloader to RAM, which was a major improvement, but it hung, so I booted into manufacturing mode *and loaded up the recovery mode via e200tool* one more time and just made a file called Sansa.fmt, then selected remove safely and unplugged. After that it booted up just fine!
Now I'm not sure exactly what had happened but I'm GUESSING when you format it with a computer like that you format it in a foreign format that it can't write the files too. One last note, I think you still have to hold down the center button when you plug it in and you still have to hold record when you use e200tool, even if you are stuck in manufacturing mode by default. But either way, it's good practice.
Anyway, post if this helps at all or if you need clarification. I've been seeing this problem on several forums, so I figured that I should give my solution.
Time to install RockBox!
EDIT: Ok, there was a typo, or moreso I forgot to mention something. The changes are in between the *'s. I guess I kinda figured it was obvious what I was doing by what I quoted, but I guess not, sorry.
Bagder:
--- Quote from: Gravian on August 09, 2007, 01:20:11 AM ---so I booted into manufacturing mode one more time and just made a file called Sansa.fmt, then selected remove safely and unplugged. After that it booted up just fine!
--- End quote ---
This was a typo, right? I don't see how you can create a file like that in manufacture mode...
Gravian:
Maybe I got the name of the mode wrong? It's the mode you get when turning it on with the center button down. When it booted up it gave me the blue ring and black screen by default and the flash drive wouldn't mount, like I said, I had to use e200tool to even get into recovery mode because I wiped the 16 meg partition clean. Once I did that it gave the the 16 meg partition and from there I made the file and copied over the firmware like I would any USB flash device. If you JUST make the reformat file when it reboots it gives you a plain white text on black formating message. Although, if it matters at all, I think I may have used 260 firmware instead of 250 as it doesn't recognize the USB in windows, it gives me an error that is cataloged here:
http://www.rockbox.org/twiki/bin/view/Main/SansaE200Port#Rockbox
Unless of coarse all e200 models experience this problem, but I have only found reports for the e260. Luckily music and files can still be loaded up with the original firmware so I'm not really concerned, the only problem will be explaining that you have to boot with |
Bagder:
Ah yeah ok.
When you start it in manufacture mode you can load the bootloader to it with e200tool and when that bootloader starts it can go into recovery mode (and then you can put files on its recovery disk), so yeah it gets a little confusing in which mode you're really in then...
As long as it worked for you I'm fine! ;-)
lokasenna:
New idiot that bricked his Sansa :'(
I put my Sansa into recovery mode so I could restore the original firmware but put in some random bin on accident. Now when I switch on the Sansa the circle lights up and no backlight. My computer doesn't alert me to any usb device being connected. I figure this is a hopeless case because if I can't detect it then they can't communicate. Does anyone have any suggestions for this massive idiot? Or is trying to get Sandisk to replace it my only option?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version