I'd have put this question and bug report directly to the [PhilZ-cwm6][i9100/P] Stock Kernel+CWM6+Root+exFAT+NTFS-MS3 thread but my post count doesn't allow me to post in there yet, need 10 posts ....
Samsung Galaxy S2 - GT-I9100
Updated quickly from ICS to JB to KK over the last week or so.
CWM
I went for Philz Touch philz_touch_6.07.1-i9100.zip that gave me CWM 6.0.4.9 and the fancy purple GUI stayed for one boot but then reverted to a simpler layout though retaining the touch functions.
I also tried another Philz version which didn't boot at all.
And another philz_touch_6.43.4-i9100.zip which worked except that WiFi wouldn't switch on. That also gave the purple GUI for one boot only before reverting. Curiously this one gave me CWM 6.0.4.8
So I've gone back to the philz_touch_6.07.1-i9100.zip for now as that's the best I've found so far that works without problems for me.
My Questions are:
1. Is this normal?
2. Is there some hidden intelligence at work here changing the versions?
3. Is the CWM updating itself as I install it??
The root of your issue is this - any recovery flashed independently of the kernel on the I9100 will only persist until the next reboot. Why ? Because recovery is 'baked' into the kernel on this device & is not in its own separate partition like many other phones (where you can flash whatever recovery you want with whatever kernel you want; on the I9500/I9505 as an example). Once you reboot, your recovery will revert to that included with whatever kernel you're running.
If you want to use a particular CWM version permanently, you need to run a kernel that has it.
Excellent answer.
Baked in eh?
I'm beginning to understand but it's odd that the CWM 6.0.4.9 and the CWM 6.0.4.8 DID persist but the purple GUI front end didn't.
Either way, the CWM 6.0.4.9 I've got in there now is working happily with my ParanoidAndroid ROM and that's the main thing isn't it.
Related
After having overheating issues (presumably voltage related?) with the official XWLP7 XEU (UK) ROM I decided to try my luck on a custom slim version.
Phone was successfully CF rooted before Dynamic v1.4 ★[ICS][Slim][Performance & Battery life][25April] was installed.
Custom ROM is running fine, however when I was playing around in the recovery menu the phone screen randomly displayed artifacts after selecting "reboot now". So I was wondering if it's possible to downgrade clockworkmod to the generic public release version - namely this puppy?
Thanks for reading my first post lol
I suspect CWM went retarded during the CF to Dynamic v1.4 transition - can someone provide some insight here? I've deduced kernels were changed, but was unaware of the implications to the recovery console in doing so
Functionality only becomes an issue in the recovery menu before OS loads otherwise everything is tight as a drum
Recovery is linked to the kernel. Obviously your kernel changed when you flashed that ROM. If you want to change your CWM recovery, flash a different kernel which has the version you want.
Ok, I've gone ahead and been an inpatient muppet installing ROM manager from Google play and flashed the respective recovery console. Will this cause conflicts? It seems the original one still stands using the the three button combo when powering up where as the generic recovery console I just put on has to be executed via OS.
no issues keeping both if working perfectly....
Normaly there is a mismatch seen between ROM manager and other custom recoveries..
if you are rebooting from ROM manager to CWM if the update package flashes smoothly and flashed CWM is appears then no issue you can use it. i think its only flashes temporerly,
when you use the 3 combo you can get the recovery which is incorporated with your kernel....we only need a working CWM to flash zips, and backup,
I recall reading somewhere that installing the CWM recovery rom included with Rom Manager (https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager) on a YP-G70 (USA 5.0) results in 'bad things'
My questions:
Is this true? Will it make a mess of my device that's a headache to fix?
What is it about that version of CWM that causes the problems?
1. I've seen people have problems when the flashed CWM intened for another device.
2. Every CWM seems to be custom made so another CWM won't work on our players
There is no "official" CWM for player 4.0, 5.0... ROM Manager is useless (unless you want to use it to easily boot in recovery once you have CWM). You'll need to flash a custom kernel in the dev section that includes a modified version of CWM to work with our players.
Thanks Chris. I'd already flashed Entropy's CWM release so no problems there. I was just hoping Rom Manager's might work, so I could do some that stuff without rebooting (at least until after I've told it what I want to do. Non-touch interfaces are sooo low class, don't you know?)
I've tried multiple tutorials to root my phone but whenever I flash the CWM and restart my phone in recovery mode I still get the default Android recovery screen... What should I do?
CWM flashed on its own (I.E not 'baked' into a kernel) always only persists until the next reboot.
It's designed to allow you to flash whatever rom/kernel you want which will overwrite the temporary CWM version you flashed with the one baked into the kernel of the rom you flash/kernel you flash on its own.
If you want permanent CWM from the getgo, flash a kernel with CWM baked into it. Or use another root method. I'm not sure about either of those things (nor will most people on here be), because very few people here have this model.
I found this thread by searching; if you're having problems with a specific root method, I suggest you ask in those threads so you get 'accurate' help from people who actually have the same phone as you.
ibud said:
I've tried multiple tutorials to root my phone but whenever I flash the CWM and restart my phone in recovery mode I still get the default Android recovery screen... What should I do?
Click to expand...
Click to collapse
maybe get the dorimanx v8.34 kernel ? root and kernel at the same time, its good, quite perfect just. dorimanx v9.xx is still in test and someone told me its bugged, so i would flash the v8.34
First the specs. Samsung Galaxy s2 GT-9100 running Android 4.1.2 Build XWLSH Kernal 3.0.31-889555
Need a touch of help here. Finally had the nerve to root the GS2 on the weekend and clean out all the crud not required... so far so good
Had no success in attempts to install CWM Recovery through ROM Manager (Recovery setup > ClockworkMod Recovery > Galaxy S2 i9100 > "does not have an officially supported...."). Also found the Recovery builds on the official site but no guides whatsoever as to how to install... oh so helpful
Finally came across a guide at galaxys2root[dot]com on installing recovery from download mode using Odin. Ran through the process and ended up stuck at boot with no way of proceeding. After a panic session, was able to recover from back-up (thank god I backed up the ROM and all data before attempting to install CWM recovery). Now I'm right back where I started with no idea how to go replacing the stock recovery.
Can someone please shine some light on the situation? At a complete loss as to how to get the CWM Recovery on the phone without bricking it.
Cheers in advance
1) Don't use Rom Manager. At all. Uninstall it. It will break recovery & cause bootloop eventually if you continue to use it.
2) Thread stickied near the top of Q&A has all the info you need. Essentially, any CWM you flash independent of the kernel will only persist until the next reboot. Reason being recovery is baked into the kernel on the S2 & isn't a separate partition like other phones. So you flash a custom kernel, you end up with rooted phone + permanent CWM.
MistahBungle said:
1) Don't use Rom Manager. At all. Uninstall it. It will break recovery & cause bootloop eventually if you continue to use it.
2) Thread stickied near the top of Q&A has all the info you need. Essentially, any CWM you flash independent of the kernel will only persist until the next reboot. Reason being recovery is baked into the kernel on the S2 & isn't a separate partition like other phones. So you flash a custom kernel, you end up with rooted phone + permanent CWM.
Click to expand...
Click to collapse
A huge thankyou for pointing me in the right direction. I had since the original post found Mobile Odin (invested in the pro version) and installed the CWM Recovery from the their site... only for it to revert back to stock recover screen At least now I know why.
After much hunting around - I notice the stickied posts don't make it easy to find the correct kernel for for the AU i9100 - I found the PhilZ cmw6 kernel build.... used Mobile Odin to flash and all is now rosy.
Now question.... I was under the impression that ROM Manager was required as an install with CWM. I use Online Nandroid Backup to create full ROM/Data backups and trying out Nandroid Manager for selective recovery.... is that all I need then now that CWM is successfully installed in recovery?
Cheers again
Can't speak to those products as I've never used them, but Rom Manager & the S2 is a big no no. Doing nandroid backups, which is essentially a 'snapshot' of your phone at the time you make it, by simply booting into CWRecovery & also backing up apps/app settings with Titanium has always done the job for me.
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..