I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
calaski8123 said:
I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
Click to expand...
Click to collapse
1)mk2
2) nobody has been able to unlock new boot loader so as long as there is a root method it should not matter. Don't know about mk2 but I believe mj7 has root.
3)mdk
Me7
Mi1 (I think)
Mj7
Mk2
I think I got them all.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
calaski8123 said:
I am currently on ME7 stock build. I have rooted and unlocked my last 5 phones and thought I would do the same with the GS4 until I was surprised to see all the issues with the newer builds. I know about safestrap but I haven't taken the plunge yet. Every night I have been delaying the OTAS update Verizon is pushing out. I didn't want to upgrade to an even worse build to be on that nothing would allow me to root.
1) What is the build that Verizon is currently pushing?
2) Is it better, worse or the same when it comes to future potential to unlock and root?
3) Is there a list or chart anywhere what has a chronological order of Verizon build numbers so I can see what is being pushed each time an OTA is offered and I can research what it means for unlocking and root purposes?
Thanks,
Jim
Click to expand...
Click to collapse
Being on ME7 you are being prompted to update to MI1, then you will be prompted to update to MJ7, and finally to MK2 (the most recent). Safe rooting methods for each of these builds are different but readily available if you look in the Verizon Galaxy S4 forums. Recently, Hashcode has provided the community with the only recovery for MJ7 and MK2 - Safestrap. When you say unlock I'm guessing you mean the bootloader which is still locked - and a difficult nut to crack although there are some very smart guys working on it. I recently got my GS4 and am currently on MK2 rooted with safestrap installed. I don't see an advantage of ME7 to MJ7 or MK2 but others may feel differently. For a while ME7 and MI1 were the only builds that Safestrap worked on, but now that MJ7 and MK2 are safestrap compatible, there doesn't seem to be a disadvantage to the newer builds. Hope that helps sort it out a little. Cheers.
CoMtnMan said:
Being on ME7 you are being prompted to update to MI1, then you will be prompted to update to MJ7, and finally to MK2 (the most recent). Safe rooting methods for each of these builds are different but readily available if you look in the Verizon Galaxy S4 forums. Recently, Hashcode has provided the community with the only recovery for MJ7 and MK2 - Safestrap. When you say unlock I'm guessing you mean the bootloader which is still locked - and a difficult nut to crack although there are some very smart guys working on it. I recently got my GS4 and am currently on MK2 rooted with safestrap installed. I don't see an advantage of ME7 to MJ7 or MK2 but others may feel differently. For a while ME7 and MI1 were the only builds that Safestrap worked on, but now that MJ7 and MK2 are safestrap compatible, there doesn't seem to be a disadvantage to the newer builds. Hope that helps sort it out a little. Cheers.
Click to expand...
Click to collapse
YEs thanks... I'll do some research on the newer builds. I really just wanted to know if there was one build that is best to be on and then root. I didn't want to update and find out rooting would be more difficult or have problems but likewise, I didn't want to root on ME7 and miss out on some added features in the newer builds.
If you guys had to pick the best build to be on for a balance of rooting and features, which would it be. For purposes of rooting, I'm OK with stock, I don't need a custom ROM. I just want to delete bloatware, run an ad blocker, wifi tether and Google Wallet (with NFC payments).
And yes, I meant an unlocked bootloader when I said unlocked. I know safestrap works, I just have always been on unlocked with a custom recovery where I could make backups. I felt way safer that way. I'm sure its fine, but safestrap is a new method I'm not yet comfortable with.
Thanks,
Jim
I think MJ7 would be best. I upgraded to MK2 and don't notice much difference (it was a small incremental update - still 4.3). The nice thing is that if you do manage to screw up MK2 or MJ7 you can always ODIN back to MJ7 and start fresh. MJ7 seems to be slightly better for flashing as you also have to flash the kernel module after each new rom and MJ7 has one on Hashcode's page whereas MK2's is "coming soon".
I have been using safestrap for over a year with my Razr prior to the SG4 - very stable and a huge help when you want to try multiple roms but not want the hassle of flashing back and forth between stock and custom roms. Just make sure you read all of Hashcode's instructions on using it.
He probably knows more about it than me I'm on MDK still.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
OK great. So if I do the OTA update Verizon is pushing, it will install each one individually so I can stop when I get to the one I want? It won't just go right to the most recent build?
Jim
calaski8123 said:
OK great. So if I do the OTA update Verizon is pushing, it will install each one individually so I can stop when I get to the one I want? It won't just go right to the most recent build?
Jim
Click to expand...
Click to collapse
Yes. Correct. That one I do know!
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Ok I updated to MJ7. I'm getting this shield notification now that says it detected unauthorized access to a secured area. I searched and found this is an annoying issue that only seems to be fixed with a factory reset... ugh WTF? ! ? Samsung and Verizon are really starting to blow.
If I try and update this security thing it's it going to prevent me from rooting?
Any other way to stop it besides a factory reset?
Thanks,
Jim
calaski8123 said:
Ok I updated to MJ7. I'm getting this shield notification now that says it detected unauthorized access to a secured area. I searched and found this is an annoying issue that only seems to be fixed with a factory reset... ugh WTF? ! ? Samsung and Verizon are really starting to blow.
If I try and update this security thing it's it going to prevent me from rooting?
Any other way to stop it besides a factory reset?
Thanks,
Jim
Click to expand...
Click to collapse
That's Knox. On the initial MJ7 build, it was raising that issue whenever you went from one WiFi access point to another.
If you allow it to update the policy, that defect goes away.
No need to factory reset.
If you root your phone, allow SuperSU to disable Knox and the problem will go away.
I just rooted my SG4 MK2 and that Knox thing showed up on my supersu access. It scared the crap out of me because I thought I was tripping it and on my way to hard bricking my phone. Thanks k1mu. I just hit disable and the shield went away.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Related
I was rooted with custom recovery on MDK. I decided to restore my Stock rooted backup so I could take OTA path to MJ7.
I’m currently on MI1 waiting to update to MJ7 and noticed the Samsung Custom boot logo. Device Status says “Custom”. I’m no longer rooted, no more custom recovery due to the ME7 and MI1 OTA updates. How should I proceed?
I’m worried about tripping the Knox fuse and I know there’s no going back. Does it matter? Will the MJ7 update overwrite this status? Or do I need to take care of it on MI1 before moving forward to MJ7?
EDIT: While on MI1, I used the ODIN files to go completely back to stock MI1. This returned the Device Status to "Official" and the boot logo returned to normal. This link is for the ODIN files with instructions: (http://forum.xda-developers.com/showthread.php?t=2301259).
Screenshots, for reference.
You could try the [root] triangle away app. I would read through the thread 1st....http://forum.xda-developers.com/showthread.php?t=1494114
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
^^^ what he said. Odin and start fresh. Although it does seem like a shame to see a MDK device getting updated and locked down but hey it's not my device.
Normally reading the first two sentences of this post would have been the most disheartening thing to see in a S4 forum, luckily or unlucky today it comes in second only to garwyn just closing the dev thread about coming up with ideas for unlocking the bootloader, and it happening so shortly and randomly after my post here, which I consider the most significant public progress we've made in unlocking this bootloader, because its the only public progress I've seen since we were gifted with loki.
majeiks said:
The straightforward approach might be just to ODIN back to stock MI1 and go from there. Will that solve the problem?
(http://forum.xda-developers.com/showthread.php?t=2301259)
Click to expand...
Click to collapse
Confirmed. This did the trick. Device Status says "Official" and the boot logo returned to normal. Will update OP with solution.
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
cell128 said:
I'm on mdk lokied. I rather wait someone will surely make a stock rooted 4.3 or use it as a base for their rom..give it a week and it will be worth it. We probably won't get kitkat here for a long time and especially if your locked down.
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
MJ7
matt1733 said:
yes patience is the way to go give it a little time if nothing develops then you can always go to a locked down device I upgraded my wife's phone and trust me the improvements are things we already had like the wi fi notification thing and the e911 icon being removed. I flashed the radio for the 4.3 update which is the most important thing anyways so I'm gonna hang in a little longer and see what roms pop up..
Click to expand...
Click to collapse
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Runamok said:
I was running Hyperdrive 9.1 on Safestrap on my I545. One day there must've been a pocket dial because I pulled it out and it said there were too many password attempts and I needed the recovery password or there would be a factory reset and data would be wiped. So I Safestrapped into stock, (ME7), but I never liked ME7, so decided to go back to unrooted stock and upgrade to MJ7.
Bottom line, so far I love it. It runs significantly smoother, faster, and with less bugs than the other ROMs I've tried. I'm not a developer and I understand the passion some have for custom options, but at the end of the day, if stock updates make improvements and eliminate most of the bugs, then it's a whole lot easier. I'm liking MJ7 on my phone.
Click to expand...
Click to collapse
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
http://forums.androidcentral.com/ve...xy-s4-security-notice-after-update-4-3-a.html
Knox security warnings - No biggie
azraell33 said:
Are you getting the security warnings yet? A friend has stock MJ7 and has been getting security warnings. He asked me to take a look at it . after about 3 seconds of googleing I found the answer. Its a known bug in MJ7.
Thank you for pointing this out. I checked into it and I doubt it's a bug. I DID get the security warning the next morning after install, which coincided with the timing of your message. My reaction to it was to simply agree to getting the security updates. I have not had any problems since, and my phone is running fine. I tried multiple ROMs while I had Safestrap on my phone, and MJ7 is performing as well as any of them. The caveat is that I'm not able to make as many mods to phone features, but to be honest, a lot of the mods were superficial tweaks that I didn't really use that much on a regular basis.
I APPRECIATE what developers have done to spur Verizon and Samsung into fixing the problems with the earlier versions of the software. Obviously, I was unhappy enough to attempt altering the firmware and risk losing warranty service. Having said that, I've come to a place where the time and effort it takes to act as my own customer service agent isn't serving me well. When I started having problems with my custom ROM and realized there had been not one, but TWO Verizon updates in the space of 3-4 months, I made a choice to accept the good with the bad and go the route of accepting updates in one easy click, instead of expending the energy it takes to be my own R&D and customer service department. .
MJ7 is running fine. Energy efficiency seems very good. Stability appears solid. Response time and hangups appear to be all but eliminated. Those were the reasons I tried a custom ROM, energy efficiency, stability and performance. MJ7 seems to have addressed those reasonably well.
A big THANK YOU to developers who had an influence in nudging Verizon into action. Security will continue to be a looming issue, and hopefully it will not quash the creativity of brilliant independent thought.
Click to expand...
Click to collapse
After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
budding_developer said:
After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
Click to expand...
Click to collapse
Hashcode hasn't gotten Safestrap running on MJ7 yet. It may be a while before he's able to find a way around the new enforcement in MJ7. There's some chance it may not be possible.
k1mu said:
Hashcode hasn't gotten Safestrap running on MJ7 yet. It may be a while before he's able to find a way around the new enforcement in MJ7. There's some chance it may not be possible.
Click to expand...
Click to collapse
Yeah, I have found that out... and soft-bricked it twice trying to disable selinux. Verizon sent me a replacement, which was on ME7 out of the box; flashed MI1, Root de la Vega, got back to my set up and locked out updates by uninstalling FWUpgrade.apk and SDM.apk in Titanium.
I guess I'll just stay where I am until the devs figure a way around the selinux thing -- that's what is keeping everyone out.
Verizon is Big Red alright! ! (communist)
budding_developer said:
Yeah, I have found that out... and soft-bricked it twice trying to disable selinux. Verizon sent me a replacement, which was on ME7 out of the box; flashed MI1, Root de la Vega, got back to my set up and locked out updates by uninstalling FWUpgrade.apk and SDM.apk in Titanium.
I guess I'll just stay where I am until the devs figure a way around the selinux thing -- that's what is keeping everyone out.
Click to expand...
Click to collapse
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
theslowhand said:
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
Click to expand...
Click to collapse
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
mmuzzy said:
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
Click to expand...
Click to collapse
I don't think its right to dicker something up then return it, BUT one could say that if they wouldn't have locked the bootloader this wouldn't be a problem and its there own dam fault and serves them right. I am not going deny I have been considering throwing mine under the car tire and returning it in hopes I will get a MDK version, but I pay for insurance that covers that kind of thing. Besides with my luck I would get a reman that had 4.3 on it and would be doubly screwed.
mmuzzy said:
I'm going to play devil's advocate here for a sec. The previous post talked about how he goofed up his phone, which he should have known was a possibility any time you flash your phone or try to modify it, and then made Verizon pay for his actions by exchanging it. So while I think it sucks that we can't easily flash recoveries and ROMs on our phones, I also think I see one possible reason why they feel the need to clamp them down.
Click to expand...
Click to collapse
azraell33 said:
I don't think its right to dicker something up then return it, BUT one could say that if they wouldn't have locked the bootloader this wouldn't be a problem and its there own dam fault and serves them right. I am not going deny I have been considering throwing mine under the car tire and returning it in hopes I will get a MDK version, but I pay for insurance that covers that kind of thing. Besides with my luck I would get a reman that had 4.3 on it and would be doubly screwed.
Click to expand...
Click to collapse
I agree with mmuzzy. Got to eat it your self when you take the risk. Seems like everyone knows how Verizon is operating trying to lock down these flagship phones so everyone knew it going in so To speak.
So if you screw it up I'd have to say you gotta do what's right and eat your mistake regardless of Verizons reasons for locking down the phone...
Sent from my SCH-I545 using xda app-developers app
Cure for the Communist problem...
theslowhand said:
Verizon goes way too far taking away our liberty with OUR OWN PROPERTY!
What's the nexy best carrier for Eastern NorthCarolina?
Verizon is just COMMUNIST!
Click to expand...
Click to collapse
Check out this post I put up. I am now on AT&T (GSM USA) with the same S4, cut my phone bill in half, and have a kick-a*s custom ROM. Here's the thread I put up as a guide on how to do this --> http://forum.xda-developers.com/showthread.php?p=47328895#post47328895
Mj7 calls for safestrap 3.70 or preferred 3.71
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
budding_developer said:
After successfully rooting my Verizon/ Galaxy S4 on MI1 and then following the recent tutorial at http://forum.xda-developers.com/showthread.php?t=2504408 I have not been able to get Safestrap v3.6x to successfully install recovery.
Apparently, the OTA upgrade from Verizon now has SELinux enabled and enforcing a pre-defined Samsung security policy that blocks Safestrap every time it attempts to install recovery. I have searched but have not found any mention on the web or on HashCode's site about how to get around that and be able to successfully install recovery.
Can anyone point me to a work-around for this?
Click to expand...
Click to collapse
Must use Safestrap 3.70 or 3.71 (recommended) for mj7 I have used both but 3.71 is supposed to be strictly for mj7 and mk2
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 7 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
VRUFNC2 ("NC2")
VRUFNC5 ("NC5")
There's another release that was apparently a leak or limited release, MG7.
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on. The best way to tell what bootloader you have is to install an app - "Phone INFO *Samsung*" and "Phone info" will both tell you what build and bootloader you have.
The "Developer Edition" devices have "I545OYUA" build numbers versus the consumer versions, which start with I545VR.
Once you're on a particular build, it is not possible to downgrade to an earlier release. The single exception to this is that you can flash MJ7 over MK2, but that's it.
If you're past MDK, you can't bypass the bootloader until an exploit is found.
If you start flashing things without verifying that it's for the release on YOUR phone, you risk bricking it. There's dozens of youtube videos telling you how to flash custom recovery on your phone that WILL NOT WORK unless you're on the MDK bootloader. Be sure to comment in the youtube thread after they assist you with bricking your phone.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
For NC2 and NC5, you can't currrently root unless you downgrade the baseband to MK2.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recovery will not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
k1mu said:
I posted this hoping it would become a sticky.
Moderators: any chance? Or is this unacceptable since it's not a question?
Click to expand...
Click to collapse
this really needs to be a sticky as we all know how many aren't taking the time to more than a cursory check in these threads
---------- Post added at 06:16 AM ---------- Previous post was at 06:09 AM ----------
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is the original MDK baseband. Not checking first before flashing will often break your phone.
If you need to know what baseband you're on, use "Settings", "More", "About phone" and scroll down to the "Baseband Version".
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're on the MDK baseband. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
k1mu, I also created a step by step guide (with links) that walks you thru the entire process of going from ME7/MI1 to MJ7 by flashing the wipe tar image of MJ7, installing your saferoot, safestrap and HD11
http://forum.xda-developers.com/showthread.php?t=2579278
I was feeling pretty bad for all the people that were messing up their phone becasue od not understanding the entire process.
Props to you both ! The only thing I would emphasize for MDK users is to get yourself educated (plenty of threads) on the Loki process. The proper use of it when flashing unfamiliar recoveries or kernels can save alot of headaches (trust me I know !!)
Bumping
Sent from my SCH-I545 using XDA Premium 4 mobile app
MJ7
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
sixtythreechevy said:
Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
Click to expand...
Click to collapse
nope updating modem changes what your baseband version says.
For those who are unsure if you can install the custom recovery:
The BUILD must be MDK not the MODEM. If you are running different build you can flash different modems. Just because you have the MDK modem does not mean you can flash a custom recovery.
Yeah you can flash any baseband at any time you like...that's your radio/modem. You can also flash a new build as long as your bootloader remains on MDK. For example, I'm running a stock MJ7 ROM but I'm still Loki'd on the MDK bootloader.
Sent from my SCH-I545 using Tapatalk
ok heres my issue
Delete
What really matters here is what Bootloader you're running. Since updating the modem changes the Baseband string, that can't be used to tell if a phone is locked. I've updated the OP to say Bootloader version and to explain how to get to the Bootloader version.
FordNate said:
I'm MDK on the GS4 and believe me i knew about the whole Verizon/At&t/TMO long time ago (smarter than the average near and able to laugh at people when they do do things like that) ok so my issue i tried updating my recovery earlier to philz 6.08 from just CWM 6.0.44 (?). It soft bricked my phone. I just spent 7 hours getting it back to operational order. I tried everything under the sun, u name it i probably did it, but i kept with Verizon packages only. Trying to find a stock image of MDK is impossible to say the least. Good news though. its up and running again only issue i lost root
Root the first time was simple and maybe took 20 minutes. Now i cant get motochopper or any other exploit to to work. Phone "see's" that a program is trying to get access but does not allow me to accept it, only offers to reboot now or later. Help a man out here.. I'm still on mdk just cant get root back. yes i check usb debug even toggled it a couple times. Verify apps unchecked and unknown checked.. Dang Stock is not good.
Click to expand...
Click to collapse
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
tkacer said:
Have you tried this: http://forum.xda-developers.com/showthread.php?t=2301720
Click to expand...
Click to collapse
yes and got it running again with root
Happy 4 ya - nothing worse than a borked phone !!!!
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
dbinnc said:
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?
ANy help appreciated.
THanks,
Derek
:crying:
Click to expand...
Click to collapse
Install the MK2 no-wipe from here.
I want to bump this thread so we can use the OP as a starting point for a stickie guide concerning verizon S4 and what you need to know for modding your phone.
Naddict will be assisting in getting the sticky set up. This will be a WIP and will NOT be a thread to post questions. Lets get all our smart people contributing with info and links as needed to help all those who wish to mod their phone from not repeating all the same errors and bricking.
k1mu said:
The number one reason people brick their Verizon Galaxy S4 phones is due to attempts to flash recovery using Goo Manager, dd, and other tools without understanding when those will or won't work. The Verizon S4 is very locked down, and will reject such attempts in most cases.
The only Verizon Galaxy S4 release that permits a custom recovery is a phone with the original MDK bootloader. Not checking first to tell what's installed before flashing will often break your phone.
1. What releases are there, and how can you tell what you have?
There are currently 5 different releases of the firmware for the I545.
VRUAMDK (Usually called just "MDK")
VRUAME7 ("ME7")
VRUDMI1 ("MI1")
VRUEMJ7 ("MJ7")
VRUEMK2 ("MK2")
You've got to know what bootloader and firmware you have installed before you do anything. The bootloader is the critical thing, but unless you're using a MDK bootloader, chances are that the bootloader on your phone is the same as the build version. To figure out what you're running, use the "Settings", "More", "About phone" menu. In most cases, the "Baseband version" displayed and the "Build number" will be the same, which tells you what build you're on.
If you start flashing things without verifying that it's for YOUR phone, you risk bricking it.
If you need to tell for sure what bootloader you're on, you can use applications like "Android System Info" (Open the "System" tab and the "Buildinfos" and look for Bootloader), or from a shell by using the command "getprop ro.bootloader". Use either adb shell or the "Terminal Emulator" app to do that.
2. What can you do with your phone?
Rooting:
For MDK, root using this link. or this link.
For ME7, root using this link.
For MI1, root using this link.
For MJ7 and MK2, root using this link.
If you want to install a custom recovery, you MUST have the MDK bootloader. Follow the MDK link above.
If the bootloader isn't "I545VRUAMDK" you have a locked bootloader and can only use Safestrap to install custom ROMs. Custom recovery is not possible. Attempts to install custom recovery will soft-brick your phone and require you to re-flash a stock ROM.
Information on Safestrap is available in this thread.
Recover by re-flashing stock
For MDK, Follow this link.
For ME7,Follow this link.
For MI1, Follow this link.
For MJ7, there's a no-wipe and a full wipe image.
For MK2, Follow this link.
Flash new Modems
The firmware that runs the phone's radios, which allows you to connect to the networks (CDMA, LTE, WiFi, Bluetooth) can be updated independently of the bootloader. Flashing the MJ7 modem can get you new LTE bands, for example. Read here for information on available modems.
3. What to avoid
Every carrier's version of the Galaxy S4 is different. Things that work for the Sprint, AT&T, T-Mobile, and other carriers phones may not work on the Verizon version and can lead to bricking your phone. Don't do things just because it works on the T-mo, AT&T, or sprint phones unless you don't care if your phone is rendered useless.
Regardless of what you read, recommendations to use Goo Manager to flash custom recoverywill not work and will soft brick your phone unless you're running the MDK bootloader. Don't do that.
If you manage to do the wrong thing and soft-brick your phone, search the Android Development forum for a factory image that can be flashed to recover it based on what baseband you started with.
For example, this image for MJ7 (Android 4.3).
Click to expand...
Click to collapse
Excellent! Thank you!
Developers edition bootlader
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
kerryh420 said:
Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)
Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.
Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
Click to expand...
Click to collapse
I'm pretty sure you'll need to root first. Also I'm not sure standard twrp is what you need for the Dev edition. They are lokied and I don't believe you have a need for that. That being sailing not exactly sure what your process for rooting will be or which recovery you need.
Maybe this thread will give you some insight.
http://forum.xda-developers.com/showthread.php?t=2339849
Then research about flashing roms on the Dev. Edition. It will be different for you.
Sent from my SCH-I545 using XDA Premium 4 mobile app
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
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
uniroot said:
New member here. Bear with me, please, for possible n00b questions.
I'm not new to rooting & ROM'ing. I've been rooting and ROM'ing for years, but I haven't done much in a while due to excessive work schedule and family obligations. But I'm looking to get back into it.
I've had my VZW S4 for about 9 months. I'm rooted, but running stock ROM.
Phone: i545
Android: 4.2.2
Baseband: I545VRUAME7
Kernal: 3.4.0-690088
Build Number: ...ME7
As I said, I've got lots of experience with rooting and ROMs. I flashed my prior phone easily over 100x experimenting with different ROMs. But since I'm going from 4.2.2 to 4.4.2, I think I better ask regarding my strategy to be sure I don't end up with a brick.
My general plan is to: update my phone to 4.4.2 via OTA update, root, flash recovery, then experiment with various ROMs. Specifically, these are the steps I'm setup to follow:
Back up everything (App's, contacts, bookmarks, SMS, etc.) via Titanium -- actually, I've already done this
Perform factory reset in its current state (4.2.2)
Accept OTA 4.4.2 upgrade from VZW ==> I assume this will revert phone back to UNroot status??
Re-root via Towelroot
Download SuperSU
(Remove KNOX??)
Install recovery
Install ROM
Questions:
I've read about Samsung KNOX. If KNOX is "triggered", Samsung won't honor the warranty. But I don't care about the warranty at this point, so is the whole KNOX thing a moot point for me?
Anything else I should be aware of? Any experienced users of S4 that see an obvious gap in the above plan, I would be much appreciated in hearing your advice.
For what it's worth, I've been studying the following YouTube video for what lies ahead.
"CyanogenMod 11 (CM11) on the Samsung Galaxy S4! (Install, Setup, First Look, and etc)"
Click to expand...
Click to collapse
1. DO NOT TAKE THE OTA
2. read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick.
Sent from my SCH-I545 using XDA Free mobile app
I've been researching this for a couple of days, and obviously I'm missing some details.
Why not take the OTA for 4.4.x? What am I missing? What's the issue?
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
uniroot said:
Doing some more research this morning...
When you say: "read the forums regarding what your options for recovery. Don't try to flash cyanogenmod or you'll end up with a brick."
I read from another post: loki allows you to install whatever you want, not just Touchwiz-based ROMs. If you want to install CM, you've got to use Loki.
So I need to perform the loki hack first, right? If I install CM without the loki hack, I will brick my phone?
Click to expand...
Click to collapse
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
joshm.1219 said:
Loki only works on MDK, the firmware version before me7. everything after MDK can only run safestrap. Can't downgrade.
You can use the OTA but it will fail if your system is modified at all. If you know all modifications you've done and can remove them, go ahead. If not, use the NC5 tar file in Odin to upgrade.
Click to expand...
Click to collapse
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
uniroot said:
Excellent, thank you for providing this info! I'll look into Odin.
For clarification...I have performed certain "modifications" since I've owned the phone. If I perform a factory reset on it in its current state, does that not remove/reset all of the mods I've done??
Click to expand...
Click to collapse
It should, but not always. Also you have to use the unroot from the supersu app.
---------- Post added at 01:27 PM ---------- Previous post was at 01:27 PM ----------
Oh and the tar files are here: http://forum.xda-developers.com/showthread.php?t=2735172
I recommend using Odin 3.09
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
uniroot said:
You're saying I will need to un-root prior to performing the NC5 Odin?
Do I need to worry about changing/updating my old ME7 build before the NC5 Odin?
Click to expand...
Click to collapse
No, you only need the unroot if you try the OTA. Nothing else needs to be done to use the tar file with Odin, but I would recommend backing up important data to an external SD and flashing the full wipe file to ensure you have a clean system.
Latest OTA "patches" TowelRoot
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
~JohnnyB~ said:
I've read recently I've read that the OTA will fix the vulnerability that TowelRoot exploits to gain root. But most if not all of the articles were specific to the S5. It is possible that taking the OTA will patch the same vulnerability and remove root again. It's been a long time since I've had to work this hard to root/ROM anything...so I'm not sure if I'm correct or not, but it's something to consider before taking the OTA...if you haven't already.
Click to expand...
Click to collapse
Towelroot works on NC5, the latest OTA for this device. Towelroot came well after the OTA. If we get another firmware update, I'm sure it will patch towelroot.