I have a Verizon S4 ME7 and since ive rooted my phone i am unable to boot into recovery mode, but download mode works fine.
I followed the root steps here (http://forum.xda-developers.com/showthread.php?t=2380325) and i got supersu and root does work.
Then i installed CWM recovery following these steps (http://theunlockr.com/2013/07/30/ho...od-recovery-on-the-samsung-galaxy-s4-verizon/) but everytime i try to manually boot into recovery or through the CWM app, it gives me this error:
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : VZN
Successfully applied multi-CSC.
other notes: before the error the green android is loading then he tips over with a red triangle and the code appears, im confused on the problem i have went back to stock and then rooted again and same error again.
randiandi said:
I have a Verizon S4 ME7 and since ive rooted my phone i am unable to boot into recovery mode, but download mode works fine.
I followed the root steps here (http://forum.xda-developers.com/showthread.php?t=2380325) and i got supersu and root does work.
Then i installed CWM recovery following these steps (http://theunlockr.com/2013/07/30/ho...od-recovery-on-the-samsung-galaxy-s4-verizon/) but everytime i try to manually boot into recovery or through the CWM app, it gives me this error:
# MANUAL MODE #
-- Applying Multi-CSC...
Applied the CSC-code : VZN
Successfully applied multi-CSC.
other notes: before the error the green android is loading then he tips over with a red triangle and the code appears, im confused on the problem i have went back to stock and then rooted again and same error again.
Click to expand...
Click to collapse
If you rooted ME7 , the God's don't want recovery. If you rooted MDK they do...go figure.
ME7 has no recovery at this point, just root..
Sent from my SCH-I545 using Tapatalk 2
dang....
Pixelation said:
If you rooted ME7 , the God's don't want recovery. If you rooted MDK they do...go figure.
ME7 has no recovery at this point, just root..
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
So, does that mean i cannot install custom roms?
randiandi said:
So, does that mean i cannot install custom roms?
Click to expand...
Click to collapse
Yep.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
****HELP!**** I am having the same issue but I am on MDK build...
I am having the same issue... I was having the same error but,now I get the cwm recovery successful flash in rom mgr, go to reboot, and it just sits on recovery loading in the corner on the Samsung unlock screen... It is just stuck everytime I try it.help! I want something besides this stock rom.
Specifications:
Sch-i5454 (rooted)
4.2.2
Vruamdk
Kernel: 3.4.0-562219
I was previously rooted with hyperdrive rom and me wanting to try something new with cynagenmod 12 nightlies and it was too many bugs especially bluetooth. I tried to go back to hyperdrive and was unable to...that's why I am in this mess.
Related
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.
So I'd been having some problems lately with my phone hanging on the Samsung screen on boot. Been running CM11 1/1/2014 nightly most recently. Decided to try using TWRP instead of CWM. That didn't seem to help my issue, so I tried installing CWM again. I used an app called Recovery Tools to download the touch version of CWM. After it said it installed, I tried to boot into recovery and got the error "Unauthorized software found. Please contact Verizon." (paraphrased a little).
Doing some research it looks like that error typically comes up when the bootloader is locked. Now, obviously I had my bootloader unlocked (well, Loki'd) because I was running CM11. Any help fixing this? I'm able to bypass the warning screen on boot if I hold down vol up + power like I'm going into download mode, but then hit vol down to cancel to boot up the phone. Once booted everything is ok, but any reboot just brings that up again. Using ROM manager to flash CWM recovery seems to work ok and it says its installed, but same issue. So does trying to flash TWRP from Goo.
If I were to run this tool that I used to root and loki before (http://forum.xda-developers.com/showthread.php?t=2301720) to install a recovery, would I be able to get everything going again? I think that somehow the recovery I installed wasn't Loki'd, although I picked the right one for my device.
Thank you in advance for any replies.
The fix I found was by pure dumb luck. I ended up trying to flash a recovery with Odin. Odin failed but reboot back into the os. I then used the twrp manager app from the playstore (mainly because goomanager wasn't downloading the recovery at the time) to flash the latest twrp recovery and all was good. Even though Odin failed at flashing the recovery I still think it helped somehow. I haven't thought much about why but I might have to now.
Sent from my SCH-I545 using Tapatalk
You could probably try using ODIN to get back to stock MDK and then Re-Root and install a recovery after.
Edit: And then flash CM11 again.
Sent from my SCH-I545 using Tapatalk
Will this one-click stock ROM work?
http://www.rwilco12.com/downloads.p... S4 (Verizon) (SCH-I545)/Stock ROMs/One-Click
or, which of the files on this page are what I would want? (about 1/3 of the way down for SCH-I545)
http://www.droidviews.com/how-to-install-latest-official-firmware-on-samsung-galaxy-s4-all-models/
I was actually able to reflash TWRP w/ their app from the Play Store. Still get a lot of boot hangs on the Samsung logo though. Seemed to happen less with CWM, but now I'm too scared to try to install a different recovery. I appreciate all your help guys.
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..
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?
have tried safestrap ( says successful, but does not actually let you push "boot to recovery) and CWM. i had safestrap working before, but got a soft brick and had to flash a stock unrooted nk1 build via ODIN. any help is appreciated.
UPDATE:
problem was busybox APK was installed, but not binaries -.-