Related
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
I used this & it worked for me. Easy & quick: http://forum.xda-developers.com/showthread.php?t=2219803
I used the method mentioned above. Seemed to work perfectly. Very easy too.
Sent from my SPH-L720 using Tapatalk 2
Is the bootloader locked or unlocked on the Sprint version ?
Doesn't it have to be unlocked since they are reporting success rooting it?
mysongranhills said:
Doesn't it have to be unlocked since they are reporting success rooting it?
Click to expand...
Click to collapse
These threads are a bit confusing and i want to make sure before i decide to get one
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Wow thats crazy flashing something to your phone that isn't made for it.
opz187 said:
No one really knows if the bootloader is locked or not. Some are able to obtain root, but when flashing certain things, bricked their s4. One dude tried flashing stock and bricked. So I wouldn't get too crazy yet until a dev or someone who knows what they're doing figures out exactly what's going on.
Click to expand...
Click to collapse
We have a Stock (dump) build, which will be made available later today that flashes just fine.
If you're following the Engadget bootloader thread, i posted this earlier today..
http://forum.xda-developers.com/showpost.php?p=40844084&postcount=141
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
With regards to the boot methods - we have found something interesting.
@crawrj Had used the Moto root method and couldn't use Solid Explorer properly (i.e. couldn't open init.rc to view, copy system files, etc)
He then used the CF autoroot method and functionality came back.
While not specific enough to point at anything (we don't have logs to look at) I would advise you to check your apps that need root to make sure they function properly.
Just FYI.
I used the AT&T root method and worked fine for me only took 20 seconds.
http://forum.xda-developers.com/showthread.php?t=2252248
Just follow the steps and you will be rooted.
Sent from my SPH-L720 using xda premium
---------- Post added at 09:43 AM ---------- Previous post was at 09:42 AM ----------
Pheonix28 said:
This method worked and was painless.
http://forum.xda-developers.com/showthread.php?t=2252248
Click to expand...
Click to collapse
Sorry didn't see this post.
Sent from my SPH-L720 using xda premium
benny3 said:
Is the bootloader locked or unlocked on the Sprint version ?
Click to expand...
Click to collapse
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Shadow_God said:
The write protection is enabled in odin mode....don't know what that means as I haven't dived in yet :thumbup:
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
I have the HTC ONE and it has the Write Protection enabled also. We have a work around that can be flash through recovery, Not sure how you would implement it with Odin but here is the Link, Maybe you can look at it and may help
http://forum.xda-developers.com/showthread.php?t=2236849
JasonJoel said:
I admit it, I'm confused by the various different rooting threads at this point.
Which root method is the right one for the Sprint model?
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Motochopper, featured in you tube (http://www.youtube.com/watch?v=6fi1tYaoP0U) or (http://www.youtube.com/watch?v=GrvrXXFb2Uo) and be sure to Download the Drivers from the samsung website. For some reason, the drivers within XDA didn't work for me. Once I D/Ld the one specifically for Sprint, motochopper was able to communicate w/my s4 and rooted it:good:
I've not tried the motochopper stuff so I can't speak for that.
I can confirm that I had success the first time with no driver download needed when I used the CF auto-root method. I simply plugged the phone in, let Win7 download the drivers. I then put it in recovery mode (vol down, home and power button, release power button) and once win7 downloaded those (MHT etc) drivers I loaded the file through pda in odin and it went right through with no problems whatsoever.
The CF auto-root thread is here:
http://forum.xda-developers.com/showthread.php?p=39901375
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Unknownforce said:
I would suggest waiting until we figure out just what WRITE PROECTION: ENABLED means on the download screen.
Keep in mind that obtaining Root and bootloader lock status are two completely separate things. Typically, the bootloader being locked doesn't affect the ability to OBTAIN Root. But it will block certain partitions of the device being flashed, if it's indeed locked. And it can also affect the root from being permanent or not. (sticking after a reboot)
Root is an android system thing. An operating system thing. Bootloader is a low level boot thing, before android itself is even initialized. Think of it like the BIOS on a PC, it's the screen you see before you get to windows or linux or whatever operating system you're running.
It's sounding like they are having success with writing to many of the partitions that are ordinarily blocked by a locked bootloader. So it's sounding like the WRITE PROTECTION: ENABLED doesn't actually indicate whether or not the bootloader is locked. But we don't know that for sure yet. It's too early to tell.
Click to expand...
Click to collapse
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
k2buckley said:
If unknownforce tells me to wait, I wait. I trust his advice quite a bit, after seeing what he is capable of in the evo3d section.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
There is nothing wrong with staying with what you know.
Once we get a complete package, which may not be too far in the near future, we'll know more.
---------- Post added at 06:26 PM ---------- Previous post was at 06:23 PM ----------
crawrj said:
Our phone is not locked, at least not in the way we know it. We have flashed kernels, recovery and the system partition from Odin. CF Auto root is the best method of Root IMO. Although both rooting options install and stick. But as MoHoGalore stated I had trouble with an app that required root access using the Moto method. I switched to the CF method and everything was working perfectly. We have no idea what the Write Protection means yet but so far it has not inhibited us in any way.
Click to expand...
Click to collapse
I can attest to this and I'm still functional.
But, for the masses, there are a few of us willing to try if you want to wait.
Here's hoping we know more very soon. :beer:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
Questions should be in Q & A. That's what its there for.
Buying a 900V is a big mistake if your not on Verizon. No, you cannot flash N9005 roms on this device. Your best bet would be installing one of the roms in the development section here. http://forum.xda-developers.com/verizon-galaxy-note-3/development
lidor578 said:
hello there
i did a mistake and buy note 3 n900v
my rom is based on mje
and my device is very slow and the tw luncher is not smooth like n9005 even that they share the same cpu and gpu
i want to change my rom to one is clean from everyrhing from verizon (like apps and bootanimation)
i have root access and i dont want to brick my device
can i install n9005 rom?
someone can help me please ?
Click to expand...
Click to collapse
how do you rooted your mje n990v? i can't
huess113 said:
how do you rooted your mje n990v? i can't
Click to expand...
Click to collapse
Kingo... worked on mine
shiftr182 said:
Kingo... worked on mine
Click to expand...
Click to collapse
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
rkmFL said:
I don't know if there is a scamware version of Kingo going around or something, but I've never been able to get it to work.
I can use ADB without any problems on my SM-N900V. I then run Kingo and it does nothing, just sits there "waiting" for the devices. Windows Firewall disabled, No AV software, Trying Kingo w/Admin permissions and without. Nothing works.
After wasting hours with this, I finally decided I'd try a vanilla Windows 8 install, nothing on it but Kingo. Still didn't work.
Brought my phone back to my PC, ADB works just fine -- tried Kingo again -- nothing.
...On a related note...
After searching the forums for some time, there is one question I just can't determine definitively:
Can the SM-N900V (Verizon Galaxy Note 3) be truly "unlocked" with a custom recover (or) are we still limited to Safestrap options?
Thank you in advance,
RKM
Click to expand...
Click to collapse
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
In regard to the recovery, if you have a retail Note 3 from Verizon you will brick it if you flash a recovery other than safestrap. The bootloader will recognize the recovery is not stock, your knox will void you warranty and the phone will not boot. The only available recovery option for retail is safestrap.
shiftr182 said:
I had the same problem with Kingo initially. I don't remember how I fixed it, but it was a simple fix.... something stupid. Now it works with no problem.
Click to expand...
Click to collapse
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
Any luck with vroot?
I wish you could recall the "something simple" to make Kingo work. Where can I get "Safestrap?"
I just got a Verizon SM-900V with MJE yesterday. I need root to be able to use ARUnchained with my AppRadio 2. I tried Kingo, and it just kept switching between "connecting" and "downloading drivers" it never would connect to the phone. At this point, I'm not to concerned about custom ROMs, nor am I concerned about voiding the warranty. I just need to be able to obtain ROOT without bricking my phone. All of the threads on successful rooting of this device are from around November of last year. So, is there a way to successfully root any more? Thanks in advance!
please help.. I have 900v upgraded to 5.0.1....lost pics and voice recorded files...
please help with my note 3
rkmFL said:
I've tried all of the crazy suggestions that people have claimed will make it work. Setting screen timeout to 10 minutes, allowing untrusted & disabling app inspection, everything.
I can even use ADB directly from the Kingo directory, no problem.
And here's the real kicker .. if I delete the token allowing ADB access to my phone, Kingo will not trigger the phone to prompt for one. So Kingo is *not* even attempting to run ADB.
Not to mention, if you look at the logs, the entire time Kingo is communicating with Chinese servers. Sure, it might not be doing anything to root the phone, but that's not going to stop them from sending loads of data to China in the process.
At this point I think I think I'm best to chalk up the 12+ wasted hours on Kingo and give vRoot a try. What a nightmare, I've never had such a bad experience with an Android tool, whether it be for S-OFF, Rooting, etc.
Click to expand...
Click to collapse
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
ryujeff said:
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
Click to expand...
Click to collapse
We do not have root for NB1 as of right now.
We have no idea how long it will take, and asking for an ETA is rude.
Other Kitkat devices have been rooted.
Simple search could tell ya bro.
Live long and prosper...
ryujeff said:
When will the root for NB1 be out? i know that the developers are still working on it, but i just want to know how long will it take. cause i cant wait to do awesome things with the new firmware!!! Did any other kitkat devices succeed to root? like Nexus 5? I should switch to T mobile. tired of this bootloader.
Click to expand...
Click to collapse
Root itself has nothing to do with the bootloader. In the future it will be harder for even unlocked devices to be rooted. Google is cracking down on root too. Unfortunately.
If you are not able to develop should not stop you from trying to find a root method yourself. It could very well be another root method works. After all the first root method for the i337 was made for Motorola phones.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
ryujeff said:
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
You are not really asking for an ETA and not really rude--:good:
It is just a question like who will win the lottery tomorrow--no one knows
There is a thread on the subject you can follow
I wouldn't hold my breath and if you "really" want root/custom roms may want to look at other phones, sorry to say--
ryujeff said:
Ok Im sorry for asking about root. Some people says that root won't be able. Just wanted to know. I was not trying to be rude, but well... it went wrong.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If my comment came across as rude. I apologize. I only meant for it to be helpful.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
CAG-man said:
Root itself has nothing to do with the bootloader. In the future it will be harder for even unlocked devices to be rooted. Google is cracking down on root too. Unfortunately.
If you are not able to develop should not stop you from trying to find a root method yourself. It could very well be another root method works. After all the first root method for the i337 was made for Motorola phones.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Wait, when Chainfire recently got international gs4's root method, Chainfire said that AT&T model cant be rooted due to it's locked bootloader.
Chainfire's CF auto root has not been able to work on the Galaxy S4's in the US because of the locked bootloader true. In my understanding of the method it requires access to the bootloader to inject the su binary. The S4 can be rooted, just not with the chain fire method. All the root methods so far have more or less been obtained through some sideloading. Pushing it off the sd card or off a computer through the adb interface. Therefore not needing to access the bootloader for fastboot to inject the su binary to gain access to the root user.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
CAG-man said:
Chainfire's CF auto root has not been able to work on the Galaxy S4's in the US because of the locked bootloader true. In my understanding of the method it requires access to the bootloader to inject the su binary. The S4 can be rooted, just not with the chain fire method. All the root methods so far have more or less been obtained through some sideloading. Pushing it off the sd card or off a computer through the adb interface. Therefore not needing to access the bootloader for fastboot to inject the su binary to gain access to the root user.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Rooting needs write access to the system partition and since bootloader locks the write access, we can only get temporary root.
So does that mean that sideloading enables us to access to the system partition without bootloader's restriction?
ryujeff said:
Rooting needs write access to the system partition and since bootloader locks the write access, we can only get temporary root.
So does that mean that sideloading enables us to access to the system partition without bootloader's restriction?
Click to expand...
Click to collapse
I don't know your experience level with Unix type systems. Excuse me if you have expereince. In a nutshell Android is built on top of Linux, a Unix type system like OSX and of course Unix. Unix type systems have a "master user" a "super user" named root. Root is the almighty powrful, and thus why it is common for access to it be restricted on Android. The root user can make any system level change. A user can access the root user by typing SU in the command line. This is because the SU binary exists.
The boot loader is pre-system. Its sole purpose and function is to load the operating system. In our case it is also making sure it only loads the approved operating system made by Samsung and ATT. A common bootloader in Linux is called GRUB. Some changes to the system can be made through GRUB. This is in effect what Chairfire does, uses the bootloader to make the changes. Our bootloader is locked so this method will not work. That however does not mean a change cannot be made in the Operating system itself. Why? Because once the bootloader is done, it's sole purpose in life is over until the next boot. An example is found in the check for custom software. When you restart your phone go to settings -about device - status as fast as you can. You will notice as the very bottom Device Status will read "Checking" which will be replaced by either official or custom after it is done. This is the post boot check samsung built in. This is done from the operating system and not the boot loader.
In the operating system there is the super user also known as root, administrators, and standard users. When we use Android we use it as a standard user. You can find the list of Administrators in settings - security - device adminstrators. On our device when root has been achieved in the past it was because a security hole had been found in the system more or less. A developer finds the hole and makes the way to place the SU binary in the system folder. Once there, we can access the root user, the system has been "rooted."
Because it is a give and take battle with the manufacturers, the hole that allowed the most recent root method will inevitably be patched. However in doing so another will inevitably be made. It could be possible that it was an old one. Thus it is good to check other methods that have been created for our device or other devices. It could be it is a new hole entirely and that a new method will be created. All of this does not need approval from the bootloader, because its purpose in life is just to check the OS and initiate it.
I hope that made sense. I tried to make it brief. If anyone see any errors feel free to correct it. I have a good concept, just may not have worded it right.
Sent from my GT-P5210 using XDA Premium HD app
CAG-man said:
I don't know your experience level with Unix type systems. Excuse me if you have expereince. In a nutshell Android is built on top of Linux, a Unix type system like OSX and of course Unix. Unix type systems have a "master user" a "super user" named root. Root is the almighty powrful, and thus why it is common for access to it be restricted on Android. The root user can make any system level change. A user can access the root user by typing SU in the command line. This is because the SU binary exists.
The boot loader is pre-system. Its sole purpose and function is to load the operating system. In our case it is also making sure it only loads the approved operating system made by Samsung and ATT. A common bootloader in Linux is called GRUB. SOme changes to the system can be made through GRUB. This is in effect what Chairfire does, uses the bootloader to make the changes. Ours is locked to his method will not work. That however does not mean a change cannot be made in the Operating system itself. Why? Because once the bootloader is done, it's sole purpose in life is over until the next boot. An example is found in the check for custom software. When you restart your phone go to settings -about device - status as fast as you can. You will notice as teh very bottom Device Status will read "Checking" which will be replaced by either official or custom after it is done. This is the post boot check samsung built in. This is done from teh operating system and not the boot loader.
In the operating system there is the super user also known as root, administrators, and standard users. When we use Android we use it as a standard user. You can find the list of Administrators in settings - security - device adminstrators. On our device when root has been achieved in teh past it was because a security hole had been found in the system more or less. A developer finds the hole and makes the way to place the SU binary in the system folder. Once there, we can access the root user, the system has been "rooted."
Because it is a give and take battle with the manufacturers the hole that allowed the most recent root method will inevitably be patched. However in doing so another wil inevitably be made. It could be possible that it was an old one. Thus it is good to check other methods that have been created for our device or other devices. It could be it is a new hole entirely that a new method will be created. All of this does not need approval from teh bootloader, because its purpose in life is just to check the OS and initiate it.
I hope that made sense. I tried to make it brief. If anyone see any errors feel free to correct it. I have a good concept, just may not have worded it right.
Sent from my GT-P5210 using XDA Premium HD app
Click to expand...
Click to collapse
so if the bootloader checks for an approved operating system made by Samsung and ATT would that be a hole needed to place the superuser binary in the system folder? I'm sorry if that sound noobish but your posting have got me curious but I do not posses the knowledge or software to do anything.
Yeah thanks for lengthy explanation. I know what GRUB and root is. Anyone using linux should know that. Now I understand a bit more.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
If Apple developers can keep coming up with ways to jailbreak the latest OS, I'm sure our talented Android developers will find a way. I have faith in them. :good:
Let's hope so. I like ATT for better coverage than TMO and less money than Verizon. And, want a Note4 on ATT.
Hello everyone,
My girlfriend was playing with her phone, and accidentally deleted almost 2,000 pictures from the ATT GalaxyS4, which of course were not backed up.
I tried looking for various data-recovery tools, but they all require a rooted phone. I tried to root it with the Kingo app, and using towelroot, but both failed. I am aware you can also do it downloading an older firmware, with the help of Odin, then using towelroot, then flashing with the NJ4 firmware again, since towelroot doesn't work on current version.. but I am afraid using this method will eliminate or overwrite any trace of the invisible "deleted" photos still left on the internal memory.
Does anyone have any suggestions / ideas on how to safely either root this phone, or restore the photos?
Appreciate any reply/info/help. I have spent hours looking into all this and am pretty new to it, all to no avail..
If nothing else is anyone familiar with any reputable paid data-recovery services out there? These photos are pretty important to us both so that is also an option we would look into.. just not sure how effective any of this is. Maybe send the phone to the CIA or NSA...
Thank you for any help.
Disk digger may be an option but I think it requires root. Odin will wipe the device so that's not an option
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Disk digger may be an option but I think it requires root. Odin will wipe the device so that's not an option
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yea, I looked into Disk Digger already, unfortunately it requires a root, which seems to be the case with almost all, if not all data-recovery programs for the phone. Not sure if there is any way to even do this without a root.. I have had no luck finding one.
Kingo has good reviews and claims to support most of the main phones, but I have had no luck with it, it just goes into a loop of downloading and waiting for device.
Thanks.
Anybody ever hear of a root called, "CC root gadget"?
Should come up in google, I can't post links yet. Couldn't find any info on it and didn't want to try it.. seems a bit shady.
I was concerned about Security with Kingroot so decided to try this. I'm on a RETAIL Verizon Note 4 running 4.4.4.
I did a factory restore then after setup, I DISABLED SDM, THEN I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot on the "Personal" side.
It worked. Root is, On Demand, temporary, And I think it is safer than using Kingroot without Knox.
I went into recovery to check but no Knox trip. I win!. I have two environments. One rooted the other as secure as you can get.
This is like having a dual boot on the fly. With this root you can at least use Adaway. You can get a lot done with it. This is the best root solution for the Retail Verizon Note 4. I am hoping to get developers interested.
O.K.,This is where I'm at. If someone could look at the pictures and tell me what I should add to the OP description, I'll do it. Look at the last two pictures, Knox would not let me take the screen shots because of security.
Check Out MOST ASKED QUESTIONS and Fixes in the next post.
MOST ASKED QUESTIONS
1. What phone is this for? Retail Verizon Note 4. This may also work on other un-rooted phones
2. What ROM are you on? 4.4.4 found HERE http://forum.xda-developers.com/not...w-to-roll-to-kk-4-4-4-lollipop-5-0-1-t3097054
3. How did you set up your google account? I set my personal side up with a "burner" email and the Knox side with the email I use every day.
4. How do you disable SDM? I used this: http://forum.xda-developers.com/and...---------------------------------------------
5.Where do you get My Knox" The Play Store.
6. Where did you get Kingroot? http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
7. What order do you install the software? Restore 4.4.4/Set up Google account./disable SDM/setup My Knox/Kingroot on personal side/=enjoy..... .......Note: this is not for use with SuperSUME.
8. Is root permanent? Some of the modification made when rooted are permanent but this Root is On Demand, temporary And I think this root method is safer than using Kingroot without Knox.
9. What about reboots. If a App ask to reboot first try not rebooting some changes will take effect without a reboot. If you have to reboot use a soft-reboot like SimpleReboot. You will almost always lose root with a hard reboot.
10. For an added security measure I am going to use the "Personal" root side as a playground and reboot before I open the My Knox Security side. Just to throw off any would be hackers.
Fixes
1. I found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select allow and then on the first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
The same procedure may work for other apps. For some reason Adaway starts working without a reboot. You will need to clear and restart your browser.
Calm down, these things take time. First when you reboot allow your phone to settle down, a minute or two. Don't open anything. FIRST, Open and run kingroot. Once root is established run Adaway like I said. It probably will work the first time but if it fails just try again. It seem that once Kingroot gets to the point where it is not asked for permission, the reboots go away and it becomes more stable.
2. O.K., KNOX disables USB debugging, but I was able to uninstall Knox at the Playstore /Re-enable USB debugging/ then use gatesjunior's debolater app to remove SDM/ then install Knox /then root with Kingroot and it is working great again. I did try to put Super-Sume Pro on top but it would NOT work. I think Super-Sume Pro removes Knox. So I had to start over but I got it working great. If you need to use USB debugging for anything now we have to uninstall Knox. I'm still testing now.
-----------------------------------------------------------------------------------------
Check Back to post # 1 & 2 for updates.
Having some guys look into this.
doctor-cool said:
I was concerned about Kingroot and security so decided to try this.
I'm on a retail Verizon Note 4 running Gatesjunior's Safe 4.4.4.
I did a factory restore then after setup, I installed My KNOX from the Play Store and set it up .
Then I rooted with Kingroot . It worked. Now sometime when I reboot I get the Unlock logo with the words Custom on the boot screen just like the DE Note 4 . I went into recovery to check but no Knox trip. I win the Root Price. I have two environments. One rooted the other as secure as you can get.
Click to expand...
Click to collapse
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
warriorpluto said:
Nice you found a work around.great job brother
Sent from my SM-N915V using XDA Free mobile app
Click to expand...
Click to collapse
did you test it?
Extreme Syndicate L
This is like having a dual boot on the fly
gatesjunior said:
Having some guys look into this.
Click to expand...
Click to collapse
I have two separate Google play store account on two separate partitions .
Can you get it to work with SuperSuMe Pro.
All this time we have been disabling Knox and actually My Knox is your friend.
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Wetzel402 said:
I purchased Super SU me pro but haven't tried anything yet. Interestingly my company's MobileIron administrator app still takes effect with My Knox so until I see more progress I'm going to avoid moving forward. MobileIron has root detection and when I first set it up using Gate's debloater to disable any system apps caused it to lock me out of my email. Perhaps once we have root perfected I might be able to find a way to bypass all of that...
Click to expand...
Click to collapse
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
doctor-cool said:
I think that as long as the Knox's partition is locked nothing can get in are out. I still don't like being dependent on a China App, For over the internet root every time I want root. Our goal of rooting the Retail Note 4 permanently is achievable. I have seen the unlock icon and the Custom on my boot screen at times.
Click to expand...
Click to collapse
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
gatesjunior said:
Well, in all fairness, we have seen that as well without Knox being installed and configured, but I want someone else to validate this approach.
Click to expand...
Click to collapse
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
doctor-cool said:
Sometime I see the unlock icon and the word Custom, when I hard reboot manually.
Sometime I see the unlock icon and the word Custom, when the phone reboots unexpectedly, when some app ask for root.
AND Sometime I see the regular screen.
And once I did a hard reboot, it had a normal boot screen and the phone stayed rooted without Kingroot after a Hard Boot.
Click to expand...
Click to collapse
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
elliwigy said:
did you test it?
Extreme Syndicate L
Click to expand...
Click to collapse
No. I havemt backed up my phone yet to try. Ill do it when I get home and try
Sent from my SM-N915V using XDA Free mobile app
not random
elliwigy said:
custom boot screen simply means you attempted or modified something (root) can cause it..
im sure even on a temp root it would show custom for a reboot or two.
youre saying you get random reboots but root sticks regardless?
Extreme Syndicate L
Click to expand...
Click to collapse
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
doctor-cool said:
They are not random reboots, it happens when a app ask for root. Like when AdAway ask for permission instead of granting permission it just reboots. I retry AdAway again and the next time when it ask for permission it is granted then I have to manually soft reboot. XDA is a lot better without commercials trust me. :silly:
Click to expand...
Click to collapse
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
elliwigy said:
lol. so every app needs to be ran twice til it sticks.. im just trying to get more info, no commercials here.
Extreme Syndicate L
Click to expand...
Click to collapse
I meant when AdAway disables the commercials it is worth the trouble. But yes most of the time the root results are temporary . But once you get it set up your good to go and it is worth the trouble until your battery dies
-----------------------------------------------------
Edit: I may have found a fix for AdAway, Inside Kingroot under Root Authorization for AdAway select alow and on first run of AdAway when ask if you want to reboot, check: Never / then No = Problem solved .....yes
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Hotdizzle said:
I can't even install My Knox due to "a custom OS has been previously installed on this device". I'm on the latest "safe" LP BOG5 upgrade by hsbadr
Click to expand...
Click to collapse
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
doctor-cool said:
It only works on the Retail Note 4
-----------------------------------------------------------------------
Edit: It would work on the DE Note 4 if it has not been modified.
Click to expand...
Click to collapse
I have the retail note 4
Hotdizzle said:
I have the retail note 4
Click to expand...
Click to collapse
Then...l don't know. I'm on safe 4.4.4, how about you?
-----------------------------------------------------
I just read your post 16 . Your on LP I'm on KK
LOL this works?!? how did nobody ever try this until now.. I'm speechless