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

[tipstir]

Update...

There was some issues using the prior 1.7xb and the new 1.8 Utility don't know why or what happen? Then the e260 locked up and didn't want to do anything. I even tried to clone e280 to e260 and that didn't work. Nothing worked as I thought it did, but e260 didn't or couldn't read from the database.  So finally all I could do is use delete everything on e260. Used Windows XP Pro SP2 format to FAT32 onto e260. Then use I had to use 1.7xb first then 1.8 to get the 3.1 installed. I don't know why this had to be done but everything works.

For some strange reason 1.7xb could install the correct files, but 1.8 couldn't I got error each time prior. I did install that missing dll but still had the same effect.

[Febs]

There was some issues using the prior 1.7xb and the new 1.8 Utility don't know why or what happen?

The current version of the Rockbox Utility is 1.0.9.

Then the e260 locked up and didn't want to do anything.

What do you mean, "then the e260 locked up"?  It just locked up on its own?  What exactly were you doing at the time it locked up.  What do you mean by "locked up"?

I even tried to clone e280 to e260 and that didn't work. Nothing worked as I thought it did, but e260 didn't or couldn't read from the database. 

I thought you said it was locked up?  Were you able to do things other than use the database?

[tipstir]

There was some issues using the prior 1.7xb and the new 1.8 Utility don't know why or what happen?

The current version of the Rockbox Utility is 1.0.9.

Okay it's now 1.9...

Then the e260 locked up and didn't want to do anything.

What do you mean, "then the e260 locked up"?  It just locked up on its own?  What exactly were you doing at the time it locked up.  What do you mean by "locked up"?

I was trying to play a song it just didn't play so it would just go back to the main menu and freeze-up! No song would play no matter what I did..

I even tried to clone e280 to e260 and that didn't work. Nothing worked as I thought it did, but e260 didn't or couldn't read from the database. 

I thought you said it was locked up?  Were you able to do things other than use the database?


It did lock-up and had to just press down  on the power/menu button for a long-time before it would say Shutdown then that would hang a bit before it turned off. I quickly tried to see if it would open a file folder under XP when you do a USB and it did.  Cloning didn't work even after removing Rockbox manually. I've tried everything. So best bet was to format the unit to FAT32. At the time you only had the 1.8 utility then that didn't work because of the missing dll. So now you have 1.9. I had to use 1.7b to restore Rockbox. Turn on the Sansa e260. Turn it off. Use 1.8 to install the 3.01 version. That worked! I don't know what happen it just didn't updated to 3.01 so easy on both the e260 and e280. They both have the latest firmware update from Sansa.

But it works now no problem... Should I run 1.9 or just leave it as it is...?  I have some cousins who had purchased couple of e250 during Christmas. I had installed Rockbox 1.7b at the time. It was weird install on them the Rockbox. First it was there, then after a shutdown and turn off Rockbox was removed and Sansa default was showing. I had to re-install Rockbox one more time until it was working on theirs.

I wanted to tell them about 3.01, but I know can tell them to use 1.9 instead..

[Febs]

At the time you only had the 1.8 utility then that didn't work because of the missing dll. So now you have 1.9. I had to use 1.7b to restore Rockbox. Turn on the Sansa e260. Turn it off. Use 1.8 to install the 3.01 version. That worked! I don't know what happen it just didn't updated to 3.01 so easy on both the e260 and e280. They both have the latest firmware update from Sansa.

Please note that the current version of Rockbox Utility is 1.0.9, not "1.9."  The current release of Rockbox itself is 3.1, not "3.01."

But it works now no problem... Should I run 1.9 or just leave it as it is...?

Rockbox Utility version 1.0.9 is the current version, and so that is the one that we recommend you use.  If you have a working installation of Rockbox, then you will only need to run the Utility if you want to upgrade to a new release or a more current build of Rockbox.  Whether you do that is entirely up to you (though if you are experience problems, we recommend that you try a current build before reporting the problem here).

In any event, this issue does not appear to be related to the topic of this thread, so if you have further questions, please start a new thread in the appropriate forum.

[davekaye]

I have V1 E260 and was not able to use the automated tool - Sansa not detected.  But I was able to do a manual install.  I am using Win XP/SP3. 

[bluebrother]

I have V1 E260 and was not able to use the automated tool - Sansa not detected.  But I was able to do a manual install.  I am using Win XP/SP3. 

Please read the whole thread. I already explained the issue at http://forums.rockbox.org/index.php?topic=19914.msg142194#msg142194

Besides, issue reports don't help at all if not stated in which version the issue appears.

[gaucho84]

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).

Hello. I have received today my Sansa E260 and was ready to install RockBox when I faced the same problem other reported. I would like to know if it's going to be a fix and when?

Thank you

[petulant]

Had the same problem on my e280. in xp it did not detect the player. So i tried the manual way and just copied the main file to the player. When I tried to install the boot file I got the same problem as with automatic installation. So then I simply just switched to mandriva(linux) and followed the manual and then after some lines in the terminal(very simple, just follow the guide in the manual) it found and installed the bootloader.. so untill there will be an update, use linux to install..

[ellory]

I am having the same issue with my e250.  Installer version 1.0.9, latest firmware from Sansa, WinXP SP4

I'm confused, was this supposed to be fixed in 1.0.9 or do we need the next update?

[bluebrother]

I am having the same issue with my e250.  Installer version 1.0.9, latest firmware from Sansa, WinXP SP4

The posts above clearly state that the problem exists in Rockbox Utility 1.0.9 (and 1.0.8, but that's not stated above).

Hello. I have received today my Sansa E260 and was ready to install RockBox when I faced the same problem other reported. I would like to know if it's going to be a fix and when?

The issue is already fixed in svn but no new release has been made since (mostly due to RL issues). Besides, we do not estimate any timeframes, and given the fact that developers also have a real life I'm quite annoyed reading questions about dates. Additionally, all questions you asked are already answered on the Rockbox Utility wiki page

Until a new release is made you can either build yourself from svn, use sansapatcher instead for installing the bootloader (it does only affect the bootloader) or use the older Rockbox Utility 1.0.7 for installing the bootloader. To install Rockbox 3.1 Rockbox Utility 1.0.9 is needed (again, not for the bootloader).

[gaucho84]

I am having the same issue with my e250.  Installer version 1.0.9, latest firmware from Sansa, WinXP SP4

The posts above clearly state that the problem exists in Rockbox Utility 1.0.9 (and 1.0.8, but that's not stated above).

Hello. I have received today my Sansa E260 and was ready to install RockBox when I faced the same problem other reported. I would like to know if it's going to be a fix and when?

The issue is already fixed in svn but no new release has been made since (mostly due to RL issues). Besides, we do not estimate any timeframes, and given the fact that developers also have a real life I'm quite annoyed reading questions about dates. Additionally, all questions you asked are already answered on the Rockbox Utility wiki page

Until a new release is made you can either build yourself from svn, use sansapatcher instead for installing the bootloader (it does only affect the bootloader) or use the older Rockbox Utility 1.0.7 for installing the bootloader. To install Rockbox 3.1 Rockbox Utility 1.0.9 is needed (again, not for the bootloader).

thank you.

here´s what I did:

installed bootloader with utility v 1.0.7
installed all the rest with frontend 1.0.9 (3.1)

no problem at all...

[ellory]

Thank you gaucho84

[Dasha]

I have the same problem as the Next 3 Pages on this topic EXCEPT I cannot Automatic Download to a Sansa C200  Could this be the reason

Warning: When first starting ROCKBOX UTILITY run “Autodetect”, found in the configuration dialog (File → Configure). Autodetection can detect most player types?   
If so It contradicts this:

Select USB MTC Before Downloading?

I did everything that the others did from the manual I switched to USB MTC Mode [maybe we all should have stayed in “Autodetect” or is that only after installation’ on initial startup???] > then Downloaded as "Run" the Latest Version.
I downloaded as “Run” from R/Box Utility’ then My Programs> Sansa c200> and SAVED R/Box to Sansa c200 folder? I did not try and place it in Music, Playlist, Data, or any of those files at this point (How Do I Find the Root File) R/Box Icon was in the Sansa Dive E page as a Separate File so I opened and went to  Opened the R/Box Icon and clicked on Big Install and I keep getting

HTTP Network Error: HTTP request failed. Please check your Network Settings and Proxy Settings
Cannot Read Version Information

Version Info: Product Rev.: PP5022BF-06.10-S301-06.10-S301.01.07PRT
Base Code: 06.10-S301-06.10-S301.01.07PRT
ODM Ver.: S301-06.10-S301.01.07PRT
OEM Ver.: S301.01.07PRT
Build Type: RT
Build Date: 2007.01.06
Build Number: (Build 23.01)       
Can somebody Help Please and Please Explain it in "Easy Dumbmans" terms I don’t know anything about Rootkits and Stuff, Thanks Dasha                                                                                                                                                                 

[bluebrother]

HTTP Network Error: HTTP request failed. Please check your Network Settings and Proxy Settings
Cannot Read Version Information

1. You picked a minute in which the download server was down. This is extremely unlikely and I don't know of any recent outtakes.
2. something is broken with your network connection. Are you using a proxy to connect to the internet?

[Dasha]

Hi bluebrother Thank you for your advice and Patience

I will get back to "Internode" today and get it fixed I can tell them what's wrong this time! Thanks again bluebrother, Dasha