So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
chickentech said:
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
Click to expand...
Click to collapse
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
buru898 said:
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Click to expand...
Click to collapse
metpage said:
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
Click to expand...
Click to collapse
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
formula91 said:
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
Click to expand...
Click to collapse
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
chickentech said:
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
Click to expand...
Click to collapse
Have you tried doing Android Pay before restoring stuff from Titanium Backups? There is a slim possibility that it may be altering something from system, making it fail the safetynet checks.
I would try flashing the zip from TWRP instead of sideloading as well. Just in case.
chickentech said:
...
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Click to expand...
Click to collapse
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
sn0warmy said:
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
Click to expand...
Click to collapse
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Update: Reddit user MajorNoodles has informed that Android Pay works on his Nexus 5. Chainfire, on his Google+ post, does mention that the working of Android Pay is by accident and not by design. He expects Android Pay to be updated in the future to counteract this.
Click to expand...
Click to collapse
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
nvm
PhoenixTank said:
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
Click to expand...
Click to collapse
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
chickentech said:
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
Click to expand...
Click to collapse
If you're rooting to modify the hosts file to block ads.... that changes system, and will trip Android Pay's SafetyNet checks. The best adblocking I can get without changing System is Adblock Plus for Android. (Root on ABP seems to only allow some sort of localhost proxy network rerouting instead)
FYI Safetynet Playground trips for me, but Android Pay works just fine.
UPDATE: Weird, now I pass, must be because I recently re-encrypted my phone.
So now it's confirmed, I can use Android Pay and not trip SafetyNet API. Neato.
Thanks! That hosts file was it.. A fresh install and I'm gold with Safetynet Many thanks all around!
You're very welcome!
Right now I'm using adblock plus + a "patcher" that's pretty "lucky" heh.
Hi there everyone !!
I gone a long way till now...
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/how-to-enable-oem-unlocking-bricked-t3249003
And now I'm trying to get full Stock phone with Encryption, Locked oem and systemless Root without No warnings. = S E L R N
As far as I went was S R N when i tried to encrypt it got stucked on colorful bubbles screen.
Anyone got idea how to reach this ?
Did somone checked is AdAway after changing location of host file and symlinking it, stops Google Pay/Makes additional warning while booting ?
Related
Losing Android Pay is really the only thing keeping me on the stock ROM. Is this something that devs are even looking into or has everyone just resigned themselves to not using it if you want a custom ROM?
goodtimes50 said:
Losing Android Pay is really the only thing keeping me on the stock ROM. Is this something that devs are even looking into or has everyone just resigned themselves to not using it if you want a custom ROM?
Click to expand...
Click to collapse
Easy enough to achieve, depends on how the developer implements root in their ROM.
I am on LeeDroids ROM and Android pay works.
chazall1 said:
I am on LeeDroids ROM and Android pay works.
Click to expand...
Click to collapse
Really?! Have you actually added a card and used it to make payments via NFC?
chazall1 said:
I am on LeeDroids ROM and Android pay works.
Click to expand...
Click to collapse
I don't believe you.
I checked the LeeDroid thread and multiple people have reported it working. I'd just be paranoid with every AP update that it will no longer work.
Speaking off android pay, can you hide the annoying NFC icon from statusbar without root? I use my mobile banking app a lot and my bank app won't work with rooted phones (found that out on my M8). I am aware that I need the NFC on for Android Pay to work but I wish it could just turn itself on when needed
Rotten Ross said:
Speaking off android pay, can you hide the annoying NFC icon from statusbar without root? I use my mobile banking app a lot and my bank app won't work with rooted phones (found that out on my M8). I am aware that I need the NFC on for Android Pay to work but I wish it could just turn itself on when needed
Click to expand...
Click to collapse
No, unfortunately you're stuck with the icon without root.
Android Pay also works on Badboyz Sprint ROM. I used it yesterday at Walgreens.....
I have been making payments for a week now. Can add delete cards
Give it a try
Great news! Thanks guys!
failedjedi said:
I don't believe you.
Click to expand...
Click to collapse
You can believe what you want, Unlocked, Rooted, S-offed on BadBoyz ROM and Android Pay works.
chazall1 said:
I have been making payments for a week now. Can add delete cards
Give it a try
Click to expand...
Click to collapse
Hi. Noob, kinda, here...
I'm on LeeDrOid r110, systemless xposed and SuperSu, but have yet to get Android Pay to work. I've even tried disabling Xposed and SuperSu, which only crashes as I try to add a credit card, specifically, once I press the "+" icon, my screen goes black, then it crashes and I get the Android Pay white loading screen. How do you have it set up?
Oh, I'm on 1.80.xxxx, S-Off...
k_l_o said:
Hi. Noob, kinda, here...
I'm on LeeDrOid r110, systemless xposed and SuperSu, but have yet to get Android Pay to work. I've even tried disabling Xposed and SuperSu, which only crashes as I try to add a credit card, specifically, once I press the "+" icon, my screen goes black, then it crashes and I get the Android Pay white loading screen. How do you have it set up?
Oh, I'm on 1.80.xxxx, S-Off...
Click to expand...
Click to collapse
Xposed breaks android pay as it modifies the system. How are you "disabling" it? Did you flash the removal .zip in recovery? If not I would try that first and see if you can get Android Pay working. If you have done that and android pay is still not working I would flash the appropriate RUU to get back to stock, unrooted, then go through the steps to root (systemless) and flash your rom, but do not install xposed. It SHOULD work after that.
BladeRunner said:
Xposed breaks android pay as it modifies the system. How are you "disabling" it? Did you flash the removal .zip in recovery? If not I would try that first and see if you can get Android Pay working. If you have done that and android pay is still not working I would flash the appropriate RUU to get back to stock, unrooted, then go through the steps to root (systemless) and flash your rom, but do not install xposed. It SHOULD work after that.
Click to expand...
Click to collapse
Hi Bladerunner.
Thanks for replying. Didn't realize how old this thread was until after posting.
I'm using the Systemless Xposed v85.7 from this thread:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
There's a "Disable Xposed" toggle, I guess similar to SuperSu also has a toggle. I want Xposed more than I want Android Pay. Maybe these people that are Unlocked, Rooted, S-Off, and running LeeDrOid don't have Xposed install and that's why their Android Pay is working.
Anyway, I'm just a bit OCD or unrealistic in thinking I can have it all.
And I would "Thank" you, but reached my quota today. Will make up tomorrow.
Cheers...
Android Pay works without issue on a systemless rooted stock ROM even... Just don't modify system and you're good. For now anyway.
schmeggy929 said:
You can believe what you want, Unlocked, Rooted, S-offed on BadBoyz ROM and Android Pay works.
Click to expand...
Click to collapse
Hi schmeggy.
Any chance you don't have Xposed installed? I don't see it listed in your signature. I think that's the true culprit. Beside being on different ROM, I'm on LeeDrOid which is systemless, Xposed is the only difference with your setup.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
EtherealRemnant said:
Android Pay works without issue on a systemless rooted stock ROM even... Just don't modify system and you're good. For now anyway.
Click to expand...
Click to collapse
Thank you for your feedback.
I've tried to maintain systemless, but still no joy. There are posts that state Android Pay works for them and my HTC 10 would be complete if I can solve this issue.
FYI...
Since I love picking at scabs, can't leave well enough alone, and have a severe case of update-itus, last one is a whole different can of worms, I followed my hunch and hope this will help anyone else curioused/interested.
I dirtied flashed my ROM, LeeDrOid, which delete/wrote-over, idk because they're the geniuses, not me, the Xposed Framework, I was able to verify via SafetyNet Helper and being able to add a credit card in Android Pay, that YES, Xposed Framework bunks Android Pay. I will try to make a purchase during lunch today and will update.
k_l_o said:
Hi schmeggy.
Any chance you don't have Xposed installed? I don't see it listed in your signature. I think that's the true culprit. Beside being on different ROM, I'm on LeeDrOid which is systemless, Xposed is the only difference with your setup.
---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------
Click to expand...
Click to collapse
I see you found the issue, No I do not use Xposed.
k_l_o said:
FYI...
Since I love picking at scabs, can't leave well enough alone, and have a severe case of update-itus, last one is a whole different can of worms, I followed my hunch and hope this will help anyone else curioused/interested.
I dirtied flashed my ROM, LeeDrOid, which delete/wrote-over, idk because they're the geniuses, not me, the Xposed Framework, I was able to verify via SafetyNet Helper and being able to add a credit card in Android Pay, that YES, Xposed Framework bunks Android Pay. I will try to make a purchase during lunch today and will update.
Click to expand...
Click to collapse
Too bad we havent been able to figure out a xposed app that tricks safetynet api into thinking its all good, then we could have it all
yea, even with systemless xposed, you still need to disable xposed via the toggle switch, and then reboot to get android pay to work. I managed to get my 2gb of free verizon data for making 3 soda purchases at work. Although, on a semi related note, android pay doesnt like one of my CC's with SE chip, it likes my other 2 just fine.
Hi guys,
I was using Pure Nexus for a long time and didn't have an issue with this, but now I'm on stock and my Verizon plan is a legacy plan that doesn't allow me to have WIFI tethering.
What is the best way to do this on Oreo 8.1?
I assume it's using ElementalX Kernel and changing the code to say true, I don't remember the command line
Should I be doing it this way? If so what recovery should I be using with Oreo 8.1?
Do I flash it differently than 7.1 Nuget? (boot to bootloader, boot to RC1 TWRP image, install TWRP zip)
Thanks ahead of time
I'm with him. Coming from a nexus 6 to a pixel 2XL and need pointed in the direction to a ROM or whatever the solution is now to unlock the hotspot on big red. Still on a grandfathered plan. Thanks in advance.
Add net.tethering.noprovisioning=true to your build prop (I use JRummy's Build.prop editor, just add the line to the bottom of the file). I also believe there is a Magisk module for this.
funkybrunk said:
Add net.tethering.noprovisioning=true to your build prop (I use JRummy's Build.prop editor, just add the line to the bottom of the file). I also believe there is a Magisk module for this.
Click to expand...
Click to collapse
This means I need to be rooted... I assumed the same.
What are you running to be rooted on Oreo 8.1? My assumption is it's different than Nuget 7.1 since I had issues doing it the same way.
fsuagentsmith said:
This means I need to be rooted... I assumed the same.
What are you running to be rooted on Oreo 8.1? My assumption is it's different than Nuget 7.1 since I had issues doing it the same way.
Click to expand...
Click to collapse
I haven't had to reroot in a while, Last time was when 8.0 was released. I used the guide here:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324
All subsequent monthly updates and update to 8.1 were applied using flashfire, and root was maintained via everroot (function in flashfire). I honestly don't understand why more people don't use FF to update, it definitely is the easiest. Just make sure to clean themes before updating.
funkybrunk said:
I haven't had to reroot in a while, Last time was when 8.0 was released. I used the guide here:
https://forum.xda-developers.com/pixel-xl/how-to/guide-how-to-systemlessly-root-pixel-xl-t3660324
All subsequent monthly updates and update to 8.1 were applied using flashfire, and root was maintained via everroot (function in flashfire). I honestly don't understand why more people don't use FF to update, it definitely is the easiest. Just make sure to clean themes before updating.
Click to expand...
Click to collapse
Thank you, I'm following this post and have now a stupid problem.... my encryption password is incorrect, not sure why. Any idea on where to find out what I used (even though I know what I used when setting up the phone from scratch)
I just did a factory reset and started over to make sure I wasn't going crazy.... still no dice. TWRP is not accepting my encryption password.
Update:
I was told in another thread that this is a known issue with TWRP and Oreo 8.1. The only fix was to remove the PIN after boot and work from there. I have done this and your directions worked. Thanks
Hey, fsuagentsmith
Did you enable hotspot on 8.0/8.1?
Let me know, cause I'm ready to jump off the pure Nexus too!
fsuagentsmith said:
Thank you, I'm following this post and have now a stupid problem.... my encryption password is incorrect, not sure why. Any idea on where to find out what I used (even though I know what I used when setting up the phone from scratch)
I just did a factory reset and started over to make sure I wasn't going crazy.... still no dice. TWRP is not accepting my encryption password.
Update:
I was told in another thread that this is a known issue with TWRP and Oreo 8.1. The only fix was to remove the PIN after boot and work from there. I have done this and your directions worked. Thanks
Click to expand...
Click to collapse
.me said:
Hey, fsuagentsmith
Did you enable hotspot on 8.0/8.1?
Let me know, cause I'm ready to jump off the pure Nexus too!
Click to expand...
Click to collapse
Yes I did.
Sorry I didn't see your post till just now as I don't contribute much on this site. I kind of know what I'm doing but I'm too busy to be a big contributor.
Thanks for asking.
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
I Could Be Dead Wrong But..
epickid37 said:
I want to install magisk, but I still want to be able to take ota updates. I also want to keep the stock recovery if possible. Is there a good way to do this, or will I have to flash TWRP?
Edit: it looks like magisk v15 is bricking 7x's. Should I wait a bit before I try to install it?
Click to expand...
Click to collapse
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
RaiderWill said:
I Do Believe You Need To Be Rooted To Install Magisk...
And to root you have to Unlock your Bootloader.
Your device will Reject Any and All O.T.A.'s with an Unsecure (A.K.A. Unlocked) Bootloader.
That's why you get that hidious *Warning!* message everytime you reboot.. your device knows it's unsecured.
You can sideload all the upcoming O.T.A.'s when someone makes them available.. I kinda doubt that is going to be on day one though.
The Nice thing about those of you that are rooting is, you can just pay the $18.00 bucks and bring your phone back to stock with that D.C. tool that is being discussed in the Q & A.. I assume it works on all variants ?
Anyway.. good luck to you if you do decide to go ahead and unlock that Bootloader.
Click to expand...
Click to collapse
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Damn.. It's Been So Long..
epickid37 said:
Magisk is a rooting method, I know from experience that you don't already have to have a rooted phone. Also magisk v14 added a feature where you could patch the boot image and flash it via adb.
What's this "D.C. tool"? It sound interesting
Click to expand...
Click to collapse
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
RaiderWill said:
You Are 100% Correct...
You're conversing with an old "SuperSu" guy here.. I totally forgot mag's is a rooter like Su.
But you still have to Unlock that loader to make it happen.. You are not going to get any O.T.A.'s
I know Magisk can hide root for things like netflix... But not to recieve Vendor Updates.. unless things have changed drasticly.. please correct me if I'm wrong..
But again.. sideloading is always an option.
Click to expand...
Click to collapse
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
A Virgin...
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
When It Comes To Huawei.. I'm A Virgin...
Every other phone I've seen, the O.T.A. will notify you that your system has been "Modified" and will not attempt the update.
When you root.. Your Phone Becomes Insecure.. and is vernable to Malware, Virus, Hacks and god knows what else.
O.T.A.'s are Signed Packages.. They Ain't Going To Da Hood To Do Business...
Keep it locked if you want everything on day 1.. Then you can Root to your hearts content.
epickid37 said:
I'm probably wrong, but from what I've read, you can still take ota's with an unlocked bootloader?
Click to expand...
Click to collapse
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Note u definitely can't take OTA updates with Magisk installed. What's worse is the normal recovery doesn't have a proper update option so u'll have to use Huawei's Dload method which fails if u have tampered the system. Restoring to the stock ROM with a locked bootloader is also incredibly hard on Huawei/Honor devices.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
epickid37 said:
Here's how to take ota updates with magisk. But what your saying is Huawei doesn't use recovery to update, they use proprietary methods that detect system modifications, right?
Click to expand...
Click to collapse
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
ayush rao said:
Thats not what I meant, Huawei does use the recovery to update like any other phone but their recovery doesn't let the user to sideload their own OTA files. U'll have to use their Dload method which is an absolute pain.
Further, the Magisk page u posted here mentions the system and vendor must not be modded so that means you can't use any app like Titanium Backup to block or uninstall apps since it tampers the system. Thats really annoying since the whole point of rooting is to modify the system. Also if u used TWRP then u will have a hard time trying to find the right recovery file corresponding to the firmware u r on. It is really hard for Honor devices since u'll have to download a large file and, using a tool on XDA, extract the images u need. IMO rooting this phone is worth it right now especially since it is new and will constantly be recieving OTAs in the coming months.
Sent from my Honor 8 using XDA Labs
Click to expand...
Click to collapse
Ah, ok. Thank for your help!
OK, I just bought a new Moto Z2 Play, and I of course, want to Root it. I have done Root on all my previous smart phones so I have some experience. I read thru all the threads here, but still have some remaining questions.
Where can I get the latest Moto drivers for Win 10 64-bit? I rather have just the drivers, if possible, than some other bloat Moto utilities too.
Where can I get the latest ADB ? I know, there are lots of sources if I search, but I am looking for a safe copy.
What do I use for TWRP? TWRP 3.2.1-0 ? [TWRP][64 bit][3.2.1_r12] ? Alternate TWRP v3.1.1.0 ? I am even asking, because I read a post and its reply, that mentioned that the 64-bit had to be used, but I haven't seen that mentioned anywhere else.
As part of TWRP, should I do the "Swipe to allow modifications for /system" ? I have read posts suggesting either way, and remain unsure which is best.
I plan to install the latest Magisk Manager, v5.5.5. Or should I install simply Magisk v15.3?
Should I plan to Hide the Magisk Manager?
Do I need to, also, install SuperSU and BusyBox from the Google Play Store?
Is there anything additional I need to do, to successfully handle Safety Net ?
Thanks!
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
First, let me start with a heartfelt thanks! :highfive:
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
Click to expand...
Click to collapse
Yes, but it has instructions like this:
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Click to expand...
Click to collapse
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
WaltA said:
First, let me start with a heartfelt thanks! :highfive:
Yes, but it has instructions like this:
Which is why it left feeling unsure, do I swipe or not? Is having the system partition modified "good" and a normal part of this type of root'ing?
Plus, the mention of flashing SuperSU, lead to my question about going that (which you replied 'no').
Maybe I am simply having a case of information overload. With possibly, a strong addition of having too many different opinions which might not all be valid.
Click to expand...
Click to collapse
I'm glad you have read! :good:
I understand you're dilemma and have also experience info overload, when researching rooting / flashing procedures. It never hurts to read it, yet again and watch any YouTube videos available on the subject.
I always swipe to allow modifications when installing TWRP. Otherwise, TWRP will be in READ ONLY mode.
I am not certain about Busy Box, but haven't needed it. Magisk has A Super User function, so SuperSU is not needed.
I am no expert, just trying to help, so please don't take anything I've said as the gospel. Read everything and then read it again.
pizza_pablo said:
Did you read?
https://forum.xda-developers.com/z2-play/how-to/guide-resource-help-thread-t3627615
I used Juniors version of TWRP.
https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Yes to Magisk Manager.
Yes to Magisk.
No to SuperSU.
No to Busy Box.
Click to expand...
Click to collapse
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Click to expand...
Click to collapse
No. I'm still on Nougat. I have no interest in Oreo, for this device.
The Analog Kid said:
Any hint up to which 8.0 security patch update will @Junior Passos method will work
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I'm on August security patch.
Note: Systemless root is not an option on this box due to locked bootloader, do not tell me that root is not an option, because I am rooted right now.
I rooted my Fire TV 2 (FireOS 5.2.7.1) with the hardware method using SuperSU in system mode, although whenever I open SuperSU it immediately crashes. It still comes up with root prompts and I can still accept them, but I can't actually open the app and change settings because it just instantly crashes. Is there a fix for this?
If there isn't a fix for this issue, are there any other SYSTEM MODE superusers that do the same thing as SuperSU.
(Magisk is systemless root, so it doesn't meet the criteria above.)
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Sus_i said:
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
Click to expand...
Click to collapse
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Sus_i said:
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Click to expand...
Click to collapse
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Bertonumber1 said:
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Click to expand...
Click to collapse
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
dovedescent7 said:
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
Click to expand...
Click to collapse
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Bertonumber1 said:
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Click to expand...
Click to collapse
I was told that you have to update to the latest version of FireOS and those versions are extremely broken. I can't use that unlock method unless someone finds a way to do it without updating to the latest firmware.
Sus_i said:
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Click to expand...
Click to collapse
It's not an option because the unlock requires an update to the latest firmware (stock firmware) or so I was told.
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Toothless_NEO said:
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Click to expand...
Click to collapse
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Sus_i said:
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Click to expand...
Click to collapse
Interesting, Why does It work to change the theme in Xposed and not through preferences and/or modding the app?