HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
clarinetboy said:
HI, so I'm on MDK, rooted, and running GPE 5.0 LP, and I was recently attempt to update my recovery. I used Jrummy's ROM installer to install the TWRP 2.8.3. I rebooted, and now when i load into recovery, it says "kernel secure fail" and won't let me do anything. Is there a way to fix this? Any help would be appreciated.
Update: After attempting to reboot it a few times, I am able to boot to ROM, but still unable to boot to recovery.
Click to expand...
Click to collapse
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
MehStrongBadMeh said:
Boot to the ROM and install Flashify from the Google Play store. Use it to install the latest TWRP. That should clear everything up.
Click to expand...
Click to collapse
Hmm. Ok so I installed TWRP 2.8.3 via Flashify, and successfully rebooted to recovery. I then flashed JFLTE-GPE 5.0 (jan. 2nd version). Now can't boot to either recovery or ROM, both of which are saying "secure fail: kernel." I did not loki doki. Ahh help!
Update: After rebooting multiple times, I can now reboot to recovery, but not to ROM.
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
clarinetboy said:
Update: I used the 12/24 loki doki and now it seems like the ROM is working.
Click to expand...
Click to collapse
I ran into a similar problem, and had to completely restore to stock via Odin.
What were your steps here? Also I had trouble getting loki to install, which steps did you use?
Related
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
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
First, you should have done more research. You can't install a custom recovery on 4.3 (or MJ7). The only thing available is a "questionable" root method. No custom ROMs and no Safestrap.
Second, once an update has been applied, there is no way of going back.
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
If that doesn't work, try this one. http://forum.xda-developers.com/showthread.php?t=2507253.
Make sure you read ALL instructions first.
Good luck.
m634 said:
So after rooting and taking the android 4.3 update, my phone worked just fine with root. Then I tried to install a custom recovery (TWRP, using the ADB method) and ever since then, the recovery is just gone. Whenever I try to boot into it, the phone boots into download mode with an error message saying, "Could not do normal boot". After that, I tried installing TWRP from the Goo Manager app. Nothing changes. I also can't find a stock restore for 4.3 or a downgrade to 4.2. Is there any way for me to get back stock recovery or a custom recovery?
Click to expand...
Click to collapse
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
k1mu said:
You can't install a custom recovery on 4.3/MJ7.
The only way to recover this is for you to flash the full-wipe MJ7 image that you'll find here in the development forum.
Then, consider reading before flashing. The I545 has a locked bootloader and can't support a custom recovery or custom kernels.
Click to expand...
Click to collapse
Thanks! Knowing this, I think I will just stick with root but no recovery...hopefully, something will change and allow me to unstick myself from this situation in the future.
riker147 said:
You should check this thread out. http://forum.xda-developers.com/showthread.php?t=2507217.
Click to expand...
Click to collapse
This worked well when I had the same issue. I did lose root even with Survival Mode enabled on SuperSU, but otherwise no issues. Thank you.
I have a rooted MDK Verizon S4 with SuperSU installed. I had been trying to use Rom Manager to install clockworkmod recovery and every time, it comes back with the message that it has been successfully installed. When I try to boot into recovery, it wouldn't work. I finally installed GooManager and went ahead and installed TWRP. Now I am able to boot into TWRP with no issues, but when I try to overwrite and install clockworkmod recovery from within Rom Manager, it again comes back with the message that it has been successfully installed, but it still boots into TWRP.
I understand that I can use TWRP to switch over to a different rom, but I am just befuddled as to why I am not able to install clockworkmod. Can you guys please help me understand what I am doing wrong?
the_jaguar said:
I have a rooted MDK Verizon S4 with SuperSU installed. I had been trying to use Rom Manager to install clockworkmod recovery and every time, it comes back with the message that it has been successfully installed. When I try to boot into recovery, it wouldn't work. I finally installed GooManager and went ahead and installed TWRP. Now I am able to boot into TWRP with no issues, but when I try to overwrite and install clockworkmod recovery from within Rom Manager, it again comes back with the message that it has been successfully installed, but it still boots into TWRP.
I understand that I can use TWRP to switch over to a different rom, but I am just befuddled as to why I am not able to install clockworkmod. Can you guys please help me understand what I am doing wrong?
Click to expand...
Click to collapse
You can either ODIN the CWM edition you want (for example Philz Touch Recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) - get the md5 file of course for ODIN. You can also try to flash the zip file of Philz Touch Recovery from your SDCard (same site - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) through TWRP. Reboot into recovery and see what happens.
Skeetch79 said:
You can either ODIN the CWM edition you want (for example Philz Touch Recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) - get the md5 file of course for ODIN. You can also try to flash the zip file of Philz Touch Recovery from your SDCard (same site - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) through TWRP. Reboot into recovery and see what happens.
Click to expand...
Click to collapse
Thanks. When I was trying to install CWM within Rom Manger, I ended up paying for the touch upgrade, hence my desire to try and install CWM form within Rom Manager... It's just a bit frustrating that I can't figure out what's going on..
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
....
Bootloader is locked and custom recovery can't be installed on newer/updated S4. Do some reading to find out what is and is not possible with a locked bootloader.
the immunity said:
I have Safestrap up and running again but I'm wondering how can you install other recoveries like TWRP and CWM so I can boot directly into the custom recovery without a splashscreen I believe it's called (newbie here). I followed instructions online with GooManager for TWRP and ROM Manager for CWM but neither will actually boot into the custom recovery.
In GooManager after it says the TWRP recovery has been installed, it will reboot but then take me to the downloading boot screen and say "could not do a normal boot." What's with that? I actually had to use ODIN again to flash the stock ROM back (I tried this three times to no avail...)
And for CWM it says it successfully flashed in ROM Manager but when I actually reboot into recovery, whether it be from the app or manually, it will just boot into the stock Android recovery. I don't get it...
What am I doing wrong and/or is my phone not compatible with these recoveries?
Specs:
Verizon Galaxy S4
Android 4.3
Build MK2
Kernel MK2
Also are there any other recoveries that might work with my phone?
Thanks!
Click to expand...
Click to collapse
I'm not sure how any one misses a sticky thread like this one:
http://forum.xda-developers.com/showthread.php?t=2606501
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..