Installation / Removal > Sandisk - Installation/Removal

e280 installation bricks. cannot boot into recovery.

(1/3) > >>

blistovmhz:
I picked up an e280 yesterday, looked at the gui for about 10 seconds before deciding once again, rockbox = win.
I used the rockbox installer for my first install.  Everything went fine.  It booted to rockbox immediately after installation.  Wouldn't go into disk mode (read about that later).
Tried booting to the origional firmware (OHNOES!) and it locks up, screen fades into a horrible nuclear blast of gamma, and eventually fades to black.  Nothing after that.
Reboot back into rockbox, no problem.  I notice though that I don't see any of my music I'd previously copied in.
The entire "music" folder is missing.

So onto recovery.
I downloaded this mi4 file http://daniel.haxx.se/sansa/e200/PP5022.mi4
Booted into recovery mode, noticed there was a file called "version.txt" in the recovery partion (16Mb part).
I left it alone as I didn't put it there.
Copied in the mi4 file, unmounted, made sure the fs was sync'd, unplugged the player from USB, and it hangs on writing.
I left it for about 30 minutes and gave up, rebooted the player.
Player powers on, blue ring led is on, screen is black, nothing happens behond that.
I couldn't find another thread with this problem, so I took it back and replaced the player.

New player today.
Followed the e200 installation instructions here http://download.rockbox.org/manual/rockbox-sansae200/rockbox-build.html
Installed properly, again, it boots to rockbox, doesn't see my music folder, reboot to origional firmware, and the player locks up again.
This time I put it into recovery and deleted the "version.txt" as I suspected it was being dd'd instead of the firmware.  Copied the mi4 file i got from here http://daniel.haxx.se/sansa/e200/1.02.15a.mi4 , unmounted, unplugged, and this time it wrote the image correctly.
Rebooted, and the origional firmware came up..

So, I've now managed to completely brick the first device (future shark isn't allowed to ask me any questions about returns  :) ), and still cannot get rockbox to work.

Seems sorta silly that their recovery partition doesn't have its own locked firmware so you can't overwrite it and brick your device.

Anyone have any ideas on why this is happening?
(No, its not the R model)

Thepher:
Might have similar problem with e280...?

First boot to Rockbox is ok...  so I connect usb, nothing happens.

power off, power on, "horrible nuclear blast of gamma".

Power off, unplug, power on holding left, "horrible nuclear blast of gamma".

Rockbox still boots fine though.

So is it a brick?

blistovmhz:
Thats exactly what happened to mine, I just went a step further and killed ALL the firmware I believe.
I think the firmware is b0rked, and recommend against installing it right now until someone comes up with some solution.
In the mean time, you can likely still recover yours by booting into recovery mode, and copying in that mi4 file, as listed in the first post.
Just make sure to delete the version.txt file that shows up, and when you're done, make sure you unmount the device, wait a bit to be sure its written, disconnect, and let it go until it reboots itself.

(ps. this is a "no, its not bricked yet" response.  others may disagree on the definition, but at this point, yours is still recoverable)

zajacattack:
OK, there is an official bug in sansapatcher 0.3. It is being worked on. Until then, you need to use sansapatcher 0.2, otherwise you won't be able to boot the OF.

blistovmhz:
I used the sanspatcher-0.2 for my second device, and boot still failed.
I'm not sure what I used for the first device because I used the installer.

Navigation

[0] Message Index

[#] Next page