Related
Can someone explain how to do a stock carrier rom backup so it can be later (or if something goes wrong during installation of custom rom) restored via odin.
how to do that and which odin version should i use.
Thanks in advance,
Regards
Ummm...U can't make backups with Odin u can do it with CWM but not on stock....
So no backup but u can flash stock rom via Odin when you are done...
ANDROIDCUSTOMIZe said:
Ummm...U can't make backups with Odin u can do it with CWM but not on stock....
So no backup but u can flash stock rom via Odin when you are done...
Click to expand...
Click to collapse
yea i know but i have locked phone and my provider gave me with something like "their custom rom" which is still stock but locked. so if something goes wrong with flashing sutom roms with network i want to have solution for coming back. that's the problem
ANDROIDCUSTOMIZe said:
Ummm...U can't make backups with Odin u can do it with CWM but not on stock....
So no backup but u can flash stock rom via Odin when you are done...
Click to expand...
Click to collapse
We can backup stock rom with CWM...-_-
AnnoyingZlatan said:
yea i know but i have locked phone and my provider gave me with something like "their custom rom" which is still stock but locked. so if something goes wrong with flashing sutom roms with network i want to have solution for coming back. that's the problem
Click to expand...
Click to collapse
Rooted+CWM installed in your phone?
Use cwm recovery to backup your stock rom.
Root your phone, instalar cwm and do a backup.
To restore it you need first to convert the file System to rfs, and then restore the backup through cwm. This is because custom roms use ext4 file system and if you don't convert it, cwm won't restore your backup.
dxppxd said:
Use cwm recovery to backup your stock rom.
Root your phone, instalar cwm and do a backup.
To restore it you need first to convert the file System to rfs, and then restore the backup through cwm. This is because custom roms use ext4 file system and if you don't convert it, cwm won't restore your backup.
Click to expand...
Click to collapse
i know that, but how to do that "convertion" (manually or there's program) from ext4 to rfs after backup in cwm where to find backup file, please explain
To convert system to rfs you must flash a full package firmware via odin
Sent from my GT-S5830 using Tapatalk 2 Beta-5
AnnoyingZlatan said:
i know that, but how to do that "convertion" (manually or there's program) from ext4 to rfs after backup in cwm where to find backup file, please explain
Click to expand...
Click to collapse
I use cf-root ext4 Manager app, easy. There is also a way with adb commands, I don't have the link right now. Google is your best friend (and big brother)
dxppxd said:
I use cf-root ext4 Manager app, easy. There is also a way with adb commands, I don't have the link right now. Google is your best friend (and big brother)
Click to expand...
Click to collapse
O, please give me link for that app. does that go like this:
install apk as any other
convert
do i have to have some special kernels or i can install it on custom rom
EDIT: http://forum.xda-developers.com/showthread.php?t=1158197 this is the link from ketut. do i have to flash whole cf root kernel or i can just install the app on my custom rom's kernel??
AnnoyingZlatan said:
O, please give me link for that app. does that go like this:
install apk as any other
convert
do i have to have some special kernels or i can install it on custom rom
EDIT: http://forum.xda-developers.com/showthread.php?t=1158197 this is the link from ketut. do i have to flash whole cf root kernel or i can just install the app on my custom rom's kernel??
Click to expand...
Click to collapse
Well, if you are going to use cf-root ext4 manager to restore a stock backup its probably recommended to use cf-root kernel, and you will lose the custom rom you're using, so why do you care if it's just the app or the entire kernel?
I don't know if just the app will work, but it's irrelevant. Just Flash a custom rom with cf-root applied, or Flash the cf-root kernel, convert to rfs and you're good to go. You'll restore a backup and basically wipe any custom rom you were previously using.
Otherwise, a Odin one package will revert your file system to rfs, and wipe cwm recovery (so you need to root and istall cwm afterwards and then restore backup)
1. Root your phone
2. Install CWM
3. Backup your Current ROM*
4. Install yuour Custom ROM, and if something happen
5. Flash Stock ROM with odin
6. Root your phone
7. Install CWM
8. Restore your Current ROM*
Make sure you didn't wipe anything in your SD card..
CMIIW
Backup via CMW via recovery
dxppxd said:
Well, if you are going to use cf-root ext4 manager to restore a stock backup its probably recommended to use cf-root kernel, and you will lose the custom rom you're using, so why do you care if it's just the app or the entire kernel?
I don't know if just the app will work, but it's irrelevant. Just Flash a custom rom with cf-root applied, or Flash the cf-root kernel, convert to rfs and you're good to go. You'll restore a backup and basically wipe any custom rom you were previously using.
Otherwise, a Odin one package will revert your file system to rfs, and wipe cwm recovery (so you need to root and istall cwm afterwards and then restore backup)
Click to expand...
Click to collapse
So, first I have to make nandroid backup, I did that.
EDIT : Ok, I have installed cf root kernel, but now how to convert system file to rfs and do backup.. Thanks in advance
Ext4 Manager app will convert your file System to rfs, so do it before restoring backup.
The other way, Flash a Odin one package, root, install cwm and restore.
AnnoyingZlatan said:
So, first I have to make nandroid backup, I did that.
EDIT : Ok, I have installed cf root kernel, but now how to convert system file to rfs and do backup.. Thanks in advance
Click to expand...
Click to collapse
3 ways to do it:
1.EXT4 Manager App
2.Flash Cf-root
3.Flash Odin full package file.
Sent from the year 3000 using a SGA where sheep's are not present.
dxppxd said:
Ext4 Manager app will convert your file System to rfs, so do it before restoring backup.
The other way, Flash a Odin one package, root, install cwm and restore.
Click to expand...
Click to collapse
Thanks, so i just after converting that system file to rfs, do a restore in cwm?
Download .md5 file for stock n flash it via odin 4.38 with Cooper
Sent from my GT-S5830 using xda premium
Yes, once you converted to rfs your stock backup can be restored.
Uhh... Yes you can................
PulseDroid said:
Ummm...U can't make backups with Odin u can do it with CWM but not on stock....
So no backup but u can flash stock rom via Odin when you are done...
Click to expand...
Click to collapse
You can do that, just make sure you root with odin, or the z4root app
Now since it has been recommended not to use CWM on ICS anymore, what are the possible ways to do Nandroid backups / restore? Especially for rooted stock versions.
darthvedor said:
Now since it has been recommended not to use CWM on ICS anymore, what are the possible ways to do Nandroid backups / restore? Especially for rooted stock versions.
Click to expand...
Click to collapse
Chainfire invented that nandroid i dont think there is a program beside CWM.
Its impossible to Nandroid without CWM.
Not all CWM's are dangerous, IF you want to be uber safe, Flash NoteCore kernel its a safe kernel with safe CWM included.
darthvedor said:
Now since it has been recommended not to use CWM on ICS anymore, what are the possible ways to do Nandroid backups / restore? Especially for rooted stock versions.
Click to expand...
Click to collapse
Did u mean cwm is cwm.zip...
Flash custom kernel n do nandrois backup/restore from cwm thats kernel..
Sent from my GT-N7000 using Tapatalk 2
Hi everyone!
Maybe I have a basic doubt, but because I don´t understand, I like have clear this. Yesterday I decided root, replace the recovery and install a custom rom on my Note (N7000). I choose the kernel from PhilZ and install following the recommended method (very easy).
After this all work perfect, I do a full backup of actual system (this is nandroid backup, right?) and after this I install the CM 10.1.3 that also work well. I not rememeber exactly, but following some steps to install this ROM I do before or after install this procedures also: WIPE/DATA FACTORY RESET, WIPE CACHE, WIPE DALVIK CACHE. This procedures are correct?
The device work well, but I have a big doubt because if I boot into recovery I not see anymore the PhilZ touch interface, now I see:
CWM Based Recovery 6.0.3.6
that is other recovery, right? Is normal this behavior? I not understand in what step I change the PhilZ recovery to CWM.
Thanks in advance for all info and help to clear this
This is the CWM recovery same as philz, the difference is that, the version you used before.. It was touch, and after flashing the recovery changes as the CM 10.1 flashed their own kernel...
so it is the same recovery, do not worry
and yes, AOSP/CM roms have their specific kernels, so please do not flash philz on the current recovery...
and one more thing... the process is correct, do a wipe data and factory reset and then format system and preload
Thanks NoteboyTech, yes, I know that work basically like PhilZ, but my main doubt is in what moment of all procedures are installed the CWM Based Recovery. This mean that this CWM are installed in the moment that I install the CM 10.1.3?
Now if I like keep the PhilZ, is safe if I boot again in recovery and install from the .zip file from PhilZ again? or not recommend this?
The wipe: I need made the wipe factory, cache and dalvik before each time that I like restore a ROM or also kernel?
Thanks!!!
You are using a cm rom. Philz kernel Tw doesn't work with cm rom. If you flash philz on cm, phone won't boot.
There is no need to wipe if you just changing the kernel.
If you want the touch recovery, you can install nx kernel which includes philz recovery and is a cm based kernel.
Sent from my GT-I9500 using xda premium
DroidAR said:
Thanks NoteboyTech, yes, I know that work basically like PhilZ, but my main doubt is in what moment of all procedures are installed the CWM Based Recovery. This mean that this CWM are installed in the moment that I install the CM 10.1.3?
Now if I like keep the PhilZ, is safe if I boot again in recovery and install from the .zip file from PhilZ again? or not recommend this?
The wipe: I need made the wipe factory, cache and dalvik before each time that I like restore a ROM or also kernel?
Thanks!!!
Click to expand...
Click to collapse
Read my post again, I edited it!!!
Thanks to all!
Now I believe that understand a bit more
Perfect. This mean that if I like keep the PhilZ as recovery I need install the nx kernel, right?
Now, if for example in the future I like try one new version or actual version of my stock ROM, is safe to download from Samsung Updates website, install from .zip like I do with the CM, and ready, I have the stock ROM. Is correct?
OK, I not need wipe anything for kernel installations, but yes for ROMs, right?
Only data/factory and cache or also dalvik?
This wipes I need made before install the ROM or after?
Thanks for all!
Stock rom has be be installed using odin not like the cm
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
Stock rom has be be installed using odin not like the cm
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Thanks!, ah, right, because stock rom´s should be installed using download mode instead recovery mode, right?
And the last: all the native apps from Samsung like SPen, etc, that go with the stock rom, I can download from any place or installed now into the CM 10.1 or future versions of CM? Thanks!
DroidAR said:
And the last: all the native apps from Samsung like SPen, etc, that go with the stock rom, I can download from any place or installed now into the CM 10.1 or future versions of CM? Thanks!
Click to expand...
Click to collapse
Sorry bro, CM roms cannot do TW features like SNOTE, SPEN, and all.. so with CM you loose all samsung goodies..
NoteboyTech said:
Sorry bro, CM roms cannot do TW features like SNOTE, SPEN, and all.. so with CM you loose all samsung goodies..
Click to expand...
Click to collapse
Ups! :S Small detail Thanks!
One more that I detect: when I boot into recovery (CWM-based Recovery v6.0.3.6) I see that the last and bottom line on main screen say this message bellow. Its important this? Thanks!
Code:
Warning: No file_contexts
Nothing wrong with it. Comes on new Cwm recovery.
Sent from my GT-I9500 using xda premium
Today I try make a complete nandroid backup, but can be possible that the CWM Based Recovery 6.0.3.6 don´t have this option?
Some days back, with the PhilZ recovery, I can do very easy.
To restore a nandroid backup I need use the same recovery or the generated files are compatible with all recovery?
????
CWM 6 versions are compatible.. it can be restored using any recovery.
Why can you make a nandroid back on 6.0.3.6?
Main Menu> Backup & Restore> Backup to Internal or External SD
nokiamodeln91 said:
????
Click to expand...
Click to collapse
Thanks nokiamodeln91!, maybe yesterday when I try Im a bit sleepy at night Also in this moment I found a "nandroid" name into the menu.
Have a link to read how backup the IMEI number?
Can be possible that I detect that after I made all these changes (change the recovery, root, install new rom, etc) the Serial number of the device has changed? I can change from any area to the original one?
Option to backup efs is in the philz recovery. Or you can use ktool from the playstore to backup efs. This has to be done as soon as you root. There is no point of backup if the imei has already changed.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
Option to backup efs is in the philz recovery. Or you can use ktool from the playstore to backup efs. This has to be done as soon as you root.
Click to expand...
Click to collapse
OK, as already tell me I can´t install the PhilZ recovery on CM 10.2, this mean that my only option is install the ktool and backup EFS (this backup the IMEI), right?
nokiamodeln91 said:
There is no point of backup if the imei has already changed.
Click to expand...
Click to collapse
No, the IMEI is correct, the change is in the SERIAL NUMBER of the device, not IMEI. This can be fixed writing the correct serial number?
Not sure how to correct the serial number.
Ktool is a good tool to backup efs.
Sent from my GT-I9500 using xda premium
Well, it so happened that I was on omni rom 4 3.1 with cocore kernel twrp recovery and I saw in a thread that we can theme our recovery by adding a ui.zip file in the theme folder of twrp. Ever since then, my phone boots in recovery only (without the three button combination). Plus in twrp, the theme is applied but I get a super zoomed view of the recovery so I can't restore nandroid as well. Of course, I used my last resort and brought back my phone to stock through odin but the problem is what did I do wrong and what should I take care of to prevent this sort of **** from happening in the future?
Sent from my GT-I9070 using xda app-developers app
Why did you use the co-core kernel for a cm ROM??
The rom shouldn't boot if you did this..
BTW You are getting the super zoomed recovery maybe because you are using the ui.zip designed for a mdpi/ldpi screen resolution.
Our screen is hdpi.
Sent from my GT-I9070 using Tapatalk
But I used the ui.zip for hdpi devices only.. and I dont know.. the rom just flashed when I used cocore. By the way.. I dont see any other method for obtaning recovery except shaan's temporary cwm.. is there any other method as well??
Sent from my GT-I9070 using xda app-developers app
RazaVakil7995 said:
Well, it so happened that I was on omni rom 4 3.1 with cocore kernel twrp recovery and I saw in a thread that we can theme our recovery by adding a ui.zip file in the theme folder of twrp. Ever since then, my phone boots in recovery only (without the three button combination). Plus in twrp, the theme is applied but I get a super zoomed view of the recovery so I can't restore nandroid as well. Of course, I used my last resort and brought back my phone to stock through odin but the problem is what did I do wrong and what should I take care of to prevent this sort of **** from happening in the future?
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Do not mess with something that you are not sure that works on our phone. If you read that someone that has I9070 phone is using something, you can use it. Searching and using stuff from other phones can make you mess like that you got.
Omni MUST use its kernel, you CAN'T use COCORE on it. You will end up with a bootloop if you use COCORE on OMNI.
What you need to do is to flash stock FIRMWARE with ODIN. Download CoCore kernel, UNPACK it and use KERNEL.BIN.MD5 (copy to phone memory). Install UKF and ROOT EXPLORER. Open Universal kernel flasher and follow the procedure to install COCORE. Install, reboot and you have permanent recovery (CWM or TWRP depends what CoCore version you choose).
Perhaps you guys misunderstood me.. I did not flash cocore on Omni.. I flashed cocore on stock and then I flashed omni rom.. so I guess I have permanent recovery..
Im sorry if I sound like a noob but hey, every expert was once a noob, Im learning
I agree to the part of messing with things that people Dont use on our phone, I'll see to that in future..
Sent from my GT-I9070 using xda app-developers app
RazaVakil7995 said:
Perhaps you guys misunderstood me.. I did not flash cocore on Omni.. I flashed cocore on stock and then I flashed omni rom.. so I guess I have permanent recovery..
Im sorry if I sound like a noob but hey, every expert was once a noob, Im learning
I agree to the part of messing with things that people Dont use on our phone, I'll see to that in future..
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
I missunderstood. Because you wrote: "that I was on omni rom 4 3.1 with cocore kernel twrp"
P.S. Maybe that theme problem have something to do with version of TWRP. But I can't tell for sure.
dagger said:
Why did you use the co-core kernel for a cm ROM??
The rom shouldn't boot if you did this..
BTW You are getting the super zoomed recovery maybe because you are using the ui.zip designed for a mdpi/ldpi screen resolution.
Our screen is hdpi.
Sent from my GT-I9070 using Tapatalk
Click to expand...
Click to collapse
By the way, why did you tell the rom should not boot? Is it because the cocorekernel is only supported on android 4.1 or some other reason?
shut_down said:
I missunderstood. Because you wrote: "that I was on omni rom 4 3.1 with cocore kernel twrp"
P.S. Maybe that theme problem have something to do with version of TWRP. But I can't tell for sure.
Click to expand...
Click to collapse
And when I went from omni rom to cm11 by maclaw, my recovery changed to cwm... any idea why did this happen because I was supposed to have permanent twrp
RazaVakil7995 said:
And when I went from omni rom to cm11 by maclaw, my recovery changed to cwm... any idea why did this happen because I was supposed to have permanent twrp
Click to expand...
Click to collapse
The recovery in our phone is dependent on the kernel.
So if the kennel changes, the recovery changes..
Sent from my GT-I9070 using Tapatalk
custom recovery in cm11
So if i flash from stock rom jb to cm11 (tc) , the recovery changes to cwm , no matter if u had CoCore+cwm or CoCore+ TWRP in stock rom.
What happens to the kernel in cm11?
i have done nandroid backup with TWRP, but since recovery changes to cwm in cm11 , will i no longer be able to restore the backup ?
Would it be better to do a nandroid backup with CoCore+Cwm then?
[email protected] said:
So if i flash from stock rom jb to cm11 (tc) , the recovery changes to cwm , no matter if u had CoCore+cwm or CoCore+ TWRP in stock rom.
What happens to the kernel in cm11?
i have done nandroid backup with TWRP, but since recovery changes to cwm in cm11 , will i no longer be able to restore the backup ?
Would it be better to do a nandroid backup with CoCore+Cwm then?
Click to expand...
Click to collapse
If you flash stock JB firmware you get stock recovery (not CWM or TWRP). And you can't use nandroid backup of JB if you are on CM11 because Preload partition is used for SWAP, and it will be non usable for JB. You must flash script to repartition it or flash stock JB firmware. If you have TWRP backup, flash stock JB, root it, install CoCore with TWRP recovery and there you go...
Backup
shut_down said:
If you flash stock JB firmware you get stock recovery (not CWM or TWRP). And you can't use nandroid backup of JB if you are on CM11 because Preload partition is used for SWAP, and it will be non usable for JB. You must flash script to repartition it or flash stock JB firmware. If you have TWRP backup, flash stock JB, root it, install CoCore with TWRP recovery and there you go...
Click to expand...
Click to collapse
Thank you. So i understand that nandroid backup is useful only when something goes wrong during the process of upgrading from stock JB to CM11 .
one more doubt, I have also backed up app user data + system data with Titanium Backup Pro. That can be used to restore all data after i upgrade to cm11 right? Will Titanium Backup Pro take care of efs ( related to IMEI no.) if something goes wrong after flashing cm11. Btw i have also backed up efs with Samsung Tools app.
Also could you enlighten me about my first question in previous post " what happens to kernel in cm11" ?
[email protected] said:
Thank you. So i understand that nandroid backup is useful only when something goes wrong during the process of upgrading from stock JB to CM11 .
one more doubt, I have also backed up app user data + system data with Titanium Backup Pro. That can be used to restore all data after i upgrade to cm11 right? Will Titanium Backup Pro take care of efs ( related to IMEI no.) if something goes wrong after flashing cm11. Btw i have also backed up efs with Samsung Tools app.
Also could you enlighten me about my first question in previous post " what happens to kernel in cm11" ?
Click to expand...
Click to collapse
CM11 ROM 4.4.2 or 4.4.3 is the result of an update of version 4.1.2 of Android Jelly Bean. If right now, you have a backup system and applications that have been stored in the system when you are Jelly Bean. Then you want to restore the backup to the CM11, then I guess you will get an error. Because the system is Jelly Bean, and Kitkat system is 2 different things in the context of the "system". So you can do this while using TB Pro applications only restore data only, such as: backup contacts, sms / mms, third-party applications such as, apk, application of playstore etc.. Not the whole system ROM previously, JB.
Related to the kernel, system jelly bean, and kitkat system, has different kernel. In this case the kernel is owned by CM11 ROM, not the stock ROM 4.4.2/4.4.3 by samsung. CM11 kernel 4.4.2/4.4.3 allows us to perform GPU OC and CPU OC/UC/OV/UV In the default kernel Stock ROM (JB), you will not be able to do it, unless you replace it with a custom kernel, as the Cocore kernel. Hopefully it can be more clear.
I've installed liquidsmooth rom kitkat 4.4.2 on my galaxy s advance GTI9070.. I made a backup of my stock jellybean update using TWRP recovery mode. But it seems that the new rom has CWM recovery mode. I want to restore my phone to backup rom, but i can't access TWRP recovery mode.. Everytime i enter into recovery mode it shows CWM mode and it doesn't show my backup.. Plzz help..
bhaukali said:
I've installed liquidsmooth rom kitkat 4.4.2 on my galaxy s advance GTI9070.. I made a backup of my stock jellybean update using TWRP recovery mode. But it seems that the new rom has CWM recovery mode. I want to restore my phone to backup rom, but i can't access TWRP recovery mode.. Everytime i enter into recovery mode it shows CWM mode and it doesn't show my backup.. Plzz help..
Click to expand...
Click to collapse
On what ROM you was before?
If it was on 4.4 too, take its kernel, install it with Universal kernel flasher and go to recovery and restore it.
Kernel is in ROMs zip, name of it is boot.img.
shut_down said:
On what ROM you was before?
If it was on 4.4 too, take its kernel, install it with Universal kernel flasher and go to recovery and restore it.
Kernel is in ROMs zip, name of it is boot.img.
Click to expand...
Click to collapse
No, i was not on v4.4. I was on stock jellybean update.
bhaukali said:
No, i was not on v4.4. I was on stock jellybean update.
Click to expand...
Click to collapse
Then best way is to flash stock JB with Odin, install CoCore with TWRP and do nandroid restore.
shut_down said:
Then best way is to flash stock JB with Odin, install CoCore with TWRP and do nandroid restore.
Click to expand...
Click to collapse
isn't there any other way without downloading stock JB.. Is there any way i can get get a kernel with TWRP for kitkat 4.4.2 for my phone?
bhaukali said:
isn't there any other way without downloading stock JB.. Is there any way i can get get a kernel with TWRP for kitkat 4.4.2 for my phone?
Click to expand...
Click to collapse
I was lazy to give you full answer there.
First on 4.4. our developers repartitioned preload partition to use it as a swap, and on 4.1.2 there were some apks. So if you want to go from 4.4 (and 4.3.) you must repartition it with this guide.
Then you download SlimKat or OmniROM and use its kernel to get TWRP, extract its ZIP and copy kernel to phone (it is boot.img in root of ZIP file). Then install Universal kernel flasher and some root explorer from the Play store and install kernel. When it is done go to recovery (you will have TWRP) and restore your backup.
P.S. You can use CoCore kernel with TWRP too. But the process is the same.
shut_down said:
I was lazy to give you full answer there.
First on 4.4. our developers repartitioned preload partition to use it as a swap, and on 4.1.2 there were some apks. So if you want to go from 4.4 (and 4.3.) you must repartition it with this guide.
Then you download SlimKat or OmniROM and use its kernel to get TWRP, extract its ZIP and copy kernel to phone (it is boot.img in root of ZIP file). Then install Universal kernel flasher and some root explorer from the Play store and install kernel. When it is done go to recovery (you will have TWRP) and restore your backup.
P.S. You can use CoCore kernel with TWRP too. But the process is the same.
Click to expand...
Click to collapse
Sorry for bothering you guys here, but does someone know how to flash cocore remix r 10 on any rom that is not stock? I mean any other flashable zip roms....... because everytime I end up in bootloop .
pictorul20 said:
Sorry for bothering you guys here, but does someone know how to flash cocore remix r 10 on any rom that is not stock? I mean any other flashable zip roms....... because everytime I end up in bootloop .
Click to expand...
Click to collapse
You get a bootloop because CoCore is for Stock ONLY. You can't use CoCore on any other ROM than on Stock based one.
@shut_down
My zip to restore is needed in 4.4 ROMs based on Team Canjica sources built till 14 June, after that date (since we removed /preload as swap partition on 15 June) is no longer needed with new builds this is only an info, most of the users don't know neither on what build they are :silly: better to continue to tell them to flash that zip before restoring that kind of ROMs, nice work.