I'm trying again to raise your interest here.



We released an awesome new dualboot firmware v2.51 some days ago. Don't hesitate to try it and give your feedback. The R0 will never die   :big:

http://www.anythingbutipod.com/forum/showpost.php?p=620734&postcount=887

Hello guys!

No one interested in rockbox?  :cry:

The FM radio is now included in the official builds.
Installation instructions: http://anythingbutipod.com/forum/showpost.php?p=509846&postcount=1
Feel free to translate into Spanish if you want  ;-)

Just to let you know guys, the R0 is now officially included into the Rockbox Build System and thus shows up here: http://build.rockbox.org/

Instructions to install the latest Rockbox version are in the 1st post of this thread http://www.anythingbutipod.com/forum/showthread.php?t=58642

Enjoy  :big:

I hope you enjoy this surprise guys. It's already Christmas  :mrgreen:

If you notice some unkwown issues please report them to Lorenzo or me.

Oh and don't forget my Rockbox theme hehe:
http://www.anythingbutipod.com/forum/showthread.php?t=66487

Lorenzo and me are pleased to announce that the 1st modded firmware for the YP-R1 is now released. We hope you'll enjoy it as it took us long time to develop it and write the long readme below. Moreover Lorenzo worked on that project whereas he doesn't even own a R1 so you can really thank him.


Alternative Download Link

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

Latest Version: v4.00
Based on firmware: v3.07
NOTE: this firmware is as stable as the official firmware 3.07.


#### Changelog ####

** Version: 4.00 - 12/09/2011 **

- Safe Mode (the R1 can be connected to the computer in any situation, even when the device is bricked - also gives access to the hidden memory)
- CPU downclocking tool (downclock the CPU frequency from 532 MHz to 200 MHz to improve a bit battery life)
- DRK (Device Rescue Kit - Easily unbrick a R1)
- Sysdata customization possible (the user can customize the interface pictures, language files, sounds and fonts himself!)
- Translation improved in French language (NOTE: please give us an hand with translations in other languages!!)


#### How to install firmware 4.00 ? ####

Like for any official firmware, just put the R1.ROM file at the root of the R1. At next startup it will automatically update the firmware.


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

This framework works on the R1's internal memory. It allows a normal user to unbrick a bricked R1 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 4.00 archive file you downloaded, there is a DRK folder. Just copy & paste it at the root (main directory) of the R1.
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 R1.
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.
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-32 GB storage). Use it as last resort solution!! As you run this feature from the internal memory, the R1 may get stuck on the boot screen. In this case wait a little (1 min 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 R1'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 R1, please turn off the device and reset it.
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

NOTE: a file called DRK_debug.txt is created at the root everytime you use DRK tool.
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 R1 is bricked and not normally recognized by the computer anymore. Indeed, the Safe Mode starts even before the R1 application is loaded! That way you can easily unbrick the device (see "How to unbrick a R1?" below).
Moreover it gives you access to the hidden memory of the R1 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 R1 is fully off (press reset). Then connect it to the computer. As soon as you see the Samsung boot screen, press and hold the "volume up" key until you see the Safe Mode screen on the R1.
Now in "My Computer" or in your drives manager you should see 2 volumes: the usual R1 internal memory 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 R1 ? ####

If your R1 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 R1 has to be in firmware 4.00. If it is in the official firmware (from 1.xx to 3.xx) you cannot unbrick the device yourself, you have to send it back to the Samsung after-sales service center.

There are 2 different ways to unbrick the device:

1) Using the DRK
You have to connect your R1 to the computer in Safe Mode (read the Safe Mode instructions above). Then run the DRK's Clean_database feature 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 R1 still doesn't boot, use the Delete_settings feature and as last resort solution the Nand_Killer feature.

2) 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 R1 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 R1 still doesn't boot, format the memory.


#### CPU Downclocking tool ####

By default the R1 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 much 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 R1 is fully off (press reset), then turn it on and as soon as you see the Samsung boot screen, press and hold the "volume down" key 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 "volume down" 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 4.00 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 R1 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 "power_on.wav" and "power_off.wav".
If you want the startup and shutdown sounds to be removed, you can replace the default files by the empty files in the "No Startup & Shutdown Sounds Mod" folder of the Firmware 4.00 archive.
Actually you are obliged to replace the files, you cannot just delete them. If there is no file in the Auidata folder, the R1 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 4.00 and the provided Sysdata folder already contains improved translation in French language.
But if you are not satisfied with this translation or want to improve the translation in another language, you can edit the TXT files in the "UniArray" folder.
Don't remove strings and make sure there is not twice the same string in your new translation otherwise the R1 won't read the TXT file properly.
The best way to edit the file is to check on the R1 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 R1 is useless as many strings don't concern the R1 (it's the same file for R0, R1, M1 and other players)

3. Fonts
You cannot add a 4th font but you can replace the 3 default ones (Candy, Gothic & Jumok). They are in the "Font" folder.
For the replacement, most TrueType fonts should work properly.
For example if you want to replace the Candy font by let's say Arial, just delete AV_candy_kr_v.ttf, put arial.ttf in the folder and rename this file to AV_candy_kr_v.ttf.
The only thing you must bear in mind is that there always has to be 4 files named "AV_Big_gothic_kr.ttf", "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 JPG, BMP, GIF or PNG format. Thus, 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 QWG format. Unfortunately this is a proprietary format and there is no editor available as of today.



#### Credits ####

__ Lead developer, System Mods __

<Lorenzo92 aka MemoryN70 - memoryS60 at gmail dot com>

__ Community Manager, beta tester, (ugly) Safe Mode screen and French Language __

<lebellium>


...Finally thanks to abi forum too!!

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!!

We are pleased to announce that the 2nd modded firmware for the YP-R0 is now released. The main feature is the Device Rescue Kit which may save your life, or at least your R0 sooner or later (see below for more information). At first we had planned to include the CPU downloading tool too but evaluating the efficiency (=benchmarking the difference of battery life) takes quite much time and Lorenzo spent much time on the well progressing Rockbox port these days. This is why we decided to include it in next version instead.


Alternative Download Link 1
Alternative Download Link 2

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.10
Based on firmware: v1.25
NOTE: this firmware is as stable as the official firmware 1.25.
This new release includes the DRK - Device Rescue Kit - that allows a normal user to restore a bricked device with a normal microSD card! Forget Samsung repair centers...


#### Changelog ####

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

- BIG: DRK
- Some minor fixes in Italian and French language (NOTE: please give us an hand with translations in other 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...

- include the cpu downclocking tool (from 532 mHz to 200 mHz-> doubles battery life!)
- 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...

#### F.A.Q. ####

1. Oh shit! My player won't boot anymore ... maybe it's bricked! What to do?
- Well I hope you installed (at least) the version 2.10 of the modded firmware. So that you can use a microSD card to use rescue tools. If your firmware version is not 2.10 or more recent, well go to the first Samsung repair center. After that, install promptly my modded firmware!!!
  Now follow DRK instructions ;=)
  Please try these options in order: Backup_settings, Clean_database, Delete_settings and finally Nand_Killer. Nand_killer is not necessary if device is already unbricked deleting database or settings.

2. Hey! Your DRK didn't work...
  - Strange! After formatting everything I'm sure your device is clean. Maybe you did something wrong. Just retry.
  If you still face the issue, just send me an email or write a post on the ABI forum for more help!!

3. I have no microSD card!
  - Just buy one if you don't want to give money to Samsung. No other way to unbrick the device is available now.

4. This FAQ is soo short...
  - Just contact Lorenzo92 or lebellium for more info...

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

This framework works 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 archive file you downloaded, there is a DRK folder. Just copy & paste it at the root (main directory) 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 if you are knowledgeable enough.
Create a folder called "DRK" in the root (main) directory of the 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 potentially delete the extension 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 on microSD card.
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!!

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, please turn off the R0 and reset it (keep the power button pressed for at least 5 seconds) or press reset hole.
Turning device on WITH the microSD card inserted starts the selected process(es). Some of them need reboot so the device will automatically shut down. Simply restart it to see the result

NOTE: 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)

#### Credits ####

__ Lead developer, Italian Language, System Mods __

<Lorenzo92 aka MemoryN70 - memoryS60 at gmail dot com>

__ Community Manager, beta tester and French Language __

[Many thanks] <lebellium> [/Many thanks]

__ Spanish Language __

<fray_luis> and <Klakring>

__ Russian Language __

<Night_demon> and <5TORM>

...Finally thanks to abi forum too!!


#### Disclaimer ####


THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

CPU downclocking should be user-selectable (default 532Mhz or 400 or 200) through a small script file added to the NAND.
The next firmware should be released in the coming days but I can't tell you exactly when because the developer is also working on the Rockbox port and the modded fw has to be fully tested before the release.

edit:
BTW: is the new spanish translation of the UI OK or is there something to change in next mod?

I spoke with the developer. It's impossible the battery life is worse in fw 2.00 than in fw 1.25. The modifications we made cannot change battery life  ;-)
But in next modded firmware, battery life will be better than any previous official firmware thanks to the CPU downclocking mode (532Mhz > 400 or 200Mhz)  :gafas:

We are pleased to announce you that the 1st modded firmware for the YP-R0 is now released.
It has been a long work so we hope you will enjoy it!


Alternative Download Link 1
Alternative Download Link 2

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).

Read-me file by Lorenz092:

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

Latest Version: v2.00
Based on firmware: v1.25
NOTE: this firmware is as stable as the original one. Don't expect some great improvements ;)
Remember this is a first release...


#### Changelog ####

** 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...

- include the cpu downclocking tool (from 532 mHz to 200 mHz-> doubles battery life!)
- the player is kept in "Sleep mode" for more than 8 hrs: lower this to 1 hr
- when headphone is detached, it stops player. 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...


#### Credits ####

__ Lead developer, Italian Language, System Mods __

<Lorenzo92 aka MemoryN70>

__ Community Manager, beta tester and French Language __

<lebellium>

__ Spanish Language __

<fray_luis> and <Klakring>

__ Russian Language __

<Night_demon> and <5TORM>

...Finally thanks to abi forum too!!


#### Disclaimer ####


THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.



Pictures

-New battery status bar:



-Spanish language

Or I just use Google translation and hope its translation will make sense this time and will not suck as usual  :silbar:

The NAND is integrated (soldered) to the PCB (It's K9HCG08UID on my picture).

Okay thanks ;)

Normally we will release firmware 2.00 in the following days  :banana:

Thanks
And what's the difference between
"apagar pantalla en: xx min" and "Pantalla apagada: xx min" ?

Because if "Pantalla apagada: xx min" makes sense, that's great, that perfectly fits the screen  :mrgreen:

Yeah indeed, "Display Off Time: 1min" means the display stays on during 1 min then turns off
"Tiempo de apagado de pantalla" is the most accurate way to say it but I guess it's too long and the horizontal scrolling is very slow on the R0. It would be better to find a translation where you immediately see "15 s, 1 min, 3 min, always on" without scrolling.

In French I replaced it by "Ecran éteint: xx min" (display off: xx min). It's less accurate than "Délai de désactivation de l'écran" ("Tiempo de apagado de pantalla") but at least there is no boring scrolling anymore