The "My ipod install went wrong" Thread. **Updated 6th Aug 2007**

[scorche]

And my point is that Rockbox Utility is not quite ready to become the official install method yet.  It still needs some testing and tweaks.

[Llorean]

By which he means "The manual is downloaded by Rockbox Utility, and when Rockbox utility is made the official method, the manual that it downloads will include instructions for it, but at this time they would either confuse people NOT testing new software, or require additional code in RBUtil that would just have to be cut out shortly later."

[GodEater]

That is the intention - you however, have walked into the process right in the middle of the transition period. There's not much we can do about that I'm afraid - you'll just have to bear with us.

[bluebrother]

When I got the brief error message about a "mount point" it would have made more sense for the error message to have read something like "Detection of Player Has Failed. Would You Like to Auto Detect? Yes/No."

If autodetecting the device failed there is no way to detect the mount point. So this won't work at all.

Then, why after detection did the software not automatically issue a "Warning: Player Must Be Formatted Win-Compatibile By iTunes" immediately and before the full install button was pressed resulting, this time, not even in a dialog box but a terminal-screen warning.

Because it hasn't been implemented yet. As you should have found on the wiki page of Rockbox Utility it just has been released. Currently it's a bit centric to experienced users, but honestly, which unexperienced user should replace the firmware of his player anyway?
 

Why, instead, does not that section of the manual (generated, after all, by the RockBox Utility) reference the actual software being used and which, I assume, is at least one generation newer than ipodpatcher?

Because it hasn't been done yet. Feel free to update the manual and post a patch. And the manual is not and will never be generated by Rockbox Utility.

As I said earlier, Rockbox Utility is really new (the Qt port started less than 2 months ago!). We're doing open source here and follow the common "release early, release often" rule. This of course generates issues like software and documentation not matching, but everyone is welcome to help fixing it.

Just to explain your various "why" questions ...

[im1dermike]

[INFO] Ipod model: Video (aka 5th Generation) ("winpod")
Enter i to install the Rockbox bootloader, u to uninstall
 or c to cancel and do nothing (i/u/c) :i
[INFO] Using internal bootloader - 47112 bytes
[INFO] Moving images to create room for new firmware...
 Error reading from disk: Data error (cyclic redundancy check).
[ERR]  Write failed
: No error
[ERR]  Image movement failed.
[ERR]  --install failed.
Press ENTER to exit ipodpatcher :

any ideas on this?

I'm getting this same error.  I've never frozen my iPod.  Have any resolutions to this problem been documented?

[GodEater]

It's usually been down to a faulty cable.

[im1dermike]

So the USB cable I'm using to connect my iPod to my computer, which has always worked before, is the cause of this bootloader installation error?

[Llorean]

He said "Usually." Feel free to do some testing to determine if it's something else.

[im1dermike]

Just tried it on my firewire cable with the same results.

[lanfear]

Could you add this to the first page of this thread?

After updating, RockBox freezes at the start (logo) page
Delete or rename your config (insert exact name) file in the .rockbox directory and reboot.


That has helped me a few times, but I update seldom and always forget it in between, making me panic and spending a lot of time before figuring it out. It might just help someone else too!

[Original post edited to clarify that the problem occurred after updating.]

[Llorean]

It'd be helpful if you figured out what was causing it to freeze (which line in the .cfg) and do some experimenting. If nobody actually reports and documents bugs, developers don't know they happen, and if nobody spends the time to track down what specifically triggers them those of us who don't experience them can't figure out what might be going wrong to work on it.

[lanfear]

It'd be helpful if you figured out what was causing it to freeze (which line in the .cfg) and do some experimenting. If nobody actually reports and documents bugs, developers don't know they happen, and if nobody spends the time to track down what specifically triggers them those of us who don't experience them can't figure out what might be going wrong to work on it.

Oh, of course! Unfortunately, I'm in a hurry now so I don't have the time to track down which specific configuration line caused the problem. While I really want to help improving the product, my first objective was to get rid of the freeze.

But it happened to me after updating Rockbox to a newer build on my 1G Nano, so deleting/renaming the config file could be added as a general troubleshooting tip for "freeze problems after updating".

[Llorean]

Considering how infrequently "Freezing after updating" is a problem (for example, it's never happened to me on my Nano) I'd much rather people came here, asked about it, and helped figure out what went wrong, rather than deleting their .cfg file and going about their day.

[lanfear]

Considering how infrequently "Freezing after updating" is a problem (for example, it's never happened to me on my Nano) I'd much rather people came here, asked about it, and helped figure out what went wrong, rather than deleting their .cfg file and going about their day.

Well if you're that confident about it since it never happened to you personally (do you hear how that sounds?), great!

Now I've atleast done what I can to increase the total accumulated Rockbox knowledge by adding it to the forum for people to find by searching.

[Llorean]

I'm confident it needs investigation. You do not add Rockbox bug workarounds to this. You seek to fix the bugs.