I really really miss exposed and I really don't want to root as besides exposed I personally have no need to. I just can't seem to get virtual exposed up and running. Along with not finding and good hot to videos on YT. I get it installed and everything just no luck with actual installing module for some reason. TIA for all help or input
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
spart0n said:
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
Click to expand...
Click to collapse
If I rooted I wouldn't need to run virtual or magisk I could just run Xposed. I just don't want to root as it's easier for OTA without root. Especially seeing how often updates are coming for this phone since it got released.
lg3FTW said:
If I rooted I wouldn't need to run virtual or magisk I could just run Xposed. I just don't want to root as it's easier for OTA without root. Especially seeing how often updates are coming for this phone since it got released.
Click to expand...
Click to collapse
I don't see how you can get xposed running without being rooted but I am a noob at this still lol
spart0n said:
I don't see how you can get xposed running without being rooted but I am a noob at this still lol
Click to expand...
Click to collapse
It's called virtual Xposed. It's what my post is mostly about getting it running on the phone. No worries we are all rookies one time or another
lg3FTW said:
It's called virtual Xposed. It's what my post is mostly about getting it running on the phone. No worries we are all rookies one time or another
Click to expand...
Click to collapse
I understand your desire not to root, but the only downside to rooting wousl be security, and magisk keeps security intact. Edxposed (unoffical Xposed for Android P) works perfectly fine in magisk.10/10 would recommend. Plus magisk has methods for maintaining root after OTAs
Cm4nXD said:
I understand your desire not to root, but the only downside to rooting wousl be security, and magisk keeps security intact. Edxposed (unoffical Xposed for Android P) works perfectly fine in magisk.10/10 would recommend. Plus magisk has methods for maintaining root after OTAs
Click to expand...
Click to collapse
I bought the unlocked model for root truly but I haven't rooted a phone in 3 years since my LG g3 and g4 and for some reason I can't seem to wrap my head around easiest and safest way to root the OP7 . Don't want to break it. Nicest phone I've ever owned.
There's a tool by the guy who maintains TWRP for the phone. It's called tool all in one and can unlock and root your phone with a simple GUI. OTAs are almost as simple as stock, just 2gig files instead of ~500mb. It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, reboot
Arden144 said:
There's a tool by the guy who maintains TWRP for the phone. It's called tool all in one and can unlock and root your phone with a simple GUI. OTAs are almost as simple as stock, just 2gig files instead of ~500mb. It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, reboot
Click to expand...
Click to collapse
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
lg3FTW said:
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...fully-upgraded-to-9-5-7-t3937414/post79679795
Have you tried TaiChi? It's an alternative to virtual exposed.
lg3FTW said:
All that seems amazing and I love the tool kits made for other devices heck I remember rooting GB when it was a one click app just to root your device. Miss those days. I'll have to search more as you really lost me with this part.
It's just download from oxygen updater, settings local install, TWRP retention script, Magisk inactive slot install, r
Click to expand...
Click to collapse
I don't think you even need the all in one GUI. It's a very simple process.
Kinda Easy to follow Guide
MORE COMPREHENSIVE GUIDE
spart0n said:
if you root with magisk there is a module for xposed framework but it looks old and it says it won't be updated and I haven't tried it
Click to expand...
Click to collapse
Yes, but there's EdXposed which is compatible and works flawlessly with Safety net. Not all modules work but that's an Android Pie incompatibility issue, not an Xposed problem.
---------- Post added at 17:13 ---------- Previous post was at 17:09 ----------
lg3FTW said:
I bought the unlocked model for root truly but I haven't rooted a phone in 3 years since my LG g3 and g4 and for some reason I can't seem to wrap my head around easiest and safest way to root the OP7 . Don't want to break it. Nicest phone I've ever owned.
Click to expand...
Click to collapse
It was amazingly easy. You just enable developer option, select enable OEM unlocking, back everything up (the phone will get factory reset) and advanced reboot, hook it up to your computer, reboot to bootloader, and then fastboot OEM unlock, reboot your phone to make sure the warning appears and reinitialise the system (since your phone did just get reset), reboot to bootloader, fastboot boot twrp.img, optionally flash the twrp installer, and flash Magisk. Done. Rooted. After installing OTAs, but before rebooting, use the install to slot B option in Magisk manager.
Lirannl said:
Yes, but there's EdXposed which is compatible and works flawlessly with Safety net. Not all modules work but that's an Android Pie incompatibility issue, not an Xposed problem.
---------- Post added at 17:13 ---------- Previous post was at 17:09 ----------
It was amazingly easy. You just enable developer option, select enable OEM unlocking, back everything up (the phone will get factory reset) and advanced reboot, hook it up to your computer, reboot to bootloader, and then fastboot OEM unlock, reboot your phone to make sure the warning appears and reinitialise the system (since your phone did just get reset), reboot to bootloader, fastboot boot twrp.img, optionally flash the twrp installer, and flash Magisk. Done. Rooted. After installing OTAs, but before rebooting, use the install to slot B option in Magisk manager.
Click to expand...
Click to collapse
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
oregonhynita said:
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/how-to-convert-tmobile-op7-to-t3935947
oregonhynita said:
Do you know if TMobile one plus 7 pro be rooted as well? I've seen people say yes and people say no. Which carrier do you have?
Click to expand...
Click to collapse
I've been told you can, but I don't have one of those. Carriers are mostly irrelevant outside of the US (and I live outside of the US myself). I use the international, carrier agnostic model (1917).
Related
Late last year, with my HTC M8, I remember there was a systemless root SuperSU version that allowed me to have a stock rooted ROM and still use Android Pay. I read yesterday there is an experimental version of Xposed that is systemless and lets you use Android Pay with one reboot to turn Xposed off and no need to rebuild the app cache when turning it back on. Doubt there is a Samsung version of that yet but may come eventually. My question is if anyone has tried a stock ROM (or ordin to stock), systemless root, and been able to use Android Pay?
Yes. I am using stock LP with systemless root and Android Pay working perfectly.
theophile2 said:
Yes. I am using stock LP with systemless root and Android Pay working perfectly.
Click to expand...
Click to collapse
I went ahead an odin'd back to stock MM and then took the OTA update to latest. Then used odin to flash TWRP, twrp-3.0.2-0-M-nobleltespr.tar. Booted in recovery and flashed SuperSU, BETA-SuperSU-v2.74-2-20160519174328. Once that all was done I checked if my phone would still pass the SafetyNet check that Android Pay uses and it passed! So systemless root and stock android MM. Then I went ahead and tried the new systemless version of Xposed. http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 It flashed and works fine. I can disable xposed, reboot, and then I still pass the SafetyNet check (so pay should work but haven't tried yet). Enabling Xposed and rebooting is super quick and doesn't require a rebuild of the apps like it used to. I'm not sure what type of system modifications may cause the SafetyNet app to fail so all I've done so far is remove Voicemail (I use Google Voice) and have AdAway installed to block ads. I have the xTouchWiz, CrappaLinks, YouTube Ad Away, and Amplify Xposed modules installed and working.
Let me see if I understand this correctly. You're rooted without tripping knox?
hotspace said:
Let me see if I understand this correctly. You're rooted without tripping knox?
Click to expand...
Click to collapse
Definitely not! I haven't heard of a single person being able to root and not trip knox. I'm talking about Android Pay which doesn't care about Knox. Samsung Pay will not work.
I did make a purchase the other day with Android Pay too. Just needed to disable systemless xposed in the app, reboot, and then pay worked fine
Nice...Cool. is there a write-up anywhere on how you guys did this?
As for Samsung pay, I use Capital One and USAA. Neither of these guys participate...so I'm SOL and considering tripping knox. I can't use either of the secure payment methods.
hotspace said:
Nice...Cool. is there a write-up anywhere on how you guys did this?
As for Samsung pay, I use Capital One and USAA. Neither of these guys participate...so I'm SOL and considering tripping knox. I can't use either of the secure payment methods.
Click to expand...
Click to collapse
I pretty much described how I did it above. Just used odin to put the stock .tar on, then took OTA updates, then installed TWRP via ODIN, then SuperSU, and eventually systemless Xposed. All the info is around the sprint forum for more details on each step. Since you're already stock you can probably just skip right to TWRP. That step will trip knox!
For whatever it's worth, I found that I had to delete /su/xbin_bind before Android Pay would work. Here are the steps that worked for me:
celsian said:
For those who are confused, here are my steps for using Android Pay while rooted.
1. I reset my phone to factory defaults by installing all original software.
2. Unlocked the boot loader.
3. Installed TWRP, but kept it read only.
4. Installed Beta Super User 2.67
5. Through Android terminal after entering su and allowing terminal emulator root access:
6. rm -r /su/xbin_bind
7. chmod 751 /su/bin
Android Pay works, root is still active. Thanks all.
Click to expand...
Click to collapse
Doing it this way, Android Pay "just works" with root, no need to "unroot" or reboot or anything. Note, however, that I do not have Xposed installed, and henderjr is right that Android Pay will quit working with normal Xposed, and if you use systemless Xposed, you have to disable it before Android Pay will work.
theophile2 said:
For whatever it's worth, I found that I had to delete /su/xbin_bind before Android Pay would work. Here are the steps that worked for me:
Doing it this way, Android Pay "just works" with root, no need to "unroot" or reboot or anything. Note, however, that I do not have Xposed installed, and henderjr is right that Android Pay will quit working with normal Xposed, and if you use systemless Xposed, you have to disable it before Android Pay will work.
Click to expand...
Click to collapse
Yep all correct except newest SuperSU doesn't need any of those extra steps (xbin_bind deleted or chmod).
Sent from my SM-N920P using Tapatalk
will this work for note 5 from us cellular?
SM-N900R4 (OJ5)
i talked to bigbiff in #twrp on freenode and he said probably can use the sprint note 5 twrp for the us cellular n5.
this was the case for the note 3 from us cellular too. had to use the sprint twrp.
en11gma said:
will this work for note 5 from us cellular?
SM-N900R4 (OJ5)
i talked to bigbiff in #twrp on freenode and he said probably can use the sprint note 5 twrp for the us cellular n5.
this was the case for the note 3 from us cellular too. had to use the sprint twrp.
Click to expand...
Click to collapse
I tend to follow most posts in the Sprint Note 5 forum and haven't seen anyone say they tried or used Sprint TWRP on a US Cellular version so I really can't say. Give it a try maybe? I'd think the worst case scenario is you need to Odin back to stock. Not an expert though so that be on you if it bricked. For sure I'd get a stock tar available before you try.
henderjr said:
I tend to follow most posts in the Sprint Note 5 forum and haven't seen anyone say they tried or used Sprint TWRP on a US Cellular version so I really can't say. Give it a try maybe? I'd think the worst case scenario is you need to Odin back to stock. Not an expert though so that be on you if it bricked. For sure I'd get a stock tar available before you try.
Click to expand...
Click to collapse
yea im pretty sure us cellular note 5 users can use twrp that is sprints.
i did find a twrp us cellular recovery for PD6 (im on PE1 now) i might download PD6 stock firmware then flash that us cellular twrp recovery but worried about what kind of root to do
i dont think i want to perm disable samsung pay and i think if i use SuperSU (systemless root) that i might be able to save it.
can anyone confirm this?
to my understanding systemless root means i dont need to flash a custom kernel?
If you flash twrp samsung pay will never work again for you
Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient
Nice!
suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.
Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.
I just ordered a Bolt, can't wait to play
Screen shots
OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%
More screenshots
Random stuff that can be unlocked hidden in the phone.
urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding
Hey there im looking for a while now but i cant seem to find a legit/trusted way to root my shield. I realy want to root it because i like fully customizing my devices and modifying apps. Please leave links to the right working software versions. I prefer: twrp, super su as the software to root my device. Also adb and the drivers are needed. Im not realy familiar with the new way of rooting. The only device i have ever rooted was a samsung tablet on 4.4 kitkat with a 1 click root app. All help is appreciated!
HolyChickenGuy said:
Hey there im looking for a while now but i cant seem to find
a legit/trusted way to root my shield. I realy want to root it because i like fully customizing my devices and modifying apps. Please leave links to the right working software versions. I prefer: twrp, super su as the softeware to root my device. Also adb and the drivers are needed. Im not realy fammiliar with the new way of rooting. The only device i ever have rooted was a samsung tablet on 4.4 kitkat with a 1 click root app. All help is appreciated!
Click to expand...
Click to collapse
Via fastboot Unlock bootloader and flash twrp, flash root in twrp (magisk or supersu)
C4SCA said:
Via fastboot Unlock bootloader and flash twrp, flash root in twrp (magisk or supersu)
Click to expand...
Click to collapse
Ok thanks but what versions of the software do i need
like what twrp and what version of the supersu
The lastest version of both work with Shield OS 5.2 (Nougat April 2017).
TWRP 3.1.1-1 and SuperSU 2.82
AdriK said:
The lastest version of both work with Shield OS 5.2 (Nougat April 2017).
TWRP 3.1.1-1 and SuperSU 2.82
Click to expand...
Click to collapse
Thank you so much!!! This is what I was looking for. As soon as i have time im definiality going to try
Or Magisk 13.3, if you choose to go that route.
redpoint73 said:
Or Magisk 13.3, if you choose to go that route.
Click to expand...
Click to collapse
Is there also any proof that it will work and will the stock nvidia apps stay after rooting???
Also thanks!!!
Is this video still really working on 7.0 os 5.2?
Also I heard you don't need shield family drivers on win 10 is that true???
Heyyyyy I did ittt!!!!!!!!!! Tanks to every one. Im sooo happy now.
Thank you all for the help
HolyChickenGuy said:
Is there also any proof that it will work and will the stock nvidia apps stay after rooting???
Click to expand...
Click to collapse
I know you've already accomplished it. But just for the record, yes there is proof it works. Plenty of folks have rooted with both SuperSU and Magisk. Both work, and I've also used both to root this device; and the NVIDIA apps still work.
---------- Post added at 09:55 AM ---------- Previous post was at 09:49 AM ----------
HolyChickenGuy said:
Also I heard you don't need shield family drivers on win 10 is that true???
Click to expand...
Click to collapse
I don't think you really need them. Pretty sure I rooted the device without installing the Shield drivers. If any issues connecting to the device, than try the drivers.
redpoint73 said:
I know you've already accomplished it. But just for the record, yes there is proof it works. Plenty of folks have rooted with both SuperSU and Magisk. Both work, and I've also used both to root this device; and the NVIDIA apps still work.
---------- Post added at 09:55 AM ---------- Previous post was at 09:49 AM ----------
I don't think you really need them. Pretty sure I rooted the device without installing the Shield drivers. If any issues connecting to the device, than try the drivers.
Click to expand...
Click to collapse
Ok thnx. Im also kinda looking at migisk is there also any real benefits of using that on a tablet or should I just stop playing Pokémon go .
Im nog doing something with xphosed so that's not a big deal. But I do device customization will that interfere with that safety check thing?
HolyChickenGuy said:
Im also kinda looking at migisk is there also any real benefits of using that on a tablet or should I just stop playing Pokémon go .
Click to expand...
Click to collapse
Magisk is really cool. Magisk Hide works well, although it's turning into a real cat and mouse game, where Google has been updating Safety net to break Magisk Hide, but then topjohnwu updates Magisk Hide to work again. It's a bit annoying, but topjohnwu seems to have a good handle on it, for now.
Magisk also has a bunch of cool modules. Those are mods that can be toggled off and on, so no need to dirty flash ROMs to "uninstall" mods, etc. You can check out the Magisk module collections in the Magisk forum section.
You might also check out the new suhide, if you don't want to switch to Magisk. Apparently suhide will pass Safety Net. But I haven't checked it out, personally.
https://forum.xda-developers.com/apps/supersu/suhide-lite-t3653855/page3
HolyChickenGuy said:
Im nog doing something with xphosed so that's not a big deal. But I do device customization will that interfere with that safety check thing?
Click to expand...
Click to collapse
Depends on what customizations. Depending on what exactly you are doing, yes you might trip Safety Net.
G
redpoint73 said:
Magisk is really cool. Magisk Hide works well, although it's turning into a real cat and mouse game, where Google has been updating Safety net to break Magisk Hide, but then topjohnwu updates Magisk Hide to work again. It's a bit annoying, but topjohnwu seems to have a good handle on it, for now.
Magisk also has a bunch of cool modules. Those are mods that can be toggled off and on, so no need to dirty flash ROMs to "uninstall" mods, etc. You can check out the Magisk module collections in the Magisk forum section.
Depends on what customizations. Depending on what exactly you are doing, yes you might trip Safety Net.
You might also check out the new SuperSU Hide. Apparently it's been updated to pass Safety Net. But I haven't checked it out, personally.
Click to expand...
Click to collapse
Ok thnx I already switched ?. The 1 thing is in the downloads tab I can't seem to flash the xposed modules I tried them all. As I had magisk I thought well why not. But now I can install ?
Also I'm looking to root my nexus 5x as my primary phone. Can rooting it block my carrier service like T mobile
HolyChickenGuy said:
G
Ok thnx I already switched . The 1 thing is in the downloads tab I can't seem to flash the xposed modules I tried them all. As I had magisk I thought well why not. But now I can install
Click to expand...
Click to collapse
How are you trying to install? After downloading, try to go to "Modules" in the menu, then tap the + icon, and select the module to install.
Also, go into Magisk Manager settings, and make sure "Magisk Core Mode Only" is not selected.
Not all modules work with all devices, and I also think a lot of the modules have not been updated to the new template for Magisk 13, so that might be causing the problem also.
You might try to download a module(s) from the Magisk forum section, and see if you can install it. Once downloaded, I think it should appear in the Magisk "Modules" section, if you tap the + button (as suggested above). Or alternately, I think you can flash in TWRP. The forum has a lot of cool modules that don't appear in the "Download" section of the Magisk Manager app, so I often download them from the forum threads, anyway.
https://forum.xda-developers.com/apps/magisk
HolyChickenGuy said:
G
Also I'm looking to root my nexus 5x as my primary phone. Can rooting it block my carrier service like T mobile
Click to expand...
Click to collapse
I know nothing about that particular device, so you should post in that device specific (Nexus 5X) forum, for the most accurate info.
In general for most Android phones, rooting should not affect service through your carrier. They might give you some baloney about not providing tech support for rooted devices, or not being able to "activate" it on their network. But as long as the phone already works on your carrier, rooting will not affect your cell service.
redpoint73 said:
How are you trying to install? After downloading, try to go to "Modules" in the menu, then tap the + icon, and select the module to install.
Also, go into Magisk Manager settings, and make sure "Magisk Core Mode Only" is not selected.
Not all modules work with all devices, and I also think a lot of the modules have not been updated to the new template for Magisk 13, so that might be causing the problem also.
You might try to download a module(s) from the Magisk forum section, and see if you can install it. Once downloaded, I think it should appear in the Magisk "Modules" section, if you tap the + button (as suggested above). Or alternately, I think you can flash in TWRP. The forum has a lot of cool modules that don't appear in the "Download" section of the Magisk Manager app, so I often download them from the forum threads, anyway.
https://forum.xda-developers.com/apps/magisk
I know nothing about that particular device, so you should post in that device specific (Nexus 5X) forum, for the most accurate info.
In general for most Android phones, rooting should not affect service through your carrier. They might give you some baloney about not providing tech support for rooted devices, or not being able to "activate" it on their network. But as long as the phone already works on your carrier, rooting will not affect your cell service.
Click to expand...
Click to collapse
Ok thank you I'll be sure to check the forums!
Just messing with the android O theme
Engine XD sus
Running stock ROM not rooted, getting this error? .. bootloader is unlocked though
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Eric214 said:
Google has Google pay check for an unlocked bootloader. If you are unlocked it will fail, you do not have to be rooted just bootloader unlocked for Safteynet to fail. You might as well install Magisk and let it hide that you are unlocked and rooted if you wish to use Google Pay. If you do not want to root, then just relock the bootloader, JUST MAKE SURE YOU HAVE THE STOCK RECOVERY AND NO CUSTOM RECOVERY INSTALLED. Otherwise you will brick your device. Also, be aware that relocking your bootloader will wipe all internal data off the phone so backup any photos, files, anything of importance before relocking bootloader.
Click to expand...
Click to collapse
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
Strange... on my OP 6 with unlocked bootloader and Magisk root, Google Pay runs fine. And even Magisk Hide was not enabled for Google Pay (now it is).
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Eric214 said:
What are you talking about? I've been using Magisk with passing safetynet since it came out a couple years ago. I just used Google Pay times today with no issues.
The issue is Google will fail Safetynet if you just have an unlocked bootloader and no magisk installed to pass the safetynet checks.
Click to expand...
Click to collapse
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
hallo dare said:
Magisk hide won't hide it. Alot of apps not able to avail of the hide function.
Click to expand...
Click to collapse
please dont give users the wrong impression
Magisk DOES hide it.
i have an unlocked bootloader, TWRP, MAGISK, and a custom kernel installed
and ive been using google pay for the past week without issues.
Why would I give users wrong impression? It's happening to me!!! Just because it doesn't happen to you or others then it cannot be true?
I've also an unlocked bootloader, TWRP and Magisk installed and Magisk is not hiding specific apps. Simple as that.
hallo dare said:
What I'm talking about is what I'm experiencing. I've magisk installed, Google Pay is ticket to magisk hide, along with other apps, and they all detect root
Click to expand...
Click to collapse
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Eric214 said:
Then Magisk must not be installed properly. You must have done something wrong is all I can think of. I use Google pay 2-5 times a day without issue and on the OnePlus 6 since launch, zero issues.
Click to expand...
Click to collapse
I've gone and done a complete format and re-installation of everything and the same issue is present.
hallo dare said:
I've gone and done a complete format and re-installation of everything and the same issue is present.
Click to expand...
Click to collapse
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Eric214 said:
Maybe delete the Magisk APK/zip you have and download a fresh copy then.
Click to expand...
Click to collapse
Done that, but made no difference. Just reading on another thread that it appears to be an issue for many.
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Orito said:
Magisk Hide works fine out of the box (no alterations) with Google Pay for me.
Historically, when it fails it's because Magisk is out of date.
hallo dare, if you want help, post your Magisk Manager's landing page, then another of your test results. Past that, you should head over to the Magisk XDA thread.
Edit:
I guess I forgot to mention I am on the BETA channel - so not exactly without alteration.
Click to expand...
Click to collapse
Thanks Orito,
Yeah I'll do just that. Can you please post the magisk you flashed and I'll try it please.
I flashed the 16.4.
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Orito said:
I'm running 16.42. In Magisk.
Open Magisk Manager.
Menu.
Settings.
Update Channel -> Beta
Check for Updates -> Enabled
Close Magisk Manager completely.
Reopen.
Click to expand...
Click to collapse
Exactly what I've been doing. Thanks
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
ben_deez said:
Hello I have a question. I have a OnePlus 7 Pro rooted with Magisk and of course the Dasher app wont work properly. Could I simply flash back and forth from a Magisk boot partition to a non rooted boot partition in order for Dasher to work? I wanted to get some insight before I start flashing things..
Thank you
Click to expand...
Click to collapse
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
V0latyle said:
Does the Door Dash app detect root? Chances are you just need to make sure you're passing Play Integrity BASIC and DEVICE verdicts. More information here
It's generally inadvisable to try swapping back and forth between the slots on A/B devices. They aren't meant to be swapped at will; the purpose of A/B slots is for seamless system updates, and you could very well render both slots unbootable by attempting to do so.
Click to expand...
Click to collapse
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
ben_deez said:
So I installed the above Integrity Checker and I failed all three. What if I leave the other slot alone and flash back and forth TWRP backups of the boot partition on my current slot? What would you recommend at this point?
Thanks again
Click to expand...
Click to collapse
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
ben_deez said:
Are you a Marine? Me too. Former Marine that is. Ooh-Rah.... I understand if you need to delete this reply since it is off topic.. But I had to shout out.
Click to expand...
Click to collapse
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
V0latyle said:
Read the post, please. The answers to your questions are there. Changing your boot image won't matter because your bootloader is unlocked, and that alone means you're going to fail all Play Integrity verdicts without using USNF.
There's no such thing as a former Marine, you should know better, knucklehead! 2007-2016, 2844/2841/2862/8411
We have several other mods who are Marines: @Az Biker, @Clark Joseph Kent for example, we even have a few veterans from other countries.
Click to expand...
Click to collapse
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
ben_deez said:
We were told to use the term Former Marine in bootcamp... and never use the term "X Marine" Former means "The same but at a different time" 1993-1997 1391... I'm from the "old Corps"....
Click to expand...
Click to collapse
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
ben_deez said:
But yes I did read everything on the post.. Good info thank you. I'm just trying to find a solution to this without having to lock the bootloader.
Click to expand...
Click to collapse
Well, as mentioned in that thread, you should be able to pass BASIC and DEVICE integrity by installing USNF 2.4.0, which forces Play Integrity to use basic evaluation instead of hardware methods. Don't worry about STRONG integrity, I am not aware of any apps that require that attestation. The vast majority of Play Store apps only use the DEVICE label as this indicates that the device (and software) has been tested via Android CTS; those which require additional security use the BASIC label as well. There are a few apps that use their own root detection techniques such as the presence of a SU binary or the Magisk app, but these are few and far between, and I highly doubt that the Dash app would be one of these. I would think it's a safe assumption that it simply uses the DEVICE label, maybe the BASIC label as well. Since you were failing all 3 labels, this would make sense.
Install the Magisk module mentioned in the thread and reboot, then use Integrity Checker to verify you're passing BASIC and DEVICE labels. If Dash still doesn't work, force stop and clear app data.
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
ben_deez said:
I installed USNF 2.4.0 rebooted and still failed all 3 integrity checks including BASIC and DEVICE. The Dasher app will install and seems to work fine until I select "Go Dash" to start accepting deliveries. It just loops back to the sign in page. I've cleared the data and cache and uninstalled and installed many times.... I even tried using older versions of the app with no success. I've tried using Magisk Hide and Zygist to no avail. appreciate you taking the time for my questions.. Much appreciation
Click to expand...
Click to collapse
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
V0latyle said:
What version of Magisk are you using?
I believe that since you're using a Chinese device you may still need to use MagiskHide Props Config to spoof a valid fingerprint.
Click to expand...
Click to collapse
25.2
ben_deez said:
25.2
Click to expand...
Click to collapse
I installed MagiskHide Props Config but I'm not sure which fingerprint to use.. Many selections... I selected the TMobile fingerprint since I have a GM1915 . I'm also still on 10.0.3.GM21AA So far it hasn't fixed the problem.
What about a Dual Boot system? Is it possible to have dual boot systems with one rooted and one thats not rooted? It still wouldn't hide that the bootloader is unlocked tho right? Because I got the app to work on my old LG V20. Apparently once the bootloader was unlocked on the v20 it couldn't ever be locked again because of using Dirty Santa to unlock it. My v20 was vs995 and I converted it to un996.. all I did to make the app work was do a factory reset. I didn't have to flash the original vs995 firmware. But I think the bootloader should still be unlocked on the v20 even after the factory reset... The app didn't work on my OnePlus 7 pro even after I did a factory reset. frustrating.
V0latyle said:
One of my younger brothers was a bulk fuel specialist in Okinawa, he just got out a few months ago
No Kidding? How cool is that? I was at Camp Hansen 9th ESB Bulk Fuel Co.. Before that I was Station Fuels at MCAS El Toro in 1996 running the Hot Pits. Small world
Click to expand...
Click to collapse