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
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,
I have the nvflash recovery thing on my G2x and there is this very weird thing that happens that I was wondering if anyone else experienced.
The first time I flashed the CM7 I backed up the whole thing and restored and everything was fine. Then I did some stuff and backed up again except this time when I restore all my apps are gone and none of the widgets work so I restore the first backup again and everything is fine. Then I add all the stuff I added on stock and backup again. Then I restore the new one and the same thing happens but when I restore the first backup everything is fine.
Am I doing something wrong? Or has anyone experienced this before?
Are you performing a WIPE before you restore from the NANDROID Backup?
When ur backing up the rom u don't wipe anything rite? Just go into recovery and backup? Cuz ur not supposed to wipe anything just go in and backup
Yes, I am performing a wipe before I restore and no I'm not performing a wipe before the backup lol otherwise there would be nothing to backup
I have a updated g2x (gingerbread via Lg updater) installed NVflasher was able to boot into recovery performed a nandroid back up did a full wipe and was going to flash Xbroarders rom until i relized i put it on my internal instead of external so i then tried to flash my back up and got "no file found"did a reboot and all im getting is a black screen wit flashing keys. plz help
Hi. I've been using a ROM for the last little while (SlimICS), and I like it, more or less. There's a feature in another ROM (ParanoidAndroid, per-app density), that I'd really like to try out, but this ROM also has a lot of features I don't want (tablet mode) and doubt I would like. I use TWRP as my recovery...if I use TWRP to make a backup of System, Data, Boot, Recovery, .android_secure, and EFS, will I be able to flash this other ROM, then restore the backup to go back to my old ROM after I play with the new one a bit? Will the backup of these items bring me back to exactly how it was before, if I do a Wipe Cache/Dalvik Cache/Factory Reset?
Sorry if these questions are answered elsewhere, I'm just trying to make sure that my limited understanding of all this isn't incorrect, in my specific situation.
If you make a backup through recovery, when you restore, it'll be exactly where you left off, settings and all, when you shut the phone down.
When backing up in Recovery, you are backing up the OS and apps. This is called a nandroid. This does not backup anything on the sdcard.
Yesterday, I flashed a different kernel version on my NS. Before flashing, I did a nandroid backup using Reovery. Unfortunately, the kernel failed to load properly and I was stuck in a boot loop. I restored my backup I have done previously, and my phone was back where it was, few minutes before. It is very easy to do and backups/restores and verified using MD5 checksum.
Keep in mind that some apps put stuff on the sdcard. So if you flash your phone to a new ROM, upgrade apps and then go back to another ROM, it is possible that some apps won't work anymore. I've never seen this happen but this is a possibility.
I downloaded Trickdroid and everything is good. before I did the download I backed up stock in TWRP.
When trying to restore stock it says 'completed' in about two seconds and when I then reboot I'm still on Trickdroid.
Was I meant to do a nandroid in cwm? Can't think why TWRP wouldn't just restore.
Obviously I still have the stock image on my sd card in the recovery folder of TWRP, so would there be any other way of flashing/installing it whilst bypassing TWRP if I have to?
I faced a similar problem and I freaked out. I installed MIUI to test it and then after I tried to restore my Trickdroid nandroid. Every time I boot the phone after restoring, it kept asking if I want to use the miui launcher and then an error appeared saying your phone has stopped and nothing works.
I did wipe everything (system, data, cache, dalvik) but the same thing happened over and over. It also refused to install any new ROM. I thought I had a brick. Then after a couple of reboots to recovery, I could install a fresh trickdroid and then on top of it I could restore my nandroid.
Now I am weary of installing anything new. I have a CWM nandroid as well just in case.
Sent from my HTC One S
I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so
Just had an idea, would it make a difference if I flashed the new boot.img before wiping the current ROM? meaning, before restoring trickdroid, I flashed the kernel of trickdroid.
Because yesterday I had the same experience again this time with CM9 and I had to make a fresh install
Sent from my HTC One S
torxx said:
I included a script which does not allow you to switch from Trickdroid to another ROM as it's the best anyway
Just kidding, try to reflash your Recovery or so
Click to expand...
Click to collapse
Don't worry, I'm sticking with trickdroid, just wanted the peace of mind of knowing I could go back to stock anytime.
Now I can't, I'm stuck with you
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
****, good question
Sent from my HTC One X using xda app-developers app
Restore takes care of wiping for you.
Piggybacking off the OP, sometimes when I try to restore my TWRP backup it fails, and then the only way I've found to get it working again is to do a boot loader factory reset, and then essentially start from scratch or load an older working backup. No problem, just a minor annoyance. Is there something I'm doing wrong or any advice someone can give me?
Sent from my HTC One X using xda app-developers app
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I always wipe everything before a restore, just in case
Better safe than sorry
Restoring a back up !
When restoring a back up from any recovery wipe everything just as if you were installing a new rom. Factory reset, cache, dalvik cache, system just to be safe. Factory reset wipes data and all cache but not system and if you do a factory reset and then try to wipe I think dalvik again you get an error but no harm done it just will not do it again. I usually do them all and then do the superwipe zip and that willl give you a good piece of mind that it is properly wiped. Also, I have noticed that using the external sd card seems to work best for installing roms or backing up and restoring back ups or anything else like mods or themes. Here is the superwipe zip in case anyone needs it.
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I've done both, but I like not having reinstall all my apps, and reset all my ringtone, and that goes with a full wipe. so when ever i can i flash over. Just make sure your slashing the same rom over the old one.
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
XNine said:
You shouldn't worry about losing ANYTHING on a backup when you do a factory reset, because the backup houses all of the data and settings anyway.
All you do is Factory Reset, Nandroid>Restore, and your old backup will flash everything the way it was when you did a backup in the first place. Factory Reset is always wise, especially when you're fiddling with different ROM's based on different kernels or systems (AOSP/Sense).
Click to expand...
Click to collapse
Ahh, this is true I recant my statement. I was mistakenly thinking about flashing a new ROM over an older version, not a buck-up. I feel stupid.
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
gunnyman said:
when restoring a nandroid if you've got the new HBoot I think you have to restore boot.img separately via fastboot. Is that right?
Click to expand...
Click to collapse
Nope. I just flashed a bunch of roms yesterday and did restores with no issue. I think if your using the stock rooted 2.2 you are correct, but any other rom a restore works fine.
Not Restoring = Bad Idea
Hydromea said:
Hi, just have a quick question that's been bugging me for a while now. If I have made a full backup using TWRP and I want to restore it, should I:
Fully wipe system and caches and then restore; or just restore right over my current ROM?
Click to expand...
Click to collapse
I have made the mistake of not wiping everything (excluding sd card) when changing ROMs or when restoring from a backup. This may be a little different because it was when I was switching to a new ROM on my brother's phone, but I tried to take the lazy way out and not restore everything. I really didn't feel like redownloading everything. I soon learned that this was a mistake, and his "phone" app suddenly disappeared. He was also unable to send or receive texts. This soon made the process even longer than I wished it to be because I needed to go back and restore everything again and get it back to normal.
Error While Restoring using twrp
I took a back up of everything using TWRP and then when i tried to restored its giving me error while restoring system E:Unable to extract tar archive . Please help
Are you trying to restore a backup from a different version of TWRP? For example, currently running 2.7.0.8 but backup was originally made using 2.3.3.1?
Sent from my Evita
error on backup restore twrp
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
WOW! After a good 3/4 days of frustration, thinking I had ruined my device, I finally got my TWRP backup to restore.
It's my first time using this software and the restoration process is truly amazing. I mean, my test messages were still there, even my browser history and last page loaded up in chrome were still there. I'm blown away.
The strange thing is that It didn't work when all 3 partitions were selected. When I tried it this way (as per the many step by step instructions that I read) my phone would load up a black screen with just the notification bar visible. I'd see my voicemail, sms, wifi and battery icons at the top, but absolutely nothing else except for a myriad of pop ups that read 'Unfortunately [app name] has stopped working'.
So I bit the bullet and did some trial and error with the partitions.
Turns out that when I only selected 2 of the 3 (I believe they were 'Boot', 'Data' and deselected 'System') everything loaded up just as it was before the backup, except there were only the stock apps available and no google services at all. .....Very odd.
So I did the boot to recovery method before turning the phone off (vol. up - Home - Power) which restarted the phone and strangely brought back EVERYTHING as mentioned at the start of this post.
You can probably understand my confusion here and while I'm VERY happy that it all worked out, I don't understand why it worked with only 2 of the partitions but not with the recommended 3 of them?
Can anyone shed any light on this?
---------- Post added at 01:16 PM ---------- Previous post was at 01:02 PM ----------
debmikeshan said:
hi i have a nexus 4 running 6.0.1 reserection remix, however when i do a backup on twrp then transfer
it to my pc its fine, but when i restore it it not going as a zip and its giving me this error, could not find meta-inf/com/google/android/update-binary' in the zip file. error installing zip file/sdcard/twrp/backups/01c237769c62991c.zip please help, thanks
Become a member of the w
Click to expand...
Click to collapse
Hmmm. I'm definitely no pro at this stuff, in fact i'm very new when it comes to using TWRP, but this is what happened with me.
First of all, the backup that I did was simply a folder of files, not zip.
Transferred that do my PC, wiped my phone with TWRP and replaced the backup folder back into the TWRP/Backup folder. However, after reading up on how to restore on about 10 different android sites/forums, only 1 post shared the most vital piece of information.
You folder has to be in the 'serial' number folder that's located in the 'Backup' folder for TWRP.
When I put my backup folder just into the TWRP/Backup folder, the Restore section would only see the folder itself but the partitions were not available/listed for selection.
Once I placed my Backup folder into the TWRP/Backup/e1oog75 (that alphanumeric name is just a random example made for visual clarity) folder, my partitions were visible and available for selection right away.
Hopefully this helps somewhat.