I searched the forum and the internet before this post. I am not able to restore a nandroid backup of fresh. Everytime I do I am thrown into a never ending boot loop. I've tried to install the radio, wimax, rom, and then nandroid restore over that..nothing..ive tried just to do the nandroid restore after a data, cache, and delvik cache wipe. I've tried most of the things that I thought would be logical and I cannot restore my nandroid backup. If I install the ROM things work fine but I cannot restore the nandroid backup. Can anyone point me in the right direction?
Thanks.
CJ
Have you tried removing the SD card right after a nandroid restore?
No. Will try that right now.
Sent from my PC36100 using XDA App
Why do these obvious question and answer type posts keep ending up in Android Development?????
IMO this is a "Question" and "Questions" go in the "Question and Answer" section.... When you want to make a rom, or develop some software come post in this section.
ceejay3k said:
I searched the forum and the internet before this post. I am not able to restore a nandroid backup of fresh. Everytime I do I am thrown into a never ending boot loop. I've tried to install the radio, wimax, rom, and then nandroid restore over that..nothing..ive tried just to do the nandroid restore after a data, cache, and delvik cache wipe. I've tried most of the things that I thought would be logical and I cannot restore my nandroid backup. If I install the ROM things work fine but I cannot restore the nandroid backup. Can anyone point me in the right direction?
Thanks.
CJ
Click to expand...
Click to collapse
What recovery are you using? If it is Clockwork, it doesn't wipe sufficently for Fresh's ROM and thus causes the boot loop problem. You have to wipe using Amon RA's recovery and then reflash Fresh. You could go back to Clockwork after wiping with Amon.
Sent from my PC36100 using XDA App
chazglenn3 said:
Why do these obvious question and answer type posts keep ending up in Android Development?????
Click to expand...
Click to collapse
Because there is a STAGGERING amount of information just in our little corner of this forum and a traditional forum layout is a sh*t way of handling this amiunt of data.
I wish it didn't happen too, but vie moved on to accepting and understanding it. About all we can do is not flip out on people or be rude when we tell them they are doing it wrong. Otherwise they will just ignore us.
Well first to chazglenn3, spiicytuna, and alcaron, I'm sorry for not posting in the correct section. I didnt mean any harm. I forgot about is other sections of supersonic because this page was in my favorites.
Anyway, @uclajw1, I was using amon's recovery and nothing worked. What I ended up having to do was wipe the device (data, cache, delvik), install radio, wimax, restore nandroid backup, and then flash the Rom over all of that and I got into the OS. From there, I was getting FC's like crazy so I reinstalled all the apps forgetting about the feature in titanium backup that I could use to fix file permissions. But for now all is well. That's just a lot of work to do again do i hope I can figure something else out...
CJ
Sent from my PC36100 using XDA App
uclajw1 said:
What recovery are you using? If it is Clockwork, it doesn't wipe sufficently for Fresh's ROM and thus causes the boot loop problem. You have to wipe using Amon RA's recovery and then reflash Fresh. You could go back to Clockwork after wiping with Amon.
Click to expand...
Click to collapse
Why do people keep saying this? Hasn't this been fixed awhile ago?
Related
I had put on CR_Mod_1.35.531_OTA Full ROM with add on it ran fine. I tried a different one did didnt like it. I went back but now can't download anything from the market I get the insufficient storage available, installation unsuccessful. I wiped but did not do the wipe factory reset for fear of not sure if it would get rid of my root. What should I do I have retried several times.
Reflash the rom you are trying to install, this time do a wipe/factory restore within clockwork. You will not lose root.
Edit1: Only time you shouldn't have to wipe is when your flashing an update of the current rom your using. Keep in mind if its a major update, they recommend you do wipe. Another thing I recommend is doing nandroid backups of the roms your using, it really makes life easier backs up EVERYTHING so if you ever have to go back all you have to do is a nandroid restore, search the forums you'll find how to do it. Hope this information helps.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
niftymu said:
Reflash the rom you are trying to install, this time do a wipe/factory restore within clockwork. You will not lose root.
Edit1: Only time you shouldn't have to wipe is when your flashing an update of the current rom your using. Keep in mind if its a major update, they recommend you do wipe. Another thing I recommend is doing nandroid backups of the roms your using, it really makes life easier backs up EVERYTHING so if you ever have to go back all you have to do is a nandroid restore, search the forums you'll find how to do it. Hope this information helps.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
I did a wipe/factory restore put on a working rom but still have the same problem
Did you try wiping cache? Its the option below wipe/factory restore in Clockwork.
Also, make sure your /system, /data & /cache partitions are mounted when in Clockwork, if not anything you do will not be applied. (This includes flashing roms)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
niftymu said:
Did you try wiping cache? Its the option below wipe/factory restore in Clockwork.
Also, make sure your /system, /data & /cache partitions are mounted when in Clockwork, if not anything you do will not be applied. (This includes flashing roms)
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
I redid it again and its all good maybe I missed something the first time.
Thank you for your help and advice
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
KNguyen104 said:
i had the same problem when i tried to update on the g2. i backed up the phone and wipe data and caches and flashed again the it worked you might have to do it acouple of times
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Using the RomManager interface I chose to Wipe Data and Cache and also chose the gapps package to install. I guess I could try it again but I was mystified why it didnt work since I "thought" it was so simple.
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
snowboarda42 said:
If you're coming from a sense rom, wipe cache, data, dalvik, system, boot, basically everything but the sd card. After that, flash cyanogenmod, then gapps, then start the phone.
Sent from my hand with XDA Premium installed
Click to expand...
Click to collapse
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Alpine- said:
I'm an android noob, you'll have to forgive me. I thought when I selected "wipe data and cache" prior to flashing CM7 in the RomManager interface that it meant it would wipe all of that.
So I need to manually wipe everything except the card? Also, a secondary question, will any of this jeopardize the ability to restore my currently backed up stock sense rom if **** hits the fan?
Click to expand...
Click to collapse
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Alpine- said:
So I have a rooted (latest unrevoked) EVO with stock ROM. Radio is the current version so I did not need to flash a new radio. I have the rom backed up with rom manager and also a Titanium Backup.
I download Cm7-final with Rom Manager and proceed to flash it. All appears well until it loads and I'm stuck in CM7 splash bootloop and never get into the actual OS/homescreen. I boot to recovery and restore my prior rom backup, luckily all is fine.
My question is what have i done wrong? I read the EVO CM7 Wiki and it looks like I followed the instructions correctly. Do I need to ditch using RomManager and try it manually? Any suggestions on why I got this bootloop?
Click to expand...
Click to collapse
I had the same issue....although mine have been caused by restoring system data.
What I did is manually DL the rom, boot into recover, wiped cache/dalvic, flashed from zip (Both CM7 and the proper GAPPS file) and it worked.
eventer289 said:
No it won't as long as you have a nandroid. Look up the "VR Superwipe," and flash it. I'd recommend booting into recovery manually and doing this. Wipe cache and dalvik after flashing the superwipe for good measure. Finally flash the ROM.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Alpine- said:
nandroid? So the RomManager rom backup I created isnt sufficient? I also have a full Titanium Backup saved too. Why Nandroid? I was under the impression this was just a similar app to Titanium - wrong?
Thanks for the input guys.
Click to expand...
Click to collapse
So wait, still getting the loops?
teh roxxorz said:
So wait, still getting the loops?
Click to expand...
Click to collapse
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.
What I started doing was booting into RECOVERY (i know it sounds scary but it really isn't) A little off topic but there is a great app that I think every rooted user should use, it's called: Reboot Control Widget It only costs a measly $1 in the Market but it's well worth it. Basically you put the widget on the desktop and click on it. You are then given the option to Reboot your phone, Hot Boot (fast reboot), boot into Recovery, Bootloader or Shut Down. Best dollar you will ever spend on an app.
So anyway, l strayed from my point. The problem you are experiencing is partially due to not having fully wiped your phones data/cache. I know you think you did it through the Clockwork app but from experience it doesn't work that well. There is a "flashable" file called Calkulin's Format All. It is in the DEV section posted in Calkulin's Rom section. It will clear everything except the contents of your SD card.
1. Boot into RECOVERY
2. find: INSTALL ZIP FROM SDCARD
3. select the Calkulin's Format ALL.zip file (your phone will be totally clean after this)
4. Again, choose INSTALL ZIP FROM SDCARD
5. Select the ROM you want to flash. (If it is a Cyanogen based ROM you will have to flash the appropriate Google Apps file after flashing the ROM. If flashing a Sense ROM the Gapps file is not necessary)
6. Flash Gapps file (Google apps if necessary)
7. Once this is done select REBOOT SYSTEM NOW
I feel confident that if you follow those steps you won't run into any bootloops!
I have added the Format All.zip file that I mentioned in my last post.
Little advice:
- take the time to do a Nandroid before flashing a new rom
- use Titanium to restore only the apps w/o the data. I know it's nice to restore everything the way you had it on the last rom but from my experience this has led to instability in the new rom. Also from my experience when you are on a SENSE rom and use Titanium to backup your files and data when you install a AOSP (like CM) rom and try to restore those files and data it won't even let you. Just something to keep in mind if you are switching between CM to Sense or vice versa.
Alpine- said:
I have no tried since I got all these suggestions. Sorry for the confusion. I suspect manually wiping and manually installing will work.
Click to expand...
Click to collapse
Yes it should.
Manually wipe you factory/data, cache, dalvik, then flash the rom with the latest gapps and you'll be good.
SantinoInc said:
Alpine:
When I first started flashing stuff I relied on the Clockwork app to do everything. I used it to flash roms and clear/wipe data and cache. However, after running into problems like yours I started doing it manually.....
Click to expand...
Click to collapse
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
when you use clockwordmod recovery to wipe your phone the dalvik doesn't wipe with the wipe option you see on the main screen, i belive you will see the option to wipe it in the advanced menu
Alpine- said:
Wow, great post. Very informative and detailed, thanks a lot.
So why is creating a nandroid backup better than the ROM backup function in RomManager? I restored that rom once and it worked flawlessly. How does nandroid differ from the rom backup created in RomManager?
Click to expand...
Click to collapse
They are the same. ROM Manager boots you into recovery and nandroids for you. People have mixed experiences with ROM Manager. From my experience it is best just to boot manually into recovery and take care of all your flashing and wiping there.
Sent from my PC36100 using Tapatalk
so i have been using CM7 RC1 w/ stock kernel for a while now, without any issues. i was reading up and wanted to try the new incredikernel though, for the governor rather than using setcpu/juice defender for increased battery life.
so i did a titanium backup, then in Clockwork did a full backup before i started messing with anything. i then mounted to computer to put the kernel on the SD card. i did this, but was confused where to actually put the .zip file so that CW would see it. SD card or internal memory? i've had this issue before.
anyway, i didn't find the .zip when i booted into recovery, so i went to re-mount to USB to move it over to the other directory, and everything seized up on me. trying to mount USB basically froze my phone. re-booting did not fix, when i try to go into CM settings or try to mount USB same freezing would happen.
OK fine, i just did a nandroid backup so i figured it wasn't a big deal since i haven't actually made any changes yet and so i restored. then it would not boot. got stuck at the CM7 bootloader. ****. so i tried an earlier restore point, from a few months ago. that worked (also CM7-RC1 when i first put it on). i didn't wipe cache/dalvik when i tried the first time, so i wiped now and then tried to restore the most recent backup again. still, no luck.
so i've been living with the older restore trying to get everything how it was before. another note, i had installed a battery meter (RC1 did not come with one), and when trying to flash this, got stuck at the same bootloader screen again. another thing to note is that i have been updating CW to the latest version when it is available, but all versions are 3.xx. the latest i think i went from 3.0.0.5 to 3.0.0.8. just trying to include as much info as possible here...
any ideas? it's frustrating because i haven't actually been installing anything new. at this point i just want my phone the way it was, i.e. getting the latest restore point to work. it won't, but older restore versions will work. did CW mess up the backup, is it corrupt? is this a CM7 issue or CW? help please!
if this is in the wrong forum, apologies, it wouldn't let me post in the dev thread due to lack of posts.
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
k_nivesout said:
Did you do a complete wipe before trying to restore your backups? In recovery, wipe data/factory reset, wipe cache, wipe dalvik cache, format boot, system, data and cache.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i did not do that before. i just tried though, and same result. stuck in CM7 boot loop.
wtf happened to my backup!
That happened to me once. Try this. Save everything on your sd card to your computer. Reformat card. Then put just the nandroid back on card. It might help.
Yeah sounds like it may be an issue with the SD card or your backup..
Sent from my ADR6300 using XDA App
Ok I'm a bit confuse with amon ra recovery. I recently did an nandroid back up with fresh Rom 4.0. Then I flash a new Rom which is omj Rom. So I decided to nandroid restore back to fresh and once done I'm stuck on the HTC logo for very long time. So I keep on wipe and restore over and over still same problem. So I went and reflash fresh again after that I went back to amon ra recovery and nandroid restore and it works. so I'm confuse about it. do I need to be on the same Rom to restore back? I can't restore back to different Rom?
Sent from my PC36100 using XDA App
You can restore to anything that you have made a nandroid of, normally.
Just wipe everything in the Wipe setting, and I usually wipe dalvik and cache again, separately, then restore the nandroid you want.
TBH,m I have a nandroid of stock/rooted that I restore to before I flash any new ROM
culua said:
Ok I'm a bit confuse with amon ra recovery. I recently did an nandroid back up with fresh Rom 4.0. Then I flash a new Rom which is omj Rom. So I decided to nandroid restore back to fresh and once done I'm stuck on the HTC logo for very long time. So I keep on wipe and restore over and over still same problem. So I went and reflash fresh again after that I went back to amon ra recovery and nandroid restore and it works. so I'm confuse about it. do I need to be on the same Rom to restore back? I can't restore back to different Rom?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Some people say it isn't necessary to wipe, but it seems like you may need to. Try wiping data, cache and dalvik then restoring next time.
(from... Evo/MIUI/Tapatalk)
I always tend to wipe a few times and always use the format_all.zip... which unfortunately I do not have a link to at the moment. Make sure you wire the cache and davlik-cache separately imo
I had flashed Warm TwoPointThree. Didn't really like it so I restored to my nandroid back up. Now the phone randomly crashes for no apparent reason. It is sitting next to me on my desk and just now it crashed, wasn't even touching it. Secondary to the crashes is that after it happen and I try to report the phone is registering no charge and then immediately shuts down till I put it on a charger, regardless of actual battery charge.
Edit
More info. It has never crashed while on the charger. Don't know if that is relevant.
Did you wipe properly prior to restoring your nandroid? Also, what recovery are you using? If it's not Amon-ra, you need to get it! Make sure when doing a nandroid restore you have the appropriate items checked for restore (Assuming you did this when making the nandroid to begin with). Usually Boot, System, Data, and SD ext if partitioned.
Im using Amon-ra and I have an unpartitioned SD card. What do you mean by wipe? I'm a new to the entire rooting thing.
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
dieselford said:
You need to wipe all data factory reset, boot, system, and dalvik cache in recovery three times each. Then restore your nandroid. You can also use a superwipe script but I feel manually wiping them is best.
Sent from my PC36100 using XDA
Click to expand...
Click to collapse
Can I use the wipe feature in Amon-ra to do this?
Yes. That is the way to do it.
Sent from my PC36100 using xda premium
Try fix permissions, I think RA has it under other, or if u have Rom manager there is an option to fix permissions
Sent from my Synergized Aggressive Lionfish Evo using the XDA app
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
SabaBoBaba said:
I think I may have found a problem with the backup I was using. For some reason the backup file had 2 copies of every entry.
Under the other tad in RA recovery there was options to fix apk uid mismatches and move recovery.log to SD.
I selected the fix apk uid mismatches. Im hoping that is the fix permissions that the previous poster was talking about. If not then can I get some direction in doing it properly?
Click to expand...
Click to collapse
Yes that's it.
Well the crashes have started again. They seem to start slow, one crash then like 3 days later another and then just increase in frequency, today it crashed 5 times before noon. I'm at the point that I think perhaps I need to wipe and not attempt to do a restore. My concern is will I lose my root if I do that?
Will I lose root if I do wipe with out restoring afterward?
SabaBoBaba said:
Will I lose root if I do wipe with out restoring afterward?
Click to expand...
Click to collapse
If you wipe without restoring, you won't have a ROM on your device. You'll have to flash one, and as long as it's a custom or rooted stock ROM, you'll be fine.
Well I did a factory reset tonight so we'll see how that goes. Thanks to those people who contributed.
Well I did the factory reset and this morning it crashed again. I'm at a loss. All this started after I installed the Warm 2.3 ROM and then restored back to a backup to get the stock ROM back. Any thoughts on what to try now?
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
SabaBoBaba said:
Any further help that anyone can offer on this. I'm at the end of what I can think of to do
Click to expand...
Click to collapse
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Captain_Throwback said:
Just stop restoring and flash a ROM from scratch. Do a full wipe (everything except SD card), and then flash the ROM (custom or stock) or your choice. It seems that the restore is at the root of your problem, so it may be time to give up on that.
Current ROM (BootManager Slot 5): ICS-Deck-PreBeta20 | Kernel: Mason v0.14 SBC (FSO)
Click to expand...
Click to collapse
Well Im going to flash this http://forum.xda-developers.com/showthread.php?t=1455340&highlight=stock+rom and see if that works. Thanks for the assist.
After wiping last night and loading the rooted version of the latest stock ROM it crashed again today. Next idea?
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Grizraz said:
Try wiping in recovery by flashing Edify_Format_ALL (found on xda). I manually wipe Dalvik, habit... Flash rom from scratch. I use Titanium Backup to back up apps and data just for these situations. Some caches are moved to SD card, maybe delete these folders and let system rebuild them. (ie android_secure).
Hope you get it sorted out.
Click to expand...
Click to collapse
Ill give that a shot. I hope I can fix what ever I did to foul this thing up.
Just from searching the forums I really dont understand this edify thing. Can you help be get some clarity on it?