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
Related
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
Hi,
I'm completely new to the root world...
I tried to install towelroot V2 on my Galaxy Note 3 which runs the Kernel 3.4.0-636608.
I rooted it, root checker said all ok, but after installing SuperSU, updating binaries and rebooting the device, root checker says it's not rooted...
Now it's worst, Wifi is turning 100% even when turned off, and sometimes the screen of my phone stays black, even if I push the buttons, in that case I need to remove the battery and to reboot the phone...
Any solution ?
Again I'm a newbie, I don't even know how to restore the phone or to do a reset, so please help me...
Thanks in advance
RaphaelBEN said:
Hi,
I'm completely new to the root world...
I tried to install towelroot V2 on my Galaxy Note 3 which runs the Kernel 3.4.0-636608.
I rooted it, root checker said all ok, but after installing SuperSU, updating binaries and rebooting the device, root checker says it's not rooted...
Now it's worst, Wifi is turning 100% even when turned off, and sometimes the screen of my phone stays black, even if I push the buttons, in that case I need to remove the battery and to reboot the phone...
Any solution ?
Again I'm a newbie, I don't even know how to restore the phone or to do a reset, so please help me...
Thanks in advance
Click to expand...
Click to collapse
Hi.
To reset yr phone, turn off yr device first.
Then, press and hold power button, home button and volume up button at the same time.
In a few seconds, u will see a recovery options.
In there, scroll down using volume down button and click factory reset/wipe data using the power button.
Then, wipe cache partition and dalvik cache.
Once u done all that, reboot yr device.
U may need to towelroot yr device again if it lost root.
Hope this will help u..
Cheers..
maanz "L" said:
Hi.
To reset yr phone, turn off yr device first.
Then, press and hold power button, home button and volume up button at the same time.
In a few seconds, u will see a recovery options.
In there, scroll down using volume down button and click factory reset/wipe data using the power button.
Then, wipe cache partition and dalvik cache.
Once u done all that, reboot yr device.
U may need to towelroot yr device again if it lost root.
Hope this will help u..
Cheers..
Click to expand...
Click to collapse
Thank you very much for your answer.
Do you think there is any solution to avoid this freeze that happen instead of clear all the datas ? Because I didn't save my phone, and I don't even know how to save everything so that I just have to plug it back to my computer to restore everything (I am a former user of an iPhone...)
Thanks for your help !
RaphaelBEN said:
Thank you very much for your answer.
Do you think there is any solution to avoid this freeze that happen instead of clear all the datas ? Because I didn't save my phone, and I don't even know how to save everything so that I just have to plug it back to my computer to restore everything (I am a former user of an iPhone...)
Thanks for your help !
Click to expand...
Click to collapse
Since u are new to android, let's do the hard way...
Another thing is, after u installed SuperSU, have u allowed root checker to gain permission from SuperSU?
There are few members complained of wifi 100% in here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23.
For me, I don't have this problem so far.
maanz "L" said:
Since u are new to android, let's do the hard way...
Another thing is, after u installed SuperSU, have u allowed root checker to gain permission from SuperSU?
There are few members complained of wifi 100% in here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23.
For me, I don't have this problem so far.
Click to expand...
Click to collapse
Nope, any application never asked me for SuperSU permission, not even adblock...
But Root checker was saying that the check appeared to be very slow...
How about saving all the datas ?
u have to let SuperSU grant permission on all root apps, mate.
if not, the rooted apps will not work..
saving datas??
Sent from my SM-N9005 using Tapatalk
maanz "L" said:
u have to let SuperSU grant permission on all root apps, mate.
if not, the rooted apps will not work..
saving datas??
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
It's ok now, I just did a hard reset on my phone...
I know I had to grant SuperSU permission but it wasn't asking for...
Anyway, problem solved but I lost a few of my data...
Thanks for your help guys !
Unable to root
Hi~
I'm new to rooting too. SM-N9005 running on 4.4.2 & kernel 3.4.0-1703205 here. Tried to root my note 3 with towelroot V2 but failed. After pushing the "make it ra1n" button, it says "you should have root, no reboot required." However I checked with rootchecker app from playstore, and it says that I do not have root access. Therefore I have a few questions that I hope you guys can help me with.
1) Is rootchecker app from playstore reliable & accurate in telling whether or not a device has root access? Or are there other ways to check whether a device is rooted?
2) Does having root access means you can download any paid apps for free?
3) After rooting my note 3, can I update from 4.4.2 onwards? What will happen if I were to update my rooted device?
4) Does having Aptoide & apps downloaded through it hinder or affect the rooting process?
Please help and Thank you.
Mouzai said:
Hi~
I'm new to rooting too. SM-N9005 running on 4.4.2 & kernel 3.4.0-1703205 here. Tried to root my note 3 with towelroot V2 but failed. After pushing the "make it ra1n" button, it says "you should have root, no reboot required." However I checked with rootchecker app from playstore, and it says that I do not have root access. Therefore I have a few questions that I hope you guys can help me with.
1) Is rootchecker app from playstore reliable & accurate in telling whether or not a device has root access? Or are there other ways to check whether a device is rooted?
2) Does having root access means you can download any paid apps for free?
3) After rooting my note 3, can I update from 4.4.2 onwards? What will happen if I were to update my rooted device?
4) Does having Aptoide & apps downloaded through it hinder or affect the rooting process?
Please help and Thank you.
Click to expand...
Click to collapse
Hi.
are u using the newest and latest firmware update? I'm not sure whether it will work with towelroot v2. AFAIK, towelroot will work for firmwares before June release. need to read up here: http://forum.xda-developers.com/showthread.php?t=2783954&page=23
1) rootchecker app is reliable as lots of people used it. there should have other apps on playstore to check for root.
2) no, paid apps is paid apps. rooting yr device means u are able to "get inside or hack yr phone's system" and u can make adjustments or "mods" to system files (for developer level).
3) u can update new firmwares, but u will lose root and towelroot may not be able to support unless geohort (towelroot dev) updates it.
4) u can install any app u like, it will not hinder yr rooted device.
Cheers..
Hi~
Thanks a lot for your reply & helpful answers! Anyway after granting access of rootchecker from superSU, it says I do have root access. However I can't tell the difference... hahaha. So lets assume my device is rooted, may I know how can I delete all those useless & space consuming built-in apps of my note 3 during purchase?
Use titanium backup
Sent from my SM-N9005 using XDA Premium 4 mobile app
Most of us were talking about Towelroot over in Jcase's PIE thread or over in collinjames' thread, but I think it's time it deserves it's own thread.
UPDATE:
@iKrYpToNiTe made the awesome TowelPieRoot which makes this method easier to use. You can still use this thread to root your phone, but I will be using his method from now on. Happy rooting!
Important Links:
Geohot's original post.
Towelroot's Homepage
Mod Strings
What is Towelroot?
Towelroot is a rooting method for most android phones, and it uses an apk to obtain root (dead simple too, push one button, no need for other tools and workarounds). (source)
Why do we use Towelroot in conjunction with PIE?
PIE nor Towelroot disables write protection. Both of them offer a temporary root that has to be applied after a reboot. The advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then Towelroot allows you to continue rooting "on the go" in the future without needing a PC.
How does it work with the Moto X?
It works the same as PIE. It gives root access but the device is still write protected. It is also temporary and must be reapplied after a reboot. However, a soft/hot reboot can keep the root access, due to soft/hot reboots only rebooting the graphical Android shell.
What does it work on?
XT1049 - Republic Wireless, not confirmed, should work.
XT1052 - European
XT1053 -T-Mobile US, not confirmed, should work.
XT1055 - US Cellular, not confirmed, should work.
XT1056 - Sprint, not confirmed, should work.
XT1058 - AT&T, Rogers, Claro, Movistar, Vivo, Oi, TIM
XT1060 - Verizon
How do I use this tool?
Remember to apply PIE first!
1. On your device, go to here.It will start to download the .apk
3. On your device, go to Settings>Security>Unknown Sources and tick the box.
4. Run the downloaded apk, tr3.apk
5. Press "welcome to towelroot" 3 times.
6. Replace the last 0 with a 1, due to modstrings.
7. make it ra1n
Your device should now be rooted and you should be able to use apps such as Greenify and Titanium Backup.
Some applications that should work with root, might not work with this method.
Some people have experimented with using Superuser apps, but I have not seen a consistent method to use one.
How are we keeping root after reboots?
We aren't rebooting! Seriously, we soft/hot reboot which allows us to keep root after a graphical reboot. And even if you do reboot, you can always reapply the root with Towelroot. You just need to make sure you have applied jcase's PIE before hand.
Xposed:
jpond83 posted up some instructions in the PIE thread about how to get Xposed to work:
Make sure you have installed PIE before you try to use Xposed or it will NOT work. View jcase's PIE thread for more details.
jpond83 said:
1) install towelroot. Xposed installer, Busybox installer, power menu
2)run towelroot, click "welcome to towelroot", replace 0 with 1, make it rain.
3) run xposed and click install
4) run busybox installer and click install
5) run power menu and click "hot reboot"
6) enjoy root without using a PC.
Click to expand...
Click to collapse
Current problems/bugs
Some users have problems with soft/hot rebooting. Reapply PIE.
Random reboots.
Warning about using this exploit
Myself or anyone that has helped develop this are not responsible for anything that occurs to your phone by using this method.
As for this thread, feel free to post your experiences with this tool or any supplements to add.
I'm glad this finally has a dedicated thread. Good job OP
I finally got it working. When I installed SuperSU it was lagging. But I kept it off. I even have hkthememanager running with KitKat all white settings from the nexus forum.
Sent from my XT1058 using XDA Free mobile app
The softboot/hot boot issue comes from not having busybox installed.
jpond83 said:
The softboot/hot boot issue comes from not having busybox installed.
Click to expand...
Click to collapse
I've installed 3 different Busybox installers:
Busybox by Stephen (Stericson)
Busybox Installer by JRummy Apps Inc.
Busybox X by Robert Nediyakalaparambil [root]
The first and the third one said they installed successfully, but the second one did not.
Even after 2 installations succeeding, I was still unable to soft/hot reboot.
Any ideas?
I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.
jpond83 said:
I use busybox installer with the blue icon. Never had a issue with softboot as long as I install everything in the order I stated in the other thread.
Click to expand...
Click to collapse
Guessing that is the Busybox Installer , I just get this when I try to install it. I have root access, but Busybox is not installing.
But when I use Busybox by Stephen, it says it installs correctly, and my Busybox checker says it does too, but Power Menu still won't Hot Reboot.
Have you ran pie root before? It needs to be ran on the device once before for it to work.
jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?
dier325 said:
Replying the PIE exploit has seemed to fix it. Thank you.
Should I add to the original post that you need to install PIE?
Click to expand...
Click to collapse
Yes, its a must. It should only need to be ran once. After that you should never need it again unless you factory reset.
jpond83 said:
Have you ran pie root before? It needs to be ran on the device once before for it to work.
Click to expand...
Click to collapse
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.
KidJoe said:
Wait, so you need to use PIE to make stuff work under towelroot work on the X?
If so, why not just stick with PIE? Why add towelroot?
Click to expand...
Click to collapse
Towelroot can work just by itself, but PIE adds some functionality that allows for easier softbooting.
jpond83 said:
Did you read??? You only need to use pie once. After that you can reboot your phone as much as you want and just root with towelroot.
Click to expand...
Click to collapse
I'm sorry that it bothers you so much that I have a question I'm asking. But if you must know, YES I READ. I've read this thread, the PIE thread, and Does Towel Root have any potential in the Motorola field?
And if you can read, you would know that you didn't even answer my question of "why use both?". Instead you just sort of flaming me for asking something and said pie only needs to be run once which is already stated very clearly in what I quoted.
What I'm getting at with my question is something that is implied, but not stated.....
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
But it does beg a few more questions (at least by someone who is READING all of this, but not using either PIE or TowelRoot)...
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?
KidJoe said:
It is understood that since neither PIE nor Towelroot disables write protection on locked bootloaders, if you root with either PIE or Towelroot, you need to re-root after power off/on (or "hard" reboot as some are calling it). It appears the advantage to Towelroot is that it is an APK that sits on device, so unlike PIE, Towelroot can be run later, non-tethered to a PC, should you have to power off/on. So you use PIE first while tethered and initially rooting, then whatever it does allows Towelroot APK to continue working properly when "on the go" in the future without needing a PC.
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
This is a great explanation of why we are using both. I will add a paragraph to the OP that paraphrases what you just said.
KidJoe said:
Is PIE needed once before Towelroot only if you want Xposed? Or is it always needed once if you ever plan on using Towelroot? (i.e. Are there any cases where Towelroot alone works? like if you only want to block ads or tether. Or must you have used PIE once already, if you want to make use of Towelroot to root at all?)
Click to expand...
Click to collapse
Towelroot alone works, but we've found that some applications (i.e. Xposed, Busybox) don't work unless you have PIE. Using them together allows us to use them.
KidJoe said:
[*]Must it be done in a certain order? I.e. if you've used towelroot and realized you forgot PIE, can you just run PIE and be good? or must you reboot, use PIE, then use Towelroot again?
Click to expand...
Click to collapse
The method of each one must be done in order but it does not matter which one you apply first to the device. In fact I just had Towelroot running on my device and then applied PIE allowing for Xposed to work.
KidJoe said:
[*]What changes are made by PIE that survive power off/on and enable Towelroot to work when trying to use Xposed?
Click to expand...
Click to collapse
PIE allows us to keep Busybox installed on the device which allows us to Soft/hot reboot.
KidJoe said:
[*]If this information is accurate, can Geohot and Jcase work together on a single solution, and possibly single on device solution for the X?
Click to expand...
Click to collapse
I want to remind everyone that there are very few of us who are using both of these methods together currently. It is fine for these questions to be brought up for the uninitiated. As for them working together, I think Jcase stated that he wants to move away from the X, as well as I think he is on holiday due to his current signature. I don't know about Geohot but some people have created a thread over in the Moto G forum raising some money to buy the device for him after he said he would try to work on it if he had one.
I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary
KidJoe said:
If that is truly the case, then I think that should be highlighted better, and @dier325 should add it to the OP as many are missing that bit of information. It would also cut out some of the frustration by those encountering issues when running PIE again, after they had to power off/on. (as they could use PIE when first setting up, then towelroot if they lose root while away from their PC).
Click to expand...
Click to collapse
I have added another section to the OP explaining the situation.
cell2011 said:
I have jcases pie root on my x and g and i either always soft boot in xposed framework and keep phone on airplane mode when not in use and charge when necessary
Click to expand...
Click to collapse
Adding them together allows you to root without having to use a PC if you do reboot your device, say it dies.
Thanks guys for clearing this up. I think Towel root should be renamed to something less middle east reference and it would be welcomed more.
So basically if we want more functionality with our root, we should do PIE first? I clicked over onto the PIE page but didn't really how it's done. I have towelroot down, but it seems PIE is a good idea to use in combo with towel root. I could be missing something though cause I'm in the XDA app at work.
I do understand though that PIE is a one time thing and we should just use towel root thereafter when we reboot and need to reroot again.
Sent from my XT1060 using XDA Free mobile app
Using PIE in conjunction with Towelroot allows you to use apps such as Xposed.
Sent from my XT1060 using XDA-FORUM, powered by appyet.com
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:
will4958 said:
I stopped messing with KingRoot some time ago, just didn't seem worth my time considering you lose root after a reboot. Especially when certain apps require a reboot to take effect, such as Adaway, Xpose, and several others. I'm more-or-less fine without root, but that doesn't mean I wouldn't root my phone if I were to come across a stable and perm root solution.:cyclops::fingers-crossed:
Click to expand...
Click to collapse
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..
Reminon said:
I was on KK, and a friend of mine updated to 5.0.1. I said screw it and fully updated, not caring about root anymore. If this were more stable I would use it more. Temp root is annoying, but it survives hot reboots, which is sufficient for apps most of the time..
Click to expand...
Click to collapse
I tried to use the hot reboot feature of a rooted reboot app I have on my Tab 3 8.0 after installing something like Xpose, but the root didn't survive. The only real reason I tried to install Xpose was to use the Motorola hotspot app found in it. I'm currently using the paid version of FoxFi and it works great, it's just a four step activation compared to the one touch I got spoiled by on my S4. No biggie.
Over on AT&T note 4 thread someone said that they have temp root for 5.1.1
Edit: someone already posted that disregard this ..[emoji4]
Sent from my SM-N910V using Tapatalk
Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here
EdrickMG said:
Temp root only will give two things uninstall bloatware, SD card fix.... I don't see any other advantage, well I'll give a shoot and put my conclusion over here
Click to expand...
Click to collapse
When I was on 4.4.4, I realized I could use the default file explorer to manage my SD card, meaning copy to, delete from, or anything else I needed to do with it. I'm currently on 5.1.1 now and have been for about a few weeks now. On occasion, when I install a big game, I'll get a prompt asking me if I want to move the app to my SD card, so no need for the SD card fix app. The only thing I don't like about the 5.1.1 update, though, is that the sidebar seems to pop out a bit slower than it did on 4.4.4, but that's to big a thing for me. Since I have the two apps I use the most that can be accessed from the sidebar on my Pie Control app, I can access them much quicker. Keep the dream of root alive, people. It'll come someday, hopefully. If not, at least we have cool phones to play with.
ok i can confirm that i obtained temporary root, uninstall all bloatware... so well its not perfect cuz system its very unstable but at least its a begining, now im gonna give a try to sd card fix and other stuff...
Ok SD card fixed worked... but i dont belive it will remain after reboot, so.... well at least i uninstall that Amazon stuff and Activation Agent "Not a Verizon card" stuff
Wait What........... Are we saying we now have temp root on 5.1.1
gersrt said:
Wait What........... Are we saying we now have temp root on 5.1.1
Click to expand...
Click to collapse
That's it right, at least now you can uninstall all Verizon and Amazon crap from the system
Would it be possible to disable the ****ty Verizon logo boot screen and have it disabled after reboot. Thanks
It's important saying temporary root was achieve in BPA1 bootloader, 5.1.1
I managed to get a keyboard to open by switching from the stock keyboard to kii keyboard. Have not tried any others. Is there a mod we can do for hotspot with temp root to use the native hotspot app? I'm so tired of using foxfi.
Is there a safe upgrade yet from 5.01 to 5.1.1 Thanks. I need to know in case I need to roll back to 5.01.
Thanks
Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?
nubleeet said:
Wasn't the sole purpose of the BPA1 update to "remove pre-installed Amazon apps"?
Click to expand...
Click to collapse
Only the appstore and its widget..
Most of bloatware remains like NFL, and even instagram, however after deleted most of it, I don't know which one.. Allow me to use Hotspot without foxfi
Unstable indded
Reminon said:
Last night I was bored and tried kingroot again on 5.1.1. It had been a while since I had tried, and it always said they were looking for a method. This time, it rooted successfully, but made the system very unstable. It caused Lag, and the keyboard stopped functioning, but root checker confirmed root. Temp root of course.
Click to expand...
Click to collapse
I tried it out and it says it root is successful, but on my phone it just locks up after the rooting. I just wanted to uninstall the crap. Bummer.
Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.
Nada
gersrt said:
Ok So Ive been checking the ATT note 4 forum and they have been suggesting that the root exploit may have been found through the Note 4 Stock keyboard. A suggestion also made was before you root change your keyboard to Swype mode then root and it appears to be more stable. Maybe someone could try install a third party keyboard before root and see if it makes a differwnce.
Click to expand...
Click to collapse
So I downloaded Swype and Nada. Just keeps locking up. Kingroot even updated a few min ago to 4.8.1. I thought yes! But still false hopes. Still locks up for me and can't do a darn thing. Can't wait until my contract is up I am so dumping Samsung and Verizon. I think I am gong back to a flip phone and a laptop. So tired of no root and feel like I got duped into this phone.
Hello everyone,
I've noticed that there hasn't been any threads about rooting the Xperia Z2 Tablet on lollipop. Most threads have discussed how to root the device on 4.4.4 and to create an update image to maintain your root whilst updating to 5.0+.
I've scoured the interwebs and found nothing so I'll make it easy for those whom don't know how to achieve root or don't want to do much work without creating images and such.
First off I'm not responsible for any inconvenience that may come with rooting your device and losing your warranty. I can and will be willing to help out in restoring or answering questions that you may have.
This method uses Kingroot... For those who have a problem with kingroot, it is only used to achieve root and this guide will also be showing you how to remove kingroot and install Supersu with ease. Using the link below download the necessary files: Kingroot V4, Supersume, XZDualRecovery 2.8.26. Place all these files on the root of your devices internal storage/SD card excluding Xdualrecovery as that needs a PC. (If you want to Xposed working I will also supply the files needed for that as well). https://www.mediafire.com/download/wrsajbgw2jr6czt
*Make sure you have unknown sources enabled under Settings>Security>Device administrators as well as Developer Options available and USB debugging enabled. (To enable Developer Options go to Settings>About Tablet>Build Number and click it 10 times).
1. Install NewKingroot.apk and run the application. It will notify you that a root method was found and to try it. It may take up to 2 minutes to achieve root. (If all you wanted was root and are content with kinguser then you're done! :good: if you want Supersu and/or a custom recovery then continue on to step 2!
2. Connect your Tablet to your PC via microUSB. On your PC open and extract the contents of TabZ-lockeddualrecovery2.8.26-RELEASE.combined.zip to your desktop. Now double click install.bat a screen will pop up providing you with options to install xdualrecovery. Choose option 2. Installation on ROM rooted with SuperUser by pressing 2 and enter. The script will run its course and tell you to grant permission on your tablet. Open up your tablet and a kinguser prompt will show asking you to grant or deny permission to ADB (Grant it!!!) afterwards your tablet will reboot on it's own to TWRP. (I advise you to either make a backup of the tablet now or after you install Supersu as insurance in case of any mishaps). Click reboot System.
3.Install Supersume, open the application and run it. It will of course ask to grant it permission (Grant it!!!) it will check the environment (making sure that there isn't any Pokemon nearby that you don't need... Sorry Pokemon Go reference) and it will begin removing kingroot and install Supersu. If you didn't have Supersu installed already great! It'll open up Supersu automatically. Supersu may ask you to update binaries (DO NOT click TWRP as it will reboot and you have to start the process over from step one!!! :crying: Just click Normal and once it says successful you're done! :victory: The next step is optional if you Want Xposed.
*Optional 4. Install XposedInstaller_3.0_alpha4.apk. Open your app drawer and open NDR Utils. It will ask for permission (Grant it!!!) now here you may choose your preferred recovery... Philz Touch Recovery,TWRP or Clockwork Mod Recovery. Click Reboot to Primary Recovery (fourth option) once it's rebooted you want to click install>SD>xposed-v85.1-sdk22-arm-by-romracer-20160620.zip and swipe to install. You should get a success when it's finished. Now simply reboot and your apps will be upgrading. Congratulations you now have root with SuperSU and xposed! :victory:
**if you wish to uninstall Xposed simply reboot to recovery and click install>SD>xposed-uninstaller-20151218-arm.zip uninstall the application once it's rebooted and you're good to go!
***if you have a problem with Supersume not working, reinstall Newkingroot.apk and run it again to get root. Then run supersume again (Grant permission!!!) and let it run its magic.
If anyone has issues, has questions or needs help PM and I will do my best to help and answer all your questions. Please don't be discouraged because I'm new here! I will be soon adding a link to a video tutorial on how all these steps can be done!
I have the Verizon 561, will this allow rom upgrade to marshmallow?
chin_bone said:
I have the Verizon 561, will this allow rom upgrade to marshmallow?
Click to expand...
Click to collapse
Hi there, I also have SGP561 as well for Verizon. Verizon didn't release Marshmallowfor the device yet unfortunately. ???? still waiting and more then willing to confirm when it does
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
creepingcreep said:
Just ran on my 5.1.1 z2 and work first time. Great stuff thanks!
Click to expand...
Click to collapse
Glad it worked for you. Just wanted to help people out as I had invested time trying to figure out my own. I didn't like flashing files constantly so tried making easy.
Never had luck with kingoapp and today isnt any different
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Sent from my SM-G930V using XDA-Developers mobile app
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Sent from my SGP561 using XDA-Developers mobile app
ToneLa said:
Never had luck with kingoapp and today isnt any different
Click to expand...
Click to collapse
Sorry to hear what version are you using? Use the provided KingRoot in the download link provided
Daimonion1980 said:
Am i correct that you don't provide the kingroot.apk?
Which version are you using?
Click to expand...
Click to collapse
No, in the link provided all necessary apps and folders/zips are included. Including KingRoot apk
Cammy253 said:
How do you boot into custom recovery from device off? Everytime I try it takes me to the stock recovery
Click to expand...
Click to collapse
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
JediDru said:
Thanks so much. I am away for another week but I can not wait to try this. I got a verizon z2 tablet since it seemed to be the cheapest 10 inch tablet. You have breathed new life in to it.
Click to expand...
Click to collapse
That's great news to hear! I picked one up and wanted to root and I did on KitKat but when I upgraded to lollipop I lost root and rooted it the long way... Needed something simpler and couldn't find anything on here. So I wanted to make sure a guide was available to all. Enjoy and let me know how it went
reymund602 said:
Power off device. While device is booting up at the Sony logo hold power and volume down/up (depends on customer recovery) until led flashes green and device vibrates then let go
Click to expand...
Click to collapse
Thank you working great
Sent from my SGP561 using XDA-Developers mobile app
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
ToneLa said:
If you're talking about your google drive, there is no kingoapp.apk in there
All there is:
- supersume.apk
- tabz-lockeddualrecovery
- xposed uninstaller
- xposed v85.1
- xposed installer
Click to expand...
Click to collapse
Let me double check and if anything I'll post a link to the apk
Sorry that you're having issues though
bilestoad said:
I downloaded the most recent kingroot, which worked on my Verizon sgp561, and then I used your superuser file to change over to su. Seems to work just fine.. I'm on 5.1.1.
Click to expand...
Click to collapse
Thanks for confirming! If you didn't see the KingRoot apk in drive I'll upload the current version!
ToneLa said:
I tried the most recent kingroot and it fails.
An old version gave me an error code of 0x162982
Click to expand...
Click to collapse
What is the software version you are having problems with?