FiiO M3K Install (Native port)

[amachronic]

You need to hold down the rewind / fast forward buttons in the WPS. There's no problem with it as far as I'm aware. You can use the touchpad debug menu in System > Debug > View HW Info > Touchpad to verify the touchpad is working properly. You should see button: 00000040 when holding rewind and button: 00000080 when holding fast forward.

[7o9]

On build 025f780685-211229, I get the following panic when I plug in a USB cable connected to a PC while the M3K is off:

*PANIC*
Exception occurred: Trap Instruction [0xffff8be5] at 0x800683d0 (stack at 0x80002814)

If I turn it on first and then connect the USB, it is fine. The value in square brackets is not always the same, I have also seen 0xffbf8ae5. The other two address are always the same.

I have seen the same on the Q1 once, with this message:

*PANIC*
Exception occurred: Trap Instruction [0x3f77bff7] at 0x8006b83c (stack at 0x80002814)

On both the M3K and the Shanling Q1, the behavior is also very odd when 'USB Mode' is set to 'Ask'. On the M3K, when you unplug the USB cable it will ask if you want to enter mass storage mode. If you answer 'no', you will end up with a blank screen (apart from bar at the top) and can only shutdown the player. If you answer yes, you will end up in the menus and can still use the player. On the Q1 you keep getting the same prompt and seem to stay in 3x3 mode until you manage to start something else that resets the touchscreen mode. If you manage to click something that the yes/no prompt sees as 'no', you end up with the same blank screen as on the M3K.

I have also gotten the following panic (M3K) when answering yes or no on the 'enter mass storage' prompt when plugging in the USB cable while the player was turned on and running Rockbox:

*PANIC*
TLB refill handler at 0x8007f14c! [0x0]

A similar panic can be achieved on the Q1 the same way:

*PANIC*
TLB refill handler at 0x80082324! [0x0]

Both do not always happen but seem a result of attempting to exit the yes/no screen by a combination of touching the screen/touchstrip and pressing buttons.

[amachronic]

Thanks for the detailed report! It's a division by zero error caused by a mistake on my part when I added the improved time estimation (96cfe329a6). Gerrit still seems to be down so I'm unable to merge any fixes right now, but I'll fix it as soon as I can.

On both the M3K and the Shanling Q1, the behavior is also very odd when 'USB Mode' is set to 'Ask'

I know. Ask mode is completely broken on native ports since the yes/no screen prevents Rockbox from responding to any USB requests, so the host computer thinks the USB device is broken. Crashes on the Rockbox side are another matter, but hardly worth dealing with when the feature is so badly broken.

It's probably best to disable the 'ask' feature on native ports until it can be fixed properly -- you're not the first person to report this.

[sourex]

You need to hold down the rewind / fast forward buttons in the WPS. There's no problem with it as far as I'm aware. You can use the touchpad debug menu in System > Debug > View HW Info > Touchpad to verify the touchpad is working properly. You should see button: 00000040 when holding rewind and button: 00000080 when holding fast forward.

i have not any things in debug with HW ? but i have a workaround for me with 2 min steps at every push.
Next an last and biggest problem. The Button for lock doesnt work. Do u have a solution for this ?

[amachronic]

sourex, are you using the old XVortex port - with the graphical boot menu to pick between rockbox and the fiio player? The problems you're talking about sound like complaints I have seen about the xvortex builds. They do not happen for me on the native port (nor should they happen).

There's been a native port for a while now - the first post in this thread explains how to install it. Basically, the native port replaces FiiO's buggy Linux  kernel and uses Rockbox as the kernel, just like sansas or ipods do. Admittedly installing the bootloader is a pain on Windows, so if you don't want to go through the 'official' install process, another user on the forums (vitt13) made a package which includes the Rockbox native bootloader, which you can install like a normal M3K firmware update:
https://www.mediafire.com/folder/p2l3a22u3d7kk/M3K_fw_1.4.5_dualboot_rb
(original forum post)

(Mind you - I've never tested his update, but it should work.)

[projeKct]

I followed all instructions, and I can boot in Rockbox by pressing Power, or I can boot in FiiO mode by pressing Play+Power.

But when I press Play+VolUp+Power, I doesn't boot in FiiO recovery mode. I only see the button light but the LCD remains off.

If for some reason some part of your flash got corrupted/wiped, I have a full flash dump you could recover with. Unfortunately I don't have anything rigged up to easily dump or restore bits & pieces of the flash. I can spin up something but it may take a couple of weeks.

If you really need to use the Fiio recovery, and you took a bootloader backup (fiiom3k-boot.bin), then you can restore it using the RB bootloader. That will restore the Fiio bootloader and should let you access the recovery. But this will only work if the rest of the flash is intact, which you can't easily determine yet.

Hi amachronic,

Does your full flash dump is still available? How can you transfer it to me? How do it "install" it?

I'm still not able to boot my rockboxed M3K in FiiO recovery mode, and sadly I don't have a bootloader backup (fiiom3k-boot.bin)

Thank you, or anybody else that want to help!

[amachronic]

I'm still working on the bootloader, slowly. It's been a fairly big overhaul, not just adding flash dump/restore but other fixes, improvements, and a test suite to weed out the inevitable bugs. I've still got to turn the mess into something sensible to commit. I added the dump/restore part in the last 2 weeks, so it's technically working - just not very well tested. So sorry about the delay... I made the mistake of giving a time frame, which I've blown way past. It'll be ready eventually.

I can't believe I forgot to mention this -- but there is a pristine backup on the wiki which I posted ages ago. https://www.rockbox.org/wiki/pub/Main/FiioM3K/nand.bin. Rename this file to fiiom3k-boot.bin, and use the bootloader restore option. This gets you back to the original firmware, so you will be able to use its updater if you want to upgrade/downgrade the OF, but if you reinstall Rockbox you'll run into the same issue again.

Restoring from that backup will only work if your flashed recovery kernel is intact, but I think that is highly likely. At any rate, I don't think the restore should cause any further damage. I think it's more likely that the dual boot configuration in Rockbox is wrong (for some reason) and the recovery kernel can't boot up properly, rather than the flash getting damaged.

[projeKct]

I can't believe I forgot to mention this -- but there is a pristine backup on the wiki which I posted ages ago. https://www.rockbox.org/wiki/pub/Main/FiioM3K/nand.bin. Rename this file to fiiom3k-boot.bin, and use the bootloader restore option. This gets you back to the original firmware, so you will be able to use its updater if you want to upgrade/downgrade the OF, but if you reinstall Rockbox you'll run into the same issue again.

Wow! My problem is now solved, thank you very much! It went smoothly. And as you said, when I reinstall Rockbox, the problem is back, but now it really is a minor problem, as I can return my M3K to its original state anytime!

So thanks again, and keep us updated with new versions when you have some time.

[amachronic]

Glad to hear it worked -- and that confirms the problem is with Rockbox's dual boot support.

[HelgenX]

in CMD got these errors
[error] cannot open file bootloader.m3k (tar error: -2)
[error] Boot failed: -2
The un zipped bootloader file I unzipped and transfered was named "bootloader]
Should it be renamed?

I'm getting this error as well. I have the .rockbox folder extracted to the SD card, I have the m3k file on the root of my SD too, the m3k file and the exe file on my C drive. Installed the driver with Zadig for boot mode.

Edit: So I changed to libusbk driver, it now says "notice: rockbox bootloader version (version number)

Doesn't do anything else from here, I just turn off the device, the rockbox menu doesn't show up.

[vitt13]

I'm getting this error as well. I have the .rockbox folder extracted to the SD card, I have the m3k file on the root of my SD too

Make sure that your SD card is formatted in FAT32.

[amachronic]

in CMD got these errors
[error] cannot open file bootloader.m3k (tar error: -2)
[error] Boot failed: -2
The un zipped bootloader file I unzipped and transfered was named "bootloader]
Should it be renamed?

I'm getting this error as well. I have the .rockbox folder extracted to the SD card, I have the m3k file on the root of my SD too, the m3k file and the exe file on my C drive. Installed the driver with Zadig for boot mode.

Edit: So I changed to libusbk driver, it now says "notice: rockbox bootloader version (version number)

Doesn't do anything else from here, I just turn off the device, the rockbox menu doesn't show up.

The 'cannot open file' error means that jztool could not find the file on your computer. To clarify you should have this folder structure on your computer:

Code: [Select]

Rockbox/
  jztool.exe
  bootloader.m3k
And you should open the command prompt in the "Rockbox" folder. It does not have to be named "Rockbox", I just use that as an example; the important thing is to put both files next to each other in the same folder.

If the bootloader version is being displayed, it means jztool did open the file, and the bootloader should have loaded. The Rockbox menu will appear on your player, not the computer. If this isn't happening, try again with this command:

Code: [Select]

jztool.exe -l debug load fiiom3k bootloader.m3k
and post the output here.

[sourex]

sourex, are you using the old XVortex port - with the graphical boot menu to pick between rockbox and the fiio player?

Yes, thats right. I will try your port . Thanks for your work and information !!

Edit:
not so good with the m3k file
Rockbox not found and i can not flash again. I will write in the post u link.

[juupi]

Hi,
thanks for this great port to F3K.

Is there a way to use the volume buttons for skip tracks with long press when the screen is off (original FW do so)? Perfectly display stays off, so skipping and volume control is possible with hard buttons, even the player stays in the pocket.

I already searched in the manual. I only found 8.5.7. Advanced Key Lock. It looks like the function to control with locked screen should work with it. But on one hand I could not toggle Exempt Play and Exempt Volume on my device and I found no way to use volume button with long press for skipping.

[bahus]

Is there a way to use the volume buttons for skip tracks with long press when the screen is off (original FW do so)?

It's 2 keys combination in rockbox: Play + Vol Up and Play + Vol Down