Installation / Removal > Sandisk - Installation/Removal

Problem with Rockbox manual installation on Sansa Clip Zip

<< < (4/5) > >>

bluebrother:
I've tried this (though on OS X right now) and I get the following output:


--- Code: ---$ ./mkamsboot-mac clpza.bin bootloader-clipzip.sansa patched.bin
mkamsboot Version 1.5
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[ERR]  Original firmware unknown, please try an other version. Tested ClipZipv1 versions are : 1.01.12, 1.01.15, 1.01.17, 1.01.18
[ERR]  Could not load clpza.bin

--- End code ---

You really don't get a "Original firmware unknown" output?

steak:

--- Quote from: bluebrother on January 12, 2013, 06:06:49 PM ---You really don't get a "Original firmware unknown" output?

--- End quote ---

All I get is a black window flashing up for a fraction of a second. The same pops up for a longer time when using manual install for Clip+ AND I get a patched file (so far I assume it works), that's all. I managed to take a screenshot of both and I am definitely sure I could not see more lines in the 1st screen.



One thing seems weird to me. Why is rb Utility working with the Sandisk OF file v01.01.20 I downloaded and the manual install not ? Do they use different versions of mkamsboot.exe... and then why ? Or does the Utility work in a different way ?

bluebrother:

--- Quote from: steak on January 13, 2013, 04:25:03 AM ---All I get is a black window flashing up for a fraction of a second. The same pops up for a longer time when using manual install for Clip+ AND I get a patched file (so far I assume it works), that's all.

--- End quote ---

Pops up? Are you actually running the command from a cmd prompt? You are *not* supposed to start mkamsboot by clicking on it / creating a shortcut to start it.


--- Quote from: steak on January 13, 2013, 04:25:03 AM ---One thing seems weird to me. Why is rb Utility working with the Sandisk OF file v01.01.20 I downloaded and the manual install not ? Do they use different versions of mkamsboot.exe... and then why ? Or does the Utility work in a different way ?

--- End quote ---

Rockbox Utility gets updated more often than mkamsboot (and other firmware patching tools).

bluebrother:
This is how your command line output is supposed to look like (and how you are supposed to use it). I'm using the folder the manual suggests, though the folder used isn't relevant as long as you can write to it. You can also copy the text from that window (using the menu that pops up when you click the window icon). That output is what we call "log".

(Note: seems I can't attach files when editing an existing post)

steak:

--- Quote from: bluebrother on January 13, 2013, 08:05:17 AM ---Pops up? Are you actually running the command from a cmd prompt? You are *not* supposed to start mkamsboot by clicking on it / creating a shortcut to start it.

--- End quote ---
My mistake, I never realized what the manual meant by "cmd prompt" and never actually used it !! Instead I executed the command line directly through WinXP StartMenu>Execute>command line>Ok_button.

So much for the time wasted ! Now I understand all about the  bloody "log". Sorry for all the hassle but that was foreign2 language to me.

(Funnily I started using computers when prompt or whatever I should call it were just about to be replaced by Windows, so maybe I should have remembered...)

Back to subject, now at last I do get the log indeed :

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version