Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
Keep in mind this is experimental and not exactly publicized as a feature of ICS, so don't count on this as your only method of backup!
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
1. Connect your device via USB, and open a command prompt.
2. Optionally, type the command 'adb devices' to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
There is a command, 'adb backup' (to be detailed shortly), that will now allow you to create a full system backup.
The command parameters format is:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use* is simply:
adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
* This may not work for every setup. If you get an error such as "adb: cannot open file ./backup.ab", use:
adb backup -all -f C:\backup.ab
Click to expand...
Click to collapse
Or substitute the path of your choice in place of C:\.
To explain the parameters:
-f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
-apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
-shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
-all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
-system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
<packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
adb backup -apk -shared -all -f C:\backup20111230.ab
Click to expand...
Click to collapse
4. You will see a screen like the following:
{
"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"
}
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you will get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your phone returns to the home screen.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
adb restore C:\backup20111230.ab
Click to expand...
Click to collapse
replacing 'C:\backup20111230.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE 12/31: Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
NOTE 06/12: There seems to be a bug in which backup and restore operations will fail unless a desktop backup password is set under Developer Options. It will not work with a blank password.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Kevin
In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.
faizalmzain said:
In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.
Click to expand...
Click to collapse
Interesting. They must have deemed it not quite ready for primetime yet. Seems like it should show up in a future version sometime in the not-too-distant future, then. Until then, this seems to work pretty well.
I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.
RogerPodacter said:
I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.
Click to expand...
Click to collapse
While that's true, if you're already past the point of painful return, why start over when this backup method is available? It's not a question of if it works (it does work).
my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?
sahakiap said:
my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?
Click to expand...
Click to collapse
Yes, as shown in the guide, just use the 'adb restore' command after unlocking the bootloader. You may wish to backup your Internal Storage manually, just to be safe, and backup your SMS with a third party app, if you care to keep them. Obtaining root isn't covered in this guide, but yeah, you can root it once you've unlocked the bootloader.
I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?
ktulu029 said:
I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?
Click to expand...
Click to collapse
Interesting. Could you post the exact command that you used, and also what OS you're running?
copkay said:
Interesting. Could you post the exact command that you used, and also what OS you're running?
Click to expand...
Click to collapse
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64, and my phone is running 4.0.2 if that is useful information.
It runs everything on the phone like prompted, just doesn't save any data.
ktulu029 said:
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64
Click to expand...
Click to collapse
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?
Wow, this should be a freakin STICKY!!!
copkay said:
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?
Click to expand...
Click to collapse
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.
ktulu029 said:
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.
Click to expand...
Click to collapse
After allowing the backup, did you get a Toast saying "Backup Started"?
I do. And shortly after, maybe 5 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.
ktulu029 said:
I do. And shortly after, maybe 10 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.
Click to expand...
Click to collapse
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.
copkay said:
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.
Click to expand...
Click to collapse
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.
ktulu029 said:
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.
Click to expand...
Click to collapse
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.
copkay said:
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.
Click to expand...
Click to collapse
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.
ktulu029 said:
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.
Click to expand...
Click to collapse
The versions might matter, but you're on the same revisions I'm on. Now, I will say that I am running from C:/Program Files(x86)/Android/android-sdk/platform-tools/ rather than just the straight C:/ prompt, just because I've been too lazy to add ADB to my system variables. I'm also using MTP, which shouldn't affect it.
Yeah, things have changed quite a bit; going from the Droid line to the Fascinate was my last jump.
The only thing I can think of to try is to make sure that you are running your Command Prompt as Administrator. The fact that it's creating a file at all seems to disprove that this would have an effect, but it's worth a try.
i rooted my " sgs2 SGH-T989 " Yesterday and as i was learning more things on this website i found out that i need to do a EFS Backup to stay out of trouble "but i m in it right now " ..so i downloaded the app ( hc-ktool ) used it and this is what it gave me after doing a backup check :
checking current efs backup.....
/sdcard/efs.img found
-------------------------------
mount returned: 255
(unable to mount image-image corrupted?)
/!\ nv_data.bin NOT FOUND in backup!!!
/sdcard/efs.tar.g2 Found
-------------------------------------
/!\nv_data.bin NOT FOUND in backup !!!
plz what to do now , i tried the other methode but i keep getting this "busybox : permission denied"
any help ?
1- are you rooted?
2- why do u need to mess with EFS? I really see no reason to do so at all
what do u mean by u r in trouble right now? is your phone still functioning normally?
thanks for responding, my sgs2 i rooted and i have done a cwm backup and also a titanium backup too, i just wanted to backup my EFS folder too as i heard many people having problems with EFS folder becoming corrupted with the use of some ROMs....so to do the backup i used ’ hc.ktool ' backup did not succeed and phone now is doing all kind of bizar things. .....turns off with just pressing power button for 2 seconds with no meneu showing...lost my contacts ....lost my lockscreen....phone freezez sometimes....but i still have the right EMEI number !! my phone is just rooted still with stockRom.
i think the hcktool messed up my phone is there a way to undo or go to previous state before i used the hcktool ?
any help is welcomed phone is only 3 months old
Read this
http://forum.xda-developers.com/showthread.php?t=1438451
thanks xcrazydx
i should try that too, i ll give it a shot tonight, but as one of my friends advised me, i did a " dalvik cleanup + fix permissions " and It seems to have fixed both the lockscreen problem and the power off issue too...( to be honest i have no clue what dalvik clean up & fix permission do exactly to the EFS Folder if anything at all !! but i still have the screen freeze happening every now&then plus some apps forceclose " like opera browser, was using it when suddenly shut down for no reason " still having issues with busybox also
i still dont now if my EFS FOLDER is corrupted or not " my IMEI number is still the same thow...I JUST DONT GET IT ALL THIS HAPPENING AND I M STILL AT STOCKROM DID NOT FLASH A SINGLE ROM YET !!
i hate " hc-ktool"
Forum:
If this specific question is in another thread, please forgive me and redirect me.
If not, any instruction would be greatly appreciated.
Equipment:
Visual Land, Prestige 7
Model # VL - 107
ICS 4.0.3
Baseband 1.0
Kernel 3.0.8+
Build # 86F5-D1-H1-MO1-1718.20120327
Objective:
To create a backup/recovery img/dump of the existing stock ROM, without having to add "clockwork", "cynogen", etc...
Software on Hand:
Windows 7
Livesuit 1.09
Virtualbox
Ubuntu via Virtual Machine
Please detail everything and speak to me as if I were a little child...
Thanks in advance!
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Can this be done with ADB?
ruscan.calin said:
I'm sure you have a recovery on your phone that's a tool to create a backup of stock rom on your sdcard
enter recovery (usually volup+menu or something like that) or you have some options in phone menus to backup device
that will create a set of img files on sdcard that's your backup also you can restore your phone from this backup if you get in trouble
so it's a good idea to have one !
Click to expand...
Click to collapse
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
gth826a said:
That's a negative...
The tablet is completely stock - straight from the box.
In turn, I do not have a recovery (such as clockwork, cyanogen, etc.) that would allow me to make a backup img.
And, I would like to start/learn by making a backup img without such a recovery; i'm assuming this requires using ADB.
Therefore, I need detailed instructions on how to create said backup img...
I have not found any settings or options in the tablet itself that performs this function either.
Click to expand...
Click to collapse
I understand now this is a tablet so it's common problem for some
well you have to find a way to root device to get access to system files then use a rom dumping tool just take a look here or here
nobody can tell you for sure how to do that this is device specific I do not know to much about that particular tablet just try
I just got this tablet today, and it's rooted out of the box.
Not sure if that helps you, but I wanted to contribute if I could.
[signature]
Recovery for Galaxy Ace 2 - i8160
Hi,
Any chance of a simple recovery for the Galaxy Ace2 i8160 ?
VL107 Update Down To 4.0.3/4.0.4
Hello,
I've been trying to figure out how to change my VL-107's OS, and a Recognized Contributor pointed me to this thread.
I've downloaded LiveSuit, but I can't figure out how to make it work. If at all possible, I need two things: an .img file for 4.0.3 or 4.0.4, and instructions on how to apply this update via command prompt or a program that utilizes command prompt.
I have Windows 8.1, my VL-107 (Visual Land Prestige 7), and LiveSuit (which I'd really rather not use).
The only experience I have in flashing involved using command prompt, and I'm much more comfortable doing this than relying on a program to do everything "behind the scenes". Otherwise, I would also be willing to put an .img file on my tablet's "SD card" and apply the update through Recovery mode.
Hello everyone, today while trying to do backup in twrp, I am continuously getting the error message as "createTarFork() process ended with ERROR: 255
Backup Failed.". I tried some solutions mentioned in the forums, but they seem to be having error with different folder. In the log I found that there is error in opening webviewgoogle, but I couldn't found that folder anywhere.
Invalid encryption mode 'ice:aes-256-cts'
Backing up System...
Invalid encryption mode 'ice:aes-256-cts'
Error opening: '/system/app/WebViewGoogle' (Structure needs cleaning)
I:Error in Generate_TarList!
Error creating backup.
I used codeworkx and Blu spark twrp and both seems to have the same issue. Kindly help me in doing a backup. Thanks in advance.
I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???
Princeland said:
I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???
Click to expand...
Click to collapse
I just skipped the back up and did format the data and clean installed the ROM and it worked. Earlier I was unable to restore due to mount system error but I just clicked the system in advanced->mount in twrp and restore the old backup...
Try deleting all paralell apps under the apps Section
galaxy s4 nutjob said:
Try deleting all paralell apps under the apps Section
Click to expand...
Click to collapse
It's not related to parallel apps. I checked this one already.
I had this problem a couple weeks ago:
So the first thing you do to fix the system partition not mounting is to download this tool: https://androidfilehost.com/?a=show&w=files&flid=38683
Tool looks like this: https://i.imgur.com/04L1h9b.png
Step one: Install drivers. Should be straightforward.
Step two: Make sure you device is connected. It detects it in fastboot and everything just press the refresh button a couple of times. In this case you're best off starting in fastboot mode.
Step three: Erase all data / Decrypt internal storage. https://i.imgur.com/2HZN1jK.png
Step four: Flash twrp. Make sure to select your device in the dropdown list. Then select recovery flasher and flash the one shown in screengrab. https://i.imgur.com/80N32db.png
Step five: reboot into recovery and flash what ever you want.
This tool is extremely usefull and quite timesaving. Make sure you explore it's features.
Note: I do not own the tool nor do I know the dev.
Happy to help
pinnekeshaar said:
Step three: Erase all data
Click to expand...
Click to collapse
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.
lockywolf said:
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.
Click to expand...
Click to collapse
Well I guess you've been right on time with your part of the advice. You know, three months later. Also, some people have brains and can think of the fact they need to backup their stuff before deleting everything.
Three months later I found this thread in Google.
And also, just in case, the thread is exactly about making backups.