Related
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
mad_max911 said:
I flashed I9100XXLP2 ROM from this tread: http://forum.xda-developers.com/showthread.php?t=1420996 ,
After that i flashed Chainfire's CF-Root XXLP2 (Rooted Kernel) from the same tread.
After testing i decide to go back to my previously created CWM backup...
Restoring backup results in boot loop.... TO fix this i need to flash kernel again trough odin.. Tried multiple times....
Why does my old backups not working any more? What has changed?
Click to expand...
Click to collapse
CWM version has changed in the CF-root kernal. Many times the backup done with old CWM is not properly recoverable.
Try wiping the data/cache and dalvik cache and recovering nandroid backup.IF this doesnt work , then Best option would be to get your nandroid backup to PC , format the system , flash a stock ROM,root it and try getting to get the backup working again.
Hope this helps!
I think ICS has a different bootloader to that of GB? If so, flash original bootloader from Intratech thread post #2 with Odin in PDA or Bootloader section:
http://forum.xda-developers.com/showthread.php?t=1075278
Then try restore nan-droid backup again.
Maybe I'm wrong, but you won't hurt anything if you follow his Odin flashing instructions.
Sent from my GT-I9100 using xda premium
Interesting... Ill try some off suggestions later. Just to clarify little more: after boot loop i flash kernel trough ODIN, (syah kernel [same kernel that is in recovery]) and everything works (i boot into previously recover system and all fine...), then going into recovery once again after restoring problem occurs again. So problem is not in CWM as kernel itself contains it...
So, maybe better question would be what part of android system does CWM NOT backup... For example, i now that it does not backup camera firmware... What else? It would be great if this backup/recovery would be more complete (including all software/flash/drivers parts of android system...).
Best regards!
Its simple you require the version of clockwork mode recovery on your phone that you used for the backup to recover .
Caught me out last week and took an age to realize the solution .
jje
Yes, backup was created witth syah 2.6.6 and its CWM version... So, i flashed that kernel trough ODIN, booted CWM and recover- stuck at boot once again...
Sent from my GT-I9100 using XDA App
Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
clown85 said:
Hi guys. I wanted to go back from cm10.1 to stock 4.1.2 and did a nandroid backup with cwm 6.0.2.7 touch and saved my data also with titanium backup.
After flashing stock JB I couldnt find the titanium backups anymore which I realized are stored on internal card so after wiping everything my data is gone. Ja I know my fault. But then I thought I can just restore the nandroid backup I just made to have everything how it was before, but after doing it my screen stopped at the samsung galaxy s3 screen and didnt boot anymore.
Of course I made the backup with 6.0.2.7 and restored it with th same version, but I dont get why its not booting correctly :S
After that I thought I just root the stock phone and flash cm10.1 and try to restore again but it also didnt help.
thax in advance
galaxy s3 gt I9300
Click to expand...
Click to collapse
try philz recovery.
sriram231092 said:
try philz recovery.
Click to expand...
Click to collapse
It says in all the steps E:failed archive external sd
is it a problem to rstore from external sd card? so shall I just try to put it on internal?
Worth trying if you have no backup of it .
jje
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
clown85 said:
Just to make it sure. I root my s3 installing stock jb, then I flash cwm with odin and install su.zip from sd card. always get root access. is it a problem for cwm to flash it first before having root access to the phone???
Click to expand...
Click to collapse
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Endiej said:
CWM doesn't work without root access. Have you tried to install a complete new stock ROM from Sammobile.com? Even though this doesn't recover your data, your phone might work again.
Click to expand...
Click to collapse
My phone works just fine. The problem is to flash the cm10.1 nandroid backup successful to get my internal sd memory back.
btw I tried to copy the backup to internal sd but then it says md5 sum mismatch god damn it..... I just wanna have my internal sd card files back. grrrrrrrr
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
slaphead20 said:
If you have Phil's recovery use the aroma file manager to find and move the back up so it can be seen as I'm guessing you are suffering the sd/0/0 etc problem
Click to expand...
Click to collapse
I guess Im just ****ed... I tried moving it with aroma and then it says error again. its just possible for me to restore the nandroid with cwm which I originally had and just from external sd and even then the logfile says everything is fine just restoring system is an error. that sucks cuz I cant boot the phone then to get access to my internal space via usb
or is there another possibility to restore internal card to get access????
Have you changed recovery versions between creating the backup and trying to restore it?
slaphead20 said:
Have you changed recovery versions between creating the backup and trying to restore it?
Click to expand...
Click to collapse
of course not.
its just weird that I can restore everything exept for this cm10.1 backup. I made already a stock jb backup and I could easily restore this one :S but it doesnt help me anymore.....
Endiej said:
CWM doesn't work without root access
Click to expand...
Click to collapse
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
rootSU said:
Yes it does. Recovery and root are completely unrelated. Read the root guides.
Step 1 - flash recovery via odin
Step 2 - flash su zip via recovery
CWM can flash zips, backup and restore without root access to android. Root access is within android only
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
clown85 said:
Okay thats what I was thinking before hand... I got another idea. can I flash a working ROM like 10.1 and then go to cwm advanced recovery and restore data instead of the whole nandoid system???
Click to expand...
Click to collapse
You can try.
Sent from my GT-I9300 using Tapatalk 2
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
clown85 said:
I have the feeling that my cwm 6.0.2.7 version creates corrupt backups al the time. I just set my phone up with cm10.1 and immediately did a backup on it. I tried to restore it and while restoring it says
Erasing boot before restore...
restoring boot image...
restoring system...
restoring data...
.android_secure.img not found skipping restore of /sdcard..............
restore complete funny funny
please tell me that there is a way to rescue this
Click to expand...
Click to collapse
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
rootSU said:
What's up? Does it not boot? Everything you posted above looks normal so can't advise.
I would recommend updating to latest anyway as 6.0.2.7 hasnt got SDS fix.
Click to expand...
Click to collapse
No it doesnt boot if I try ro restore the backup I end up seeing Samsung Galaxy S3 screen and thats it....
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
clown85 said:
I just updated to cwm 6.0.3.2 and made a backup and it also showed the above problem but this one restores and boots correctly :S
Click to expand...
Click to collapse
What is "The above problem"? If it restores and boots, its fine.
clown85 said:
Another idea is. When I made the first backup with 6.0.2.7 I was also running on yank555 1.6c kernel. Is that important to set up the restore with a running system and this exact kernel? Please tell me what to do if so.
Click to expand...
Click to collapse
Nandroid backup takes
boot.img (kernel)
system.img (ROM)
userdata.img (Your stuff)
Its okay. Somehow I got the data restored with advanced restoring which didnt work with 6.0.2.7 but with 3.2.
close here.
thanx for your help
Hello.
I'd like to give MIUI a try, but, of course, I'd also like to switch back to my stock ROM if things go wrong or if I don't like MIUI.
How can I backup my entire phone (rooting, Recovery Mode capability and other on-power key-combination-activated features etc etc) and 100% failsafe restore it at any time?
Thanks in advance.
Rooted stock = do a nandroid (CWM) backup which is essentially an 'image' of the phone at the time you make the backup. Try MIUI; don't like it ? Restore the nandroid you took of your rooted stock setup. Sorted (You will need to ensure you backup the contents of your external SD card separately if you have one).
Be careful you don't 'overthink' this, it's really very simple both ways (backup/restore).
My Recovery Mode doesn't have a backup option
MistahBungle said:
Rooted stock = do a nandroid (CWM) backup which is essentially an 'image' of the phone at the time you make the backup. Try MIUI; don't like it ? Restore the nandroid you took of your rooted stock setup. Sorted (You will need to ensure you backup the contents of your external SD card separately if you have one).
Be careful you don't 'overthink' this, it's really very simple both ways (backup/restore).
Click to expand...
Click to collapse
Thanks for prompt response. I took a look at current Recovery Mode menu and it doesn't include a backup/restore option like in http://forum.xda-developers.com/wiki/ClockworkMod_Recovery. It shows only the above:
Code:
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
test redbend fota[FS]
-----------------------------------
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ZVV
Successfully applied multi-CSC.
I've already downloaded Recovery from clockworkmod.com but didn't do anything with it yet.
Sorry if it has already been detailed in another thread, but I didn't find it and I don't know how to make such nandroid backup.
Thanks.
OBackup
I've just downloaded OBackup app from Play store and am doing my backup.
My question is: after I flash MIUI, what are the tools/steps I'll need to restore my backup?
Thank you very much.
That's the stock Android recovery.
OK...
What you need to do is not install CWM separately. That will only persist until you reboot & is designed to allow you to flash whatever rom/kernel you want which will have it's own version of CWM baked into the kernel.
That backup program you're using; no idea as I've never used it.
What I recommend you do is find a custom kernel you like (actually, any custom kernel will do given you're going to flash Miui) which will have CWM. Flash that into your stock setup, then make a nandroid (CWM) backup of your stock setup so you can go back to it if you don't like Miui/whatever else you try (If you restored this & wanted to go back completely stock/unrooted/etc, all you'd need to do is flash a stock kernel). This is what you asked for in your OP. I warned you not to start overcomplicating things, and this is exactly what you're doing.
The kernel supplied with Miui should have CWM, so if you find you don't like it, you should be able to simply restore the backup you made of your stock setup in CWRecovery.
I also very strongly recommend you learn 'the basics' as you seem to be lacking in this knowledge. Flashing stuff/etc without knowing these things leads to busted phones. Read the tutorials/guides stickied near the top of the General section; there's a wealth of information in those.
Hi!
I've a similiar problem with my GT-i9100!
Can I do a restore of my stock ROM (that have android 4.1) if I've install a costum ROM like RootBox that have a different version of android (4.2.2)?
Can my phone brick because there are a differents kernel?
Tnx you all! ^^
Rox666 said:
Hi!
I've a similiar problem with my GT-i9100!
Can I do a restore of my stock ROM (that have android 4.1) if I've install a costum ROM like RootBox that have a different version of android (4.2.2)?
Can my phone brick because there are a differents kernel?
Tnx you all! ^^
Click to expand...
Click to collapse
No it won't brick.
sadekmefti said:
No it won't brick.
Click to expand...
Click to collapse
Hi and tnx for reply!
I've try to do a restore of my sock rom from recovery but it's says to me that there is an error on md5 check sum...
I've install the RootBox ROM in my gt-i9100...but I can't come back to sock from recovery because the stock kernel dosen't work with RootBox's Kernel...
so I've to use odin to flash the stock firmware.......at the origin, my idea didn't comprised use odin because of download mode counter (so that why I did a backup!)...but now I don't have any other way...!
...what a sad story.. XD
Rox666 said:
Hi and tnx for reply!
I've try to do a restore of my sock rom from recovery but it's says to me that there is an error on md5 check sum...
I've install the RootBox ROM in my gt-i9100...but I can't come back to sock from recovery because the stock kernel dosen't work with RootBox's Kernel...
so I've to use odin to flash the stock firmware.......at the origin, my idea didn't comprised use odin because of download mode counter (so that why I did a backup!)...but now I don't have any other way...!
...what a sad story.. XD
Click to expand...
Click to collapse
You can't restore your backup because of a different MD5 SUM which means that your backup has been corrupted.
Flashing a stock ROM or Kernel via ODIN will not increase your flash counter.
Flash NeatROM Lite, this is the best ROM ever, it like stock with additional things.
Sent from GT-I9100 using Tapatalk 4
sadekmefti said:
You can't restore your backmyf a different MD5 SUM which means that your backup has been corrupted.
Flashing a stock ROM or Kernel via ODIN will not increase your flash counter.
Flash NeatROM Lite, this is the best ROM ever, it like stock with additional things.
Sent from GT-I9100 using Tapatalk 4
Click to expand...
Click to collapse
DIO *******************
I will cry...... :'( so the recovery hadn't save well my backup..I read about similar error and I hoped that was thet...
My last chance is use Odin..
Only a question: can I flash the stock rom from recovery renaming the file .tar.md5 in .zip?
Tnx for you for the counsel! I will try thet rom after solving this problem! For now I have changed rom and I'm using MIUI and it works really well!!
Rox666 said:
DIO *******************
I will cry...... :'( so the recovery hadn't save well my backup..I read about similar error and I hoped that was thet...
My last chance is use Odin..
Only a question: can I flash the stock rom from recovery renaming the file .tar.md5 in .zip?
Tnx for you for the counsel! I will try thet rom after solving this problem! For now I have changed rom and I'm using MIUI and it works really well!!
Click to expand...
Click to collapse
You can't flash a stock ROM from recovery by changing .tar.md5 to .zip .
You want to change ROM to Stock, use Mobile Odin to flash a Stock ROM or Flash NeatROM v4.8 Lite.
sadekmefti said:
You can't flash a stock ROM from recovery by changing .tar.md5 to .zip .
You want to change ROM to Stock, use Mobile Odin to flash a Stock ROM or Flash NeatROM v4.8 Lite.
Click to expand...
Click to collapse
Tnx you! I understand what I have to do! I'll try your rom today
Tnx again!!!
I am aware that this has been asked before but there are conflicting answers withing the threads that I have read.
I am running 4.1.2 WLSW having worked my way through the various jb releases over time. Root has been retained using everroot in mobile odin. The kernel is stock.
Having decided to install a stable release of cyanogenmod (10.1.3) I have been reading around for days to avoid pitfalls or to know what to do should a problem arise.
The only one thing that I am still unsure about is whether it is indeed safe to use a temporary cwm (flashed via stock recovery) to install cyanogenmod. I have downloaded the latest temporary cwn from the rommanager site and it appears to work just fine - I have created a backup without issues so I can get back to where I am now if I don't like or have problems with cyanogenmod.
I was planning to flash [KERNEL] ClockworkMod Recovery 6.0.2.9 from this thread http://forum.xda-developers.com/showthread.php?t=1118693 - but in the last couple of pages in the thread there are users that have had boot failures after flashing it. This is what has lead me to ask the question is it safe to use the temporary cwm?
I am aware that there are other kernels that I could use (Philz/Siyah) but would like to know which cwm is safest/best for the installation of cyanogenmod.
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
andrewwright said:
Install philz kernel by flashing in stock recovery and put that zip on ext sd. Stay away from rom manager. Dont use it. When you have philz installed make a nandroid bkup and make sure preload is included too. Also bk up you're efs folder with ktool free from playstore. As you have root get that and bk efs up asap. once you have done a nandroid bkup and done the efs bkup then flash cm. May be good to get a copy of you're modem now too.
Click to expand...
Click to collapse
I have backed up efs already using ktool and have already made a nandroid backup using temporary cwm - good advice none the less.
I have read that rommanager is problematic with the i9100 so am not planning to use it.
My method of choice to flash Philz would be mobile odin (unless there is some disadvantage by doing it this way?).
Regarding my modem, it is included in the stock firmware so I could flash just the modem from this using mobile odin if I have trouble (I have assumed mobile odin works in cm).
My original question remains however - why not use temporary cwm?
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
andrewwright said:
Mobile odin will work on cm. And yes you can flash with temp cwm. Get you're modem from here on xda. Makes no odds how you flash philz Use odin or recovery its up to you.
Click to expand...
Click to collapse
If I can flash with temp cwm, there is no need to flash philz at all - or have I missed something?
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
andrewwright said:
If you flash with temp there's no guarantee. Philz then flash is a safer way of doing things.
Click to expand...
Click to collapse
Presumably the latest Siyah kernel will also do?
Yes that's ok
It's simply a matter of preference.....temporary CWM is as it 'says on the tin'........temporary....
You have to reflash it every time you want to use it.
PhilZ is permanent....once it's flashed, it's there, no further action needed, plus it has a touch interface unlike regular CWM......
If you intend to stay with stock, but want to have the advantages of CWM, then I'd advise go with PhilZ...purely because a few steps less are necessary to be able to use it.......
(Enter stock recovery, flash CWM then use CWM to flash whatever..... every time with temporary CWM)
If you intend to flash a custom ROM, it'll come with its own permanent CWM anyway (which will overwrite the PhilZ kernel and/or remove the need to continuously reflash the temporary CWM)
Sent from my GT-I9100 using xda app-developers app
Thanks for the advice folks. I flashed Siyah then installed cm 10.1.3 and the associated gapps. All went without a hitch. I was actually surprised how quickly the process completed. I had the rotating cm boot image less than 2 minutes after starting the install from first zip.
Off topic, but I am totally impressed with the cm ROM. I find my frustration at constantly waiting for phone manufacturers to catch up with vanilla android releases has completely melted away.
Glad it's sorted :thumbup:
Add solved to name of thread pls
I am almost ready to perform my first custom ROM installation.
I am only travelling with a Mac so I can't use Windows software.
Is there a way to backup my/EFS directly from the phone?
Sent from my GT-I9100 using Tapatalk
You need a custom recovery. How will you flash a custom rom w/o custom recovery?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Blomberg said:
I am almost ready to perform my first custom ROM installation.
I am only travelling with a Mac so I can't use Windows software.
Is there a way to backup my/EFS directly from the phone?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Download HC ktool from the market, create your efs backup with it and use a root explorer to copy it to an external removable micro SD card......
Edit.......you need to be rooted in order to use HC ktool.......
This might be my S2, or it might be my W...but it's definitely CM
mezo91 said:
You need a custom recovery. How will you flash a custom rom w/o custom recovery?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For rooting I will use Framaroot.
For installing CWM I believe that you can install it via ROM Manager, or you can install the ROM directly via Mobile Odin.
Sent from my GT-I9100 using Tapatalk
OK....first....
Why look elsewhere for rooting methods? Everything you need is right here on XDA.
Second.....NEVER use ROM manager on an S2.....it breaks things.
Third....mobile Odin can only be used on rooted devices....primarily for flashing stock firmwares.
What version of android is on your S2....GB, ICS or JB?
This might be my S2, or it might be my W...but it's definitely CM
Yes, I found Framaroot here and am planning to use it for the rooting purposes.
Thanks, good to know. So I will need to install CWM manually I guess. Somehow.
What is it that Mobile Odin does, is it an actual reovery ROM itself or does it install CWM which in turn installs the ROM?
But I can use Mobile Odin to install a custom ROM I think?
I am 4.1.2 JB
Sent from my GT-I9100 using Tapatalk
Mobile Odin is a phone based version of PC Odin.....it is designed to flash back to stock from a rooted modified phone without the need to hook the phone to a PC....
You're on 4.1.2.....
Search for the PhilZ thread.......
With the downloads contained, you can root and flash CWM via the stock recovery in one flash.....don't get much easier than that.......
This might be my S2, or it might be my W...but it's definitely CM
I can root it and flash it in one step? I've found like 50 guides but none of them as simple as you're suggesting.
There are so many ways to do each individual step.
I reckon the steps after that would be to install my custom ROM via CWM via SD card. Clear/Wipe cache and install the custom ROM again?
Sent from my GT-I9100 using Tapatalk
Edit: How can I backup EFS before using the technique you mentioned to root/flash CWM in one go, if my device is not yet rooted?
As I said........easy.....
1) flash PhilZ via stock recovery to root and flash CWM
2) At this stage your phone will still boot normally and allow you to download HC ktool in order to make your EFS backup. It might be an idea to make a full backup (nandroid backup) of your current setup using CWM too....
3) use CWM to flash the ROM (and it's associated gapps package) of your choice.
4) use CWM to perform the cache, dalvik and data wipes.
5) reboot, perform initial setup download user apps.......
Job done.......
This might be my S2, or it might be my W...but it's definitely CM
You could also juse Siyah Kernel, a good alternative to philz:good:
Except that it can't be flashed via the stock recovery.....it has to be flashed via Odin......
This might be my S2, or it might be my W...but it's definitely CM
In which way does a Kernel replace a rooter/bootloader flasher, are these not different things?
Sent from my GT-I9100 using Tapatalk
keithross39 said:
As I said........easy.....
1) flash PhilZ via stock recovery to root and flash CWM
2) At this stage your phone will still boot normally and allow you to download HC ktool in order to make your EFS backup. It might be an idea to make a full backup (nandroid backup) of your current setup using CWM too....
3) use CWM to flash the ROM (and it's associated gapps package) of your choice.
4) use CWM to perform the cache, dalvik and data wipes.
5) reboot, perform initial setup download user apps.......
Job done.......
This might be my S2, or it might be my W...but it's definitely CM
Click to expand...
Click to collapse
I very much appreciate your help Keith. I've been on numerous forum but never got this good feedback.
I searched the PhilZ thread and got so many results. My model is i9100 of the Galaxy S2, I guess the methods you have been describing works for this model?
I need to backup program data and EFS before I dare start playing around.
How can I backup EFS before using the technique you mentioned to root/flash CWM in one go, if my device is not yet rooted?
You can't. And you don't need to unless your phone is rooted, because if your phone is rooted nothing you can do to the phone is capable of borking the EFS/IMEI.
Edit - Also, I'm detecting a lack of knowledge of 'the basics' in the threads you've posted recently; I strongly suggest you read all the guides/tutorials stickied in the thread near the top of the General section before you do anything to your phone. A lack of knowledge exponentially increases the risk of you permanently breaking your phone depending on how little knowledge you have when you attempt to 'do stuff' to the phone.
For backing up the efs you'll need to flash a recovery first (like Philz as already suggested).
But anyway, problems with the efs won't be caused by just rooting so you can go ahead and root first and then use KTool.
kestrel5915 said:
For backing up the efs you'll need to flash a recovery first (like Philz as already suggested).
But anyway, problems with the efs won't be caused by just rooting so you can go ahead and root first and then use KTool.
Click to expand...
Click to collapse
* * *
Thank you. As I want to perform all the necessary steps directly on my phone, I am now thinking of doing the following.
Installing Framaroot (APK) and rooting my Samsung Galaxy S2 i9100 (http://forum.xda-developers.com/showthread.php?t=2130276)
Installing KTool and backing up EFS to external SD-card
Installing Titanium Backup (Root version) to backup AppData
Alt 1.) Downloading Mobile Odin to OS. Flashing ROM + GApps via this. But this keeps my stock recovery? (http://forum.xda-developers.com/showthread.php?t=1347899)
Alt 2.) Downloading PhilZ Touch Recovery 3.0 for Galaxy S2 i9100 which flashes + re-roots for me (?). Not sure if it's the right version as the post is old? (http://forum.xda-developers.com/showthread.php?t=1840223)
Alt 3.) Flashing CWM via Mobile Odin, and then in turn boot to recovery (now CWM) and flashing ROM + Gapps via CWM. This should update my recovery as well as my ROM?
After flashing ROM, entering recovery to Wipe Cache, Dalvik and Data
Flash ROM again as previous step supposedly deletes the ROM?
Boot ROM, Configure, Install Apps and restore App Data
Does the above look correct?
Is the version of PhilZ the correct one? It appears to be a 'temporary recovery' rather than a permanent, which might be what I am after if I want to flash the current version of CWM for Galaxy S2 from www.clockwerkmod.com/rommanager
Follow the instructions I gave in this post....
http://forum.xda-developers.com/showthread.php?p=48583106
and you will have a rooted phone running a custom ROM. No need to reflash the ROM after the wipes. Wiping cache, dalvik and data will NOT erase the ROM, all it'll do is erase any personal settings and downloaded apps.
Mobile Odin can't be used to flash custom ROMs, I think it can be used to flash CWM.... but only if you can find a compatible version in a .tar format.
PhilZ is still your best bet.....you will root your phone and install CWM in one hit.....all from your existing stock recovery. The CWM inPhilZ is NOT temporary, though it WILL be overwritten when you flash the ROM which will contain it's own permanent version of CWM. Just match your phones build version to the PhilZ kernel that you download.......
Why make extra work for yourself by increasing the number of steps you have to take (use framaroot then try to find a compatible CWM) when you can do it in one step?
And as mentioned before.....DON'T use ROM manager on an S2.....it breaks things....specifically recovery....one of your prime goals.....
This might be my S2, or it might be my W...but it's definitely CM
cubflyer said:
You could also juse Siyah Kernel, a good alternative to philz:good:
Click to expand...
Click to collapse
I made big projects of things. As a complete novice within Android, I've read through numerous threads, made project notes, consolidated info and made Mindmaps to understand this.
From my understanding, a kernel (I've seen Siyah mentions on many places) is the interpreter between hardware and the instructions given by the software.
In which way is this comparable to a recovery partition/ROM, namely PhilZ?
I'm sure it's some detail I'm missing, and thanks for the tip.
keithross39 said:
Follow the instructions I gave in this post....
http://forum.xda-developers.com/showthread.php?p=48583106
and you will have a rooted phone running a custom ROM. No need to reflash the ROM after the wipes. Wiping cache, dalvik and data will NOT erase the ROM, all it'll do is erase any personal settings and downloaded apps.
Mobile Odin can't be used to flash custom ROMs, I think it can be used to flash CWM.... but only if you can find a compatible version in a .tar format.
PhilZ is still your best bet.....you will root your phone and install CWM in one hit.....all from your existing stock recovery. The CWM inPhilZ is NOT temporary, though it WILL be overwritten when you flash the ROM which will contain it's own permanent version of CWM. Just match your phones build version to the PhilZ kernel that you download.......
Why make extra work for yourself by increasing the number of steps you have to take (use framaroot then try to find a compatible CWM) when you can do it in one step?
And as mentioned before.....DON'T use ROM manager on an S2.....it breaks things....specifically recovery....one of your prime goals.....
This might be my S2, or it might be my W...but it's definitely CM
Click to expand...
Click to collapse
Thank you once again Keith for your engagement and good tips.
I think the reasons why I am considering the different options, and also trying them out - is to get a broader understanding of Android and the alternative processes as I approach my goal of flashing a new ROM.
1.) So far I installed Framaroot and rooted the device successfully.
2.) I then downloaded Hellcat's kTool and made an EFS backup (and a kernel dump, whatever that is)
3.) Then I installed Titanium Backup and backed up all user + system apps (+data I think)
4.) I then downloaded CWM from www.clockworkmod.com/rommanager > recovery as a zip, booted the stock recovery and started CWM (locally, without replacing stock recovery for some reason), from which I did a full Nandroid backup (with stock recovery intact in this backup, I guess. Device was however rooted so it's not fully original).
I reckon I now just need to download my custom ROM and it's relevant Gapps.
I have read good things about Mobile Odin, and since a while back it supports *.zip files so I believe it is a good alternative for flashing custom ROM's now as well.
PhilZ was a bit intimidating, as there was a general thread and different model based threads in each subforum. They were also in different versions, dates and basebands. Also it appears to be available in a "permanent" download as well as a "temporary", which caused my confusion in the last thread.
I did not know that the recovery was replaced when installing a custom ROM, as I did not know that they contained their own partition of a recovery ROM.
Thanks for the information about not needing to re-flash ROM after the relevant wipes.
Thanks for the discouragement of ROM Manager, I promise to stay away from it.
From my understanding, PhilZ seems to be a modified version of CWM6, which includes ChainFire's Auto Root and some other add-ons as well. Is this a correct understanding?
You don't need to backup system apps/data from Titanium Backup because restoring them on a new rom will definitely cause issues.
Plus in case of a bad flash or something nandroid is always there for you so before doing anything new with the phone always do a nandroid backup.