Hello everybody! I made a cm9 b14 nandroid backup a week ago to try out the new miui mintberry, now if i try to restore the backup i have some problems like no statusbar and random recovery reboots. So I came back to miui and now i m considering doing a nandroid backup of miui mintberry in order to try the new cm9 b15, i wanted to ask you what could have caused the problems described so to avaid them if (after doing the miui backup and flashing the new rom) i will want to go back to miui in the next days. Another question is: do i loose all the saved passwords (gmail wattsapp facebook freesms..) by doing a nandroid backup or they are stored with all the data?
I hope my questions are clear
Thank you in advance!
Sent from my GT-I9000 using XDA App
Upp..please spmeone help me to understand what i did wrong..
Sent from my GT-I9000 using XDA App
Hi, I'm running CyanogenMod 7.1 now, and I have ClockworkMod Recovery 5.0.2.6.
But I want to restore and Clockwork won't see my backup because it was done in a newer different version 5.0.2.7.
How can I restore my backup ?
to restore your nandroid backup its best to first install the rom you took the back up off.. factory reset your phone and then do a fresh install of the rom you backed up.. after flashing restore the backup..
you won't have any FCs or anything with this method.
Related
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me? Thank you
Nothing to see here, move along.
Thanks bud you are sooo helpful.
Sent from my SAMSUNG-SGH-I897
koreancanuck said:
Hey guys,
I've been using nandroid since my magic days. With my magic, I've had no problems whatsoever always wiping and doing a restore of my old nandroid backups. However, it does not seem to be the case with my captivate for some reasons.
Here are a few methods I've tried:
1) Factory wipe/data reset using clockwork recovery and restore nandroid (which I did with my magic.. not sure why they don't work)
2) Flash to 2.1 stock and do nandroid restore.
3) Flash to the ROM after a wipe that I want to restore to then do nandroid restore.
All three methods allow me to complete nandroid restore but upon reboot it's just non-stop FC city.
Can anyone guide me?
I am not sure but do you only have one backup you are trying to use? Could be an issue with backup. Is three any lag fix in the equation? It sucks but if three worst of it is you can flash the rom but not restore your apps then I guess consider your self lucky
Captivate
Cog 2.4
Click to expand...
Click to collapse
Yep. I disable my lagfixes before doing restores. To be honest it's not that big of a hassle since I can just use tibu pro and do one click restore for apps and restore my settings as well. And nandroid takes so much longer on captivate than magic D: Still it would be nice to always go back..
Sent from my SAMSUNG-SGH-I897
Hi,
I hope that my experience could help other persons that fall in my situation.
After a try of CM, I couldn't restore my stock backup anymore, the phone hanged up in the lg boot screen.
There were no problems about ext4 partition or wiping or fixing permission.
I was thinking to do a NVflash procedure, but i gave another try: using old modaco CWM recovery. I overwrited CWM 4.2.0.2, performed a wipe, installed the modaco zip ext4->ext3 (i didn't remember if i was ext 3 or 4) and then restore my STOCK backup: EVERYTHING WAS FINE!!!
Maybe there's a problem in the newest CWM during restore a backup, i don't know, but in this way i could restore my original firmware.
Hope that this could be usefull.
Did you do your stock backup with modaco CWM? It has different MD5 checksum than the CWM. Might be the case why you can't restore your backup.
No, I did the stock backup with the original CWM.
I think that the problem is in the restore procedure of the original CWM (4.2.0.2), in fact also the CM restore is impossible, only if you install the zip immediately after the restore. Instead... hangs up.
I find when that happens the best method is to reflash the rom your restoring and just restore the data from your nandroid backup. Always works for me.
confirm this issue with cm & nandroid restore
-----------
This is true, restore and then install the rom. But how if your restore is the stock rom? NVflash? It's not the same.
Fortunally, Modaco CWM solve it without this procedure.
Thanks!!
This solve my problem with my stock nandroid restore. I downgrade CWM to 3.1.4 (did the backup with 3.2.8 version) and now works perfect!!
Finally i could restore my stock rom.
my solution was...
1. nandroid backup of mcr
2. full wipe & installed cm7
3. nandroid restore of mcr
4. installed mcr without wipe (this solved bootloop after restoring)
Hi all,
I'm just curious on what is the right way to make Nandroid backup on the International Note? *I'm used to my AT&T Galaxy Note that only uses 1 CWM version - so I have no clue with the N7000*
So I already know that I have to use the Abyss Kernel to flash in between Custom ROMs.
How about making Nandroid Backup and Restore?
Should I flash Abyss first, then reboot to recovery (from advanced, not restarting the phone) then make the back up or restore from there?
Or should I use the CWM version of the ROM that I last flash that I want to backup (e.g. Alliance ROM)?
Will it affect restoring from different CWM versions?
Thanks!
keplenk said:
Hi all,
I'm just curious on what is the right way to make Nandroid backup on the International Note? *I'm used to my AT&T Galaxy Note that only uses 1 CWM version - so I have no clue with the N7000*
So I already know that I have to use the Abyss Kernel to flash in between Custom ROMs.
How about making Nandroid Backup and Restore?
Should I flash Abyss first, then reboot to recovery (from advanced, not restarting the phone) then make the back up or restore from there?
Or should I use the CWM version of the ROM that I last flash that I want to backup (e.g. Alliance ROM)?
Will it affect restoring from different CWM versions?
Thanks!
Click to expand...
Click to collapse
Somehow it will affect, and i am not sure you can restore from diff roms.
nandroid backup procedure is same(going in cwm recovery and do backup)
shivg86 said:
Somehow it will affect, and i am not sure you can restore from diff roms.
nandroid backup procedure is same(going in cwm recovery and do backup)
Click to expand...
Click to collapse
Oh ouch .. that is really a good point. So Nandroid does NOT back up CWM?
If it does not, I guess .. I can only restore from nandroid using only one ROM with the same CWM it used.
Hi keplenk =)
I backup and/or restore almost every day. I'm not a cwm-r or android expert at all, just talking from my own experiences.
In the beginning, many months ago, when I just had bought my N7000 I flashed/restored/backup/wiped from all kind of kernels and cwm recovery versions, and it happened that I wasn't able to restore my backups. It was kind of very frustrating from time to time to loose a well tweaked and configured rom. But I was lucky I didn't emmc brick. That I realize today.
Then I changed my cwm-r habits. And I would for backups recommend you just enter cwm-r from whatever rom you are using and make a backup (nandroid). It will backup your kernel and cwm-r too.
To restore I would say it's a good idea to flash Abyss4.2, then REBOOT recovery to full wipe and then restore rom. Make sure you really installed Abyss4.2 and REBOOTED recovery before you wipe because else there could be a risk you end up with a nasty emmc hardbrick depending on if you are on a safe kernel or not. Many people would probably say it's not necessary to wipe, and maybe it isn't. But by the time I didn't it happened once in a while that I got problem with restore, not often at all though, but still it happened a few times. Since I started using this method with wipe, restore has worked fine without any problems hundreds of times (yes, I flash/backup/restore a lot xD, haha).
But once again, I'm just speaking from my own experiences nandroid backup/restore... I don't say it's the proper or best way to do it. It works fine for me though.
Happy Flashing =)
Sent from my GT-N7000 using xda premium
Hello,
I recently migrated from gingerbread 2.3.3 (DarkyROM) to mackay 4.2.2 ROM. I made nandroid backup with CWM before I flashed mackay ROM and also full backup with Titanium Backup Pro. Everything went well all except restoring contacts. After I flashed mackay ROM I realized that they weren't synchronized with Google account. I've tried to restore them with titanium backup pro, but it didn't make any difference.
Now I have TWRP which can't see 2.3.3 nandroid I've made with CWM. My guess is that the solution is to switch to CWM, sync contacts to google, switch back to TWRP, restore nandroid of 4.2.2 ROM and then sync contacts from Google server again.
However, I have no idea how to do that.
Please help, it's pretty urgent.
Thanks!
Have a look at the McKay kernel thread for the flashable McKay settings app and use that to switch between the cwm and twrp recovery
Sent from my GT-i9000 using xda premium
Thanks, I actually got to CWM. However, are you sure I can just restore 2.3.3 GB? Because when I migrated from 2.2.3, I had to install CM9 before CM10.1 in order to avoid IMEI loss.
Hi Guys.
I haven't worked much with CWM so far and couldn't find a proper answer in the threads here.
When I do a restore from a CWM backup I've not seen an option to choose just data or apps ... so I suppose the whole system including the rom and kernel will be restored. right?
As I'm happy to have CM 10.1 running after all finally, I'd just like to restore the data (SMS, etc.) from a CWM backup. Is there a possibility to do so?
Thanks for your help.
Cheers
I don't think you can do that. I used titanium backup pro to restore only the apps+setting to do that.
Sent from my tf101
Ok, thanks. Should have thought about it before.... Sometimes fingers are faster than the brain.
Cheers
You can do an advanced restore and just restore /data but it's not recommented to do this coming from stock and restoring on CM I guess...
Afro said:
You can do an advanced restore and just restore /data but it's not recommented to do this coming from stock and restoring on CM I guess...
Click to expand...
Click to collapse
Why not?
ProtheusIRC said:
Why not?
Click to expand...
Click to collapse
Stock and CM use different bases, and therefore restoring data of Stock can bring over some incompatible data/apk's and this can and most likely will cause a bootloop, from reading i think i can establish the safest way when your changing Rom's is to full wipe and 'clean' install. However when going from nightly to nightly this is not needed, and some data can be restored between same android version Rom's, for example CM10.2 is 4.3.1, data may work on slimbean 4.3.1.
Hope this clears things up for you.
I would also suggest to do a clean install without data recovery. If you want your data you can use Titanium Backup for App data. For the other personal stuff you can make a backup to your PC..
Sent from my 4X HD via XDA Premium
CWM Recovery, URGENT REPLY!!
I faced this problem that my rom got stuck on boot image, so I had another custom rom zip in my sdcard, so to install that I had to format my phone, now I have that backup and I only want to restore system settings, apps, app data, my data(sms, call logs and stuff), I dont want to restore the system or anything else which will make it get stuck on boot image again, now which choices shall I choose in advanced restore to restore only these specified items?
Please reply urgently as I have to travel in a few days and I wont be able to do it over there.
Cheers