Hello - I am using Sony Xperia S. I have tried all kernels - Advanced Stock ICS Kernel, SSpeed Kernel and XSX Kernel, but I still haven't gotten the backup/restore function to work properly.
When I try to restore a backup made in CWM, it says md5sum mismatch (I haven't tried some md5sum generators/fixers yet).
When I try to restore a backup made with ONandroid, the md5sum is OK but nothing gets restored.
Help is extremely appreciated. Thank you.
Which version of Advance Stock Kernel you tried? Backup/restore in ics11 works great for me. Only problem I found is that Nandroid from ics4 can't be restore using ics5-11. This is there problem in ics4 or lower because md5 is still broken. It was fixed since ics5
Sent from my LT26i using xda premium
Thanks for the reply.
Well, all this time I have been avoiding to do a factory reset - come on, I don't have a valid backup so I wouldn't dare wipe my phone.
From purchase to current state, I believe these are the steps I have taken.
Purchased
Updated (using PCC) to stock ICS 4.0.4 (HK version)
Unlocked bootloader using official generated Sony code
Flashed Advanced Stock ICS kernel (whatever the version was at that time)
Flashed MooDeD 90.5 Rom
Flashed XSX Kernel
Updated XSX Kernel
Flashed KASSpeed Kernel
Flashed KA10.2 Rom with KASSpeed Kernel v3
Throughout this entire time, ever since when I first flashed a custom kernel, the backup/restore function has never worked properly.
Is there anyway to fix this problem without full wipe? Or is there a way to make sure the validity of my backups (so I can full wipe and then restore my backup)?
Thanks for any help.
I've heard that backup/restore function in XSX Kernel didn't work properly. The creator of XSX posted the question here. Not sure whether he has got the solution and fixed the problem in the latest version.
I suggest you flash ics11.elf (the latest version of Advance Stock Kernel) and then try creating Nandroid backup. After that, reboot into recovery again and restore the backup (still with ics11). Let me/us know if it works or not. I suggest ics11 because I have used it to Nandroid backup/restore many times (more than 10 times) and I have never run into any issue with it.
try to flash the recovery on the stock kernel from Bin4ry:
http://forum.xda-developers.com/showthread.php?t=1596285
else i could suggest, is that you format your sd card.
Thanks for all your replies.
Yea - I saw the creator of XSX Kernel post the question too.
But here's the thing - I don't really understand how Backup/Restore in CWM works, but my bet was that it has nothing to do with the data partition. With me keep on flashing new kernels and new ROMs, I would think that both the boot and system partitions have been formatted/wiped and then flashed. Does that mean the Backup/Restore function has to do with something in the data or other partitions?
And by the way, is it a universal problem that everyone has with the error mounting /cache in recovery?
Anyway - I just flashed ics11.zip through CWM, did a reboot and then did a backup - md5sum mismatch when restoring.
Does it make a difference if I flash it through CWM or fastboot?
Update: None works. But it's late here and there are many more things I can try.
So far for me, Advanced Stock ICS Kernel 11 as well as Bin4ry Recovery resulted with md5sum mismatch when restoring.
Will meddle more with ONandroid when I get the time to - because when I backup with ONandroid, at least md5sum are all right.
Thank you all for now.
And Realfelix, thanks for your suggestion - I will try the recovery later maybe... and you do mean external memory when you say SD card, right?
Data partition is also backed up and (normal) restored. If you take a look at /sdcard/clockworkmod/backup/..., you'll see data.ext4.tar. That's the backup of data partition.
About ics11.elf vs ics11.zip, as far as I know, elf contains ramdisk, zImage and rpm.bin while zip contains only zImage. If you flash zip, only zImage is updated. Something I don't know is whether CWM recovery is in ramdisk or zImage.
Sent from my LT26i using xda premium
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
I know that cwm versions 6.0+ have a new method of backing up files. After restoring an older GB rom that has an older version of cwm, I can no longer restore these new cwm backups. I'm not aware of a cwm 6.0+ existing for GB. I tried installing siyah's GB kernel, but it only had cwm 5.5. Does a cwm version 6.0+ exist for GB roms?
Our kernels come with cwm built into them. And since gingerbread kernels aren't being developed anymore I'd say no. Good luck, happy flashing.
Sent from my SGH-I777 using Tapatalk 2
I may be wrong, but as far as I am aware, CWM6 is only for JellyBean Builds. As Phalanx said, there is no V6 for GB.
Xander_25 said:
I may be wrong, but as far as I am aware, CWM6 is only for JellyBean Builds. As Phalanx said, there is no V6 for GB.
Click to expand...
Click to collapse
CWM 6 is available on ICS. But i didn't think it existed for GB. Oh well, guess i'll have to start over.
To restore em just flash CM9 or 10 first and there ya go. CWM 6 is ready to restore your backups.
Sent from my SGH-I777 using Tapatalk 2
Slavestate said:
To restore em just flash CM9 or 10 first and there ya go. CWM 6 is ready to restore your backups.
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Well I feel stupid..I'm not sure why I didn't think of that. I'm about to just reinstall shostock2 and then voila, cwm 6. Thank you sir!
Also, if you try to restore a cwm 6.0 backup from an earlier version of cwm, it will restore only the boot.bin, and fail on the rest of the backup. However, the phone will now have the cwm 6.0 kernel, and the next time you restore, it will work.
Here is what I do when I am wanting to restore back/forward from CWM5 saved nandroid to/from CWM6 saved nandroid.
RESTORING A CWM5 NANDROID:
1. If I am on CM Version with CWM6 and want to go back to a nandroid backup made while on CWM5 I flash this CWM5 based siyah kernel http://db.tt/owgZanij
2.Once I have installed the CWM5 Kernel I hold down volume+/- and power to restart recovery.
3. I choose the nandroid backup CWM5 based and restore it.
RESTORING A CWM6 NANDROID of Cyanogenmod firmware:
1. I flash this Siyah CWM6 Kernel http://db.tt/iHax4mvQ
2. Once I have installed the CWM6 Kernel I hold the Volume +/- and Power button until I am rebooted to recovery again
3.I choose the CWM6 (CM10 in my case) NANDROID BACKUP and restore
As long as I am on the correct version of CWM my nandroid backup will work properly. Even if the nandroid backup has a different kernel than the siyah kernel you just flashed. The nandroid restore will overwrite the kernel back to the correct kernel from the rom you were originally on.
I also use this method of flashing these kernels if I want to install a new rom based on Sammy builds or based on ASOP/CYANOGENMOD ROMs. So depending on which way I am flashing I prepare for it without having to flash a complete rom. Since flashing a kernel is much quicker. Just need to remember which way you are going and which kernel I want to get it done.
Sent from My SGH-I777 Running Red Reaper Rom
RockRatt said:
Here is what I do when I am wanting to restore back/forward from CWM5 saved nandroid to/from CWM6 saved nandroid.
RESTORING A CWM5 NANDROID:
Click to expand...
Click to collapse
Solid write uP Rock, thanks for helping him!! Good to have you around......
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Nyssa1104 said:
Question since you state you using philz kernel why dont you use his CWM to backup and restore your backups instead of Odin mobile.
iT comes as part of the kernel http://forum.xda-developers.com/showthread.php?t=1877270
Click to expand...
Click to collapse
Thanks for your reply.
I only use mobile odin to flash official firmware so its a fresh start before installing a rom.
I've tried to restore from philz before but had the same problem. Normally use Dorimanx.
I myself had no probles with Mobile odin pro of CWM in Philz kernals and since Philz kernal this tends to be the normal backup or flashing aid for me. Since I have a Micro SD card install back up and roms are place on this..
by the way Im using SuperSUPro and not Superuser for root.
symondo12 said:
Hi Everyone,
Every time I restore a sammy JB install from recovery it always hangs on the bootscreen and never boots up. I was wondering if anyone has had this issue before or its something that I'm doing wrong
When restoring I always run an odin flash using mobile odin and root it with philz. I then delete all the system folders, wipe cache etc and restore.
If i used a different kernel to backup the install i will install that kernel before restoring.
I've tried several roms such as neatrom, Alliance and Wanam but get the same result. CM/AOSP roms restore ok.
If anyone has any suggestions it would be much appreciated.
Many thanks
Click to expand...
Click to collapse
I have a possible solution just flash entire original rom(the one you are going to restore) once, then restore your nandroid backup, clear cache/dalvik, reboot. I have a hunch on the problem that it might be caused by another roms /preload partition data (our nandroid backup won't usually backup it by default so it actually never gets wiped or overwritten)
Edit :I forgot to mention a factory reset at the beginning.
Sent from my GT-I9100 using xda app-developers app
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 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.