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
Related
First off sorry if this is answered in another post, lease kindly direct me to the post if it is =)
I just tried to install a second ROM from ROM Manager. I was running DCU and created a back-up in ClockworkMod before I started then installed the new Fresh ROM successfully. When I tried to go back to my first ROM via the restore point I set up it gets stuck in a boot loop. The 2nd restore point from the Fresh ROM loads up just fine.
Is there anyway to fix the older restore point and get back to DCU or should I just wipe everything and reinstall DCU...
Thanks in advanced!
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Bielinsk said:
do a data wipe, clear cache and dalvick
Then restore your backup. Clockwork does not seem to like certain roms.
Click to expand...
Click to collapse
thanks, i was able to wipe everything from the original android recovery mode and upload an old nandroid back up but from Clockwork it didnt seem to clear the dalvik cache, when i clicked clear it just went back to the last menu it never said anything in the log and when i loaded up the Clockwork backup it still didnt work :/
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?
I've got a general question that I haven't really found an answer for - although I know the information is there, I'm just not 100% sure how to piece it together. I'm hoping all you experts out there can help provide some guidance.
Using my EVO as an example, I currently have Fresh 3.5.0.1 flashed and have been very happy with it. But, I've been dinkin' around with Titanium Backup and uninstalled a few things (i.e. LiveWallpaper) and generally (probably) made a mess of things.
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
I have ROM Manager installed... is it as simple as creating a NANDROID backup, downloading the ROM again and flashing? Or, should I boot into recovery and clear caches, wipe data/factory reset? I'm not sure if a "wipe data/factory reset" from the CM recovery (3.0.0.5) is the right thing to do.
Guidance would be very helpful and much appreciated. Hopefully, others could use any information provided to do the same with their device if they're unsure how to do the same thing with other ROM's.
i usually like using amon ra recovery instead of clockwork recovery which is the one use by rom manager, if you want to try it rom manager has an option at the bottom that says flash different recovery and says amon ra, if you click it your recovery will become amon ra which i like better for wiping. but to answer your question, yes for a fresh start on a new rom you need to boot into recovery, then NANDROID BACKUP, then wipe 1.cache 2. dalvik cache 3. data and then flash your new rom and you are good to go
If you want to start fresh on the current 'Fresh' ROM then, yes, wipe fully and reflash.
sent from my
Everything is still working fine, I'd just like to get a fresh start with Fresh 3.5.0.1 but I'm not exactly sure what I should do to ensure a totally clean device.
Click to expand...
Click to collapse
Just do exactly what you did when you flashed it for the first time. Place zip on sd card, nandroid backup, wipe everything, flash rom.
so ive been having issues with my restores so i decided to try things with amon ra again.backed up and wiped with amon, and superwipe, flashed jellybean rc2 and it wouldnt go past fastboot, well i tried just reflashing, it booted but got stuck on the white incredible screen. reboot to amon ra, wiped same as above, flashed a copy of cm7 and booted into it...a lot of my data was there...like i restored an older backup...so i tried to restore the backup i made with amon, fastboot again...redo cm7 and reflash recovery...5 vibes. back into rom to deal with today
so my question is twopart...why did jellybean and the restore go to fastboot and why is my phone not wiping everything...
id love to keep this phone going once i get my s3 but dont know if ill end up getting problems from it basically being a dirty flash
sorry for the long post. and thanks in advance
OMG_VTEC said:
so ive been having issues with my restores so i decided to try things with amon ra again.backed up and wiped with amon, and superwipe, flashed jellybean rc2 and it wouldnt go past fastboot, well i tried just reflashing, it booted but got stuck on the white incredible screen. reboot to amon ra, wiped same as above, flashed a copy of cm7 and booted into it...a lot of my data was there...like i restored an older backup...so i tried to restore the backup i made with amon, fastboot again...redo cm7 and reflash recovery...5 vibes. back into rom to deal with today
so my question is twopart...why did jellybean and the restore go to fastboot and why is my phone not wiping everything...
id love to keep this phone going once i get my s3 but dont know if ill end up getting problems from it basically being a dirty flash
sorry for the long post. and thanks in advance
Click to expand...
Click to collapse
Flash twrp and try again
Sent from my ADR6300 using xda app-developers app
Hi,
I've done a nandroid backup to my CM10 rom (http://forum.xda-developers.com/showthread.php?t=1945441)
then I've tried to do a restore (using a different sd card with the same partition)
well, the rom is stuck on boot, and after restoring it also to the original card it is also get stuck on boot.
I have 4ext recovery touch v1.0.0.4 RC3
do you have any suggestions? beside installing the rom again....
if you need more info please ask.
tnx!
Did u full wipe before u restored the backup? Did u change hboots?
Sent from my HTC Desire
did everything....
I've tried without full wipe, and with full wipe
I've tried restoring only the data,
I've even updated now to the latest 4ext recovery touch
nothing worked.............
any idea what can I do?
tnx, Nitzan
ndori said:
I've tried without full wipe, and with full wipe
I've tried restoring only the data,
I've even updated now to the latest 4ext recovery touch
nothing worked.............
any idea what can I do?
tnx, Nitzan
Click to expand...
Click to collapse
to restore nandroid u have to do a full wipe first. what recovery did u do the nandroid with? if 4ext recovery then boot recovery and goto
wipe/format
format all partitions except sdcard
then
backup/restore
and restore nandroid.
also make sure u have the same hboot from when u made the nandroid backup.
Sent from my HTC Desire
Done it
jmcclue said:
to restore nandroid u have to do a full wipe first. what recovery did u do the nandroid with? if 4ext recovery then boot recovery and goto
wipe/format
format all partitions except sdcard
then
backup/restore
and restore nandroid.
also make sure u have the same hboot from when u made the nandroid backup.
Sent from my HTC Desire
Click to expand...
Click to collapse
I've done exactly that, and it doesn't work
The question is where the problem lays? The recovery? The backup itself? Or maybe the rom?