Hi scatwell . Thanks for the link. If it's ok I can add it to my glacier and alike repair guide. About the hack, I did a little bit of research and in my opinion it's not the sellers that hack the firmwares. It seems that the factory does that. Here's why I think that: The firmware is made by a few files which are all put in 1 file. Those files are mainly the music player, the recorder, the radio, etc. Those are all the programs the main kernel executes when you access the menu items. Somewhere between these files, there's the bootloader and a driver (I guess) that holds the flash type. The kernel (the main program) loads this driver and executes it. Now, depending on the chip inside, it will choose the proper driver program for the flash. Here's the tricky part. Whoever produces these players and has the sourcecode for the firmware, forces the kernel to load a higher capacity flash driver and the player reports a higher capacity.
I am still trying to get the firmware out from the clone file, but I am not sure it's possible. I'll report back if i get it to work.
Thanks again for the clone file.
I'm sure you're correct that the factory puts the hack in. It's also quite likely the sellers do not have any links to the firmware fixes/upgrades.
I'm hoping to receive a 550MB file which is an s1clone of the dehacked player. Not sure how I will get it to you if it arrives but maybe it'll zip down smaller.
Thx for your interest. Good luck with trying to extract f/w.
That's nice. I suggest you use 7-zip to pack the file. I compressed a ~200 mb file down to 8 mb with it. What you need is to use the ultra level and put the dictionary to 48 mb or bigger (but you'll need a good computer with lots of RAM memory). Here I couldn't even move the mouse while compressing (only 384 mb of ram).
Btw, good news, I found 2 new glacier firmwares and one of them is 9.1.5.1 . I'll make those available as soon as I can.
__________________
Good player: KiORA K7702 (SPMP3052A)
Dead player: Nexus Nomad A217 2gb, broken screen
EarBuds: Sony TwinTurbo MDR-E755
hi im having problems recovering my mp4 player
because when i try to press the recover firmware button in mp3 update tool it stops and says "Read or write device information failed! Please exit the program and check if device is connecting!" sometimes "Flash Is No Responding" and "Unknown Flash Error" what should i do?
ive tried so many version of mp3 player utilities
That's nice. I suggest you use 7-zip to pack the file. I compressed a ~200 mb file down to 8 mb with it. What you need is to use the ultra level and put the dictionary to 48 mb or bigger (but you'll need a good computer with lots of RAM memory). Here I couldn't even move the mouse while compressing (only 384 mb of ram).
Btw, good news, I found 2 new glacier firmwares and one of them is 9.1.5.1 . I'll make those available as soon as I can.
S1clone will be compressed & uploaded as soon as I get it (if I get it!). In meantime, any chance of the 9.1.51 - is it full version?
RevC means revision c, that is the version of the guide.
Portions of the guide may apply to different players too...For example Issue3 applies to all players. But the firmware in the pack not. That is only meant for Glacier and alike players, so don't use it if you have a different one.
__________________
Good player: KiORA K7702 (SPMP3052A)
Dead player: Nexus Nomad A217 2gb, broken screen
EarBuds: Sony TwinTurbo MDR-E755
. Thanks for the link. If it's ok I can add it to my glacier and alike repair guide. About the hack, I did a little bit of research and in my opinion it's not the sellers that hack the firmwares. It seems that the factory does that. Here's why I think that: The firmware is made by a few files which are all put in 1 file. Those files are mainly the music player, the recorder, the radio, etc. Those are all the programs the main kernel executes when you access the menu items. Somewhere between these files, there's the bootloader and a driver (I guess) that holds the flash type. The kernel (the main program) loads this driver and executes it. Now, depending on the chip inside, it will choose the proper driver program for the flash. Here's the tricky part. Whoever produces these players and has the sourcecode for the firmware, forces the kernel to load a higher capacity flash driver and the player reports a higher capacity. 
