Can't Install Rockbox... e260 Sansa not detected

[Highlander]

I had the same problem with Rockbox Utility :
- logged with admin rights on Windows XP SP3
- Sansa e280 v1 FW 1.02.18F connected on MSC and mounted as drive I:
- the autodetect function in Rockbox Utility correctly detected my e280 and the I: mountpoint
- but when I tried to do the automatic complete installation I got the "no Sansa detected!" error message

So, I did the manual installation and it worked flawlessly.

[bluebrother]

So, I did the manual installation and it worked flawlessly.

Manual installation as in the manual way using sansapatcher or by using the "Installation" tab in Rockbox Utility?

[Highlander]

I did the manual way using the sansapatcher, I didn't try the "Installation" tab in Rockbox Utility. In Rockbox Utility I only tried the "Complete installation" from the "Quick start" tab, nothing else.

[MaitreSoda]

I forgot to mention that in my case, manual installation won't work whether I'm using the sansapatcher or the rockbox utility...

[thefred]

I'm in exactly the same pickle as MaitreSoda and Jwooten. It's with a new c250. I Just tried to install Rockbox - both the automatic and the manual method. In the automatic mode, I had to specffy the drive letter as it would not autodetect. It then allowed me to install Rockbox, but not the boot loader. I switched to manual installation and got hung up on the sansa patcher. It could not detect my C250.

Any thoughts? Anything else to try?

[bluebrother]

I had to specffy the drive letter as it would not autodetect. It then allowed me to install Rockbox, but not the boot loader.

You sure you don't have a v2 model? Please post the output of the About / System Info dialog of Rockbox Utility.

[thefred]

Thank you for answering. I'll bet it is a V2. I didn't know that V2 wasn't Rockboxable. Oh well, I have an old E280 that I'm sure must be a V1. I'll give that a try.

Here's the output from About-> System Info (the C250 is device L -- I can't see where the version is identified):
-------
OS
Windows version 5.1, build 2600 (Service Pack 3)

Username
phantom

Permissions
Admin

Attached USB devices
VID: 04b8 PID: 010a, Perfection1640
VID: 054c PID: 01bd, Silicon Media R/W

Filesystem
A:\, 0 MiB available
C:\, 1618 MiB available
D:\, 342870 MiB available
E:\, 49151 MiB available
F:\, 0 MiB available
G:\, 0 MiB available
H:\, 0 MiB available
I:\, 0 MiB available
J:\, 0 MiB available
K:\, 0 MiB available
L:\, 1127 MiB available
M:\, 0 MiB available
-----------------------
Thank you again for helping out a newbie.

[Febs]

Thank you for answering. I'll bet it is a V2. I didn't know that V2 wasn't Rockboxable. Oh well, I have an old E280 that I'm sure must be a V1. I'll give that a try.

Here's the output from About-> System Info (the C250 is device L -- I can't see where the version is identified)

What is the firmware version of the original firmware?  If it is in the 1.xx.xx series, it is a v1.  If it is in the 3.xx.xx series, it is a v2.

[bluebrother]

Attached USB devices
VID: 04b8 PID: 010a, Perfection1640
VID: 054c PID: 01bd, Silicon Media R/W

This is really strange -- this doesn't show any sign of a Sansa attached. For comparison, I get the following relevant line (among others):

VID: 0781 PID: 7451, SanDisk Sansa c250

VID is the vendor ID and that identifies the device being manufactured by Sandisk. The two lines you get also look like completely different devices judging from the description. Do you have a hub between player and PC or are you using front ports? If yes try connecting the player directly to a backside port.

[haithun]

yeah,

i have the same problem i have e280 v1 but the problem seem to be the bootloader because i can install rockbox from the installation menu. he downloads it and extract it.
but then if i try to use the bootloader installation it fails because he couldn't find any sansa

i found a way how bring rockbox back on your player its no really good solutions but one
because you just need to bootloader to let rockbox run take the rockbox utility 1.0.7b its the newest one that works than you copy rockbox 3.1 manually to the player

[bluebrother]

i found a way how bring rockbox back on your player its no really good solutions but one
because you just need to bootloader to let rockbox run take the rockbox utility 1.0.7b its the newest one that works than you copy rockbox 3.1 manually to the player

Please be more specific -- it doesn't help us fixing bugs if we don't have detailed information. Which version of Rockbox Utility did you try before, what OS are you running? What exactly is the error message when trying to install the bootloader? Are you using the Quick Start setup or the individual bootloader button? Bootloader installation was reworked with Rockbox Utility 1.0.8 and it's possible that there is a bug (though I have tested e200 installation myself and it worked flawlessly).

[haithun]

sorry for that. i've a win xp sp 3 and i used rochbox utility 1.0.9 and 1.0.8 with dll
the problem is that he first detects the sansa but than at the installation screen (all the bootloader installation, the complete and quick installation) he can´t find my sansa but i see it at the exporer.

i think the problem is at the detection because my "version.sdk" file at player says that i have a v1 with firmware version 1.02.24E but the "version.txt" says that the firmware version is 3.02.24E
this seems to be the problem that the rockboxutility has a mistake at the detection at the installation screen(it is a v1 beause rockbox ran before on it)

but i can install rockbox with the install rockbox button

[bluebrother]

the problem is that he first detects the sansa

Meaning detecting using the "Autodetection" functionality in the configuration dialog? Does it figure the correct drive letter?

i think the problem is at the detection because my "version.sdk" file at player says that i have a v1 with firmware version 1.02.24E but the "version.txt" says that the firmware version is 3.02.24E

No, that's definitely not the issue. You need to distinguish between autodetection as done in the configuration dialog, which also utilizes USB IDs to identify the player (which is used in case of the e200) and the detection done during bootloader installation. This is done to verify that you install the bootloader on a real player as it requires writing directly to the disk to put the bootloader in the firmware partition. That partition won't show up in Windows Explorer, thus the player showing up with a drive letter doesn't tell anything if installing the bootloader will work. If you would install the bootloader to a drive that is not an e200 you would cause damage to the filesystem on that drive, thus this additional check is necessary.

But using the older 1.0.7 of Rockbox Utility works with the same setup (same computer, player attached to the same USB port, same user logged in)?

but i can install rockbox with the install rockbox button

Installing Rockbox is simply unzipping an archive to the player. This applies to all packages you can install except the bootloader. Thus, as long as the drive letter of the player is correct, this will work just fine -- you could even install to any hard drive (which of course wouldn't make much sense).

[haithun]

yeah,
i mean the autodetect function and he find the drive letter and the type of player
and yes if you use the same user(i use "SuRun" a program that imitates the vista admin control but I've tested already as usual admin),the same PC, the same player, the same USB port with older rockbox utility 1.0.7 and 1.0.7b it works but you than need 1.0.9 to put rockbox 3.1 on it or you do manually

maybe you can make a rockbox utility version that is like 1.0.9 but with the old part for bootloader

[bluebrother]

maybe you can make a rockbox utility version that is like 1.0.9 but with the old part for bootloader

No. There is absolutely no point in that -- fixing bugs isn't done by rolling back changes (or improvements, like in that case -- the only annoying thing is that a bug came in).
Nevertheless, I managed to identify the issue. It's caused by Windows inability to open a device multiple times (or linux capability of doing that -- as linux is my main development OS it seems I overlooked testing exactly this combination with windows).

Maybe someone shouldn't make releases just before leaving for christmas ...

Edit: for the record, this was also reported as http://www.rockbox.org/tracker/task/9729 (unfortunately with much less information than in this thread).