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
Related
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.
SOLVED: Used TWRP instead of CWM to flash.
I flashed [ROM][KRT16M] AOSP Google Android KitKat 4.4 GEEB [Nov.2] using CWM and my ATT LG e970 has no cellular or wifi now.
stock rom rooted and unlocked using freegee
backed up stock 4.1.2 using cwm
I went into recovery and cleared system cache and dalvik cache.
flashed the rom
flashed the gapps
flashed SuperSU
rebooted and saw 4.4 launcher.
tried to turn on wifi and did not work.
no cellular signal from ATT either
I tried rebooting it and it displays the stylized android logo for greater than 2 minutes before the screen flashes and boots into the lock screen still without wifi or cellular.
help.
EDIT: I was digging trough the thread and it said that CWM6.0.3.8 had conflicts with SuperSU that led to no service
I restored my nandroid backup and my phone works fine.
What can I use to flash [ROM][KRT16M] AOSP Google Android KitKat 4.4 GEEB [Nov.2]? TWRP and how do I get it? Trough ROM Manager?
Use TWRP instead of CWM.
OMGMatrix said:
Use TWRP instead of CWM.
Click to expand...
Click to collapse
Yea, I guess CWM is my problem. I flashed Houstonn's stock PA and it had the same no cellular problem. I will try to install TWRP and flash instead.
Thanks.
EDIT: How do I install TWRP using fastboot? I installed CWM via ROM Manager and that was easy, but I can't find a working installer for TWRP. How do I install using fastboot command from my PC? Do I need to install anything?
EDIT: Installed TWRP
Well, I installed TWRP 2.6.3.0 using fastboot from my PC.
Did backup to external sd card.
Flashed PA and BanKs 4.3 Gapps.
Factoryreset/clearcache and cleared dalvik before and after every flash.
Now my camera works, unlike before when I flashed on CWM 6.0.3.8 where the camera would just crash. "About Phone" now shows the phone's IMEI.
Unfortunately I cannot get service. ATT is detected but it is stuck on registration.
There is a version of twrp that acardinal posted in his slim bean 4.3 thread (they're testing a 4.4 skim bean alpha), it's recommended for v4.4...not sure if the updated twrp is recommended or required. Might be worth looking into.
There is also an updated boot loader in Houstonn's 4.4 geeb thread...don't know if it'd be of help or not.
At minimum I'd bring up your issue in Houstonn's thread. Maybe one of those folks has seen your issue.
Have you tried flashing any radios?
Sent from my Optimus G using XDA Premium 4 mobile app
DraginMagik said:
There is a version of twrp that acardinal posted in his slim bean 4.3 thread (they're testing a 4.4 skim bean alpha), it's recommended for v4.4...not sure if the updated twrp is recommended or required. Might be worth looking into.
There is also an updated boot loader in Houstonn's 4.4 geeb thread...don't know if it'd be of help or not.
At minimum I'd bring up your issue in Houstonn's thread. Maybe one of those folks has seen your issue.
Have you tried flashing any radios?
Sent from my Optimus G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. This time, I used TWRP instead of CWM to flash and then I rebooted the phone a couple of times and it now works fine.
Guess it was just CWM causing issues with all my rom flashes.
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
basti_b24 said:
Hey folks,
I'm desperately trying to get a CustomRom working on my GP4.
I'm relatively new to the device, but not to CustomRom's, since I was using a Motorola Defy untill last summer, running CM7.2 and CM9, MIUI and a couple of others.
So here's my issue:
I flashed the Terrasilent Kernel in order to get CWM so I could flash the .zip's from there, as some weren't available for odin.
The kernel works fine, but as soon as I try to flash any CustomRom (I tried CM9, CM10.2, Hydrogen and the PACMAN Rom), I'm just getting infinite bootloops.
I also tried flashing with SD card removed, SD card back in....doesn't help. No matter whether it's done with odin or CWM.
Mostly I get stuck at the Samsung screen , the PACMAN insert coin or the Terrasilent phonebooth .
Does anyone have suggestions how I could make it work?
Cheers!
Click to expand...
Click to collapse
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
TheKryptonite said:
Did you wipe the data/cache? Also, I believe you're supposed to flash then ROM first, THEN you flash the kernel.
Click to expand...
Click to collapse
Forgot to mention that: I tried various ways: first wipe data/cache, then flash ROM; first flash ROM, then wipe cache; wipe cache, flash ROM, wipe again...
In order to get CWM recovery and being able to flash a zip I flashed the Kernel first. For CM9 I followed this http://forum.xda-developers.com/showthread.php?t=2213152
As I couldn't flash any of the pre-flash zip from stock, I thought it's necessary to flash a kernel including CWM first. It was done in the same way in some youtube tutorial I watched, where the guy already had the terrasilent kernel on his device.
For odin, I will check if it works with first flashin the ROM and afterwards the kernel.
Cheers for your fast reply!
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, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.