Samsung YP-R0 Hacked Firmware

Iniciado por lebellium, 21 de Julio de 2011, 09:34:11 AM

Tema anterior - Siguiente tema

0 Usuarios y 1 Visitante están viendo este tema.

klakring

Cita de: tronideco en 25 de Agosto de 2011, 05:42:27 PM
Cita de: ampherio en 26 de Julio de 2011, 06:03:24 AM
Aprovecho el hilo para deciros que si alguno quereis ponerlo en uso en redcoon este modelo (creo que es este YP-R0 o YP-RO como dice redcoon) esta muy economico:

http://www.redcoon.es/index.php/cmd/shop/a/ProductDetail/pid/B304377/cid/18017/Samsung_YP_ROJ_AB_EDC/

Yo creo que son productos ya abiertos ya que yo me compre un samsung YP-U6 bastante barato tambien y la caja estaba un poco rota por dentro por lo que tuvo que ser abierto anteriormente ya que de fabrica no se rompe la caja, aunque tengo que decir a su favor que parece nuevo y no he tenido ningún problema. (es mi opinión tal vez me toco a mi y no no pasa siempre)

Hola, acabo de comprar el reproductor a redcon. Ya tenía uno, pero por ese precio me pareció muy interesante y así tengo uno de repuesto. Sólo 25€ más gastos de envío. El primero con las mismas características me costó 69€ hace 10 meses.
Viene perfectamente precintado, la caja y el producto sin abrir y en perfecto estado. Así que me parece que he hecho una buena compra.
Comento esto porque decíais que la caja de otro producto que comprasteis en redcon venía abierta. No ha sido mi caso.
Saludos.

Enhorabuena porque a ese precio es una compra fantástica y como mp4 es una chulada! :gafas:

Y, aunque ahora mismo el YP-R0 lo tiene un amigo que le ha gustado mucho (junto a los M1 :jejeje:) y que seguramente me lo cambie por una EOS gracias otra vez a lebellium por sus actualizaciones de firmware :beer:

Saludos
Repros: Sansa Clip+ RB / Fuze v2 LOD RB, Samsung R0
IEMs: Brainwavz M2, F.A. Eterna Rev.1, Audéo PFE 112
Amps: FiiO E5, SoundMagic A10
Otros: FiiO S5K / N3

tronideco

Saludos de nuevo. Parece ser que hay algunos problemillas con el nuevo firmware 2.10. A algunos que lo hemos instalado en el r0, nos aparece de vez en cuando un mensaje que dice "system checking".
No aparece siempre pero si con frecuencia cuando se arranca el reproductor después de haberlo apagado totalmente.
Este problema lo han tenido otros usuarios que han escrito en el foro donde escribe lebellium.
El creador del firmware está de vacaciones por lo que hasta que no vuelva dentro de unos días no sabremos nada.
Saludos

lebellium


Lorenzo and me are pleased to announce that the 3rd modded firmware for the YP-R0 is now released. We hope you'll enjoy it as it took us very long time to develop it and write the long readme below :)


Alternative Download Link

It works like a normal firmware. Just put the R0.ROM file at the root of your R0 and the device will upgrade the firmware when your reboot it. If you're not satisfied with it, you can downgrade to the official firmware 1.25 without any problem (tested).

###############################################################
                    YP-R0 firmware mod
- just some fixes and improvements for our beloved player -
##############################################################

Latest Version: v2.20
Based on firmware: v1.25
NOTE: this firmware is as stable as the official firmware 1.25.
You can now unbrick the device without a microSD card, enjoy better battery life and customize the resources files!

#### Changelog ####

** Version: 2.20 - 09/09/2011 **

- Safe Mode (the R0 can be connected to the computer in any situation, even when the device is bricked - also gives access to the hidden memory)
- Experimental: CPU downclocking tool (downclock the CPU frequency from 532 MHz to 200 MHz to improve a bit the battery life)
- DRK improvements (better database cleaning, now also works on the internal memory without a microSD card)
- Sysdata customization possible (default battery indicator and system sounds are back, colored battery indicator and removed startup & shutdown sounds from fw 2.10 now provided as optional mods, the user can customize the interface pictures, language files, sounds and fonts himself!)
- Some minor fixes in Italian and Russian languages (NOTE: please give us an hand with translations in other languages!!)



** Version: 2.10 - 08/08/2011 **

- BIG: DRK (Device Rescue Kit)
- Some minor fixes in Italian and French languages


** Version: 2.00 - 27/07/2011 **

- Improved and corrected some languages (Italian, French, Spanish, Russian)
- Battery status (bars) colored (Green, Yellow and Red)
- Reset by holding power key time lowered from 10 secs to 5 secs (easier and safer to turn off completely the device)
- Removed startup and shutdown sounds


#### TODO ####
Maybe in future versions...

- the player remains in "Sleep mode" for more than 8 hrs: lower this to 1 hr
- when headphone is unplugged, music playback is stopped. Could be annoying
- try to tune some register in the as3543 codec to improve quality or power save
- try to symlink microSD to internal memory to include its content songs in the database too!

- more and more to come...



#### How to upgrade from firmware 2.10 to 2.20 without losing your personal settings and FM presets ? ####

Your R0 has to be in firmware 2.10 (if you upgrade from stock firmware 1.xx you'll lose the settings) and you need a microSD card.
Go to the firmware 2.20 archive and copy & paste the "DRK" folder to the microSD root directory. Then enter the DRK folder and remove "_DONE" from the "Backup_settings" file name.
Fully turn off the R0 (press reset or press and hold the "power" key for 5 seconds). Insert the microSD card. Turn on the R0, it may automatically shut down. Now you can see a new SETTINGS folder has been created on your microSD card.
Install firmware 2.20 (just put the R0.ROM file at the root as usual). In the DRK folder on microSD card, remove "_DONE" from the "Restore_settings" file name. Once again, fully turn off the R0, insert the microSD card. Then turn on the device and now you can see you still have your settings and FM presets! :)



#### DRK aka Device Rescue Kit ####

This framework works either on the R0's internal memory or with a normal microSD card (WARNING: it must be formatted as fat/fat32 to work). It allows a normal user to unbrick a bricked R0 or simply save his settings before a firmware update and restoring them after.
1. Using pre-made files
That's the best and easiest way to use the DRK for most users. In the firmware 2.20 archive file you downloaded, there is a DRK folder. Just copy & paste it at the root (main directory) of the internal memory or of the microSD card.
Inside this DRK folder you can see 5 files. These files are already provided WITH "_DONE" extension. This keeps them from executing automatically, it's like the OFF position. When you want to use a feature, just delete _DONE from the file name to turn it ON. After the selected feature ran on device, the file is automatically renamed with the _DONE extension.

2. Creating one's own files
This way is only recommended for advanced users.
Create a folder called "DRK" in the root (main) directory of the internal memory or of the microSD card.
Into this folder create an empty file (using Notepad for example) and name it according to the feature you want to enable (see the 5 possibilities below)
NOTE: case sensitive!!
NOTE: please remember NOT to add any extension to file name. By default Windows hides file extensions. Please enable them to be able to delete the potential extension coming when you create the file.
When the feature ran on device the file is automatically renamed with a "_DONE" extension to keep it from executing automatically. Just delete this extension to execute the feature again.


Backup_settings -> saves the current settings to an automatically-created SETTINGS folder at the root of the internal or external memory.
Restore_settings -> restores the settings contained in the SETTINGS folder (you can restore only RadioApp.ini too, for example. In this case you just have to remove the other settings files)
Delete_settings -> removes the settings from the player
Clean_database -> deletes the library database from the player (WARN: That way it may have some problems to boot. Just retry booting it for a few times ;))
Nand_Killer -> WARN: this erases nand content (format). Removes eveything from the user memory (4-8-16 GB storage). Use it as last resort solution!! If you run this feature from the internal memory, the R0 may get stuck on the boot screen. In this case wait a little (1min for instance) then press reset and start the device.
The Nand_Killer feature formats the device using the 8192 bytes allocation unit size instead of the default 4096 bytes. This may cause slower transfer rates. That is why, after using this feature you should reformat the device from the R0's settings or from your computer.
Please DO NOT use/try NTFS or other filesystems than FAT32: they aren't supported by the kernel, thus bricking the device again.

Using several features at the same time is allowed. Just don't use strange mix like backup_settings and restore_settings ;)
After a process has run, please note that the file is renamed to _DONE. This prevents a second call to the same function ("dangerous" hehe). To reuse it, simply delete the _DONE extension.

After putting the DRK folder and the desired feature file(s) inside on the internal or external memory, please turn off the R0 and reset it (keep the power button pressed for at least 5 seconds) or press reset hole.
Turning on the device starts the selected process(es). Some of them need reboot so the device will automatically shut down. Simply restart it to see the result :)

IMPORTANT NOTE: At startup the R0 checks if there is a microSD card inserted and if there is a DRK folder on it. If yes, it runs the selected features (those without _DONE extension) from microSD. If no, it checks if there is a DRK folder on the internal memory and then run the selected features from there.

NOTE 2: a file called DRK_debug.txt is created on microSD everytime you use DRK tool or you just insert the SD while booting.
It is not directly necessary, but it can contain useful informations to analyze problems (I hope none for the moment)


#### Safe Mode ####

The Safe Mode allows a normal USB connection to the computer in any situation, even when the R0 is bricked and not normally recognized by the computer anymore. Indeed, the Safe Mode starts before the R0 application is loaded! That way you can easily unbrick the device (see "How to unbrick a R0?" below).
Moreover it gives you access to the hidden memory of the R0 containing the settings and some data. That's useful for the Sysdata customization (see "Sysdata customization" below).
How to enter the Safe Mode? Make sure the R0 is fully off (press reset or keep the "power" button pressed for 5 seconds). Then connect it to the computer. As soon as you see the Samsung boot screen, press and hold the "back" button until you see the Safe Mode screen on the R0 (backlight is very low, that's normal, that way battery charging is a bit faster).
Now in "My Computer" or in your drives manager you should see 3 volumes: the usual R0 internal memory, the microSD volume if a card is inserted AND the "NEO-GHOST" (sometimes also called "Samsung microSD") volume (hidden memory).
As written on the Safe Mode screen, "after editing system files, unmount the volumes (=safely remove the device) before disconnecting the USB cable!"
Once you disconnected the USB cable, press reset to turn off the device.

NOTE: in this mode, the battery is charging as usual. There isn't just any indicator.


#### How to unbrick a R0 ? ####

If your R0 is stuck on the boot screen at startup and is not recognized by the computer anymore, don't worry. With this modded firmware you can unbrick it!
Of course your R0 has to be in firmware 2.20 (or at worst 2.10). If it is in firmware 1.xx or 2.00 you cannot unbrick the device yourself, you have to send it back to the Samsung after-sales service center.

There are 3 different ways to unbrick the device:

1) Using the DRK from a microSD card:
Just run the DRK's Clean_database feature from a microSD card following the DRK instructions above. It will rebuild the database at next startup. In most cases that should be enough to unbrick the player.
However, if the R0 still doesn't boot, use the Delete_settings feature and as last resort solution the Nand_Killer feature.

2) Using the DRK on the internal memory
With this new firmware 2.20 a microSD card is not necessary anymore to run the DRK, you can use it directly on the NAND internal memory.
For that, you have to connect your R0 to the computer in Safe Mode (read the Safe Mode instructions above). Then run the DRK's Clean_database feature from the normal internal memory following the DRK instructions above. It will rebuild the database at next startup. In most cases that should be enough to unbrick the player.
However, if the R0 still doesn't boot, use the Delete_settings feature and as last resort solution the Nand_Killer feature.

3) Deleting manually the problematic files - for advanced users only -
If you don't want to use the DRK, you can delete the problematic files yourself.
For that you have to connect your R0 to the computer in Safe mode (read the Safe Mode instructions above). Then go to the hidden memory ("NEO-GHOST") and delete the "Db" folder and the "EntryList.ent" file at root.
At next startup it will rebuild the database. In most cases that should be enough to unbrick the player. However, if the R0 still doesn't boot, format the memory.


#### CPU Downclocking tool ####

By default the R0 CPU (=processor) frequency is set at 532 MHz. It is possible to downclock it to 200 MHz to improve a bit battery life. By how much depends on what you do with the player.
With continuous music playback and display off the battery life is not really better but for a mixed-use (if you use several features, navigate on the player with display on etc...) you should notice an improvement.
However at 200 MHz the User Interface is a bit slower and laggy and the DNSe effects are not usable anymore (jerky sound playback when display is OFF).
To activate the downclocking tool make sure the R0 is fully off (press reset or keep the "power" button pressed for 5 seconds), then turn it on and as soon as you see the Samsung boot screen, press and hold the "user" button (...) until you see the home menu.
To disactivate the dowclocking tool and then come back to 532 MHz, just repeat the previous operation (press the user button at startup) or delete the "cpu_downclock.on" file from the "NEO-GHOST" memory (see the Safe Mode instructions above)

NOTE: This is still experimental. Please give us your feedback about the battery life improvement you measured.


#### Sysdata customization ####

The Sysdata folder (into the Mods folder) provided in the firmware 2.20 archive is fully customizable. Below are the main things you can change and customize.
But first you have to put this Sysdata folder at the root of the "NEO-GHOST" memory (see the Safe Mode instuctions above). The R0 first checks if a Sysdata folder is present in the "NEO-GHOST" memory. If yes, it will load this one. If no, it will load the default hidden Sysdata folder.
Thus if you want to cancel all your modifications, you just have to delete your Sysdata folder from the "NEO-GHOST" memory.

1. Startup and Shutdown sounds
You can replace the default startup and shutdown sounds in the "Auidata" folder. They have to be in WAV format and the file names have to be "PowerOn.wav" and "PowerOff.wav".
If you want the startup and shutdown sounds to be removed like in firmware 2.10, you can replace the default files by the empty files in the "No Startup & Shutdown Sounds Mod" folder of the Firmware 2.20 archive.
Actually you are obliged to replace the files, you cannot just delete them. If there is no file in the Auidata folder, the R0 will make a terrible noise at startup.
NOTE: The default files properties are WAV PCM 16 bit 352 kbps 11 KHz. Other audio properties may work but not guaranteed

2. Language files
Firmware 2.20 and the provided sysdata folder already contain improved translations in Italian, French, Spanish and Russian language.
But if you are not satisfied with these translations or want to improve the translation in another language, you can edit the TXT files in the "UniArray" folder.
Don't remove strings, don't change the encoding format (UTF-16LE) and make sure there is not twice the same string in your new translation otherwise the R0 won't read the TXT file properly.
The best way to edit the file is to check on the R0 what word or sentence you want to improve and then to look for the related string in the TXT file.
Translate every string of the TXT file without checking on the R0 is useless as many strings don't concern the R0 (it's the same file for R0, R1, M1 and other players)

3. Fonts
You cannot add a 4th font but you can reverse or replace the 3 default ones. They are in the "Font" folder.
How to change the default font in all languages except English and Korean? As you probably noticed, you can only change the font in Korean or English language.
For the other languages the only font available is Gothic (AV_gothic_kr_v.ttf). If you prefer the Candy or Jumok fonts, you can rename one of those to AV_gothic_kr_v.ttf and then rename the Gothic font to Candy or Jumok.
But you can also put a new font, most TrueType fonts should work properly.
For example if you want to replace the Gothic font by let's say Arial, just delete AV_gothic_kr_v.ttf, put arial.ttf in the folder and rename this file to AV_gothic_kr_v.ttf.
The only thing you must bear in mind is that there always has to be 3 files named "AV_candy_kr_v.ttf", "AV_gothic_kr_v.ttf" and "AV_jumok_kr_v.ttf" in the "Font" folder.

4. Interface Customization
If you are motivated enough you can even customize the interface. Indeed, the "Image" folder contains the different pictures the interface is made of.
Some of them are in BMP format. It's easy to edit or replace them, you just have to use the same resolution and format.
But as you can see, many others are in QMG (Qmage) format. Unfortunately it is a proprietary format (http://quramsoft.com/solution_e/qmage.asp) that Samsung also uses for some mobile phones and as of today it still doesn't exist any editor for this format.
However, there is a trick, using the Samsung Theme Designer software. Indeed you can create a new theme, import the picture you want and then export the theme. It will automatically convert your PNG/BMP/JPG/GIF picture to a QMG picture.
But first you have to know the picture resolution. As QMG is not recognized as a picture format by any OS or software, you cannot know that information just like that. Read the "QMG files resolutions.txt" file into the Mods folder to see the list of QMG files and resolutions.
Then in Samsung Theme Designer you have to find a mobile phone featuring the same display and images resolutions.
For example, if you want to change the "01_list_black_back.qmg" file (Sysdata>Image>01_Introduction) which is the background for the Polaris theme, you have to find a phone with a 240*320 screen in the Samsung Theme Designer.
In this case, Select the GT-S3850 model, select the Idle_Background.png picture and replace it by the 240*320 picture you want. Click on "Export Theme". In the project folder there is now a *.smt archive.
Extract it with Winzip, Winrar or 7-Zip. Now just copy & paste the "Idle_Background.qmg" file to the 01_Introduction folder, delete "01_list_black_back.qmg" and rename "Idle_Background.qmg" to "01_list_black_back.qmg"!
As you can see, it's not easy to do but it works!



#### Credits ####

__ Lead developer, Italian Language, System Mods __

<Lorenzo92 aka MemoryN70 - memoryS60 at gmail dot com>

__ Community Manager, Beta tester, (ugly) Safe Mode Screen and French Language __

<lebellium>

__ Spanish Language __

<fray_luis> and <Klakring>

__ Russian Language __

<Night_demon> and <5TORM>

...Finally thanks to abi forum too!!