Hello,
I recently got a Samsung Galaxy S4 Google Edition (i9505G) and went through all the steps of rooting, unlocking, and flashing CM11. I noticed that when I tried installing CWM 6.0.4.4 on it, it would work to let me install CM11, but then somehow still reboot into stock recovery: (I made a thread here before I found a solution: http://forum.xda-developers.com/showthread.php?t=2603469).
I just recently installed TWRP 2.6.3.0 and found it to work without the issues I was having with CWM 6.0.4.4, although both are supposed to work fine. Is this a known problem or has anyone else found the same thing?
This isn't really a question (hence not in the Q&A) as I find it to be a development question for CWM in case I'm the first to have this findings with the recent CWM and recent 4.2.2 Android builds.
mrmartin86 said:
Hello,
I recently got a Samsung Galaxy S4 Google Edition (i9505G) and went through all the steps of rooting, unlocking, and flashing CM11. I noticed that when I tried installing CWM 6.0.4.4 on it, it would work to let me install CM11, but then somehow still reboot into stock recovery: (I made a thread here before I found a solution: http://forum.xda-developers.com/showthread.php?t=2603469).
I just recently installed TWRP 2.6.3.0 and found it to work without the issues I was having with CWM 6.0.4.4, although both are supposed to work fine. Is this a known problem or has anyone else found the same thing?
This isn't really a question (hence not in the Q&A) as I find it to be a development question for CWM in case I'm the first to have this findings with the recent CWM and recent 4.2.2 Android builds.
Click to expand...
Click to collapse
I use CWM 6.0.4.4 on my i9505G as I prefer it to TWRP. I have run both at different times with no issues except TWRP will sometimes lock on the splash screen.
wilbarger said:
I use CWM 6.0.4.4 on my i9505G as I prefer it to TWRP. I have run both at different times with no issues except TWRP will sometimes lock on the splash screen.
Click to expand...
Click to collapse
Did you use the i9505 version of CWM 6.0.4.4?
mrmartin86 said:
Did you use the i9505 version of CWM 6.0.4.4?
Click to expand...
Click to collapse
Yes, the version for jfltexx. I flashed it through ODIN and never had any problems with it. Are you using ODIN to flash your recoveries?
wilbarger said:
Yes, the version for jfltexx. I flashed it through ODIN and never had any problems with it. Are you using ODIN to flash your recoveries?
Click to expand...
Click to collapse
Sometimes. I think I found the problem. I was using ROM Manager to flash the recovery, which seems to write the recovery somewhere else, because then I get stuck in a CWM bootloop when I would hit Restart-->Recovery. That is how I was getting stock recovery and CWM, because I just replicated the problem and had TWRP and CWM, then touch CWM and CWM. I don't know if it it writing it in a temporary fashion, but it is annoying. I'm going to just fix it by just using the ODIN versions and being done with it.
Related
Hi all,
A while ago I soft bricked my I9505 and returned back to stock ROM and stock recovery.
Now I want to install Omega ROM again.
I always used CWM Recovery... on my S2, S3 and on the S4.
Is TWRP or Philz recovery a better choice?
No, it doesn't really matter. Though I prefer CWM for the same reason as you mentioned.
I would recommend Philz touch recovery because it is based of CWM, and it is a very good recovery.
I've heard some issues for the newer versions of TWRP for flashing some custom ROMs, but i used TWRP from the beginning so i'm sticking with it. I like the interface.
Any recovery will do, though. :silly:
Thanks guys...
I'm now with Philz Touch CWM.
To be honest, I like it a lot.
I don't use the touch function though. Chances are bigger that you click something wrong
You can see that it is actually an improved version of CWM.
I really like it a lot.
I have a D801 (T-Mobile). I rooted it a while back. I'm a bit of a noob. Recently, I wanted to flash KitKat. To do that, I had to flash a custom recovery. I installed TWRP as that was the one my instructions gave me. However, I am unable to flash anything. I cannot flash kitkat, cwm, stock, etc. I need any and all suggestions to at least flash stock recovery though I would really prefer to flash cwm.
PinkPanther3719 said:
I have a D801 (T-Mobile). I rooted it a while back. I'm a bit of a noob. Recently, I wanted to flash KitKat. To do that, I had to flash a custom recovery. I installed TWRP as that was the one my instructions gave me. However, I am unable to flash anything. I cannot flash kitkat, cwm, stock, etc. I need any and all suggestions to at least flash stock recovery though I would really prefer to flash cwm.
Click to expand...
Click to collapse
Got same Problem. Cant factory reset with twrp or cwm recovery. When i tried it frezzes when i flash a custom Rom sometimes shows me an error sometimes not. It doesent install or wipe. When i reboot everything is like before. Using stock LG rooted ... So no love for custom Roms hmm
Sent from my LG-D802 using XDA Premium 4 mobile app
Having a recovery that is up to date is key to flashing kitkat roms. I use Freegee. It's a free app in the Play Store. Once you install and run you'll have the option to install a recent twrp or cwm. You flash the recovery from the app, could not be easier. I recommend twrp 2.6.3.3 as I had issues with cwm 6.0.4.6 and it's also faster.
Make sure you're rooted before
Returned to Stock
PallyBud said:
Having a recovery that is up to date is key to flashing kitkat roms. I use Freegee. It's a free app in the Play Store. Once you install and run you'll have the option to install a recent twrp or cwm. You flash the recovery from the app, could not be easier. I recommend twrp 2.6.3.3 as I had issues with cwm 6.0.4.6 and it's also faster.
Make sure you're rooted before
Click to expand...
Click to collapse
I was rooted. Also, nothing seemed to recognize d801. They recognized the verizon, att, and the international but not t-mobile. I eventually just had to reinstall the stock rom as installing cwm over twrp froze my phone on the lg logo. Haven't gotten back around to rooting it again. When I do, I will definitely try that app.
Thank you
PallyBud said:
Having a recovery that is up to date is key to flashing kitkat roms. I use Freegee. It's a free app in the Play Store. Once you install and run you'll have the option to install a recent twrp or cwm. You flash the recovery from the app, could not be easier. I recommend twrp 2.6.3.3 as I had issues with cwm 6.0.4.6 and it's also faster.
Make sure you're rooted before
Click to expand...
Click to collapse
Thanks you for suggesting Freegee. I have been unable to flash anything for a while but after I downloaded Freegee and updated my version of TWRP I was able to flash the current version of PA.
Hi,
I currently have CWM 6.0.4.4 installed on my d802 but I can't update it.
I have tried flashing using this tool:
CWM 6.0.4.7
TWRP 2.7.0.0
CWM Touch 6.0.4.4
I also tried flashing with ROM Installer.
In every case, the flash seems to work fine, but I reboot to recovery and it's still CWM 6.0.4.4 and nothing has changed. I've tried factory reset, wiping cache (dalvik too), yet it didn't make a difference.
If it matters, I'm currently using CM 10.2-20131110-NIGHTLY-d802.
The point of this is because I get an error when I try to flash a kitkat rom (e.g. CM 11.2) and I assume I need to update recovery.
Any help or suggestions would be appreciated.
http://forum.xda-developers.com/showthread.php?t=2584938 Try flashing twrp 2.7 this way
OH MY GOD I had Root Access set to Apps Only in Dev options. I feel like an idiot.
Thanks anyway Art, at least Flashify made me realise there was an issue with root.
Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?
Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk
Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl
Uncheck auto-reboot in Odin.
Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!
Hi all,
Had been rocking Fusion's Lollipop ROM since inception but decided to try another flavor and installed Cyanogenmod along with their new own recovery which overwrote TWRP. Didn't think much of it until I decided this ROM wasn't for me. Flashing of TWRP fails through Cyanogen Recovery though I have been able to flash ROM's. Also attempted flashing a .tar via ODIN which claims it was successful, alas Cyanogen Recovery persists.
As there seem to be other limitations with this recovery I'm determined to remove it but having a heck of a time. Any suggestions??
Thank in advance
stevedavies76 said:
Hi all,
Had been rocking Fusion's Lollipop ROM since inception but decided to try another flavor and installed Cyanogenmod along with their new own recovery which overwrote TWRP. Didn't think much of it until I decided this ROM wasn't for me. Flashing of TWRP fails through Cyanogen Recovery though I have been able to flash ROM's. Also attempted flashing a .tar via ODIN which claims it was successful, alas Cyanogen Recovery persists.
As there seem to be other limitations with this recovery I'm determined to remove it but having a heck of a time. Any suggestions??
Thank in advance
Click to expand...
Click to collapse
I had the same problem, here is how i solved it:
go in to play store and download TWRP MANAGER install the app and then go to install twrp, select your device and the right recovery for your phone and start flashing...
jonpah said:
I had the same problem, here is how i solved it:
go in to play store and download TWRP MANAGER install the app and then go to install twrp, select your device and the right recovery for your phone and start flashing...
Click to expand...
Click to collapse
Had an issue with my account for a bit and subsequently forgot to reply, if anyone has the same issue - fixed! Such a simple solution. Hate to admit how long I spent messing around with this... Thanks to Jonpah!