Have goodness Rom on my sch-i605. 2.5.0 TWRP. Want to update to CM11 Kit Kat.
Using Flashify I updated TWRP to 2.6.0.1. That was using the 2.6.3.3 img file for i605. I falshified again choosing the 2.6.3.3 img file. Said it worked and reboot now. I did and it is permanently stuck on Samsung Galaxy Note II.
Solution?
I had the same problem with aokp and newest twrp. I had to Odin back to stock, reroot, etc. Wish I could tell you more...
rashone said:
I had the same problem with aokp and newest twrp. I had to Odin back to stock, reroot, etc. Wish I could tell you more...
Click to expand...
Click to collapse
I'm downloading the stock rom now. Already downloaded the newest samsung drivers and installed. Was hoping not to go through all that but ....
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
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
jmdearras said:
My son's S4 is rooted, and a while back he loaded GooManager, and tried to install recovery with it. Phone still works, but tries to load code over the USB on power-up.
What does GooManager do to the system, and how can we undo it? Or should the phone just be wiped and odin flashed to 4.3?
Jim
Click to expand...
Click to collapse
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
k1mu said:
That's a common problem. You can't install a custom recovery using GooManager. At best, if you're running MDK, you can use Loki to flash a custom recovery.
The best fix for your situation is to flash a stock ROM. At the very least, grab the recovery from the stock ROM and flash that.
Click to expand...
Click to collapse
Do you know what GooManager does before rebooting? I'd like to manually remove it.
Where is the stock ROM for Verizon 4.2.2? Or can I just Odin 4.3?
Thanks much!
Jim
I have Phil Touch 6.0.4.5 CWM installed.
I put this on to try CM11. Didn't like it so re-flashed the the latest official ROM and its been running fine for a while now.
Theres a new official update out I wanted to try but flashing via CWM it says "Installation aborted".
I then tried the older official ROM and this too aborts hower CM11 installs fine.
Any ideas? I am Wiping ROM and clearing Cache.
You cannot flash official updates with custom recovery. You need the stock recovery for it.
A word of caution. The new OTA update most likely has knox. If you plan to try out other custom roms, refrain from flashing. If you are only a stock rom user, flash away.
Silesh.Nair said:
You cannot flash official updates with custom recovery. You need the stock recovery for it.
A word of caution. The new OTA update most likely has knox. If you plan to try out other custom roms, refrain from flashing. If you are only a stock rom user, flash away.
Click to expand...
Click to collapse
Thats odd. I could have sworn I reflashed the official rom using CWM.
Thanks for clearing that up.
Can I still enter standard recovery having CWM on there or do I need to reflash via a standard recovery via odin?
You need to flash one using Odin. If you have a flashable recovery zip file, you can replace the recovery image in the zip file with a stock one.
Sent from my GT-I9205 using Tapatalk
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Did you fiqure it out
Sent from my SM-G900P using XDA Free mobile app
lsdyna said:
Hello,
I followed this post to root and install TWRP recovery on my Sprint Samsung Note 3. The root procedures went well, showing rooted successfully.However, I installed TWRP recovery using GooManager, and also tried installig through Odin.
It shows that TWRP recovery is successfully installed, but I am not able to boot into recovery. The phone seems to try to boot into TWRP for ever.....
Later I read this post, which says that Do not try on Android 4.4.2 KitKat firmware!
IS my issue due to my rooting and installing TWRP are based on 4.4.2 (my phone is having new NC5 OTA update)? How shall I do?
Thank you very much for your helps!!!
Click to expand...
Click to collapse
You should be suing TWRP 2.7.0.1 and do not use goo manager.. Go to their site and click on the alternate download.. I do believe TWRP mentioned they disable the goo manage download because of issues.. Make sure you are also choosing the right phone.. I have choosing the wrong phone more than once.. Also when your done flashing in odin, and you reboot into recovery manually, make sure you wait until you see the line about recovery, before you release the 3 buttons, or you will just boot into your desktop.. Also you can use TWRP on KItKat firmware as many have done so..
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Drake9897 said:
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Click to expand...
Click to collapse
Bump, would really like some help :/
Back to stock
Drake9897 said:
Bump, would really like some help :/
Click to expand...
Click to collapse
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
I'll try that! Thanks! (sorry for late reply)
just flashed stock and got twrp back, tried to flash my RLS 19 backup and it completes at 3gb out of 1.2gb and 170% out of 100%. ugh :/ also twrp won't install via goo manager, have to use twrp manager .
TheSt33v said:
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
Click to expand...
Click to collapse
z
Also I'm running danvdh's lollipop GPE as well. It's actually the reason i updated twrp and started to get this issue. i'm running the same version of twrp as you and still no hyperdrive backup can restore. ):