Recent Posts
91
Theming and Appearance Customization / Re: Attempting to Alter USB Screen of a Pre-Existing Theme
« Last post by chronicallyoffline on March 04, 2025, 07:08:26 PM »So, you're going to want to look in the SBS file of the theme, rather than the CFG or WPS files. in the SBS (Statusbar-Screen) you should find a line with a conditional along the lines of
In the CustomWPS docs, 21 is the USB screen, so this conditional is saying
IF the Current Screen (%cs is USB Screen (21,) then Load Viewport (clearscreen) then Display Viewport (usb.) | IF NOT, do this other thing, etc.
If the theme doesn't have a USB screen section in the SBS file, you'll need to create it, define it, then point it to the USB image.
Up top, you would want to pre-load the image
From there I would look through the naming conventions in the theme to make sure you aren't accidentally calling something else twice. I took a look and it doesn't appear to have a USB screen implemented into it.
Edit: After looking further into the code, it seems VERY reliant on conditionals and info viewports. I'm taking a crack at it now, I'll post again if I get anything good haha.
Code: [Select]
%?if(%cs, =, 21)<%VI(clearScreen)%Vd(usb)|%VI(menu)%Vd(info)>In the CustomWPS docs, 21 is the USB screen, so this conditional is saying
IF the Current Screen (%cs is USB Screen (21,) then Load Viewport (clearscreen) then Display Viewport (usb.) | IF NOT, do this other thing, etc.
If the theme doesn't have a USB screen section in the SBS file, you'll need to create it, define it, then point it to the USB image.
Up top, you would want to pre-load the image
Code: [Select]
%xl(usb,usb,0,0)From there I would look through the naming conventions in the theme to make sure you aren't accidentally calling something else twice. I took a look and it doesn't appear to have a USB screen implemented into it.
Edit: After looking further into the code, it seems VERY reliant on conditionals and info viewports. I'm taking a crack at it now, I'll post again if I get anything good haha.
92
Theming and Appearance Customization / Re: track progress bar stops progressing at a certain point
« Last post by chronicallyoffline on March 04, 2025, 06:07:22 PM »For anybody in the future that might have a similar issue, I figured it out!
I used Windows Paint to edit the bmp, and had to make sure under properties that "black and white" (not "color") was selected; otherwise, the black of a color bmp is read as black. Black in a b&w bmp is read as the foreground color!
If you want a bit of an easier time creating or editing bitmaps for themes, Paint.net will let you save a bitmap as 1-bit, meaning two colors only. I use it over MSPaint because it's both free and full featured with options for editing smaller files with unaliased outlines.
93
Feature Ideas / Re: Using a computer to select tracks for playback on device (iPod 5/Video) via USB
« Last post by PlainRamenNoodles on March 04, 2025, 04:46:17 PM »Wouldn't really need two way communication, as I only want to play music from the iPod, using the raspi as a remote of sorts.Thank you!
94
Hardware / Re: Hifiman HM-801: Newer builds became unstable. Can I help?
« Last post by HungryDaze on March 04, 2025, 02:27:07 PM »I haven’t had a chance to test the latest build yet. However, I’ve encountered a different kind of problem, which I believe relates to the hardware section. I bought a new microSD card, the 'Samsung Micro SDXC EVO Plus 512 GB,' and found that Rockbox doesn’t work with it on the HM-801 — it just freezes. The stock firmware, on the other hand, works perfectly. This is a modern microSD card, while Rockbox works fine with my older one. My friend also had the same issue with a modern SDcard. Is addressing such compatibility issues too big a challenge, or is it something that can be resolved?
95
Apple - Installation/Removal / Re: No DFU devices found
« Last post by saratoga on March 04, 2025, 12:32:46 PM »If the apple firmware isn't working restore the iPod first or you won't be able to dual boot.
iPodpatcher is for a different iPod.
iPodpatcher is for a different iPod.
96
Apple - Installation/Removal / Re: No DFU devices found
« Last post by questions2000 on March 03, 2025, 10:36:41 PM »I was really hoping someone would respond.
I still cannot understand why if the device is in DFU mode that it does not detect during the scan.
If anyone has any ideas, please mention them, I really could use some help.
Thank You
I still cannot understand why if the device is in DFU mode that it does not detect during the scan.
If anyone has any ideas, please mention them, I really could use some help.
Thank You
97
New Ports / Re: Dethonray dtr 1 plus
« Last post by Kostament2 on March 03, 2025, 02:51:57 PM »I’m so stupid 
Press hide and didn’t notice it.
Press hide and didn’t notice it.
98
Theming and Appearance Customization / Re: SNAZZY issue USB
« Last post by user18081971 on March 03, 2025, 08:51:40 AM »Try this should be on line 84 or 86 somewhere there change
#__Clear Screen
%Vi(clearScreen,0,0,0,0,-)
To
#__Clear Screen
%Vi(clearScreen,0,0,1,1,-)
And tell me if that fixes it.
- Misery
Hopping in to say this fixed worked for me as well! Thank you
99
Hardware / Re: AIGO EROS Q Version 2.2 HW4 and restoring my rootfs and bootloader manually
« Last post by disrel on March 02, 2025, 10:37:48 PM »Haha I think this deserves a post of it's own.
So guess who fucked up their rootfs and bootloader while they were messing around (me lol)
From my flash.img, you can carve out the uboot.img, uimage.bin using these commands:
For system.ubi
I put them all in a directory called 'update', salvaged the manifest from Surfans F20 v3.4 Hosted Port and added the bootloader to the manifest. Changed md5 hashes ofc.
and this is how I "unbricked" my OF for EROS Q v2.2. Here is the update file - https://drive.proton.me/urls/7CNTWMQ904#Yb1mlhIROA7i
So guess who fucked up their rootfs and bootloader while they were messing around (me lol)
From my flash.img, you can carve out the uboot.img, uimage.bin using these commands:
Code: [Select]
dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=0 count=353924
dd status=progress conv=notrunc,noerror,sync if=flash.img of=uimage.bin bs=1 skip=3145728 count=2397712
For system.ubi
Code: [Select]
ubireader_extract_files -k flash.img
cd ubifs-root/0
mkfs.ubifs -e "124KiB" -c "1024" -m "2048" -j "8192KiB" -U -v -o "SYSTEM.UBI" -r "rootfs"
I put them all in a directory called 'update', salvaged the manifest from Surfans F20 v3.4 Hosted Port and added the bootloader to the manifest. Changed md5 hashes ofc.
Code: [Select]
mkisofs -volid "CDROM" -o update.upt update
and this is how I "unbricked" my OF for EROS Q v2.2. Here is the update file - https://drive.proton.me/urls/7CNTWMQ904#Yb1mlhIROA7i
100
Hardware / Re: AIGO EROS Q Version 2.2 HW4 and restoring my rootfs and bootloader manually
« Last post by disrel on March 02, 2025, 10:01:03 PM »Hey! I just got one of these.
It seems that the AIGO EROS Q variants have moved on to version 2.2. Not sure what hardware revision it is, but some person on Reddit claims hw4 files work.
https://www.reddit.com/r/rockbox/comments/1i4ceya/comment/md1tinu
EDIT: Confirmed on my end, the hw4 files indeed work for EROS Q v2.2 (jztool method on Windows 11 64-Bit). I backed up the original bootloader, please let me know how I can contribute to update the main rockbox page
Good to hear, if you want to go ahead and try the standard hw4 update file just to make sure, it's here: https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt. It will either work fine or it will reject it because the device name is different. You just need to put it on the SD card with filename "update.upt" and run the recovery mode from the bootloader.
If you also want to dump the entire flash and share that it would good too. I'll stash it away in case it's needed at some point. Lately it seems like we've been getting fewer and fewer stock update files from the manufacturer.Hey! I dumped the flash after I installed the native port. Hope that doesn't ruin things?
I ended up restoring the original bootloader so I get an untampered nanddump. The SHA256 of the flash.img - 8999ea585bc700b64f5b12ab85d204c3fcf415e08f8149057856546df5119fbc
Also I was able to analyze the it using https://github.com/nlitsme/ubidump with block size 0x20000
https://drive.proton.me/urls/03N9J2RR1C#egKE3fHI5iAr
Also to confirm, hw4 upt files for the native port work for EROS Q v2.2! For those who get the new players, hope this helped
Excellent, thank you! I've got it stashed away. I think we can make our own "stock" updater if we really need to for some reason.
What would that consist? If you can give me some pointers I could get started on some things. I was looking at tools/hiby_patcher.pl to see if I could generate a hosted port for mine (for development).
I don't feel confident enough on it to give instructions, but I think it would involve pulling out the various separate parts of the image (bootloader, system, ...others...?) and making them their own files, and then compiling a similar iso image like one of the stock updater files. Fortunately my understanding is that each part of the image has a fixed offset in memory. There's a manifest file that needs to have all the correct names and md5 hashes, etc. I hope that helps? Open up one of the stock update files and you'll see what I mean - You can simply rename it to "update.iso" and open it that way.
I will say though, I've messed with already-compiled update files and made our own bootloader-only update files, but writing to anything other than the bootloader is beyond my wheelhouse so you may wander a bit into uncharted territory, just so you know.
Well I did compare the files and here are my findings. I used Surfans F20 v3.4 (hw4) as my base.
The UBOOT.BIN has changed, I haven't bindiffed it but that's interesting.
The UIMAGE.BIN remains the same.
I am working on SYSTEM.UBI. I just need to figure out the proper offsets so I can carve the "payload" out of my nandflash. I am using tools/hiby_patcher.pl as my base to figure out how the update files work (the hibyos_nativepatcher and agptek_rocker have been helpful as well).
I will report more soon. It's an uphill battle!