Hello,
Im using the TeamRogue's recovery (1.3.0) and I made a backup using this, before trying out a rom.
Now i wanted to go back to my backup, so i restored it, however it is stuck at the asus eee pad screen (boot screen).
I've seen more people with this problem and some say wiping the cache after the restore fixes it. Or when using the Super Wipe script, reboot after wipe and then restore.
Now after a lot of tries and wipes i finally got it booting fine.
However, me as stupid as I am, I tried another rom, so now I got the same problem, however only this time i can't get it to work.
Any help appreciated!
Kind regards,
ps. sorry for the grammar mistakes
What ROM were you on when you made a backup and what ROM did you try out?
If you went to an ICS base ROM and went back to a HC base ROM, you must get a HC kernel back, you can achieved this by flashing the HC ROM after your backup is done restoring.
I was on ICS and i flashed a ICS rom.
I also know about the kernel thing, ive flashed to my 3.2 backup to with no problem.
It just hangs on boot, has to be with \boot partition
Saw a few reports of this in the Team Rouge thread.
Same way to fix, nandroid restore and once it's done. immediate flash the ROM the backup is based upon. (No wipe if you want to save your data).
I had this happened to me going once going to an older ICS backup.
So.. to make this clear, i made a backup of the stock ICS.
So, i have to restore my backup and then flash a stock ICS rom or will EOS or some kind work to?
pretty much it is because eos is asop and stock is stock and some things that are different between the two are not restored when you restore a nandroid
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
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 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
I have a couple of questions, been digging around xda and the web and found some conflicting answers...
1) Does a Nandroid backup also back up the kernel? I'm thinking about dabbling with some custom kernels, but don't want to potentially mess things up as well as have an easy way back to the stock kernel if I don't like the custom one for one reason or another.
2) What would happen if I made a Nandroid backup from recovery, did a full wipe (/data, /system, /sdcard, caches), rebooted then restored from the Nandroid backup?
I'm still pretty new to all this but I've done some reading and a wee bit of flashing & rooting on Nexus devices and the HP Touchpad. I also have an old TF101 that I'd really like to tinker with as well.
Thanks!
cardula said:
Hi
I have a couple of questions, been digging around xda and the web and found some conflicting answers...
1) Does a Nandroid backup also back up the kernel? I'm thinking about dabbling with some custom kernels, but don't want to potentially mess things up as well as have an easy way back to the stock kernel if I don't like the custom one for one reason or another.
2) What would happen if I made a Nandroid backup from recovery, did a full wipe (/data, /system, /sdcard, caches), rebooted then restored from the Nandroid backup?
I'm still pretty new to all this but I've done some reading and a wee bit of flashing & rooting on Nexus devices and the HP Touchpad. I also have an old TF101 that I'd really like to tinker with as well.
Thanks!
Click to expand...
Click to collapse
I don't know much about kernel but I do know that Nandroid backup backups everything exactly where the phone is.
That means if you do factory reset and restore Nandroid backup it will restore everything from the day you made the Nandroid backup.
I hope it clarifies everything.
Let me answer your questions.
1. When you do a nandroid backup, it backs up everything. Including the kernel.
2. If you nandroid backup, factory reset your device then restore your nandroid backup. Your device will return to the same state you had it previously. You will have all your content, files and settings. However if you do a backup, then factory reset and reboot, your device will be wiped of everything but it will boot up. As if the device was just turned in upon purchase. Also note, if you do a backup, then wipe your device (factory reset) you will not lose your backup.
Just note, if you ever flash a ROM, even if the developer states there is no issues. MAKE A BACKUP, sometimes things go wrong.
Happy flashing
If I helped, don't hesitate to hit that Thanks button
Thanks for the quick replies!
I was a bit confused about 2) because I read somewhere that if you make a nandroid backup of a stock ROM, then install a custom ROM (non-Stock based ie CM, PA or OmniROM) you must flash the stock ROM again before you can restore the nandroid backup, or else restoring the nandroid backup will not work. Is this true?
Consider the following example, say I:
-flash TWRP on my device and root
-make nandroid of stock, rooted ROM
-wipe /data, /system, /sdcard and caches and reboot back into recovery
-ADB push a non-stock custom ROM .zip file and flash the custom ROM
-decide I want to return to stock, rooted ROM after a while
-Boot into TWRP, then wipe /data, /system, /sdcard and caches and reboot back into recovery
-ADB push my original stock, rooted nandroid backup to /sdcard while in reocvery
-restore nandroid backup
What would be the outcome of the above example? I'm very curious...but I'd like some advice before attempting something like this myself as I'm still kinda new to all this
BTW I'm now comfortable flashing back to stock using fastboot and the google facotry image to restore a Nexus device so I now know how to do this in case things go south. I'm just curious if this would work on a device where returning to a full stock state isn't so easy.
No you don't need to install anything to get back to the previous state. So if you had a stock rooted ROM, then backed it up. But you decided to flash, let's say. Cyanogenmod but you wished to return back to stock, you don't need to flash stock ROM, all you have to do is just wipe data and restore your backup.
And for the example.
The outcome would be, you would be resulted with a stock, rooted rom.
If I helped, don't hesitate to hit that Thanks button
Thanks again, krishneelg3 for the quick reply. Been wondering about this for a while.
Cheers
No worries, if you have any other questions to ask, just ask. xda is a giving community !
If I helped, don't hesitate to hit that Thanks button