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?)
Related
Hi, I have the I9100 from two weeks, and I had noticed that samsung phone architecture is slightly different from other android phones.
Before I9100, I had an HTC MAGIC, HTC HERO, NEXUS ONE, ZTE BLADE.. all of these phones are managed and structured in the same way: Bootloader, Recovery, and ROM.
When I get the root, I can flash the recovery, and then I'm sure that if I flash a buggy rom (with a buggy kernel) I can always start the recovery and flash another one.
In samsung is different and I can't find a technical guide on how this phone works.
It seems that the recovery is INSIDE the kernel. Then if I flash a buggy kernel I loose the recovery!
Another strange thing... why do I need to use odin? And why some of the roms (also here in xda) must be installed trough it and others trough recovery?
Why some people have flashed a buggy kernel and can't flash trough odin?
What's the download mode is used for?
Is download mode is a state of the phone that is loaded before and without the kernel?
Why I can't use rom manager (installed trough the market) to flash my recovery and I need to use the CWM that is hardcoded inside the kernel?
I need some answers because I don't wanna follow the guide without knowing what I am do.
Can someone help me?
... no one answered me yet?
Are my questions, silly questions?
I looked into the guides I found here and I didn't found any answer for me..
Well I Don't own a s2 but samsung androids are different
There is no separate recovery partition so it needs to be in the kernel/rom
So its obvious an other method is needed to flash roms if something bad happens with the current rom/kernel so odin and download mode exist
Very Interesting... but.. is download mode loaded before (ad instead) kernel?
If this it is a restore operation should be loaded always.. also from a complete wipe of everything right?
But.. I read somewhere that some buggy kernel does not allow odin to find the phone..
Then.. If I lose the recovery and odin does not recognize my phone... Am I in a 'deadlock' situation?
All I've found about temporary cwm installed on stock recoveries are that they caused a lot of problems with the ICS superbricks issue, but nothing about if they were safe or not on non-ICS, for example GB.
I was planning to get CWM4 (I don't want touch CWM if possible) for the I9100 (from the CWM site, http://clockworkmod.com/rommanager , recovery-clockwork-4.0.1.5-galaxys2.zip), and install this into the stock recovery of my Zergrush-rooted GB 2.3.5 rom to get temporary CWM, and use nandroid to create security saves or to recover them back.
(The link I comment is the temporary CWM, right? )
If there's no superbrick involved, what is the risk of installing and using that temporary CWM4 version on my GB rom everytime I wanna use nandroid? Any at all?
Thank you a lot in advance!
Use your other thread don't make duplicates.
Is ROM Manager fully functional on this phone now? Just wondered if all of the options: CWM, Updates, Fix permissions, etc. are all working for folks - with no issues. Will it update to CWM Touch?
Thanks for any input.
im running touch flawless but i cant seem to download and go straight to recovery i have to manual but cwm is working fine
I posted a lengthy question earlier on this....for me, ROM Manager 6.0.1.5 (non touch) insatalls and seems to work fine, however when I try to do a backup of my current ROM it does not fully do it.
Uninstalling ROM Manager and flashing via fastboot the posted CWM recovery, I was able to do a successful Nandroid.
Just sucks not being able to use ROM Manager to backup your current ROM...for me at least.
At the Rom Manager Website I see both versions for the DNA:
http://www.clockworkmod.com/rommanager
It says the version number (for both) should be 6.0.1.5. Currently running 6.0.1.2 on my phone.
But on my phone, if I click on Flash ClockworkMod Recovery, it says Unsupported Device. Hmmmmm
Any update on this?
Is ROM Manager now supporting the DNA?
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.
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..