Rockbox Technical Forums
Installation / Removal => Manual Installation => Sandisk - Installation/Removal => Topic started by: P.Opus on September 06, 2007, 10:44:01 AM
-
I have been on the fringes quietly monitoring Rockbox development on the E200R series, and you guys have been amazing.
With SDHC support and success in putting Rockbox on the "R" series, I am almost ready to give this a spin.
I have read the instructions and they sound simple enough for someone with some Linux experience, so I may give it a shot.
(Believe me, I will read all the warnings and etc. before proceeding)
However, one question I need answered. I noted that you needed to modify the original boot loader to prevent the "signature check" that was blocking earlier attempts at putting Rockbox on the R series Sansa.
Does putting Rockbox on an "R" series Sansa change it to a vanilla E200?
The reason is, I'm a longtime Rhapsody Subscriber and am currently addicted to Rhapsody Channels.
I know Rockbox allows dual booting, but will it disable my Rhapsody functionality in the player? I know Rockbox itself won't support the special "Rhapsody" features such as "channels" and native .rax file (Rhapsody DRM) tracks. But can I dual boot into original "Rhapsody" firmware that will restore the special Rhapsody functionality, or does the modified bootloader require me to use "vanilla" E200 firmware from this point.
I hope this is clear enough. Ideally I want to be able to use Rockbox without loosing the specific Rhapsody feature set.
Thanks in advanced.
Opus ???
-
It was very clear :)
I don't know, rockbox on the E200R is very new, and I would be hugely surprised if any of the devs are subscribers to a DRM music service!
You could try popping onto IRC and asking one of the devs. I suspect the answer will be along the lines of shouldn't do, but no-one has tested it.
-
No, putting Rockbox on an R model still makes it boot the original Rhapsody firmware when << is pressed during startup.
-
Thanks, Badger. Has anyone tried using Rhapsody with a Rockbox modified R after modification? Any issues discovered?
Thanks for the quick reply.
-
Thanks, Badger. Has anyone tried using Rhapsody with a Rockbox modified R after modification? Any issues discovered?
Thanks for the quick reply.
I didn't have an e200R, so I just put the R bootloader/firmware on my e200 and tried Rhapsody - it complains about a corrupt device certificate. I think this was more of a problem with trying to fake it into thinking the e200R rather than a problem with the bootloader.
-
I've had Rockbox working fine on my e280 for a while so when the instructions for the R series were released I tried it out on my brothers e270R. I went through all the instructions exactly and everything seemed to work fine. Rockbox now runs on his e270R with no problems. HOWEVER, when I try to boot the original (Rhapsody) firmware with Power + |<< I get that black screen with white text scrolling down and then it slowly fades to white until the whole screen is white. The Rhapsody firmware never loads. I though I did something wrong so I used the unbrick instructions to put the latest .mi4 (from sansa.com) on the player. Rhapsody worked fine, but no Rockbox. So I went through the instructions again, line by line, and the same thing happened. It seems like I have to choose between one and the other... and the Rockbox firmware doesn't support USB yet so I'm gonna leave Rhapsody on there for now.
Any ideas what went wrong?
-
Not really, your description seems similar to that of at least one other R owner.
It might be due to minor hardware differences or it might just be that the rockbox bootloader needs to do something differently when it loads and runs the Rhapsody firmware image.
-
Im having that same problem too! Can you devs figure out how to fix this? Or do I have to just use recovery mode, update to rhapsody firmware, then use usb? Over and over? Or are you working on usb support for rockbox itself?
-
Same here, I'm having the same problem on my E260R. Â However, my player would slowly fade to white, then slowly to a completely black screen. I'm thinking there are probably minor hardware differences.
I've also tried both the mi4 firmware file in the instructions and with the latest mi4 from Sansa's site with the same result.
-
I'm getting the same problem, so I just stuck the Rhapsody firmware back on there. We're so close!
-
Just to be sure, are you all absolutely sure you followed the instructions exactly and did not deviate at ALL (not one tiny bit, like if you got the OF.mi4 from some other site than the one linked)? Why I mention this is because my e250R dual boots perfectly, and the process I used is detailed in those instructions.
-
I hate to admit it, but I replaced the instructions for the OF.mi4 with the recent Rhapsody 1.0.2.165. Sorry... :P
-
and if you try with the version in the instructions... ?
-
I tried it with both versions. The latest from Sansa and the one in the directions. I got the same result both times.
-
it could mean that either the bootloader needs to be changed, or the rockbox startup firmware needs to be changed. or, it's just a hardware problem.
-
Those of you who are experiencing this issue, can you please download this file (http://scorche.cleansoap.org/rockbox/OF.mi4), place it into your system folder (this is a hidden folder that resides in the root of the device and should not be created by you), and tell me what happens?
-
I tried the the one from the instructions (cut-and-paste). Still does the white fadey thing. Then I tried scorche's one, still no dice.
Heck, all I need the Rhapsody FW for is USB...
-
Mine should be the same one as that, but I figured if mine worked, there was a chance you are all getting a bad one.
This whole thing would be so much simpler if I wasn't able to dual-boot...
-
To those who have the problem, what version information does the bootloader show? It should say "Version: rXXXXXX:XXXXXX-XXXXXX" - the full line could help in figuring out the problem.
-
I think that having the screen do the fade thing may be damaging it. I am starting to see blotchy spots when it fades.
-
No. Mine fades to white for around a second and then boots into the Rhapsody firmware.
-
i have a video of what mine does, follow this link:
http://myspacetv.com/index.cfm?fuseaction=vids.individual&videoid=17724967
I think videos would be more helpful to actually show what happens.
-
I already saw that...stop repeating it. If you are so keen on making videos, make one that details your entire installation process including showing the text and everything that you do so I can be sure that you are doing everything correctly.
-
Ok, I'm working on it right now. I'll modify.
-
fading to white is expected.... please, just go back to the OF and wait for an official installer (could be days away) so we can user-proof it
-
so we can user-proof it
As in keeping us from using it? Like water-proof. Why would you want to prevent us from using it?
-
Of course not. "user-proof" meaning "user won't easily break it and screw something up big-time".
-
Well, I actually like doing it manually. But I messed it up the first time, so it probably would be best for other people just to be safe. Do you still want to see the video or do you already know what it does exactly?
-
Mine fades slowly to white (all at once, not bottom up). No text appears, and the Rhapsody firmware never starts. I've left it for like 5 minutes, so I know it's no dice. Oh, well, I'll look out for that idiot-proof installer. ;)
-
so we can user-proof it
As in keeping us from using it? Like water-proof. Why would you want to prevent us from using it?
I wanted to say idiot-proof, but thought that may be too harsh and could be taken the wrong way... just like the ipodpatcher.. completly idiot proof...
-
After days of going back and forth between these forums and those on AnythingButIpod, I have finally managed to dualboot into Rockbox, albeit by modifying my e270R and turning it into a regular 270. Here is generally what I did:
Keep in mind I tried to dualboot using the e200R instructions here on Rockbox, but managed only to boot in Rockbox, and got only a fading white screen when I tried to boot into the OF, so...
While in UBUNTU, I downloaded the e250R bootloader from http://daniel.haxx.se/sansa/e200/250R_bl.rom, renamed it BL_SD_boardSupportSD.rom - and a firmware file from http://daniel.haxx.se/sansa/e200/rhapsody/pp5022.mi4
then I put my player into recovery mode and copied the two files onto the disk. I unmounted the player and it booted into the rhapsody firmware as usual.
I then proceeded to follow the e200R bootloader installation instructions from Rockbox and recovered the bootloader using e200tool.
Once again I put my player into recovery mode and transferred the firmware and bootloader files from
http://daniel.haxx.se/sansa/e200/PP5022.mi4 and http://daniel.haxx.se/sansa/e200/BL_SD_boardSupportSD.rom to the player.
I unmounted the player and it booted into the vanilla e200 firmware, sans Rhapsody.
I then proceeded to follow the Rockbox install instructions for regular e200 players and now I dualboot fine, albeit without Rhapsody.
I hope this summary helps at least one other person who was suffering from the fading white screen.
Any further questions, please do not hesitate to send me a message. Â
-
Thanks Sansauser07, this method worked perfectly. I'm now dual booting my E260R with Rockbox and the non-rhapsody firmware 1.03.01H. Any idea if you know this imethod is permanent, or can it be reverted back to an e200R firmware?
-
AFAWK, all this kind of fiddling is perfectly possible to revert.
-
Sounds cool... I wanted an e200 anyway! I knew there was a way using the BL method to get an e200.
Now, if I can manage to convert my e200R to an e200 using their firmware and a standard bootloader, can't I just use sansapatcher?
-
if I can manage to convert my e200R to an e200 using their firmware and a standard bootloader, can't I just use sansapatcher?
Yes you can, as then you have effectively turned it into a plain e200.
-
The only difference between the e200 and the R's is just the music subscription, right? So it's not a big deal to ditch the rhapsody firmware. Also, are you sure you need to do the bootloader install twice? All it's doing is overwriting the bootloader anyway..
-
What has to be done is the loading of the e200 loader on the e200R (which allows for bootloader patching, go figure), and then the patching itself. However, you must place the new e200 firmware on while in [e200] recovery mode so both get written, or else it won't boot next time.
-
Also, are you sure you need to do the bootloader install twice? All it's doing is overwriting the bootloader anyway..
My thoughts exactly, yet that was the only way I was able to recover into the e200 bootloader without dualbooting into a fading white screen. A bit messy, but for now it has to be.
-
Following the Instructions above, my sansa now dualboots(thanks :D) However, there are a few steps you can skip, because you are just putting something on that's coming right back off. I already skipped this step, with the same dualbooting effect. It's hard to explain, but you should be able to figure it out yourself. ;)
-
Sorry, that doesn't fill me with confidence.
I specifically bought a Rhapsody model for two reasons.
One, Subscritpion based music using Microsofts PFS (Play For Sure) DRM can be really flaky. On the Rhapsody Sansa's, they play Rhapsody's Native .rax files. The long and short of it, is that file transfers are much faster and reliable.
Also, Rhapsody Channels are really great.
I am really excited by the work you guys have done here. If I ever decide to stop using Rhapsody, then Rockbox may be an answer for me. However, if using Rockbox will force me to give up my tight Rhapsody integration, I'm not really interested in doing it yetl.
Keep up the good work.
Will
-
It'll only be a short while until we (they, I mean) to get the Rhapsody firmware to work dual-boot. Even though I don't use Rhapsody and its channels, the R firmware is faster and smoother, in more ways than one.
I also had this one question... since the patched bootloader simply bypasses the signature check, can we use themed R files now, too?
-
I also had this one question... since the patched bootloader simply bypasses the signature check, can we use themed R files now, too?
Although this is a not at all Rockbox-related question, the answer is yes.
-
It'll only be a short while until we (they, I mean) to get the Rhapsody firmware to work dual-boot.
That is why I am still quite puzzled at the moment. As I said before, I dual boot the Rhapsody firmware just fine, and yet, no one else seems to be able to. And if they followed the instructions exactly, they did the exact same thing I did.
-
Does it matter? Who cares about rhapsody? E200 is the same exact thing, except for a little more animation and the rhapsody feature.
-
Alright... I have a new test for those willing. Please use this bootloader: http://scorche.cleansoap.org/rockbox/BL_SD_boardSupportSD.rom in place of the first one that the instructions tell you to download (http://daniel.haxx.se/sansa/e200/BL_SD_boardSupportSD.rom). Follow the instructions exactly as they are, but just don't download the first one listed (use this one instead). Then come back and tell me if you are able to dual boot.
-
Does it matter? Who cares about rhapsody?
Probably quite a few people who paid for an e200R wanted the R and not just a plain e200 as then they could've bought that to begin with.
So I would say it matters. Rockbox on the R models will not take off properly before we can dual-boot fine on it.
-
Alright... I have a new test for those willing. Please use this bootloader: http://scorche.cleansoap.org/rockbox/BL_SD_boardSupportSD.rom in place of the first one that the instructions tell you to download (http://daniel.haxx.se/sansa/e200/BL_SD_boardSupportSD.rom). Follow the instructions exactly as they are, but just don't download the first one listed (use this one instead). Then come back and tell me if you are able to dual boot.
Still no dice, scorche. I followed the directions to the T, and using your BL instead of the one on the page. After the whole process, this white screen still occurs. I've left it for five minutes this time around, and it's still white when I come back.
Why would using a different e200 bootloader change anything? Just to eradicate the possibility of a corrupted file, like before?
When I messed around yesterday turning my e200R into an e200 (it worked by the way, and was cool, but seemed to work slowly for me), I noticed that dual-boot on the regular firmware also does the fade to white, but then goes to the e200 firmware. I'm assuming this is an encryption issue, right?
-
Well, what if we resigned the Rhapsody mi4 file with the dummy signature? Then, put it in system as OF.mi4 and see what happens.
-
I followed the instructions for dual booting the e200R. I was able to use Rockbox, but when I attempted to boot into the Rhapsody firmware I got the fading white screen to complete black screen exactly like an early post in this thread, as shown in his video http://myspacetv.com/index.cfm?fuseaction=vids.individual&videoid=17724967
I would prefer to have the vanilla e200 firmware. I have tried to get the vanilla e200 firmware on my e260R and have not been successful, unlike an earlier member who said that they were able to get the e200 firmware on the e200R.
Could someone post accurate and precise steps for a complete dual boot Rockbox and vanilla e200 firmware install on a e200R.
-
Could someone post accurate and precise steps for a complete dual boot Rockbox and vanilla e200 firmware install on a e200R.
Follow the directions in my post on page 3 of this thread. You will essentially have modified your e200R into an e200.
But beware, you will probably not be able to recover into your e200R firmware again.
-
Basically, you follow the instructions for bootloader patching and don't follow point 6 under step 1, and points 1 and 2 under step 3. That means, don't download the modified e200R booloader, and don't rename the bootloaders. If you follow the directions the same from there, you will copy the Sansa's default bootloader to replace yours on the e200R. Then, download the Sansa e200's firmware, and place it on there as well. Unmount your player, and remove the plug. It'll reset, and you have a perfect e200. Then you can just follow the directions on here to install Rockbox on the e200. ALL DONE!
But beware, you will probably not be able to recover into your e200R firmware again.
I have done this process, and then gone back to my e200R using the regular e200R bootloader patch, and drag the Rhapsody firmware on, so it works.
-
I have done this process, and then gone back to my e200R using the regular e200R bootloader patch, and drag the Rhapsody firmware on, so it works.
Were you able to use Rhapsody and its channels after the conversion back to an e200R? in Rhapsody mode?
-
I dunno, I don't use them, but I would assume yes because the Rhapsody decryption is in the hardware (I think).
EDIT: The only way to explain why e200->e200R conversions aren't working are that it must be a hardware issue: the firmware is the some. e200R->e200 should work fine, and back should be even easier because you can just drag the bootloader and firmware in recovery mode and you'll be back in all the DRM-mmy, anti-aliased goodness.
-
I did get my e260R dual booting with Rockbox and e200 firmware. Thanks to ZWaldowski's post.
-
Ignore what I have said about trying my files. I have tested with the exact files as I linked to in the procedure and my Sansa still dual-boots. I am planning on returning my Sansa and trying a new one soon to see if I can still dual-boot the e200R firmware.
EDIT: As another person in IRC was able to install it and dual-boot Rhapsody just fine, I am now of the opinion that you are doing something wrong and shall keep that theory until evidence points otherwise (although I am still open to new evidence, of course).
-
Yes, I am double-booting fine as well. Did you follow the directions EXACTLY?
You have to:
1. Download the Rhapsody firmware from the link on the E200RInstallation page.
2. Unzip it to get pp5022.mi4.
3. Rename pp5022.mi4 to OF.mi4.
4. Plug your Sansa in while in MSC (Rhapsody) mode (NOT MTP [PlaysForSure] mode).
5. Put OF.mi4 IN the SYSTEM folder (you may have to change settings to view hidden files and folders).
-
I have also done an install of plain e200 FW and Rockbox on an e200R. It double boots however when I boot into the e200 FW I get this screen:
>>>>
Rockbox boot loader
Version r12896-070323
Sandisk Sansa e200
Partition 0: 0x06 1896MB
Partition 1: 0x85 20MB
Loading original firmware...
Trying firmware partition
BL mi4 size: E400
Cant load from partition
invalid file format
Trying /System/OF.mi4
Mi4 size: 52B400
CRC32: 1DB36CCA
Model id:
Binary type:
Calculated CRC32: 1DB36CCA
Searching for key:
sansa...key found
sansa key used
<<<<
Is this correct?
-
I have also done an install of plain e200 FW and Rockbox on an e200R. It double boots however when I boot into the e200 FW I get this screen:
>>>>
Rockbox boot loader
Version r12896-070323
Sandisk Sansa e200
Partition 0: 0x06 1896MB
Partition 1: 0x85 20MB
Loading original firmware...
Trying firmware partition
BL mi4 size: E400
Cant load from partition
invalid file format
Trying /System/OF.mi4
Mi4 size: 52B400
CRC32: 1DB36CCA
Model id:
Binary type:
Calculated CRC32: 1DB36CCA
Searching for key:
sansa...key found
sansa key used
<<<<
Is this correct?
That appears just right; I get the same screen. Mine e200R still does the fade to white, but then two seconds later starts the e200 firmware.
One question: is there any way for us (as in e200 users, who use sansapatcher ;) ) to use a decrypted firmware so it starts faster?
-
I believe there is, why not try the Multi-boot custom build (found at http://e200.digerati1338.googlepages.com/multibl). Follow the directions for decrypting the original firmware, then put the decrypted firmware at /SYSTEM/F1.bin. Also, don't delete OF.mi4 until you finish upgrading. Once done, you will boot into rockbox default, and the original firmware with the center button.
-
It looks like that Multi-BL bootloader is a modification of the e200 bootloader. Has anyone tried it on a e200R? Has it worked for anyone?
-
Xoring, I have got my Sansa e280R dual booting with Rockbox and the e200R firmware just fine.
-
I realize that *some* people have it working fine, but I haven't gotten it to work properly and it seems like others are having the same problem. It's very convenient to call us idiots and say that we're doing something wrong or we didn't read the instructions or something. But I'd say you're wrong. I've been using Slackware as my primary OS for over 6 years. I'm not new to Linux or programming or following instructions. I followed ALL of the instructions exactly and even repeated it several times with different versions of the firmware to rule that out as a possibility. I have been unable to get it to work the way it's supposed to and I find responses like "It works for me, you're doing something wrong" to be dismissive and unhelpful. If you're not going to contribute toward a solution, at least acknowledge that other people might know what they are doing and might be reporting legitimate bugs even if your particular hardware doesn't experience the same issues.
-
I haven't got my E280R properly dual-booting into the original firmware either and I'm no idiot. There has to be a difference somewhere because I followed those instructions exactly.
It's either an assumption that some people make or some hardware difference that invalidates the scheme...
Thing is that I would really love to be able to still use the R firmware since I think it's better than the nonR one.
-
Since it seems people have trouble on the plain e200 as well with the recent bootloaders, I'm assuming this is a problem that is real and that happens to both e200 and e200R owners. Possibly there are variations that make it work on some and not on others.
So if we can find out when in time it broke on the e200, we should be able to fix this. If not, we should be able to make a e200R bootloader based on the code from where the e200 one worked and try that on the e200R players...
-
Please let me know if I can help somehow to find the solution for this issue.
Do you think I should try re-doing the whole patching procedure again?
ty
-
Ok, here's a test for you:
1. Get the SVN sources for 2007-07-31
2. Apply the R model bootloader keys in bootloader/main-pp.c from a recent source
3. Build a bootloader
4. Install this bootloader and see if it dual-boots better
5. Report what happened, success or not
-
I'm leaving work now but I'll try doing that tomorrow and will let you now if I was successful or not :)
-
Ok, here's a test for you:
1. Get the SVN sources for 2007-07-31
2. Apply the R model bootloader keys in bootloader/main-pp.c from a recent source
3. Build a bootloader
4. Install this bootloader and see if it dual-boots better
5. Report what happened, success or not
I was trying to follow your advice but I'm not really an expert at this stuff so please help me out a little.
1. I did: svn co svn://svn.rockbox.org/rockbox/trunk -r {2007-07-31} rockbox
2. The tea_keytable variable already has an entry for "rhapsody", and it's the same key as the bootloader/main-pp.c from the current trunk. I'm not sure what I'm supposed to "Apply" here.
3. I ran ../tools/configure and told it to make an e200r bootloader. make ran fine, no errors.
4. This is where I got stuck. I have a 'pp5022.mi4' in the build directory and a 'bootloader.bin' and 'bootloader.elf' in the build/bootloader directory. I read over the E200R instructions for patching the bootloader but that document just gives you steps to follow, it doesn't tell you what the different files are so I'm a little lost now as to what to do with the files I'm looking at.
5. Obviously, not results so far... :(
-
I thought there was somebody who already did the regression testing and identified the change at fault, didn't he? That's why some people were waiting for the developers to see the problem and try to address it... :)
Guys, please tell me if I am wrong!
ty
-
The pp5022.mi4 from step 4 is the Rockbox bootloader.
-
Just got a e280 outta futureshop for $150 CAD for the purpose of rockboxing it.
So far I've been able to follow the instructions like usual, I have rockbox installed, but
when I go to load the Sansa Firmware, I see text printed, and then the screen fades to white, fades to black and my player hangs. I have tried a couple of other .mi4's from Bagder's site, but I still get the same problem.
Any help is as always greatly appreciated, thanks ;)
EDIT:
had a look around the bug tracker and found this: http://www.rockbox.org/tracker/task/7806
and links to a forum thread on this subject. (http://forums.rockbox.org/index.php?topic=12762.60)
I've used sansa patcher 0.2 to load the older bootloader and things are working nicely.
@mods: please merge my post or lock this thread, thanks
-
Success!!!
Well, mostly.
Using the pp5022.mi4 file that I compiled from the revision you suggested I can successfully dual-boot. However the top two rows of pixels are corrupted for both Rockbox and the rhapsody firmware. For the moment, the minor screen corruption isn't a problem though.
Update: I'm posting a link to the pp5022.mi4 that worked for me. Maybe it will work for others who are having the same problem.
ftp://wisard.no-ip.com/pp5022.mi4
-
Hey Xoring
Have you applied any patches to your source code? A fix for those corrupted pixels might be in one of the patches. Where you able to dual-boot a Rhapsody player or just a nonR with your bootloader? If it was a non-Rhapsody..I thought that was already working.
I've built a bootloader myself but I can't try it because I forgot the cable at home :(
ty
-
Nice work xoring,
The display bug is fixed in the current bootloader but it wasn't back in the version which you're using right now.
It seems it is the added microsdhc support that broke the OF loading in the current bootloader. And since we don't even need microsd support in the bootloader, we should probably try to just disable that in the most recent svn code and see if that makes it run fine again.
There's just this little problem not all people experience the hanging problem, and within this latter category there seem to be several Rockbox devs!
-
alaron: I was working on a Rhapsody player loading a Rhapsody firmware. My non-Rhapsody player never had any issue booting the OF.
Bagder: Since I seem to have an affected Rhapsody player on hand I'd be happy to test code for you guys to make sure everything works for all users.
-
Hey xoring,
Thanks for making that clear :) I'll update the code to date and build a bootloader and it should dual-boot properly and have that pixel corruption you were talking about fixed.
-
Update: I now have a fully working pp5022.mi4 that fixes the pixel corruption.
svn up -r 14423 rockbox/
svn up -r 14620 rockbox/firmware/target/arm/sandisk/sansa-e200/lcd-e200.c
I posted the file at the same place as the previous one.
ftp://wisard.no-ip.com/pp5022.mi4
-
Hey, |Rain| showed up on IRC (http://www.rockbox.org/irc/reader.pl?date=20070927#23:01:47) and provided a patch that might work. It basically disables the microsd card (and doesn't start a thread) for the bootoader:
http://pastebin.ca/718278
(I don't think it has been posted to flyspray just yet)
It would be great if you could try this on a fresh SVN checkout on an e200R player.
-
Bagder: I just tried out that patch (svn up && patch -p0 < booloader.patch). I didn't get any errors when I patched or compiled, but the resulting bootloader causes my e200R to freeze on the first SanDisk logo-screen. It doesn't load either firmware.
-
Hi guys
I can confirm that neither the bootloader build from HEAD or the one patched worked, both froze at the Sandisk screen. So it's not the patch who's freezing, but the HEAD source.
I've tried Xoring's posted bootloader and works fine on mine, I can dualboot but I have 1 line of corruption on top of the screen. If we could fix that... :)
I think xoring's bootloader was built off an older code base...not the from HEAD, am I right?
ty
-
alaron, did you try the new one? I posted one at 2am EST that fixes the corrupted pixels.
-
nope I tried your first one ;)
I'll try your new one now!
-
Perfect xoring, that bootloader worked fine ;) no pixel corruption!
I wonder why the HEAD source doesn't work since I was thinking to get the latest version...
You have your sources sync'd to an old revision...
svn up -r 14423 rockbox/
svn up -r 14620 rockbox/firmware/target/arm/sandisk/sansa-e200/lcd-e200.c
If I have time this weekend I'll try to play with the sources a little bit.
Thanks Xoring!
-
The problem with the boot-up freezing at the logo-screen was fixed in HEAD so I gave that patch another try and got the original problem again. It boots Rockbox fine, but not the OF.
-
Thanks Xoring :)
This morning when I tried HEAD was broken for us :( they put up the fix really fast.
We can probably trace the problem in the simulator and fix it...if time permits ;)
-
Anyone knows if this bootloader would work with a newer version of the original Rhapsody firmware which is:
Product: e280R
FW: 01.02.031
Region: America
Build Date: 2006.12.14
Thanks
-
why not try it and find out for us. worst that can happen is you have to re-install, but after the ordeal with the bootloader you should be very familiar with the unbrick/reinstall process.
-
Where can I get a newer Rhapsody version from? Sandisk's software will detect they have a newer version and will ask if you want to install it but that will not work with out setup. I need to get the actual .mi4 file and place it inside System folder.
I'm willing to try if I can get a new firmware version.
-
After a few minutes on the official website I found this...
http://www.sandisk.com/Retail/Default.aspx?CatID=1449
...which links to this:
http://mp3support.sandisk.com/firmware/rhapsody-1.0.2.165.zip
-
Tried it and works fine :)
Thanks Xoring!
-
Just to be sure, are you all absolutely sure you followed the instructions exactly and did not deviate at ALL (not one tiny bit, like if you got the OF.mi4 from some other site than the one linked)? Â Why I mention this is because my e250R dual boots perfectly, and the process I used is detailed in those instructions.
could u put the links to get rockbox on the r series im dyin to try it it worked for u ill c if it works for me
-
Sansauser07
could u give a link to the e200r bootloader instructions and e200 tool for windows would help alot i really want rockbox and e200 is wat i wanted anyway thanx
-
Please read the guidelines. Especially the parts about real english, double posting, and searching the wiki/forums before you post.
-
e200 tool for windows would help alot i really want rockbox and e200 is wat i wanted anyway thanx
1. e200tool for windows doesn't exist (well, it does, but nobody's gotten it working yet)
2. You need to use Linux to do the conversion.
3. A howto is in the other thread you posted in.
-
k thanx
-
k thanx
Glad to see you're taking the "real english" requirement seriously... ::)
-
Sorry I'm used to abbreviating words is there any way you know of to get rockbox on the e200r series on windows (xp) could you put links and links to instruction please it would help a lot I really wan't rockbox thanks
-
sansauser7
i would follow your instuctions but I can't get the e200tool i have windows and I can't find the instructions if you could post links that would be a big help thanks
-
It has been told many times over.
e200tool is not working on windows. Boot linux and use it from there.
-
how do you boot linux?
-
if anyone knows hot to get rockbox on e250r on windows please post links would help and instructions thanks
-
OK, if you read this whole topic, you will see that (as I have stated before), the only way to get rockbox on an e200R with Windows is even more complicated than for Linux and is not for anyone who doesn't know what they're doing. I will post directions if you really want, but you have to know what you're doing, ESPECIALLY with drivers.
-
First of all... rockboxer11, I'll ignore your poor grammar, frequent misspellings and double-postings, but please contain yourself and wait for the devs to get e200tool working on Windows. They will post instructions for Windows users as soon as they have it working, you won't find instructions for it anywhere because at this time they don't exist. If you REALLY want Rockbox to run on your Sansa, READ all the instructions very carefully and learn to use the Linux operating system (Ubuntu is a good place to start http://www.ubuntu.com/).
Second. An update on my progress with building a working firmware...
Following a lead on Flyspray, I checked out the latest version and commented out the section labeled "Check for SDHC" in firmware/target/arm/sandisk/ata-c200_e200.c and rebuilt the firmware and it works perfectly. Is there any other method to check for SDHC that won't result in freezing firmware?
Also, I'm hosting the currently-working pp5022.mi4 in the same place as before if anyone wants the latest copy without having to compile themselves.
ftp://wisard.no-ip.com/pp5022.mi4
-
No, xoring, I have a working copy of e200tool for Windows, and I used it to put Rockbox on my e280R. I will post directions if anyone wants, but if you are a beginner, I would wait, the e200tool on Windows method requires a lot of knowledge with drivers.
-
I'd love to have the Windows copy. And the instructions, definetly give me those too :P
Never much of a Linux person.
So, anyway, if I do this, since reading though this I just want a simple answer- Can I dual boot back and forth with Rockbox and the regular firmware? Running a Sansa 250r model.
Thank you for your time :D
-
Yes, you should be able to, but people have had trouble dual-booting between rockbox and the rhapsody firmware while others have no problems.
-
Steps for windows, please :X
-
Right here, http://www.rockbox.org/twiki/bin/view/Main/SansaE200RBootloaderPatching#Bootloader_Patching_in_Windows.
-
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!
-
@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.
-
@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.
That did it xoring. Thanks for the help and all the work you've done to make it possible.
-
Building a bootloader from trunk works now with no patching. I have is hosted in the same place as usual.
ftp://wisard.no-ip.com/pp5022.mi4
-
both bootloader and sansapatcher have been updated on the official download.rockbox.org site so following the "official" paths and methods should now work fine!
-
zajacattack
I followed your instructions for Windows, I know how to do it all, but when I download libusb from your link, when it is done downloading, I cam't unzip it it just says "do you want to save the file or have internet explorer try to find the program to run it" and when I use internet explorer it brings me to a page with links that don't do anything how do I unzip it? and also is there a way to uninstall it ? please post instructions it would help alot thanks.
-
By "download", I mean save the file, and then unzip it. And, yes, all you have to do is delete the folder. You are not installing the filter driver, all you need is the device driver.
-
how do you unzip it though? I tried and I can't figure it out how do you unzip after you save it then i'm good and I should be able to do the rest myself thanks
-
Well, to unzip tar files, I like to use WinRAR. You can use gzip as well (http://www.gzip.org/#exe) or any other application that can handle tar files.
-
Ok thanks and when I said If you could delete it I ment can you delete it of the sansa?
-
I tried using those programs but it still won't let me extract the files this is exactly what happens click your link to the libusb click the download link thing on the website then this pops up this is exactly what it says
Do you want to save this file, or find a program online to open it?
Name: libusb-win32-device-bin-0.1.12.1.tar.tar
Type: Unknown File Type, 101KB
From: internap.dl.sourceforge.net
the the buttons at the bottom say
Find Save Cancel
please post a step-by-step I really want rockbox thanks
-
Hey! No more need to do this. Go to E200RInstallation in the wiki. e200rpatcher is now working and can be used instead.
-
I followed the instructions in the wiki exactly but my e250r still won't boot rockbox I think it is because it say to copy a file to the "system" file on your device and mine doesn't have one and how do you copy something to the root of your device
-
OK, you must go to "Control Panel", then to "Folder Options", and enable the viewing of hidden files and folders. Then, you will be able to see the System folder.
-
I got it now how do you boot the originalk filmware
-
I got it now  how do you boot the originalk filmware
http://www.rockbox.org/manual.shtml
The manual tells you how.
Edit: Please do not post the same question to every thread you can find. If you have everything installed correctly, I believe you dual boot on Sansa's by holding the left button when you turn on.
Please read both the manual and the forum guidelines.
-
please post link to .mi4 file please
-
Read the sansa instructions on how to install rockbox on you device!!
-
I have had the white screen of death prob to. I think I know how to fix it. Go to restore/rescue mode and drop in the original .mi4.eject the 260r and let it do its thing. Now reconnect the 260r to your cpu. use the sansa updater to check for new firmware but don’t update. look at the mp3 player line and the firmware line. if they say anything other than sansa e260r for player and your original firmware version, go to the root of your player and drop in the original .mi4 then eject the player. let it do its thing then reattach. check the firm and player again it should be factory. I don’t think that loading the original .mi4 in recover/rescue mode fully recovers the player.
Now go to http://www.rockbox.org/twiki/bin/view/Main/SansaE200RInstallation and download the new e200r patcher and diver. boot player in manufacturer mode go to device manager then to libusb-win32 devices and update the driver with the new one from the address from above. run e200r patcher install rockbox per the instructions posted on the page above and boommmm duel boot. you may get the white screen of death for 3 to 5 sec mine boots in 3 sec from the time it starts turning white.
I tried the new patcher before fully reverting and it did not work for me, you might try it first to save some time. I know my spelling is bad and this is probly the longest run on sentence in history but I’m tired and sleepy so cut me some slack. thanks to every one who has worked to port rockbox to the e260r..... primus forever
-
thanks but could you post a link for the mi4 and the sansa updater thing to
it would help a lot I really want to get the origanal firmware back thanks
-
All the links you need are in the manual. Please demonstrate you have read it as you're required to do so by the forum posting guidelines.
-
the sansa updater is on the cd that come with the player. the firmware i used for mine is here http://www.sandisk.com/Retail/Default.aspx?CatID=1449 .
-
Success!!!!
Granted, I screwed up and put the .rockbox folder in the wrong location, like a dingbat, and got the dreaded "could not find rockbox" message. However, simply using recovery mode and placing the original firmware .mi4 file got me back up and running.
After I "re-read" the fine manual, I caught my mistake, downloaded the .165 firmware file from Sandisk, loaded the .165 firmware file in the system directory (after renaming it of course), moved the .rockbox folder in it's proper location,
Rebooted the Sansa, and then used recovery mode to load the boot loader (the one you rename to pp5022.mi4) into the hidden partition, and Voila!!!
Success.
What a cool system. I gotta hand it to you fellows, what a great program.
Now the only thing left to do was to move all my stuff out of the "music" folder into a folder I made called "my music" so that the file browser will allow me to browse that folder without setting the file settings to "view all".
BTW. Read the installation instructions, they are quite fine, and the Windows installation, is really quite easy, if you have any computer knowlege whatsoever, (and make sure you read fully where to put stuff.)
I also tested dual booting, and all my Rhapsody Channels work as well. You guys are great. You've just extended the life of my Sansa E280R by an immeasurable amount.
Who needs a Sansa View when I have Rockbox. By the time those 16Gig and above SDHC cards come out, I'm sure that USB will be fully functioning in Rockbox, and the only need to dual boot will be to listen to exclusive Rhapsody content.
-
I'm glad to hear it worked out! Yeah, there was a problem earlier with the rockbox BL and the OF, but the bugs were worked out, and it is working now. Glad to hear your support for Rockbox, and I completely agree, this will allow the Sansa to not go out of "style" too soon.