[Q] How do I update twrp - Verizon Samsung Galaxy S 4

I have an unlocked verizon gs4, and I'm running a KK rom. I'm getting multiple fc's, which I've read is due to an outdated recovery. I've tried odin {multiple times} failure each time. I have no idea what's going on. I hate dealing with recoveries. I totally bricked my tablet trying to update the recovery. It doesn't really matter to me which recovery I use. I'm used to cwm personally. I don't know what's happening with odin. I've used it many times without any problems, not this time. Anyway, if anyone has anything to say please do so. Thanks

wily5150 said:
I have an unlocked verizon gs4, and I'm running a KK rom. I'm getting multiple fc's, which I've read is due to an outdated recovery. I've tried odin {multiple times} failure each time. I have no idea what's going on. I hate dealing with recoveries. I totally bricked my tablet trying to update the recovery. It doesn't really matter to me which recovery I use. I'm used to cwm personally. I don't know what's happening with odin. I've used it many times without any problems, not this time. Anyway, if anyone has anything to say please do so. Thanks
Click to expand...
Click to collapse
Grab Flashify from the play store and you can choose which recovery you'd prefer. It's a fairly easy app to use. Do you have a Dev S4 or an MDK build with Loki exploit?
Sent from my SCH-I545 using Tapatalk

Try this.....
http://forum.xda-developers.com/showthread.php?p=52092093
Sent from a mod junkies I545

I have the MDK build. Thanks for the help. Flashy worked.

Related

[Q] Loki'd but can't boot

Hi all,
I've been running CM since May of this year (had an MDK phone) using TWRP. Today, I decided, foolishly, to start the upgrade process to CM11. Normally, I never had an issue, but because of some difficulty with gapps on KK, I had to restore a nandroid to get back going on CM 10.2. Unfortunately, I didn't realize that boot is not something you want to restore. Maybe that caused it, maybe it didn't. Regardless, I am in the situation where I cannot enter recovery (power+UP does not actually get into TWRP) nor can I enter the OS.
So I read and read how to try to rectify the situation, but it's difficult as there's a lot of conflicting stuff for the Verizon S4.
Since I have the bootloader Loki'd (I still have the bootloader unlocked icon), I think that I could just Odin a TWRP tar via the PDA option. I am fully ready to do this, but I wanted to ask since I think I am in a delicate situation. But if I need to do it via the Loki method, how can I do anything via ADB when I can't enter recovery or the OS itself.
Should I ODIN back to MDK and work my way forward?
Thanks for your time and any help!
Okay,
So, I think there is nothing much to say or suggest.
I did update the apnhlos to MK2. I wanted to update the baseband, and I read somewhere (perhaps mistakenly) that apnhlos updated stuff for bluetooth/wifi/etc. I was able to run CM with the updated apnhlos since MI1, so it never seemed to be a problem to me. But it seems that having an >MDK apnhlos means you are rather screwed in an event like this.
Considering that, I was unable to Odin TWRP (auth failure). I will be trying to Odin the stock MDK, but I don't think it will work considering the recovery failed. I doubt that the stock MJ7 will work either, but we'll see. If I am unable to get back onto ASOP, then I will likely be using my 3rd party warranty/insurance on an unrelated issue and try again on another phone.
Nvm
Sent from my SCH-I545 using xda app-developers app

[Q] [ROOT HELP] Rooted MJ7 to MK2 - Upgrade

Hey everyone,
So I'm having a bit of an issue. I currently own (and love) a Verizon Galaxy S4 (model number: SCH-I545). I rooted my phone back at the end of November, right after the MJ7 framework release and it's been splendid. I've gotten rid of all the bloatware using Titanium Backup and my phone absolutely soars through every program I run on it as well as works as a great business device.
I'm currently encountering two problems:
1. I can't seem to find a ClockwordMod or any type of recovery software that'll actually work and install correctly. I've tried the GooManager one and the ClockworkMod app one, and nearly bricked my phone in the process of doing so. As I'm sure you all know, not being able to have a recovery program makes it a pain in the butt to deal with. I was gonna flash CyanogenMod (like I once had on my Galaxy Tab) and go with it; however, standard rooted S4 seems to do the trick and is fast and some of the Samsung stuff isn't half bad, to be fair.
2. I need to find a MK2 zip that once I do get a recovery pushed, I can update the root for stability fixes. I've searched up and down and just can't find an MK2 pushable zip that won't be like the OTA one and make me lose my root.
So XDA, can you all point me in the right direction to get both of these fixed?
No
JacobNWolf said:
Hey everyone,
So I'm having a bit of an issue. I currently own (and love) a Verizon Galaxy S4 (model number: SCH-I545). I rooted my phone back at the end of November, right after the MJ7 framework release and it's been splendid. I've gotten rid of all the bloatware using Titanium Backup and my phone absolutely soars through every program I run on it as well as works as a great business device.
I'm currently encountering two problems:
1. I can't seem to find a ClockwordMod or any type of recovery software that'll actually work and install correctly. I've tried the GooManager one and the ClockworkMod app one, and nearly bricked my phone in the process of doing so. As I'm sure you all know, not being able to have a recovery program makes it a pain in the butt to deal with. I was gonna flash CyanogenMod (like I once had on my Galaxy Tab) and go with it; however, standard rooted S4 seems to do the trick and is fast and some of the Samsung stuff isn't half bad, to be fair.
2. I need to find a MK2 zip that once I do get a recovery pushed, I can update the root for stability fixes. I've searched up and down and just can't find an MK2 pushable zip that won't be like the OTA one and make me lose my root.
So XDA, can you all point me in the right direction to get both of these fixed?
Click to expand...
Click to collapse
There's no custom recovery available for your build. Only Safestrap. There's a few stickies you might want to read in the General section.
As far as MK2, I think your only option would be to use Odin and re-root using Saferoot.
Sent from my NCC 1701 using Tapatalk 4
JacobNWolf said:
Hey everyone,
So I'm having a bit of an issue. I currently own (and love) a Verizon Galaxy S4 (model number: SCH-I545). I rooted my phone back at the end of November, right after the MJ7 framework release and it's been splendid. I've gotten rid of all the bloatware using Titanium Backup and my phone absolutely soars through every program I run on it as well as works as a great business device.
I'm currently encountering two problems:
1. I can't seem to find a ClockwordMod or any type of recovery software that'll actually work and install correctly. I've tried the GooManager one and the ClockworkMod app one, and nearly bricked my phone in the process of doing so. As I'm sure you all know, not being able to have a recovery program makes it a pain in the butt to deal with. I was gonna flash CyanogenMod (like I once had on my Galaxy Tab) and go with it; however, standard rooted S4 seems to do the trick and is fast and some of the Samsung stuff isn't half bad, to be fair.
2. I need to find a MK2 zip that once I do get a recovery pushed, I can update the root for stability fixes. I've searched up and down and just can't find an MK2 pushable zip that won't be like the OTA one and make me lose my root.
So XDA, can you all point me in the right direction to get both of these fixed?
Click to expand...
Click to collapse
You can't find a custom recovery for your phone because there isn't one.
Please, before you brick your phone - disconnect the USB cable, walk away, then go read this sticky thread in the general forum.
Then read this thread.
The only thing available for post-MDK Verizon GS4s is Safestrap.
k1mu said:
You can't find a custom recovery for your phone because there isn't one.
Please, before you brick your phone - disconnect the USB cable, walk away, then go read this sticky thread in the general forum.
Then read this thread.
The only thing available for post-MDK Verizon GS4s is Safestrap.
Click to expand...
Click to collapse
I was reading the Safestrap recovery link that you linked and I noticed it was for locked bootloaders. How do you identify what bootloader you have? When I turn on the phone, it has the "Unlocked" sign, so it may be that I'm on the old bootloader. Any idea?
JacobNWolf said:
I was reading the Safestrap recovery link that you linked and I noticed it was for locked bootloaders. How do you identify what bootloader you have? When I turn on the phone, it has the "Unlocked" sign, so it may be that I'm on the old bootloader. Any idea?
Click to expand...
Click to collapse
You have a locked bootloader. You will have to use safestrap. Be sure to read. Lots of helpful links and tips in the general section. Yesterday I upgraded to mk2. Used saferoot. Installed safestrap. Loaded up hyperdrive. Runs great.
Pmmac said:
You have a locked bootloader. You will have to use safestrap. Be sure to read. Lots of helpful links and tips in the general section. Yesterday I upgraded to mk2. Used saferoot. Installed safestrap. Loaded up hyperdrive. Runs great.
Click to expand...
Click to collapse
Do you have the zip/update package for mk2? Can't seem to find it myself
JacobNWolf said:
Hey everyone,
So I'm having a bit of an issue. I currently own (and love) a Verizon Galaxy S4 (model number: SCH-I545). I rooted my phone back at the end of November, right after the MJ7 framework release and it's been splendid. I've gotten rid of all the bloatware using Titanium Backup and my phone absolutely soars through every program I run on it as well as works as a great business device.
I'm currently encountering two problems:
1. I can't seem to find a ClockwordMod or any type of recovery software that'll actually work and install correctly. I've tried the GooManager one and the ClockworkMod app one, and nearly bricked my phone in the process of doing so. As I'm sure you all know, not being able to have a recovery program makes it a pain in the butt to deal with. I was gonna flash CyanogenMod (like I once had on my Galaxy Tab) and go with it; however, standard rooted S4 seems to do the trick and is fast and some of the Samsung stuff isn't half bad, to be fair.
2. I need to find a MK2 zip that once I do get a recovery pushed, I can update the root for stability fixes. I've searched up and down and just can't find an MK2 pushable zip that won't be like the OTA one and make me lose my root.
So XDA, can you all point me in the right direction to get both of these fixed?
Click to expand...
Click to collapse
take some time to read...this is a stickie
http://forum.xda-developers.com/showthread.php?t=2606501
decaturbob said:
take some time to read...this is a stickie
http://forum.xda-developers.com/showthread.php?t=2606501
Click to expand...
Click to collapse
I'm not a n00b to this at all. I now have Safestrap, it runs fine. I rooted it by myself and have done a lot to it since (November 2013). I get how these things work, but I can't for the life of me find an update zip for MK2. That's all I'm looking for at this point.
JacobNWolf said:
I'm not a n00b to this at all. I now have Safestrap, it runs fine. I rooted it by myself and have done a lot to it since (November 2013). I get how these things work, but I can't for the life of me find an update zip for MK2. That's all I'm looking for at this point.
Click to expand...
Click to collapse
I think you have to search for an MK2 tar file to use with Odin.
Sent from my NCC 1701 using Tapatalk 4
The success is real!
riker147 said:
I think you have to search for an MK2 tar file to use with Odin.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
FOUND IT! WOOP, thanks for the help guys; for anyone else trying to find one, use the "No-Wipe" in this thread, http://forum.xda-developers.com/showthread.php?t=2578209 and flash with ODIN 3.09, located here: http://rootjunkysdl.com/getdownload.php?file=Galaxy S4/Firmware Odin MK2/Odin3-v3.09.zip

ROM Install after NG6-NC5 downgrade

After two and a half hours of frustration, I eventually gave up.
I downgraded from NG6 to NC5, and then from NC5 to both NC2 and MK2 (separately) after MUCH Googling and forum searching.
For the longest time I couldn't get anything to work, until I realized that my USB extension cable was the cause of my problems. I finally got down to NC5 rooted. I tried to install Liquid Smooth and Cyanogenmod through Odin, and it wouldn't work. I got Liquid Smooth to install through Safestrap, but it just got stuck at the loading image forever.
I eventually got frustrated and let the Samsung software put NG6 back on, and left it alone. That's where I'm at now.
I assure you I've read absolutely every thing ever written on every subject by every person ever born in the history of mankind while trying to figure this out. Can someone PLEASE give me a walkthrough SUMMARY of how to get custom ROMs on this phone, beginning with NG6? I'm not a newbie. I've rooted and installed custom ROMs on numerous phones and tablets. But I can't keep playing with this phone, trying to get it to work. I'm going to end up becoming a serial killer if I get one more error message. I am now desperate, and asking for help.
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
sponix2ipfw said:
Serial killer might be in your future. Unless you are MDK, safestrap is what you are limited to and it has only a few ROMs it can function with. Cyanogenmod is not supported with safestrap, AOSP/AOKP and such can soft-brick the phone.
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
"Serial killer might be in your future" lololololol.

[Q] Installing TWRP on jfltevzw 4.4.2 (NC5)

I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
zQueal said:
I was one of the idiots that accidentally upgraded to the newest firmware when it first came out. My device is totally rooted, but I've been reading that I'm required to use things such as SafeStrap or Loki to install custom roms. I'm not sure if this is still the case as its been months since this was discovered. I've been trying to search the forums extensively for a fix, but I've been unable to find one. One thing I came across: here seems to be a very simple way to install TWRP on the Galaxy S4, however, I don't wan to run the risk of bricking my phone and being SOL because I have ****ty firmware and no way to custom recover my phone.
Point blank, would I be able to install TWRP manager via GooManager given that I've updated to NC5? Or even if not, what are my options for custom recovery/roms? End game, I want to walk away with 5.0.1 GPE or Cyanogenmod 12. Hopefully.
I'd really appreciate any and all help. Attached is a screenshot of my phone information.
Click to expand...
Click to collapse
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
scrillakev said:
Once you updated to anything past MDK there's no going back . Safestrap is the only option to install Touchwiz ROMS.
Click to expand...
Click to collapse
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
zQueal said:
Damn! That's what I figured. I followed [this guide](https://www.youtube.com/watch?v=BLHZfPwLkPM) and installed the SafeStrap APK, but stopped at the "install recovery" step. I've been reading that this can soft brick your phone. Do you have any input? Is it safe to do? If it does brick my phone will I be able to factory reset with Odin?
Sorry for the barrage of questions, I'm a bit of a noob.
-----------------------------------------------------------------------
EDIT:
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.
Click to expand...
Click to collapse
I never used SafeStrap so I doubt I will be much help. But once you rebooted your stock ROM is no longer there? Might have to just flash a stock image via ODIN and try again. Verizon isn't going to help you either with modding your phone, XDA is the place to be.
Has there been anything new since this thread was posted or is it impossible still?
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Sorry buddy you're SOL
Sent from my SCH-I545 using XDA Free mobile app
If you are rooted use a terminal editor app and type:
getprop ro.bootloader
If it says anything other than I545VRUAMDK your only choice is SafeStrap.
That means if you bought an S4 and it came with MK1, NC5, NK1, or anything other than MDK you cannot flash a custom recovery. The same applies if you took an OTA from VZW. This has been stated 1000's of times here.
Hint:
Look on the box that your S4 came in and read the last three characters where it says what build the phone has.
mcbeat257 said:
Has there been anything new since this thread was posted or is it impossible still?
Click to expand...
Click to collapse
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
safestrap version
Well, I decided to go ahead with it. It worked fine. I rebooted to SafeStrap and went right to do a backup. It failed. I tried to reboot into my stock rom, and it was 0MB. I really might blow up Verizon HQ.[/QUOTE]
***Make sure you are using the correct version of safestrap for your current baseband
another good app from the google play store to download is samsung info
I have used safestrap in the past as I was in the same scenario as you. I currently now have a MDK phone
Illogi.xbone said:
Keep checking up on SS they are working on the ability to also use custom kernels on top which would make it essentially as efficient as a custom recovery, with some storage loss.
Click to expand...
Click to collapse
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
mcbeat257 said:
How come they haven't been able to unlock the bootloader when only the build version is changing......
There should have been an exploit awhile ago....and why haven't they made an odin option for MDK yet?
Click to expand...
Click to collapse
The exploit was weeded out after MDK
Sent from my SCH-I545 using XDA Free mobile app
The bootloader was never "unlocked" on MDK, there was just an exploit available that allowed the installation of a custom recovery. That exploit was closed in the first update from MDK and a new one has not been discovered. The bootloader itself has some pretty strong encryption so it may never be unlocked.

Any way to ROOT or Downgrade 5.0.1 OC1

I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Nope, by taking the latest OTA (or in this case Kies) you've locked yourself into the latest version, for which there is currently no Root
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
52brandon said:
That sucks. No way to use Odin in order to downgrade or anything? This is the first time since I've ever owned an android phone that I've been stuck without root
Click to expand...
Click to collapse
Nope. Locked Bootloader sucks.
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Charlie115 said:
Every single time there is an update these individuals always end up in this situation! !! No matter how many times they're told to wait and just not update!!!
Click to expand...
Click to collapse
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
52brandon said:
I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed.
Click to expand...
Click to collapse
If you're ever in this situation again, give up on retaining your current root, flash back to true stock (with a re-partition .pit file as well), and re-root. If you had flashed the nc5 full-wipe with the .pit file and just restored root from a clean system, you would have been fine.
52brandon said:
Don't lump me In with that crowd. I had no intention on going to 5.0.1. If you read my original post, I was upgrading to Hyperdrive KK21 from KK20 (and yes, I followed every single instruction to the T. My only guess is that the USB connection got messed up and only flashed a portion causing the problems) and it **** the bed mid-update. I couldn't get into SS recovery or even stock recovery, only DL mode. I spent 2 days without a working phone trying to flash every single Odin file that retained root and they all failed. So I used Kies to try to repair it and ended up ****ed on 5.0.1. The one solution I didn't want. I've NEVER had an android since the D1 that wasn't rooted running a custom ROM. Which is why I'm so desperately trying to get back to rooted. While 5.0.1 is actually a very nice OS, not having all the root options is killing me. And since its now 2 generations old, my hopes that a root exploit will be found, or that people even care enough to try to find one are extremely low. But, I sure hope I'm wrong, and that an exploit for one of the newer generations Galaxies will work on this one too. I'm OCD about having root and this is killing me
Click to expand...
Click to collapse
Well, you should have known better than to use kies...
Sent from my SCH-I545 using XDA Free mobile app
Honestly I don't even think that devlopers will make much effort to even find out how to root this version as its says that this is one of two updates before getting lollypop.
Development Forums are for developers to share their work and post their Roms and Mods.
Questions belong in the Q&A section.
Thread has been moved to correct section, please pay attention to XDA rules.
Root
52brandon said:
I don't mean to beat a dead horse, as I'm sure it's been brought up. But every search I've done just brings up how to update to OC1 without losing root. All the way back to the original Motorola Droid, I've always rooted and added a custom recovery and ROM to every phone I've had. I was running Hyperdrive RLS20 and loved it. I've been using Hyperdrive since my Galaxy S3. Then I saw Hyperdrive RLS21 came out and decided I wanted to give it a shot. And although I've flashed over a few hundred ROMs no problem, this time really screwed my phone. I could only get into DL mode. I tried about 25 different ways until I had Kies fix it, which put it on 5.0.1. Can I revert down with Odin? Or is there anything I can do to get root and SU back. Any help would be much, MUCH appreciated
Click to expand...
Click to collapse
KingRoot 4.1 rooted my galaxy s4 on oc1....and try flashing an nc5 tar in flashfire
You cannot flash anything with flashfire. If you flash that tar, you WILL brick.
Question
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Epiphany^ said:
Just wondering, i have rooted my OC1 with Kingroot 4.1, now, can someone make a guide showing how to downgrade from OC1?
PD:. Sorry for my horrible english.
Click to expand...
Click to collapse
You can't downgrade from OC1.
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
kingroot does work
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Munk3ybones said:
I had done the dumb thing and was impatient and did the oc1 update to later find out you can not downgrade and im on Verizon Samsung galaxy s4 (sch-i545) which even on kit kat is very limited to rooting it.. but on a whim I seen a post about king root and it mentioned that and I did see this myself but it will say not supported like it did on mine. but I figured what the hell.. whats the worst that could happen... well im rooted now and only tried because I had seen others make that comment.. well kingroot works for s4 Verizon with locked bootloader.. no need to downgrade from oc1.. just get the app and click... took less than 10 mins if I rememner right.. and I have had no pronlems in 3 days.. it oddly even fixed some of the bugs I was having with oc1 like incoming calls not ringing
Click to expand...
Click to collapse
You have root. But you have a much lower chance of getting an unlocked Bootloader than anyone on NC5/NK1/NK4. They have root, module loading, and a potential for kexec to run custom kernels.
Don't upgrade to OC1 via OTA if you haven't already everyone! Use Muniz_ri's keeproot upgrade method!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 12:53 AM ---------- Previous post was at 12:53 AM ----------
bigg6987 said:
Downgrade isn't a root issue, it is a bootloader issue. Unless the bootloader gets unlocked, we're stuck on OC1
Click to expand...
Click to collapse
Even then you're stuck. Rollback has little to do with the BL. Rollback is set at a much lower level (physically).
Sent from my Nexus 6 using Tapatalk

Categories

Resources