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.
Related
Hey everyone,
First of all, i apologize if any of what i'm asking here is stuff that has been covered before. I have been searching myself for answers for the last several days and have found plenty of good info, but i am new to android and i think i need to ask some question to help get a base level understanding of what i need to do. I am a bit nervous about bricking my phone so i maybe haven't been as adventurous trying to get everything running as god intended.
Firstly, i have used and understand Odin, using it to flash roms and such. I have rooted the phone and installed ROM Manager and clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e and i cannot do the update.zip, I get signature verification failed. Now i KNOW this is cause of the android recovery 3e, and i have found this issue has been encountered plenty before, but my confusion is in some of the solutions i have found. Mainly the terminology and how the steps directly apply to the phone. For example, I found on another forum thread :
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is. Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
What i really need i guess is for someone to break it down for me and either explain the steps or give me a detailed step by step on how to get clockworkmod recovery working so i can proceed with the cyanogen mod running on phone (not enjoying touchwiz at all).
Again, sorry if i am giving anyone spasms at my noobish-ness, but i have been searching for my answers for a day or two now and i haven't been able to find anything that really tells me what i need to know.
Phone : GT-I9100M
Android : 2.3.3
Kernal : 2.6.35.7-I9100XWKDD-CL
Build : GINGERBREAD.UGKG2
Thanks
riccochet said:
Hey everyone,
clockworkmod 4.0.1.5 on the phone, but when i boot into recovery mode, it is still on the android recovery 3e
That means you have not installed it flash CWM and \Root from here .
Root + CWM .
http://forum.xda-developers.com/showthread.php?t=1103399
Beware of following instructions from a separate rom to the one you are flashing .
1- Copy the Zimage from your rooted kernel and paste it to SD card of your phone.
2- Flash the Stock kernel via Odin to get rid of Yellow triangle.
3- Flash the Zip file (Zimage) via CWM which you've already pasted in Step 1.
i don't really understand what the zimage is.
ZImage is the kernel .
Why do i need it, what IS it frankly? Where do i get it or a stock kernel for my phone. Does versioning matter much? i read that for the most part the kernels are almost identical to each other, and the fact all i really need is for the android recovery mode to be 2e or whatever it is (so it will not do the signature check on the update.zip file), that i don't really need to pay much attention to the actual kernel version.
You are confusing yourself .
Flash correct CWM from above link .
Choose the custom rom and follow the instructions posted for that rom .
CyanogenMod as the man says
Warning : Not for new users, flash this build only if you know what you are doing !!!
#Followed by his install instructions ~~~
jje
Click to expand...
Click to collapse
Thanks for the reply. I have been doing more reading and i think i am understanding the rooting process a bit better.
I looked at the link you posted (thanks for that, i saw the forum post for the i9000 but i never could find the i9100 post for some reason) and i DO have another question after reading through a good chunk of the posts on it.
There is no CF Root for my kernel, but the reply that was made to someone else with my kernel version was :
"Flash the Stock 2.3.4 ROM (XXKG5, XXKG6 or XXKG7) and root with CF-Root-XXKG6."
I understand that process and how it works but i thought you were only supposed to flash roms based on your firmware version? My KDD kernel version is running on 2.3.3
Will this cause any issues if i flash the stock 2.3.4 ROM?
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Thanks Veyka.
I think i'm ok with the CM7 install process. I am probably going to wait until i really feel like i understand the whole process from front to back before i start messing with that though.
I can't get to that point yet however since i haven't been able to get CWM recovery working yet. I have the Android Recovery 3e, which will not install from zip files that aren't digitally signed.
So i'm trying to get CF Root installed and working, however, as mentioned in my previous post there is no CF Root for my kernel. I would like it clarified if it is ok for me to flash to a 2.3.4 stock ROM (i'm running 2.3.3) and then use a CF root for a the new ROM.
I was under the impression that this was not a good idea.
If i should not be doing this, is there a recommended way to upgrade my firmware to 2.3.4 so i can use a newer CF Root?
Thanks
Pick a new stock rom, I would go for kg6, flash it via odin.
Then flash the kg6 CF root kernel via odin and you will have cwm recovery.
Don't put the pit into odin and don't tick repartition or update bootloader.
There is a good thread with all the info you need on flashing stock roms with odin and a list of all avaliable roms.
Sent from my GT-I9100 using XDA Premium App
Thanks for all the help. I was able to make sense of the process (which is actually quite simple, just needed to put it all together in my head to make sense) and get everything done.
Appreciate all the help!
veyka said:
Download cm7 zip for the newest nightly.
Copy it to internal sd card.
Flash any cf root kernel
Boot into recovery
Wipe data and cache, you will lose all your data on your phone, so backup sms (I recommend sms backup +), also you will lose App data so you might want to back that up first using something like titanium backup.
Wipe dalvik cache (under advanced)
Chose install zip from sd card
Select the cm7 zip
Reboot
If you get stuck at the boot screen go back into recovery and flash the zip again
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
NABNAP said:
Hi,
I have rooted my phone using the quick root guide found here and therefore I have my stock kernel back w/ root. Do I need to install a cf root kernel?
Also, when the new ROM gets flashed how does one recover the apps and data lost?
Click to expand...
Click to collapse
Use Titanium Backup PRO for your app. You can backup all of them then restore on any rom.
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
NABNAP said:
Is there anything that Titanium Backup doesn't back up for which I need to use another application?
Thanks.
Click to expand...
Click to collapse
sms.. use another app to backup your sms.. for example sms backup as mentioned before..
Hi All
Please let me explain in detail:
1. I had original ICS and flashed CF-Root with ODIN
2. Flashed new JB-Polland with ODIN
3. Lost root access and CF apps
4. Re-flashed CF-Root, CF apps and root access granted
5. Opening CWM i get the following msg: "This version of CWM should be used with CF-CWM v1.1" Now from reading other posts, i think this error is due to CF-Root not supporting JB.
Therefore what are my options?
1. Can I flash a new root over CF-Root, that supports JB.
2. Do I do the triangle away and try to clear CF-Root
3. Any other suggestions?
Thanks in advance guys.
Whenever I'm flashing a ROM, I flash over the previous one.
I installed CF-Root, flashed MIUI, didn't like it so flashed CM10, didn't like it so flashed to stock again then reset my flash count to 0.
Or use it as is. Everyone who uses CF-Root with JB gets that message. You can still perform backups, updates and ZIP installs through CWM recovery.
Thanks Sleepycat, I didn't realise you could keep using it. Part of the message says some features have been disabled.
Running backup in recovery mode now and seems to be going sweet.
Thanks Guys
its just the app that's incompatible, not CWM itself.
Sent from my GT-I9300 using Tapatalk 2
Depending on what you are flashing, what is on the phone will be "overwritten". For example if you flash a kernel you will replace just the kernel, if you are flashing a full rom, everything that the rom contains will overwrite its equivalent in the phone (which is why you needed to reflash the root).
If you want to ensure you can get back to original state you needed to have done a nandroid backup at the beginning from which to restore later.
Hope this helps
Sent from my GT-I9300 using xda app-developers app
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
Is there any CWM.zip for the galaxy s3 ??
I want to keep my stock recovery and use CWM abilities like backup
Can any one find a similar thing ??:fingers-crossed:
I mean that I want it to be like my galaxy mini GT-S5570I
I had a CWM recovery . zip
If I want to use it I go to my stock recovery and select " install update from sdcard" and choose the CWM recovery . That make me boot into CWM recovery mod
yousefageaz said:
I mean that I want it to be like my galaxy mini GT-S5570I
I had a CWM recovery . zip
If I want to use it I go to my stock recovery and select " install update from sdcard" and choose the CWM recovery . That make me boot into CWM recovery mod
Click to expand...
Click to collapse
Stock recovery DOES NOT include flashing through zips so even if you in fact can flash stock recovery through CWM you CAN NOT flash CWM through stock one.
And to be honest I can't see any reason why you'd like to do so.
yousefageaz said:
Is there any CWM.zip for the galaxy s3 ??
I want to keep my stock recovery and use CWM abilities like backup
Can any one find a similar thing ??:fingers-crossed:
Click to expand...
Click to collapse
i don't think that is possible! how could you enter a custom recovery through a stock ones?!
Its called fake flash and was invented by koushik Dutta and Paul O'Brien. I used it on my HTC desire for a while. You essentially flashed it into memory and was gone on a reboot. This method is pretty old hat now. Im not convinced anyone uses this anymore. It's certainly not available on the S3.
Actually earlier rooting methods of desire gave you a leaked engineering version of the recovery that had no signature verification. That's the only reason it was possible
Sent from my GT-I9300 using Tapatalk 4
you could try something similiar, for example mobile odin, there you can flash update.zips and keep your stock recovery. (but it has no other cwm abilities)
or you use syah or googy-max kernel, where you can boot from stweaks into 2nd rom utilities which is a full working cwm and disappeares after reboot. there you can keep as well your stock recovery (but you have to flash a custom kernel )
Can mskip's toolbox do backups?
rootSU said:
Can mskip's toolbox do backups?
Click to expand...
Click to collapse
Yes, full nandroid including efs, but needs a rooted phone -and it can provide root.
boomboomer said:
Yes, full nandroid including efs, but needs a rooted phone -and it can provide root.
Click to expand...
Click to collapse
Thanks. I guess that is the OP's solution then!
maybe anpother suggestion, which i often use could be the app online nandroid backup (its on the market), which can perform nandroid backups whithout going into recovery.
So there is no need of a custom recovery as long as you do not want to restore your backup.
and in combination with mobile odin you can flash update.zips. so the basic cwm abilities are covered (as long you have root)
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