Related
Geohot stated in his thread "Possibly invited: Every Android phone with a kernel build date < Jun 3".
Do we fall under that? And is there any potential for using his root exploit somwhere in our X?
I too was wondering. Just read the article on Android Police.
http://www.androidpolice.com/2014/0...ve-and-maybe-almost-any-other-current-device/
Sent from my Moto X
I think it might be possible if you haven't updated to 4.4.3 yet.
EDIT: Known bugs:
su binaries don't seem to update. This may not be the root's fault.
Moto and HTC don't currently work because /system is write protected.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can confirm that this does not work. Just tried on my att moto x
I saw somewhere that it doesn't work because of the system write protection on the Moto X, but geohot is looking into finding a way around.
Sent from my SAMSUNG-SM-G900A using Tapatalk
linuxgator said:
I saw somewhere that it doesn't work because of the system write protection on the Moto X, but geohot is looking into finding a way around.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
You probably saw it where I did. Right above you. Good ol Brett.
Sent from my Moto X
Nevermind.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Sent from my Moto X
So I got it working for Titanium Backup and Greenify. Just have to enable Towel Root after each restart. Minor inconvenience till (if I'm able) I finally get unlocked. We'll see.
Sent from my Moto X
Jersey846 said:
So I got it working for Titanium Backup and Greenify. Just have to enable Towel Root after each restart. Minor inconvenience till (if I'm able) I finally get unlocked. We'll see.
Sent from my Moto X
Click to expand...
Click to collapse
Does this work on any type of moto x? I have a Verizon moto x.
Sorry didn't realize I was on the Verizon forums. I was searching this on my phone. So this does in fact work then? Just if you reboot your phone, you have to enable it again. I can deal with that to use WiFi tether.
Sent from my XT1060 using XDA Free mobile app
tu3218 said:
Does this work on any type of moto x? I have a Verizon moto x.
Sorry didn't realize I was on the Verizon forums. I was searching this on my phone. So this does in fact work then? Just if you reboot your phone, you have to enable it again. I can deal with that to use WiFi tether.
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on Verizon as well. (4.4.2) It's a bit tedious (should be very easy), but seems to work with Titanium Backup for freezing apps. I'm not even exactly sure how I've gotten it working but here is what I did. I'd love for somebody to chime in and let me know why my "root" has been a bit unreliable.
1. Downloaded and ran TowelRoot. Changed the last number in the string from "0" to "1".
2. Download SuperSU (Doesn't seem to install correctly, but does seem to (at least temporarily) give root privileges to Titanium Backup and the root options for Greenify.. But here's how..
3. When installing SuperSU I get a notification telling me it fails to install properly. However when I try running a root app and it requests SuperSU root privileges, and I do get a pop up asking. I grant the app privileges. However that app doesn't seem to start correctly... Until after I deleted SuperSU. Then Titanium Backup starts easily and it seems to have root access as I've successfully frozen some apps through this method.
I'm sure that I am getting lucky somehow and either missing a step or two or... I don't even know. After the only restart I have done since, I did the same thing. Towel Root 0 to 1 > Install SuperSU > Doesn't install correctly > Run root app > Grant app privileges > Delete SuperSU > Run app.
Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Sent from my Moto X
Jersey846 said:
I'm on Verizon as well. (4.4.2) It's a bit tedious (should be very easy), but seems to work with Titanium Backup for freezing apps. I'm not even exactly sure how I've gotten it working but here is what I did. I'd love for somebody to chime in and let me know why my "root" has been a bit unreliable.
1. Downloaded and ran TowelRoot. Changed the last number in the string from "0" to "1".
2. Download SuperSU (Doesn't seem to install correctly, but does seem to (at least temporarily) give root privileges to Titanium Backup and the root options for Greenify.. But here's how..
3. When installing SuperSU I get a notification telling me it fails to install properly. However when I try running a root app and it requests SuperSU root privileges, and I do get a pop up asking. I grant the app privileges. However that app doesn't seem to start correctly... Until after I deleted SuperSU. Then Titanium Backup starts easily and it seems to have root access as I've successfully frozen some apps through this method.
I'm sure that I am getting lucky somehow and either missing a step or two or... I don't even know. After the only restart I have done since, I did the same thing. Towel Root 0 to 1 > Install SuperSU > Doesn't install correctly > Run root app > Grant app privileges > Delete SuperSU > Run app.
Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Sent from my Moto X
Click to expand...
Click to collapse
Same thing I did. SuperSU doesn't seem to work, since it tries to update the SU binary every time you launch it. Just keep it on your device and don't open it. Should work for giving Root access.
dier325 said:
Same thing I did. SuperSU doesn't seem to work, since it tries to update the SU binary every time you launch it. Just keep it on your device and don't open it. Should work for giving Root access.
Click to expand...
Click to collapse
I might be missing something that you are doing then. Even if I keep it on my device but don't open it, it fails to give anything root access. Titanium, for instance, just gets stuck on the requesting root rights screen. If I delete SuperSU though, I'm able to somehow gain root for Titanium. Males no sense to a guy like me who doesn't always understand this kind of thing. Not very technically savvy.
Sent from my Moto X
Jersey846 said:
I might be missing something that you are doing then. Even if I keep it on my device but don't open it, it fails to give anything root access. Titanium, for instance, just gets stuck on the requesting root rights screen. If I delete SuperSU though, I'm able to somehow gain root for Titanium. Males no sense to a guy like me who doesn't always understand this kind of thing. Not very technically savvy.
Sent from my Moto X
Click to expand...
Click to collapse
Remove SuperSU, and try restarting your phone then applying Towelroot with 1 option again, and then check Titanium. I didn't need SuperSU to actually get root access. I only installed it because I wanted the power to deny things.
What do you mean change the number from 0 to 1? All I had to do when I loaded towel root was click "make it rain" I believe. It said I then had root but when I went into titanium backup, no root permissions were found. Is it because I didn't install superuser?
Sent from my XT1060 using XDA Free mobile app
dier325 said:
Remove SuperSU, and try restarting your phone then applying Towelroot with 1 option again, and then check Titanium. I didn't need SuperSU to actually get root access. I only installed it because I wanted the power to deny things.
Click to expand...
Click to collapse
Ok gotcha. I thought I actually had done that but no app actually gained permission till SuperSU, but I could be mistaken. Will give that a try.
Sent from my Moto X
---------- Post added at 09:06 AM ---------- Previous post was at 09:05 AM ----------
tu3218 said:
What do you mean change the number from 0 to 1? All I had to do when I loaded towel root was click "make it rain" I believe. It said I then had root but when I went into titanium backup, no root permissions were found. Is it because I didn't install superuser?
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
For the Moto X, we are supposed to change the last number in the Towelroot number string from 0 to 1. This can be achieved by triple tapping "Welcome to TowelRoot V3" in the TowelRoot app itself and then changing that last number from 0 to a 1.
Sent from my Moto X
Jersey846 said:
...Somebody did tell me in a different thread that I need to run PieRoot once and I'll be fine after that. Not exactly sure what he meant by that since I'm unfamiliar with PieRoot, so it's possible that is the necessary step in my method that is missing and causing all sorts of nonsense. If this is indeed the step I'm missing, I'd love precise and exact directions on how to run pie root.
Click to expand...
Click to collapse
PIE is the exploit/process that JCASE released to Root the X on 4.4.2 a little before Geohot released TowelRoot. Neither address write protection on the X, so there are some limits.
Since PIE was made specifically for the X, it will likely work better, more reliably.
But no matter how you root, if write protection is still enabled (which will be the case if you can't unlock your bootloader), you'll have issues with apps and things that rely on or require write permissions on /system, /system/bin, etc. That is the reason SuperSU is giving you problems.
Jersey846 said:
For the Moto X, we are supposed to change the last number in the Towelroot number string from 0 to 1. This can be achieved by triple tapping "Welcome to TowelRoot V3" in the TowelRoot app itself and then changing that last number from 0 to a 1.
Sent from my Moto X
Click to expand...
Click to collapse
Oh okay. See all I want root for is to use wifi tether. I will have try what you said later.
tu3218 said:
Oh okay. See all I want root for is to use wifi tether. I will have try what you said later.
Click to expand...
Click to collapse
What WiFi tether app will you be using or do you use? That is one of my things I want too. Tried one app yesterday and it didn't work.
Sent from my Moto X
Jersey846 said:
What WiFi tether app will you be using or do you use? That is one of my things I want too. Tried one app yesterday and it didn't work.
Sent from my Moto X
Click to expand...
Click to collapse
I Dont have one yet. Need to first try and get root.
Sent from my XT1060 using XDA Free mobile app
So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TPR like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3
Xposed causes WiFi to stop working... fix
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
prashantsingh480 said:
NOW firstly uninstall your xposed installer ,And the download the latest version v7.1 from repo.xposed.info/module/de.robv.android.xposed.installer
& install it..
IT SHOULD WORK..
& SORRY FOR MY ENGLISH
Click to expand...
Click to collapse
No luck....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk
Now it's not even seeing that there are networks in the area. [emoji20]
Sent from my Moto X (XT1053) using Tapatalk[/QUOTE]
first uninstall the xposed installer & then check if it catches the wifi network or not ..... :good::good:
Deleted
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
tnp9008 said:
The WiFi starts working after a hard reboot which makes xposed not work because I lose root after a hard reboot. Whether or not the xposed installer is installed or not doesn't make a difference. My WiFi is fine now that I did a hard reboot.
Sent from my Moto X (XT1053) using Tapatalk
Click to expand...
Click to collapse
NOW ,root your moto X by root master .
& check if it catches the networks or not if it catches.
the install xposed installer v7.0 not the latest (v7.1).
then check ...
SHOULD WORK ......
BEST OF LUCK....
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
rignfool said:
Does your phone reset the system partition after reboot?
If so... Try flashing xposed... Switch install method to manual recovery flash... Run the installer... Then reboot to recovery and flash the zip...
MotoX has a nasty system reset thingy... You have to look for the workaround in your device thread...
Why its borking WiFi... I'm not sure
Click to expand...
Click to collapse
I know my system partition is read only. The only way to have read/write is to unlock my bootloader which I could do but I don't want to lose my warranty so that's not an option right now. When the warranty runs out I plan to get an unlock code and obtain full root with system read/write but that's a ways off. I don't have custom recovery installed so I can't flash manually in recovery; the root access I gain is temporary. I have to re-root with Towel Pie Root after every full reboot. From what I read in the TPR thread people have had success using xposed on the Moto X like I'm doing, but for some reason it borks my WiFi.
Update: After digging through the TPR thread it looks like this is a somewhat common issue with TPR + 4.4.3 + Xposed. The TPR dev is looking into the issue.
Android pay doesn't seem to work with my bootloader unlocked rooted MotoX14. Is this a result of the root? Kinda bummed, has anyone else tried it?
Edit: disregard I fixed it. Simply uncheck "Enable Superuser" in the supersu app - Then verify your cards then recheck the "Enable Superuser" - Profit (err spend money)
I tried this, but I'm still getting a message that Google cannot verify that my device or the software running on it are Android compatible. Was this the same issue that you encountered? Are you running a custom ROM, and if so, which one? I'm on the latest Nexus Experience.
Guys you have to be on pure edition, and non rooted devices.
Sent from my XT1095 using XDA Free mobile app
Yes I was able to get my cards verified but when I tried to checkout it gave me an error at the register. I will try again at a different store, but it appears that the service does not like to play well with root/unlocked phones. I am on the stock Moto X lollipop 5.1 software, no ROM. I think ROMs are more temperamental in reference to Android Pay.
Thought, would turning off superuser through the SuperSU affect daily activities? I used root mainly to get tethering as well as some system modifications like volume panels and such. Would turning root off cause those to not work or only services that routinely need to access root (ie: Greenify)
I am having the same issue. Tried disabling superuser but get the same error. Also tried the xposed module No Device Check, didn't work.
Unlocked bootloader, stock rooted rom and xposed.
Need a way to get around this.
Same problem here. Stock Rom 4.4, super User disabled,no luck.
I'm having the same issue with the stock 5.0 rom, with unlocked bootloader, supersu disabled, twrp recovery, and xposed.
I've tried with rootcloak and no device check xposed modules too.
From what I've gathered reading other threads android pay doesnt like custom roms so I'm wondering if it's the changes that xposed makes that's causing issues or if it could be the custom recovery. Many people are having success just unrooting but that didn't work for me so there's more that's being flagged as not compatible in my setup. I've seen people saying they have no issues with unlocked bootloaders as well so really thinking it's recovery or xposed. I just don't use tap and pay enough to try wiping the phone and playing with settings though.
Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe
WOP_Drive said:
Same problem here. . . XT1095, stock 5.1, rooted, no XPosed. . . disabled SuperSU, rebooted, re-loaded credit card, same error. I even tried "permanently removing root". Same error.
Too bad. . . I've been geeking out since 2012 paying for items using Google Pay and NFC. . . guess I have to revert to the swipe
Click to expand...
Click to collapse
Did you reboot your phone after you disabled SuperSU? It worked for me and I had xposed installed
Yes.... I did reboot after disabling SuperSU.
I tried rebooting after disabling superuser and it still didn't work, I wonder if TWRP is causing the issue.
Never got it to work by disabling SuperSU. I even restored an old unrooted backup, but still no luck. However, I'm sure it's not TWRP. I loaded up a clean image, still using TWRP, and Android Pay worked. Go figure. Not sure what was wrong with my unrooted backup, but I can confirm Android Pay works when unlocked and on TWRP recovery.
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
Mine does not show modified, doesn't show that box at all actually.
I'm on 5.0 though, was that added to 5.1?
I am on 5.1, guess it's a new addition.
Has anyone tried re-locking the bootloader and then try getting Android Pay to work? I haven't yet. Here's an article that walks you through it using a Nexus device (not sure if it'll work on my XT1095).
article/video
I'm running stock 5.1 on a rooted XT1095 (bootloader unlocked) with TWRP. If anyone has step-by-step instructions that'll get Android Pay to work on this configuration, I'm "all ears"! THX!
Relocking the bootloader does not affect it.
Sent from my XT1095 using Tapatalk
I'm on 5.1 on an XT1095. I ended up restoring that stock OTB system image I mentioned over the non-rooted Nandroid backup I had. Works fine now. Still unlocked. Still using TWRP. I don't see that software status message under about phone though. Weird.
Sent from my XT1095 using Tapatalk
GatorsUF said:
Wonder if it has to do with the settings showing the system is "modified"?
Settings -> About phone -> Status
Click to expand...
Click to collapse
I'm on 5.1 pure edition, mine doesn't have "modified"
ksd316 said:
I'm on 5.1 pure edition, mine doesn't have "modified"
Click to expand...
Click to collapse
Does android pay work on you phone?
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
I know this has probably been done/said/repeated about 100 times, but did you toggle the "root authorization" in the three dots "general setting" menu after you hit "Try to Root" and rooting gets to 100%? If it doesn't work, try again. If it still doesnt work, turn off the phone, turn it back on, and start fresh with Kingroot. I didn't figure the toggling out the first time. Once I did, sunshine runs and passes all tests.
Agreed it sucks and it doesn't work flawlessly 100% of the time, and sometimes needs a reboot to work properly, but it does work. I just tested right now to confirm the procedure. I'm still not ready to buy / unlock but I've gotten to this point a couple times.
Try to factory reset your phone. Then try to use kingroot to unlock your bootloader. Should probably work.
Sent from my XT1254 using Tapatalk
Run Sunshine b4 kingroot then when its rooted go to settings unthick and thick root aut then switch to sunshine with recents button and cross fingers..if done quickly works like a charm
In all fairness calling kingroot **** when it doesn't even support the turbo is ridiculous. It has atleast allowed most to temp root and unlock and it's free.
Sent from my XT1585 using XDA Premium 4 mobile app
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
y8s said:
I know this has probably been done/said/repeated about 100 times, but did you toggle the "root authorization" in the three dots "general setting" menu after you hit "Try to Root" and rooting gets to 100%? If it doesn't work, try again. If it still doesnt work, turn off the phone, turn it back on, and start fresh with Kingroot. I didn't figure the toggling out the first time. Once I did, sunshine runs and passes all tests.
Agreed it sucks and it doesn't work flawlessly 100% of the time, and sometimes needs a reboot to work properly, but it does work. I just tested right now to confirm the procedure. I'm still not ready to buy / unlock but I've gotten to this point a couple times.
Click to expand...
Click to collapse
I did this about 20 times so far. It get's root, even Sunshine detects it sometimes, but then shortly after forgets it has root.
I'm not going to dig too much into this, but even with the issues, King Root is an amazing app if you think about it. Talk about ungrateful when a week ago we didn't think our phones would ever even be rooted let alone unlocked.
Keep trying and eventually it will work, or if you get fed up go build your own temp root, that's not too hard right?
Sent from my DROID Turbo using Tapatalk
Have you tried a factory reset or fxz'd back to stock first?
ostriches3064 said:
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
Click to expand...
Click to collapse
After multiple attempts this method worked for me also.
Sent from my XT1254
golgothagecko said:
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
Click to expand...
Click to collapse
Try the desktop version of Kingroot. I had your very same problem and once I tried the desktop version, everything went as it was supposed to go. Beware that the interface is in Chinese, but very intuitive though, so just click on the highlighted button.
After no less than 3 hours of fighting with Rootking, I finally got this phone rooted. Whew!
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Kingroot worked like a charm for me. It did take a few tries and a couple of reboots. Sunshine recognized root for me however and I purchased the unlock code. I am now running resurrection remix ROM and I am loving it. $25.00 may sound expensive to some. However, I never thought I would be able to root and unlock this phone being a Motorola. Just keep at it and eventually you will attain root and be unlocked. Most definitely worth it.
dnwhome3 said:
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
ostriches3064 said:
I also had trouble with king root until I tried this:
1) Install both sunshine and king root
2) Run king root
3) While king root is running switch to sunshine and go through the steps. It should say that it is rooted (at least is did for me)
4) Once your bootloader is unlocked, re-run king root to get actual root.
5) Flash twrp
6) uninstall king root from the app setting
7) flash supersu from twrp
8) run the beta apk of super su
9) profit
Hope this helps
Click to expand...
Click to collapse
For step 6, I assume you mean open up the kingroot app, go to the settings and select uninstall? When I do that I get a warning that I will lose root access. Is that true? Will flashing supersu in step 7 once again give me root?
m4rk0358 said:
For step 6, I assume you mean open up the kingroot app, go to the settings and select uninstall? When I do that I get a warning that I will lose root access. Is that true?
Click to expand...
Click to collapse
You are correct on the first question. For you second, you'll lose it temporarily, if at all. As soon as you uninstall king root, boot into twrp and flash supersu. Then run the beta apk from another thread (i forget which one) and you will have root. As proof, I'm running apps such as adaway, xposed, etc.
golgothagecko said:
My ability to purchase and use Sunshine has been thwarted by this horrible root APK known as Kingroot. I've rebooted my phone more times than I can count. I get root some times, but then it quickly forgets it actually has root. Even the root junky video posted below had issues with it. We really need a more reliable temp root method.
Click to expand...
Click to collapse
Yeah it is a nuisance, but I enabled airplane mode started my WiFi, installed sunshine, installed kingroot, installed flashify, ran kingroot, it failed rebooted, ran sunshine got to the checking for root part, hit home, started kingroot, rooted at about 50% used recents to switch to sunshine, it asked for permissions, granted them, ran sunshine. Rebooted, ran kingroot again, at 50% started flashify, granted root, flashed twrp, rebooted into twrp did the fix write permissions thing it asks you about on first twrp boot, rebooted, rooted once more with kingroot (its now stable) uninstalled kingroot (because you can after it is stable) and downloaded supersu, and rebooted into recovery and flashed supersu.
Sent from my DROID Turbo using XDA Free mobile app
dnwhome3 said:
Although it was very frustrating for a day and a half, Kingroot finally worked for me. The three dots did not open a menu so there was no setting to toggle authorizations, only the per-app settings once an app requested root. Trying to use it more than once between reboots was a waste of time. In the end, it was: reboot; run sunshine to just before it needs root; run kingroot; and as it rapidly approaches 100%, switch back to sunshine and let it finish. It took well over 30 tries for me.
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
Are you looking at the 3 dots in the upper right or the broken 3 dots at the bottom? I'm talking upper right. The bottom one is vestigial and you can ignore it.
Remember to do it AFTER you get to 100% root. Not at this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
y8s said:
Are you looking at the 3 dots in the upper right or the broken 3 dots at the bottom? I'm talking upper right. The bottom one is vestigial and you can ignore it.
Remember to do it AFTER you get to 100% root.
Click to expand...
Click to collapse
I never would have guessed that the auth setting doesn't show up until later.
Ok so I have managed to get sunshine to work by using king root through the process described earlier and I now have an unlocked bootloader. I am not sure however how to go about getting my root access to be more permanent so I don't have to try and use king root. I don't want to install any custom ROMs of any sort at this point, just looking to get root access for apps.
Also a side question has anyone been able to or come up with a method to relock the bootloader on this device?
I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!
https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
mew1033 said:
I've got an app I'd like to use that somehow keeps detecting root. It's called Blind (https://play.google.com/store/apps/details?id=com.teamblind.blind)
I've also got Pokemon Go installed, but that works just fine. Not problems with Magisk Hide.
I'm ready and willing to provide logs and such, just not sure where I should start.
Thanks!
Click to expand...
Click to collapse
Did you ever figure it out?
Just. Tried too. For test lol.
Didn't work for me.
I'm having issue with spay for gear 3.
If you can figure it out and maybe we can also both our issues
It suddenly started working for me today...
I was having this issue too. I eventually got so frustrated, I unrooted my device, relocked the bootloader, and did a factory reset. Still thinks I'm rooted, even though I'm completely factory. I think they get some unique device identifier and block your device server-side
If anyone figures it out, please let me know.
A bit of an annoying workaround: if you can make a comment with a different phone, and you get a notification telling you someone replied, you can open the app by tapping on the notification. However, it won't work if you open it by tapping on the icon
Any update?
Tried a whole bunch of things to hide Magisk. Blind just doesn't work.
Works!
Looks like Blind is detecting if your bootloader is unlocked. I installed this Magisk module called "SafetyPatch", which prevents apps from detecting if your bootloader is unlocked. That fixed it for me!
Darn, tried installing SafetyPatch, but still no luck
I suspect my phone has been blacklisted or something
I had checked logcat and it seems that blind was using com.liapp.lockincomp to detect root and display the alert. after hiding magisk manager and using magisk hide on blind it still didn't work even after clearing data/reinstalling the app. after a few days it magically started working again. guess they blacklist devices for x amount of time after they detect root.
I had Blind 2.5 and Magisk 17 working together. About two weeks ago I updated both and it stopped working. Anyone using Blind 2.6 with Magisk 18? I think my device got banned - downgrading Blind to 2.5 didn't help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Seeing the issue on Blind 2.6.4 with Magisk Hide Enabled. Any other suggestions on a workaround?
Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.
babelus said:
Waited one week, installed Blind 2.5 from a backup and it works fine with Magisk 18.
Click to expand...
Click to collapse
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?
1nv1n said:
So you uninstalled it & re-installed it after a week?
When you say backup, do you mean an APK that you had backed or a backup taken from TiBackup?
Click to expand...
Click to collapse
Correct, uninstall Blind, wait a week, reinstall from backup of APK (TitaniumBackup). I can share the APK, but you shouldn't trust me.
I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.
1nv1n said:
I uninstalled Blind. Uninstalled Xposed. Made sure Magisk was able to pass all SafetyNet checks. Re-installed Blind from the Play Store. Used Magisk to hide it & was able to launch it without issues.
Click to expand...
Click to collapse
Thanks for sharing, this worked for me
(Rooted stock Moto Z2 Force with Oreo)
Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?
1nv1n said:
Looks like it's broken again? I tried following the same process; but even after being hidden through Manager, it's still able to detect either root or bootloader unlock.
Anyone got any ideas?
Click to expand...
Click to collapse
I can confirm my workaround using the old version of Blind stopped working. New version works for a day or two after installation, then it detects root and I have to uninstall and wait for the ban to expire.
How many days does the ban last for?