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

[bradesp]

Guys,

I'm stumped.  Connected by v1 e260 via msc/usb and mounts as Drive F:.

I run the RockBox install utility and it doesn't auto detect, but when I hit the browse key it automatically defaults to my my e260 sansa on drive f:

I then click "complete install" and i receive an error message indicated that "no sansa is detected".

Please see my screen capture.

BTW, I have full admin rights on my laptop.

Any suggestions?

bradesp

[saratoga]

Is it in MSC or MTP?

[bradesp]

Sorry, I had a typo in my orig post...   I'm using MSC to connect via USB.

[jwooten]

We are having exactly the same problem with a v1 e280.  Both the automated installation and sansapatcher crap out with "No Sansa Detected"

We've tried both XP and Vista platforms.  We have removed the sansa updater.  The USB mode IS set to MSC.  We have sansa f/w 01.02.24A in the e280.

Messed around with this thing for three hours today with no luck!

[pjcpj]

I'm having the same problem.  I just bought a refurbed e280 so there is no box/discs/instructions, etc.  But I was able to get everything I needed to run it off Sandisk's website.  Windows (I'm running XP SP3) is detecting it as drive F:/.  I have run the Sansa Updater and verified that it is v1 (1.02.24A to be precise).  I'm connected via MSC in USB Mode.  I can browse to it in Rockbox and select drive F but when I click Complete Installation from Quick Start the error comes up that Sansa Not Detected. 

I did some research and noticed that this was a known error last year that was fixed by running the Sansapatcher in Linux.  This is something that I am not able to do so any other suggestions (within Windows) would be greatly appreciated.

**** Great news!  I found a fix.  It's amazing what you can do when you choose to READ THE MANUAL.  Rather than doing an automatic install I did it manually.  Select the option from the Rockbox download page to manually install.  It does take a little bit longer than the auto install but it worked like a charm for me.  GOOD LUCK 

[jlslate]

I upgraded to the newest Sansa firmware (version 01.02.24A) and of course it wiped out rockbox. I was unable to re-install it via the automatic method, as the above posters did, with the same symptoms. It couldn't find the Sansa, but then would say that it found it but couldn't install. I performed a manual install, but it still didn't work. I realized that the subdirectory installed was <rockbox> instead of <.rockbox>. I couldn't rename the directory via File Manager, and instead had to open a cmd prompt and do it there. (This is on Vista, by the way.) Works fine now.

Jim

[jwooten]

Well neither the automated or manual install instructions worked for me on the e280.  sansapatcher immediately comes back and says that no e200s were found and aborts.

are there switches on the sansapatcher that can tell it what to do and where to do it?  I've been cruising the web site for an hour this morning looking for that detail and it doesnt seem to exist...

[Chronon]

Does the Sansa appear as a drive letter in Explorer?  I ask because I have read of instances of the Sansa not connecting to the PC due to a very full disk.

[jwooten]

Yep, it shows up as drive F for us - we can browse the disk, check out the .rockbox directory (did the manual unzip to get that in there) but absolutely no dice with running sansapatcher.exe.  It exits out with "no sansa detected".  And yes, we are running it as administrator and no, the sansa updater software has been removed.

[Llorean]

Can you just confirm what the actual official firmware version is on that player?

[bradesp]

One possible culprit is the updated firmware everyone appears to be using (myself included) version 01.02.24A ...  I upgraded the firmware on my e260 refurb prior to attempting the RockBox install.  I have a second e260 refurb I purchased a while back that I have not yet updated the sansa firmware..  I will attempt to install rockbox on this unit and report back what happens.  If it works, then I think it's safe to say that the new firmware is the cause of this current install problem.

Stay tuned.

Ok, just tried the installer on my other e260 that runs the older firmware 01.02.18A and guess what?  Identical problem...  installer can't see the sansa, yet my XP laptop shows it as drive F:\ on my computer (I have the e260 setup as MSC so it's mounts as a USB flash drive when connected to the computer).

It's now up to the wonderful folks here on RockBox to help us debug this issue.

FYI, I've attached a screen shot showing this second e260 clearly mounted as an F:\ on my laptop.

Hoping for a solution soon!

Success Finally!

I used the manual install procedure in the manual and I'm good to go!  Hopefully one of the RockBox developers can sort out the issue with the autoinstaller.

Thanks!

[MaitreSoda]

I have the exact same problem that jwooten, meaning that although I followed to the letter the instructions given in the manual, neither will the automated or the manual installation work... There is always an error with the detection of the player. Uninstalling the Sansa Updater and rebooting didn't change a thing.

I have a Sansa e280, with the 01.02.18A firmware wich I can see as drive F: in "My Computer".

If anyone has any idea, I'd be very interested

Thanks !

[tipstir]

I had same issue I just backup everything on the unit and had wipe off everything manually. Then use the new program utlity to install a fresh copy of 3.1. Added my music manually to the Music folder. Ran database on the over 1,000 music files. Reboot the Sansa again. Everything works.

e260 and e280

I am using the default theme and got rid all the other themes.

[Chronon]

Themes (whether they work or not) won't affect the installation of Rockbox.

[MaitreSoda]

I had same issue I just backup everything on the unit and had wipe off everything manually. Then use the new program utlity to install a fresh copy of 3.1. Added my music manually to the Music folder. Ran database on the over 1,000 music files. Reboot the Sansa again. Everything works.

e260 and e280

If I understand well, you recommend to format the unit and try again ? I don't really see how this could have an influence on wether the software sees it or not...