Hello Everybody,
Last week I have made a CWM backup of Stock 4.1.2 with Philz touch recovery and then installed CM 10.2.
Yesterday I flashed PhilZ-cwm6-DDLSC-ODD-5.11.2-signed.zip and rebooted into recovery to restored my previous CWM backup of stock 4.1.2
I did all wipes and restored backup successfully. After rebooted I can see only a black screen with status bar with three icons (battery,time and network).I hve tried for two times but same problem.Then I reinstall CM10.2 using recovery.
I didnt understand where I have mistaken.
Please tell me what to do? I want to restore my backup.
Thanks in advance.
Sent from my GT-N7000 using xda premium
did you check if the restore preload was selected?
nokiamodeln91 said:
did you check if the restore preload was selected?
Click to expand...
Click to collapse
I dont understand. I mean how to check it?
Thanks...
Sent from my GT-N7000 using xda premium
Some where in misc nandroid settings.
You mean I have to check Preload after restore my cwm backup?
Sent from my GT-N7000 using xda premium
You have to check it before restoring the backup as stock 4.1.2 uses preload partition for a lot of apks.
I really don't get what you are asking. You have to go to nandroid setting and place x besides include preload.
nokiamodeln91 said:
You have to check it before restoring the backup as stock 4.1.2 uses preload partition for a lot of apks.
I really don't get what you are asking. You have to go to nandroid setting and place x besides include preload.
Click to expand...
Click to collapse
Ok,No problem.I have Installed SweetRom 10.5 Black for 4.1.2.
And Thanks for your kind help.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Related
ive been searching every where on how to do this with out reflashing my rom. i did a nandroid but i updated the recovery so i cant use that it gives me some suggestion to do it via adb. if there is no other way to get it back i guess i will go about it that way but if there is a apk available that will be much more appreciated!
Flash through recovery:
http://db.tt/A1VCXiM
Sent from my Nexus One using XDA App
will give it a shot thanks
EDIT: Works great! thank you so much
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Sent from my Nexus One using XDA App
cmstlist said:
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Click to expand...
Click to collapse
You can also flash another custom recovery from ROM Manager...
Sent from my Nexus One using XDA App
cmstlist said:
Glad it's resolved, but I don't see why an updated recovery would preclude you from restoring the nandroid backup. In Clockwork recovery you can go to Advanced Restore and restore only the System partition from the recent backup.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
wouldn't the restore overwrite the current recovery in place?
solidmac said:
wouldn't the restore overwrite the current recovery in place?
Click to expand...
Click to collapse
Recovery is not part of the system partition, and in typical nandroid backups it is not even imaged as part of the backup.
Tried link in OP, just goes to Drop Box login.??
That's because I remove the file after a while...
http://db.tt/A1VCXiM
Sent from my Nexus One using XDA App
@danger-rat, Thanks for putting it up again. Got it now.
Everytime I factory reset, I went to bootloop and my nandroid backup also had md5 mismatch.....
I tried to remove this mismatch. But it failed!!!
Sent from my GT-S5830 using xda premium
Then it's a bad backup
This was sent from a Galaxy Ace. Problem?
EmoBoiix3 said:
Then it's a bad backup
This was sent from a Galaxy Ace. Problem?
Click to expand...
Click to collapse
This is my friend's ace dude.... My ace had such problem.... Please help!!
Sent from my GT-S5830 using xda premium
Are you on stock rom cuz then you have to convert your ext partition first before backups can work
GOOD LUCK
I had the same issue on my ace and nothing fixed the issue. I deleted the backup, flashed rom again and used CWM 5 to create another backup... Working fine since then with no issues while restoring....
Sent from my GT-S5830 using xda premium
CWM 5 or 4...... Try flashing a nandroid backed up rom.... For ex. Aashrom (maybe.... Wrong spelling. )
thespb said:
Everytime I factory reset, I went to bootloop and my nandroid backup also had md5 mismatch.....
I tried to remove this mismatch. But it failed!!!
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
have you renamed your backups and left gaps in what you've renamed them to, ie "new rom 30 04 12", instead of "new-rom-30-04-12 " cwm don't like gapp in-between words and will throw up md5 mismatch errors if you do, if this is the case, just fill the spaces in what ever you renamed them to and cwm will allow you to restore previously saved backups
Do another backup
Stock nandroid backup and md5 mismatch solution
thespb said:
Everytime I factory reset, I went to bootloop and my nandroid backup also had md5 mismatch.....
I tried to remove this mismatch. But it failed!!!
Sent from my GT-S5830 using xda premium
Click to expand...
Click to collapse
Greetings bro,
If you are trying to restore a nandroid backup containing your stock rom, then check this guide out: http://forum.xda-developers.com/showthread.php?t=1606336
Only follow it up to STEP 3.
For md5 mismatch error you can see this guide: http://forum.xda-developers.com/showthread.php?t=1606047
Hope i helped.
If I flash CM9 (link) with CWM can I switch back to CM7 by flashing with CWM, for example can i switch back to the MiniMod X ROM(link)?
Yes you can but before and after installation wipe data and cache it's better for your phone and finally dont forget to make a nandroid backup
Sent from my GT-S5570 using xda premium
Yes. CWM stays intact. If that is what you are afraid of.
You can switch between roms any number of times
genieass said:
Yes. CWM stays intact. If that is what you are afraid of.
You can switch between roms any number of times
Click to expand...
Click to collapse
Yes you're right he must don't forget to make a nandroid backup of his phone to restore it if he have an issue like boot loop
Sent from my GT-S5570 using xda premium
Hi All,
Is it OK or Possible to Nandroid restore my old Stock ICS ROM from CM10 CWM ROM(Recovery) ?
Thanks.
Yes. Done it many times.
Sent from my GT-N7000 using Tapatalk 2
You're on a safe kernel, so it will be fine, be aware when back on ics if on stock kernel you need to be careful or install safe kernel.
Sent from my GT-N7000 using xda premium
yeah I guess if he made a nandroid backup of a stock rom.. 99% it has a safe kernel in it.
Thanks for the help guys ... :highfive:
& I hope the other way is also OK (Restore CM10 Nand backup from ICS CWM recovery) ?
ya
nokiamodeln91 said:
yeah I guess if he made a nandroid backup of a stock rom.. 99% it has a safe kernel in it.
Click to expand...
Click to collapse
SpyderTracks said:
You're on a safe kernel, so it will be fine, be aware when back on ics if on stock kernel you need to be careful or install safe kernel.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Sorry if I am asking/saying something wrong..will the Nandroid restore work if currently using a different kernel than the backed up one? Read somewhere that current kernel & backed up kernel should be the same for the restore to happen properly..
no.. u can restore the nandroid made on any kernel. just that when the nandroid restore completes the kernel will be that inlcuded in the nandroid
Thanks guys :good:
You may well face bootloop after restore, just clear cache and dalvik from recovery, should clear it fine.
Sent from my GT-N7000 using xda premium
clear cache and dalvik from recovery + format /system
then restore from recovery
(recomended) restore using recovery & kernel you using for backup
works great for me
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Hi xda community. I'll try to explain exactly what I did and what's happening.
I flashed Cyanogenmod and everything went fine. As the latest Nighty became available, I downloaded it and tried to apply the update. I'm using Philz Touch as recovery. The update process started as usual, but then it stopped when it was almost done. I rebooted recovery and it begun again to install the update without success at all.
I've opened Odin and tried to re flash the recovery, hopping that I would be able to get to the normal Philz Touch recovery and it started (again) the update process.
I've ticked NANDROID full wipe and flashed the recovery again and I got the recovery menu. I performed a Nandroid restore, and recovery couldn't mount the /data partition.
I've realized that the /efs partition wasn't mounted. I manually mounted it and Nandroid backup successfully restored everything.
Ripper ROM (Samsung Based) booted up well, and I had to flash a modem since I didn't have signal. I thought everything was fine. But now as soon as I install a new ROM (either Sammy Based or AOSP) I lose my IMEI and get in Factory Mode.
I've tried restoring efs from backup and it didn't work. The only way I get it to work is restoring from Nandroid backup.
Can anybody help me please?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
AW: Strange IMEI behavior
Rekoil said:
Does Ripper Rom use Perseus kernel perhaps? If so, join us over here.
Click to expand...
Click to collapse
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
jjpro45 said:
Yeah, I'm running that kernel...is that perhaps what's causing the problem with the /efs partition?
Edit: tried to flash another kernel and got no signal but as long as I flash Perseus it works!
Why is this happening???
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Beats me mate, myself along with a couple others are having the same exact problem. We have no idea what is going on. Discuss possible solutions in the thread I linked.
AW: Strange IMEI behavior
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
jjpro45 said:
Does that means that I'm now stuck on that kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yes, join the club.
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Cundis said:
So, does this mean those of us haven't got this error should stay away from the Perseus kernel?
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Not at all. I have been using it from the start. Will choose it every day over stock kernel
nateboi81 said:
Not at all. I have been using it from the start. Will choose it every day over stock kernel
Click to expand...
Click to collapse
Just out of curiosity, what happens if you install a non-Perseus kernel?