I installed CWM v5.5.0.4, CF-v.15 then install Hyper rom v8 on my friend's S3, everything just fine until yesterday he tried to reroot it himself due to wifi problem (as he said).
Now the phone cannot boot and cannot enter download mode with the volume down + home + power combo, or any other combos (it stucks on S3 logo for a while then reboot to cwm), in cwm I can't use volume keys to navigate, it still reboot when I press power button ("reboot system now" selected by default)
Please help, thanks
Flash TWRP and not CWM as CWM is very outdated. Then flash a custom ROM and Gapps from TWRP.
audit13 said:
Flash TWRP and not CWM as CWM is very outdated. Then flash a custom ROM and Gapps from TWRP.
Click to expand...
Click to collapse
Not true. Cwmr is not built for the roms that the phone was never designed to run. Cwmr is still the most stable recovery for the s3 provided that you don't go higher than 4.3, which is where the stock updates ended.
Beamed in by telepathy.
Neither CWM or TWRP, as far as I know, depend on the stock ROM installed on the phone, they both depend on the model of the phone. I stopped using CWM a long time ago and have not run into any issues. I like TWRP because it has many more options.
If you only want to flash stock-based custom ROMs, CWM should be fine but, from what I have seen in custom ROM threads, most newer (KK and higher) custom ROMs need TWRP.
The OP referenced Hyper rom v8 (https://forum.xda-developers.com/galaxy-s3/development/rom-hyper-rom-t3329988) in the original post and this ROM's installation video used TWRP rather than CWM.
My post was not meant to be disrespectful to CWM in any way as the CWM team has performed great work over the years.
audit13 said:
Neither CWM or TWRP, as far as I know, depend on the stock ROM installed on the phone, they both depend on the model of the phone. I stopped using CWM a long time ago and have not run into any issues. I like TWRP because it has many more options.
If you only want to flash stock-based custom ROMs, CWM should be fine but, from what I have seen in custom ROM threads, most newer (KK and higher) custom ROMs need TWRP.
The OP referenced Hyper rom v8 (https://forum.xda-developers.com/galaxy-s3/development/rom-hyper-rom-t3329988) in the original post and this ROM's installation video used TWRP rather than CWM.
My post was not meant to be disrespectful to CWM in any way as the CWM team has performed great work over the years.
Click to expand...
Click to collapse
No offence taken. I'm just being as factual as possible. Twrp is definitely needed for higher than 4.3.
Beamed in by telepathy.
shivadow said:
No offence taken. I'm just being as factual as possible. Twrp is definitely needed for higher than 4.3.
Beamed in by telepathy.
Click to expand...
Click to collapse
Thank you. Now, back to the problem at hand:good:
Related
I'm new to this forum and find the i717 a wee bit more complicated than my old phone. (a Galaxy S 4g.)
I've managed to get CWM touch 5.5.0.4 on the phone and have successfully flashed the deodexed stock jelly bean rom. However when I try to flash any of the "quincy.att" based rom, CWM gives me an error, which I imagine means that I need a more recent CWM. Before I flashed stock jelly bean, I was able to get the 6.0.3.6 quincy.att CWM on the phone using the terminal but when I tried using it, it did not see the external sdcard and I could not get there to flash any rom. I tried using ODIN to flash CWM 5.8.4.3 but ODIN just sat there and nothing got loaded onto the phone at all.
So it is kind of a chicken and egg situation here. What is the minimum version of CWM I need to flash any of the quincy.att roms and how do I get it on there and working? Or am I supposed to use TWRP? I haven't tried that. I remember it from the 4g and it was a pain to use on that phone. I have tried to flash the 10.1 quincy.att plain Cyanogen and the chameleon rom and I just get error messages from CWM,
Just use twrp.....your probably getting error 7 ...install twrp
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
TWRP is piece of cake here. you will never look back
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
longhairdaddy said:
I'm having issues getting cwm 6.0.4.4 to work.... 6.0.4.3 touch or regular work just fine, but the few times I've tried flashing 6.0.4.4 in order to flash the latest Kit Kat I get stuck in a bootloop. The only way to fix it is to remove my battery, flash twrp with Odin, wipe everything, flash cwm (earlier than 6.0.4.4) and reflash a ROM. I've tried: updating through ROM manager, flashing 6.0.4.4 in recovery, converting a zip to a tar (thinking maybe the file was corrupted). I'm beginning to think my phone just doesn't like Kit Kat.... Now I'm back on Padawan because it's like literally the most stable ROM for my phone. Any ideas?
Click to expand...
Click to collapse
If 6.0.4.3 touch works "fine", why don't you just use that?
veningTrMarchal
tube517 said:
If 6.0.4.3 touch works "fine", why don't you just use that?
Click to expand...
Click to collapse
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
longhairdaddy said:
cwm 6.0.4.4 is recommended for the Unofficial AOKP 4.4.2 flash and I couldn't get it to install with 6.0.4.3. It installs with 6.0.4.4 but ends up in a bootloop.
Click to expand...
Click to collapse
Try CM11 for KitKat. It's very stable.
tube517 said:
Try CM11 for KitKat. It's very stable.
Click to expand...
Click to collapse
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
longhairdaddy said:
I actually did try CM11 Kit Kat and liked it but about ten minutes after everything boots up it will force close and go into a boot loop. I've tried the various gapps packages, installing without gapps then flashing them, wiping dalvic before and after and in between, I dunno.
4.3 ROMs run like a diesel, it just seems I can't get 4.4s to be stable. I just now flashed the Beanstalk 4.4.2 along with the updated gapps and can't get past the beanstalk animation. Sat there for an hour.
I appreciate the input though.
Click to expand...
Click to collapse
I had the same issues with 4.4 kitkat roms. Did you format system in CWM when wiping? This solved my bootloop issues. Also, make sure you have a clean download of the ROM. Flash the ROM twice back to back when flashing a new kitkat rom
Hi, I'm a new to rooting, but long time jailbreaker, and man this is way harder than I thought!
I think I'm on the right track, I've uploaded Rom (Super Nexus 3.0 i9100 ect), CWM-SuperSU v0.97 and Google apps (gapps-jb-20130813 ect)
But, I've unfortunately had a couple of failed attempts, originally coming from 4.1.2, I'm now back to 'stock' 4.0.3 and can't update, so I'm going to try again.
So I wanted to know, using Odin, is 6.0.2.9 the latest version of ClockwordMod and/or for the Galaxy S II (if it matters?) I've already got it on there, but I've also got a Siyah on there too, so just want to do another flash to a CWM.
And yes, no quarms about completely wiping the phone, I've backed up all the music, pics, call logs, ect, so just want to learn how to root to the latest version of android, and this version looks great.
Mm it's really not harder than you thought. You're over complicating things.
2 current options :
Have you flashed & are currently running siyah? If so, then boot into recovery and flash supernexus & gapps. Done.
Not currently running siyah? Flash siyah via Odin in download mode. Reboot then into recovery and flash your rom and gapps. Simple. Rooted and new rom.
As far as using CWM on its own (ie just flashing the recovery) it'll only be temporary. Every reboot it will reset to stock recovery. Hence why you need to flash siyah to keep the permanent recovery & be able to flash a new rom.
Sent from a galaxy far, far away
Hopper8 said:
Mm it's really not harder than you thought. You're over complicating things.
2 current options :
Have you flashed & are currently running siyah? If so, then boot into recovery and flash supernexus & gapps. Done.
Not currently running siyah? Flash siyah via Odin in download mode. Reboot then into recovery and flash your rom and gapps. Simple. Rooted and new rom.
As far as using CWM on its own (ie just flashing the recovery) it'll only be temporary. Every reboot it will reset to stock recovery. Hence why you need to flash siyah to keep the permanent recovery & be able to flash a new rom.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Thanks Hopper,
I decided to use CWM 6.0.2.9 (so now there are three kernals, 2 CWMs and 1 Siyah, wish I knew how to clear them out).
First time I tried to use Super Nexus 3.0, it looked ok, but wouldn't reboot, but then I just re-installed eveything again (both times CWM), and now I've rebooted twice no problems? I think I read somewhere that it had to be done twice, I have no idea why that would be.
Oh yeah, but now I need to get Swype back on there, forgot it was a Samsung exclusive, I'll see how I go from the Google Play, but I'm guessing I could get a custom .apk from the internet anyway.
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..
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Al-Dazzlez said:
Hi all !
ive searched thoroughly for a few days and have not found an answer to my question so I am making a new thread.
I have been wondering if it is possible to install a ROM without getting the recovery changed. By this I mean, can you install a ROM without going from TWRP to CWM or vice versa? it seems stupid, yes I know, but in all of my experience, and for the last 50+ ROMs, upon flash, the Recovery changes with the kernel, so I wanted to know if anyone can answer me (in regard to S2) and yes I do know that some RoMs only work with a certain version of CWM or above etc but I was curious.
Thanks in advance for any help
~daz
Click to expand...
Click to collapse
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
warrior1208 said:
Actually, upon flashing the kernel, the recovery would change. But the change depends. If you switch from an older Omni ROM to an updated Omni ROM version, your recovery doesn't get changed since Omni ROM uses TWRP. Similarly, if you use a Cyanogenmod ROM and update to a newer version of Cyanogemod ROM, the recovery doesn't change; remains same- ClockWorkMOD Recovery.(CWM)
BUT, if you want to flash Omni ROM over Cyanogenmod, then by default, CWM Recovery would get changed to TWRP. So, if you want to have the same recovery as you had with the earlier kernel(due to earlier ROM), you have to flash that kernel.img again after every new ROM flash, and then you can reboot to recovery.
Click to expand...
Click to collapse
Well that clears up a lot othings so thanks for the reply
Hi i want just install cwm on my s3, and be with stock firmware , i dont wanna install Custom Roms or same like that, just be with CWM and stock rom. so still root required when CWM INSTALLED FROM ODIN? SORRY FOR DUMP QUESTION
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
audit13 said:
No need to root before installing a custom recovery with Odin.
I recommend TWRP over CWM as CWM has not been updated for a very long time.
Click to expand...
Click to collapse
Neither has the s3 and twrp is known for borking your nand, so much so that they have a section on it on twrp website.
My opinion, use the last official cwmr for your device.
@shivadow, I didn't know that twrp affected the s3. The last version I recall using on the last few sgh-i747m phones I had was 2.87.
Do you have a link to the twrp section regarding this issue? Might be good to have it stickied?
Thank you.
Twrp buggers all devices in the end, not just the s3. It's like there's a bug that can't be solved.
Quick Google found this https://github.com/TeamWin/Team-Win-Recovery-Project/issues/773