Rockbox Technical Forums

Installation / Removal => Manual Installation => Sandisk - Installation/Removal => Topic started by: mrglass on September 11, 2007, 07:32:38 AM

Title: Unpredictable Brick E280
Post by: mrglass on September 11, 2007, 07:32:38 AM
Hi All,

I am aware that at least part of this is in various FAQ's, and I spent some time researchign before I posted.  But before I try it again I want to make sure it is not going to repeat.

Given this covers both Rockbox and Sansa Standard Firmware I will not limit the attributes to either.

a).  I purchased the Sansa E280 player from Amazon.  Was quite happy with it, especially as it gives functionality of Ipod without the Itunes infestation.
b).  I installed the software, including the firmware update checker.
c).  I updated the firmware.  (Note:  I'm running Vista32)
d).  After a while, and much time spent reading various forum posts on ABI and rockbox, I downloaded rockbox and ran Sansapatcher to enable it.

e).  Rockbox worked fine.  HOwever after a day or so I got tired of the interface, and tired of pressing left-arrow each time I needed to boot to the old firmware.  I ran Sansapatcher and selected uninstall.  The clincher for me was that none of the Rockbox skins/themes yet had the since picture navigation that the Sansa original firmware had.  That said I could fully understand that Rockbox was inevitably going to advance and surpass the OF.



f).  On the reboot, I got the "unable to boot to firmware message".  Eventually I was able to get into the manufacturing mode and copy across the old Sansa Firmware.

g).  The reboot seemed to work fine and the device was back to normal.  The Sansa Firmware updater prompted me to update again, which I did.

h).  I copied across a bunch of mp3 files, and disconnected.

i).  When it did the reboot, it started a REALLY LONG "refreshing database", halfway through the screen went fuzzy, and it went black with the blue ring.



j).  Reboots wouldn't work.. the only way to turn it off was to hold the power for 17 seconds.  I tried the various connect, connect manufacturing mode, connect factory mode etc. etc. etc.  None worked.



=========================

My question, (and hopefully I have given enough detail that people have enough background).



1.  Is this familiar to anyone?  (I haven't seen this quite mentioned on the forums).

2.  I'm nervous about putting in any new firmware, (amazon sent me a new one), either from Sansa or Rockbox so that it bricks again.  

and yes I did read all the manuals beforehand... and yes I did follow the instructions exactly.

Thanks,

Gavin
Title: Re: Unpredictable Brick E280
Post by: Llorean on September 11, 2007, 07:37:55 AM
Considering you're talking about problems with the original firmware, this isn't really a relevant question for the Rockbox forums. You already uninstalled Rockbox, and successfully from the sound of it.
Title: Re: Unpredictable Brick E280
Post by: mrglass on September 11, 2007, 07:58:20 AM
I take your point, but the concern I have is that some legacy changes may have been left over from the rockbox installation.
Remember, when I sansapatch U-ed the device, it didn't come back normally, ... I had issues where I had to follow various steps to try to get back to a bootable device.

The firmware I loaded was a US-firmware I found on an old link to Sandisk.com, so I wasn't "back to normal" until the firmware was updated.

Occam's Razor seems to be cutting both ways right now ..

Simple interpretation 1.  I managed to boot back to Sansa firmware, (eventually), therefore issue had nothing to do with Rockbox Sansapatcher.

Simple interpretation 2.  The fact that the uninstall did not work correctly may have left some residual issue.

I agree interpretation 1 is more likely than 2, but I am following both lines of investigation on Rockbox and AnythingbutIpod until I can be fairly confident I have understood and eliminated danger to put Rockbox back on the new device
Title: Re: Unpredictable Brick E280
Post by: Llorean on September 11, 2007, 08:03:07 AM
Rockbox's bootloader installation does one thing: It moves some data on a disk, and puts our data before it.
Rockbox's bootloader removal does one thing: It removes our data and shifts that original data back.

When you updated with the official firmware, it completely writes over that whole area, destroying any changes we might have made to it anyway. There is no place for any Rockbox data to have been left over: We do not flash.