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
Related
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Piaband said:
It was really easy to put an unlock code into adb.
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
if i could unlock it when i had gotten it in august, sure. but it's too much effort to start over at this point. i have everything set up perfectly. never had to start over. also didn't want to pay for it and send my info to some stranger on the internet. anyway, moot point. good for you, but that option's not available for most people.
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
No nothing roots 4.4 at this point.
vegasdgk said:
So does this work when your already updated to 4.4?
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No he basically just rewrote the instructions of how to root the original firmware.
akellar said:
No he basically just rewrote the instructions of how to root the original firmware.
Click to expand...
Click to collapse
I didn't rewrite it. No where are there instructions for getting root AND write protection off on the 4.2.2 camera update without 1 using command line commands AND 2 that network based program (called Cydia compactor I think). There's none of those complications here. Most people don't even realize 1 click root survives the camera update.
But you are right as to kit kat. I thought my title was clear that this is for jellybean though.
mistermojorizin said:
Are the root methods too complicated/risky for you? This is a simple solution.
Start with: original droid maxx software (12.7.7 i believe) on Verizon
1. Install motoroot 1.0 (JCase's first root method from original development section), run it, and click root (that's click #1). Make sure everything's working, reboot a few times, use rootchecker to make sure you've got root. (note you won't have write protection off and there'll be a 10-15 sec delay after booting up before you have root). But hey, it's 1 click.
2. Take 1st Verizon OTA to the 4.2.2 with camera update (12.15.15 i believe). Root should survive. Check that it did with root checker.
3. Install the write protection no more from the moto x original development section on your computer. download android-sdk and make sure adb is working, make sure fastboot is working. connect your phone to your computer and run the "write protectoin no more" app on your computer (that's click #2).
That's it. Now I have write protection permanently off, and I have root. I didn't have to use cydia impactor and mess with a tricky update to 4.4 which if it doesn't work I couldn't go back to a rooted phone. I never had to fxz anything or restore anything to stock, or lose any of my data. I didn't have to pay a dime or give someone on ebay all my phone info.
Sure I'd like to have 4.4, but pretty happy with where I am and how easily I got here. And I've read a lot of people say "the root methods are too complicated" --- well this is pretty easy cause you're just using 2 packaged apps.
I've gotten a lot from this forum, and just thought I'd share. Please don't flame. I feel like this is the best compromise of features:effort for me.
Click to expand...
Click to collapse
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
-Zeta- said:
Hello,
I have rooted my phone when i am in 12.7.7, then i took the OTA update 12.15.15, now my device is in a boot loop, it boots normally and after a few seconds it will reboot and it goes over and over again.
any thoughts on this and should I use RSDLite to flash it to either 12.7.7 / 12.15.15???
Click to expand...
Click to collapse
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
mistermojorizin said:
which method did you use to root it? what system stuff did you change after rooting it?
a lot of people had bootloops after taking an OTA because they did the root method that had replaced their stock recovery with a write protect off mode. so in effect, they were having bootloops because they didn't have the recovery, not because they had root. it their case, there was an easy solution of just flashing a recovery. unfortunately i don't know the details of how to do that off the top of my head.'
in any case, rsd'ing to either of those software versions will likely fix all problems.
i rooted as i described with motoroot 1.0, which didn't affect my recovery and was easy to OTA without problems.
good luck
Click to expand...
Click to collapse
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
-Zeta- said:
Thanks for the quick reply,
I used the PwnMyMoto here to root, i forgot that this method will replace / remove the stock recovery.
With a minute of panic and some google search, I'd managed to use RSD lite to flash the 12.15.15 FXZ and now my phone is back in business but kinda lost root.
Right now I am looking into the RockMyMoto method here and see if it can help me to gain root.
Click to expand...
Click to collapse
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
mistermojorizin said:
glad you got your phone back in order, might want to check out slapmymoto (which is the path to rooted kit kat and involves running rockmymoto on the way) while you're at it
Click to expand...
Click to collapse
Not sure about the battery life on kitkat of the MAXX right now, so i will stick with 4.2.2 first and do a little research.
Anyway, thanks for the reply and I've gained root on 4.2.2 (12.15.15) using RockMyMoto:laugh:
Someone tell me what it is. I wanna keeo root, lol, dont feel like going through all that
From online research, It's just to fix some bugs and a slight performance increase. I don't know if it will break root because I'm not rooted
Sent from my C6916 using XDA Premium HD app
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
mariussilverwolf said:
I do have root, so I can report. I just installed it and am going through the rebooting process now. Notes:
* My custom boot animation did not change. This looks promising so far.
* "Android is upgrading..." message. Now to sit and wait as 139 apps get optimized.
* None of my XPosed modules kicked in, nor did DashClock load as my lockscreen widget. Hmm. That's less promising.
* SuperSU launches. Auto-start items are triggering Toast for being enabled with elevated permissions. This looks better.
* Checking XPosed. Says inactive. Updating and rebooting.
* Everything looks good. All my XPosed modules trigger. Root still active.
I can't find anything immediately apparent as present in the update, but the fact that it doesn't break root is good enough for me right now.
Click to expand...
Click to collapse
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
TrunkleBob said:
I had a similar experience, except that Xposed is still not active. It constantly says "The latest version of Xposed is currently not active." I have completely uninstalled/reinstalled to no avail.
Everything else requiring root is working, however.
Click to expand...
Click to collapse
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
How did you install it easily, i keep getting could not be verified
mariussilverwolf said:
I had that happen recently; after SuperSU updated it wasn't properly prompting for XPosed to gain access. I had to change SuperSU settings to allow the prompt to generate and be on top of any window and clear out the XPosed settings within. On the next open, all the prompts generated and I was able to grant access again.
Click to expand...
Click to collapse
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
anyway to decompile this update to see what files are there?
im getting could not be verified as well, trying via sony update center on PC, im rooting with xposed as well
arghhh before i was able to use root-cloak on the sony update app and download updates... seems i cant do that anymore. how did you get to install while rooted? @mariussilverwolf ?
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
chriscosta77 said:
I have a T-Mobile Sony Xperia Z1s. I updated without really thinking about it. I suppose it was a dumb move. It's an updated Kernel version apparently. My current kernel version is:
Code:
3.4.0-perf-gf96f13d-00907-gaee6e5a
[email protected] #1
Thu Oct 9 09:14:33 2014
So what I guess that means, is that the exploit that enabled us to root Xperia devices previously, has been patched. I had my SuperSU Pro setting for "Survival Mode", ticked "on", and I was able to maintain root. However, I suspect, that if I factory reset my Xperia Z1s that this new firmware would not be rootable, as I bet this is just considered a "security patch". I would have really been pissed if I had lost root because of some crappy OTA update. SuperSU Pro to the rescue.
I rooted my phone using the "simple" rooting method that had come out after "Towelroot", It was called "Easy Root Tool"? anyway, it was a pretty easy process.
Edit: I found the thread again: http://forum.xda-developers.com/showthread.php?t=2784900 But I'm too chicken to try and factory reset and re-root my phone, because I'd hate to not have root.
Click to expand...
Click to collapse
It is broken, on latest minor ota through pc companion update, not restore, and trying to root with easy root but it isn't working
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
nickcaper said:
same here... "cant be verified"
so basically no go on the update.
im rooted. i have dual recovery.
c6916
any possibility of a tft file to use for updating?
Click to expand...
Click to collapse
I just used my cousin's phone as a tester, it breaks root, haven't tested with supersu pro yet with survival mode
i swear, its like these companies dont want us to use the devices the way we want. A simple thing like root and they make it so hard, even impossible on some models. These companies should know by now that there is a niche which desires freedom like rooting.
if i wanted a frggin phone that didnt have root or a locked os or bootloader id get a dam iphone.
im seriously NOT buying another phone from a store.
ill make sure i get something i can work with the way i want. its already stupid expensive as it is just out the box all locked up and full of bloat wear.
it takes a stupid amount of time and effort just to make these devices do what we want.
which is something that i shoulda got when i paid for it..
looks like i wont be updating sh.... t till i know i can use my device freely.. the way i want.
Unrelated to the root conversation, I'm stock, but my data is acting a bit weird since the update. Did this update change the radios?
Sent from my C6916 using XDA Free mobile app
4.4.4 root
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Your question.
Johann Broseph said:
Im new to xda and i just wanted to know is there a root for the sony xperia Z1S that works with android 4.4.4 kit kat? I just recently got the phone and i didnt root it before updating it
Click to expand...
Click to collapse
Please just use the search feature, you can easily find the root method. The root method is even on the first page of this topic.
For reference (since my root access remained post update) here's what I have enabled in SuperSU settings:
* Enable SuperUser
* Show Notifications
* Auto-refresh apps and logs tab
* Enable su during boot
* Mount namespace separation
* Trust system user
* Enable permission warning
* Enable Pro
As I mentioned in a previous thread, root was obtained using towelroot on 4.4.4. I haven't run into any issues with root-check invalidating any installs since. The OTA installed without any error messages. I can inject audio into /system/media/notifications and I can create new folders on the root directory that remain after reboot. Maybe I got lucky? I hope by sharing this that other people can duplicate my findings and we can find a way for everybody to maintain a working root solution after this update.
TrunkleBob said:
I just did all that and got SuperSU to re-prompt. Xposed still says it is not active.
I just noticed something else weird; as mentioned before, any other apps that require root are working, but in Root Explorer, if I hit Mount R/W, nothing happens. I don't get an error, but it also doesn't re-mount.
I suspect these errors may be related, because in Xposed I can no longer install by writing directly to /system, I have to use the recovery method. So su is working, but enabling read/write on /system is not.
Click to expand...
Click to collapse
I've been doing some digging and discovered I'm missing a file. Following the original directions for rooting, I created a script and have Script Manager executing it at startup.
The first command is:
Code:
su -c "/system/xbin/kill_ric.sh"
This fails because that file does not exist on my phone. Anyway to get that back?
I had a huge problem with this yesterday and long story short, you cannot use the easy root method if this update is applied. I had to use the flash tool to get the last ftf files and start over from scratch. Avoid this if you can.
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
gqukyo said:
I don't really care to update but is there anyway to get the notification of the failed verification off my notification tab? I'm OCD about keeping my notification list clear...
Click to expand...
Click to collapse
only way to get the notification off is to go into settins then look for apps then look for update center. click on it and click on the clear cache. only problem now is. you will need an app like sd maid or something that stops that app from starting automatically when the phone turns on. this is what i do.. it works... you wont get anymore notifications unless you manually make it check.... i use sd maid...
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
If you have rooted your N6P and you are at a store and want to use Google Pay, is there a way of quickly (on the fly as it were ) unrooting the phone,, making purchase and then rerooting?
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Cares said:
Go into SuperSU. Uncheck Enable Superuser. Add your cards. Turn root back on and you're good to go. It appears the only caveat to root is that you're unable to add payment methods. You should be able to pay.
Click to expand...
Click to collapse
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Tried this method on my Nexus 6. It knows I'm rooted, even if I've disabled SU entirely and rebooted.
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
So how do you ensure the system partition is not changed?
kboya said:
Have a search about, at least one of two people have confirmed that they have paid with root disabled, but only if the system partition hasn't been changed
Click to expand...
Click to collapse
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
teknomar7 said:
Have you actually tested this at a terminal? Everything I've read says root or custom roms will not work with Android Pay. You can unroot and add the cards, but it will still not function at a POS terminal. I am yet to find someone that can confirm it works the way you mentioned. Everyone agrees that you can add the cards... but that's where the functionality stops.
Click to expand...
Click to collapse
I just added my cards. I'll test it out later today. Need to find a store that takes Android Pay
teknomar7 said:
Pardon my ignorance here... but doesn't rooting the device modify the system partition? If not... maybe that's the difference with the other threads I've seen. Everyone was using custom roms as far as I know. I'd like to be able to root so I can use adblocker and still use Android Pay. I can live without a custom rom on stock android... but I really miss adblocker.
Click to expand...
Click to collapse
There's a root without changing system. As I said, have a search about. I read it earlier today or perhaps yesterday. There's a thread about the root without system.
Thanks... found the link.
http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
cool, no worries.
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
ArkAngel06 said:
So I can confirm that Android Pay will not let you add cards while rooted, but it will let you complete a payment at a terminal while root in SuperSU is enabled. So once you have your payments setup, you can root and use Android Pay.
I own a store with a terminal that accepts Android Pay and have tested it a few different ways over the past 2 days. Every way worked. Unrooted, root simply disabled, root enabled.
The only thing root does is makes it so you can't add a card.
And I have regular root, not the new systemless root.
Click to expand...
Click to collapse
Can you still pay after a reboot? Thanks.
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
Lol, I'll have to try tomorrow.
Was this explanation debunked, then?
http://www.xda-developers.com/googl...-with-root-and-android-pay-in-the-xda-forums/
You
Aridon said:
It works. I wish the misinformation would simply stop. It has worked on devices in the past, it works on devices now and it will most likely work on devices in the future. We had threads before launch how root would disable bank apps, fingerprint sensor, android pay etc and it is all simply untrue.
It works.
Click to expand...
Click to collapse
Yes, but Google stated that Android Pay can't be used with root. So of course there will some question to it.
source
And root absolutely does effect Android Pay. However if seems only while adding payment methods, and nothing once they are added.
What Google is using to determine if the device has been tampered with: https://koz.io/inside-safetynet/
Its definitely an interesting and pretty secure setup. Since it seems to happen real-time, maybe they turned off the "su_files" check and thats why Android Pay works on rooted devices now.
boxcar8028 said:
Can you still pay after a reboot? Thanks.
Click to expand...
Click to collapse
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
ArkAngel06 said:
So tried it again today after rebooting with root enabled and it does not work. So there you go. Android Pay does not work while rooted, period.
It does work with root simply disabled in the SuperSu app and then a reboot.
Maybe the new systemless root, though chainfire said if it does work, it was unintentional and Google will probably patch it.
Click to expand...
Click to collapse
This is correct. If you try to pay, after adding your cards and re rooting, it will fail.
You must disable root again to pay. You can reenable after.
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?