[Q] Restoring to a different Phone using CWM - EVO 4G Q&A, Help & Troubleshooting

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.

Related

[Q] Restore nandroid backup on new phone with unrevoked3?

If I run unrevoked3 on stock 1.47 (new Evo), can I restore a rooted 2.2 nandroid backup from my first Evo that was made with Amon_Ra? Would it work without engr. hboot? If so, could I be in trouble later by going to this rooted 2.2 backup w/o full root?
Had to bump this because I was curious to see how to restore a nandroid backup if I were to get a new phone for whatever reason.
Is it as simple as putting the sdcard from the old phone into the new rooted phone and performing a restore (assuming the same recovery method is used in both phones; in this case clockwork)?
m4rk0358 said:
Had to bump this because I was curious to see how to restore a nandroid backup if I were to get a new phone for whatever reason.
Is it as simple as putting the sdcard from the old phone into the new rooted phone and performing a restore (assuming the same recovery method is used in both phones; in this case clockwork)?
Click to expand...
Click to collapse
It should be. the hardest part should be rooting your phone.

Clockworkmod Recovery Nandroid over 3GB! ?

So I tried to make a nandroid backup today and had to pull the battery because it was taking forever. I checked the size of the file and it was over 3GB. I've made a bunch of backups before and they are usually aroud 200mb or so. What could be the problem? Any help would be great. Thanks.
my average aosp backup is 200-300mb, sense 500-600mb, desirehd mod 600-700mb
theres definitely a problem there, you could try RA recovery and do a backup (honestly i think its better but your absolutely fine if you have at least 1 good RA backup just to save your RSA keys) delete that 3gb backup file/folder because its obviously bad, try again and see if it still does it, if so then go into Rom Manager and flash RA recovery then reflash Clockwork and try the backup
That's either a glitch or you have some SERIOUS stuff on your phone lol. Anyway, I'd recommend reflashing Clockwork if it happens again.
I deleted the bad backup then I tried flashing RA Recovery and doing a new backup with the same results. What I ended up doing was restoring a previous backup and then tried and new backup. All is back to normal now.
I want to update my radio, wimax, pri, and nv. I know I should make a backup using RA recovery. Do I do a normal backup or backup with ext? I want to make sure I backup my RSA keys. Thanks for the help guys.
normal backup is fine
glad your problem is resolved

[Q] [Help] Nandroid Fail

This isn't like some of the other nandroid fail threads i've encountered.
I had a full nandroid backup of my tmobile g2 (eng hboot) and I lost that device. I got an exact replacement, rooted it (no eng hboot), installed rom manager only and flashed clockwork. I then copied my nandroid backup to the clockwork/backups directory and did a restore.
The phone booted successfully with cyanogen 7 nightly 22 flashed but the only problem is that it seems to have done a fresh install...as in there are no apps, no data, just cyanogen 7 nightly 22. It appears it didn't restore anything except the rom itself. Any ideas? thanks in advance.
ps. ive done multiple data wipes, and tried 2 different nandroid backup files on the new phone.
Did you have darktremors a2sd installed on the old ROM? CWM3 seems to have an issue for some with seeing the sd-ext partition and won't back it up. So when you select 'restore' in CWM it *successfully* completes the nandroid restore correct, no errors? It would be odd for it to give you a 'restore complete' message if it ran into any errors.
pretty sure I don't have a2sd installed on the old rom. first time i'm hearing of it. I don't recall getting any errors after restoring the backup but I will try again and double check. I also have much older backups that I can try to restore and see if those go through
Well I think this needs more attention if it's really not restoring the nandroids fully. Seems like it's restoring the system.img and whatnot just not the data.img. Maybe try it with ADB and see if it works. I've never had to do it that way but I know it can be done, you may have to run it in a shell.
I tried restoring a nandroid backup from February, which I believe was backed up with an older version of clockwork, and it was completely successful. This tells me that either the new clockwork is not backing up correctly or it's getting corrupted.
I then tried restoring 3 different backups and they did not give me any errors but failed to restore my data. hmmm

[Q] HELP - backed up sense rom will not boot

Ok so i got my brand new replacement evo yesterday and of course the first thing I did was root it and did a nandroid backup! And then restored my previous rom I had backed up well I needed to back up my sprint vm through titanium on the sense rom and so today I went in to restore it after wiping data/cache/davlik and after restoring the sense rom will not go past the boot screen! Is there something I can do to get this back and going past the boot screen? HELP!
It's not safe to restore nandroid backup from a previous phone, at least you made a backup first, restore it, then DELETE all the nandroid from your previous phone. Start over, but keep the titanium backups, they safe
NewZJ said:
It's not safe to restore nandroid backup from a previous phone, at least you made a backup first, restore it, then DELETE all the backups from your previous phone. Start over, but keep the titanium backups, they safe
Click to expand...
Click to collapse
agreed agreed agreeeeed. restore the backup u made with the new phone, then start over.
Ok now im confused...because I think one of you misunderstood me. Ok I now get I shouldnt restore a nandroid backup from a previous phone. But ok so if I delete all my backups (except for the sprint sense rom) will that rom reboot then? So i will be able to redo the process?
yes, if you have a backup of the stock rom from your NEW phone, you can restore that one, all other backups you had saved from your previous phone aren't going to work. So you can delete them, your titanium backups of your apps will still work, just your rom backups wont, so yes, u will be able to restore the stock rom backup that you made on the new phone, hope that made sense... lol
If I understand right, you already restored the backup from your previous phone. This could cause issues with the system not restoring the previous backup. Go back and wipe data, cache and dalvik then try restoring the backup from your current phone.
If you still can't restore, try flashing the stock rooted rom.
Once you get it working, I'd check to see if 4G works. If you don't live in a 4G coverage area, run the RSA key checker app and make sure you didn't bork your wimax.
(from... Evo/MIUI/Tapatalk)

Wimax.img file size?

Through help on another thread, I was able to locate a wimax.img from a prior nandroid backup made with amon's recovery. I was also able to open terminal and flash it back to the system making the Wimax keychecker say my keys were now ok. Question is this. Why would directly flashing the wimax.img recover the key but when I tried nandroid restoring the whole folder, the keys still wouldn't be present even though the wimax.img was in the folder?
Also, someone please check your nandroid folders and let me know how large the wimax.img is. The one I got to flash successfully is just over 2,000kb. I also found an old clockwork recovery on my sd card with a backup that has a wimax image file of nearly 12,000kb! Restoring that backup still showed my keys missing with keychecker though. When I tried to directly flash the 12,000kb wimax file, i received a bad block error.
My problem is that even though my mac address checks out and keys are present, I still cannot connect to Sprint 4g, it scans and finds the service, but connects and disconnects repeatedly without ever making a good connection. Is there a way my keys show up but aren't correct? Does the radio version at the time of backup make a difference when you are trying to recover?
legasus233 said:
Through help on another thread, I was able to locate a wimax.img from a prior nandroid backup made with amon's recovery. I was also able to open terminal and flash it back to the system making the Wimax keychecker say my keys were now ok. Question is this. Why would directly flashing the wimax.img recover the key but when I tried nandroid restoring the whole folder, the keys still wouldn't be present even though the wimax.img was in the folder?
Also, someone please check your nandroid folders and let me know how large the wimax.img is. The one I got to flash successfully is just over 2,000kb. I also found an old clockwork recovery on my sd card with a backup that has a wimax image file of nearly 12,000kb! Restoring that backup still showed my keys missing with keychecker though. When I tried to directly flash the 12,000kb wimax file, i received a bad block error.
My problem is that even though my mac address checks out and keys are present, I still cannot connect to Sprint 4g, it scans and finds the service, but connects and disconnects repeatedly without ever making a good connection. Is there a way my keys show up but aren't correct? Does the radio version at the time of backup make a difference when you are trying to recover?
Click to expand...
Click to collapse
I am not 100pct sure about this but I thought only Amon had the proper ability to backup wimax keys and restore without a problem. I could be wrong since I was not a fan of Clockwork just for that reason. My Wimax backup is 12 megs
wimax for me are always 12000 if you are trying to restore with clockwork you need to select advanced restore so that it restores your wimax too,because clockwork backs up your wimax by default but doesnt restore on a normal restore just on advanced
Well, I think what the real question is though is just because keychecker says my rsa key is present, doesn't necessarily mean the whole thing is present? I appears my backup with the 2,000kb wimax.img may not complete? I will look for advanced restore in clockwork to see if that restores the image.
At some point I wiped my sd card (copied all files first to pc) and reformated it for ext 1 and ext 2. My guess is this occurred somewhere between having wimax keys and temporarily losing them. Would this have screwed something up with my wimax partition where the wimax was originally stored?
thats a good question, because i have 2 sd cards one partitioned and one that's not, and i have never tried restoring a partition back up on the non partition card and the other way around.
What are your thoughts on the actually size of the wimax.img and the fact that keychecker says the key is present??
why dont you try getting a stock rom like sprint lover and doing a full wipe with something like caulkins wipe all and flashing the rom to see if its your rom not playing well with your wimax. also where did you get your wimax backup from?
edit: better yet why dont you flash clockwork and do an advance restore from the one that has the 12000, then if your 4g gets fixed, go back to amon and reflash to what ever you have now, i would suggets that if 4g gets fixed you dont restore, instead redo everything from scratch and then back up
What are your thoughts on the actually size of the wimax.img and the fact that keychecker says the key is present??
I got the 2,000kb wimax.img from one of my nandroid backup folders. Just this morning, I flashed the pc36100 sprint lovers rom and it said the keys were missing. Plus, the 4g wouldn't even turn on, it just stayed at turning on before finally saying unable to start 4g. The 4g doesn't work on any roms I have tried (currently on Fresh 3.5) I have tried Myns, Kings, CM7, and a couple others, to no avail.
emcp422 said:
why dont you try getting a stock rom like sprint lover and doing a full wipe with something like caulkins wipe all and flashing the rom to see if its your rom not playing well with your wimax. also where did you get your wimax backup from?
edit: better yet why dont you flash clockwork and do an advance restore from the one that has the 12000, then if your 4g gets fixed, go back to amon and reflash to what ever you have now, i would suggets that if 4g gets fixed you dont restore, instead redo everything from scratch and then back up
Click to expand...
Click to collapse
Good info. Will it work if I just do an advanced restore of the wimax? Or do I need to advance restore the system and everything for it to work. I am currently on my favorite fresh 3.5 setup and just switched to Clockwork and was hoping I could just do the advanced wimax restore. Or will that backup no play nicely on it's own?
try alone first if it doenst work try the full backup
Here is the interesting part. I did the clockwork advanced restore and verified the wimax key was present on my current Fresh setup. I also refreshed the old Clockwork backup that contained the wimax originally and got the system up and running (It was Sprint lovers I believe) and verified the wimax key was present. I checked both of the backup folders and the wimax.img created in clockwork in both cases was about 12,000kb. I then switched recoveries back to amon and did a full backup (selected all options) of both the Fresh system and Sprint lovers. When I open up those nandroid files, the wimax.img is only about 2,000kb? So, either I am not backing up what I think I am, or these two recoveries back up wimax much differently resulting in various output file sizes. Can someone explain this?
Also if am running one of these with verified wimax key, then nandroid restore to another file that doesn't have the wimax.img backed up, will I still have the key in place left over from what I was running? I understand how all of this works relatively well, but this wimax stuff sure has been throwing me for a loop! Thanks again for all the help!
My 4G works, and my Amon Ra wimax.img is 12 mb (12000 kb). Perhaps you should try a fresh download and install Amon Ra again, then try only backing up wimax. I only used Clockwork to make a backup once, right after I rooted, and don't have it handy to check the size of that one if it even has a wimax.img. I originally backed up my wimax keys via terminal, it was about 4000kb if I remember correctly.
If you restore a backup made with AR that doesn't include wimax, your working 4G should remain intact.
But your situation is odd... so I can't guarantee that to be the case.
(from... Evo/MIUI/Tapatalk)
yeah you can restore,just make sue you dont select wimax, and yeah it sounds like your amon ra is bad, its should always be 12000. but good to hear you are up and running, remember always and remember to restore with the recovery you used to back up, and i would keep a copy of the working wimax backup on my pc for safe keeping
What I don't understand is why my wimax key checker says the keys are intact even after flashing the 2000 kilobytes wimax.img
Sent from my PC36100 using XDA App
Also, how can I safely flash a new recovery without losing anything? I have not done that in particular yet, with the exception of my original root process, but that included every step
Sent from my PC36100 using XDA App
legasus233 said:
Also, how can I safely flash a new recovery without losing anything? I have not done that in particular yet, with the exception of my original root process, but that included every step
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
You can download a PC36IMG of Amon Ra from my dropbox, here: http://db.tt/WP0beNa
Don't rename it - it's named PC36IMG.zip exactly (even if you can't see the .zip), which is what it needs to be named. Put it on the root of your SD card, then boot into the bootloader. It'll scan for the file then ask you to update. Agree with the volume up button, then when it finishes flashing, don't reboot when it asks you. Instead go into recovery and make a nandroid backup of only wimax. If you want, you can go ahead and backup the default options as well, but do them in a separate backup.
Reboot back into the rom and make sure that 4G is working properly, then check the size of the wimax.img file.
If it's still too small, then that's totally weird. Hope you get it figured out, though.
OK, I flashed the recovery and made a nandroid backup of the wimax. I then used file explorer to check the size and it still says 2.38 MB. Just to make sure, I then changed to clockwork and recovered a wimax image that was 11.88 MB and rebooted. I then changed recoveries back to amon again to make a nandroid backup of my recovered clockwork image. Again, the nandroid output image file was 2.3 MB!?!
Is there some other way to check the wimax size/files without doing a backup? I am so confused right now.
Sent from my PC36100 using XDA App
what version of amon ra are you using i suggest 2.3, and also as long as you have a working backup even if it is from clockworkmod your safe, you can always go back and forth between recoveries if you need to, and if you need to restore a nadroid, just uncheck wimax, that way you dont touch the one you have that is working
If I recover one wimax.img over another, wont the original get overwritten? If there were any errors in flashing either of the images, wouldn't it tell me?
Sent from my PC36100 using XDA App

Categories

Resources