[Guide] OTA & ROOT GUIDE

pltctytc said:

i'm guessing there are those out there that wet themselves getting the newest update.

i'm also guessing that KK isn't worth the trouble of updating, rooting, and if all your data is lost, reinstalling all your email accounts and software, settings, etc.

i've updated KK last year on a moto and really nothing in the KK update worth the possible disaster. past experience w/ verizon and any of their late and lame updates have more potential for screwing up your phone

Click to expand...

Click to collapse

You are 100% wrong. The leak for KK is especially exciting for VZW Note 3 users as it is still SElinux permissive AND allows for kernel modules to be loaded. I would avoid the official OTA to KK like the plague. But as for jumping onto the KK leak.. it might be the single most exciting thing to have happened to stock ROMs in recent history.

chefb said:

so basically this is the end of the line for the note3...the s5 is not rooted? and they totally locked down the galaxy line?

Click to expand...

Click to collapse

I wouldn't take such a bleak outlook as that. First and foremost we need to remember that the culprit here is Verizon...Samsung devices on T-Mobile & Sprint have unlockable bootloaders so it's certainly not the manufacturer - it's clearly the carrier. Yes, Samsung is responsible for Knox, which is a pain, but we've proven in our own device's case how that isn't too big a stumbling block to overcome. If we had an unlocked bootloader Knox would be a fly to swat out of our way on the path to complete and total freedom to mod whatever we'd like. It's only because of the locked bootloader that we are stuck using EXTREMELY bright people like @Hashcode, @designgears, @BeansTown106, @bajasur, @Chainfire etc. to create mind-bending work-arounds for these complicated and enterprise-level security systems.

What I would say is that the latest word out of Google with their acquisition of a company called Divide, which specializes in enterprise security and the like, is that the need for something like Knox is diminishing on a device manufacturer basis. I do have some severe doubts as to whether Samsung would disband their new corporate security blanket, but if Divide has software that does what it says it does on every android device out of the box there may be redundancy issues having both that & Knox running at the same time. I have a feeling Google will win should there be a conflict and Samsung will then drop Knox & use Divide.

This still doesn't solve the bootloader & root issue some are facing, I realize. The unfortunate truth about that is that some carriers, Verizon especially, have taken a stand that unlocked bootloaders aren't worth their trouble and decided to offer "developer editions" which carry no risk to them and they don't have to subsidize. I understand their decision being a business manager/owner myself, but I, of course, understand the frustration as a user and the true owner of the device.

To directly talk to your point - No, this isn't he end of the line for the Note 3 or any galaxy device. Just look at what Kingo was able to do with being able to root our previous builds. There's a chance they or someone else will figure out how to root NC4 and possibly many more builds going forward on many more devices. There's also the potential for further leaked builds like our NC2 which is a wide open playground of potential in an otherwise maximum security prison that is Verizon. And the fact that Kingo, VRoot & others aren't somebody like us posting our stuff on XDA for the whole world to see (open source), then the root exploit is drastically less likely to be patched by Verizon. Ultimately, I don't like trusting the root process to somebody without a face and without access to their code in an open source way, but that may be the final frontier of smartphone rooting - that we must mask our path to victory so the evil Big Red don't follow our breadcrumbs and trap us in a no-root prison.

The true way to stop this bullying by Verizon is the old "talk with your wallet" technique where we don't buy devices with a locked bootloader. The problem is Verizon has a perfect fallback for all those people. They'll say, "Sure you can root (assuming someone figures out a way) & do all that stuff - just buy our developer edition! Sure, it will be a ton more money but that's the cost of being an evil rooting hacker!" And since that's not what we want - we want our subsidies and the ability to treat it like our own personal hardware - we are at an impasse. For many people the only choice for decent network is Verizon (that's me) so for me and a lot of other people, we can't take a stand and choose the provider that offers unlockable bootloaders and subsidies, so we're forced to deal with Verizon's shenanigans. It sucks, it really does...but we're stuck...that is, until T-Mobile or Sprint pick up their game and provide a network with even a fraction as much coverage and speed as Verizon...but that's, in my opinion, something that's years off, if ever.

Nidisa said:

Does this method work IF:

I am rooted via root de la vega, running latest safestrap, beans v2 on Rom slot 1.
Baseband ver MI9
Build number MJ7

Would I have to uninstall anything to use your instructions OP?
Would I need to switch in safestrap to stock slot before beginning process?

Honestly haven't had a lick of trouble being on M19 baseband, but maybe I'm on borrowed time?

Click to expand...

Click to collapse

If you're already on build MJ7 then I'd just Odin the MJ7 baseband over in beans thread here: http://xdaforums.com/showthread.php?t=2524572 No need to do this which will lose you root.

Transmission courtesy of my Note 3 & XDA Premium

Nooooo. Apple is ddosing

Sent from my SM-N900V using Tapatalk