Couple of noob nandroid q's - EVO 4G Q&A, Help & Troubleshooting

Short and sweet:
1. I'm using the recovery that comes with Toast's 2of2 method (this is Amon Ra?) The Nand/ext backup fails for me and I read in a thread that's expected, but I can't find it again with the forum search. How would I fix this, and is it necessary? Is the regular Nandroid backup good enough?
2. Does a Nandroid backup include the kernel? If I push a custom kernel and have problems, will a Nand restore revert me to the kernel I had when I made the backup?
Thanks for the help in advance.

yes and yes
the ext bkup fails bc you dont have a ext partition yet

1. Do you have an EXT partition on your card? If not then you can just use the straight Nandroid backup.
2. Yes a Nandroid should back up the kernel at the point you made the back up. (not 100% sure but 99% )

I hate to hijack the thread but it looks looks like it died down a little and in my search effort this is the closest to what my question is. so to save making a new post on something probably answered before.
I am a relative noob. (i know sad) but i am learnign fast. I was wondering what exactly a nandroid back up does and does not back up.
I am doing the Starting over method to get back to stock 1.47(rooted) to see if it fixes 4g and think i can just nandroid after doing the method described to get my rom back etc. My only fear is that by nandrioding what ever benefit i got from starting over will be reverted.
Srry for the long explaination but basically if i Nandroid is it basically a complete image changing literally everything back to the previous state(ala HDD img)? If not will doing the starting over method then nandroiding revert me back to having the problem again?
Thanks in advance.

Nandroid backs up your entire system config. Radio, software, kernel, rom, etc. As long as you don't unroot, your system will be exactly the way it was after you restore.
Omega, if you do the back to stock root and then restore Nandroid, I'm pretty sure it will be as if you never did the back to stock. Pretty sure but not 100% positive.
Sent from my EVO using xda App

Nandroid does NOT back up or restore your radio, wimax, boot or recovery partitions
AFAIK nand only backs up your system and userdata partitions, not positive about the cache or misc partitions.

nebenezer said:
Nandroid does NOT back up or restore your radio, wimax, boot or recovery partitions
AFAIK nand only backs up your system and userdata partitions, not positive about the cache or misc partitions.
Click to expand...
Click to collapse
Thank you very much. This should mean that once i do the starting over i should then be able to just nandroid back to my rom without having to redo my kernal/theme/rom and it shouldn't mess up my wimax radio again.

omegasun18 said:
Thank you very much. This should mean that once i do the starting over i should then be able to just nandroid back to my rom without having to redo my kernal/theme/rom and it shouldn't mess up my wimax radio again.
Click to expand...
Click to collapse
Correct .
*edit- looks like I'm wrong about the boot partition. I just unzipped a nand and there's a boot.img in there.. still shouldn't affect radio or wimax though

Related

If I do a nandroid backup, then flash to a new ROM...

Currently, I have an EVO with the OTA update + Unrevoked3 for root. I want to flash a custom ROM, so I'm planning on going through the SimpleRoot process, but I'm not 100% sure if I'll like the result.
My question -
After making a nandroid backup from the new bootloader that Unrevoked 3 provides, should I be able to restore my phone EXACTLY how it was prior to going through SimpleRoot and flashing a custom ROM?
no, if you do the simpleroot you will end up with hboot 76.2 which is, as of right now, irreversible
nebenezer said:
no, if you do the simpleroot you will end up with hboot 76.2 which is, as of right now, irreversible
Click to expand...
Click to collapse
I'm getting conflicting answers on this between forums. One user has told me that a Nandroid backup will return your phone to the exact state it was in at the time of backup (like a Ghost image). Are you saying that one could not load the stock ROM/RUU, restore the Nandroid backup, and be back to whatever root state the phone was in? And if so, is this because the root permissions are actually set at a lower level that never gets wiped out even between ROMs?
nebenezer said:
no, if you do the simpleroot you will end up with hboot 76.2 which is, as of right now, irreversible
Click to expand...
Click to collapse
Ok, minus the HBOOT 76.2 change, if I restored my nandroid backup, would the vast majority of the system be restored? The HBOOT thing doesn't prevent me from restoring a backup, right?
SilverZero said:
I'm getting conflicting answers on this between forums. One user has told me that a Nandroid backup will return your phone to the exact state it was in at the time of backup (like a Ghost image). Are you saying that one could not load the stock ROM/RUU, restore the Nandroid backup, and be back to whatever root state the phone was in? And if so, is this because the root permissions are actually set at a lower level that never gets wiped out even between ROMs?
Click to expand...
Click to collapse
Nandroid makes a backup .zip file full of .img's of certain partitions. For practical purposes yes, you will restore everything you see and use on a daily basis. For literal purposes, no, you will not literally return to the EXACT IDENTICAL STATE you were in if you made a nand backup then installed the 76.2 hboot or upgraded your radio or wimax.
mspiegle said:
Ok, minus the HBOOT 76.2 change, if I restored my nandroid backup, would the vast majority of the system be restored? The HBOOT thing doesn't prevent me from restoring a backup, right?
Click to expand...
Click to collapse
Yes, minus your hboot, radio, wimax and recovery partitions.

[Q] NANDroid Backup Question...

Hey everyone... I was wondering -
If I make a NANDroid back up of my stock froyo rooted ROM (ROM #1),
Do a full wipe and then flash another ROM (ROM #2) and make a NANDroid BU of ROM #2,
Then do another full wipe and flash another ROM (ROM #3) and make a NANDroid BU of ROM #3...etc etc...
My question is - Can I restore any given NAND BU to any given ROM, or Do i actually have to reflash that ROM to get it back on the phone?
I tried doing this with a NAND BU that I made with a ROM I had flashed... it got buggy and I ended up restoring my NAND BU from the stock ROM. Then I wanted to show some one the ROM I had flashed before and tried to restore the NAND BU I made of that particular ROM and it got 3 dots into the restore then said it couldnt be completed.
I am wondering if it couldnt be completed b/c the NAND BU was corrupted some how - or if this is actually not some thing you can do...
any info on this would be helpful...
JS3
yes you can do that. before you restore you may want to wipe the cache and dalvik just to make sure that is all cleared out (unless you also do backups of the cache)
What recovery are you running when the restore failed? i am guessing amon, so when you get an error you should move the log to sd so you can check out what exactly the error was
elegantai said:
yes you can do that. before you restore you may want to wipe the cache and dalvik just to make sure that is all cleared out (unless you also do backups of the cache)
What recovery are you running when the restore failed? i am guessing amon, so when you get an error you should move the log to sd so you can check out what exactly the error was
Click to expand...
Click to collapse
Ok, I thought I could but I was thrown off by the failed attempt. I always do a FULL wipe when flashing from one ROM to another... and I'm not sure how to back up the cache...
The main back ups I preform are the NAND, Titanium and occasionally I use MyBackUpPro...but I only use the last one for contacts and texts...
I always use Amon_Ra... I am currently using 2.2.1... I am assuming that the NAND BU was corrupt some how.
I am trying to think if I made the back up with the same version of Ra or not and I assume that shouldnt make any differance. Now the only other variable would be that I changed the name of the main file - but I always do that with all my NAND BUs and I didnt have any problem restoring my stock froyo that was named in the same format...(ex: StockFroyo-011911 <~~ which worked Vs. WarmTwoPointTwo-012911 <~~ which did not work)...
You can make backups of multiple and re-flash them at your will [just know which is which, by naming them.] Also, do a cache and dalvik wipe before hand, and you're good to go.
JayStation3 said:
Hey everyone... I was wondering -
If I make a NANDroid back up of my stock froyo rooted ROM (ROM #1),
Do a full wipe and then flash another ROM (ROM #2) and make a NANDroid BU of ROM #2,
Then do another full wipe and flash another ROM (ROM #3) and make a NANDroid BU of ROM #3...etc etc...
My question is - Can I restore any given NAND BU to any given ROM, or Do i actually have to reflash that ROM to get it back on the phone?
I tried doing this with a NAND BU that I made with a ROM I had flashed... it got buggy and I ended up restoring my NAND BU from the stock ROM. Then I wanted to show some one the ROM I had flashed before and tried to restore the NAND BU I made of that particular ROM and it got 3 dots into the restore then said it couldnt be completed.
I am wondering if it couldnt be completed b/c the NAND BU was corrupted some how - or if this is actually not some thing you can do...
any info on this would be helpful...
JS3
Click to expand...
Click to collapse
Just wanted to tell ya thanks for the app recommendation (Elixir)... nvr seen it before but it's pretty awesome..
blakjak220 said:
Just wanted to tell ya thanks for the app recommendation (Elixir)... nvr seen it before but it's pretty awesome..
Click to expand...
Click to collapse
No problem, I love it... Also check out last months favorite app. I love that one too cause you can totally customize your texts and what not - It took me almost 4 hours of messing with settings to figure out EVERYTHING that handcent does...
Also thanks goes to teh, appriciate the info
That's wat I do I have several different backups of the most stable roms I like and switch to witch one I like just gota remember the date of backup
rayfrausto said:
That's wat I do I have several different backups of the most stable roms I like and switch to witch one I like just gota remember the date of backup
Click to expand...
Click to collapse
If you use rom manager, or amon ra, you can rename them, so its easy to tell.
teh roxxorz said:
If you use rom manager, or amon ra, you can rename them, so its easy to tell.
Click to expand...
Click to collapse
Yeah, I knew you could rename them... I have been doing that - but for some reason I cant get my NAND BU of myns warm twopointtwo to work, I guess I'll just reflash it... I dunno...
If your battery is less than 30%-40% or something, Amon-Ra won't restore or backup. If it's not working, plug in your phone and try again. Also, I would upgrade to RA-2.3. Much better IMO, only version since 1.8 that I haven't had any trouble with. I had also sorts of issues with backups and restores either taking FOREVER or just plain not completing. For the first time, I'm at a point where i have like 5 ROMs on my phone and switch whenever I feel like.
jstalford said:
If your battery is less than 30%-40% or something, Amon-Ra won't restore or backup. If it's not working, plug in your phone and try again. Also, I would upgrade to RA-2.3. Much better IMO, only version since 1.8 that I haven't had any trouble with. I had also sorts of issues with backups and restores either taking FOREVER or just plain not completing. For the first time, I'm at a point where i have like 5 ROMs on my phone and switch whenever I feel like.
Click to expand...
Click to collapse
Cool, yeah I may have had a bad battery level, I dont remember what my batery % was when I tried it but that makes sense... thanks, Also with the 2.3 I have it - I just havent flashed it yet... Thanks again

[Q] Restoring to a different Phone using CWM

I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
ChadH42 said:
I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
Click to expand...
Click to collapse
Generally, I don't believe it's recommended to restore a backup from one phone to another. However, I've seen reports that it it can be done. As you assumed, you are correct by NOT restoring the wimax. If you were to do that, it would restore the RSA keys of your old phone, overwriting your NEW RSA keys. You don't want to do that. So remove the wimax.img from your nandroid backup before you restore.
Also, I'm not positive on this, but I do believe that if your old backup was made on a certain hboot version, that you need to be on the same hboot version when restoring that backup. (lets say you when you created the backup, your hboot version was 2.10, then when you restore your backup, be sure the hboot version on the new phone is also 2.10). The reason I believe taht to be true, is because I had always had hboot .93 on my phone, and all backups I had ever made were when I was running .93 hboot. I then downgraded to the ENG .76 hboot, (to use fastboot), and I tried to restore a backup that had been created when I was on .93 hboot, and it did not go well. After the backup restored and I rebooted, it booted straight to fastboot, and that was the only place I could get. None of my old backups would restore. I then switched back to hboot .93, and my backups restore perfectly fine. So that is what led me to my conclusion. Good luck with your quest. ( i personally recommend just starting fresh, and not restoring an old backup, just to be safe)
k2buckley got you covered, but restoring a backup from an old phone to a new one WILL cause you problems, and the easiest way to avoid it is to not do it.
The best you can do is backup your apps via titanium backup and your launcher settings, transfer those folders to your new phone. When restoring the apps, do only app and data, NOT system settings.
Thank you both for the reply. Based upon your feedback I decided to do a clean install of everything.
You're welcome; just trying to make it smooth as possible.

Nandroid Backup Question

So heres a noob question.
If I use (Rouge currently) to do a "backup" under options. And then start flashing ROMs, if I restore that backup I did, does that get me 100% back to the point of when I did the backup? Meaning, it restores -everything- like it never happened?
I've always wondered this, so if I'm flashing things, I can always get back to my fully stable setup exactly like it never happened by restoring? Or does the backup via Rouge( or CWM, or whatever ) only back certain things and I'll have to do more setup after restoring to get back up and running exactly like I had the phone before?
Sorry for the noob question, just want to make sure I got this straight.
It will restore everything 100%. You also have the option to restore other partitions separate, system, boot, and the most important , data.
Sent from a phone with kNOw CIQ ...
TeamERA said:
It will restore everything 100%. You also have the option to restore other partitions separate, system, boot, and the most important , data.
Sent from a phone with kNOw CIQ ...
Click to expand...
Click to collapse
This is what I assumed, thank you for the confirmation!
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
1) It's always best NOT to restore system data when flashing a new rom. All your system data is specific to the rom you are flashing, so you don't want anything to conflict with the new data you are using now. Will cause a lot of problems in the long run.
2) TB is the best way to restore apps and apps+data that I know of. MyBackUp Pro is another good one, but TB works best for me. I'm sure there are others in the market also.
And I moved this to the Q&A section.
Well, this is what I thought too in fact I rooted my phone, installed CWM and the next step I performed was a nandroid backup thinking I could get my stock setup back if I ever wanted it. All was good. Then I flashed for a while and found a setup I liked and before proceeding I did another nandroid. THEN a while later I got to a point were I found myself, for time purposes wanting to fall back to my second backup so I thought: "hey, lets try restoring from this nandroid file I so maticulously spent time creating"!
That's when, for me at least, this whole nandroid Backup/Restore exercise falls on its face. Because when I tried to restore the backup I made it gave me a MD5 error..and I know there's a workaround that you can use by modifying the file I think that's basically what your doing? I didn't try it, I figured if the file needed to be modified before it could be restored what was the point anyway.? I just used my plan B which was Titanium Backup.
Anyway I keep my eyes open for an answer to this mystery, I think it has to do with the different CWM versions from one ROM to the next? Still not sure though?
Oh and hopefully this post wont just get rudely deleted like my first post on the same subject did? I made the same mistake you have by posting in the "General" area instead of the Q&A section!
the only time I have had a Android fail for md5 was when I changed the name of the backup. so maybe that's what you did?
RubenRybnik said:
So heres a noob question.
If I use (Rouge currently) to do a "backup" under options. And then start flashing ROMs, if I restore that backup I did, does that get me 100% back to the point of when I did the backup? Meaning, it restores -everything- like it never happened?
I've always wondered this, so if I'm flashing things, I can always get back to my fully stable setup exactly like it never happened by restoring? Or does the backup via Rouge( or CWM, or whatever ) only back certain things and I'll have to do more setup after restoring to get back up and running exactly like I had the phone before?
Sorry for the noob question, just want to make sure I got this straight.
Click to expand...
Click to collapse
I have done many restores and everything comes back just like it was before.
---------- Post added at 12:40 PM ---------- Previous post was at 12:28 PM ----------
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
I only use Titanium backup to backup and restore specific apps on my phone. I use CWM for the system.
patrao_n said:
the only time I have had a Android fail for md5 was when I changed the name of the backup. so maybe that's what you did?
Click to expand...
Click to collapse
nope. I followed step by step...pretty hard to mess it up with qbking77 video's? Is there any other possible reason, you can think of?..and really, how many people test out thier restores? I'm just wondering?
Just one quick point of clarification regarding the Nandroid backup/restore. From what I've read, the restore will bring back your kernel and ROM but NOT the modem version. If the modem is important to you you'll have to flash that back separately.
Magicspell said:
Just one quick point of clarification regarding the Nandroid backup/restore. From what I've read, the restore will bring back your kernel and ROM but NOT the modem version. If the modem is important to you you'll have to flash that back separately.
Click to expand...
Click to collapse
Good point ... Thanks to everyone for the replies, got a much better understanding on the backup/restore process in both cwm and titanium now ) Thanks!
One more question about the MD5 ... So you can not change the name of the backup of CWM? I didn't think name change would effect how MD5 is generated.
RubenRybnik said:
Here is a follow up question:
If I do a Titianium Backup for apps and sys data. Then I flash a new ROM, I usually do a Titanium restore of both Sys and App data ... It gets me up and running the quickest.
1.) Is this safe, or will sys data mess with the ROM
2.) Is there a better, more supportable way to do this?
Click to expand...
Click to collapse
You can also use your latest nandroid back up to restore data. I just tried this as a test with my wife's phone (i also did a separate back up in TB just in case) and it works well.
She was on one of Calks ROMs, and I wanted to switch her to the bare version of the ROM. I wiped data/cache/dalvik, installed the bare rom and rebooted. Once booted, I verified everything was gone (apps, contacts, sms, settings, ect). Then I went back to CWM and went to back up and restore->advanced restore-> restore data. When I booted back up, all her apps, contacts, sms, settings were back. I guess this would be a quick and dirty way to restore your stuff when jumping between a lot of ROMS.
s9amme said:
You can also use your latest nandroid back up to restore data. I just tried this as a test with my wife's phone (i also did a separate back up in TB just in case) and it works well.
She was on one of Calks ROMs, and I wanted to switch her to the bare version of the ROM. I wiped data/cache/dalvik, installed the bare rom and rebooted. Once booted, I verified everything was gone (apps, contacts, sms, settings, ect). Then I went back to CWM and went to back up and restore->advanced restore-> restore data. When I booted back up, all her apps, contacts, sms, settings were back. I guess this would be a quick and dirty way to restore your stuff when jumping between a lot of ROMS.
Click to expand...
Click to collapse
So just to be clear ... "Restore Data" in CWM is just Apps and Apps data, no system data is restored correct?
RubenRybnik said:
So just to be clear ... "Restore Data" in CWM is just Apps and Apps data, no system data is restored correct?
Click to expand...
Click to collapse
Yes on apps and data.

[Q] Full Restore

What app do I use to back my phone up to do a complete restore to where it was pre-flash. TB only restores the apps and data but not the Launcher and the way i had everything set up pre-flash. Any help would be appreciated. thanks in advance.
Need to flash a recovery and do a nandroid. TWRP 2.6.3.7. Goo manager to flash the twrp.
sent from my sm-900t.
@rbiter said:
Need to flash a recovery and do a nandroid. TWRP 2.6.3.7. Too manager to flash the twrp.
sent from my sm-900t.
Click to expand...
Click to collapse
Long been A fan but I just completed my first successful flash, and I used TWRP 2.6.3.1. So could you be a little more specific. I appreciate your help but I have been searching and there are explanations out there i just don't understand them. thanks again in advance.
I think 2.6.3.1 has been working for some people but I would recommend flashing .4rc2 or higher. I think all the kinks have been worked out since .4rc2. You need to hit backup and rmemeber what is ticked. Now untick that and backup efs first and store that separate and maybe even backup to sdcard or computer. Then go back and tick at least system and data for your nandroid. If you plan on flashing kernels, do boot.IMG too. Not sure about cache. I did it anyways for hahas my first backup. I don't know if you need to reset up your phone or not. And I think there have been problems with titbackup restores because of Samsung and Knox stuff. Need to read up in that for specifics. I've seen a couple custom kernel descriptions say their kernel fixes TB issues but like I said need to look around on your own as I don't really use TB. Had too many small issues so I manually cherry pick data I need and just start fresh each phone. Also been awhile since I've flashed anything because my note2 had insane chip so I didn't do anything crazy to trigger SDS. I spent all weekend researching recovery myself before I proceeded. Make sure you do the efs backup first!! In cade something bad happens youmight need that.
sent from my sm-900t.
@rbiter said:
i think 2.6.3.1 has been working for some people but i would recommend flashing .4rc2 or higher. I think all the kinks have been worked out since .4rc2. You need to hit backup and rmemeber what is ticked. Now untick that and backup efs first and store that separate and maybe even backup to sdcard or computer. Then go back and tick at least system and data for your nandroid. If you plan on flashing kernels, do boot.img too. Not sure about cache. I did it anyways for hahas my first backup. I don't know if you need to reset up your phone or not. And i think there have been problems with titbackup restores because of samsung and knox stuff. Need to read up in that for specifics. I've seen a couple custom kernel descriptions say their kernel fixes tb issues but like i said need to look around on your own as i don't really use tb. Had too many small issues so i manually cherry pick data i need and just start fresh each phone. Also been awhile since i've flashed anything because my note2 had insane chip so i didn't do anything crazy to trigger sds. I spent all weekend researching recovery myself before i proceeded. Make sure you do the efs backup first!! In cade something bad happens youmight need that.
Sent from my sm-900t.
Click to expand...
Click to collapse
thank you so much!!!!
Thanks for this informative post.
Just to verify that it is recommended that we back up the EFS separately then backup the DATA/SYSTEM/BOOT partitions next? I would like to make sure that I will have everything needed just in case I/phone mess up somewhere along the line of flashing ROMS and themes. There seems to be more occurrences of boot-loops with the GN3 than there ever was with the GN2.
When restoring, I presume we just flash the backups then reboot as usual?
Thanks
Yeah. I backed up my efs first. Then backed up to my laptop. Then I backed up modem for haha's and to laptop. Then I backed up boot, system and data. If you don't wipe data when you're flashing around you should only need to flash boot and system. I haven't run into problems yet so I havent had to flash data. It's always been there and settings and apps have been fine.
sent from my sm-9005.

Categories

Resources