last night i decided to go back to stock and try the androidiani hacks and so far everything is running superb. im curious tho, if i make a nandroid of my current rom, will this back up the androidiani hacks as well?
say i want to flash a new rom, will the new flash remove the hacks? will the nandroid restore the hacks if i decide to flash back?
The hacks are incorporated into your system.img. If you back it up, they will be there. If you flash a nandroid, the tweaks will be there only if they were part of the nandroid image.
Sent from my MilestoneXT720 using XDA Premium App
Related
RESOLVED!
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
kimbernator said:
I flashed cm7, but not without making a nandroid of the stock rom. I tried restoring the backup and it would not make it to the boot animation. No errors or anything, same version of clockwork as before.
The only thing I didn't try was advanced restore. Would that do anything differently?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Being that you flashed CM7, and having troubles going back to 2.2.x you must be using 3.0.0.5 as a recovery image. You need 3.0.0.6, or a 2.x recovery image.
This thread [http://forum.xda-developers.com/showthread.php?t=986522] will help explain the ins and outs and how to flash 3.0.0.6.
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
kimbernator said:
Hey! I figured it out! And this should apply to all of us with mytouch 4gs.
The issue was that i was on clockwork 3.0.0.5, which i was on even when i backed up the stock rom. 3.0.0.5 allows for gingerbread flashing, but not froyo. So if you experience an issue like this, downgrade to 2.5.1.2 in rom manager and try recovering - lucky for me, even nandroids made in 3.0.0.5 were compatible with 2.5.1.2
Click to expand...
Click to collapse
That's what the thread i posted earlier explained. and showed you how to fix. It's sticked in the Q&A section.
What a breakthrough that was...I better write that down.
did a search didnt find anything...
I hear ppl backup and restore there using cwm what does that do ? why does it actually restore?
When you back up using CWM you are doing what is called a nanadroid back up. When you run the back up it creates a complete image of your phone in its current state so all system and data apps, personal settings widgets on your home screen etc are all backed up. So if you flash a new rom and you don't like it rather than starting from scratch you can just restore your nandroid and your phone will be back to the state it was before you flashed the new rom
I would recomend doing a nadroid back up before you flash anything in recovery, some people might say this is required but in my personal experince it can't hurt.
Sent from my HTC Desire Z using XDA Premium App
thanks i guess ill just back up after i get alll my settings like ringtones, settings, apps downloaded etc.
why would i do it b4 i flash anything in cwm?
(I would recomend doing a nadroid back up before you flash anything in recovery, some people might say this is required but in my personal experince it can't hurt.)
If you flash something in cwm that you were not supposed to, like a theme not designed for your rom, it can cause the phone not boot. If you did a nandroid you can just restore and everything will be back to how it was before you flashed
Sent from my HTC Desire Z using XDA Premium App
please
cjward23 said:
If you flash something in cwm that you were not supposed to, like a theme not designed for your rom, it can cause the phone not boot. If you did a nandroid you can just restore and everything will be back to how it was before you flashed
Sent from my HTC Desire Z using XDA Premium App
Click to expand...
Click to collapse
how can i restore it?? fullwipe>wipecache>restore, or what?
When restoring nandroid, you Don't have to wipe anything, just restore
Sent from my sgs2 running cm9 using xda app
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=1059485
it is a really simple thing.. I just did it for the first time and it feels easy and nice to have your whole system backed up on your sd card
Hey.
If I flash custom rom and then decide to go back to stock rom, do I just run the nandroid backup on top of the custom rom, or I have to wipe or something to make it run smooth and fast?
Thanks.
I just restore. But if u feel a lil frantic about issues do the normal wipe process
Sent from my LG-P999 using XDA Premium App
SAme here, never wiped, always worked great.
It wont hurt, but it wont change anything either, because restoring the nandroid rom actually does that for you automatically
I can't restore my CWM backups. I get an error saying unable to mount system.
I'm not using ROM Manager and I even tried reinstalling the same ROM that I made the backup from and then restoring the backup, but it still doesn't work. I'm using Octane 2.x with DrHonk's KJ1 Kernel and my CWM version is 3.0.2.8x
I've seen several posts on this issue, but haven't seen a clear answer. Some people say it doesn't work and others have said it does. If anyone can provide some help, I'd appreciate it. I like to try out different ROMS and with other phones such as the Vibrant (yes I know this phone is different) I have always made a backup with CWM and if I didn't like the ROM I could go right back to my previous one with very little work. I know I can use Titanium and I do that, but you can't restore everything so I end up having to redo a lot of stuff.
If anyone can provide some help with this, I would appreciate it.
Thanks,
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
This is mostly correct. Just left one thing out. Make sure after you flash Bali and restore your nandroid that you also reflash cwm/voodoo kernel.
Sent from my SGH-T959V using Tapatalk
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Thanks for the response. I guess I'll try to doing an advanced restore of the data the next time since that sounds like the least painful method. If that doesn't work I'll try the bali kernel.
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
bkoon1218 said:
Please keep in mind that you CANNOT perform an advanced data restore from Froyo to GB. It will cause issues, such as incoming calls going directly to voice mail.
If you are moving from Froyo to GB, be sure to create a backup of your apps and data using Titanium Backup. Restore everything once you're on GB and it'll work fine.
Click to expand...
Click to collapse
I'm doing GB to GB.
dbldown7 said:
From what I understand, you'll get that error when you restore a GB backup. Froyo works fine.
As a work around, you can boot into CWM, flash Dr Honks Bali kernel, then goto advanced>reboot recovery. When CWM boots again, you can restore your backup.
Another work around that I've seen mentioned is to boot into CWM, reflash the ROM of the backup you want to restore. Once the ROM flashes, goto backup/restore>advanced restore and backup the data only. That way you get the system partition from flashing the ROM, and your old data partition from your backup.
I haven't tried either of these methods. Guess I probably should have disclosed that first, but this is what I have gathered by reading some of these threads.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I followed the first suggestion, flashing Dr Honks Bali 3.3 Kernel and it worked great. Just make sure you re-flash your old kernel before you reboot and you'll be fine. Thanks for this.
Ive tried both Rogue and Roach's recoveries.
Every time i backup and restore (i wipe first), it is always successful.
Upon a reboot, it hangs at the very first Asus screen, never gets to the animation.
Ive always had success nandroiding my hero, nexus and evo 3d but cannot get a restore to work on my Transformer.
Kinda frustrating but im getting good at starting fresh. (Fast anyways)
Any ideas or help would be greatly appreciated.
Thanks!
After you restore the backup, then flash a kernel. That will allow it to boot up normally..
Is that the proper way to restore?
I realize that will probably work as I have to fastboot flash boot.img every rom change on my 3D
That means I need a flashable zip of each kernel of every nandroid I make in order to restore? Or fastboot the kernel.
There has to be something I'm missing or an easier way.?
Anyone?
Sent from my Transformer TF101 using xda premium
The only time you need to flash a kernel would be restoring back to HC from ICS as CWM doesn't restore the kernel. I have been jumping from ROM to ROM testing which one I like and no problems nandroid restoring my backup. I'm using Team Rouge version recovery.
I have some weird issues then.
I'm assuming the best bet for me as of now would to restore then immediately flash the rom on top of the restore.
Sent from my Transformer TF101 using xda premium