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.
Related
Hi XDA, I'm a relatively new owner to Android phones (3 weeks) and have a problem that I can't find any leads on.
I cannot flash any Touchwiz-based ROMS without the phone going into a boot loop and having to reflash via Odin. I know that AOSP ROMS work fine because I use goomanager to flash CM10, Carbon, and Liquid smooth previously. The problem only occurs with touchwiz roms. Here is the rundown of how I noticed the problem:
I download Crash ROM and move it to my internal SD card. I install TWRP via goomanager. I then use goomanager to wipe the data, cache, and dalvik cache, and to install the Crash ROM zip. The phone gets to the samsung logo then gets stuck in a boot loop.
I reflash it through Odin using the tutorial at GalaxyS4root and it boots fine. I use goomanager to reinstall TWRP and try flashing it through TWRP instead, again doign a full wipe of the data, system, cache, and dalvik cache. Same thing occurs and I reflash through Odin.
Fast-forward to last night; I decide to try another Touchwiz rom, this time Wicked ROM. I download it and put it on the internal SD card; using TWRP I wipe it again, and install it. Aroma Installer comes up and I make sure to select AT&T as my carrier. I get to the end of the installation and the phone reboots. This time its much worse than it was with Crash ROM, the phone is vibrating to signal it starting up, but the screen stays blank and then a few seconds later it vibrates again. This repeats constantly and the phone also couldn't boot into recovery mode (but it could boot to download mode). So I tried reflashing it twice, but the issue persisted. Through google I determined it to be a stuck power button. I've returned the phone to AT&T to be replaced for faulty hardware and am awaiting its return.
So now is where I ask you guys. I've spent a solid hour googling this and nothing related to my problem comes up. So does anyone have any experience with the S4 not being able to flash touchwiz based roms? Or could anyone point me to any leads as to why this would occur that I can investigate further?
Thanks for the help.
-Tryer
EDIT: I'm pretty sure it wasn't MF3 because I could flash certain ROMS fine.
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
DeadlySin9 said:
You made sure to flash a touchwiz kernel? And if you have AT&T model you made sure to use either auto-loki recovery or flash the loki zip?
Click to expand...
Click to collapse
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Tryer1234 said:
For Wicked ROM, in the Aroma installer it asked which kernel I wanted, I don't remember for sure but I either chose Stock or Deviant. I'm still new to Android device so does GooManager or TWRP auto-loki? If not then I did not flash loki over either, I'm not sure if this would keep touchwiz ROMS from running but allow AOSP ROMS to run.
Click to expand...
Click to collapse
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Aou said:
Just skimmed the OP and thread a bit - sounds like you need to loki your kernels, basically. TWRP doesn't auto-loki, but do a quick search for loki-doki.zip - if flashed immediately after flashing a kernel (or rom with kernel), it will patch the kernel to take advantage of the Loki exploit in aboot. You pretty much have to do this for every/any kernel that's not 100% pure stock. Some recoveries (like CWM I believe) will auto-loki, but I don't ever rely on these. I just always flash loki-doki.
Click to expand...
Click to collapse
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Tryer1234 said:
Thanks, how would I loki something like Wicked ROM though, which once it finishes with Aroma installer, immediately reboots the phone and bricks itself? I don't have a chance to loki as I can't get back to TWRP before that occurs. Also there is a chance the new phone I receive will have MF3, will rooting and using Loki allow me to use Odin to restore it, or is there as of yet no way to reflash the stock ROM on MF3 devices?
Click to expand...
Click to collapse
when the device reboots after the aroma install, i would pull the battery, replace it and use the 3-button combo to enter custom recovery. then i'd flash the loki-doki zip. thats just me though. i hate aroma.
http://lmgtfy.com/?q=what+is+loki+doki
also: http://forum.xda-developers.com/showthread.php?t=2292157
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.
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. Writing from my Phone now. Im running cm 11. I installed or flashed philz touch...
Then installed cm11.
I want to do a nandroid backup..
But when i tried restarting to recovery, it skipped that part and went to cm11..
Normal reboot.
Before i flashed cm i had latest stock rom from samsung.
I flashed philz touch that time to..
But when i then installed cm, something went wrong, got some error on cm.
Uid's something. Forgot. I could not boot in recovery, so i used odin, flashed philz touch.
Factory reset and my Phone was fine!
Cm and recovery.
Now it seems i cant get into recovery again...
Anyone know whats the issue?
Locked bootloader? Have not read up on that yet...
Its wierd if recovery just fails or whats the issue.
Pardon the blurry explenation and my bad english/spelling. Im tired.
Thanks in advance.
It was the Quick boot app. Since i set developer options in cm to restart into recovery through CyanogenMod.
But the Buttons did not work last time i tried.
But its kinda solved. Flashed the latest recovery with rashr yesterday...
So i will just use cm to boot into recovery..
Thanks anyways.
I'm still running stock rooted MF9 with TWRP. I've only taken TWRP as far as 2.5.0.2 and am wondering if there's any risk to upgrading to 2.8.3.0 or completely swapping out recoveries to Philz latest. Is it possible upgrading or changing recoveries would impact the existing ROM's ability to boot or cause other issues? I've been away long enough that I simply can't remember if an existing ROM would be recovery agnostic. Thanks!
No none at all.
Thanks!