Rockbox Technical Forums

Third Party => Unsupported Builds => Topic started by: Bilgus on July 10, 2017, 08:44:27 PM

Title: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on July 10, 2017, 08:44:27 PM
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite

Multiboot bootloader and firmware allows Sd card boot.

By putting the multi-boot bootloader on your device you can still run rockbox from the internal memory like normal.

Edit 11-15-2019:

Dev versions of the firmware now include redirect code
simply place the .rockbox folder and rockbox_main.<playername> on the root of the SD card and you should be good to go

[/color]

Edit 4-28-2021:
Windows users make sure you have show file extensions for known filetypes
or use the trick for forcing windows to use your filename in entirety - including quotation marks around 'pathname/filename.<player>'
see:
https://www.thesitewizard.com/faqs/save-without-txt-extension-notepad.shtml


Alternatively by using a special firmware build that allows the boot drive to be passed from the bootloader
you can run Rockbox from a sd card and you can even direct the bootloader to run the firmware from a
different root folder within the sd card.
http://www.mediafire.com/folder/x9hvpqrmfx76n/Multiboot_Firmware


Currently only for select players; The list of supported players will eventually be expanded.

For those of you who can compile your own builds see:
(Gerrit) g#1556 g#1613
for the requisite patches

Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml (https://www.rockbox.org/daily.shtml)
Clip+, Fuze+, FuzeV2, ClipZip users I have compiled everything you need, builds are at this link:
https://www.mediafire.com/folder/jmkihef72v62p/Multiboot_Bootloaders
http://www.mediafire.com/folder/x9hvpqrmfx76n/Multiboot_Firmware
https://www.mediafire.com/folder/bt7aow95pwlo8/MultiBoot_Bootloaders
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite

The proper layout of file: rockbox_main.<playername> is imperative;
The file either needs to be completely empty for the root of the SD card
or a single slash '/' this will instruct the bootloader to look in SD/.rockbox

The text editor within RB seems to add a (EOF) as does linux so use
'touch rockbox_main.<playername>' in linux
or simply put a single forward slash in the file '/' (no quotes)


Clip+ User:
Edit-2022-
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
First download clppa_MBOOT.zip
unzip the file clppa_new.bin to root of internal storage rename as clppa.bin,
safely remove device then reboot and enter original firmware ( left button on DPAD )
wait till device turns off

DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
Next download MultiBoot_FW_ClipPLUS [latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called rockbox_main.clip+ in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the current boot drive
if not check that the rockbox_main.clip+ file is actually empty or single slash '/'.

Fuze+ User:
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
First download fuzeplus_MBOOT.zip
enter original firmware ( Volume Down )
unzip the file firmware_new.sb to root of internal storage while connected in the Original Firmware USB MODE rename as firmware.sb,
safely remove device then reboot and again enter original firmware ( Volume Down )
wait till device turns off

Edit-2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
Next download MultiBoot_FW_Fuze+ [latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called rockbox_main.fuze+ in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the
current boot drive if not check that the rockbox_main.fuze+ file is actually empty or single slash '/'.

ClipZip User:
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
First download clpza_MBOOT.zip
unzip the file clpza_new.bin to root of internal storage rename as clpza.bin,
safely remove device then reboot and enter original firmware ( left button on DPAD? )
wait till device turns off

Edit-2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
Next download MultiBoot_FW_ClipZip [latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called rockbox_main.clipzip in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the current boot drive
if not check that the rockbox_main.clipzip file is actually empty or single slash '/'.

FuzeV2 User:
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
First download fuze_v2_MBOOT.zip
unzip the file fuzpa_new.bin to root of internal storage rename as fuzpa.bin,
safely remove device then reboot and enter original firmware ( Left on the click wheel while powering on )
wait till device turns off

Edit-2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
Next download MultiBoot_FW_FuzeV2_[latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called rockbox_main.fuze2 in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the current boot drive
if not check that the rockbox_main.fuze2 file is actually empty or single slash '/'.

Advanced:
you can also redirect the firmware to a different directory on the sdcard with Redirect file
rockbox_main.<playername> should again be placed in root of
drive you would like to be main, if this file empty or there is no leading
slash firmware will be loaded from /.rockbox in root of the internal drive
If instead a /<*DIRECTORY*> is supplied in rockbox_main.<name> then
firmware will be loaded from /<dir>/.rockbox/

The directory can have multiple levels however
leading slash MUST be included
trailing slash can be omitted
(eg. /test/.rockbox would be simply '/test' in the redirect file)

Notes:
Redirect file will not work on internal drive (whatever is default boot drive)

Volume with the highest index containing redirect file will be loaded
first.

Firmware file is checked for boot data region.
If bootdata region is missing, firmware
image will not be loaded.


On failure or if no redirect file is found load will fallback to
internal drive

As a safety feature a blank file, a single '/' or a /<directory> needs to be in the redirect file otherwise internal storage is loaded.

Firmware (.rockbox directory) may be copied to the sd card while still in device no need to actually remove the card to copy the firmware to it

Bootloader file goes in root of the internal storage on these 3 devices,
the Fuze+ however, needs to be in Original FW USB mode to recognize the addition of a new boot loader file (firmware.sb)

ROLO reboot after transferring the firmware is not supported yet so you need to actually turn off and turn on the player.

The proper layout of file: rockbox_main.<playername> is imperative;
The file either needs to be completely empty for the root of the SD card
or a single slash '/' this will instruct the bootloader to look in SD/.rockbox

The text editor within RB seems to add a (EOF) as does linux so use
'touch rockbox_main.<playername>' in linux
or simply put a single forward slash in the file '/' (no quotes)
Title: USB bootloader mode vs regular USB mode (Clip+)
Post by: Orbiter on August 08, 2017, 12:14:18 PM
I have installed a special Rockbox build that boots from an external SD card (reported version fc9c7d7M-170228). When I take out the SD card and then power on the player, it switches into "Bootloader USB mode".
In this mode, the player is recognized as an external drive. But when I put the SD card back and restart Rockbox,
 it does not show up in the computer.
Is there a way to make the USB connection work in regular mode, provided it works in the bootloader mode?
Title: Re: USB bootloader mode vs regular USB mode (Clip+)
Post by: johnb on August 08, 2017, 01:35:30 PM
The version fc9c7d7M-170228 is only mounting the external drive. I am using that on purpose.

Are you sure you have RB put onto the internal drive at all, i.e. is there a .rockbox directory with content?
If so, you can simply (re)move the rockbox_main.clip+ on the SD root and next time it should boot from internal.


If not you can download a newer version which boots from SD and shows both internal and external from here:
http://www.mediafire.com/file/ulqkbvq64a819rp/MultiBoot_FW_Clip%2B_5-22-17_rockbox-full.zip

Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml
by Bilgus.


Title: Re: USB bootloader mode vs regular USB mode (Clip+)
Post by: Orbiter on August 10, 2017, 10:25:00 AM
Thanks for the detailed explanation, but booting is not the problem. The problem is that the player does not show up as an external
USB drive and I cannot transfer audio files to it when it boots normally.
In USB bootloader mode it is recognized as two drives, one of which is the internal drive, and the other is probably the SD card slot.
So the question is how to make the player show up as an external drive under normal boot.
Currently it does not even appear as 'Unknown device', plugging it in has no effect.
Title: Re: USB bootloader mode vs regular USB mode (Clip+)
Post by: johnb on August 10, 2017, 01:07:59 PM
Have you hidden the internal drive?:
https://download.rockbox.org/daily/manual/rockbox-sansaclipplus/rockbox-buildch8.html#x10-1500008.5.9

Try and clear the .rockbox/config.cfg file or check whether you find the relevant line/setting in there ...
Title: Re: SANSA CLIP+ FUZE+ FUZEV2 ZIP: Bilgus Multiboot Bootloader and Firmware
Post by: saratoga on August 18, 2017, 11:54:30 AM
They are entries on our gerrit server here:

http://gerrit.rockbox.org/r/
Title: How To: Compiling Multiboot Firmware
Post by: Bilgus on August 22, 2017, 04:27:53 PM
You are going to want to see https://www.rockbox.org/wiki/WorkingWithPatches

When you go into gerrit you will want to click Download and save the patch files

Multiboot Firmware
http://gerrit.rockbox.org/r/#/c/1556/
http://gerrit.rockbox.org/r/#/c/1613/

They will need to be applied in sequence so save them and add a sequential number at the end eg. 1;2;3
[they download as zip files so do this as you unzip them as well]

So first lets start from a clean branch
note: if you already have stuff going on you will need to commit it or 'git stash ; All the below commands ; git stash pop'

type
Code: [Select]
git checkout master
git pull --rebase
git checkout -b multibootFW
patch -p1 < /path/to/fab3535-1.diff <-repeat for each patch
patch -p1 < /path/to/78d621f-2.diff


next after you are done adding the patches to your build (you might need -p0 or -p2 instead of -p1)
it is time to compile the firmware

so from the root of your rockbox dir ~/Desktop/rockbox for instance
type
Code: [Select]
mkdir <yourplayer>-multibootFW
cd clipzip-multibootFW
../tools/configure

then type the number of your player from the list for instance the clip zip is #65 so I type 65 then hit enter
next type 'N' for normal build
and finally type
Code: [Select]
make -j && make fullzip
this zip will get unzipped to your sd card

If you are continuing with other builds you will want to commit these edits

Type '..' to return to the root folder
first type 'git status' to get a list of the modified files
make sure the files don't start with ../ or you will need to go up a level by typing '..'
type
git add <fullfilepath>(..For each of the files we just patched)

OR if you FOR SURE don't have any other modified files
type
Code: [Select]
git add `git status | grep modified | sed 's/\(.*modified:\s*\)//'`

Finally type 'git commit'
add some text for description at the top (note empty commits do not save)
then hit CTRL 'o' and press enter to write commit message then press CTRL 'x' to exit

after all is done you can go back to master 'git checkout master'
and then start on your next branch git checkout -b <my totally awesome edits>'
or go back to your previous work and type git stash pop ( if you stashed work )

Thanks @ [Saint]


Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
Multiboot Bootloader [Most likely You won't need this use the precompiled bootloader instead]

You risk bricking your player if you mess up a bootloader build

Although most of these players do have recovery modes You Have Been Warned

Bootloader code is now in dev builds
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on August 27, 2019, 02:32:26 PM
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite

The bootloaders are on the mainsite now Rbutility will install them
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on September 22, 2019, 07:13:34 AM
Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite

The bootloaders are on the mainsite now Rbutility will install them

What does it mean it's on mainsite? Where is the option to install to sd card in rockboxutility?
Which version of rbutility should I use?

Thanks.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on September 22, 2019, 01:46:49 PM
do a bootloader install
the bootloader is backwards compatible

However,
rbutil doesn't have the option to install to the sdcard you need a special firmware version for the time being
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on September 22, 2019, 03:42:31 PM
do a bootloader install
the bootloader is backwards compatible

However,
rbutil doesn't have the option to install to the sdcard you need a special firmware version for the time being

I see... can you please tell me where I can get such firmware and what's the procedure to install it? The links above are all striken out or not available... I guess my Clip+ internal nvram is going bad and I'd like to transfer RB to the external card, before it dies...
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on September 22, 2019, 03:51:30 PM
Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml

http://www.mediafire.com/folder/x9hvpqrmfx76n/Multiboot_Firmware

That is a bit older than the current dev builds but perfectly serviceable
I'm not completely sure how RbUtil handles the bootloader I assume it'll just let you install the new one
If not I can walk you through how to do it manually


The firmware just needs to be unzipped to the sdcard and
a file named rockbox_main.clip+ with a single '/' (no return and no quotes)
made on the root of the card



Quote
The proper layout of file: rockbox_main.<playername> is imperative;
The file either needs to be completely empty for the root of the SD card
or a single slash '/' this will instruct the bootloader to look in SD/.rockbox
The text editor within RB seems to add a (EOF) as does linux so use
'touch rockbox_main.<playername>' in linux
or simply put a single forward slash in the file '/' (no quotes)
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on September 26, 2019, 06:09:46 PM
Oh, I see... thanks for the link. I need some more help, please.

First... some clarification... just in case: when we say SD card it means the external card plugged into the side of the Clip+, when we say internal memory it means the memory on the SoC.

What I did until now:
1. Downloaded MultiBoot_FW_ClipPLUS_11-17-2018_rockbox-full.zip and extracted it to the SD (SD card's: /.rockbox) card (that's my drive G).
    Note: that I'm transfering files with the SD card inserted into the Sansa Clip+ booted via rockbox. Is this OK?
2. Created the file on the SD card(!) G:/rockbox_main.clip+ (using cygwin: printf "/" > /cygdrive/g/rockbox_main.clip+). Checked the size, it was 1 byte.

I then went to rbutil 1.4.0 (on Windows) and installed the boot loader on both G: (that's my SD card) and also E: (that's the clip+ internal memory)
I also took care to eject both drives. Note that when installing the boot loader I get asked to provide the original firmware (clppa.bin). I see the firmware
file on the target drive, when finished.

When I rebooted the device I noticed that I'm still seeing all the old playlists from the internal memory (this should not happen, I guess).
I also checked the Debug menu for the Bootdata (is this Debug(Keep Out) ->Bootdata or something else?)... but could find no such entry. How can I check where did it boot from?
 
I also diffed the contents of SD/.rockbox before and after boot - no new files were created or changed (md5sum of all files under SD card's /.rockbox), which
leads me to believe it did not boot from SD card.

I installed the boot loader using both the stable (3.14) and dev version (5afdcdd) - no difference at all. I also tried to uninstall the bootloader
using rbutil, but it says that the bootloader could not be uninstalled on this device (that I should flash the original firmware to remove it).

I also tried to create empty SD/rockbox_main.clip+ - no luck, either. Heck, (in desperation) I even tried to create rockbox_main.clip+ on the
internal card :)  Still no luck.

I guess I'll need the instructions on how to install the correct boot loader. If possible on windows (cygwin)... or if that's not possible, I'll try to get hold of linux box. Maybe somone removed the multiboot code from the dev build?

Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on September 26, 2019, 07:34:36 PM
The bootloader has to be installed by booting into the sansa firmware
If you are doing it manually the bootloader here is the same one rbutil would build for you
https://www.mediafire.com/folder/jmkihef72v62p/Multiboot_Bootloaders

Clip+ User:
First download clppa_MBOOT.zip
unzip the file clppa_new.bin to root of internal storage rename as clppa.bin,
safely remove device then reboot and enter original firmware ( left button on DPAD )
wait till device turns off
Next download MultiBoot_FW_ClipPLUS [latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called rockbox_main.clip+ in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the current boot drive
if not check that the rockbox_main.clip+ file is actually empty or single slash '/'.

You have already copied your FW on the SD card I'd recommend you eject it prior to booting into the Sansa OF
otherwise it'll make you wait while it indexes it,
put it back after the device turns off when finished updating

Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on September 27, 2019, 03:31:15 PM
Oh, Yeah! :) Thanks, Bilgus!

Worked as a charm - the only minor detail was to set the USB mode to MSC when booted into the original Sansa firmware. Otherwise you see only the MTP Internal Memory device (which you can't safely remove). Did not try the update in MTP mode, though...

I can also see the Boot data menu in Debug and the old playlists are gone!

Thanks again... hope this will prolong the life of my salsa clip until there's (hopefully) a better device to put RB on.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: 1918mute on February 28, 2020, 10:05:28 PM
Hi, Bilgus,

I have rockbox previously installed on my Sansa Clip+ internal storage, I am not sure whether I need to uninstall the Rockbox firmware/bootloader from internal storage first.

I followed these instructions to install and it looks like it still boot rockbox from internal storage:

Quote
Next download MultiBoot_FW_ClipPLUS [latest date]_rockbox-full.zip and unzip to the root of your SD card
Finally create an empty file called Rockbox_main.clip+ in the root of the SD card
now put sd card in device and reboot; Under Debug menu you should have a new entry 'Bootdata' that lists the current boot drive
if not check that the Rockbox_main.clip+ file is actually empty or single slash '/'.
 

I could find the entry
Code: [Select]
Debug(Keep out) - Boot data
it shows contents like
Code: [Select]
Magic: rbmagic! There is a line says
Code: [Select]
CRC: BAD Does this mean sdcard boot failed?



Thanks very much!
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on February 29, 2020, 09:58:05 AM
Yes that means sd boot failed, you should be able to update the boot loader with rbutility
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on April 30, 2020, 05:38:47 PM
@Bilgus: I noticed that RB 3.15 was released - release notes say "Booting from multiple volumes is now possible.". Does that mean that I can install RB on the external SD card without doing all the steps above? I can't find more info on booting from multiple volumes, Does RockBox Utility support installation to multiple volumes?

After 8 months of running RB on the external SD card it started having write problems - like before on the internal memory. From the time RB was installed I never wrote anything to the SD card. The only thing that changes is that RB updates the recently played bookmarks. Is it possible that RB is always writing to the same sector and thus wearing out that specific sector by updating the bookmarks? Does it have any anti-wear-out logic? Like always writing to a new sector and discarding the old one? If there is no such logic I'm a bit weary of letting RB update the recent bookmarks (though that's one of the best features) since it will result in wearing out of the SD card.

Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on May 01, 2020, 11:35:13 AM
Found the answer (sort of) here: http://forums.rockbox.org/index.php?topic=53154.0

Before I read the link I installed 3.15 stable - first keeping the old multiboot loader (clppa_new.bin). Installation went fine, the files were there but I could not play anything. Also Debug->Bootloader was showing some weird magic.

I then reflashed clppa_new.bin (your old one)... It was probably not needed, anyway... put the latest development build on the SD card (like indicated in the link above). This time it worked - I can play files again. Don't know what's the issue with 3.15 stable, though.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on May 01, 2020, 02:34:10 PM
3.15 Release does not have the logic to remap the drive the DEV versions do though

Sorry I missed your previous question, short answer SD cards do wear out
Does RB do writes to the SD card when running from it YES
Will this wear it out eventually? MAYBE
Can you tell me how long that will take? NO CLUE

Here is the thing though the SD card is replaceable [ unlike the player :( ]
It probably has more to do with the quality of the SD card than Rockbox
Anecdotally I have been running the same SD card for ~2 years with usage 5 days a week 6 hrs a day will no ill effects and it writes several bookmarks daily
updated the music probably 5 times
Still I Can't tell you how your SD card will fare

You might be able to get those bad sectors marked and removed but I've only had marginal luck with that on USB Flash drives
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: SamoDadela on May 06, 2020, 04:55:57 PM
@Bilgus
Thanks for the answers.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: username_already_taken on November 22, 2020, 06:34:54 AM
Firmware file is checked for boot data region.
If bootdata region is missing, firmware
image will not be loaded.


Multiboot isn't working for me on Clip+ and I suspect this is the reason.

I installed the 2020 bootloader and am using a dev firmware build but the player doesn't work unless the internal flash directory is named .rockbox, which I take to mean that the firmware in the SD card is never being used (rockbox_main.clip+ with a single / is present in root of SD card).

How can I fix this?
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on November 22, 2020, 10:07:13 AM
I don't think 2020 bootloader was released yet did you build it yourself?

check boot data in both cases CRC should be OK

but further down if internal boot then it should read 00 00 00 00 00
on sd card it should read 00 01 00 00 00 (and Boot Volume <1> on supported fw)

The final thing is to re-make the redirect file rockbox_main.clip+ either completely empty or a single /
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: johnb on November 22, 2020, 10:49:08 AM
username_already_taken,

try the attached redirect file. Remove the '.txt' extension and put it into the SD root directory.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on November 22, 2020, 11:37:57 AM
I'm able to reproduce the issue it appears the bootloader is broken in the last weeks but i'll have to investigate a bit more

No I just happened to fall into the trap of using a file editor and it left a \n at the end

here are the freshly tested files I made from HEAD these worked for me

Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml
http://www.mediafire.com/folder/0xagre8mhvwmb/Clip%2B2020Multiboot
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: username_already_taken on November 23, 2020, 06:34:19 AM
I don't think 2020 bootloader was released yet did you build it yourself?

The final thing is to re-make the redirect file rockbox_main.clip+ either completely empty or a single \

I should have mentioned my screen is dead, I need to use voice navigation.

I test that I'm not using the SD card by comparing mtimes on files in the internal and SD firmwares (the latter never updates), and by renaming the internal folder (the player stops working).

I also mispoke, I'm not using the 2020 bootloader because the latest one is from 2019, this is what I'm using:
https://download.rockbox.org/bootloader/sandisk-sansa/clipplus/
https://download.rockbox.org/bootloader/sandisk-sansa/mkamsboot/linux-x86-64/
OF 01.02.16
Rockbox dev build with working voice file
Doing a manual installation because my Rockbox utility is outdated and the new binary doesn't run on Debian buster.

I tried both the 0 bytes and 1 byte forward slash variants, not backslash though, I assume that was a typo since everywhere else says /?

I will try the new files and report back soon, thanks for helping!

EDIT: quick update: the rockbox_main.clip+ file uploaded in that link is 2 byte with newline, I will fix it before properly testing
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on November 23, 2020, 12:46:23 PM
yes sorry it is a single forward slash, the \n won't matter if there is already a / in the file it just matters for empty ones IIRC

Go ahead and install that new bootloader just copy to the internal drive and reboot into the sansa firmware, it shuts off the device when finished so rather than risk turning it off too early just plug / unplug the USB after 15 mins and see if it boots and connects to USB
 (since your screen is out)

Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: username_already_taken on November 23, 2020, 12:51:06 PM
Still no luck with the downloaded clppa.bin and firmware, exact same behaviour.
Works perfectly from internal flash .rockbox/, not at all when internal flash directory is renamed. The .rockbox/ on the SD card is a straight copy of the one in internal flash, and a 1 byte / rockbox_main.clip+ is present on the SD root.

Not sure if it matters any but after doing manual bootloader installation, the clppa.bin file is left on the root of internal flash after installing.
Don't know if that's supposed to happen, or if it means the bootloader wasn't installed properly and despite all these attempts I'm still running the old bootloader.

Is there an easy way to debug this with voice operation? If not, I'll give up and keep on using the internal flash, no big deal.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: username_already_taken on November 23, 2020, 12:53:28 PM
Go ahead and install that new bootloader just copy to the internal drive and reboot into the sansa firmware, it shuts off the device when finished so rather than risk turning it off too early just plug / unplug the USB after 15 mins and see if it boots and connects to USB
 (since your screen is out)

I've just been copying, ejecting and powering off with gnome-disks, unplugging and waiting a minute.

Do you mean I need to boot holding left to call the OF, then wait?

EDIT: that was definitely it, rebooting into OF, waiting, then plugging in the USB cable and mounting shows a bunch of OF directories on the flash root and no more clppa.bin. And now it works, SD firmware is being used as expected!

Thanks again for the help and for your contributions to Rockbox in general.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on November 23, 2020, 02:29:20 PM
If clppa.bin is still there then it did not update

word of warning you must rename to clppa.bin before copying it to the internal drive
if you do the rename after it will not pick it up

to update it should just be copy the file power off then hold left arrow and power on

edit:
Good to hear glad you got it working

and Thanks :)
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: bahus on March 08, 2021, 01:41:47 AM
> you can also redirect the firmware to a different directory on the sdcard with Redirect file

It doesn't seem to work for me on my Sansa Clip Zip. I'm trying to load firmware (latest daily build) from /rbclipzip/.rockbox folder on my SD card.
On loading it gives me splashes "No .rockbox directory" then "Installation is incomplete" and then loads in failsafe mode.
Boot 9de8993af6

Boot data:
Bootdata RAW:
Boot Volume: <1
CRC: 1b6947cc
CRC: OK!
00: 01 00 00 00 00

If .rockbox is placed in root of SD Card everything works smoothly
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on March 08, 2021, 06:27:38 AM
Unfortunately I broke the patch that was supposed to do that functionality so it only works from the root of the card till I get back to it
Edit -2022-
DOWNLOAD A RECENT DEV VERSION FOR YOUR DEVICE
https://www.rockbox.org/daily.shtml

root redirect is in the dev builds now you can redirect to any folder
@amachronic also made a plugin to switch which build you run [Apps/multiboot_select]
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: odel on August 09, 2021, 01:16:52 AM
I had problems getting my clip zip to boot from SD until I formatted it as Fat32.

Now it works great!
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: bahus on March 04, 2022, 02:36:18 PM
> you can also redirect the firmware to a different directory on the sdcard with Redirect file

Bilgus
Just noticed that this feature is fixed with https://github.com/Rockbox/rockbox/commit/c9857098ac0a3173d5d03baa3c32d9a8e29faec8
Cool!

My tests result:
1) It doesn't work with `/rbclipzip` in redirect file. But does work with shorter folder name `/rbcz`. Is it expected restriction on folder length?
2) With .rockbox placed in the root directory of SD card, I see content of SD card right inside Files menu (folders and files). But now additional entry is appeared mircorSD0 (for internal) and microSD1(for SD card). Not sure if this change is related to your changes but it was only single microSD0 (for internal) before. microSD1 entry is redundant here.

And with `/rbcz/.rockbox` I see only 2 entries microSD0 (for internal) and mircorSD1 (for actual SD) in Files menu. Would be cool to see content of SD card right inside Files menu (basically behave in the same way when it's placed in root of SD)
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on March 04, 2022, 04:41:45 PM
I'll have to look into the name length, shouldn't be an issue.. IIRC its MAX_PATH @ 260 chrs and testing it I see it boots the file just fine but it appears to lose the last 2 chars once booted so yeah def a bug

Yes SD<0> and SD<1> are related to this patch, I'll have to see about the best way to hide them, not sure that enumerating everything in the root is the best idea as it could get pretty confusing but i'll try it

thanks for the report

Edit:
Oh nevermind I see the issue the buffer is too small in the redirect
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on March 04, 2022, 09:02:51 PM
Quote
>Yes SD<0> and SD<1> are related to this patch, I'll have to see about the best way to hide them, not sure that enumerating everything in the root is the best idea as it could get pretty confusing but i'll try it

yeah as I suspected it has to be this way if you enumerate the root of the SD into the redirected folder and it has the same dir names its a crapshoot on which folder you actually get (last mounted overwrites the prior)
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: Bilgus on March 06, 2022, 04:45:34 PM
Fixed as of today Mar 06 2022
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: skwal on May 12, 2023, 03:08:44 AM
because of problems with the internal storage i use rockbox on sd as decribed.
works.

but i have on question.
after using rockbox on sd i et two sd cards shown on the player
sd0: empty
sd1: my files

on the pc i only get one sd card: sd1 with my files


when  activate auto bookmark rockbox writes the bookmark.
but when i activate as start mode latest bookmarks he say: no bookmark found
manuel i ca find the latest bookmark (sd1)

is the problem that rockbox searches the bookmarks on sd0 and not on sd1 ? how can i solve this?
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 04, 2023, 02:07:52 AM
Could somebody please tell me what I'm missing with this?

I've got a clip zip with firmware version V01.01.20A and I've followed the instructions as I understand them:

- I downloaded a dev build and put that on my SD card (which is a Sandisk 16gb - fat32).
- I created the empty file as instructed with the proper name.

But when I switch it on it just boots straight into the sansa firmware.  Have I missed something?

Would really appreciate any help with this...

Thanks in advance!

Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: 7o9 on June 05, 2023, 03:00:55 PM
Did you miss installing the bootloader?
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 07, 2023, 05:29:49 PM
@7o9 Thanks  very much for your reply.

I didn't install a bootloader - I thought because that part was struck out in the instructions that it was no longer necessary and installing a Dev build somehow made it not necessary.  I saw it said the bootloaders were available on the "mainsite" but there was no link and I didn't see them on the mainsite.

So do I need to install the bootloader on my Clip Zip first?   And where are the bootloaders?

Thank you!
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: eugenkss on June 08, 2023, 03:31:20 AM
When you install via the Rockbox Utility, you can select to install also the bootloader.

For manual installation, there are instructions in the Rockbox Manual on how to install a bootloader
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 08, 2023, 09:16:15 PM
Hi,

Thanks for your help and please excuse if this is a silly question but does the bootloader get installed on the device or the SD card?

Also, I just copied the latest daily build onto the SD card as I thought that had the bootloader - so that's not right?

Previously I did use the utility to install and did select the bootloader to install but that didn't work either so I must be missing something.

Can somebody please clarify a couple of things for me:

1/  Is it necessary to use a dev build or does this work with the latest stable version?

2/  Is the Multiboot bootloader different from the regular bootloader? 

It says above that "Multiboot bootloaders for Sansa Clip+ ClipZip, Fuze+ Fuzev1 and Fuzev2 are now on the mainsite" but there's no link and I've looked but not found them - where are they?

I'm keen to get this working but can't see what I'm doing wrong.

Thanks for all the help with figuring this out!  Much appreciated!
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: 7o9 on June 11, 2023, 01:42:01 AM
The bootloader is installed to the device’s flash memory and must be installed so the device actually knows to look for Rockbox.

The multiboot functionality is part of the regular bootloader now. Only when it was new and experimental there was a separate version for the adventurous.

Dev builds of Rockbox are much newer than the latest release. They are stable and fully suited for daily use.

Rockbox utility is the easiest way. What went wrong when you tried to use it?
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 11, 2023, 01:50:23 AM
Thanks v. much for clarifying.

When I tried it it just booted straight into the Sansa software.

Should it work with the stable release version too? 
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: saratoga on June 11, 2023, 08:22:01 AM
That means you didn't install the bootloader. Run the installer, select bootloader and then install it.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 11, 2023, 04:54:53 PM
I thought that might have been the case but I ran the installer again and made sure the bootloader was selected and it still did the same thing - booted straight into the Sansa software.

This is what I did this time round:

1/ I ran the utility and, with the bootloader box selected and using the stable release, installed Rockbox onto my SD card

2/ Created the redirect file in the root of the SD card.

What did I miss?

Do I need to use a daily build?

Do I still need to create the redirect?

Does it matter what version of Sansa firmware is on the player?

Thanks so much you guys for your help with this!
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: bahus on June 11, 2023, 05:29:23 PM
If I remember correctly to install bootloader you need to flash patched original firmware(prepared by rb utility) using original firmware update procedure.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: saratoga on June 11, 2023, 06:54:37 PM
You need to install the bootloader onto the internal memory. The device cannot actually boot from SD, which is why it's dead if the internal memory fails.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 11, 2023, 07:05:40 PM
So I went wrong by failing to install the bootloader on the device?

So should I first install just the bootloader on the device via the utility and then install Rockbox without the bootloader on the SD card?

Really appreciate the help - thank you.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: saratoga on June 11, 2023, 07:56:37 PM
Yes
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on June 11, 2023, 08:08:15 PM
ok, thanks v. much, I'll give that a go.

And the bootloader in the utility is the same as the "multiboot bootloader"?  I'm still not clear as to whether they are separate things or the same...
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: 7o9 on June 12, 2023, 12:03:02 PM
They are not separate.
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: llnx1 on June 21, 2023, 02:20:04 PM
I directed boot file on MicroSD and now my Clip+ boots fine

Can I delete these files and folders that are in internal memory ?

(https://i.imgur.com/efgsePC.jpeg)
Title: Re: SANSA ClipZip Clip+ Fuze+ FuzeV2 Multiboot Bootloader and Firmware
Post by: cj17 on July 13, 2023, 10:58:50 PM
I finally got it working - thanks so much everyone for all the help!!!