This time I want to offer you a double guide. In this video I will show you how to make a quick backup of your partitions using a tool, dumpall.zip, which you can find in different variants, depending on the device on which you are going to use it. In addition, I will show you the difference between a stock Recovery and a custom Recovery, and how to perform the temporary flash without losing the OTA updates. Now my phone is clean and pure. As you can see, using a stock Recovery, if I try to install dumpall.zip or any package, an error will be displayed. This is because the test keys are disabled. The complete guide on Recovery Mode and how to create your own customized version will be found in the “ROOT” section of the BananaHackers website. The guide on how to replace Recovery Mode is divided into two parts. For a temporary use read from the point 1 to the point 5. The sixth point is for a permanent replacement. Now it’s much easier to get root privileges, just use an application like ADBroot or Wallace. With the following command we will create a backup copy of the original Recovery: dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery-backup.img bs=2048 I have already prepared a custom Recovery in my home folder, which I will go to rename in recovery.img (to facilitate the operation simply by making copy / paste of the command)… …and place on my sd card with a command from the normal shell: adb push recovery.img /sdcard The command needed to flash the partition is as follows: dd if=/sdcard/recovery.img of=/dev/block/bootdevice/by-name/recovery Let’s go try it and see how it works. To use this version, remember to mount the system first. An alternative version is available that mounts it automatically, but I want to show you how the original version of Speeduploop works. As you can see the internal script is copying all 32 images of my partitions on the sd card, creating a folder called “dumps” which will contain everything. The two largest partitions are “system” and “userdata”, and additional time will be needed to copy them. You can read the internal scripts of this package to try the same operation directly from the computer, if you prefer. I personally prefer to use this method. Working from a custom recovery is more convenient, as the total time will be much less than that required by the PC. This operation, while I was shooting the video, lasted 6 minutes. I had to cut this video to save you time. In a previous test, stopping the B2G daemon from my PC with the shell took about 40 minutes to complete the same operation. In this case it’s better to play as a guest! More informations in the “BACKUP” section of the BananaHackers website. Dumpall has finished his work. Now let’s go and see the results from my PC. Let’s go see my sd card. The internal script of the system partition on first boot replaced my custom Recovery with the original one, so a backup of it is completely useless in this case. As you can see there are both my recovery-backup.img file (which I created with the first command) and recovery.img, that is my custom Recovery. In addition there is also the “dumps” folder, containing images of my 32 partitions. system.img is around 800 megabytes, while userdata.img is around 2.5 gigabytes. This is the script to disable if you want a permanent custom recovery. The Recovery Replacement Guide continues, in step 6, necessary for its permanent replacement. However, if you only want to use Recovey Mode once to perform an operation like this, just steps 1 to 5 are enough. Let’s check out this rule. Now from Recovery Mode the dumpall.zip package should not work, even if I mount the system. Installation aborted! So my device is currently clean and ready to receive further updates, as always! Now that you’ve seen another perfectly successful test, I invite you to explore the BananaHackers website and consult the BACKUP section for more informations. Thanks for your attention and support! See you next! BananaHackers.net JOIN THE REVOLUTION!