I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
number_thirty_two said:
I took a Nandroid backup of my stock phone (all partitions) before I flashed a new ROM (DN3). Then I decided to return to stock ROM, so I wiped phone and restored Nandroid backup (all partitions except bootloader and recovery).
Now the phone will not boot, it just shows a logo and then a black screen. I can connect to it via ADB however.
I thought Nandroid backup was a safe way of preserving phone, but it seems it cannot actually be trusted?
Click to expand...
Click to collapse
depends on bootloader i guess, but maybe try wipe data and preload / cache and dalvik and reflash, make sure ROM to flash is on external sdcard as may lose all data on phone
Having the same issue after re-partitioning my phone. My nandroid backup is about 2.3gb and it took about 200 seconds to restore. Nothing was actually restored when I booted up. (This nandroid was made to my SD-Card, wonder if that makes any difference.
N7105 rocking AOSB with AGNi kernel,
Sent from a small country named Singapore.
Click "Thanks" if I was of any help!
Related
Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?
hydrano said:
Hello
i have a boot loop after restoring a backup, because after installing 'gapps' to the Cyanogenmod 7, it didn't work anymore
So i went into the Recovery mode to restore the backup.
But after restoring is the splash screen in a booting loop.
What can i do now?
There isn't another backup on my sd card
Is it possible to install another Rom directly from the recovery menu?
Click to expand...
Click to collapse
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452
brandall said:
I had problems with bootloops after restoring nandroid backup - I restored all but part of it in advanced and it worked...
Check out this thread to see if it helps - http://forum.xda-developers.com/showthread.php?t=985452
Click to expand...
Click to collapse
brandall, thankyou, I was in a nandroid-restore-boot-loop and your tip about not restoreing 'boot' saved me too (messinga around with my brothers Desire and I don't want him kicking my ass becaused of needing an unwanted full wipe)
but it's strange that an nandroid of a fully working installation fails when restored :S (had the same HBOOT when backup and restore, and the restore was made 15 minutes after creation :S )
Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App
MatDrOiD said:
Go into recovery, wipe everything and restore backup.
Swyped from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!
MrPontus said:
Yes we both did that, but somehow the backup went broken.
I tried wipeing EVERYTHING and restore backup maybe 5 times, but boot loop every time.
So the solution was to wipe and do an advanced restore were you restored ext, system, data and cache.
But NOT restore Boot!
Click to expand...
Click to collapse
Just happened to me, not restoring boot finally got me out of the bootloop, thank god. Thanks for that tip
I've been running CM 10, 4.1.2, on Verizon gn. Works fine.
But I can't leave well enough alone, and want to try 4.2.2.
That should be easy right, just flash the recent CM 10.1. No cache wiping. Right?
But if I do that and I don't like it. how do I go back? Is it as simple as just flashing CM 10?
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Any help appreciated.
Since you are migrating Android versions, I would recommend that you do a full wipe, so system, data, and cache (and restore apps from TiBu if you must). You can do a nandroid backup from recovery; if you don't like 4.2 just restore it. When restoring a nandroid backup everything will be exactly the same.
seandarcy said:
Also, I have Ti backup. The backup folder is sdcard/TitaniumBackup. I've read that 4.2.2 creates /sdcard/0/ for data. Does this mean that my present backup will be deleted?
Click to expand...
Click to collapse
I just upgraded from 4.1.2 to 4.2.2 and had the same concern about being able to go back if I had problems and knowing that the partitioning of internal storage would be changed.
I recently got my GN back from Samsung after getting the screen replaced. Before sending it off, I totally wiped and reset the phone to stock. I made sure I did a full Ti backup first, then a Nandroid backup, and finally copied the entire contents of internal storage via "adb pull" to my desktop computer. When I got the phone back, I reversed the process and was able to restore the phone entirely to where it was before the wipe.
I did the same operation before upgrading to 4.2.2, without wiping the phone. So if I'd have wanted to go back to 4.1.2, I'd have wiped the phone, including internal storage, and restored as described above. I'm pretty confident that this would have removed the new partitioning from 4.2.2 and reset it to where it was before the 4.2.2 upgrade.
Sorry to be dense, but...
So I do a nandroid backup from TWRP 2.4.4.0, system, data and cache
From TWRP flash the CM 4.2.2.
Do nandroid restore from TWRP?
Flash gapps, restore apps from TiBu.
Now if want to go back to 4.1.2:
Flash 4.1.2, wipe system data cache.
Flash gapps, restore apps from TiBu
Do I have this correct?
Nandroid the entire thing from TWRP, wipe system, data and cache from TWRP, flash CM10.1 and gapps from TWRP, restore apps from TiBu in ROM. If you don't like it just restore the nandroid from TWRP. TiBu only restores apps, nandroid restores everything: ROM, account, system settings, apps, etc.
The only extra thing I referred to was making a full copy of your phone's internal storage to your computer using "adb pull". This would allow you to wipe the internal storage and restore it, in case the partitioning change from "/storage/sdcard0" to "/storage/emulated/0" needed to be removed. But if TWRP's nandroid backup and restore takes care of this, this step isn't necessary.
How easy? Dead easy.
Sent from my Nexus
Here's the situation, I was on cm nightlies 4.3, made a nandroid of it then I odin'd back to stock 4.1.1 so I could unlock. After that I rooted and flashed cwm touch 6.0.4.3, format /system and /data wiped cache, dalvik and tried to restore my backup, it seems as everything restored correctly but then it gets stuck on splash screen.
kooshy91 said:
Here's the situation, I was on cm nightlies 4.3, made a nandroid of it then I odin'd back to stock 4.1.1 so I could unlock. After that I rooted and flashed cwm touch 6.0.4.3, format /system and /data wiped cache, dalvik and tried to restore my backup, it seems as everything restored correctly but then it gets stuck on splash screen.
Click to expand...
Click to collapse
you need to go back to the recovery you used to make the nandroid with if you want to use it; also, some times you can't restore a 4.3 backup when you are on 4.1..
wase4711 said:
you need to go back to the recovery you used to make the nandroid with if you want to use it; also, some times you can't restore a 4.3 backup when you are on 4.1..
Click to expand...
Click to collapse
I knew about that already thanks but still didn't work, and I i even flashed the cm rom then tried to restore backup but didn't work either. I just restored my phone data via sms/call log restore and tib but would like to know how to fix this in the future.
I made a backup of my 5x when it was running rooted/xposed 6.0.1 but then decided to update to 7.1.1 to try out the new features. But now I really miss a lot of xposed modules so I decided that I want to restore my 6.0.1 backup that I made a couple of weeks ago. So I flashed the 6.0.1 factory image from Google's developer website and was able to successfully boot into Marshmallow again. However after installing TWRP I tried restoring the backup (through USB OTG) after wiping system and cache and a doing factory reset but it pauses on "restoring system image" for a brief moment then proceeds to reboot by itself despite that it's only 27% complete. The reboot however does not go to completion and so the phone is stuck in a bootloop. I'm really not sure where the problem is here. Is it TWRP? Or the backup file? What can I do?
Which version of TWRP have you used? By any chance the backup also contained EFS?
marioemp2k7 said:
Which version of TWRP have you used? By any chance the backup also contained EFS?
Click to expand...
Click to collapse
I used version 3.0.2-2.
And isn't EFS supposed to be backed up anyway? I just checked the backup folder and it contains 4 files that begin with "efs". Should I delete those and try again?
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
marioemp2k7 said:
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
Click to expand...
Click to collapse
I made the backup while I was running 6.0.1 and I flashed the 6.0.1 factory image so they both should have the same vendor image.
I also tried wiping everything except for internal storage and I unchecked "EFS" when restoring the backup but the same problem still persists, the phone automatically reboots itself before the restoring is complete and gets stuck in a bootloop. I'm not sure where the problem is at this point. I guess I'll just have to start from scratch again
So I made a backup through OrangeFox of my A13 AOSP rom (checked every option). Now I tried to restore the backup and the restore goes normally but when I reboot to system it shows Poco logo for couple seconds then reboots to recovery and internal memory is messed up. I formatted data and tried installing the rom then restoring data alone, then data and super system, Ans the result was the same which is the rom animation starts and "starting Android" loading screen appears but never goes away. Any idea on how to get it working?
Thanks in advance
Are you trying to restore the Backup after you formated data/reflashed ROM ?
I trusted TWRP backups twice, and both times it failed.
I think to backup /data, you also have to backup /metadata, because /metadata stores the encryption-key for /data.
I also recommend the app "Swift Backup" from Play Store, it's the best app for backing up apps + appdata, messages, and call history. Requires Root to backup app-data of course.
Aserar said:
So I made a backup through OrangeFox of my A13 AOSP rom (checked every option). Now I tried to restore the backup and the restore goes normally but when I reboot to system it shows Poco logo for couple seconds then reboots to recovery and internal memory is messed up. I formatted data and tried installing the rom then restoring data alone, then data and super system, Ans the result was the same which is the rom animation starts and "starting Android" loading screen appears but never goes away. Any idea on how to get it working?
Thanks in advance
Click to expand...
Click to collapse
Yeah seems like is a tough (or impossible) mission to recover a backup in alioth.
I've done twice too, and both didn't booted too.
And this in twrp skkk, so I guess it's the same thing in all recoveries.
lapirado said:
Yeah seems like is a tough (or impossible) mission to recover a backup in alioth.
I've done twice too, and both didn't booted too.
And this in twrp skkk, so I guess it's the same thing in all recoveries.
Click to expand...
Click to collapse
cyanGalaxy said:
Are you trying to restore the Backup after you formated data/reflashed ROM ?
I trusted TWRP backups twice, and both times it failed.
I think to backup /data, you also have to backup /metadata, because /metadata stores the encryption-key for /data.
I also recommend the app "Swift Backup" from Play Store, it's the best app for backing up apps + appdata, messages, and call history. Requires Root to backup app-data of course.
Click to expand...
Click to collapse
Okay so I figured it out. You basically need to flash the same backed-up rom first and fully boot it to system. This will take care of encryption, then reboot to recovery, then restore your backup (boot/data/super). At this point reboot won't work yet. You need to go back to recovery and reflash the rom again then boot into system. For me it booted once but the status bar was missing. I did a restart and voila! It worked.
Aserar said:
Okay so I figured it out. You basically need to flash the same backed-up rom first and fully boot it to system. This will take care of encryption, then reboot to recovery, then restore your backup (boot/data/super). At this point reboot won't work yet. You need to go back to recovery and reflash the rom again then boot into system. For me it booted once but the status bar was missing. I did a restart and voila! It worked.
Click to expand...
Click to collapse
Thanks for sharing your solution!
Sounds a bit quirky but I'm glad someone got TWRP Backup Restores working!
Man the bloody forced encryption.. i hate it.