Recent Posts
1
Other - Installation/Removal / Re: Surfans F20 v2.7: Getting started (pardon my initial caution!)
« Last post by Abscissa on Today at 02:19:11 PM »Excellent, thanks!
From what I can tell, my backed up boot image seems, at least to me, to likely just be a different version of the one from the official uboot.bin. More similar than different, and the differences seem to have some interesting patterns.
But at this point, I'm clearly no longer in the realm of "Installing Rockbox" so I should probably move to a different subforum for further discussion. Would this thread be the appropriate place?: https://forums.rockbox.org/index.php/topic,53601.0.html
From what I can tell, my backed up boot image seems, at least to me, to likely just be a different version of the one from the official uboot.bin. More similar than different, and the differences seem to have some interesting patterns.
But at this point, I'm clearly no longer in the realm of "Installing Rockbox" so I should probably move to a different subforum for further discussion. Would this thread be the appropriate place?: https://forums.rockbox.org/index.php/topic,53601.0.html
2
Hardware / Sansa e200 shuts down while playing
« Last post by Braverman on Today at 01:12:21 PM »It's been plguing me for a while, but now - annoying.
Just shut down, but threw out an error:
Data abort at 3007b138
FSR 0x8
(domain 0, fault
pc: 3007b138
sp: 300e76c0
A: 3007b440
A: 3006db10
bt end
Version: f0a05e0993-220804
Also is there a limit to the number of bookmarks contained within the most-recent.bmark file?
Just shut down, but threw out an error:
Data abort at 3007b138
FSR 0x8
(domain 0, fault
pc: 3007b138
sp: 300e76c0
A: 3007b440
A: 3006db10
bt end
Version: f0a05e0993-220804
Also is there a limit to the number of bookmarks contained within the most-recent.bmark file?
3
Feature Ideas / Re: Option to Launch shortcuts instead of WPS context menu
« Last post by chris_s on Today at 10:21:13 AM »Would it help if you could long press „Select“ to go fron the QuickScreen to the Shortcuts Menu? I have a patch for that and have really come to enjoy that behavior on my own devices. Just haven‘t gotten around to putting the finishing touches on it (adding documentation and all of the keymaps), so it can be considered for release.
4
Other - Installation/Removal / Re: Surfans F20 v2.7: Getting started (pardon my initial caution!)
« Last post by amachronic on Today at 03:28:22 AM »[...]USB boot mode is part of the CPU boot ROM, it's baked in hardware and can't break due to a failed firmware update. So you can always recover the bootloader with jztool, or with Ingenic's own flashing tools if you can figure out the parameters or badger the manufacturer into telling you.
Ok, so my questions now, before I go trying out any other images, or native, or anything just yet:
1. Regarding both the device's USB boot mode, and also the device's flash update process: Do we know whether those abilities are stored as part of the bootloader in the internal flash (and could potentially get clobbered by a bootloader update gone wrong, bricking it), or whether they instead live somewhere lower-level that can't get nuked by a bad flash update? (Although, it seems unlikely to me that the flashing process would live on a lower-level than the bootloader since it would require at least the ability to read a fat32 filesystem. Maybe exfat, too. The usb boot mode would seem more likely to be safe from a bad update, but I wouldn't really know for sure.)
Quote
2. Are we able to discuss extracting the bootloader from a .upt file so that I'd be able to double-check the backup I made?The .upt file is just an .iso, rename it and mount or extract it as you wish. Inside you'll find uboot.bin. The bootloader backup is just a straight dump of the first 128k of your flash which corresponds to the first 128k of uboot.bin. Unfortunately verifying your backup isn't totally straightforward because the data in the update image will be different from what's on your flash -- some parts like the flash partition table are deliberately left out of the .upt image, and apparently Ingenic's updater leaves random garbage in some unused parts of the flashed image, which makes hashing the images impossible.
I just diff images with radiff2 -x and check if things look "reasonable," never bothered to write any tool to verify backups. Off the top of my head the only differences should be around 0x200-0x7ff, 0x3c00-0x3fff and maybe the uboot environment block.
5
Other - Installation/Removal / Re: Surfans F20 v2.7: Getting started (pardon my initial caution!)
« Last post by Abscissa on August 07, 2022, 04:56:34 PM »Thanks. I think the main mistake I made was trying to dive into this before actually checking the Surfans website to see how updating the official (non-rockbox) firmware is even done in the first place (my other mistake was trying to do this entirely too late at night!!) After taking care of all that, and getting hold of the device's official firmware update files, things started making more sense to me. (And looking back now, I see my previous post above was...very confused. So nevermind that post now!!)
As I'm understanding things now, the .upt image files are the standard firmware update file format for this particular device (and all the other Aigo ErosQ/K-based ones), and isn't really a rockbox-specific filetype, right?
Ok, so I was able to get jztool working and running the v7 bootloader on my device. I used it to make a backup of my pre-installed bootloader and stored it away elsewhere. I'm not sure how to extract the bootloader from the official (non-rockbox) .upt file (or if that's even something we're able to discuss here) so that I can verify they match (just for my own peace of mind).
I didn't do anything else via jztool just yet. But I did go ahead and try installing the patched v2.5 .upt image from the option in the original firmware. That seems to work exactly as expected - I get a boot menu to choose between rockbox, or the stock player, or a small util suite (which I noticed also lets me invoke the firmware update process, which is nice). The stock player, as expected, now reports v2.5 instead of v2.7 and no longer outputs anything through line-out. It looks like installing the actual rockbox player software is separate from that .upt installation...which all makes sense to me now: If I understand correctly, the .upt images are updates for the device's internal flash memory, which stores both a bootloader and the stock (non-rockbox) player software. That bootloader can be either stock, or one that's been patched with the ability to run rockbox, which is stored on the SD card.
So I went and tossed rockbox onto the SD card (I used Rockbox Utility to do this, just to try it out that way. I unchecked the bootloader option, since I'd already installed it directly.) Aside from the line-out issue of course, rockbox is running fantastically now for me too. And I guess, the way I have it set up right now, rockbox is running hosted, not native, right?
Ok, so my questions now, before I go trying out any other images, or native, or anything just yet:
1. Regarding both the device's USB boot mode, and also the device's flash update process: Do we know whether those abilities are stored as part of the bootloader in the internal flash (and could potentially get clobbered by a bootloader update gone wrong, bricking it), or whether they instead live somewhere lower-level that can't get nuked by a bad flash update? (Although, it seems unlikely to me that the flashing process would live on a lower-level than the bootloader since it would require at least the ability to read a fat32 filesystem. Maybe exfat, too. The usb boot mode would seem more likely to be safe from a bad update, but I wouldn't really know for sure.)
2. Are we able to discuss extracting the bootloader from a .upt file so that I'd be able to double-check the backup I made?
As I'm understanding things now, the .upt image files are the standard firmware update file format for this particular device (and all the other Aigo ErosQ/K-based ones), and isn't really a rockbox-specific filetype, right?
Ok, so I was able to get jztool working and running the v7 bootloader on my device. I used it to make a backup of my pre-installed bootloader and stored it away elsewhere. I'm not sure how to extract the bootloader from the official (non-rockbox) .upt file (or if that's even something we're able to discuss here) so that I can verify they match (just for my own peace of mind).
I didn't do anything else via jztool just yet. But I did go ahead and try installing the patched v2.5 .upt image from the option in the original firmware. That seems to work exactly as expected - I get a boot menu to choose between rockbox, or the stock player, or a small util suite (which I noticed also lets me invoke the firmware update process, which is nice). The stock player, as expected, now reports v2.5 instead of v2.7 and no longer outputs anything through line-out. It looks like installing the actual rockbox player software is separate from that .upt installation...which all makes sense to me now: If I understand correctly, the .upt images are updates for the device's internal flash memory, which stores both a bootloader and the stock (non-rockbox) player software. That bootloader can be either stock, or one that's been patched with the ability to run rockbox, which is stored on the SD card.
So I went and tossed rockbox onto the SD card (I used Rockbox Utility to do this, just to try it out that way. I unchecked the bootloader option, since I'd already installed it directly.) Aside from the line-out issue of course, rockbox is running fantastically now for me too. And I guess, the way I have it set up right now, rockbox is running hosted, not native, right?
Ok, so my questions now, before I go trying out any other images, or native, or anything just yet:
1. Regarding both the device's USB boot mode, and also the device's flash update process: Do we know whether those abilities are stored as part of the bootloader in the internal flash (and could potentially get clobbered by a bootloader update gone wrong, bricking it), or whether they instead live somewhere lower-level that can't get nuked by a bad flash update? (Although, it seems unlikely to me that the flashing process would live on a lower-level than the bootloader since it would require at least the ability to read a fat32 filesystem. Maybe exfat, too. The usb boot mode would seem more likely to be safe from a bad update, but I wouldn't really know for sure.)
2. Are we able to discuss extracting the bootloader from a .upt file so that I'd be able to double-check the backup I made?
6
Hardware / Re: New cheap portable player in the market
« Last post by pmp4 on August 07, 2022, 03:09:18 PM »Not sure if it's useful but some Spreadtrum 6531 related sources can be found here:
Huge find.
It seems almost the same version firmware than player complete source code, with a lot of extra tools.
with the tool /MOCOR_12C.W13.04.23.BTDialer.20_Source/tools/DEBUG_TOOL/ResOver/Bin/ResOver.exe I can view the res.bin file (and it can modify too).
As example I put here the first 4 menu icons, extracted from res.bin using ResOver.exe
7
Other - Installation/Removal / Re: Surfans F20 v2.7: Getting started (pardon my initial caution!)
« Last post by amachronic on August 07, 2022, 10:29:55 AM »Installing the bootloader with a .upt file should work exactly like flashing the original firmware, that will give you the "hosted" port which runs on top of the original firmware's Linux kernel. speachy prepared a patched v2.7 .upt image in this thread but it hasn't been tested yet.
Using the patched v2.5 image is also possible, I think -- but line out will not work in the original firmware or Rockbox. IIRC whoever tried that was able to revert back to vanilla v2.7 afterwards. Line out definitely doesn't work in Rockbox no matter what, unfortunately, the hardware and ALSA controls have apparently both changed since the previous hardware revision.
If you want to use the "native" port you should follow the jztool install instructions on the wiki for installation, but use the v7 bootloader from this thread, not the release bootloaders linked on the wiki page.
Using the patched v2.5 image is also possible, I think -- but line out will not work in the original firmware or Rockbox. IIRC whoever tried that was able to revert back to vanilla v2.7 afterwards. Line out definitely doesn't work in Rockbox no matter what, unfortunately, the hardware and ALSA controls have apparently both changed since the previous hardware revision.
If you want to use the "native" port you should follow the jztool install instructions on the wiki for installation, but use the v7 bootloader from this thread, not the release bootloaders linked on the wiki page.
8
Hardware / Re: New cheap portable player in the market
« Last post by Bilgus on August 07, 2022, 10:27:36 AM »bahus yes that appears to contain the headers
It was quite a large amount of files but I think I have the relevant part contained here
http://www.mediafire.com/file/j4e6xx28fhbrzg2/6531_chip_drv.zip
there appear to be several versions of each with different base addresses so might still need some figuring
It was quite a large amount of files but I think I have the relevant part contained here
http://www.mediafire.com/file/j4e6xx28fhbrzg2/6531_chip_drv.zip
there appear to be several versions of each with different base addresses so might still need some figuring
9
Other - Installation/Removal / Re: Surfans F20 "NAND open error"
« Last post by amachronic on August 07, 2022, 10:06:01 AM »I bought a Surfans F20 Player as well and I want to install the native port on it.
[...]
Is it save to proceed with the installation of the native port with the latest (v7) bootloader from this thread?
[...]
Flash info:
readID opcode = FF C8 D1 C8
readID address = C8 D1 C8 D1
readID dummy = D1 C8 D1 C8
[...]
This shows you have the GigaDevice flash (same as JosephM's) so yes it's safe to install with the v7 bootloader.
Quote
I installed the ROCKbox native port from the v7 bootloader, after a success message I first booted into ROCKbox from the BOOT Menue, this worked.
Then I rebooted and I just got a flickering screen.
So I powered the device off by long pressing power.
A new press on power just gives me the flickering screen again...
So I loaded the v7 bootloader from command promt again...
I reinstalled ROCKbox and powered off after.
I pressed power again and all I got is a flickering screen again.
So I started the bootloader again and created a Flashdump and the info files again.
here are they https://mega.nz/file/jTQS1K6Y#2OMx0mlbN7KqH24NBsz7AEeZqBCtWyXwTirj_9ecDxM
Then I restored the original bootloader. Now the player is working again with its original Firmware (not with ROCKbox sadly). I hope you will have success in getting the thing working with ROCKbox! If you need something else from me I try to provide it to you.
I don't know what the issue is, but if you try a few things it might help narrow things down:
- Go into the bootloader menu (hold volume up when powering on) and boot Rockbox - see if the LCD flickers
- Boot the original firmware from the bootloader menu - check if the LCD works
- Boot the original firmware by holding PLAY when powering on
10
Hardware / Re: New cheap portable player in the market
« Last post by pmp4 on August 07, 2022, 09:14:21 AM »Pmp4 have you verified that you can repackage the extracted bins and write back to the device?
I didnt try to flash anything yet.
I'm trying to understand firmware structure first.
I found this url with "Spreadtrum Research Download Tool" source code (2.9.7007 version)
https://files.elektroda.pl/798976,researchdownload_r2.html
I'm dont know yet if it can be useful.
"Spreadtrum Research Download Tool" uses another format of firmware, in .pac files.
Once I understand it better, I'll try a flash, it would be cool change intro/end logo or menu icons.
If it's possible I'd like to keep using open source free tools like bzpwork and uniflash software.
uniflash allows flash write, and bzpwork allows lzma compress.