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)
Related
Hi guys can some one please help me..
I bought my Galaxy ace last week with gingerbread 2.3.4 (India) in it. i had taken backup using CWM 4. then i updated to CWM5 and installed " CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 (upd: 12.10.2011)" on my phone. i almost liked this ROm but this ROm eats up my battery very fast.. so i decided to roll back to my official ROM which i had backed up. but when i restore the phone it gets stuck in Galaxy ace screen.
Please help me .. how do i restore my backup.
there were no errors during the backup nor during the restore..
Please help..!!
in cwm do a full wipe and then try to restore backup --> never tried this but somewhere read it works...
if this doesn't work then flash ddkq6 firmware from sammobile.com with odin.. install cwn and rollback backup
try the first one ... second one surely will do it
amitkhetan69 said:
Hi guys can some one please help me..
I bought my Galaxy ace last week with gingerbread 2.3.4 (India) in it. i had taken backup using CWM 4. then i updated to CWM5 and installed " CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 (upd: 12.10.2011)" on my phone. i almost liked this ROm but this ROm eats up my battery very fast.. so i decided to roll back to my official ROM which i had backed up. but when i restore the phone it gets stuck in Galaxy ace screen.
Please help me .. how do i restore my backup.
there were no errors during the backup nor during the restore..
Please help..!!
Click to expand...
Click to collapse
it has been asked many times ...search forum ..... it is not restoring because cm 7 uses ext format..and stock uses .rfs.... so u have to convert .ext to .rfs before restoring ... this can be done with ext manager ...( comes with cf-root)
Press thanks if i helped.
Wait. Whatever you do, Making a nandroid backup of your stock rom won't work, it tends to create a md5 file mismatch, a few times, and don't ask me how.
Well, I hate to break it to you, but, just use ODIN all over again,load a stock rom, and things should be as light as rain. But then again, you'd revert to that crappy standard recovery, so flash that with cwm, once you're done ^_^
Ooh, and if I helped, click that shiny 'thanks' button, then.
prateek_gemini said:
it has been asked many times ...search forum ..... it is not restoring because cm 7 uses ext format..and stock uses .rfs.... so u have to convert .ext to .rfs before restoring ... this can be done with ext manager ...( comes with cf-root)
Click to expand...
Click to collapse
well i don't think ext4 manager will work on cm roms even if they are running ketut's kernel as ext4manager checks the kernel you are using..... never tried it ..ketut might have made it to work on it but no one is gonna change fs to rfs on that kernel
hey i know the last option is to flash thru odin .. but is there any other way to restore it thru CWM.. please let me know..
and ya one more thing i m following this thread to falsh thru odin " http://forum.xda-developers.com/showthread.php?t=1242925 " Please tell me whether is it correct and safe..
amitkhetan69 said:
Hi guys can some one please help me..
I bought my Galaxy ace last week with gingerbread 2.3.4 (India) in it. i had taken backup using CWM 4. then i updated to CWM5 and installed " CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 (upd: 12.10.2011)" on my phone. i almost liked this ROm but this ROm eats up my battery very fast.. so i decided to roll back to my official ROM which i had backed up. but when i restore the phone it gets stuck in Galaxy ace screen.
Please help me .. how do i restore my backup.
there were no errors during the backup nor during the restore..
Please help..!!
Click to expand...
Click to collapse
Hi @amitkhetan69...
Sorry to break it to you this way but you are not getting back to stock from custom rom without a full Odin re-flash of stock rom...
Have you tried @Jusada's IceCream Sunday2 (Extreme speed) rom...? Use this rom with a good script that has the ability to manage system resources (check my sig for scripts (V8.5 etc.)). These scripts give excellent battery managment along with many other top drawer tweaks...
There really is no need for you to go through the headache of returning to stock (unless your returning the phone for whatever reason).
FYI : You will need CWM5 to flash any CM7.2 rom... CWM4 will brick ya phone flashing 7.2 rom... "DONT DO IT" CWM5 only for 7.2 roms... I see that you have CWM5 but this could be just incidental to your situation hence my warning (in case you did'nt actually know)...
Stay Breezy n Be Lucky...
Pe"ACE"...
amitkhetan69 said:
Hi guys can some one please help me..
I bought my Galaxy ace last week with gingerbread 2.3.4 (India) in it. i had taken backup using CWM 4. then i updated to CWM5 and installed " CyanogenMod 7.1-cooper-KANG-RC1 Android 2.3.7 (upd: 12.10.2011)" on my phone. i almost liked this ROm but this ROm eats up my battery very fast.. so i decided to roll back to my official ROM which i had backed up. but when i restore the phone it gets stuck in Galaxy ace screen.
Please help me .. how do i restore my backup.
there were no errors during the backup nor during the restore..
Please help..!!
Click to expand...
Click to collapse
Bro, this is because CM7.2 RC1 that you are using is having an ex4 filesystem where stock roms have rfs filesystem. In order to resove this problem, ive made a guide: http://forum.xda-developers.com/showthread.php?t=1606336
Only go uptill STEP 3, if you wish to retain your custom recovery and root.
TheWeirdOne said:
Wait. Whatever you do, Making a nandroid backup of your stock rom won't work, it tends to create a md5 file mismatch, a few times, and don't ask me how.
Well, I hate to break it to you, but, just use ODIN all over again,load a stock rom, and things should be as light as rain. But then again, you'd revert to that crappy standard recovery, so flash that with cwm, once you're done ^_^
Ooh, and if I helped, click that shiny 'thanks' button, then.
Click to expand...
Click to collapse
NANDROID Backups DO WORK. md5 mismatch errors occour when you rename the backup folder. if you want to fix them, here is the solution: http://forum.xda-developers.com/showthread.php?t=1606047
I myself restored my stock firmware using nandroid backups countless times.
madman said:
well i don't think ext4 manager will work on cm roms even if they are running ketut's kernel as ext4manager checks the kernel you are using..... never tried it ..ketut might have made it to work on it but no one is gonna change fs to rfs on that kernel
Click to expand...
Click to collapse
ext4manager works perfectly. i restored from cm7.2 rc1 by vo-1 to stock using my nandroid backup. (ofcourse, fist converted the file partition using ex43manager )
Hi,
i have a few questions:
Lets say I use a stock GB ROM with CM Recovery. I backup in recovery and then try the new ICS. I dont like it yet, but make a backup of ICS anyway.
I try a restore from a ICS's recovery (i think it is still CM recovery, only newer version), but it fails every time (bunch of errors).
Then I flash a stock GB ROM again, and then make a restore, and it works.
Please tell me why is that? Is there a incompatibility with different versions of CM Recovery?
Am I doing something wrong?
Is there a thread which explains this (didnt find one)?
Can I switch between GB and ICS Backups?
Thank you to all who will respond
You can't restore a GB backup in CM*. They use different file systems and partitions. This is explained a lit of times on the forums
So only way for going from ICS to GB is to flash stock GB rom first and then restore it?
Indeed, and the reverse if going from GB to ICS
Hello,
I need to know before install Overcome & CWM if it's possible to backup my stock KERNEL. Currently i have 2.6.36.3 kernel.
I think that is better to restore with the original kernel if need to use tha warranty one day ?
So is it possible to backup or download the stock KERNEL.
Thanks a lot for your help.
before you do anything get a nandroid backup and save that original nandroid backup.
Nandroid Backups are a full ROM backup, that means:
Radios
ROMs
Kernels
User Data
Trying to claim a warranty after you violate the terms and services isn't the most honest thing to but if you intent to cheat the warranty system that just hold on to your backup. A nandroid backs up everything
Hi,
Thanks a lot for your reply. For the warranty I am okay with you regarding the honesty.
About the Nandroid ROM backup, i read somewhere that full backup must be done but it backup all except the Kernel !
I am little bit lost :
1/ The KERNEL Backup can be done with Nandroid backup ?
2/ Can we make Nandroid backup with stock ROM & stock Kernel (fresh TAB) ?
3/ The CWM is it a Kernel ?
Thanks a lot.
subtil123 said:
Hi,
Thanks a lot for your reply. For the warranty I am okay with you regarding the honesty.
About the Nandroid ROM backup, i read somewhere that full backup must be done but it backup all except the Kernel !
I am little bit lost :
1/ The KERNEL Backup can be done with Nandroid backup ?
2/ Can we make Nandroid backup with stock ROM & stock Kernel (fresh TAB) ?
3/ The CWM is it a Kernel ?
Thanks a lot.
Click to expand...
Click to collapse
CWM stands for clockwordmod, its a custom recovery. You need a custom recovery before you can start changing things about your tablet. It is Not a kernel. Think of a car. A kernel is like eh engine, the recovery is like a toolbox. Its more complicated but thats the idea. The stock recovery is too limited, which is why we have custom ones
When you do a nandroid back up it backs up everything. When you do a nandroid back it backs up the kernel as well as the ROM all of your settings and app data. All in one.
If you want a stock nandroid Do it first thing after you have a custom recovery. A nandroid is saved in the clockwordmod folder. Then save that file somewhere safe. Flash drive computer t whatever.
Hope this helps
subtil123 said:
Hello,
I need to know before install Overcome & CWM if it's possible to backup my stock KERNEL. Currently i have 2.6.36.3 kernel.
I think that is better to restore with the original kernel if need to use tha warranty one day ?
So is it possible to backup or download the stock KERNEL.
Thanks a lot for your help.
Click to expand...
Click to collapse
Here is the Flashable zip for backup your Old recovery and kernel
First, You need root
From your stock recovery, Flash backupkernelrecovery.zip.
Approximately 30 seconds, backup process will make a folder "mybackups" in your SD card,
Reboot as normal, and Open "My Files" and see folder "mybackups"..
You'll find 2 file recovery.img(your stock recovery) and boot.img (stock kernel)
For Restore your recovery.img
download overcome cwm from alterbridge86 thread, unzip the file and replace recovery.img from that files with yours..zip again and flash from recovery, reboot and you got your old stock recovery..
Warning: Only restore Stock recovery after nandroid Restore done..with same firmware
Tested on my P7300 and works..
Hello All
Thanks a lot for your help.
I'm now on overcome 2.2.0 with Motley Kernel.
I just done a Nandroid Backup before. I also found on Net a file to restore all, Stock rom & Kernel.
Thanks again.
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
jbin said:
Hi there,
I have a rooted N7000 running original Android v 2.3.6
I want to flash (test) it with a custom ROM.
I made a full backup of my current system (via CWM backup)
Now, when I flash a (new Android 4) custom ROM, will it then be possible to restore the old v2.3.6 image that I made, using CWM?
Other question: Do I need to take care of what type Kernal version I have
I have 2.6.35.7-N7000XXKKA-CL726566
Baseband-version is N7000XXkk5
Thanks for your reply.
Rene
Click to expand...
Click to collapse
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
djoni_gitara said:
nothing to worry about, that is what backup is intended to do.
the only thing you have to watch that you're on safe kernel like philZ when wiping data in stock ics or jb (read sticky threads)
example: if you are on philz kernel and runing ics or jb, when you restore your backup of gb, you restore your gb kernel, system, data etc, just like backing home
Click to expand...
Click to collapse
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Shyam said:
Since you are going to try custom rom, you need not to worry about emmc brickbug, since they will be using a safe kernel..but double check before flashing...so, if you are on Stock ICS kernel, you should NOT wipe/factory reset..if you do, you will brick your phone..you can just go through couple of sticky threads to know abt emmc brickbug, if you are not aware of that..whatever the steps you have mentioned above are correct..but when you flash a custom rom, follow the instructions mentioned in the Custom rom OP...
Click to expand...
Click to collapse
+1
jbin said:
OK, Thanks for the reply. So if I understand correctly:
1. I make a backup of my current ROM (Image via CWM) and put it in a safe place.
2. I can flash any custom ROM, and test/play with them.
3. Afterwards I can put back my old ROM again via CWM restore.
4. Reboot, and I'm back in the old state.
Is this right?
Can I flash ROMs by using CWM also (using zip files) or do I need to flash, using Odin?
I actually do not understand your remark about philZ, can you explain a bit more about what that means.
Thanks for your help so far
Rene
Click to expand...
Click to collapse
1. Yes, copy your /clockworkmod to your pc (just for double safety) dont cut it or move it, you need it on your internal sd card always, if you wanted to restore it again... and dont rename it (you will end up with message md5 missmatch!)
2. of course
3. Every new custom kernel like Philz kernel ( for ICS TW and JB TW) http://forum.xda-developers.com/showthread.php?t=1901191
or hydracore (not working on TW JB, but works on all other) http://forum.xda-developers.com/showthread.php?t=1749863
have built in CWM 6.x.x.x , You can recognize them by the gray background in CWM recovery. (there is no need to install independet CWM or something else, like you do on your stock GB kernel)
They are built in almost every custom rom, and these kernel are safe for wipe.
3.1 . So if you flashed new custom TW ics or jb, and after playing with them, you want back to your nandroid backup, just go boot in recovery (now you see a grey background CWM6) do all the wipes (in my experience the best way is: (advanced > wipe dalvik cache, go back > wipe cache, then wipe/data factory reset, then go into mounts and storage > format cache,system,data and preload , dont format emmc and sd card. go back into backup/restore > restore from (internal sd card or some other place depends on where you place your backup)
4. of course, when youo see a message backup complete, reboot it
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.