Just wondering what course of action I should take. If anything could get me back to my first nandroid. I just rooted my phone, and I started trying out roms, seeing which I liked best. Not sure how it works exactly, but I figured it was that I could go from one nandroid to any other and it would work. I flashed mik3d, made a nandroid, and then flashed destroyer. All correct steps done, all fine up until that point. Tried to restore, and neither of the nandroids worked. And i tested them before I flashed destroyer. I was stuck in destroyer. Since then ive been able to flash either destroyer or mik3d, but i tried cyanogen and it gets me stuck in bootloop no matter what I do. After flashing mik3d or destroyer, it let's me restore to the last backup before the flash. No other. I backed up my apps originally, but not the data. i guess i just wanna know if I could find a way to restore the original nandroid and get my apps back instead of losing all the data. Also, mik3d is currently running EXTREMELY slow. Computer unavailable for the next few hours, typing this on my phone, and its so laggy. This has taken about 15-20 minutes to type. And if there really is no way to restore my app data by restoring the original nandroid, then what should i do to restore to stock ROM, rooted or not, doesnt matter.
OK, first off, if you're just rooted, you probably have Clockwork Mod for recovery.
You want to change that to Amon Ra.
There's a post in the development section with the file and how to flash it.
This will make your nandroids obsolete.
If you DO have Amon Ra now, or after you flash it, so this:
Go to Wipe.
Wipe All User Data/Factory Reset.
Then wipe ever sub-option, EXCEPT, SD Card: or Battery Stats if you're not fully charged.
Hit return and USB Toggle. Put the ROM you want to flash on your SD Card, then you can flash that. If I were you, I would just use the Stock/Rooted ROM from the Dev section first. You need to have a Sense ROM anyhow, if you ever need to update PRL, Profile, or take your phone into Sprint.
Once you have that loaded up, go back to Recovery and make a Nandroid of it. I always backup everything except cache, which ensures that if I have to restore, it's exactly back to how I had it all set up.
Then, put a custom ROM on that you want to flash, repeat the Wipe Procedure and flash away!
Well I'll try all that when I get home. In the middle of a 4 hour drive now. But I realized that I might have an out. Just got a new SD card yesterday, and I was using that. Switched to the old one, which happens to be after I loaded mik3d but not yet destroyer, and I'm back to the stock Rom rooted. I'll deal with the rest later.
Related
I rooted using unrevoked3 and did the nand unlock. Did a nandroid backup and installed the latest cyanogenmod to play. I've done this before and gone back to my previous rom using nandroid restore. The only thing different is I looked at ROM manager this time and it asked me if I wanted to install clockwork recovery (which I thought I already had so I didn' think much about installing). Now when I try to do a nandroid restore I get errors, and I can no longer boot into cyanogenmod. I can get to the restore screen and it seems to find my nandroid backups, but when I attempt to apply them I get "Error while flashing boot image". Now when I do a full bootup it goes straight to bootloader. I don't seem to be able to do anything from recovery with my nandroid without errors.
I was able to get back
I honestly don't know how I did it. Perhaps I wiped data and it was able to get back to a clockworkmod backup I had previously done. Regardless, I am back and can flash again. Kinda scary though. I am a computer guy, but new to android dev. My advice is to read, read, and read more. You need to understand the steps, not just do them.
NashTnGuy said:
I honestly don't know how I did it. Perhaps I wiped data and it was able to get back to a clockworkmod backup I had previously done. Regardless, I am back and can flash again. Kinda scary though. I am a computer guy, but new to android dev. My advice is to read, read, and read more. You need to understand the steps, not just do them.
Click to expand...
Click to collapse
always wipe data & cache before flashing again, that's why its all over the forums...MAKE SURE TO WIPE PRIOR TO INSTALLING ANYTHING...glad it worked out for you tho
I'm also rooted via unrevoked3.1, but I haven't unlocked nand yet. I also tried restoring from a nandroid backup (after clearing data and cache), and, though it said it completed successfully, when I booted, it was just the stock setup that was on the phone the day I bought it.
I assume it's because I don't have nand unlocked-can I ask what method you used to unlock nand?
use toast part 2 ...
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
crater said:
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
Click to expand...
Click to collapse
If you are using CM7, does this mean you upgraded to one of the CWM3 recoveries? Not sure if this has changed, but backups made with the older CWM2 recoveries are not compatible with CWM3. You will need to reflash back to the older recovery before restoring your backup (pretty sure there are lots of warnings about this in the CWM3/CM7 threads, so you should probably check those out to see if this is no longer the case).
I used CWM3 to make the backup, i assumed that would work to restore it.
EDIT: Okay. so CWM3 can't handle ANY Froyo, regardless of if the backup was made with it. Misunderstood that part. Flashed to CWM32 and it worked. Thanks.
So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...
RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks
Hey all, I had Clockwork installed, and needed to flash stock to take into sprint. I tried to do a backup 5 times, but it kept freezing up on me. So i rebooted and went into ROM Manager and flashed Amon Ra. I rebooted into that, and did a backup, and it said it went fine. I checked the sd card and the backup file was about 500mb which is what it should be. I flashed the stock rom, took into sprint, and then went to restore the backup. I did a full wipe before restoring, and then went to restore. It started with the dots across the screen, but never stopped. I waited over an hour, and it kept going with the dots, which I know shouldnt take more than 10 minutes tops. So I pulled the battery, did another full wipe, and did the restore again.
This time the restore took about 5 minutes, I rebooted, and my rom's boot animation started playing, a good sign. However after the boot animation, all I can see is the stock HTC rainbow bubbles background (which was not my wallpaper) and I also see the Mik rom status bar. But nothing else. No lockscreen, no apps, no nothing. I have since tried multiple battery pulls, multiple wipes and multiple restores again, and the same problem still happens. I flashed the stock rom again, and that works fine.
So am I pretty much screwed here with this backup? Unfortunately, I did not use Titanium to backup my apps and texts, as I figured it would just be a quick flash to stock to take into sprint and then a quick restore.
You might be screwed. I was having that problem. I switched to amon-ra haus mod and I back up everything but recovery. Wipe cache and dalvik cache before and after and it works fine. But right now you may be S.O.L.
We're comin from a pure power source.
Did you try rflashing the rom and then restoring? Just a thought
We're comin from a pure power source.
metalfan78 said:
Did you try rflashing the rom and then restoring? Just a thought
We're comin from a pure power source.
Click to expand...
Click to collapse
I'm trying to do that now, reflashing the base mik rom, then I will try a restore without wiping, hopefully I can get all my apps back long enough to back them up, and then I will do another full wipe and flash
Edit: well that didnt work at all, a restore just puts me back to where I was, just a backround and status bar, no buttons or lockscreen or anything. I guess that backup is corrupted. So much for Amon Ra being better than clockwork...
This is the only recovery that has worked flawless for me. Its amon-ra haus mod. I don't know the difference I just know it works.
http://db.tt/cFafuzp9
Give it a shot
We're comin from a pure power source.
Not that it's the cause, but you shouldn't use ROM Manager, for any reason, really and definitely not to flash recovery.
The best way is the PC36IMG.zip from the thread for AR in the DEV section, flash it in Hboot and then try to flash your ROM, after you wipe everything, except the SDCard: option.
I've tried StockCWM-EL26 and Philz Touch. Both make nandroid backups without errors and restore without errors. But when I boot up after restore, I get constant popups for apps missing and crashing.
I'm to the point were I don't want to flash anything because if something happens and I want to go back, I have to start from scratch every time.
unknownsoldierx said:
I've tried StockCWM-EL26 and Philz Touch. Both make nandroid backups without errors and restore without errors. But when I boot up after restore, I get constant popups for apps missing and crashing.
I'm to the point were I don't want to flash anything because if something happens and I want to go back, I have to start from scratch every time.
Click to expand...
Click to collapse
You should not use Philz to backup or restore. I have only used Philz to flash. Once I am on the ROM, the ROM's custom recovery is sufficient enough to do backups and restores. Most of the ROMs have a custom recovery already installed. Let's say you wanted to flash villuminati. You would use Philz to flash the ROM and Gapps. Once you rebooted into recovery again, you should be on CMW. You don't need anything else. In my time of being here, I have only used EL29 to get from AGATs recovery. AGATs is not good for flashing ROMs, so most ppl use EL26 or EL29. Try it this way and see if everything works. Remember, Philz should be used only to flash, never for backing up or restoring. Let me know how it works out.
I'm currently on stock JB and everything runs fine. I need a recovery I can flash to make a nandroid of my current setup, before flashing another rom.
In my experience with my previous phone, once I found a custom rom that I liked, I pretty much never needed to make a nandroid for that rom. But I need a reliable way of restoring my current stock setup.
I actually don't intend to use Philz for anything ever again. I was already aware that it wasn't good for backups, but the last time I used it to flash Liquid Smooth ran into a bunch of trouble. I didn't like the way the rom was running, so I booted into recovery and flashed Philz to use it's convenient "wipe for new rom" to make sure everything was clean for restore (I like that it deletes .android-secure on both SD cards.) Then I needed to flash StockCWM-EL26 to restore the nandroid, but when I tried to do that I just got an error 7. I tried flashing different recoveries, roms, modems. All gave errors. Philz wouldn't do anything. Had to hook phone up to the computer and flash StockCWM-EL26 using odin. Then I restored the nandroid, booted up and everything was fubar. Hooked up to PC again, flashed stock image using Odin, and set everything up from scratch.
unknownsoldierx said:
I'm currently on stock JB and everything runs fine. I need a recovery I can flash to make a nandroid of my current setup, before flashing another rom.
In my experience with my previous phone, once I found a custom rom that I liked, I pretty much never needed to make a nandroid for that rom. But I need a reliable way of restoring my current stock setup.
I actually don't intend to use Philz for anything ever again. I was already aware that it wasn't good for backups, but the last time I used it to flash Liquid Smooth ran into a bunch of trouble. I didn't like the way the rom was running, so I booted into recovery and flashed Philz to use it's convenient "wipe for new rom" to make sure everything was clean for restore (I like that it deletes .android-secure on both SD cards.) Then I needed to flash StockCWM-EL26 to restore the nandroid, but when I tried to do that I just got an error 7. I tried flashing different recoveries, roms, modems. All gave errors. Philz wouldn't do anything. Had to hook phone up to the computer and flash StockCWM-EL26 using odin. Then I restored the nandroid, booted up and everything was fubar. Hooked up to PC again, flashed stock image using Odin, and set everything up from scratch.
Click to expand...
Click to collapse
The one thing I found out about these phones, is one thing may work for me buy not for you. It is the nature of the beast. Glad you were able to get things back up and running. Don't get discouraged. You should keep a copy of the one-click on your PC just in case you need to get back to stock. I have both the FL24 and GB27 for that specific reason.
Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2