edit: regarding below, I did another flash and this time it did create a backup in clockworkmod/backups.
maybe I did something wrong ... nah, that would never happen.
I just flashed a rom with rom manager and selected BACKUP CURRENT ROM while doing so.
Where the heck is the backed up ROM? I can't find it anywhere on sd card.
edit:
I should have said that I know to look in clockworkmod/backups, I have ton of bups in there that I did with BACKUP CURRENT ROM (just backing up, not flashing).
I am referring to when you are flashing rom and the popup with 2 choices comes up (wipe,backup). I checked backup and it seemed to do it, but there is no file in clockword any newer than the last bup I did with the BACKUP CURRENT ROM function.
on your sd card look for the clockwork mod folder, in there are two folders, "backup" and "download". it's in backup
I should have said that I knew to look there, I have ton of bups in there that I did with BACKUP CURRENT ROM.
I am referring to when you are flashing rom and the popup with 2 choices comes up (wipe,backup). I checked backup and it seemed to do it, but there is no file in clockword any newer than the last bup I did with the BACKUP CURRENT ROM function.
Related
Sorry if this is a newb question...but it comes from a newb.
I have successfully rooted, and flashed a recovery image onto my Sprint Hero....and I have created a nandroid backup of the rooted phone. Just yesterday I went in and deleted all the sprint bloatware. Here's my question:
Can I create another nandroid backup of my phone as it is right now? or will it delete my old nandroid backup? I would like to have the option to reflash to both the first state, and now the newer state. I hope this question is not confusing.
Can anyone help? Can you have multiple nandroid backup images? or do they override the previous one?
Thanks in advance! God bless!
-alex
You can have as many nandroid backups as your storage card has room for. That being said, if you do a nandroid restore, it will restore only the most recent one so if you want to restore to an older one, just move all the newer one to a different folder or something.
I add a "_sprintgolden" at the end or what ever and leave all the numbers in place that way I know whats what and can delete the extra and it will restore that backup
Yep, you can have as many as you want (store'em on your pc),just copy them out of your storage card otherwise it'll get overwritten by the next backup.
right on Iz
thanks guys! you guys are awesome! This stuff is fun! Can't wait for some new, fast Sprint Hero roms to start flashing! I haven't flashed anything yet.
Thanks again for the help! God bless!
-alex
izanagi said:
Yep, you can have as many as you want (store'em on your pc),just copy them out of your storage card otherwise it'll get overwritten by the next backup.
Click to expand...
Click to collapse
No...it won't delete any of the backups. You can have as many backups as the card will hold (as an earlier post stated). The Nandroid Restore will only restore the most recent one.
If you want to keep all on your SD card, but restore from another backup, you'll have to drop to a shell on the phone to run Nandroid. That's accomplished by using ADB from the Google Android SDK. If you type nandroid -? on the command prompt, it will give you a list of parameters you can use to restore or backup Android.
Is it possible to rename a folder created by a nandroid backup and still have it to work?
I have 3 or 4 roms backed up and it's geting difficult to remember which is which
poddo said:
Is it possible to rename a folder created by a nandroid backup and still have it to work?
I have 3 or 4 roms backed up and it's geting difficult to remember which is which
Click to expand...
Click to collapse
Yes it is possible.
I do this and it works:
\SDCard\nandroid\HT9APNT01015\ *custom named folders with img files inside*
Did you get that?
that's what I tried to do, but it seems nandroid didn't like its backups anymore after renaming the folders
when i 'Nandroid' restore the phone, do i have to reroot my phone? Or is root access still available? (Again, i'm new to the custom ROM world and getting familiair with the basics)
doing a nandroid backup is like creating an image of the phone software.
once you restore, your phone revert back being exactly the same as when you did the backup (rom wise, which includes root)
poddo said:
doing a nandroid backup is like creating an image of the phone software.
once you restore, your phone revert back being exactly the same as when you did the backup (rom wise, which includes root)
Click to expand...
Click to collapse
Thanks, i back-upped the phone after root was enabled, so it won't harm my root access.
poddo said:
that's what I tried to do, but it seems nandroid didn't like its backups anymore after renaming the folders
Click to expand...
Click to collapse
Hmmm, that is weird. I wonder if it has to do with the type or version of recovery image you have. At the moment I have RA-hero-v1.6.2.
Just to be clear, if you don't rename the folders, it restores properly?
it does, just one time it happened the backup got corrupted and wouldn't let the phone boot after restore (I am using same recovery img as yours)
I'm going to try renaming the folders again later
I wish you luck! Could you please post back with the result? I am very curious.
In my ongoing travels on the internets I will keep an eye out for a possible solution.
looks like this time it worked.
for some reason nandroid it seems nandroid has an erratic behaviour from time to time.
first time I made a copy of my first (working) backup and I renamed it, nandroid won't let me load it (thus why I created this thread); yesterday, after working fine it created a corrupted backup and I had to reinstall cronos from scratch.
only difference between my first try renaming backup directories is that the first time I made the copy via windows, while the second time I did it through Astro.
I'm going to watch into this.
EDIT: k, sorted the renaming issue. nandroid simply won't handle folders with spaces in their name
still, a couple times nandroid produced corrupted backups and this is forcing me to backup 3 times in a row just to be sure. :/
poddo said:
looks like this time it worked.
for some reason nandroid it seems nandroid has an erratic behaviour from time to time.
first time I made a copy of my first (working) backup and I renamed it, nandroid won't let me load it (thus why I created this thread); yesterday, after working fine it created a corrupted backup and I had to reinstall cronos from scratch.
only difference between my first try renaming backup directories is that the first time I made the copy via windows, while the second time I did it through Astro.
I'm going to watch into this.
EDIT: k, sorted the renaming issue. nandroid simply won't handle folders with spaces in their name
still, a couple times nandroid produced corrupted backups and this is forcing me to backup 3 times in a row just to be sure. :/
Click to expand...
Click to collapse
Glad you've found the issue! That is really weird about Nandroid creating corrupted backups...
It is so strange that using Windows (or not) creates or solves problems. I've read of instances where creating a goldcard with Win7 failed but WinXP worked.
Guys,... You using AmonRa yeah?.... It might be worth mentioning all your finds to the man Amon Ra himself,... Post something in the AmonRa thread, maybe there is something he can sort for future updates.
I have a rooted Nexus 7 running the ROM aokp_grouper_jb_build-5. If I backed up this ROM in Clockworkmod recovery, then installed a new ROM, would I be able to restore back to my AOKP ROM if I didn't like the new ROM I installed?
Yep
It's not a problem. You can back up your new ROM too. Be sure to put something in the name of your backups to let you know which ROM it is. I usually leave the date & then put the ROM name in, such as 2012-10-28-AOKP.
No problem at all
Sent From My Nexus 7- Corrupted by Trinity
strongergravity said:
It's not a problem. You can back up your new ROM too. Be sure to put something in the name of your backups to let you know which ROM it is. I usually leave the date & then put the ROM name in, such as 2012-10-28-AOKP.
Click to expand...
Click to collapse
When I back up my ROM it doesn't let me choose a name for the backup. How can I change the name of the backup?
I use TWRP and you have to set the name of the backup before you start the backup process
215alexdx said:
When I back up my ROM it doesn't let me choose a name for the backup. How can I change the name of the backup?
Click to expand...
Click to collapse
Just use your file explorer to find the file & rename it. If you are using Clockwork, there will be a folder on your sdcard called clockwork, and in that is a folder called backups. your backup file is in there, named something like 2012-10-28.12.10.3242, which is the date & time of the backup.
After Google Services drying up my monthly data cap trying to download 4.3, I thought I'd move from PACman v23 to the new Paranoid Android 3.92 as it had 4.3. I thought I did all the right things. I backed up in Rom Manager, copied the file across to my PC. I ran a fresh backup of everything in Titanium Backup and copied that all across to my PC too.
I did a factory reset/data wipe and flashed bootloader/modem/rom/gapps as instructed and got the latest Paranoid Android running. I copy across my TB backup directory and I install TitaniumBackup from the market place. I go restore missing apps, and then... it just hangs on the first app. Read a little online, change the restore mode to "Interactive", doesn't fix it. Go back to the normal setting. I run Verify Backups, and to my surprise, it says there are errors with ALL my backup files. I get pissed, decide perhaps I should've just created a flashable zip. So I say no problem. I'm persistent. I'll create a backup of Paranoid Android, reflash my PACman backup, redo my Titanium Backup, and then reflash my Paranoid Android backup and apply the TB backup zip. So I Copy my PACman zip file, choose Install ZIP from sdcard, select the PACman zip and boom... MD5 verification failed.
I realise I had some Titanium Backup essentials backup on Google Drive and Dropbox, so I copy them over. Point TB to that directory, but the same problem persists. It just hangs.
I've been copying across the same TB folder between various ROM installations with no issues, and I'm not sure what is causing the issue here. I suspect it is either the bootloader and radio (which was what has been the extra step compared to installing other roms) but I don't want to admit that now all my backups are completely useless.
Am I missing something here? Anyone have any suggestions?
TL;DR I can't seem to get any TB backups to restore on my newly flashed Paranoid Android rom.
mversion said:
After Google Services drying up my monthly data cap trying to download 4.3, I thought I'd move from PACman v23 to the new Paranoid Android 3.92 as it had 4.3. I thought I did all the right things. I backed up in Rom Manager, copied the file across to my PC. I ran a fresh backup of everything in Titanium Backup and copied that all across to my PC too.
I did a factory reset/data wipe and flashed bootloader/modem/rom/gapps as instructed and got the latest Paranoid Android running. I copy across my TB backup directory and I install TitaniumBackup from the market place. I go restore missing apps, and then... it just hangs on the first app. Read a little online, change the restore mode to "Interactive", doesn't fix it. Go back to the normal setting. I run Verify Backups, and to my surprise, it says there are errors with ALL my backup files. I get pissed, decide perhaps I should've just created a flashable zip. So I say no problem. I'm persistent. I'll create a backup of Paranoid Android, reflash my PACman backup, redo my Titanium Backup, and then reflash my Paranoid Android backup and apply the TB backup zip. So I Copy my PACman zip file, choose Install ZIP from sdcard, select the PACman zip and boom... MD5 verification failed.
I realise I had some Titanium Backup essentials backup on Google Drive and Dropbox, so I copy them over. Point TB to that directory, but the same problem persists. It just hangs.
I've been copying across the same TB folder between various ROM installations with no issues, and I'm not sure what is causing the issue here. I suspect it is either the bootloader and radio (which was what has been the extra step compared to installing other roms) but I don't want to admit that now all my backups are completely useless.
Am I missing something here? Anyone have any suggestions?
TL;DR I can't seem to get any TB backups to restore on my newly flashed Paranoid Android rom.
Click to expand...
Click to collapse
Do you have the latest version of Titanium Backup, that supports Android 4.3?
mversion said:
After Google Services drying up my monthly data cap trying to download 4.3, I thought I'd move from PACman v23 to the new Paranoid Android 3.92 as it had 4.3. I thought I did all the right things. I backed up in Rom Manager, copied the file across to my PC. I ran a fresh backup of everything in Titanium Backup and copied that all across to my PC too.
I did a factory reset/data wipe and flashed bootloader/modem/rom/gapps as instructed and got the latest Paranoid Android running. I copy across my TB backup directory and I install TitaniumBackup from the market place. I go restore missing apps, and then... it just hangs on the first app. Read a little online, change the restore mode to "Interactive", doesn't fix it. Go back to the normal setting. I run Verify Backups, and to my surprise, it says there are errors with ALL my backup files. I get pissed, decide perhaps I should've just created a flashable zip. So I say no problem. I'm persistent. I'll create a backup of Paranoid Android, reflash my PACman backup, redo my Titanium Backup, and then reflash my Paranoid Android backup and apply the TB backup zip. So I Copy my PACman zip file, choose Install ZIP from sdcard, select the PACman zip and boom... MD5 verification failed.
I realise I had some Titanium Backup essentials backup on Google Drive and Dropbox, so I copy them over. Point TB to that directory, but the same problem persists. It just hangs.
I've been copying across the same TB folder between various ROM installations with no issues, and I'm not sure what is causing the issue here. I suspect it is either the bootloader and radio (which was what has been the extra step compared to installing other roms) but I don't want to admit that now all my backups are completely useless.
Am I missing something here? Anyone have any suggestions?
TL;DR I can't seem to get any TB backups to restore on my newly flashed Paranoid Android rom.
Click to expand...
Click to collapse
I'm having the same issues. Best luck I had is to install the latest SuperSU(PA uses an integrated superuser) and then restore my apps one by one. Some work and others don't. It's a problem with 4.3/TB and SU which hopefully will be resolved. Most of my games worked but Nova launcher did not. I was also in indirect mode when restoring them.
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
I think I screwed something up before. Just did a factory reset, installed latest SuperSU and changed app installation to indirect mode. Everything restored flawlessly after that.
Here is the reply for anyone having similar issues which is explained easily in details
https://plus.google.com/app/basic/stream/z12rw1urfveawxfxm04cjl1aoor5ezninhc
johnie5 said:
Here is the reply for anyone having similar issues which is explained easily in details
https://plus.google.com/app/basic/stream/z12rw1urfveawxfxm04cjl1aoor5ezninhc
Click to expand...
Click to collapse
Thanks.
I installed stock 4.3, had to flash the latest SuperSU to get root, and found that all my Titanium Backup files were A-OK. Perhaps it is just a matter of the latest SuperSU and the TB workaround detailed on that link:
...Titanium Backup is an example of such an app. It may incorrectly detect the path to your internal storage for backups, and thus crash on backup/restore. You can fix this by going into preferences and selecting a folder under /storage/emulated/legacy as backup/restore path, not under /storage/emulated/0.
Click to expand...
Click to collapse
I'll reinstall PA3.92 and try again.
Last update: Installing the latest Paranoid Android 3.94 and putting my Titanium Backup folder in the legacy folder detailed above has given me a working solution.
Mercado_Negro said:
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
Click to expand...
Click to collapse
Thanks for the solution!! I've been trying to restore stuff for hours.
Happy I found a solution. I too spent way too long getting Titanium Backup to restore apps. And once I found this solution, implementing the folder change isn't just ticking a box or adding an entry. But all's well now. Really enjoying my first taste of Paranoid Android - lots of settings to figure out. I was having dpi/resolution issues with Simpson's Tapped Out and PA will give me several solution options. Thanks everyone!
mversion said:
Thanks.
I installed stock 4.3, had to flash the latest SuperSU to get root, and found that all my Titanium Backup files were A-OK. Perhaps it is just a matter of the latest SuperSU and the TB workaround detailed on that link:
I'll reinstall PA3.92 and try again.
Click to expand...
Click to collapse
I was having restore problems with Titanium Backup and installed SuperSU from the play store after reading this and then allowed it to update the binaries through CWM.
All my backups are now restoring fine!
Mercado_Negro said:
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
Click to expand...
Click to collapse
This worked for me, too, on two different ROMs on my HTC One. I can't believe how easy it was after I tried to figure out a solution for about two hours. Thanks!!!
Mercado_Negro said:
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
Click to expand...
Click to collapse
That's a bingo!
here is what I did (nexus 7 FLO)
menu - > preferences -> Backup folder location -> DETECT
choose /legacy instead of /0/something or other
It will ask to move the data
select yes
restore away
Mercado_Negro said:
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
Click to expand...
Click to collapse
This was much appreciated. I simply switched the backup folder location from /storage/emulated/0 to /storage/emulated/legacy instead. Problem Solved. No Rebooting, no installing SuperSU or anything. I've spent two hours trying to restore my backups (the one time, I forgot to create the flash zips with all my backups and the one time I didn't have space to create a Nandroid,) and now I'm good to Go.
Mercado_Negro said:
You have to change the backups folder to storage/emulated/legacy in 4.3 to be able to restore your applications. You can change it in Menu/Preferences within TiBu.
Click to expand...
Click to collapse
Thanks , worked perfect :good:
Xentar712 said:
I'm having the same issues. Best luck I had is to install the latest SuperSU(PA uses an integrated superuser) and then restore my apps one by one. Some work and others don't. It's a problem with 4.3/TB and SU which hopefully will be resolved. Most of my games worked but Nova launcher did not. I was also in indirect mode when restoring them.
Click to expand...
Click to collapse
Thank you. I've had a few reinstalls now where I've had to redirect TiBu to the "Legacy" path but this time with Carbon rom I also had to update SuperSU, then let SuperSU update the binary through CWM before I could restore anything.
Edit: Also if you're having problems figuring out how to change Titanium Backup's default path in preferences, your phone/tablet's Back button (beside the home button) will move you up through directories in the "select backup folder" dialog. This one had me stuck for awhile so maybe this info will help someone else.
Even changing it to legacy I am unable to get TiBU to restore. I have even made it navigate to the Titanium Backup Folder where I can see all my apps and system data backed up but it won't load it to restore for some reason.
Any suggestions?
xavier2k3 said:
Even changing it to legacy I am unable to get TiBU to restore. I have even made it navigate to the Titanium Backup Folder where I can see all my apps and system data backed up but it won't load it to restore for some reason.
Any suggestions?
Click to expand...
Click to collapse
Yes, flash superSU:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
droidgren said:
Yes, flash superSU:
http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip
Click to expand...
Click to collapse
Already had. I just set it up again from scratch. Wasn't that bad to be honest.
Titanium Backup was updated today to version 6.1.1. It uses the /legacy path now by default for ROMs using Superuser. You shouldn't run into problems anymore.
So i just back up my stock rom via cwm in extsdcard and the folder come around 7gb. After flash new rom i went to back up the new rom using rom manager. but i found the folder cwm in extsdcard is missing after the back up and i can find the new backup in emulate folder but my old file is missing. anyone could help me pls?
Dont use Rom Manager use recovery .
anakbengal said:
So i just back up my stock rom via cwm in extsdcard and the folder come around 7gb. After flash new rom i went to back up the new rom using rom manager. but i found the folder cwm in extsdcard is missing after the back up and i can find the new backup in emulate folder but my old file is missing. anyone could help me pls?
Click to expand...
Click to collapse
Always store your backup file in a computer right after backing up, never just assume that you won't lose it after installing a new ROM.
Like JJEgan said, always backup using recovery.
I would just keep looking in your files (maybe you moved the file...?) or just plain leave it for dead.
A fresh start is sometimes the way to go