Installation / Removal > Sandisk - Installation/Removal
E200R Automatic Bootloader and Rockbox Installer
scorche:
Have you read the install instructions/this thread?
zajacattack:
OK, as I stated here (http://forums.rockbox.org/index.php?topic=12712.0), I successfully have Rockbox running on my e280R, and I did it by getting e200tool to work in Windows; however, getting libusb-win32 to create the right drivers and recognize the Sansa was a pain. Now, I am willing to test out any installer that might make this easier, and the installer can use libusb-win32, the trick is to NOT install the filter drivers. I unzipped the DEVICE driver to my desktop and had inf-wizard create a driver for the Sansa in manufacturing mode, then e200tool could recognize it (I did have to rebuild e200tool with "usb_set_configuration(ud, 1);" added before the line "usb_claim_interface(ud, E200_INTERFACE);"). Anyways, I am willing to test any auto-installers seeing as most Rockbox devs don't have an e200R.
JdGordon:
can you upload the .inf which libusb-wine32 created that worked?
zajacattack:
Sure, but just remember this, the Manufacturing Mode 1 driver must be installed when the Sansa is connected. Then, running "e200tool recover BL_SD_boardSupportSD.rom" will fail, but make the device 0666:E200. Then, Manufacturing Mode 2 driver must be installed. Then, the Sansa must be disconnected turned off, and reconnected in manufacturing mode. Then, "e200tool recover BL_SD_boardSupportSD.rom" will succeed, but the device will be given to libusb. So, using device manger, Manufacturing Mode 1 driver must be uninstalled and Windows must install its own driver (scan for changes), then you can upload the patched BL.
P.S. I uploaded them as .txt files. Just rename them to .inf files.
EDIT: Sorry, wrong drivers, these are the right ones. The 0781-0720 is the one you will want, the 0666-E200 is only if you use e200tool.
Sup3rkirby:
--- Quote from: Llorean on September 14, 2007, 01:30:53 PM ---First off, there is no "windows bootloader." The bootloader is what is installed on the player, not the program that installs it, nor the tool we use to access the player.
Secondly, we don't access a hidden partition on the e200R. Unlike the e200, we don't see a hidden partition available at all from the computer's side. What we do is start the player in Manufacturer mode, which allows us to talk with it through the USB port and do certain things. In this case we replace the ROM with our own ROM, something we don't need to do on the normal e200 players ever.
In windows we haven't been able to talk properly to the player in this special mode because of the USB differences.
--- End quote ---
*Sigh*
I really do hate post like this.
I will first admit, I incorrectly referenced the 'bootloader', as I was thinking of the sansapatcher program.
But as far as anything related to a 'hidden partition'. Please refer to an earlier post made by zajacattack:
--- Quote from: zajacattack on September 09, 2007, 11:21:34 PM ---Well, what if we could directly write to the hidden partition on the R series? Then, the program could just overwrite the BL and firmware automatically instead of requiring e200tool. By the way, I can't figure out to compile e200tool in cygwin. Could someone post the latest version compiled in cygwin? I want to try something...
--- End quote ---
If you are not accessing the 'hidden partition', then what is he talking about. No comments were made to correct him.
I was simply offering help. But to help I would need information and not criticism. This topic seems to be intended for the need for a sansapatcher basically, that will allow windows users to run a program(the sansapatcher) and then have this program install a bootloader(like what is done now but only for the e200 series), thus allowing users of the e200R series to easily install and use RockBox. I was intending to offer some help by creating an installer(sansapatcher) for this purpose exactly, and so after reading the post, asked for information specifically so I could get a better understanding of what exactly needs to be done by the program.
Now it seems an installer would need to create the drivers(using the uploaded .inf files) and install them, and then have the 'updated' version of the sansapatcher(with the 'usb_set_configuration(ud, 1);' line inserted) finish by detecting and installing the bootloader. Correct?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version