I want to install Gingerbread with AbyssNote and Paranoid Android with Asylum N8 and switch between them by backing up and restoring through CWM.
I was told this should work however it fails when restoring Paranoid Android - the md5 check is good but it has an error of "failed to restore /system" when I try to restore PA. Previously when I tried this setup it also failed so I don't think its these specific roms or kernels that cause it.
Is there any way that I can do this successfully?
diji1 said:
I want to install Gingerbread with AbyssNote and Paranoid Android with Asylum N8 and switch between them by backing up and restoring through CWM.
I was told this should work however it fails when restoring Paranoid Android - the md5 check is good but it has an error of "failed to restore /system" when I try to restore PA. Previously when I tried this setup it also failed so I don't think its these specific roms or kernels that cause it.
Is there any way that I can do this successfully?
Click to expand...
Click to collapse
Make sure that the kernel you use to backup the rom is the same one you use to restore it. I'd advise flashing a kernel, reboot to recovery, backup and then again flash whichever kernel you want.
Related
I am having 5 Roms stored thru CWM, and I used to Nandroid restore one every time based in a certain rom property. This is normally an easy process.
The problem is when I am on CM7 or ICS and I want to revert back to restore gingerbread based roms then I have to use Odin for istalling the rom all over again!
whenever I see a blue recovery screen I know there will be a problem.
Is there an easy way for restoring rom without invloving the use of a laptop (Odin)? Sorry if this has been been discussed before, but I have checked thoroughly without luck.
Galaxy S-I9000
Happy new year.
The AOSP ROMs use a different file system to stock ROMs so you can't just CWM a stock ROM on top. You have to install a stock gingerbread rom with odin/heimdall with repartition then you can restore the CWM backup. (can't remember if you have to install a kernel after installing stock)
Thanks but I was hoping for an easier way. Later on I will backup a base ROM then will try to revert to it from AOSP ROMs and will restore the desired rom from there. I have just read from a similar post that is possible.
Hi everybody, I'm quite scary about what I've done today with my tab.
1. I was running under CM 9.1 stable and everything was fine.
2. I backed up my data using ROM Manager and tried today a nightly build of CM 10 from get.cm. I installed it from CWM as written in Cyanogen wiki. Before install I was warned about partition format that wasn't the same as previsouly, and I was asked to choose the update.zip again to enable the ROM flashing to start. CM 10 booted correctly, and it ran very well at first. Then I chose to install Gapps through CWM, the same I did for CM 10.
3. After rebooting, I experienced a bug: the included keyboard kept crashing and was then unusable. I decided then to restore my backup of CM 9 through CWM.
4. I did not encounter any trouble restoring the backup to my old CM 9. But I had no radio, no IMEI, no baseband etc.. in "settings/about the device" and at this point I didn't know that this was because "/radio" wasn't mounted.
5. Now I don't remember what I exactly did but I try wiping caches, restoring again, reinstalling CM 9 stable, reinstalling CM 10 stable, restoring my backup again, flashing the Kernel using Hemsfall but what I remember is:
- I first had problems with /cache
- After that I had the "E:format_volume: "make_ext4fs failed on /cache" message
- My tab reboots if I try to install CM9 stable
- I tried to install a fresh firmware through http://forum.xda-developers.com/showthread.php?t=1133590 but I get stuck at hidden.fs
Now my tab can only boot to CWM or download mode, and whether I choose to flash to CM9 or CM10 I get the message:
assert failed: getprop("ro.product.device")== "galaxtab"...
E: Error in /sdcard/cm-10-nightly....zip
(Status 7)
Installation aborted
I don't know what to do now, and I'm quite desperate right now, please help me to get rid of that "make_ext4fs" error. I'm really afraid.:crying:
When you update to cm10, the mtd partition scheme changed to a new one. Nandroid restore won't work until the partition is made back to the same as when backup was taken.
To be able to run cm again, you need to restock to GB using Odin,
then flash overcome kernel to get cwm.
Only the kernel, not the ROM.
Then use cwm to install cm,
then restore from nandroid.
Follow my signature for overcome guide.
Get GB stock safe v5, the PDF guide, and the overcome kernel.
Jump to page 7.
Sent from my GT-P1000 using xda app-developers app
Thanks you very much, be blessed, it works perfectly using your solution. I felt really really bad, thank you so much!
you are welcome.
You may want to try CM10 again.
Make sure you flash gapps for cm10 only, not gapps for cm9 or cm10.1
It shouldn't be as unstable as you said.
Hello guys,
I would like to flash a different version of CWM onto my N7000 but somehow it does not stick.
I currently run AOKP 4.1.2 and it has 6.0.1.5 as CWM which always gives you the md5 generation error when you do a nandroid backup.
I've installed Rom Manager and downloaded a different version of CWM and tried to install it both with Rom manager and also in CWM itself.
On the first boot after I flash some other recovery like the one from rom Manager (6.0.1.2) it actually loads the new recovery and lets me do a sucessful nandroid for example, but when i reboot into recovery another time the old recovery is back.
When I flash a new rom though, the CWM does get permanently replaced. I flashed a different rom which came with CWM 6.0.2.8 and then I permanently had that version. (same behaviour when I tried to overwrite it with the 6.0.1.2, wouldnt stick).
I even tried just partially restoring the nandroid and leaving boot out, but then phone will get stuck on boot.
Is there any way to permanently flash a recovery to the note without overwriting the whole boot.img? CWM and Rom Manager do not seem to be able. Maybe Heimdall or ODIN? Been so long since I had to use them..
Hope someone knows whats goin on with the recoveries.?!
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
nokiamodeln91 said:
because the recovery is in the kernel. to change recovery, you need to change the kernel. MD5 error is a known bug in AOKP.
you can use this
https://play.google.com/store/apps/...wsMSwxLDIxMiwiY29tLmgzcjN0MWMub25uYW5kYnVwIl0.
to make a nandroid backup on AOKP roms
Click to expand...
Click to collapse
thanks man, yea i got some tools installed that should be able to do a nandroid from running system, was just wondering if there is a way to permanently switch the recovery - it is sometimes booted, right after flash but then its gone - so there must be a way to stop the restore or?
Or are there any custom aokp kernels out there for the n7000? usually they only support TW or CM as far as I saw, or only older versions.
Hi Devs.
I am using Cocore kernal and my mobile is rooted. I have cwm 6. I took backup of my stock rom and after that i moved to Cm11. I installed few apps on cm11 after that i took backup of cm11 also. After That I have installed PACROM and i have backup of that rom also.
Now I have Nandroid backup of all three ROMs( STOCK, CM and PAC)
Then i have decided to restore my stock ROM . Everything went well but when it started it start without any user data and start in start up wizard with message goole.process fail and i got stuck in setting wizard.
After that i tried to restore CM and This time CM start as new rom without gapps and user data but works very fine.
Finally I try to restore pac and it comes out with same result as CM.
Now whenever i restore my backup it restore only rom but no user data or apps.
After that i tried many solution.
I have found one problem in recovery that failed to mount preload
I have fixed the permission but unable to mount preload .
I found one wierd solution to restore stock with data. : First i restore it in CWM after that i reboot my device in download mode and i flash stock JB via odin on my device and suddenly my stock rom start working with all user data
But this solution works with only stock backup and i don't want to restore stock every time via odin.
So please help me to solve this problem.
androiddoctor said:
Hi Devs.
I am using Cocore kernal and my mobile is rooted. I have cwm 6. I took backup of my stock rom and after that i moved to Cm11. I installed few apps on cm11 after that i took backup of cm11 also. After That I have installed PACROM and i have backup of that rom also.
Now I have Nandroid backup of all three ROMs( STOCK, CM and PAC)
Then i have decided to restore my stock ROM . Everything went well but when it started it start without any user data and start in start up wizard with message goole.process fail and i got stuck in setting wizard.
After that i tried to restore CM and This time CM start as new rom without gapps and user data but works very fine.
Finally I try to restore pac and it comes out with same result as CM.
Now whenever i restore my backup it restore only rom but no user data or apps.
After that i tried many solution.
I have found one problem in recovery that failed to mount preload
I have fixed the permission but unable to mount preload .
I found one wierd solution to restore stock with data. : First i restore it in CWM after that i reboot my device in download mode and i flash stock JB via odin on my device and suddenly my stock rom start working with all user data
But this solution works with only stock backup and i don't want to restore stock every time via odin.
So please help me to solve this problem.
Click to expand...
Click to collapse
When you want to go back from CM 11 and 10.2 to previous version of Android you must either to format Prelaod parition, or flash stock JB. On those two versions developers are using that partition as SWAP, so it is has differend format and can't be used for files that should be there on previous versions.
Solution 1: http://forum.xda-developers.com/showthread.php?t=2612540
Solution 2: What you did, flash stock JB from Odin.
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
That mismatch happen because of bad backup I think. You can if you are on other stock based or on CM10.1. For CM10.2 and CM11 ROMs you must repartiton preload partition to be able to do that. HOW.
SultanRTS said:
Hlo Everyone,
I Am a Newbie To Custom Android Roms on Galaxy S Advance .I am on Stock JB with Cocore Kernel And Twrp . I Want To ask if i make a nandroid backup of stock android and try to install other custom rom ,can i revert back to stock jb via backup in case problem arises ...
I had tried this on a different phone but at that time it said md5 sum mismatch .
So Simply I am asking u can i revert back to stock jb via twrp recovery ...
Waiting for reply From GS Advance users ...
Click to expand...
Click to collapse
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
th3cr0w said:
It is possible.
that md5 sum mismatch you had on different phone was most probably related to corrupted backup file - not related with current ROM installed as long as backup is not cross recovery (CWM / TWRP).
I have lost one backup same way due to corrupted files.
To be sure that it will work you can try to restore backup just after it was created - if it will work, then it should work later on.
if you will be trying CM11 revert procedure is a bit more tricky (as /preload partition is used differently than in stock):
it might need odin flash of stock, install CoCore, restore backup
EDIT ... or faster way presented by shut_down ;]
Click to expand...
Click to collapse
I had tried this on galaxy fit ,but there also i got same problem and i had to use odin to get stock back ... i don't want to go over the same pls help me.my phone is hanging a lot and i cant stay on stock so pls help me
To be sure it is not corrupted backup file you can perform restore backup just after it was created.
If it is corrupted due to some reason it will not work from the beginning.
If it go smooth you are sure that you got correct backup - just store it some place safe (not on crappy SD that might go corrupt over time or sth ...)
At that point it is safe to assume it will work as system restore point from any custom ROM back to state of when it was made (official JB with cocore and all your apps / contacts / messages / etc already in place) - with exception of CM10.2 and CM11 ROMS (and those that are based on them) as explained already - those ROMs would need one extra step before reverting (but it is still possible, just not as straight forward as on other ROMs)