Installation / Removal > Sandisk - Installation/Removal

e260 boots into RockBox fine, but won't boot into original firmware

<< < (4/15) > >>

ghoti:
i just installed rockbox on my new e280 and unfortunately have the same problem now, too... rockbox works, but booting into the original firmware fails with the strange display.
as far as i see, i can't even uninstall the bootloader because the sansapatcher does not find it anymore... (sansa dies when attached to the usb with the same symptoms as described for 'simple' booting.)

oranges2:

--- Quote from: ghoti on September 18, 2007, 06:22:03 PM ---i just installed rockbox on my new e280 and unfortunately have the same problem now, too... rockbox works, but booting into the original firmware fails with the strange display.
as far as i see, i can't even uninstall the bootloader because the sansapatcher does not find it anymore... (sansa dies when attached to the usb with the same symptoms as described for 'simple' booting.)

--- End quote ---
Boot into recovery mode by turning on the device with the lock switch on, and holding record.

Then put the BL.rom file for your model on the device: http://daniel.haxx.se/sansa/mi4.html

DavidGWRawson:
I have the bootloader that will solve the problem. However, I don't know how to post it. I will have to e-mail it to you somehow. It fixed my player when it di It's only for rhapsody editions. I just learned it the hard way...

oranges2:
Heres the text when it tries to boot the OF


--- Code: ---   Rockbox boot loader
      Version: *something really long*
      Sandisk Sansa e200
      Partition 0: 0x0B 3814mb
      Partition 1: 0x84 20mb
      Loading original firmware...
      Trying firmware partition
      BL mi4 size: EC00
      OF mi4 size: 52B400
      CRC32: 578F184B
      Model id: e200
      Binary Type: RBOF
      Calculated CRC32: 578F184B
--- End code ---

justWOOT:
I'm having the same problem with my e270. Mine is a fairly new one bought in May and shipped with firmware 1.02.15A- then upgraded to 1.02.18A. The bootloader fails to load the orginal firmware; I get the same weird screen wash and displayed text. I've tried different sansa bootloader roms (thinking perhaps there was an incompatibility with the newest one) and differnet RB builds- so I think there's something wrong with the sansapatcher. Anyone knows what the sansapatcher actually does, and where it stores/links the original firmware?

Navigation

[0] Message Index

[#] Next page

[*] Previous page