Return to Contents Page - doubleshot Developers Reference
Also, see this post on Preparing for backup.
Hey all, time for a quick public service announcement to help people make sure they don't lose things they may want to use later that came on their phone.
Post 1 - ADB backup methodology. Does not create installer package.
Post 2 - Clockworkmod Backup methodology. Does create installer package usable through CWM.
****Post 2 to be updated for Official CWM 5.0.2.7 - Meantime the method is the same.
Post 3 - To be announced.
IMPORTANT: Make sure you back up all your unique user data ( phone numbers, saved files and the like ) before doing anything to the phone. If something happens and you lose your data, don't blame me. The point of this guide is to backup your stuff, and stress the importance of backups, so ( Duh! ) make sure you backup anything you've done to the phone before you start.
-Back up your SDcard as well before starting. Just plug your phone into your computer and open up a window to it, you can drag and drop all the files off the SDcard. You could also power off the phone ( fastboot off! for best results ) and take out the SDcard and plug it into your computer with a card reader to accomplish this.
-After you back up your stuff, might be a good time to do a factory reset to your phone. If you haven't flashed a ROM yet, then perfect! Do a factory reset anyway to make what we're gonna do next as "stock" as possible. After a factory reset you will probably have to re-install superuser and busybox.
( To do a factory reset, open your app drawer and go to settings. Then go to "SD & Phone Storage" and select "Factory data reset". Yes, you do want to wipe your SDcard too. )
By the end of this guide you will understand why everyone here playing around with this kind of stuff should have the Android SDK on their computer, so on to the guide:
Today's workshop is going to require the use of ADB ( android debug bridge ), but don't be afraid of it - it's not as hard as it seems. I will also be assuming the use of a windows computer ( I'm using XP, other versions are probably similar in executing these instructions )
What we're going to do is make a quick backup of all the stuff you can easily save on your device.
You will need root access to the device to make this happen, or you will get : permission denied.
So, after you successfully S-OFF, then install Superuser (Root) and busybox, ( don't forget to check that you have root & busybox installed correctly ) put the phone down for a few minutes and take the time to get ADB running on your computer.
You'll need to download the Java Development Kit and install that on your computer. Next, you'll need the Android SDK downloaded and installed on your computer. Don't forget to run the SDK manager to get the rest of the android tools you need to make it work. Plenty of guides around on XDA if you need help with that. You will need platform-tools to use ADB.
Also, configuring the Android SDK itself to work on your computer is beyond the scope of this guide, but again, there are tons of resources all over XDA to find out how to do this.
For the rest of this posting, I will assume you have ADB set up, and I will assume you install the Android SDK to the following location:
C:\Android
That's a folder on your C: drive called Android. So far, pretty simple, right?
(If you installed it somewhere else, just modify the command to account for that)
Okay, now that that's all done, let's go ahead and get your phone backed up.
*Note: This does not make some kind of installable package you can put back on your phone, or anything like that. It will simply put everything you can copy from your phone into a folder on your computer, that you can use to get original stuff from.
For instance: You can use a stock .apk file and re-install it on your phone, or maybe you lost your stock fonts and want them back again. Simply find the font folder and copy them back onto your phone.
Click to expand...
Click to collapse
First thing you have to do, is pick up your phone and make sure it's in USB debug mode. You can accomplish this by going to:
App drawer - Settings, then Applications, then Development, then selecting "USB debugging"
Click to expand...
Click to collapse
You might want to also select "Stay awake" while there too, to prevent the phone from sleeping while you work with it.
That being done, plug your phone into the computer with the USB cable it came with. Don't do anything else to it yet, just forget about it for a little while.
(I will put all commands you type in bold so you can see them easily. Make sure to not miss any empty spaces between letters or symbols, and type them in exactly as shown.)
Now, kick up your command prompt. Go to Start, Run, and type in cmd and hit enter (or click ok).
Next, type in CD \ and hit enter. Your command prompt should now just look like:
Code:
C:\>
Now, type in CD C:\Android\platform-tools and hit enter. Before hitting enter, it will look exactly like this:
Code:
C:\>CD C:\Android\platform-tools
Your command prompt should now look like:
Code:
C:\Android\platform-tools>
Okay, stop. Go to your C drive on your computer. Make a new folder, call it "AndroidPhone" (no quotes or spaces in the name). We called it that so it will sit right next to your Android folder, making it easy to find.
Okay, go back to your DOS window, and make sure you still see...
Code:
C:\Android\platform-tools>
...as the last line in the window.
Now you want to type in: adb pull / C:\AndroidPhone and hit enter.
Before you hit enter, the whole line should look like this:
Code:
C:\Android\platform-tools>adb pull / C:\AndroidPhone
Note the spaces, and where they are. Make sure to get the forward and backward slashes right.
After you hit enter, sit back and wait. The DOS window is going to light up with a whole mess of stuff that will scroll down the screen. Some things will be skipped, others won't be. Just be patient and wait for it to be finished, it's going to take a while. Some things will happen faster then others.
When done, your DOS window will sit there and the last line will look like:
Code:
C:\Android\platform-tools>
...and have a blinking underscore right after it.
Go check the AndroidPhone folder, and make sure you got it all. It should be somewhere around 700MB in size. If it's a lot less, then you weren't successful.
That's it! Congratulations, you now have a copy of most of what was on your phone when you got it. Wasn't that hard, was it?
Let's take a look at some other ways we can use the pull command:
If you want to back up a specific folder, the "system" folder for instance and put it in a different folder called "NewBackup", then you would type this in as your command instead:
adb pull /system C:\NewBackup
...and it should look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system C:\NewBackup
Make sure to create the "NewBackup" folder before running the command!
If you only wanted to back up the system apps on the phone, and wanted them in a seperate folder called "AppBackup" and then in a folder inside that one called "stockapp" - you would type in this command:
adb pull /system/app C:\AppBackup\stockapp
...and it would look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app C:\AppBackup\stockapp
Don't forget to make the folders you will be saving to before you run the command.
For our last example, if you wanted to back up a specific app, to just your C drive, you could do this command:
adb pull /system/app/Calculator.apk C:\
...and it would look like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app/Calculator.apk C:\
Two things to note here:
1- Typing this does not work:
Code:
[COLOR="Red"]BAD CODE EXAMPLE DO NOT DO THIS[/COLOR]
C:\Android\platform-tools>adb pull /system/app/[COLOR="Red"]c[/COLOR]alculator.apk C:\
Why? the app name is typed with a lower-case "C" at the beginning. This is case sensitive, and the app we are talking about has an upper-case first letter. Compare that bad code example to the previous good one for the same app.
2-The HTC optimized apps have an "Odex" file there as well. Backing up this specific app directly, which also has a companion file Calculator.odex, doesn't get the other file. We also have to get it manually by doing it this way, type in the following command:
adb pull /system/app/Calculator.odex C:\
...which looks like this before hitting enter:
Code:
C:\Android\platform-tools>adb pull /system/app/Calculator.odex C:\
...and you will have both the app and it's odex file saved.
You don't need the .odex files to re-install the app on your phone, they will work without them. Re-installing the .apk file doesn't re-install the .odex file, you would have to put the .odex file back on the phone manually.
So that about covers it, and shows how to use the command to place things in different locations, get different folders, and specific files.
I tried to show the command with just enough variation that you could easily see what parts of the command affected which part of the outcome, and make it very plain to see how it all worked.
I even made sure to show you that you can open other folders on your computer with the DOS prompt open, do things like create folders, and then come back to the DOS window and execute a command you already typed in.
I wrote this because i've seen people already asking for things like stock system fonts, and so forth, and you should already have that backed up before you go ahead and flash a ROM. To account for the wide range of familiarity people have with the adb pull command, I tried to make the whole thing targeted to someone who has never used that specific command before.
As I said above, installing and configuring the Android SDK and the adb command specifically are beyond the scope of this thread, since it's been covered to death elsewhere on XDA and we don't need yet another one of those threads.
I think you can now see why doing such a thing is a good idea even if you just flash ROMs and don't actually create them. The Android SDK can be useful for users, too, since flashing a ROM is not something a typical user of the phone is expected to be doing. By flashing a ROM, or trying to, you take that step that makes you an advanced user of your phone.
I am extremely cautious when it comes to backups of my data, and make many of them. In my experience, most people seem to only think about backups when they need them, and by then it's too late to make one. Doing this right after you get root can save you from losing anything you might want back again some day.
For bonus points, you can then burn that folder you made of all your phone data to a DVD. Don't forget to put the Java SDk, Android SDk, and anything else you downloaded or used to make this work on the DVD as well so you can do this again or on another computer...without having to download all the software packages over and over again.
Just a friendly public service announcement/guide, and as a helpful bonus, i'm going to list all the stock system apps below with their complete location listed. This may make it more helpful to browse the other threads in our corner of XDA telling you what apps you can remove and such.
My most worthwhile contribution to the development community at this time is time itself, so trying to map out and explain where everything is on the device is where i'm at. If you are reading this, then you're along for the ride too.
Edit to add:
I was going to list the stock apps here by .apk name for reference. When I sat down to do it, this came out:
MT4GS Stock App Developers Reference
Go there for a list of apps if you need it, but the reference was written for developers - the apps are listed in alphabetical order according to .apk name, not by any other names programs might call them.
Clockworkmod Backups
***Note: Posting to be updated for Official Clockworkmod 5.0.2.7 - Update forthcoming.
In the second post we will talk about Clockworkmod backups, or CWM backups.
We will be discussing Clockworkmod version 4.0.0.9
If you are still using 4.0.0.8, then you should go Here to upgrade.
Now that we're all on the same, most recent version of the MT4GS CWM recovery utility, let's take a look at how we can use just the phone itself to generate and restore our backups.
Before we start:
- Charge your battery to full. You don't want to lose power while doing this.
- Make sure you have enough free space to make the backup. A stock backup fresh after S-OFF should be right around 700MB. Try to have about a gig available on your sdcard to make sure you get the whole backup.
First, boot into recovery mode.
- Turn off fastboot in ( settings: Power: [uncheck] fast boot.
- Power off the MT4GS
- wait until it completely powers down, there will be a red light faintly blinking inside the trackpad. Wait until it stops.
Then:
+ Hold the volume-down button
+ Then press the power button
+ Hold the volume down button until you see your HBOOT menu, then release.
+ Wait for HBOOT to load, then use the volume up and down keys to navigate to recovery, and the power button to choose it.
+ Clockworkmod will load, and then you see the main menu of your recovery utility:
- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- power off
Click to expand...
Click to collapse
*Within CWM itself, you can use either the volume up and down buttons or the trackpad to scroll the menu selections.
*You may press either the trackpad or the camera button to choose your selection.
To make a backup:
+ Scroll to 'backup and restore', then select it.
At the next menu you see:
- backup
- restore
- advanced
Click to expand...
Click to collapse
Okay, as soon as you select backup, it will immediately start the backup process.
Before we do that, we just want to make sure we have a full or decent charge on the battery, and we won't be shaking or jarring the phone while it's working. Don't do this in a moving car or train or anything.
Just put it down on a table or something, choose 'backup' and then walk away from it for 5-15 minutes.
( The amount of data and class rating/brand of your MicroSD card directly impacts the time it takes to create or restore a backup. )
When you come back, the last line of text on the screen will say:
"Backup complete!"
Now you have two choices for what you should do next. First go back to the main clockworkmod menu ( hit the hardware 'back' key if necessary ) and then choose:
- power off. If you want to turn the phone off, and take the memory card out to copy the backup to something else.
- reboot system now. If you want to boot up and transfer the backup off the phone using the phone somehow.
+ I recommend reboot, then after fully booted plugging your phone into a computer through the usb cable. Then you can transfer the file to a computer without opening the phone and exposing the internals.
Once you copy the backup onto the computer, you should probably burn it to a cd or something to make sure you don't lose it.
About the 'image' files in the folder with the current time/date on it:
-Some will be saved, some will read as an error on the screen probably...
+++As long as you have these 3 images you are okay:
-Boot
-Recovery
-System
Anything else is not really necessary, but can be helpful. If you have those 3 core image files and an MD5 checksum that matches up, you're in good shape.
...and that's basically it. CWM will make the backup or not, and if not you need to figure out why. Ask questions in this thread if this happens to you and you can't figure out why.
CWM makes the backup in a folder on the sdcard called 'clockworkmod', then the 'backup' folder, then your backup in it's own folder, the name of which is the current time and date.
/sdcard/clockworkmod/backup/
Attached below is a picture I made showing the process, including some errors of partitions not found. This is still a good backup, because I have boot, recovery and system.
Saving the third too.
Information forthcoming...
Man, you are intense!
Related
I was attempting to get the Nandroid back up feature going on my phone. I downloaded the recent RC30 for the multi-touch (I couldn't help it), and I was given this error about the application settings not responding and to force quit. Then I downloaded the SPL bootloader and the modified RC30 with the busybox. It's in this post (http://forum.xda-developers.com/showthread.php?t=459830). I did a successful backup, but now my phone won't work right.
When I boot the phone none of the buttons respond until a good 30 seconds into the full boot up, and only after I slide open the keyboard. When I press the power key the screen flashes and the blank wallpaper comes up for 5 seconds. There is no way for me to get into the recovery mode. When I tried that it gives me the phone with the exclamation point.
I think I am just at or 1 day past my 14 days. It's really going to suck if I have to pay for a new phone b/c I got cocky and thought I knew what I was doing. Hopefully you guys have a solution or T-mobile will be forgiving.
Oh, and when I look under settings it says: kila user 1.0 TC4-rc30 so T-mobile will know I rooted the phone and F'ed up.
You could try restoring with DREAIMG.nbh
and you didnt brick it, a brick doesnt do anything, yours sounds like it boots.
I can't get into recovery mode. I can get into fastboot. I found a thread on installing cupcake will help get it back to RC30, but I didn't understand where to type in the prompts.
When I tried that it gives me the phone with the exclamation point.
Click to expand...
Click to collapse
Try Alt-L at this point.
I forgot about that. Thank you! Now I just need to find a way to get my phone back to full functionality. Do I need to just find RC29 or JF RC30 and reinstall as update.zip?
It says "E: Can't open /cache/recovery/command"
We will see if reinstalling RC30 will work. Does anyone have the orignal RC30 that comes installed on the G1? I understand I'll lose root access and that might be the smartest thing for me now.
I reinstalled RC30 and it worked! Thank you guys, and thanks for putting up for my temporary insanity!
I would do a wipe and then update to jf's latest 1.4. But at this point you should be able to update to whatever you want.
Sorry if this is a stupid question but I have made a NANDROID Backup and I would like to know how to restore my phone with the backup I made.
ow to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/show...53&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Constructive criticism is welcome.
This is my first guide and it's quite late here so I'm going to go through this lightly first, and more in detail later.
Note: I am NOT responsible for any damage your phone may or may not receive. It is your fault for following this guide, not my fault for writing it. Just for the sake of saving you from a headache, I would recommend backing up your contacts before starting this guide.
Phase 1: Prepping your CDMA Hero for rooting/flashing.
1. Ensure that USB debugging and installing apps from unknown sources is enabled. You can do this by going into Settings> Applications Check unknown sources. From there go into Development and ensure that "Enable USB debugging" is checked.
2. Mount your SD card on your computer by plugging in the USB cable, and dragging down the notification area. BACKUP YOUR DATA! ALWAYS!
3. After your data is backed up, Safely remove hardware (I find it annoying to get the "this disk may contains errors" every time i plug it in) your Hero. Using your notification area, unmount your SD card.
4. On your hero, navigate to Settings> SD card and phone storage> unmount SD card. Then format your card. It should Auto re-mount after this.
5. Download FlashRec (great tool!) and Amon-RA's recovery image. Place them onto the root of your SD card (not in any folders, just drag and drop them.) Unmount your SDcard.
6. I used Linda File manager (from the market), but you can use one of your choice. Navigate to the root of your SDcard (you'll probably start there, if you dont just click sdcard.) Open flashrec with the installer, and wait until it's finished.
7. Open FlashRec, and attempt to make a backup (i simply named mine "/sdcard/backup"). If it success proceed to the next step. if not, refer to post 2.
8. In FlashRec, type "/sdcard/recovery-RA-heroc-v1.5.2.img" without the quotes. Linux is Case-sensitive, so the capital letters have to be included. tap "download recovery image". Wait for it to finish, when it does reboot into recovery mode by powering off your phone. After it's off, hold HOME and the power button. You should see some green text on a black background.
9. First things first, Make a nandroid backup. It can, and will save your ass at some point in time. Before you flash ANYTHING to your phone, ALWAYS do a nandroid backup. Congratulations, you can now flash a custom ROM!
Phase 2:Flashing your custom ROM
Since I love Flipz and his work so much I'll be using his ROM in my guide (let me know if you have a problem with it Flipz).
0. Do a nandroid backup before you even think about downloading a ROM
1. Download Fresh 1.0.
2. Do not unzip it, leave it as it is and copy it to the root of your SD card. You can do this either from recovery mode (by enabling usb mode) or through the notification bar. Proceed to recovery mode by holding HOME+END CALL (or just disable USB mode) and select "flash update from .zip" Select the Fresh ROM and wait. It should automatically reboot after it finishes installing.
3. Be patient while it's booting, it took me about 5 minutes for the first boot, after that it gets much faster. Once it loads, everything should be all fine and dandy. If it's not, well aren't you glad you made your backup? Just proceed back into recovery and do a nandroid restore.
4. You can now delete all those .apks and .zips and whatnot. Mount your SD card on the computer, and move your backed up files back onto your card.
5: Enjoy! If you don't like the clear lock, Flipz has a patch on his website (geekfor.me) to replace it with a clear screen. This should keep all of your contacts and settings in place, but I make no promises.
Sources:
The Unlockr
How to unpatch your Sprint CDMA Hero.
Phase 1: Installing the SDK/Drivers
1. Download the SDK from Google. Create a folder at the root of your C:\ drive called android (it doesn't have to be your C:\, you can put it anywhere, but this guide will use "C:\android" as it's path.)
2. If using Windows Vista or earlier, proceed to the next step.
3. Download the driver for your system.
Windows 7 32Bit
Windows 7 64bit
To find out which drivers are right for your system, go into your control panel, and change the view type to small icons. Click on system, and check and see if it says 64-bit Operating System or 32-bit Operating System. Extract the contents into:
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x64 (for the Windows 7 64-bit)
or
C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Vista_x86 (for the Windows 7 32-bit)
4. If you have not plugged your Hero into the computer yet, it's as simple as navigating to where you extracted the contents of the archive, and right clicking androidusb.INF (should be the second from the top) and clicking install.
5. Ensure that USB debugging is enabled by navigating to Settings>Applications>Devolopment. If it does not have a check next to it, tap it. Plug your phone in and wait for the drivers to install.
6. In Windows, navigate to the command prompt.
XP: Start>run type "cmd" and press enter.
Vista or later: Start/"orb" in the search box right above it, type "cmd" and press enter.
if you see a window pop up with "C:\Windows\system32\cmd.exe" if you have done this correctly.
7. type "cd \android\tools" and press enter. now type "adb devices". It should start a daemon, and show you a series of numbers. If it does, then congratulations! your drivers are installed properly! I'll come back and add later how to reinstall the drivers if they do not install correctly.
Phase 2: Unpatching your Hero
Ensure that you have an adaptor to plug your SDcard into your computer. I didn't use an adaptor when i did this, but I highly recomend it just to make things easier. If your phone or SDcard or computer or toaster blows up, catches fire, shoots lazer beams and burns your curtains, or causes any damage to your or anything else I take no responsibility.
1. Backup all of the data from your memory card onto your computer. Navigate to Settings> SD and phone storage. Unmount your SD card and format it.
2. Go to Settings> Applications> Devolopment and ensure USB debugging is enabled.
3. Open command prompt, as you did in Phase 1, and navigate to "C:\android\tools". Type "adb shell" and press enter. Now you're in your phones console. Type "cat /sys/class/mmc_host/mmc1/mmc1:*/cid"
4. Copy down the code you get EXACTLY. Double, triple, and qraduple check. If the code is wrong, you may destroy your SD card.
5. Reverse the code.
Example:
123456789
Would become
987654321
6. replace the first two numbers/letters with zero zero. (007654321). Now on your PC, navigate to Here. Copy the number (with the zeros in place!) to the box that says CID. Click continue and wait for the email with your goldcard key. Save it to your computer.
7. Download this hex editor and install it. run it (requires administrative priveledges), and put your SDcard into your computer, or mount your SDcard.
8. In the hex editor, click on the extra tab, and open both your SDcard and the Goldcard you downloaded earlier. Ensure that "Open as read only" is unchecked when you open your SDcard. Sector size should be at "512 (Hard Disks/Floppy Disks)".
9. Go to the Goldcard tab, and press Ctrl+A to highlight all of it, then press Ctrl+C to copy it. Go to your SDcard tab, and select from 00000000 to 00000170. Now click on the edit>paste write.
10. click File>save. Remove and replace your SDcard, or unmount and remount your phone. If you can navigate into the drive, congratulations you have a Goldcard.
Phase 3: Downgrading your Hero.
1. Download the1.29 RUU. Plug your phone into the USB port with your goldcard inserted. Have your phone powered on when you do this, and ensure that it is not locked.
2. Ensure that you have HTC Sync installed, and that it connects to your phone.
3. Run the RUU and wait for it to finish. After it is finished, proceed to post 1.
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
saintirish said:
If we simply want to upgrade to a different ROM or the new 1.5.2 recovery.img then can we simply pick up on your instructions from that point??
Thanks for your post. The only thing I think you are missing (for a totally new user doing this) is explaining how to boot into recovery mode when you are ready to flash the new ROM.
There is one other thing that I think would be great to have added to a post like this and that is an explanation of how to restore your programs after flashing a new ROM. Do you just reinstall them or is there a way to restore files and be able to keep your screen looking mostly the same?
Click to expand...
Click to collapse
As far as I know, you just have to reinstall your programs. This guide will also work for loading ROMs other then Freshhh, but some ROMs require you to do a wipe before you install them. Check to see if that specific ROM requires a wipe before doing an install. Yes, I have used this method to upgrade from RA's 1.2.3 to 1.5.2 with no problems.
@_Chris_Kirkland said:
Whats up with the Moto Droid? When are ROMS going to be pushed? and are you going to wright and Guide for Droid like this one?
Click to expand...
Click to collapse
I have no idea about Droid modding, as I don't have a Droid. I'm not to fond of the idea of writing a guide for a phone I don't have because I wouldn't be able to verify that it works with minimal problems.
Alright, I've completed the basics of how to do this. I'll add a problems and solutions section once people start having problems.
great job, this should help folks out a good deal.
That's my intention. Just trying to make things easier for those who aren't so good with the console. I think I'm gonna go ahead and do the Win7 driver workaround now.
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
jfoster38122 said:
In step 8 of the guide I can follow along up to step 8 but when I type in the text I don't see the download option.
Click to expand...
Click to collapse
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a custom rom that I could downgrade to 1.29 or is there something different now?
mark920 said:
So this is probably an obvious question, but I apparently not to me, but is the guide to perform a downgrade for people who have not rooted and flashed their phone? Because I was able to downgrade to 1.29 ruu after having flashed my phone with Fresh 1.0, is it because I flashed a customer rom that I could downgrade to 1.29 or is there something different now?
Click to expand...
Click to collapse
This is a guide to try and simplify patching, but it also covers a section on how to downgrade a phone that Sprint/HTC patched so that the 1.29 RUU method wouldn't work.
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
mark920 said:
How does someone get a phone that was patched by sprint/htc to not allow the 1.29ruu to work on the phone?
Click to expand...
Click to collapse
Ether get a newer Hero, or run the software update in the phone. I ran the software update >_>
abcdfv said:
You're talking about the FlashRec step right?
Could you tell me exactly what you can see?
Click to expand...
Click to collapse
Once I enter the recovery image in, the 2 options are "Flash Recovery Image" and "Restore Backup Image"
There's no download recovery image option.
- JustPyro
It may have been updated since I used it... I'll look into it
EDIT: Click on FlashRecovery image.
Excellent work! I just want to let you know that the link for the RUU 1.29 does not work (at least for me). Great guide though.
Link updated.
The rooting method for the EVO 4G is close to the same as the Droid 2, just recently created by Sebastian Krahmer at http://c-skills.blogspot.com/, but with a little variation.
Here is the step-by-step I just did on my brother's (dwizzy130) EVO 4G that came with 2.2 from Sprint.
I am NOT responsible for any damages (bricking, not working, basically anything that goes wrong) This has been tested and works. Over the next few days, I will be cleaning this post up and making the steps more clear.
Special thanks to:
Sebastian Krahmer for the exploit
dwizzy130 (my brother) for letting me test on his EVO (since I don't have one)
The unrevoked team for their methods
Toastcfh for his mtd-eng.img
Topgun966 over at evo4g.me for hosting the files
djR3Z over at TheDroidDemos.com just made a GREAT video walkthrough that should make this MUCH easier for all of you. He spent a TON of time making it yesterday, so please give him lots of thanks!
VIDEO WALKTHROUGH (2 parts)
Make sure your phone is unplugged from your computer until I tell you to plug it in!
If you already have the Android SDK and HTC Sync set up on your computer, skip to Step 4 now
Step 1: Download the Android SDK here
Step 2: Extract the Android SDK zip. Move the contents of the extracted zip to C:\
Your Android tools folder path should now be C:\android-sdk-windows\tools
Step 3: Download HTC Sync 2.0.40 here
Run the installer. Move on once installed. If reboot is required, do so and then move on.
Windows 7 Users:
Go to your start menu, then control panel. When that is open, (if you are in category view mode) click on "Uninstall a program" and then choose HTC Sync to uninstall. If you are in Icon view mode choose "Programs and Features" and then click on HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Other Windows Version Users:
Go to your start menu, then control panel. When that is open, select Add/Remove Programs, and then choose HTC Sync to uninstall. This will load the proper drivers needed for unrevoked3.
Next,
Download my evo-root.zip.
It contains a few files necessary to root the EVO.
Unzip the contents of the zip to your android sdk tools folder.
Download the unrevoked-forever.zip
Place this zip in your tools folder as well, as a zip, not extracted.
Download this PC36IMG.zip || Mirror(This is the same as running an RUU, so it will delete all of your user data when we use it later in the guide, so backup everything you want to save on your phone first)
MD5: e52f6ec4f8f5fd6dc251ef19ee19750b
Put this zip in your sdk tools folder as well, as a zip, not extracted.
After unzipping the contents of evo-root.zip to your android sdk tools folder and placing the PC36IMG.zip and unrevoked-forever.zip in the folder, move on.
Step 4: Make sure USB Debugging is ON (checked) on your EVO. Go to Settings > Applications > Development > and make sure it is checked.
Step 5: Plug your phone into the computer via USB, Make sure that the connection type in the Notification Pull-Down Bar is "Charge Only", not "Disk Drive" or else this won't work.
If your computer asks you to restart after the new drivers were installed, do that now.
Step 6: Open up a command promt from your android-sdk/tools folder.
Windows 7 users:
Open up the android sdk folder and hold shift and right click on the tools folder. You will see an option that says "Open command window here" Choose that one and you will be set. the command prompt should read something like C:\android-sdk-windows\tools>
Other Windows Version Users:
Go to the start menu, go to All Programs, then Accessories, and click on command prompt. Once open type
Code:
cd C:\android-sdk-windows\tools
Once ready, type these commands in cmd prompt from your adb tools directory. After every line press enter.
Code:
adb push unrevoked-forever.zip /sdcard/
adb push flash_image /data/local/
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb push mtd-eng.img /sdcard/
adb push PC36IMG.zip /sdcard/
Note: the PC36IMG.zip will take longer than expected to transfer to the sdcard. It is a BIG file.
Now we chmod a few things. After every line press enter. It should repeat what you typed in and then return you to a blank line with an $ for everything in adb shell
Code:
adb shell
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
chmod 0755 /data/local/flash_image
Ok now for the root shell.
*
(still in adb shell)
Code:
cd /data/local/tmp
Code:
./rageagainstthecage-arm5.bin
You will now see some text on your cmd prompt screen explaining the exploit.
Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
Once that dumps you out of the shell, type
Code:
adb shell
and you will see you now have a
Code:
#
instead of
Code:
$
now type
Code:
cd /data/local
./flash_image misc /sdcard/mtd-eng.img
that will flash your misc partition with Toast's mtd-eng.img.
This should return you to a blank line with #.
If you get an "Out of memory error" with a huge list of weird lines, here's how to fix it.
Reboot your phone normally.
Open a command prompt and go backwards in this guide until you see the big red * and start from there.
Once it is flashed correctly, move on:
Type
Code:
reboot bootloader
Remember how you pushed that huge PC36IMG.zip to your sdcard earlier? This is where that comes in handy. Once you booted into hboot, Select "bootloader" with your volume up/down buttons and hit the power button. Let it sit for a little bit while it loads the PC36IMG.zip. This can take up to 5 minutes. When it finally asks if you want to apply this zip, choose YES. (Remember, this is the same as running an RUU, so it will delete all of your user data).
If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue.
Once it is finished, select restart. You now are on the stock 2.1 build of Android.
Next step, mount your sdcard on your computer, and delete the PC36IMG.zip from it. This is because the next step requires using hboot, and you don't want to sit and wait while it loads up again, just for you to say "no" to the install. Please follow this step, for it saves 5-10 minutes of waiting ahead.
I worked extensively with Matt Mastracci, so this rooting guide will use the unrevoked method to root 2.1. This is what worked for me testing on my brother's EVO, so if you do end up trying something else to root 2.1 with, PLEASE do not post it here or ask questions, for I will only support the unrevoked team.
Now open up your web browser on your computer and navigate to Unrevoked
Choose the correct operating system to download for.
*
Make sure you install the modified android usb driver that comes with the unrevoked3 install (see the html file included when you extract the exe)
Once downloaded and extracted, run the program on your computer.
Make sure your EVO is plugged in with USB DEBUGGING ON!
It will reboot to the bootloader, and it will wait for you to use volume down to select HBOOT USB. (the last option)
After you have selected it (by pressing the power button) let the unrevoked3 program handle the rest of the flashing.
If you have had any trouble with the bootloader freezing or not moving for over 3 minutes, you most likely forgot to uninstall HTC Sync (as directed at the beginning of this guide), or you need to install the modified hboot drivers that come with the unrevoked3 program, OR a nasty combination of the both.
For the modified drivers and explanation on how to install them, open the "hboot driver.htm" file that gets extracted when you extract the reflash_package.exe. It will explain everything. You will have to reboot your phone after you install the drivers. Once you have repaired this go back to the big blue *
As soon as it is booted into recovery, you are done with that.
Next in recovery go to
Code:
install zip from sdcard
then
Code:
choose zip from sdcard
and choose the
Code:
unrevoked-forever.zip
This will flash the unrevoked forever hboot unlock.
_____________________________________________________________________
Part 2
Note: This section would not have been possible without the amazing testing and help of cilio87. He earns a gold star *
Now it's time to finish up the process and flash the stock 2.2 build of Android. You need to do this before any custom ROM in order to re-update the partitions we downgraded in the rooting process.
Step 1: Download either the update zip with
ClockWorkMod recovery included
or
Amon_RA's recovery included
This is the most up-to-date version of Amon_RA recovery that allows you to back up WiMAX partition.
(Either zip contains the final touches to the root process, one flashes clockworkmod recovery, and the other respectively, Amon_RA's recovery)
Extract the 3 files inside the zip to your desktop.
If you are still in recovery (from part one or the guide) go back to the main menu of recovery on your phone (if you aren't already at the main menu, hit vol up & down at the same time) Select
Code:
Reboot System Now
Let the Rom load, and when it gets to the sign in screen for Google, just skip everything and let the ROM boot.
If you are already on a custom rom, boot into it and follow from here.
Once It is fully booted, mount your sdcard onto your computer, and copy the 3 files you extracted from the zip to the sdcard.
Once copied, Unmount your sdcard from the computer.
Step 2: Unplug your phone from the computer. Power it off completely. Now while holding VOLUME DOWN turn on the phone with the power button, continuing to hold volume down. This will boot into hboot. You can release the buttons once you get to the hboot menu. Then use the power button to click on bootloader. This will scan the sdcard for the new PC36IMG.zip you just copied to the sdcard. When it asks "Do you want to start update?" Hit Volume Up for Yes. It will reload the zip and then start the flash. Once the flash is complete (may take 5 or so minutes) Choose NO when it asks you to reboot.
Step 3: After choosing NO to the reboot, you will see a menu again. Select Bootloader from the menu, then use the Volume Down button to hover over "Recovery" and press Power to click on it.
If your phone gets stuck at the White EVO 4G screen, pull your battery, and then power on while holding volume down again. It should boot to the bootloader again, where you can select recovery.
Once you are booted into this custom recovery, go to
Code:
Install Zip from sdcard / Flash zip from sdcard (Amon_RA)
and then (clockworkmod only)
Code:
choose zip from sdcard
You will then see the 2.2-root.zip. Click on that and accept the flash.
Once that flash is complete, return to the main menu of recovery and Select
Code:
Reboot System Now
You now have stock Android 2.2 with root and all updated partitions!
If you would like the flash_image binanry so you can flash new recovery images quickly from adb shell, flash the zip that is attached below as a normal zip in recovery AFTER you have completed this entire guide.
IN ORDER TO FLASH CM6 OR DAMAGE CONTROL, YOU NOW NEED TO FLASH THE ENG SPL. LOOK FOR IT IN THE EVO 4G ANDROID DEVELOPMENT FORUM.
Here is the ENG SPL
Good Luck!
Dan Wager
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Yes! I look forward to the rest of your post
Sent from my PC36100 using XDA App
Great news everyone!
Eagerly awaiting.
Awesome xD
Sent from my HTC Evo 4G using XDA app.
Oh thanks! Gonna be watching this all night! This is gonna be AWESOME!!
Vandam500 said:
Finally no more people asking about it
Click to expand...
Click to collapse
if only you were right...
I love the xda forums, good job to everyone involved, another reason I love my evo.
Sent from my PC36100 using XDA App
I wish I didn't just take my xanax. Ughhhh
Vandam500 said:
Awesome! Good job on everyone that worked on it. Finally no more people asking about it
Click to expand...
Click to collapse
I'll add with another question that will "end"
Will this allow me to have PRI 1.40?
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Details---
I've heard the process is more than a simple click like simple root or unrevoked... But at least we have root.
It will be nice to see the detailed failsafe guide so I don't go around bricking phones and hopefully an automated prog is made to make it a breeze.
A great help!
Having a B-day tomorrow, and have searched the month of August for a complete method to root my froyo 2.2
Thank you in advance for your expertise and assistance..
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Thank you
OMG you guys are the best devs ever ill be stuck to this like glue once again XDA is the best forum on the planet.
edufur said:
well, i followed the droid2 guide and it worked all the way up to giving me the # sign... but the cp commands are failing. but since i have #, can i just run unrevoked 3.1 at this point? or do i need to succeed in the entire driod2 tutorial?
Click to expand...
Click to collapse
no, once you get to that point you have other stuff to do.
just wait til the guide comes out... We've waited how long for this thing? an extra hour or so won't kill you. (hopefully)
Yeah, almost done writing the guide. Try not to give out anymore details yet, I should be posting the full guide shortly.
sprink0281 said:
Stop with the irrelevant posts! We don't need a hundred pages of nothing! Start a thank you thread if you want! Leave this one for the op and instructions and the files! Makes things easier for everyone so we don't have to go thru hundreds of posts to piece together relevant information!
NOTICE THE TITLE OF THE THREAD IT SAYS GUIDE LET IT BE JUST THAT!
Click to expand...
Click to collapse
And your message is wholly important? Yes, the title says "guide" but that means that the original post will contain the guide. This is a forum, not a wiki. (I know my message doesn't help at all either)
Hooray, root on 2.2!
please make it easy for us newbies too please
Greenfieldan said:
please make it easy for us newbies too please
Click to expand...
Click to collapse
I'm getting the basics out tonight and will make it an easy read like my Hero rooting guide tomorrow sometime, because I am exhausted tonight.
So I just wanted to make a short tutorial for anyone who has broken their screen and was unable to perform a backup before it happened. I recently broke my screen and through a few hours of research I've come to a final conclusion on how to get what you want from the sdcard. So I know most of you are probably running a touch based recovery which I'm sure is useless to you if your screen is busted. So without further ado, let me show you how it's done. I tried this with my main recovery TWRP MultiRom and it wouldn't work and it wouldn't work with normal TWRP or CWM either. I'll suggest a recovery in the tutorial.
What You'll Need:
WugFresh Bacon Toolkit *This program downloads all main dependencies for you*
Philz Non-Touch Recovery *This recovery provides navigation via volume keys and power button*
Fast ADB/Fastboot Installer *Installing system-wide makes this easier*
Any USB Cable
Step 1: Run the Adb/Fastboot Installer. Like I mentioned, installing this system wide makes backing everything up much easier and you'll see why later on. I also recommend the driver installation it provides.
Step 2: Power phone completely down and boot into fastboot. Volume Up+Power. Once you're on the fastboot screen, plug your device into your computer.
Step 3: Start the WugFresh Bacon Toolkit. It will ask you about your device and what rom you're using. For this process I chose Arry Build Mode at the bottom of the list.
Step 4: In the Bacon Toolkit, go to options then to the custom recovery tab. Click the bottom option for Alternate Custom Recovery. Click browse and select the Philz Recovery you downloaded earlier. Click Apply.
Step 5: On the bottom left of the Bacon Toolkit you'll see an Advanced Utilities button. Click it.
Step 6: Once Advanced Utilities is open, look to the top right of the new window you'll see some options under Fastboot Boot. Click Custom Recovery and follow the prompts until your phone boots into the selected recovery.
Step 7: On your PC create a folder to store your data after it's pulled. I created mine on my desktop and called it Android Pull. Now open that folder and Shift+Right click in an empty space. There should be an option in the list to open a command window there. This simply opens a command window that is already based off the current folder. Once you have it open type in "adb devices" to ensure your device is being seen. It should show a device ID and show it's in a recovery state.
Step 8: Type in "adb pull /sdcard/" and it should begin pulling everything off the device. Depending on how much you have on the device this could take ages, but the control panel window will show it's done by giving you the option to submit another command. Also, if you know all of your file locations you can simply pull the folders you need instead of all of them. I just found this to be an easy way to be sure I didn't miss anything.
I don't usually do tutorials as I'm more of a lurker around here so I apologize if my tutorial seems nooby. I just didn't see any solutions for my problem and when I found one I wanted to share. I've always lost data when I retire my broken phones, but I have a son now and I couldn't let the pictures just disappear forever.
I hope I helped someone out today if they're retiring their OnePlus One due to high repair costs.
ps: Hate me but I moved to a Blackberry P9982 because of this cracked screen. No more #androidmasterrace for me for the next few years.
Hey fellow Ematic EGP008 Tablet owners! This is an fairly easy tutorial on how to install a custom recovery and root your tablet! As always, there is a slight risk of "bricking" your device. I take no responsibility what so ever.
Note: This was tested on my personal Ematic EGP008 tablet, which uses the Rockchip rk3066 chipset. It may work on other devices using the same chipset, but no guarantees. If this your first time doing something like this, please use the XDA Forums (or Google) to do research or ask if there's no answer to your question.
Now, lets begin! We will need the following items:
* The Device
* A good working USB cable
* A computer with Ubuntu OR Ubuntu in a virtual machine
* Download "android-tools-fastboot" & "android-tools-adb" from Ubuntu package manager
* Download rkflashkit https://github.com/linuxerwang/rkflashkit
* Download ClockworkMod: http://crewrktablets.arctablet.com/?wpfb_dl=682
* SuperSU: https://forum.xda-developers.com/apps/supersu
If you have everything listed above, we can continue. First, if you haven't backed up your personal data (pictures, music, SMS, contacts, etc) from the device, now would be the time. Then, when you are ready, have your device on and plugged in to your computer's available USB port. Have your device's USB Debugging enabled and it should be plugged in to an external power source (NOT running on the battery alone).
Now, before we get going, we'll need to do somethings. Take the compressed file you downloaded called: rkflashkit-master.zip. Extract it somewhere you'll remember. Open that extracted folder and open a terminal in that directory (usually right-click) and type: "./waf debian" (without the quotes). It should create a new file: rkflashkit_0.1.5_all.deb. You can close out that terminal. Install this package and then launch it from your menu launcher. *Note: Make sure you have installed "python-gtk2." When launching rkflashkit, it will ask you your password; type your password in and hit enter. You will now see a window with no device information. That's OK, just leave that window open.
Now were ready to get the device ready for flashing. Get terminal running. Type in: adb reboot-bootloader . The device should now reboot into "bootloader mode". In the case with my tablet, the screen remains black. That's normal. Check the rkflashkit window... it should now show an available device and the dialog window (to the right) should have some basic information in it. *Note: It is HIGHLY recommended to backup ALL partitions before flashing ANYTHING!* When your finished backing up everything (again, recommended), click on the drop down arrow under "NAND Partitions" label and select "Recovery" (with some numbers/letters behind it). To flash the image that you downloaded (Oma_RK30_3.0.36+_CWM_6.0.3.1.7z), extract it (anywhere). Then head back over to the rkflashkit window and click the "Choose" button. Browse for the "recovery.img" file (you may need to back out to root ( / ) and navigate to the "home" folder and then your profile name to find it). Once you found it, highlight it and click "OK". *Make sure you are flashing the RECOVERY partition* Now just flash the image by clicking "Flash image". It will ask if you what to do this; click yes. It will flash the image and then verify it. The dialog box will let you know when the operation is done. To continue on with rooting the device, click "Reboot Device" (do NOT disconnect anything at this time).
The device should have booted into the operating system without any issues. Now we need to install SuperSU to give us root privileges. Mount the device as storage so the file we need can be copied to it. Copy the file you downloaded (it's a .zip file) from SuperSU on XDA to the root directory of the android device (do not extract it... leave it as is). Turn "off" storage once the file is copied over (but still leave the USB cable plugged in the computer). Return to your terminal (for adb commands) or start a new terminal. Type in: "adb reboot recovery" (without the quotes). Hit enter and the device should reboot into recovery.
The new recovery you just flashed a little while back is touch-compatible (drag your finger up or down and use the power button to "enter" sub-menus OR use a USB keyboard hooked up using an OTG adapter). Before beginning, it is wise to make a backup of your system (in case you need to restore it); scroll down to "Backup and Restore" and press the power button briefly (or enter on USB keyboard). Then select "Backup" and let it do it's work. When it it finished backing up, select "Install zip from sdcard" from the main menu; then choose "choose zip from sdcard". Scroll till you have highlighted the SuperSU zip that you copied over from the computer. Press the power button (or hit enter on USB keyboard); it will ask if you are sure you want to install this zip... scroll down to "Yes" and press the power button (or Enter) again. It should install without errors. Now navigate back to the main menu and reboot the device.
You should now be rooted! Double check that SuperSU is installed and use a root checker if in doubt. Now you can start using apps that need a rooted OS and debloat your stock system (BE CAREFUL... REMOVING THE WRONG APPS COULD LEAVE YOU WITH A SEMI-BRICKED DEVICE or NON-FUNCTIONING OPERATION SYSTEM). Have fun! Let me know how things went and even though I'm not a developer of any kind, I will try to do my best to help anyone. I'm not always online (I have a life, you know ), so don't take it personally if I don't reply in a timely fashion. Now, go enjoy your newly rooted device!
I would like to thank the following for making this tutorial possible:
- Crew RKTablets: Custom Recovery
- SuperSU Release: SuperSU rooting tool
- linuxerwang: rkflashkit tool
- Canonical Ltd.: Ubuntu Operating System