Rockbox

  • Status Closed
  • Percent Complete
    100%
  • Task Type Bugs
  • Category Rbutil
  • Assigned To No-one
  • Operating System Sansa AMSv2
  • Severity Low
  • Priority Very Low
  • Reported Version Daily build (which?)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Rockbox
Opened by sraaf - 2011-12-16
Last edited by bluebrother - 2011-12-24

FS#12459 - RockboxUtility-v1.2.11 not checking mkamsboot 1.4 error fw 01.0 2.16

RockboxUtility-v1.2.11 does not report/detect that it fails to install bootloader at all based on Sansa Clip+ 01.0 2.16 firmware due to outdated mkamsboot Version 1.4

1. Please check return value of mkamsboot inRockboxUtility
2. Please update mkamsboot for 01.0 2.16 firmware
3. Minor mkamsboot, “Tested Clip+v1” also accounts for the v2 (the + versions of Sans Clip)

mkamsboot:
[ERR] Original firmware unknown, please try an other version. Tested Clip+v1 ve
rsions are : 01.02.09, 01.02.13, 01.02.15

google “anythingbutipod 02.01.16”

Closed by  bluebrother
2011-12-24 09:24
Reason for closing:  Not a Bug
Additional comments about closing:   Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407

We cannot prevent you from telling Rockbox Utility to install on a wrong drive. If installing files on the wrong drive there will obviously no error, and the player ignoring the "installed" files.

RockboxUtility-v1.2.11 successfully patched 01.0 2.16 for me. Can you elaborate on the problem you had?

sraaf commented on 2011-12-16 23:33

Thanks,

Problem:
SansaClip Updater replaced RB based on 2.15 by OF2.16, tried reinstalling RB several times using RockboxUtility-v1.2.11 based on 2.16 and even 2.15, reported “Success: modified firmware file created” but did not result in RB to become available again. Tried also the manual installation but mkamsboot-1.4/win32/mkamsboot.exe does not except OF 2.16.

Your remark:
Based on your remark downloaded the source and found 2.16 including checksum mentioned in mkamsboot.c. also proving mkamsboot-1.4.exe to be outdated for the Clip+ 2.16 OF.

Workaround:
Finally downgraded to/using 2.15 OF, removed .rockbox, restarted and could install RB based on 2.16 OF using RockboxUtility-v1.2.11.
http://mp3support.sandisk.com/firmware/clipplus/clipplus01.02.16.zip

So the actual problem here has nothing to do with 01.0 2.16 firmware. Instead you’re saying that you tried to install the bootloader, it patched, but when you rebooted your player the firmware wasn’t installed? Can you check if the firmware bin file was created on the player?

The System Log from Rockbox Utility would also be useful in figuring what was going on there.

Rockbox Utility does not use an “outdated mkamsboot 1.4”. Rockbox Utility always uses the current version of mkamsboot, and at the time of releasing Rockbox Utility 1.2.11 the code in svn was much newer than mkamsboot 1.4 so the latest released mkamsboot (which is dated 2010 on the download server) rejecting the firmware version does not imply anything about Rockbox Utility. The code of Rockbox Utility 1.2.11 clearly shows firmware 01.02.16 for the clip+ to be recognized.

Please elaborate what you mean by “3. Minor mkamsboot, “Tested Clip+v1” also accounts for the v2 (the + versions of Sans Clip)”, I don’t understand what you’re trying to say here.

sraaf commented on 2011-12-18 20:20

1. Spend hours in trying to reproduce the problem and looking at the code.
After ‘installation’ no Warning or Error is reported based on the at that moment connected device. Found a nice patched RBfw on my photo USB stick (but could have been another incompatible player as well)

Trusting RBUtil and reading no Warning or Error in the Progress screen my habit is to disconnect the cable from the computer and picking up the player later on.

2. Elaboration mkamsboot , http://www.rockbox.org/wiki/SansaAMS → “Port Status” → there are 2 flavours AMSv1 and AMSv2, mkamsboot while running only reports v1 while also working for v2 (at least Clip+)

After ‘installation’ no Warning or Error is reported based on the at that moment connected device. Found a nice patched RBfw on my photo USB stick (but could have been another incompatible player as well)

Sounds like you picked the wrong USB device when installing, so the patched firmware wasn’t added to your player.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing