I've been curious about a few things. For one, is there a "proper" way to restore a backup from TWRP? Should you do a wipe first before you restore, or does that not matter? Let me give an example of an issue I ran into. I have a (Verizon) Galaxy Nexus, and I've mostly stuck to AOKP, but a while back, I wanted to try out a different ROM. This was back when TWRP was on version 2.4.x.x, so maybe it was just an issue with that. But anyway, I made a backup in TWRP, did my wipe, then flashed the new ROM to play around with. I played with the new ROM a little, but ultimately decided I didn't like it. So I went back into TWRP, wiped again, then used the restore function to go back to the backup I made. When my phone rebooted, though, I was dismayed to find that lots of stuff did not restore properly, and I had to waste a bunch of time fixing things that didn't restore. I was under the impression that when you restore, it just returns exactly the way you left everything before you wiped it out?
Also, I'm doing something similar now, on 2.6.0.0 of TWRP. I wanted to try a new ROM, so I made a backup, wiped, flashed the new ROM, played around with it, and decided to restore my previous backup. The backup file was about 7GB. My phone seems to be "stuck", though, in the recovery process. The bar is all the way at the end (the little slanted lines are still moving), and it's been stuck at "Restoring data..." for about 10-15 minutes, now. Is this normal? I don't remember it taking this long before, although I've only ever restored a backup a handful of times. Should I just leave it alone, or should I pull the battery, or what? I don't want to screw anything up, but I kinda need to have my phone working within the next five or so hours...
Related
My phone is mullered :-(
Whenever I flash a new ROM, all I get is a constant boot loop on first boot.
Flashing a different ROM results in the same behaviour.
The only way out of it is to re-root, taking me back to version 1.15 or something, and then if i try to flash a new ROM - you guessed it, boot loop....
This first started when I had OpenDesire installed, which was fine to begin with, but then it randomly rebooted and started boot looping.
Since then I've tried about 4 or 5 different ROMs and nothing changes.
Any ideas as to what's wrong/a solution?
Just to add, I have one the lastest radios (.08) when I try and flash.
Perhaps flashing the radio after might help?
After much struggling, I've managed to sort it.
Ended up clearing storage in recovery, which helped so long as there was no SD card in it. Had to format and repartition the card, and fingers crossed, all seems well now.
Whenever you change between diferent ROMs it is a good practice to do a full wipe via recovery. 90 to 99% of the boot-loops can be fixed doing it...
The strange thing is that I did wipe between ROMs. I'm not sure why I had a problem this time round, as I haven't had with the previous 10 flashes...
Still, it's sorted now
Funny.. found this thread via google.
I'm having the exact same issue where no matter what rom I flash it gets stuck on bootloops during the startup animation and never makes it into the rom.
NANDroid backups are perfectly fine to restore, just unable to flash any new roms. Spent all last night trying everything from swapping recoveries, to re-rooting, flashing multiple roms, urgh.
Only thing I didn't try is re-formatting the SD card so gonna give that a go now (thanks to this thread) and report back later.
Annoying to say the least.
Well what do you know... a 'partition my SD card' through rom manager (after copying said contents to my computer) worked a charm.
Most interesting......... Praise this thread and any others that gain help from it.
Did you update your radio ?
Sent from my spectrum zx
Man i'm lucky. Two hugely annoying problems in one go.
First up, yes I have replaced my radio, many times The SD card was obviously not too happy with its ext partition, so repartitioning that worked.
I also had another issue crop up straight away that was probably caused by unhappy sdcard, where when restoring apps via titanium backup, phone would reset.
After running a RRU, re-rooting, all the full works.. I find that some of the apk backups are 1kb... Which is not normal. There were about 15 apps like this. I had a backup of these apps from a week or so ago and copied those to the titanium backup directory, restored, no problemo.
Even more annoyingly TB has a verrify backups option which reported all was well. FML.
Well that was a fun morning. Time to finally get back on track *sighface*
This evening I was playing around with my Evo and got thinking, "I really like how everything is running right now! I've been running SteelH I.2 ROM stable for a few weeks, launcherpro, all my homescreens setup... perfect! I should take a backup."
I reboot into recovery, take a nandroid backup, then go to reboot the phone. Backup completed without any errors, but the phone would not restart. It sat at the white HTC and would not budge. I removed the battery several times and rebooted, but nothing. I could still get into recovery, so I wiped data, cache, dalvik and attempted to reboot. Again, nothing... just sat at the HTC screen. At this point I was thinking, "great... gonna have a long night ahead of me troubleshooting this one." I restored the backup I had just taken about 30 minutes earlier, but wasn't very confident that it would help at all... reboot, and after a few seconds, my boot screen starts loading!
So, here is what I am wondering.... I had not done any "hacking" since the last reboot... just installed/uninstalled a few apps from the market. What could have caused my phone to react like this? Also, if it wouldn't reboot in the first place, why did restoring the backup work? I had just taken the backup a few minutes earlier....
thanks!
Well, that certainly is unique. I've had problems doing nandroid back-ups (recovering from and creating them) before but it always booted just fine no matter what happened. Maybe there was a small software error that was fixed when you recovered.
Either way, I wouldn't worry about it. Recovering a nandroid back-up = problem got deleted.
That's why I tell everyone to nandroid before doing anything
Am trying to do a nandroid backup using Amon-Ra 2.3, and it just keeps laying down line after line of dots, taking much longer than I would expect, and never finishes. I've tried the suggestions in this thread on the issue, and I'm still having no luck.
Anyone have any suggestions/wisdom to offer? I've let it go for 20-30 minutes on a couple of occasions, and it's still not working -- I just end up with a screen full of dots.
Part of the reason I'm doing this is that I've been having issues with my wireless, data, etc toggling on and off on its own lately, so I thought a fresh start with a new ROM might be worth a go. Doubt that's related, but who knows, so I'm throwing that out there in case it matters.
Thanks!
PS Currently running VirusROM Airborne RC 6, to the extent it makes a difference.
What rom are you trying to restore?
If you wanted to start fresh, than you can install your new rom fresh, then restore all your apps+data, just not system settings.
I wasn't trying to restore anything, I was just trying to do a nandroid backup so I could flash another ROM. With that said, I've tried to restore an older backup to make sure I had one that worked, and that isn't working, either -- just an endless stream of dots. If I pull the battery in the midst of a restore, will I screw anything up?
jrtoastyman said:
I wasn't trying to restore anything, I was just trying to do a nandroid backup so I could flash another ROM. With that said, I've tried to restore an older backup to make sure I had one that worked, and that isn't working, either -- just an endless stream of dots. If I pull the battery in the midst of a restore, will I screw anything up?
Click to expand...
Click to collapse
No it shouldn't.
http://dl.dropbox.com/u/19699565/PC36IMG.zip Place that on your sdcard, and flash it in the bootloader, that'll re-flash amon_ra 2.3; hopefully that should fix it.
thanks man, I'll give it a try.
Aye aye, and I shall be around if it doesn't work.
well, I'm stuck in the back end of the boot animation now. Hmmm, very frustrating. How horrible would it be to just do a factory reset of the phone? Would I have to re-root?
jrtoastyman said:
well, I'm stuck in the back end of the boot animation now. Hmmm, very frustrating. How horrible would it be to just do a factory reset of the phone? Would I have to re-root?
Click to expand...
Click to collapse
If you do a factory reset, that just erases all data. You should always wipe the factory/data, cache, and dalvik cache in recovery before flashing a rom for the first time. You don't have to re-root, just restore your apps from titanium backup.
OK, so here's where I'm at:
1. I can't perform a nandroid backup
2. I can't restore any of my previous backups
3. I can't boot the phone to allow me to flash the new Amon-Ra you provided.
With all of that being the case, I feel like I'm sort of out of options at this point -- maybe just wipe it and flash the new ROM, hope for the best, and perform a nandroid after the flash? Can't really get any more screwed than I am now, right?
jrtoastyman said:
OK, so here's where I'm at:
1. I can't perform a nandroid backup
2. I can't restore any of my previous backups
3. I can't boot the phone to allow me to flash the new Amon-Ra you provided.
With all of that being the case, I feel like I'm sort of out of options at this point -- maybe just wipe it and flash the new ROM, hope for the best, and perform a nandroid after the flash? Can't really get any more screwed than I am now, right?
Click to expand...
Click to collapse
What do you mean you can't get to the bootloader?
Power the phone off/battery pull, upon turning on, hold vol+down till you see the white android screen, then it'll scan for the PC36IMG, which you apply update, then reboot. And it can still be saved.
I guess the question was how do I get the file onto my phone when I can't get the phone to boot up, but it occurs to me that I can pull the card out and load it on there that way, so let me give that a go and follow those steps. Now, I've just got to find that little card adapter thingy...
Thanks again, appreciate the assistance
Ah yes...the adapter...tis why I just always leave it in my laptop. But that will work, and you're welcome.
that did the trick, back up and running. Whew!
Much appreciated!
Glad that it worked.
I'm on an EVO 4G running Fresh 3.5.0.1 with Netarchy Toastmod 4.3.4 cfs havs-less no sbc. I'm currently using ClockworkMod recovery 2.6.0.1.
Last weekend, I wanted to try Synergy with GodMode. I don't know if it wasn't in the thread when I read it (I see the thread's been updated since my attempt), or if I just missed it, but either way, I was unaware that I couldn't install the GodMode ROM with ClockworkMod.
So I did a Nandroid backup and attempted install (I'll admit, I initially forgot to wipe data/davlik/cache). It seemed to install fine, but then couldn't make it past the boot splash. So I figured I'd cut my losses and just restore my backup. After restoring, it once again got stuck at the bootsplash (never had this issue in the past). And when I say stuck, I mean I let it sit at the boot splash screen for 5-10 minutes, pulled the battery, repeated (including wiping everything), and it could never get past it. To get the phone working again, I had to restore to a much earlier Gingerbread Deck backup that I had made while fooling around with that ROM, then I was able to restore the most recent backup without issue.
Fast forward to this evening. I figured I'd try again, but now I know I need Amon_RA's recovery. So my plan was to do another Nandroid backup, install Amon_RA, and try Synergy with GodMode. I never made it past the first step... after creating the backup (no changes were made, just the backup created), the phone wouldn't progress past the boot splash. I had to go to an earlier restore point (last weekend's) to get the phone to work. Tried restoring today's backup after getting it to work on the old backup, no luck.
Thinking perhaps the attempted GodMode install messed something up, I did a fresh install of Fresh 3.5.0.1 (pun semi-intended), fresh install of my kernel, and then tried restoring the most recent backup. Once again, couldn't get past the boot splash.
I feel like something is seriously wrong, and I don't feel comfortable going into recovery to make any changes until I have some insight into what the issue is.
To make matters worse, I rely on 4G tethering for internet, and have no landline, so if the phone is bricked while trying to resolve this issue, I'll have no resources to get help.
Any help is GREATLY appreciated. I've searched, but it seems that the problems everyone has that are like this occur immediately after changes are made and are remedied by wiping data/davlik/cache. I made no changes this evening, and wiped everything multiple times in my many attempts.
Edit: Almost forgot, some things did stand out as I was trying to get it to work.
While whiping Davlik, I was given the line:
E:Can't mount /dev/block/mmcblk0p2
(File exists)
While restoring today's backup:
sd-ext.img not found. Skipping restore of /sd-ext/.
There was a nandroid restore issue using a previous version of twrp that was remedied by restoring nandroid and then flashing the rom over top of the nandroid. Maybe try that
Sent From My Pocket
Ok I had the same problem. I wiped everything three times also wiped dilvak (might have spelled wrong) cache, and wiped battery stats. Then flashed it. It took forever also close to 15 mins. This is what I did I hope it helps.
Just a followup: I decided I could do without restoring to that specific backup (tried restoring it after wiping data a few more times, but oh well). I only installed a couple apps and changed a couple other things since the last backup that worked, so I installed Amon_Ra since it seems to be the consensus that it's a better recovery and made a backup with that... rebooted just fine afterwards.
So, I rebooted my phone this morning (old habits die hard) and it made it loaded...then froze on the lockscreen. There was a slight graphic glitch on the screen too. So, I pulled the battery and rebooted again. And the same thing happened. So, I tried again. And it just hung on the boot animation. Not "boot looping", per say, since it never started over, just going on and on and on. Tried clearing the cache and rebooting. Nope. Finally, I tried wiping the caches and system, reflashed my ROM, and watched as nothing changed.
So, I accepted my fate, made a nandroid, wiped everything, and started fresh. This isn't a big deal, EXCEPT I lost all the info from my expense manager app (I like to know how much I spend on beer each month). Now, I've tried pulling the data from the nandroid (with Nandroid Manager, Rom Toolbox Pro, and Titanium Backup) to no avail. I was able to pull the data out for a couple other apps, but not the one I really want.
So, is there anything I can do?