Related
I found I was repeating myself a lot when helping out people new to rooting their Evo. I also found that this knowledge I'm putting into this doc doesn't really exist in one place, but is spread throughout the entire Evo Forum. So below is some information to help out people with backing up their device, some backup tips, some general information on flashing, and tips and best practices for flashing. Hope this helps!!
Assumptions:
This guide assumes you are fully rooted at this point. If not follow any one of the guides in the Wiki that has been stickied on the main page of the Evo Dev forum. My personal recommendation is the Unrevoked. Very easy to use, just read up and make sure your phone is compatible.
To test root type "su" into a terminal. You should get a "#" back. You can use a terminal emulator from the market or ADB. To get ADB up and running follow this guide here. If that seems confusing than take a look at this guide I wrote for Notion Ink Adam Tablet users here. That guide is for Windows users, but Mac and *nix users shouldn't be much more difficult.
Backing up
NAND Backup:
Once rooted you can use the app quickboot to boot into recovery to do a NAND backup. If your ROM doesn't have this app installed, download from Marketplace. Open app and choose "Recovery". Once into your recovery use the volume buttons on the side to scroll up and down and power button to select to get to the option to backup. I have clockwork installed so my screen looks different, but you should be able to find the NAND backup option. This will take awhile so be patient.
Once done you can reboot and continue on as normal. This is an essential step (or using Rom Manager below). If you ever screw up something major or you try a new ROM and want to go back, this will allow you to restore easily and get back to a point where things worked fine. It would also be highly recommended to do one of these backups before doing something major that has potential to break things. Use best judgment here.
Rom Manager:
Even easier than the above is to use Rom Manager. Download it from the marketplace, run it, and let it update your recovery image for you. Once this is done go to the bottom of this app and choose "Backup Current ROM" This should do a full NAND backup. I would recommend buying this app for the other features it has, but it is up to you.
Titanium Backup (TB):
Once you have your NAND backup I would also recommend installing Titanium Backup from the Marketplace (I would also pay for the license because you get better performance and the dev deserves some green for this awesome app!). Once installed open it. The first time it will ask you to update Busybox. Let it and wait for this to download. When done it will ask you reboot app from the notification area. Do this and then wait for app to fully load, two messages should appear, the second one indicates it is fully loaded. Then hit menu and go to the batch section. Choose " Backup all user apps + system data".
This will backup everything on your phone for you to your SD card. This will take a while so go get some coffee and check back in. Do not close the app or turn off your phone, the screen can go blank and you can let it sit, but it will need time to run. I think when the screen turns off it puts an icon in notification that should be updating the progress of the batch. Once done, it should tell you in the notification area. For me it takes awhile with my 228 some elements I'm backing up. Your mileage will vary.
SMS/MMS
I recently came across a thread that mentions using Handy Backup for backing up SMS/MMS messages. I have not tried this app or used it so I don't have any directions to give on it. But I have had people ask and I have seen folks ask in other threads. So if TB doesn't give you enough, try this one too.
Backup to Computer:
I'm still looking for a better method for this one. I'm sure someone has something and if you do please let me know so I can update this section.
Currently I backup files and folders to my local NAS at home after major changes. Incremental changes I let TB handle. This is just a simple process of setting the SD card to storage and copy/paste. Works fine and I have only done this once so far after everything was set to my liking.
You might wonder why this important? Well if you are going to play around a lot with different ROMs and constantly read/writing info to your SD card, it is important because SD cards are not perfect. They can be corrupted and can fail from too much writing of info. It usually takes a lot of work to get one to the point of failure, but I managed to do it with my HTC Mogul so I can vouch that it can happen.
Important folders on SD card:
- /sdcard/clockwork/backup
This will get all backups performed by clockwork. If you grab the entire clockwork folder then you will get ROM downloads and such too. I don't really recommend this as it never takes more than 25 minutes for me to download any image. Plus with a secure NAND backup, you can always restore quickly.
- /sdcard/nandroid
This should backup the folder used by AmonRa recovery.
- /sdcard/TitaniumBackup
Folder used by TB for backing up of apps.
Of course throw in any other folders you deem important. What that is depends on you. Making a backup of everything else probably wont take long too. For me I rarely have more than 7gb of data on my card so backing up takes roughly 30-50 minutes.
All of this may seem like a lot of work, but once done you will have a robust system in place. And will allow you the opportunity to safely play!!
Restoring
Restoring is a simple process but can be time consuming. To speed things up you can pay for the full version of TB, which I highly recommend.
TB
Follow the directions below for what I do after flashing. If you have already read that and are ready to restore then do the following...
Open up TB and let if fully load, you will get two small popup messages. The second one means that TB has fully loaded the OS information. Then hit the menu key and choose batch. Scroll down and look for "Restore all apps with data". Run this batch to restore everything. Keep in mind if you backed up everything and are now changing ROMs that you might run into problems. I have yet to run across issues, but this is just an FYI. Also another reason to have a full NAND backup with Rom Manager. If you run into too many problems just restore with it and problem solved.
Restores and backups take awhile with TB, but are worth the wait. Once done with the full restore you can then do incremental backup and restores in the future.
Also don't forget to open up the apps after restoring and make sure the apps are setup how you want. Then double check with TB to make sure things are fully backed up, just click "Backup all new apps & newer versions". Once done with this reboot.
After a TB restore always reboot. After the reboot go into Rom Manager and NAND backup following the steps above in the backup section. This will ensure you have a full system backup with the settings you want.
Rom Manager
This one is pretty simple. Just open Rom Manager and choose "Manage and Restore Backups". Then choose your backup to restore. If you named the files by date and time you might have to do some guess work, but you should have a rough idea. Once you click the one you want just sit back and wait.
Flashing Tips and Problems
Watch Girls Gone Wild for help with this...
Many people have asked "Why flash custom ROM" or "What are the advantages"? Well I think one of the biggest reasons is performance gain from phone and apps. But for Evo users the number 1 reason should be better battery utilization. This can mean you see same amount of battery life, but with increased phone and app performance, or same performance, but longer battery life.
I think some people might be hesitant because it was one hell of a process rooting their device. Well to those people I say, you are over the mountain now. The hard part is done, flashing is relatively easy. I recommend doing it cause stock can cause some people minor issues and your are missing out on a lot of cool and useful customizations. And if you backup your phone as detailed above, you do not need to worry about losing anything.
Stock ROM with Root (back to defaults) or Completely Unroot:
To flash a stock ROM with root, download one from the wiki of ROMs. Then follow advice in below sections for flashing.
To unroot (This is the "I need to take my phone to Sprint" conundrum...) Follow the wiki link. Or go to HTC's website. Then go to the support section for the HTC Evo. Download the file from them and run it. You will be good to go. And if you followed the backup section above you do not have to worry about anything. Just re-root when you get your new phone or old phone back. And restore.
Also, I recommend taking out your SD card with all the root files on it. No need to bring this up or have to explain things any Sprint tech could easily see. Also if you used Unrevoked Forever you should follow this unroot guide here.
I Just Flashed with no Backups:
Below is what I did before I had Titanium Backup in place and after flashing a custom ROM...
Once booted right after flashing I make sure things look fine, fully sync to Google, then reboot. When I come back from that I turn on WiFi and go to Marketplace and Download section. Any apps I previously downloaded will be in that section waiting for me to download. Download them all at once, DO NOT leave that section before downloading everything, or you will lose that list and it will only show apps currently downloaded and installed.
Once done, open apps and customize to liking. Then download Rom Manager if you don't already have it and follow the above section. Once done with that follow the above section on Titanium Backup. Then enjoy your custom ROM.
Flashing in general:
ALWAYS make sure your battery is at least 50% full. The last thing you want is your phone to die on you in the middle of flashing.
Use Rom Manger and pay for the full version. It is a lot easier and can remove a lot of headaches and problems. If you really want to do it yourself you shouldn't have any problems, this is typically what I do and I haven't run any issues that couldn't be solved yet.
Follow the above backup guides before flashing another custom ROM. Save yourself time and trouble. Also I have read about people using NAND backups to sort of switch between different ROMs. In the short term that shouldn't be a problem, but long term that can make your SD card unstable. Make sure you follow the above section for backing up your SD card to computer.
If changing from one ROM to another it is best practice and almost always recommended to wipe data and dalvik cache. This also will alleviate many issues people run into. And if you follow my backup recommendations then it shouldn't be an issue to do either of these.
If not using Rom Manager, then put the zip of the ROM you want to flash on your SD card, and DO NOT unzip the zip file. Leave it on the root of your SD card as a zip file. Boot into recovery if you are not there already. Find the option to flash from SD card. Then choose the zip file or ROM you want to flash. Wait for everything to flash, then reboot using the option from the recovery menu. Wait for phone to boot. This can take a long time after flashing any new ROM so be patient.
Some ROM devs have other items you can add to their ROM. Follow their directions for flashing those items. Some devs want you to boot first than go back and flash, others allow for you to just start flashing right away with no waiting. Pay attention to the directions on your ROM thread. If you screw something up, try flashing the package again. If things look worse or it didn't work, re-flash your ROM or restore your backup and try again.
Otherwise, flash the ROM following directions above, flash the other packages and themes and items you want, and reboot. All should be well.
Once booted up follow guides above for backing up or restoring. Otherwise if you have problems look below before asking questions. If you can't find it here try searching before asking questions. If you still can't find it feel free to ask for help, but keep the question in the thread for your ROM you are flashing, or if you think it is a rooting issue, in the thread of the root process you followed.
Bootloop Issue:
This can be caused by a few things. For one, make sure you wipe data and dalvik cache before flashing a custom ROM. Even if the dev says it is not necessary do this before flashing a new ROM. It can help with these issues. The only exception here is if you are updating to a new version of the same ROM and the dev says there is no reason to wipe in between...
Also you can experience this if you are not fully rooted. Look toward the top of this guide for rooting advice.
Sometimes the ROM can take a while to boot after flashing a new ROM. Be sure you really do have a stuck boot or bootloop before doing a battery pull and troubleshooting. Give it some time to see if it fixes itself. If you are waiting over 30 minutes for something, you probably do have a legit issue.
Exclamation Point with Android Guy Screen
I got this when attempting to upgrade once. To get out of it, battery pull and put battery back in. Hold down "Volume Down Button" and then press power. KEEP HOLDING DOWN volume down button till white screen (Hboot) appears. Release volume down button. Wait for it scan. If it finds your PC file choose no and also no on reboot. NEXT CHANCE YOU GET remove, rename, or move the PC file from the root of your SD card. Choose "Recovery" from menu using volume buttons and power button to select. Once in recovery, choose flash from SD card and choose your ROM.
If you cannot find an image or do not have one, just go back and toggle USB. Then copy paste ROM to SD card. Keep in mind that you might need to wipe data and dalvik cache before flashing as mentioned above.
Another user commented this screen appeared when attempting to go into recovery from Quickboot app. This might mean the recovery image didn't install correctly, or could mean you do not have a recovery image flashed or installed. If this is the case, follow one of the guides in this wiki link to flash a recovery.
If you need to get out of this screen, just do a battery pull. Your ROM should boot up fine.
Battery Issues After Flashing:
Some have claimed issues with battery after flashing. To try recalibrating click here for Cyanogen's guide.
That's all for now!
I'm sure there is plenty more to add to this down the road, but for now this is all the dumping my brain can handle. Leave comments and suggestions and let's make this a strong guide with the right information to help those in need.
Very nice, hopefully you just saved someone a lot of heartache
Just added a section for un-rooting. Can someone please help me verify this is correct.
Thanks!
Awesome guide!
Thanks for the info in the Simple Root thread.
One question that was unanswered (and per your response I ask it here):
Are SMS/MMS info backed up using Nandriod or Titanuim??
I'm a little confused by which can do this.
Thanks again for the help.
ucf.elk said:
Awesome guide!
Thanks for the info in the Simple Root thread.
One question that was unanswered (and per your response I ask it here):
Are SMS/MMS info backed up using Nandriod or Titanuim??
I'm a little confused by which can do this.
Thanks again for the help.
Click to expand...
Click to collapse
Very good question on SMS/MMS. I think I have noticed that when using Handcent SMS app for sending and receiving SMS/MMS messages they are somehow backedup. I think Handcent has a folder on the SD card.
Otherwise if you are using stock messaging app, I am not sure it TB backs that up or not. If you want to verify this for me and let me know your results I would be happy to update my guide.
webs05 said:
Very good question on SMS/MMS. I think I have noticed that when using Handcent SMS app for sending and receiving SMS/MMS messages they are somehow backedup. I think Handcent has a folder on the SD card.
Otherwise if you are using stock messaging app, I am not sure it TB backs that up or not. If you want to verify this for me and let me know your results I would be happy to update my guide.
Click to expand...
Click to collapse
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
epmacman said:
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
Click to expand...
Click to collapse
Great info! Thanks epmacman and thanks webs05 for the great guide!
epmacman said:
Just wanted to say thanks for the breakdown, and with my experience Tb has backed up my sms when backing up "all system data and apps"
Thanks again OP
Click to expand...
Click to collapse
Were you using stock messaging app? Or a third party one from Marketplace?
Thanks for the information. About to start this whole process soon so this really helped Just a quick question though, do classes of the sd card matter? Have a class 2 card atm but about to buy a 16gig class 6 and figured I should do everything then.
Reanimatedshad0w said:
Thanks for the information. About to start this whole process soon so this really helped Just a quick question though, do classes of the sd card matter? Have a class 2 card atm but about to buy a 16gig class 6 and figured I should do everything then.
Click to expand...
Click to collapse
Yes, a higher class makes a big difference in speed. Make sure you wipe the new SD card from within the Evo before doing anything.
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
elr0y said:
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
Click to expand...
Click to collapse
you should wipe. the backup will save everything you had on the respective rom
Yes awesome guide thanks, just what I was looking for. Stupid question but when I do a "Backup Current ROM" in ROM Manager, does this also back up texts, apps, games etc?
Thanks again webs
elr0y said:
Dumb question (I'm new to Android):
When switching ROMs, both of which you have a backup for, do you have to wipe, flash the rom, then flash the nandroid backup?
Or would wiping and then flashing the backup work the same?
I have Fresh and Avalaunch's Froyo with all my apps both backed up. I realize it won't save much time, but I wouldn't have to keep both ROMs on my SD card if I could just use the backup to switch.
Thanks for the guide.
Click to expand...
Click to collapse
To switch ROM by restoring nand backups all you should have to do is go into recovery and restore the one you want. If you wanted to be safe you could wipe first. As far as flashing that rom before nand backup no. There would be no point of that. The nand backup restores ALL, everything that was on that phone previously. It is a full backup.
huzvi88 said:
Yes awesome guide thanks, just what I was looking for. Stupid question but when I do a "Backup Current ROM" in ROM Manager, does this also back up texts, apps, games etc?
Thanks again webs
Click to expand...
Click to collapse
Yes, it should backup everything. Upon restore your phone should look and act just as it was when you created that backup. The backup system in Rom Manager boots the phone to recovery and does a nand backup for you.
webs05 said:
Yes, it should backup everything. Upon restore your phone should look and act just as it was when you created that backup. The backup system in Rom Manager boots the phone to recovery and does a nand backup for you.
Click to expand...
Click to collapse
Haha that was my next question. Thanks really appreciate it!
huzvi88 said:
Haha that was my next question. Thanks really appreciate it!
Click to expand...
Click to collapse
Your welcome, and the same goes to everyone else.
I'm an idiot i think and just bricked my phone.
I used revoke website to root my phone I did not do a nand unlock. I then installed rom manager because I wanted to backup the current stock rom. I used the option to flash in something from rom manager and then back up. after that my phone restarted and all I see is a picture of a phone with and exclamation point. am I bricked? anything I can do? sorry I'm a noob.
-U
usctrunks said:
I'm an idiot i think and just bricked my phone.
I used revoke website to root my phone I did not do a nand unlock. I then installed rom manager because I wanted to backup the current stock rom. I used the option to flash in something from rom manager and then back up. after that my phone restarted and all I see is a picture of a phone with and exclamation point. am I bricked? anything I can do? sorry I'm a noob.
-U
Click to expand...
Click to collapse
Lol! You are fine. Fortunately HTC makes their phone tough to brick.
You are at that screen because you only did part 1 of Unrevoked's system. They have released part 2. Follow that and you should be good to go. Post questions on their threads. Good luck.
lol thanks
Hello XDA devs, this is my first time making a thread here. To keep it simple, I have an Nvidia Shield Tablet rooted on OTA 3.1 and I have just filled the recall to get a new one. I use Busybox, GLtools and FolderMount. So I have lots of things made on this tablet, my bootloader is open as well. I would like to know how I could backup this tablet so that I can make the new one just like this one without passing too much trouble. The fact that this one will be dissabled when I use the new one is also one of the problems that must not be overlooked.
Nandroid backup from recovery and copy the backup to a SD card and restore it on the new device.
Nandroid might mess up serial numbers if the backup from the original device carries over that information.?
Sent from my SHIELD Tablet using XDA Free mobile app
I was thinking something along the lines of backing up my app and user data with Titanium Backup, moving it to my sd card and then unlocking the booloader on the new tablet, rooting it and doing a restore with Titanium backup, with that backup I made on the old device. Would that work? Or would the nandroid backup work and be more effective?
What kind of serial number? If so, it would be somewhere in the hardware and a nandroid is just backing your data...
I believe Titanium requires root, so you've got a cart and horse problem. I think you can fastboot boot twrp-recovery.img and make a nandroid backup without unlocking bootloader though. Never tried fastboot boot on the shield though.
Sent from my One M8 using XDA Free mobile app
I would be interested in a step-by-step for unrooted stock Android 5.01 backup. I'm familiar enough with rooting / TWRP / flashing etc., but haven't done it on this device. Looking for easiest option. Since it's less than a month old I may just back up basic files manually and then wipe it, but if there's an easier way without going through trouble of rooting I'd be good to try it out. I've got the LTE version, by the way.
I have read that some people claim it to be possible to use a Nandroid backup for a same model phone or tablet, by following some procedures, while there are others who claim that it should not be possible.
I'm going to go the Titanium route just to be careful, as for the fastboot commands from pc, etc., I have done that before so opening the bootloader on the new device and re-rooting is not a big deal for me. I am more worried about whether FolderMount will work without problem on the new tablet when I restore with Titanium or not. I won't be making changes in my sd card, so I hope once I recover, Foldermount works and recognizes the links I've made.
AbrahamZX1 said:
I have read that some people claim it to be possible to use a Nandroid backup for a same model phone or tablet, by following some procedures, while there are others who claim that it should not be possible.
I'm going to go the Titanium route just to be careful, as for the fastboot commands from pc, etc., I have done that before so opening the bootloader on the new device and re-rooting is not a big deal for me. I am more worried about whether FolderMount will work without problem on the new tablet when I restore with Titanium or not. I won't be making changes in my sd card, so I hope once I recover, Foldermount works and recognizes the links I've made.
Click to expand...
Click to collapse
When you restore your files on your new device, Titanium asks if you to restore your old ID to prevent problems with restored apps. So yes, foldermount and such will work correctly if you do that.
Themaniacboy said:
When you restore your files on your new device, Titanium asks if you to restore your old ID to prevent problems with restored apps. So yes, foldermount and such will work correctly if you do that.
Click to expand...
Click to collapse
Would restoring my ID do anything else? I assume there would be no side effect.
AbrahamZX1 said:
Would restoring my ID do anything else? I assume there would be no side effect.
Click to expand...
Click to collapse
Correct, there will be no side effect.
How did it go?
AbrahamZX1 said:
Hello XDA devs, this is my first time making a thread here. To keep it simple, I have an Nvidia Shield Tablet rooted on OTA 3.1 and I have just filled the recall to get a new one. I use Busybox, GLtools and FolderMount. So I have lots of things made on this tablet, my bootloader is open as well. I would like to know how I could backup this tablet so that I can make the new one just like this one without passing too much trouble. The fact that this one will be dissabled when I use the new one is also one of the problems that must not be overlooked.
Click to expand...
Click to collapse
Did you use Nandroid or Titantium & if you use Nvidia Hub does rooting affect it please?
AbrahamZX1 said:
I have read that some people claim it to be possible to use a Nandroid backup for a same model phone or tablet, by following some procedures, while there are others who claim that it should not be possible.
I'm going to go the Titanium route just to be careful, as for the fastboot commands from pc, etc., I have done that before so opening the bootloader on the new device and re-rooting is not a big deal for me. I am more worried about whether FolderMount will work without problem on the new tablet when I restore with Titanium or not. I won't be making changes in my sd card, so I hope once I recover, Foldermount works and recognizes the links I've made.
Click to expand...
Click to collapse
Do a nandroid backup in TWRP. I just did this exact same thing for my recall replacement! It works just fine. All you have to do is rename the backup folder, because TWRP saves the nandroid backup in a folder that is named what your Tablet serial number is. You have to rename the folder and change the name to your NEW Tablet serial number, otherwise the backup will not even show up in TWRP on the new Tablet. I assume this is done so that people that create backups of several different devices, onto an sdcard for example, can't accidentally restore an incompatible backup (say a nexus 6 backup on a nexus 5). I can assure you though it works just fine as long as both devices are the same.
optical10 said:
Did you use Nandroid or Titantium & if you use Nvidia Hub does rooting affect it please?
Click to expand...
Click to collapse
I haven't received the recall tablet yet, so I still haven't had the chance to do the restore. I will be saving a backup for both methods though and try out a Nandroid restore first. Rooting hasn't affected any Nvidia app for me.
Success for non-rooted Shields
optical10 said:
Did you use Nandroid or Titantium & if you use Nvidia Hub does rooting affect it please?
Click to expand...
Click to collapse
Used Googles non advertised ADB command line backup, Helium backup also uses ADB for a user friendly UI if your not command line savy.
Seems to have worked but will report back if the full APK + data has left glaring holes etc. Lastpass wasn't installed but thats a plus security wise.
Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app
re: zip file rom backups
tamelion1117 said:
Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
Don't you think that if it was something feasible and worthwhile to do many of the developers would have
created something like that already after all these years?
The developers have already developed an excellent way of backing up and restoring android phones using
TWRP and CWM nandroid backup and restore functions in their custom recovery mode which everyone uses.
If you don't trust nandroid backups why not do a simple test and make some nandroid backups and restore each
of them one at a time to see if you can find any kind of issues, problems or difficulties with your phone after you
have restored each of the backups one at a time.
Have you ever created a nandroid backup which did not restore properly or know of anyone who did?
Also why not do a bit of research here in these xda forums and threads to see if you can find any posts here by
people who are having any problems, issues or difficulties using or restoring their nandroid backups.
Good luck,
Have a great day!
Misterjunky said:
Don't you think that if it was something feasible and worthwhile to do many of the developers would have
created something like that already after all these years?
The developers have already developed an excellent way of backing up and restoring android phones using
TWRP and CWM nandroid backup and restore functions in their custom recovery mode.
If you don't trust nandroid backups why not make two of them as a test and restore each of them one at a time
and see if you can find any kind of issues or problems with your phone after restoring each of the backups.
Have you ever created a nandroid backup which did not restore properly or know of anyone who did?
Also why not do a bit of reading here in these xda forums and threads to see if you can find any people here
who are having any problems or issues with their nandroid backups after they have restored them.
Good luck,
Have a great day!
Click to expand...
Click to collapse
I trust in my nandroid backups. The main reason I want to create a flashable zip with everything backed up in it is to have the ability to create a duplicate image of my phone and flash it on my wife's.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1
tamelion1117 said:
Like the title says, I'm trying to figure out how to make a flashable zip of my phone with all my installed apps, app data and settings included.
I already have a nandroid backup and I already use titanium to back up my apps and app data, but I want to have a flashable zip as another backup incase all else fails.
I also want to be able to flash the zip on my wife's N5.
Can someone kindly walk me through the process or point me in the direction of a good walk through?
Thanks in advance.
Sent from my SM-N920T using XDA-Developers mobile app
Click to expand...
Click to collapse
well if you really want to learn
here's a simple example of how you can build yourself a rom
http://forum.xda-developers.com/honor-5x/development/custom-rom-starter-template-honor-5x-t3328809
keep in mind you can't use his updater-script and you need to adjust some of the commands to match the note 5
but for the most part all roms are the same
you need:
META-INF <Folder>
boot.img
system.apps.tar.gz
system.therest.tar.gz
and optionally > data.tar.gz
once you have these you essentially have a rom
There's also an app called "zip me" in the play store that will do exactly what I wanted.
https://play.google.com/store/apps/details?id=zip.me
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1
re: backups
tamelion1117 said:
I trust in my nandroid backups. The main reason I want to create a flashable zip with everything backed up in it is to have the ability to create a duplicate image of my phone and flash it on my wife's.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1
Click to expand...
Click to collapse
If you want a duplicate image why not create two nandroids and copy one
to your pc then to your wife's phone since you say the phone is identical
which they would have to be in order to use the same backup.
Once the nandroid is on your pc you can simply copy it to your wife's
internal memory then restore using twrp.
I have about 5-6 nandroid backups of different roms for my phone.
Goodluck,
Misterjunky said:
If you want a duplicate image why not create two nandroids and copy one
to your pc then to your wife's phone since you say the phone is identical
which they would have to be in order to use the same backup.
Once the nandroid is on your pc you can simply copy it to your wife's
internal memory then restore using twrp.
I have about 5-6 nandroid backups of different roms for my phone.
Goodluck,
Click to expand...
Click to collapse
I don't think I was clear in the op. I know how to create nandroids, and yes, I could easily do it that way, but what I really want to do is compile my rom, settings apps and app settings into a flashable zip instead. To further my knowledge so to speak.
Sent from my Samsung Galaxy Note 5 running Darthstalker v8 and Xposed 85.1
Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!
Reece Pondwell said:
Okay, I'm not a techie and I want to know how to backup everything on my phone before I attempt to root my OnePlus One using KingRoot.
At first I naively thought that copying all files and folders from my phone to my laptop would work, but 3 things seem to suggest it's not as easy as that:
I get an error message every time I try copying the files in the ColorNote folder
I saw a mention somehwere that to backup something called EFS you need to run a special app
I'm guessing that my contacts and SMS messages will not be backed up just by copying files and folders from my phone.
So my question is how do I backup *everything* (not just those things I have specifically refered to here) just in case something goes wrong when running KingRoot?
I would prefer not to have to upload my data to the cloud to back it up if at all possible.
Thanks fine people!
Click to expand...
Click to collapse
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Mr.Ak said:
Do you plan to unlock bootloader and flash custom recovery? If not and you just want root,you can safely skip all of this backup part as kingroot/kingoroot won't do any harm to your device.
Also if you don't like kinguser as default granting roots app,you can change it into SuperSu too.
Here's a great guide by @Nishidh
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
Click to expand...
Click to collapse
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!
Reece Pondwell said:
Hi and thanks for your reply.
I don't plan to unlock the bootloader. I also wasn't planning on flashing a custom recovery (tbh I don't even know what "flashing" means), however I was thinking of using the KingRoot desktop version and their website states that "the desktop KingRoot version can only be flashed using recovery custom tools". I'm guessing that means that when I run KingRoot it will automatically flash a custom recovery.
BUT if doing that means that my data is wiped then I will stick to the android version even though at the moment I am trying to write an absolute minimum of data to my phone. (My reason for wanting to root is to have one last attempt to recover a load of data that I lost off my phone using a file recovery program that requires root access).
I know that if I run KingRoot just to root it is not supposed to delete any data, but I thought that it was generally thought to be good practice to backup your data before the process anyway just in case something untoward happens (in fact I *think* I read a reccommendation to do that on the official KingRoot website).
Thanks for the video link & tip and, of course, your advice!
Click to expand...
Click to collapse
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.
Mr.Ak said:
No don't use the desktop version.Use the mobile version and make sure you've fast net connection.Kingroot doesn't install recovery.It just roots,though,ofc not as good as rooting from recovery but still enough for daily tasks.
Click to expand...
Click to collapse
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101
Reece Pondwell said:
Thanks for that. I've tried running KingRoot app, but having some problems as reported here: https://forum.xda-developers.com/oneplus-one/help/kingroot-app-t3573101
Click to expand...
Click to collapse
Yes,its totally safe to quit the app.
You can try Kingoroot too.
Mr.Ak said:
Yes,its totally safe to quit the app.
You can try Kingoroot too.
Click to expand...
Click to collapse
Thanks Mr Ak!
Hey all!
I am looking to copy the app data of an HRV app that I have been using off of my Pixel 3 so I can use it elsewhere.
From what I can gather is I need SU access to do this
--> which requires me to root the device,
--> which requires me to unlock the bootloader and flash a patched image
--> which will wipe the device and delete the data I'm trying to extract?
Am I understanding this correctly? Or am I getting some detail wrong?
AM I THE CHICKEN, OR THE EGG, OR THE CHICKEN.....
Thanks in advacnce for fielding this Newbie question
I've been scratching my head for hours now as to whether I need TWRP, or Magisk..... and how I get a Nandroid backup? or Titanium? Will following the setup and steps to get this up and going result in me deleting the very data I'm looking for?
cheers,
Condorman!
iamcondorman said:
Hey all!
I am looking to copy the app data of an HRV app that I have been using off of my Pixel 3 so I can use it elsewhere.
From what I can gather is I need SU access to do this
--> which requires me to root the device,
--> which requires me to unlock the bootloader and flash a patched image
--> which will wipe the device and delete the data I'm trying to extract?
Am I understanding this correctly? Or am I getting some detail wrong?
AM I THE CHICKEN, OR THE EGG, OR THE CHICKEN.....
Thanks in advacnce for fielding this Newbie question
I've been scratching my head for hours now as to whether I need TWRP, or Magisk..... and how I get a Nandroid backup? or Titanium? Will following the setup and steps to get this up and going result in me deleting the very data I'm looking for?
cheers,
Condorman!
Click to expand...
Click to collapse
You can try an adb backup. See https://gist.github.com/AnatomicJC/e773dd55ae60ab0b2d6dd2351eb977c1
I can't guarantee it will work for you, but it is pretty much your only hope without root. Forget Titanium Backup, even if you had root. TB has not been updated since 2019, and has restore problems with newer android versions. There is no TWRP for Pixel 3 Android 11.
If you do root (which will require wiping your data) look at Swift Backup. That's what I started using since TB became obsolete.
You understand correctly, and have the details right (unless the adb backup works for you).
dcarvil said:
You can try an adb backup. See https://gist.github.com/AnatomicJC/e773dd55ae60ab0b2d6dd2351eb977c1
I can't guarantee it will work for you, but it is pretty much your only hope without root. Forget Titanium Backup, even if you had root. TB has not been updated since 2019, and has restore problems with newer android versions. There is no TWRP for Pixel 3 Android 11.
If you do root (which will require wiping your data) look at Swift Backup. That's what I started using since TB became obsolete.
You understand correctly, and have the details right (unless the adb backup works for you).
Click to expand...
Click to collapse
Hi dcarvil,
Thanks for the response.
I'll look at trying out that gist, although it may be that all hope is lost, I tried some similar commands that gave the '46' byte backup none file because it honored the 'allowbackup=0' app manifest directive