Hi --
Nexus 5 on Sprint.
I'm running into a boot loop issue when trying to restore a Nandroid Backup built on a fresh N5 about an hour after a clean install.
Details are:
I just this week updated from Stock KK (4.4.4 I think) to Stock LP (5.0.1) -- I've been waiting because of needing/wanting XPosed framework....
After unrooting and returning to stock recovery on KK 4.4.4,
I did the LP OTA followed by a Full Erase after the OTA to start fresh. (Note: I have subsequently experienced the same exact problem after installing the LP using the flash-all.bat from the Nexus 5 image extracted to the SDK/platform-tools folder.)
After completing the login and google's restore process perfectly... All things LP appear to be working well and my phone is set up the way I want. So...
I then installed CWM recovery 6.0.4.5 using fastboot.
I then used the CWM recovery to root with SuperSU v2.40
I then used CWM recovery to make a Nandroid backup... (after completing a rooted power up and returning to the recovery)
Long story short (kind of), within the first several hours I messed something up (install of Nine email app AFTER the Nandroid didn't work and was leading to android.process.acore stopping issues. Nine has since told me that the app is not compatible with my company's MDM security solution Maas36). So , I wanted to return to the Nandroid point in time and just put my company exchange email into GMAIL - Acore issues continued after removing Nine.-- but were NOT happening at the time point where I created the backup. So I booted into CWM Recovery and selected to restore and picked the backup I had made of the fresh device.
Restore via CWM recovery proceeds fine and completes. However, it goes into the flying circles boot loop (I tried leaving it go for upwards of 2.5 hours at the longest time
I can easily recover from this with a flash-all.bat in fastboot
I have done this numerous times today and it is completely repeatable. Same thing happens each time.
I have definitely restored from Nandroid previously using this process on KK. But so far no Nandroid restore possible for me on LP. To be clear, the LP install works fine, but just can't be recovered from the Nandroid backup. I guess I'm OK with that, but I'd rather not fly without a backup safety net.
Hopefully that's enough detail for someone to comment. If I've missed any helpful details, let me know.
So, have I done anything wrong? The only thing I can think of at this second is possibly needing to unroot before attempting the restore? Is that it? I don't think I've done that before.
Thanks in advance for any help that anyone can provide.
greenawayj
One quick addition. I figured someone would suggest using TWRP instead of CWM, so I'm going through that process now. I'll update the post if I find different results. I'm also making my TWRP first backup pre-root just in case that matters...
Related
Hello all,
I have successfully installed CM7 on my Nexus One. However, I have the following problem with CWM: if I ask it to make a backup from within the recovery or from RomManager, CWM (3.0.0.5, latest version available apparently for Nexus One) makes the backup, but after restarting, I am stuck on the CM7 splashscreen: I see the blue Android on his skateboard and the arrow goes around in circles (left it going for 15 minutes just to be sure).
Also, on a sidenote, when I made the initial nandroid backup in CWM from my stock Froyo, after the backup was done I had to go in RomManager and "fix permissions", because all my resident apps kept crashing with "forced close" errors. No idea where that came from. Restoring that backup did the same thing as well. I did not investigate that issue any more though as I was on my way to a CM7 upgrade anyways.
So I now have a perfectly good install of CM7 running, but I am scared of doing a CWM backup. This is far from an ideal situation, and I would love to be able to resolve this
Thanks for any help
Anyone? I really am quite upset with this situation
Use this instead?
http://forum.xda-developers.com/showthread.php?t=611829
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
yannack said:
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
Click to expand...
Click to collapse
Uh oh? It is just a custom recovery, no need to reinstall everything. You only flash the recovery and do the backup you cannot now with the broken CWM. (For my phone, there are even flashable zip files so you can switch b/w CWM and AmonRA "on the fly" via flash zip from recovery, not sure there are some for N1, try to search. )
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Which is why I am nervous at the idea of trying to make such a backup.
On a sidenote, RomManager is indeed able to flash both CWM and RA recoveries for N1 directly, which is quite nice indeed.
yannack said:
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Click to expand...
Click to collapse
I still do not understand why all this. Just flash a working recovery from fastboot (should press power and trackball IIRC on your phone). (And obviously do not use CWM to perform backups when it bricks your phone.)
On another note, flashing removery via ROM Manager resulted in bricked phones for many users, would avoid it personally.
Hi Folks, I hope this is posted in the right forum and sorry if I've missed seeing something similar already here.
I have a rooted Verizon GSIII on which I have been flashing custom ROMs and restoring nandroid backups without any problems for a while now (most recently I've been on Paranoid Android). Today I decided to try out Carbon ROM. I generated a nandroid backup using TWRP, then downloaded the ROM (the most recent nightly) and Gapps zip files using GooManager and flashed these after doing a factory reset. After rebooting the phone it seemed to start up OK... but it got as far as trying to find the network, which it unable to do. After selecting the skip option I then tried to sign in to my WiFi, but the keyboard didn't show up for me to type in the password. So I figured I'd cut my losses and just reboot into recovery and restore my PA backup. I was able to reboot into recovery and restore the backup but the PA backup pretty much did the same thing the carbon ROM did... just looped trying to find the network.
So... I'm not sure what went wrong or what to do next. Any suggestions???
I am able to boot the phone into recovery, but I'm afraid to start messing around too much without help as I'm no expert!
I do have the most recent nandroid backup and several earlier ones that did restore OK on my computer. Is there a way to flash any of these to the phone or to go back to stock?
Any help would be greatly appreciated.
Cheers.
Wipe catche dalvik factory reset then flash fresh batch of rom and gaaps if that works well getting tru start up then flash ur backup thats what i did.. If that dnt work then u gotta go tru odin back to stock
Hi,
Using Kit Kat 4.4.4 here and I bought TWRP Live Backup. Since yesterday, 10 hours ago , the Live Backup is on: Backing up: /system. Never changed. Cant even abort it. Battery is at 2% already.
I have root, is perfectly working. Just updated su binaries. Why the live backup is not working?
douglasrac said:
Hi,
Using Kit Kat 4.4.4 here and I bought TWRP Live Backup. Since yesterday, 10 hours ago , the Live Backup is on: Backing up: /system. Never changed. Cant even abort it. Battery is at 2% already.
I have root, is perfectly working. Just updated su binaries. Why the live backup is not working?
Click to expand...
Click to collapse
Make sure to use latest "busybox" by Stericson. Which custom recovery version are you actually using? Latest "TWRP" should work for it.
And in my opinion its not a beag deal to simply boot your phone into custom rcovery and doing a full "nandroid backup". For me this won't take longer than 5 minutes inluding shutting down and rebooting my phone. Doing a "live" backup doesn't bring any advantages but chances that your backup fails for some reason. Try to backup your phone without your new app. If it works, you can check out why the live backup stucks.
Hi,
Thanks for the reply.
I do have the last TWRP, 2.8.5.0.
Busy box is 1.23.1.
I thought the live backup was an online backup.
There is Classic Backup and Live Backup. Both are done with the system up.
The point of making a backup in the system, not in recovery mode is the possibility to automatically do it, instead of manually.
I've been trying to weasel my way into a stable marshmallow rom, or even stock updated ota. So earlier today I did a backup with twrp before I tried to flash (clean wipe first of course) cm13. I tried to restore the backup, after it was successfully completed and the restoration process only took 47 seconds.. obviously something went wrong with it. So I took out the battery, rebooted it and tried to restore it again to find the backup was gone. Same directory though I also checked the external sd. I mean thats not even a big deal bc I have another backup, but does anyone know why a backup would just disappear?
Thanks and happy flashing!
E6683 (dual)
Stock Malaysia ROM (MM 305)
Rooted with rooted stock kernel
TWRP is 3.0.2.0
I've had this setup for months working nicely.
I did a full TWRP backup, tried N, didn't like it (for now) and so did a restore from the backup. Following a restore, it is stuck in Recovery! As in, when I reboot System, it just bounces back to Recovery.
I could try putting stock MM back on and then restoring, but before I do, are there any quicker tricks to getting the TWRP backup working again?
TIA
m
You should have switched back to MM before restoring your backup.
There are no other way around you have to switch back to THE SAME VERSION OF MM you were using during the backup.
Don't try this in the future you could brick your phone
Baradoura said:
You should have switched back to MM before restoring your backup.
There are no other way around you have to switch back to THE SAME VERSION OF MM you were using during the backup.
Don't try this in the future you could brick your phone
Click to expand...
Click to collapse
Interesting... thank you. I would estimate I've done a TWRP restore across all phones perhaps 500 times. At a guess, I'd estimate 80% between the same version, so maybe 100 between versions. On this particular phone, this may be the first time I've tried it - I forget, I do so many. So, I'm intrigued: why? Or to put it another way: do you know what it is that TWRP fails to back up successfully or indeed restore successfully that causes this problem in the first place?
EDIT: I restored the MM stock rom (re rooted) and restored the TWRP backup and it worked fine - i'm back on MM.