Installation / Removal > Sandisk - Installation/Removal

dual boot to rhapsody firmware

<< < (22/27) > >>

zajacattack:
Yes, you should be able to, but people have had trouble dual-booting between rockbox and the rhapsody firmware while others have no problems.

Downsider:
Steps for windows, please :X

zajacattack:
Right here, http://www.rockbox.org/twiki/bin/view/Main/SansaE200RBootloaderPatching#Bootloader_Patching_in_Windows.

Strommy:
First off I'd like to thank everyone who has contributed to making rockbox possible on the e200R series. I've been tracking the progress of this and as overjoyed when I saw it boot up on my e260R for the first time.

However, I am at a bit of a dilemma. I still can't dual boot. I am only able to boot into rockbox and when I try to boot into rhapsody firmware I get the pixel fading/freeze screen. I've done my best to try and solve the issue myself with all the information in this thread but it's a little confusing with the TONS of updates there has been. Could someone please reply to this post with detailed instructions and links to files that I can use to make dual booting possible on my 260R.

Thanks again for all your hard work!

xoring:
@Strommy: Currently, the best way I have found to fix this issue is using a bootloader that I compiled with the SDHC check commented out. It has worked fine on my brother's e260R that was experiencing this issue.

The quick steps are:
1. Go into Recovery Mode.
1.a. Turn off your Sansa.
1.b. Turn on the HOLD switch.
1.c. Hold the Record button down and push the power button. Don't let go of the Record button until you see "Welcome to Recovery Mode" on the screen.
1.d. Plug in the USB cable as directed.
2. Mount the drive.
2.a. If you have Windows, it'll show up as a USB Mass Storage Device automatically.
2.b. If you have Linux, you might have to mount it manually. (the device will be /dev/sda or /dev/sdb or something similar)
3. Copy over a patched bootloader.
3.a. You can get a working bootloader from ftp://wisard.no-ip.com/pp5022.mi4
3.b. Copy ONLY the .mi4 file to the device.
4. Unmount and unplug.
4.a. In windows, stop the device with the "Safely remove hardware" option. In Linux, umount /dev/sda (or your device).
5. It will update the firmware and reboot. You should be able to boot both firmwares fine now (remember to turn HOLD off).

It looks like a patch was recently submitted to subversion to fix the issue permanently. I will test that tonight or tomorrow and let everyone know.

Navigation

[0] Message Index

[#] Next page

[*] Previous page