Database Users

[Tutorial] Root for LEAKERS 7/4/10

MAJOR Update 7/13/2010 15:48 PDT
Go to http://forum.xda-developers.com/showthread.php?t=724741 for the newer, confirmed root method
The following method is now outdated
Added optional instructions to flash Amon_RA's recovery image
Removed unnecessary steps (old step 6 and 7) because downloading the SDK folder in Step 2 already contains those files
Added .wav file of Tereg's cadence in the timing step
Added commands to Amon_RA's recovery image step
Added list of reported successes
Step 4 (Re-run SDK Setup) has been eliminated
Added 20th reported success with a new condition to try to test
Added YouTube video of user Dradien doing the count in the timing step
Added note in timing step about how long to wait after you see /!\ before you start the step over
Rearranged steps 2 and 3 since installing the USB driver after downloading Tereg's SDK folder might overwrite the modded .inf file
Added TODO note to at some point include instructions at various steps for other OS's where needed.
Tereg's testing has eliminated some extra steps, removed step 6 (the driver step), removed step 8 (maintaining a clean sd card, booting the phone back up, setting charge only, turning phone off), removed steps going into recovery where card DOES NOT HAVE TO BE IN when booting into FASTBOOT, therefore the timing step going from FASTBOOT to HBOOT has been removed.
Note about RUU OTA = Leak v3
More successes added with the new "60 partition" method explained by user anoek here: (http://forum.xda-developers.com/showpost.php?p=7089301&postcount=970)
Added 2 successes where both did not run loop.bat
Please note this process is experimental at best. While we have reported a number of successes, it has not been consistent and the success rate seems to be very low or non-existent for a number of users. We are doing the best we can to replicate this process in a more reliable way, and to continue testing for easier ways to achieve this.
**TODO**
Clarify/expand steps that need instructions based on user's OS
List of reported successes
If you find other people with reported successes, there are duplicates listed, or specific information needs to be added for an individual's case, please let Tereg or myself know.
1. Dc_striker (http://forum.xda-developers.com/showpost.php?p=6927162&postcount=1)
2. Hairson (http://forum.xda-developers.com/showpost.php?p=6942651&postcount=186)
3. tereg
4. a-wilcoxj (andirc) Also rooted another phone for another XDA member using his SD card
5. lame eris (http://forum.xda-developers.com/showpost.php?p=6974393&postcount=209)
6. kzoodroid (http://forum.xda-developers.com/showpost.php?p=6975283&postcount=225 and http://forum.xda-developers.com/showpost.php?p=6975440&postcount=228) Also rooted another phone for another person using his SD card
7. RKLamb2 (http://forum.xda-developers.com/showthread.php?p=6972493#post6972493)
8. Dradien (http://forum.xda-developers.com/showpost.php?p=6980387&postcount=318 and http://forum.xda-developers.com/showpost.php?p=6980491&postcount=320)
9. graphitedv (http://forum.xda-developers.com/showpost.php?p=6981435&postcount=334 http://forum.xda-developers.com/showpost.php?p=7011890&postcount=598) - Rooted a second phone, rooted using a Mac running 10.5.8 and the 2GB PNY card
10. djblade17 (http://forum.xda-developers.com/showpost.php?p=6981578&postcount=336) - Win 7 64 bit
11. xtreme3737 (http://forum.xda-developers.com/showpost.php?p=6985257&postcount=365)
12. reethewhat (http://forum.xda-developers.com/showpost.php?p=6987179&postcount=389) - Win7 64 bit
13. largerlager (http://forum.xda-developers.com/showpost.php?p=6988950&postcount=399)
14. Austinjs0102 (http://forum.xda-developers.com/showpost.php?p=6989397&postcount=405) - Windows XP SP3, 2GB PNY card
15. HaRdC0r3 (http://forum.xda-developers.com/showpost.php?p=6963059&postcount=457)
16. varkie (androidforums) (http://androidforums.com/htc-droid-eris/109901-how-many-successfully-went-leak-root.html#post1023198) - PNY 2GB National Geographic SD card
17. Pimpshit420 (http://forum.xda-developers.com/showpost.php?p=6990916&postcount=426)
18. rcharris (http://forum.xda-developers.com/showpost.php?p=6991694&postcount=437) -- Rooted using OS X. Originally tried in WinXP, switched to Mac OS X and got it rooted.
19. bpenney1 (http://forum.xda-developers.com/showpost.php?p=6993850&postcount=448) Had PNY card
20. davinci27 (http://forum.xda-developers.com/showpost.php?p=6996272&postcount=468 and http://forum.xda-developers.com/showpost.php?p=6996996&postcount=472)
21. Jdog94, on page 71, used airplane mode.
(http://forum.xda-developers.com/showpost.php?p=7034130&postcount=733)
22. NAA_Silent (androidforums) http://androidforums.com/htc-droid-eris/109865-leak-root-has-been-found-4.html#post1065772 -- "I tried about 30 times on my work machine running XP while using my Polaroid 16 gig card. I was not successful. Last night I tried again on my Win 7 64 laptop using the factory 8 gig card that came with my Eris. After about 5 attempts I hit the jackpot. I left the loop running instead of ctl+c after each attempt."
23. lostpilot28 (http://forum.xda-developers.com/showpost.php?p=7103114&postcount=1009 and http://forum.xda-developers.com/showpost.php?p=7113530&postcount=1038) - "I flashed the 60partitions.img file to my PNY 2GB SD card and did exactly as he said."
24. igot3ballz (http://forum.xda-developers.com/showpost.php?p=7104474&postcount=1013)
25. listyb01 (http://forum.xda-developers.com/showpost.php?p=7106183&postcount=1017)
26. homewmt (http://forum.xda-developers.com/showpost.php?p=7106822&postcount=1019) - Used anoek's dd image of 60 partition sd card
27. szgtr (http://forum.xda-developers.com/showpost.php?p=7122616&postcount=1055) - Used 4GB RiDATA card
28. lil_dez (http://forum.xda-developers.com/showpost.php?p=7142521&postcount=1087) - Did not run loop.bat
29. Nickboxer7 (http://forum.xda-developers.com/showpost.php?p=7143847&postcount=1088) - Did not run loop.bat
NEW thing to test "The last time I got /!\, I left the phone in the /!\ and popped the card out tand then right back in. Still had /!\ on the screen, but suddenly the device showed up in the loop." Also disable wifi, 3g, gps, bluetooth, and enable airplane mode.
Applications
-->Development-->and check the box titled "USB Debugging"
Video Tutorial by ECLIPS3 & Tereg
http://vimeo.com/album/250913
Prerequisites
Here is a dd image of teregs sdcard in a 7zip archive
http://www.multiupload.com/OT7SH4XNBP
1.Get the Java JDK
For the Java JDK go to http://java.sun.com/javase/downloads/index.jsp
Install Java Platform, Standard Edition, JDK 6 Update 20
2. Downloading Android SDK and running SDK_Setup
Go to http://developer.android.com/sdk/index.html and download the sdk for the platform you are using. Extract the folder contained in the .zip file to the C: drive. (In Windows's case, that would be C:\android-sdk-windows\).
Run SDK_Setup.exe from inside the android-sdk-windows folder.
*Note: you may get a prompt saying that it can't download the repository.xml*
To fix that error close the warning box and click on "Settings" on the left hand side and then check the box that says "Force Https://... sources to be fetched using http://"
Go to Available Packages, the list should now be populated, expand the list by clicking the little + next to https://dl-ssl.google.com/...
*Note: it is not necessary to download the SDK Platforms
Check the box marked "USB Driver Package" at the very bottom of the list
Click Install selected on the lower right corner of the window.
Click the Accept All Radio button on the lower right window that was brought up, and then click the Install button on the lower right corner.
To make sure you are on the right track you should now see in the list of installed packages two total packages:
Android SDK Tools, revision 6
USB Driver package, revision 3
3. Overwrite the android-sdk-windows folder with all the files you need
**TODO** (Include instructions for Mac and Linux SDK downloads)
Here you can download Tereg's complete SDK with all the files used http://www.multiupload.com/01Q1UXGLOF
Unzip the folder to C:
In our setup we have extracted the Android SDK to C:\android-sdk-windows
Root Process
Tereg's analysis has shown that RUU OTA = 2.1 Leak v3. If you have Leak v3 on your phone, then you probably do not have to do this step.
4. Flash the RUU OTA Update
Go to: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe and download the RUU OTA executable.
WARNING: THIS WILL WIPE YOUR PHONE. IF YOU HAVE ROOT YOU WILL LOSE ROOT. BACKUP THE CONTENTS OF YOUR SD CARD AND APPS YOU HAVE INSTALLED BEFORE YOU CONTINUE WITH THIS STEP.
If you need to backup the content of your SD Card, mount your phones SD card as a disk drive, open the drive within My Computer, and copy/paste all folders into a new folder. Copy the contents somewhere safe, we are not responsible for any lost data.
In addition to backing up your SD card, you should find a way to back up your phone (apps, settings, etc) using any method available (like MyBackup or Astro File Manager, etc). You will have a stock, wiped phone when you are finished with this step.
Execute the .exe and go through the wizard process.
5. Make sure USB Debugging is turned on on the phone
From the Home screen, press the Menu button -> Settings. Tap Applications -> Tap Development -> Make sure that USB Debugging is CHECKED.
Open a command prompt by going to Start -> Run. Type cmd in the text box, click OK.
If using Linux, open a terminal prompt and change your working directory to the android SDK tools folder and execute the "adb devices" command.
Execute these commands
Code:
cd \
If you don't see
Code:
C:\>
then type and execute
Code:
c:
Execute the following commands
Code:
cd android-sdk-windows
cd tools
adb devices
If you see the following
Code:
List of devices attached
HTxxxxxxxxxx device
where xxxxxxxxxx is some alphanumeric value, then you have done this step successfully.
Note: Old Step 6: Updating drivers for devices has been tested as unnecessary
6. Mounting the SD Card as a Disk Drive and formatting
Mount the SD card as a disk drive from within the phone. To do this, drag the notification bar down and tap the Ongoing notification (either Charge Only or HTC Sync) section. Tap the Disk Drive option (Mount as disk drive), and tap Done.
If you don't still have Computer Management open, click the "Start" button on your computer, RIGHT click on "My Computer", click "Manage", then Click "Disk Management" which is under "Storage" on the left pane and you will see all your drives.
Find your SD Card in the lower half of the right-hand pane. If you do not see your SD card, go to the Action menu and select "Refresh". If you bought the SD Card listed here, the size of the partition is 1.83 GB. Right click on this partition, and select "Format...", and click the "Yes" button that you are sure you want to do this.
Make the volume label blank, pick FAT32 as the file system, and select the allocation unit size 4096
DO NOT do a quick format.
Click the format button on the bottom right corner, then click OK to confirm the format.
Let it format, DO NOT eject the card while formatting.
When the format is complete, power off the phone.
Note: Old Step 8: Maintaining a clean SD card has been tested as unnecessary
7. Booting into recovery (the timing step)
.wav file of Tereg doing the count in this step: http://www.multiupload.com/IRL99EH394
NEW: Dradien has uploaded a video doing the count - http://www.youtube.com/watch?v=2bRl2ul7GdA
Note: The SD card does not have to be in. It can be out before you boot into FASTBOOT. Therefore, you do not need to press down on the SD card while in FASTBOOT, press Vol Down, then remove the SD card.
Make sure that the SD card is OUT before you begin this step.
Boot into FASTBOOT mode by pressing and holding the Send+Power buttons.
Go into HBOOT by pressing the Vol Down button.
NOTE: Running the loop is just for convenience purposes. It is not mandatory for this method to work.
Start -> Run -> type cmd in the box, click ok.
In the command prompt type
Code:
cd C:\android-sdk-windows\tools
Type
Code:
loop
and press enter
Position your right hand over the sd card and the left hand over the Volume Up button. As soon as you press Volume Up, starting counting "1-1000, 2-1000, 3-1000, 4-1000", which in Tereg's case took approximately 2.5-3.5 seconds. As soon as you finish counting, press the SD card into the phone.
Watch the command prompt. If it works it should display
List of devices attached
HTxxxxxxxxxx recovery
over and over again where xxxxxxxxxx is some alphanumeric value
If this succeeded you can stop the loop by pressing Ctrl+C
Important Note: After you see the /!\, you will need to wait for several seconds before you restart this step. You will need to wait for Device Manager to stop flickering before you pull the battery. Wait at least 10-15 seconds after you see the /!\ icon before you start this step over.
If this did not succeed, make sure that Device Manager is not flickering, then pull the battery to turn off the phone. Stop the loop in the command prompt by pressing Ctrl+C, and repeat this step again starting with the phone off.
8. Pushing files in recovery, and getting #
Next on the phone press Volume UP + Power at the same time, which will bring up a menu in Recovery.
Then select "Apply sdcard:update.zip"
THIS STEP WILL FAIL, don't worry, we expect it to.
Once the update has failed we need to go back to our command prompt (the one we stopped the loop in) and type
Code:
adb push ota.zip /sdcard/update.zip
and press enter, then type
Code:
adb push root.zip /sdcard
and press enter.
After each command, ensure there is no error message after executing the command.
The status for success will be something like
Code:
xxx KB/S (x bytes in xxxx.xxxs)
At the next prompt, type this command but DO NOT execute it yet.
Code:
adb push update.zip /sdcard
This is another timing step. You will need to scroll down to "Apply sdcard:update.zip", and press the Power button then look for a very faint, dim progress bar near the bottom of the screen. The progress bar will be green.
AS SOON AS YOU LOCATE THIS PROGRESS BAR, you need to execute the command you typed.
If successful you should see the Clockwork Mod Recovery along the top of the phone.
Go to the Partitions menu on your phone by rolling the trackball down and pressing the trackball to select it.
Then select "mount /system" once.
Scroll down to +++++Go Back+++++ and select it.
Scroll and select "Install zip from sd card". Then, scroll and select "Choose zip from sdcard", then scroll and select "root.zip"
Once this is done, select Reboot System from the menu, and let it boot normally.
After the phone comes back up to Sense UI, in the command prompt execute this command
Code:
adb install Superuser.apk
Again, you should see something like:
Code:
xxx KB/s (x bytes in xxx.xxxs)
pkg: /data/local/tmp/Superuser.apk
Success
underneath the command where x is some number
Once this step is done, make sure the phone is unlocked, awake and not asleep.
Type
Code:
adb shell
then type
Code:
su
You will get a prompt on the phone from superuser asking for permission. Allow this.
the $ symbol will change to #, which indicates you have root.
[Optional] Step 11. Flashing Amon_RA's recovery image
This step is optional. Follow these steps if you would like to flash Amon_RA's recovery image after you have achieved a root prompt.
Open the command prompt and change your working directory to C:\android-sdk-windows\tools exactly as you did in Step 12.
Execute these commands (Note: When you see $ or #, that does NOT mean you type $ or # respectively in the command. It means that is the prompt you should see at the time you are executing these commands.
If you extracted the android-sdk-tools folder in Step 3, you have all the files you need for this step.
Code:
adb shell
$ su
#mount -o rw,remount /dev/block/mtdblock3 /system
# exit
$ exit
adb push recovery.img /sdcard
adb push flash_image /data/local
adb shell
$ su
# chmod 755 /data/local/flash_image
# /data/local/flash_image recovery /sdcard/recovery.img
# reboot recovery
If you do these commands, you should be able to see Amon_RA's recovery.
At the bottom of the screen it should say "Build: RA-eris-v1.6.2", and you should have the following menu options.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Note: If you are getting Permission Denied errors while doing any of these steps and you still have Clockwork's Recovery partition installed, user Dradien has reported success with the "Fix Permissions" function within Clockwork's Recovery main menu. Dradien reported that that function took about 5 minutes and afterwards was able to flash Amon_RA's recovery image.
Afterward
One thing to note, there is a step we did not do that Slide Root method did which is install a full root.zip that allows you complete root access when you execute an "adb shell ..." command.
i.e. if you run adb shell as the following example command prompt
Code:
C:\>adb shell
you will see a $ prompt, not a # prompt.
Therefore, any commands you are executing (at least for the moment) that require root access (like to flash Amon RA's recovery for instance):
Code:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
you will need to do this in the following manner
Code:
adb shell
$su
#mount -o rw,remount /dev/block/mtdblock3 /system
So, if you are getting permission denied errors from a regular command prompt while executing commands (adb shell mount..., adb flash_image..., etc) that require root access, you will most likely need to drop into shell manually, su into root, then cut off the first part of the command, put the rest of the command into the prompt and execute it.
Example:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
becomes
mount -o rw,remount /dev/block/mtdblock3 /system
Look at other tutorials on how to flash roms, if you have any questions pm me (Captainkrtek) or join us on irc.andirc.net #droideris & #leakroot and ask for any of the opers or Tereg for help.
Below are pictures and tools Tereg used, and how he oriented the phone and positioned his hands and screwdriver over the Vol Down/Vol Up buttons with left hand and over the SD card with the right hand during the SD card timing steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Well written, thank you for writing this guide.

Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.

char561 said:
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
Click to expand...
Click to collapse
Join #leakroot to discuss it

Congrats Tereg, and CaptainKrtek. Tereg your crazy to flash RUU, thank you for trying again and proving

I should note, just remembered, I had Wi-Fi, Mobile Network and GPS all turned off during the entirety of this process.

Wow yeah great guide, people report your success with it and stuff. I'm trying it soon.
Sent from my Eris using XDA App

Great guide hopefully more people start getting root using this method, I currently have root (s-0ff) may try and root the brother in laws phone now he has leakv3. Welcome to the party leakers.

I feel completely crazy for unrooting (and that process is now done), but that's kind of where my mind is. I really want this process to be repeatable.

Hey where is the modified Inf file?

jvward said:
Hey where is the modified Inf file?
Click to expand...
Click to collapse
oops my fault, uploading now! thanks!
EDIT: In the tutorial now

ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?

jrhoades858 said:
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
Click to expand...
Click to collapse
Yes i believe you can, tereg just unrooted his phone to try this method again

Awesome! Trying in about an hour. Thank you!
Sent from my Eris using XDA App

trying right now, and yea i deleted all the adk and everyhting to start fresh =P so when i got the the part to download modded.inf i was like where the link but i remembered i didnt delete my downloads folder so i still had tht file =D haha
edit: O and fat32 with no quick format is taking forever!!!

Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.

To unroot once you do this all you have to do is use the ruu that is posted here and that will set it back to exactly how it was.

zigzackattack said:
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
Click to expand...
Click to collapse
There is a slight chance though pretty much no. Everyone who has tried it with the stock card has failed so your best bet is to go buy a $12 card

Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.

MyFixofAndroid said:
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
Click to expand...
Click to collapse
I do not believe it will. Everyone who has tried has failed.

free sim unlock

I9000 unlock instructions
1. Power on the phone and go to Applications->Settings->About Phone->USB
settings
2. Select Mass Storage
3. Connect the phone to USB cable
4. Swipe down the top notification bar then tap “USB Connected” then select
MOUNT
5. Copy update.zip file to phone mass storage root
6. Power off the phone
7. Press Volume Up+Home+Power on key to start the phone into recovery
mode
8. Go to “apply sdcard:update.zip” using volume keys then select it using
home key
9. Power on the phone then go to Andoid Market and install Terminal
Emulator
10. Run Terminal Emulator
11. Type cat /efs/nv_data.bin >> /sdcard/nv_data.bin into terminal then type
Enter
12. Connect the phone to PC in USB Storage Mode then copy nv_data.bin file
to your pc
13. Open nv_data.bin file with any hex editor (ex. Hex workshop) then go to
address 00181460
14. There are the codes
15. Power on the phone with any unaccepted sim card inside then type in the
first code to unlock the phone
http://www.mediafire.com/?3v6vsqh9qorrwn2
http://www.mediafire.com/?o8djyf4moc9ae44
use thanks button

http://forum.xda-developers.com/showthread.php?t=762384
This is a double post.
And there is no 'thanks' button

Tyxerakias said:
And there is no 'thanks' button
Click to expand...
Click to collapse
Maybe he copy-pasted from a forum that has one?

I am following 100% tutorial but I am unable to unlock my I9000. Look at the screenshot for the error that I encounter.
I have put the update.zip in root of phone memory, root of MicroSD etc but no chance. Do I need to root the phone or what's the problem?
Thanks

Hi,
I have a NSPRO box and read the unlock code, but as I insert it, it doesn't unlock the phone.
As this didn't work, I tried your method, and the code that showes up is the same as read by NSPRO box, and... it still doesn't work.
Attached is the printscreen of the HEX area where the code is. I've noticed it says "18146D" and not "181460" as your indicated. Could this be the reason why the code doesn't work?
Please help...

[How-To] When nandroid via recovery and adb fails

Alright, I faced this problem a few days backed, and when I did my research I found that a lot of people face this problem, or once in a while at least:
When you try to do a nandroid restore you see this:
Error: run ' nandroid- mobile. sh restore ' via console!
So you try to do it via adb (aka console) and you get this:
Error: unable to mount /sdcard, aborting
Frustrating right! You have messed up your phone while tweaking and thought you had the upper hand because you did a back-up.. but now you are dealing with this..
Here's the solution I gathered from web:
1. Check that you have USB de-bugging on under the development settings of your phone
2. Check that you have your sdcard partitioned to at least ext3.
3. Check that you did not rename your nandroid folder, nandroid's content to anything fanciful.
4. Check that you have enough power on your phone, at least 30 percent to be safe. Low power will disable the ability to do a restore in some cases.
Well if you don't have the above:
1. Go enable USB de-bugging under settings>manage applications>development>USB Debugging>activate.
2. Transfer whatever content you have on sdcard to somewhere safe. Then do a proper partitioning via the recovery, upgrade it from ext2 to ext3. Repair the ext in case there are some errors. After this, transfer all contents back.
3. Please rename all folders back to their original name, and don't rename them ever again.
4. Charge your phone with AC supply, and wait till it is at least 30 percent and try to do a restore again via recovery, if not, do step 1 - 3.
Trying to do a restore:
1. Do it via recovery, if everything is fine, it should go smoothly, and you got your upper hand back!
2. If you like to see words running in strings, doing via console is possible too!
-
"quoted from and credit to Slug from android forums"
Open a command prompt window (Start-All Programs-Accessories-Command Prompt)
Type cd/ and hit <enter>
Enter cd adb
Now enter adb devices and it should show "000000000000 recovery"
If so, enter adb shell and you should see the prompt change to #. You're now running as su (root)!
Enter nandroid-mobile.sh --restore. You'll see instructions about "Using G1 keyboard..." disregard and hit <enter>.
After a brief search, the default (most recent) backup found will be displayed along with any others located. If the default choice isn't the one you want to restore, you'll have to enter the full path to the correct one as displayed in the list. You can use the Edit...Mark... function from the command prompt window menu to simplify this, though. Put the cursor at the beginning of the required line, hold <shift> and highlight the test using the arrow keys. <Enter> copies to the clipboard, and Edit... Paste... places it wherever the cursor is placed.
Once you have the correct backup referenced, hit <enter> and you should see the script work its magic.
When Restore done is displayed you can reboot the handset from the recovery menu.
Alright you have got your restore back! Feedback or anymore tips to this problem are welcome! Thank you for your time.
JokerAce

so if we renamed the nandroid backup to something we will remember more easily, and that the problem, what do we do?
edit: how do we know what the original name of the backup was called.

Hi, did you get a Md5 mismatched or something? Please be clear with your problem. If it's a mismatch problem, make sure your rename'd folder has NO Space in the name.

Is there a "Comprehensive IMEI/EFS Backup" that is recommended for S4

On my d2vzw (VZW S3) this backup was recommended for IMEI before flashing new ROMs. Is this something that S4 users should concern themselves with?
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.xda-developers.com/showpost.php?p=30679476&postcount=5732

EFS Backup Galaxy S4
Yes it is recommended since the possibility that you loose your IMEI is always there when flashing ROMs.
Do this backup directly after you are rooted the first time - then you will have it later in case of a lost IMEI.
------------------------------------------------------
The EFS you can save by the following instructions.
You will need:
- Rooted phone
- Busybox installed and started once!
- Android Terminal Emulator
------------------------------------------------------
EFS Backup:
Open your Terminal Emulator and execute the following four commands:
Code:
su -c 'dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.bin'
su -c 'dd if=/dev/block/mmcblk0p13 of=/sdcard/m9kefs1.bin'
su -c 'dd if=/dev/block/mmcblk0p14 of=/sdcard/m9kefs2.bin'
su -c 'dd if=/dev/block/mmcblk0p15 of=/sdcard/m9kefs3.bin'
The EFS backups are now on the internal SD.
The first file should have around 13,6MB and the other three around 780KByte.
------------------------------------------------------
EFS Restore:
Open your Terminal Emulator and execute the following four commands:
Code:
su -c 'dd if=/sdcard/efs.bin of=/dev/block/mmcblk0p10'
su -c 'dd if=/sdcard/m9kefs1.bin of=/dev/block/mmcblk0p13'
su -c 'dd if=/sdcard/m9kefs2.bin of=/dev/block/mmcblk0p14'
su -c 'dd if=/sdcard/m9kefs3.bin of=/dev/block/mmcblk0p15'
------------------------------------------------------
Furthermore you should also use the Qualcomm Service Tool to backup your IMEI & NV.
You will need:
- Kies installed on your PC
- QPST installed on your PC
Then do the following:
1) Call *#0808# on your phone
2) Choose "AP" and "RNDIS + DM + MODEM" and confirm by clicking "OK" (your phone is now in DIAG mode)
3) Kill Kies in your task manager
4) Connect the phone via USB
5) Start "QPST Configuration" on your PC
6) Choose the tab "Ports" and click "Add New Port"
7) Choose the port "USB/QC Diagnostic" with "SURF9615" as name
8) Choose "Start Clients" in QPST and start "Software Download"
------------------------------------------------------
Backup of IMEI & NV Data:
9) Change to tab "Backup" and choose a save location by clicking "Browse"
10) Click "Start" and wait until the process is completed
11) A QCN file should have been created with a size of about 350kB
-------------
Restore of IMEI & NV Data:
9) Change to tab "Restore" and choose your location of the QCN file by clicking "Browse"
10) Click "Start" and wait until the process is completed
11) By calling *#06# you should see you old and valid IMEI again
------------------------------------------------------
Change your USB mode back by calling *#0808# again and choosing "AP" and "MTP+ADB"
------------------------------------------------------
This sounds a lot but is done really fast and you only need to do it once after the first time being rooted. Hence it is worth doing it

pitcher85 said:
Yes it is recommended since the possibility that you loose your IMEI is always there when flashing ROMs.
Do this backup directly after you are rooted the first time - then you will have it later in case of a lost IMEI.
------------------------------------------------------
Backup of IMEI & NV Data:
9) Change to tab "Backup" and choose a save location by clicking "Browse"
10) Click "Start" and wait until the process is completed
11) A QCN file should have been created with a size of about 350kB
-------------
Restore of IMEI & NV Data:
9) Change to tab "Restore" and choose your location of the QCN file by clicking "Browse"
10) Click "Start" and wait until the process is completed
11) By calling *#06# you should see you old and valid IMEI again
------------------------------------------------------
Change your USB mode back by calling *#0808# again and choosing "AP" and "MTP+ADB"
------------------------------------------------------
This sounds a lot but is done really fast and you only need to do it once after the first time being rooted. Hence it is worth doing it
Click to expand...
Click to collapse
I tried using this method on my I9195 (S4 Mini LTE model), but it doesn't make any difference. IMEI is still broken. I checked backup with hex editor, everything is fine, it contains my imei in hex. But it seems, that it doesn't write any changes in memory in my phone. Any solutions?

[Help!] Update System with Terminal Emulator with Error "no space left on device"

[Help!] Update System with Terminal Emulator with Error "no space left on device"
I follow the following instruction to update my Meizu Pro5 with success for several times, but i got an error message "no space left on device" this time. Is there any way to solve this?
1. Enable root
Enable root by tapping on Settings-> Accounts-> My Flyme-> Personal settings (first option) -> System privileges and set it to open - accept disclaimer and confirm.
2. Download and successfully install Busybox (from Google Play or see .apk below)
3. Download and install a Terminal Emulator (from Google Play or see apk below)
4. Download the correct and desired international (i) ROM/firmware (update.zip) for your device
5. Download and use the update.zip (firmware) converter that creates the required system-i.img
Click here to download converter first
Copy system.new.dat and system.transfer.list (from the update.zip) to the folder “in” (see converter folder)
Then start the converting process by starting System-conVERTER.cmd and pressing option 1 [enter]
If successfully converted you can find the system-i.img in the ‘‘out’’ folder.
6. Copy the converted system-img from ‘‘out’’ to the internal memory of your Meizu device
7. Go to Settings-> Display-> Sleep and set it to at least 10 minutes
8. Start the Terminal Emulator and run (type) the super user command
su
A permission popup will come; give permission by tapping allow (always allow).
9. Now run (type) the command for installing the system-img.
dd if=/sdcard/system.img of=/dev/block/platform/XXXXXXX/by-name/system
Replace XXXXXXX with the correct partition system for your device
MX4 Pro = 15540000.dwmmc0
M2 note = mtk-msdc.0
MX4 = mtk-msdc.0 (OR mmcblk0p6)
MX5 = mtk-msdc.0 (OR mmcblk0p18)
Pro 5 = 15570000.ufs
Example for MX5 : dd if=/sdcard/system.img of=/dev/block/platform/mtk-msdc.0/by-name/system
Note: Pro5 might require: dd if=/storage/emulated/0/system.img instead of /sdcard/
10. The installation should start after the ‘‘dd if’’ command, but please note…
…it may seem that the copying/process did NOT start because you didn’t notice it, but it DID start.
do NOT type a new command or whatsoever, just…
…be patient and give your device 5-10 minutes to process.
11. When the process is done you’ll see a # at the very end
Your device should be unresponsive by now - this is normal
12. Now just shutdown your phone (hold power button) and reboot it
13. Once successfully booted your device should be running an I-rom
Once in Flyme again it is wise - but not necessary - to completely reset your phone. Go to settings->about phone->memory->factory data reset-> check both boxes and click start cleaning (this could take 5-10minutes). Always backup your stuff if necessary.

use“SD maid”​