Recent Posts
1
Other - Installation/Removal / Re: I am at a stand still with Rockboxing my HIFI Walker, I've tried everything...
« Last post by thebluegoose on Today at 12:06:03 AM »For even further clarification,
When adding the Rockbox and bootloader (renamed to update.upt) onto my microsd, I have been attempting a firmware update but am met with Upgrade Failed, No Upgrade File Found
When adding the Rockbox and bootloader (renamed to update.upt) onto my microsd, I have been attempting a firmware update but am met with Upgrade Failed, No Upgrade File Found
2
Hardware / Re: Is there a way to enable the "Battery" option in settings for the Sansa E200 v1?
« Last post by djrz on July 09, 2025, 11:37:05 PM »I ran the battery benchmark on battery holders for 3 AAA and 3 AA sets of batteries.
3 AAA 800 mAh Eneloops: Ran for ~29 hours.
3 AA 1900 mAh Ladda: Ran for ~64 hours.
Theme: DFKT_Minimum
Earphones: Sony MDREX110AP In-ear Headphones
Tracks: Antics by Interpol played on repeat
Codec: Musepack q7
Volume -40db
If anyone is interested I can link to the battery benchmark text files.
3 AAA 800 mAh Eneloops: Ran for ~29 hours.
3 AA 1900 mAh Ladda: Ran for ~64 hours.
Theme: DFKT_Minimum
Earphones: Sony MDREX110AP In-ear Headphones
Tracks: Antics by Interpol played on repeat
Codec: Musepack q7
Volume -40db
If anyone is interested I can link to the battery benchmark text files.
3
Other - Installation/Removal / Re: I am at a stand still with Rockboxing my HIFI Walker, I've tried everything...
« Last post by thebluegoose on July 09, 2025, 11:21:43 PM »I'll add this for clarification:
I followed the Manual Native Port Wiki, [here](https://www.rockbox.org/wiki/AIGOErosQK)
I determined my Hifi Walker has a V2.0 firmware so I installed this update file, [here](https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt)
Then moved it to my microsd (a Samsung 512gb)
My SD card has been formatted to a FAT32
Both the extracted Rockbox and bootloader (titled: erosqnative-hw4-erosq_2024) are present on the microSD
--
I am getting stuck at Step 2 ("Place the bootloader update.upt file on the SDcard")
Is the bootloader file I added already the same as the "update.upt" mentioned? If so, do I just need to rename it to "update.upt"?
I followed the Manual Native Port Wiki, [here](https://www.rockbox.org/wiki/AIGOErosQK)
I determined my Hifi Walker has a V2.0 firmware so I installed this update file, [here](https://download.rockbox.org/bootloader/aigo/native/erosqnative-hw4-erosq_2024.upt)
Then moved it to my microsd (a Samsung 512gb)
My SD card has been formatted to a FAT32
Both the extracted Rockbox and bootloader (titled: erosqnative-hw4-erosq_2024) are present on the microSD
--
I am getting stuck at Step 2 ("Place the bootloader update.upt file on the SDcard")
Is the bootloader file I added already the same as the "update.upt" mentioned? If so, do I just need to rename it to "update.upt"?
4
Hardware / IPod 7th Gen iFlash: Can't load rockbox.ipod: File not found
« Last post by ktw02 on July 09, 2025, 10:03:09 PM »Hi! New rockbox user here, hope this is the right section of the forum.
I have an iPod 7th Gen (160GB, thin back, I think the 2014 model?) flash modded with an iFlash Solo, "2000mAh" square battery and a brand new 512GB TeamGroup PRO+ microsd card in an adapter. I've been able to get the latest rockbox dev builds and daily builds installed from Linux via the rockbox utility, but every few weeks of use the iPod can't read the database, and then when I try rebooting, it fails to boot and gets stuck in the bootloader with a "Can't load rockbox.ipod: file not found" error.
On the first failure I also had some issues with the SD card getting bumped by the battery and removing itself from the slot, but I glued everything down and the issue keeps happening.
Fight-Fake-Flash says the microsd is legit, so it's not that either.
It doesn't seem to be correlated with low battery, it has happened with both the battery at 90% and at 15%.
When I remove the microsd card from the iPod and put it into my computer, FSCK fixes some corruption with an inode and then the FAT32 partition mounts. All of the files seem intact, except for rockbox.ipod, which is missing. I'm able to copy rockbox.ipod back in, and it loads again in the iPod, and everything's back to normal for another 2-3 weeks.
Any ideas on a fix?
Also, is there any way I can use rockbox with the write protect switch set on my microsd adapter, as a workaround?
I still have the old HDD, it just doesn't fit in the case alongside the oversize battery. I will be testing that this week.
I'd be happy to mail this iPod to a dev for debugging as well. I live in Canada.
I have an iPod 7th Gen (160GB, thin back, I think the 2014 model?) flash modded with an iFlash Solo, "2000mAh" square battery and a brand new 512GB TeamGroup PRO+ microsd card in an adapter. I've been able to get the latest rockbox dev builds and daily builds installed from Linux via the rockbox utility, but every few weeks of use the iPod can't read the database, and then when I try rebooting, it fails to boot and gets stuck in the bootloader with a "Can't load rockbox.ipod: file not found" error.
On the first failure I also had some issues with the SD card getting bumped by the battery and removing itself from the slot, but I glued everything down and the issue keeps happening.
Fight-Fake-Flash says the microsd is legit, so it's not that either.
It doesn't seem to be correlated with low battery, it has happened with both the battery at 90% and at 15%.
When I remove the microsd card from the iPod and put it into my computer, FSCK fixes some corruption with an inode and then the FAT32 partition mounts. All of the files seem intact, except for rockbox.ipod, which is missing. I'm able to copy rockbox.ipod back in, and it loads again in the iPod, and everything's back to normal for another 2-3 weeks.
Any ideas on a fix?
Also, is there any way I can use rockbox with the write protect switch set on my microsd adapter, as a workaround?
I still have the old HDD, it just doesn't fit in the case alongside the oversize battery. I will be testing that this week.
I'd be happy to mail this iPod to a dev for debugging as well. I live in Canada.
5
Other - Installation/Removal / I am at a stand still with Rockboxing my HIFI Walker, I've tried everything...
« Last post by thebluegoose on July 09, 2025, 06:43:30 PM »Recently purchased a new HIFI WALKER H2 V2.
I attempted to follow the wiki to rockbox my device after deciding on a theme. I'm not the most tech savvy, but I get by alright most of the time. But attempting to Rockbox the device proved to be to much for me.
I called a local tech support place, explained my problem at they were happy to try to help. Today, I sat with the owner for 2 HOURS trying to follow the EROS Q wiki steps and going through the PDF manual. We even tried looking through the forums here and on r/rockbox for guidance. I relented saying that I would go to the community for support as its my only option now.
It seems that some files on the EROS Q wiki may be the incorrect links. We were not given the correct update.upt file when clicking the link in EROS Q wiki under Native Port. Additionally myself and the tech support guy found the wiki confusing using similar terms meaning multiple things.
I'm at my wits end here... Is there anyway someone can provide me more clear feedback on how to properly rockbox my device? Hell, even if there was a kind soul who would be down to hop on a video call/chat room and provide my direct support, I would be SOO grateful.
TL;DR : I've tried about everything to Rockbox my HIFI WALKER. Even going to a local tech support company. Wiki was confusing us both. Can someone please help?
:'(
I attempted to follow the wiki to rockbox my device after deciding on a theme. I'm not the most tech savvy, but I get by alright most of the time. But attempting to Rockbox the device proved to be to much for me.
I called a local tech support place, explained my problem at they were happy to try to help. Today, I sat with the owner for 2 HOURS trying to follow the EROS Q wiki steps and going through the PDF manual. We even tried looking through the forums here and on r/rockbox for guidance. I relented saying that I would go to the community for support as its my only option now.
It seems that some files on the EROS Q wiki may be the incorrect links. We were not given the correct update.upt file when clicking the link in EROS Q wiki under Native Port. Additionally myself and the tech support guy found the wiki confusing using similar terms meaning multiple things.
I'm at my wits end here... Is there anyway someone can provide me more clear feedback on how to properly rockbox my device? Hell, even if there was a kind soul who would be down to hop on a video call/chat room and provide my direct support, I would be SOO grateful.
TL;DR : I've tried about everything to Rockbox my HIFI WALKER. Even going to a local tech support company. Wiki was confusing us both. Can someone please help?
:'(
6
Hardware / Re: AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2
« Last post by dconrad on July 08, 2025, 09:29:17 AM »Right, a fair bit of progress...
I have successfully installed Rockbox on the H2! This included saving the original bootloader .bin file somewhere safe. I must say it was a relief to see the familiar Rockbox menu!
And I can report that with the output mode set to 'Line out', I do indeed get output from that jack, and can play on the Car's Aux input!
Somewhat strangely, I am not not sure if the Headphone output works correctly. 'Auto' switching doesn't seem to work for the Line out socket, at least, I will experiment a bit further.
I was mis-understanding one thing ... on the Xduoo X3ii port, the Rockbox bootloader allows booting into either the original (HiBy) firmware, or Rockbox firmware. That doesn't seem to be the case for this H2 bootloader, is that correct?
And I have realised that nothing has happened to the original H2 v2.0 firmware, I presume it is still living in Flash on the H2. So if I were to want to revert, I just have to use the recovery menu and re-flash the original bootloader image I saved (renamed...), and the H2 will boot into stock v2.0 firmware. Correct?
Thanks a lot for all of this - at the very least it has answered my original question - it is some sort of issue with the stock v2.0 firmware not switching correctly - and it has got me up to speed with Rockbox installation on the H2.
Thanks a lot for your help with this.
Regards, jon N
Good deal! You can boot into the stock firmware by holding Play while booting, or the bootloader menu by holding Volume Up while booting.
7
Hardware / Re: Sansa Fuze+ completely unresponsive after attempting to sync RB 4.0
« Last post by Kai1992 on July 08, 2025, 08:23:11 AM »I appreciate your response. I do believe I have held the power button in excess of 30 seconds with no response since this happened. Not sure if that is going to do it. I cannot get it to respond to a thing.
I will see what happens if I let the battery completely discharge then plug it into a computer. Really hoping I can get this thing running again.
I will see what happens if I let the battery completely discharge then plug it into a computer. Really hoping I can get this thing running again.
8
Hardware / Re: AIGO EROS Q / AIGO EROS K / IRULU Surfans F20 / AGPTek H3 / HIFI WALKER H2
« Last post by jkn on July 08, 2025, 06:07:29 AM »(back after being away for a couple of days)
Thanks, that worked fine!
Thanks, that worked fine!
9
Hardware / Re: Sansa Fuze+ completely unresponsive after attempting to sync RB 4.0
« Last post by cela on July 08, 2025, 03:03:49 AM »I have a Fuze+ , haven't used it for a while, but if I remember rightly if you press and hold in the top power button for about 30 seconds, it does a hard reset.
10
Hardware / Re: Sansa Fuze+ completely unresponsive after attempting to sync RB 4.0
« Last post by Kai1992 on July 08, 2025, 12:21:39 AM »Firstly thank you for responding. I am going to t try just as you say and hope for the best. Now I do have one question. As I was perusing the forum I came across someone in a similar predicament with a Fuze+ who after leaving the unit plugged into power for several days came back to a working device.
After 3 days of discharging and plugging into a computer I get no response should I try the leaving plugged in route? I am not quite sure why that worked for the other user.
After 3 days of discharging and plugging into a computer I get no response should I try the leaving plugged in route? I am not quite sure why that worked for the other user.