Database Users

[GUIDE] How To Unlock Tethering on Nexus 5X.

I'll start off by saying I didn't come up with any of this method myself, its just different information I found scattered on different threads on XDA and Reddit. Maybe some other 5X users will find it useful contained in this thread.
Secondly, this requires an unlocked bootloader, also working adb and fastboot with correct drivers for your 5X, enable USB debugging. I won't go over that here, there are plenty of other guides on how to do that, and know that it will erase all your data. As long as you can find your device via "adb devices" and "fastboot devices" you should be fine.
Lastly, you will get the corrupt data message on phone startup. I don't see any negative effects with this, other than an annoying message. Also I'm still able to use the fingerprint scanner as well as set up Andoid Pay. I can't verify Android Pay as I don't have any stores near me that accept it.
You also won't have to flash any custom recovery or root the device, which keeps it closer to stock, which hopefully will allow Android Pay to still function, hopefully someone with a Android Pay store nearby can test this to verify.
First grab TWRP for 5X from here. Save it in the same folder as your adb/fastboot install.
Make sure your phone is connected to your computer, open command prompt and verify adb sees your phone.
Code:
adb devices
Now reboot to bootloader.
Code:
adb reboot bootloader
Now we boot from TWRP without having to flash/install it.
Code:
fastboot boot twrp-2.8.7.0-bullhead.img
When TWRP finishes booting, click Mount and check the box for /system
Now we need to pull the build.prop file.
Code:
adb pull /system/build.prop
Using a text editor add this line to the end of the build.prop file and save it.
Code:
net.tethering.noprovisioning=true
Now we push it back to the phone.
Code:
adb push build.prop /system/
Make sure the permissions are correct.
Code:
adb shell chmod 644 /system/build.prop
And lastly
Code:
adb shell settings put global tether_dun_required 0
Now we just reboot
Code:
adb reboot
and your tethering should be working!
I'm currently using this method and it is working for me. I'm on Verizon with a Grandfathered Unlimited Plan, so I can't test it for any other carriers.
Most of this information I pulled from this reddit thread, I just did my best to condense it down and simplify it, and make it aimed toward the Nexus 5X specifically.
edit* People are confirming on the Reddit thread on their Nexus 6 that Android Pay is still working after making these changes!

Thanks! This works exactly as stated, even the "corrupt data" warning on boot.
I will add that - this being my first Nexus device since a Galaxy Nexus - the "fastboot oem unlock" step needed prior to this guide has an additional step where you have to enable the "OEM Unlock" option in the Developer Options menu, within the booted system. After confirming this you can unlock the bootloader via the standard "fastboot oem unlock" command prior to starting this guide.

Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!

Thanks. Worked great for me. I'm on AT&T, weird thing though, I never had any problem activating the hotspot on my OG Nexus 5.

AWESOME!

added to index
[INDEX] LG NEXUS 5X Resources Compilation Roll-Up

Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?

olivercervera said:
Guys can you please explain what do you mean as "unlock tethering"? Is not enabled by default?
Click to expand...
Click to collapse
This method bypasses the subscription check for tethering, those of us with unlimited data have to pay a separate fee to use tethering with Verizon, and this fixes that. It should be the same for other carriers as well.
Sent from my XT1060 using XDA Free mobile app

I was so excited to play with my 5x when I got home (that and dealing with my 2 sick kids) and I completely forgot to unlock the bootloader before I got too carried away. Now all the time I spent downloading apps and such is lost. Our DSL connection is slow, so all that took one time. I've been rooting and romming way too long to make such a rookie mistake.
So, I get the joy of blowing the whole thing way and re-setting it up again...

XF1ber said:
Thanks for this, used same method to push supersu and get it installed without needing to decrypt the phone!
Click to expand...
Click to collapse
Could you confirm the steps?
Can you confirm you can still use supersu? I thought the kernel had to allow su.
Also, I guess you can also install the bootunlock app and see if that works?

Thank you thank you thank you!
This is huge for me.
BTW, I assume you can just push the original unmodded build.prop back for OTA updates. Anyone know if anything else is required apart from that?

Confused on why we need TWRP just to do this.

You're not flashing twrp, just booting into it. Twrp allows you to pull and push files to /system without root, which is needed to make these changes.
Sent from my Nexus 5X using XDA Free mobile app

Can someone confirm Android Pay actually works?
Sent from my Nexus 5X using Tapatalk

T-Mobile/MetroPCS users additional steps to enable tethering
If you are on T-Mobile or MetroPCS you will need to perform some additional steps for tethering to work. After you have performed the steps outlined earlier in this thread do the following:
Under Settings -> More -> Cellular Networks -> Access Point Names
Touch the name of the APN that is selected (there may only be one) then:
1) change "APN Protocol" to "IPv4"
2) change "APN roaming protocol" to IPv4
3) Edit "APN Type" and add "dun" to the comma separated list so it reads something like "default,supl,mms,dun"
4) OPEN THE MENU IN THE UPPER-RIGHT AND CHOOSE SAVE!
5) You MAY have to reboot for this to take effect

Ok needing it for that reason makes sense now.

So... I'm getting about 30% packet loss on att with my 5x.
If I take my sim out and pop it into my nexus 6(also with marshmallow), everything is fine.
Could someone with att run some extended pings from a device connected to your phones tether and note any ping drops?
I don't know if this is a sw bug, or hardware issue.

Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X

Ascertion said:
Does this work if the device is still encrypted?
My TWRP seems to have trouble accessing /system partition with encryption.
Sent from my Nexus 5X
Click to expand...
Click to collapse
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?

MarkGbe said:
yep works fine. You have the correct twrp i presume and your phone's bootloader is unlocked?
Click to expand...
Click to collapse
Ah my bad. It's not reading my /sdcard partition. No matter. That's what adb is for. Please disregard my post. I'll update my progress when I get home later today and try it on my personal PC.

Help with 'How To Install A Custom Recovery On Your Device'

I'm following the beginners guide to release my Moto X Pure from it's shackles and am getting this from the command prompt on step 2.
Can anyone provide some assistance?
https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
C:\Android\sdk\platform-tools>fastboot flash recovery twrpclark.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (0 KB)...
OKAY [ 0.004s]
writing 'recovery'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.019s
C:\Android\sdk\platform-tools>

You need a newer TWRP image most likely, if you are using the one in that tutorial it is OLD!!!
The Moto X Pure/Style is officially supported device. Go to https://dl.twrp.me/clark/ and download
twrp-3.0.2-0-clark.img
Make sure your bootloader is unlocked and enter the following command:
fastboot flash recovery twrp-3.0.2-0-clark.img
Do NOT reboot, then on your device press VOL DN until it says Recovery and press Power, TWRP should start and allow changes to system and perform a backup to the SD card.
And BTW, pretty much everything else in that tutorial after the bootloader unlock is incorrect/outdated. Look in my signature for the proper way to root if that is your objective.

Thanks again. Petition signed.

Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.

lip008 said:
Is there an up to date sticky/guide on editing build.prop? I believe I need to add the following line so I can use native hot spot.
net.tethering.noprovisioning=true
I've downloaded ES File Explorer but I don't know if something has changed in Android or in the Explorer, but the guide I'm following isn't helping.
Click to expand...
Click to collapse
Got me... I've never had a problem tethering on any Moto device.

acejavelin said:
Got me... I've never had a problem tethering on any Moto device.
Click to expand...
Click to collapse
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!

lip008 said:
Neither have a lot of people from what I've read. I didn't have this issue on the Z Play but I sold that device. I want the Pure to be my daily driver, but I need to get this hot spot working. All this work for this!
Click to expand...
Click to collapse
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.

acejavelin said:
I think you are chasing the wrong problem... The fix you have is for when carrier's block tethering in provisioning, if it worked fine in Z then that isn't the problem.
I assume you tried the normal cache wipe, network reset, and maybe even factory default?
You need to try to use it and when it fails pull a logcat and see why.
Click to expand...
Click to collapse
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.

lip008 said:
IDK. Lots of unlocked devices still honor the carrier's flag in regards to hotspot. The Nexus devices and my gfriend's Pixel does. A new unlocked Axon 7 or the Moto Z Play do not. I've hard reset the device and now that it's been bootloader unlocked, reset again. I haven't wiped any cache or a network reset. Are those done automatically once a factory reset/bootloader unlock is done?
My device says to contact the carrier in regards to getting the hot spot enabled. I haven't tried it again with the bootloader being unlocked, but I will give it a go this morning and see what happens.
Click to expand...
Click to collapse
Hmm... That sure sounds like carrier provisioning, weird... I technically don't have tethering on H2O but it works fine and I am stock and bootloader locked.
EDIT: Well, I am a bold faced liar... I tried it now on H2O and got the "Account not set up for tethering" messaging, I know it worked on AT&T before I switched last month but I think my account there had it. Now I am curious too...
Maybe best to search in the Moto X area and if you can't find a thread about it (I looked, but only for a minute), start a new one... the title of this thread won't likely get help for this problem.
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
I found this:
Enable Wireless Tethering Rooted Moto X Pure
1. Modifying system files could render your device useless, so by continuing you’re assuming that risk
2. Using a root file explorer, navigate to /system/
3. (Optional) Make a copy of the build.prop
4. Open the build.prop file with a text editor
5. Add the following line to the bottom of build.prop file: net.tethering.noprovisioning=true
6. Save the file and reboot your device
Click to expand...
Click to collapse
Might root again and try it, I haven't had a need for root in a while... Will see, I am lazy so maybe I won't until I need to.
I generally prefer using Solid Explorer in Root Mode and QuickEdit for editing root files... ES File Explorer was once king, but became overbloated garbage the last couple years.

That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.

lip008 said:
That's what brings me back to editing the build.prop.
I have a ES file Exporer and checked off the root option so I should be able to access everything on the device.
I have never edited the build.prop and need to find the file path for it.
A sticky or something on editing build.prop would be great.
Click to expand...
Click to collapse
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer

acejavelin said:
No likely... It is so rare to have to edit it anymore, so few things require it.
Try a different explorer... ES is junk, use Solid or Root Explorer
Click to expand...
Click to collapse
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.

lip008 said:
Thanks you...especially for the quick replies. Maybe I will start up a new thread if I can't find an existing one on this hot spot issue.
Click to expand...
Click to collapse
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738

acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
How do I bump a thread?

lip008 said:
How do I bump a thread?
Click to expand...
Click to collapse
Lol... Just post a reply, it will "bump" it to the top of the thread list for that section.

acejavelin said:
Here is the thread... You can bump it if you need to: https://forum.xda-developers.com/mo...nable-wireless-tethering-moto-x-pure-t3227738
Click to expand...
Click to collapse
I was confused by the "you can bump it if you need to" comment. I took it as being something extra in addition to replying. I wasn't able to figure out the root path, but using the search function on ES Explorer I found the build.prop file, made the change, and presto....I know have hotspot working. Next up is to research the popular ROMS. I'm interested in some of the built in features like ad blocking and of course Nougat. Thanks again.

How to hide sim panel in s8 oreo

Hide dual sim manager in quick setting of s8 oreo

see thread

Anyone, please?

I tried asking this questions earlier but sadly no one responded..
Sad part of forum actually.. ppl will reply for some waste things but not for something important..
I guess for dual sim it will be there... try disabling one sim it will be gone...

solved

I don't see that on my device... maybe badges or grouping notifications?

Its in dual sim model ,when we insert 2 sim its shows in quick settings

Bump, I need it too

Maybe our hero crayonyes could save as again with an update of the previous app?
crayonyes said:
try this.
install, reboot.
to uninstall : go to settings > apps > uninstall aaa.quicksetting.hidesimpanel
Click to expand...
Click to collapse

MimKoRn said:
Maybe our hero crayonyes could save as again with an update of the previous app?
Click to expand...
Click to collapse
sadly for oreo we cannot just install overlay apk anymore to make it work.
options are:
1. install overlay apk (and reboot) then do some adb things to cmd overlay enable it (need plug to pc)
2. have samsung theme that hide this panel.
3. use substratum (and paid andromeda) and have some subs dev to make this hide sim panel (need plug to pc)
i hate oreo for this. maybe just me, but oreo sucks compared to easy theming in rootless nougat.
edit: here's reference to option 1: (need to edit bat file and change apk name)
https://forum.xda-developers.com/showpost.php?p=76109441&postcount=4357

aaa.quicksettings.hidepanel is not present in sytem apps?
it means applying this overlay to non system app is useless

karan68 said:
aaa.quicksettings.hidepanel is not present in sytem apps?
it means applying this overlay to non system app is useless
Click to expand...
Click to collapse
as i said you cannot just install overlay and expect it to work,
do as the reference link I posted.

crayonyes said:
as i said you cannot just install overlay and expect it to work,
do as the reference link I posted.
Click to expand...
Click to collapse
Thanks man it works perfectly using cmd.
Its even works fine when we reboot no probl.:good:

karan68 said:
Thanks man it works perfectly using cmd.
Its even works fine when we reboot no probl.:good:
Click to expand...
Click to collapse
Can you please share your exact steps, i am kind new to andriod.

MedoooMedooo said:
Can you please share your exact steps, i am kind new to andriod.
Click to expand...
Click to collapse
just install the sim hide apk basically its a layer theme then reboot device,then using adb apply the layer you installed.

karan68 said:
just install the sim hide apk basically its a layer theme then reboot device,then using adb apply the layer you installed.
Click to expand...
Click to collapse
Thanks, i downloaded adb tools on my windows and test adb devices commend on cmd and it works perfectly.
Now i need to know which commend i have to type to apply the layer or i need to do something else?

you need aaa.quicksetting.hidesimpanel.apk and then
Refer to this post how they apply layers in oreo https://forum.xda-developers.com/showpost.php?p=76109441&postcount=4357

karan68 said:
you need aaa.quicksetting.hidesimpanel.apk and then
Refer to this post how they apply layers in oreo https://forum.xda-developers.com/showpost.php?p=76109441&postcount=4357
Click to expand...
Click to collapse
i followed all steps but notification is still there, maybe i made something wrong

nicholas64 said:
i followed all steps but notification is still there, maybe i made something wrong
Click to expand...
Click to collapse
probably missing something
here's the screenshot

karan68 said:
probably missing something
here's the screenshot
Click to expand...
Click to collapse
i have got note 8, maybe it does not work for this reason

Moto g5 plus, 8.1, not rooted, scrcpy, ADB device list empty, driver installed. ?

I've been watching videos and reading threads and installing drivers and I just can't make this work. All I can think is maybe I am required to root my phone? Or that the drivers are all invalid now that I updated to 8.1?
I have full android studio installed and the Google USB driver.
My goal is to control my phone from my PC.
Threads here seem either out of date to complicated by much more serious goals, like flashing etc.
I don't even want to root heh.
Halp X)

Innomen said:
I've been watching videos and reading threads and installing drivers and I just can't make this work. All I can think is maybe I am required to root my phone? Or that the drivers are all invalid now that I updated to 8.1?
I have full android studio installed and the Google USB driver.
My goal is to control my phone from my PC.
Threads here seem either out of date to complicated by much more serious goals, like flashing etc.
I don't even want to root heh.
Halp X)
Click to expand...
Click to collapse
What is it what you want to do? What do you mean with "control my phone"? If you have Motorola (not Google) drivers installed (and something like minimal ADB & Fastboot) you should be able to boot your device into bootloader mode and it should be recognized.
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=drivesdk
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
Sent from my Moto G5 Plus using XDA Labs

Wolfcity said:
What is it what you want to do? What do you mean with "control my phone"? If you have Motorola (not Google) drivers installed (and something like minimal ADB & Fastboot) you should be able to boot your device into bootloader mode and it should be recognized.
Motorola drivers:
https://drive.google.com/file/d/0B0WGdtNWubBJYnlDcWRBZXltanc/view?usp=drivesdk
Minimal ADB & Fastboot:
https://drive.google.com/file/d/10NEzpxKpYWfq-HdK42ctwoEnCg-BfsRQ/view?usp=drivesdk
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Like in the title, scrcpy.
https://github.com/Genymobile/scrcpy
I want a window on my desktop that is my phone in which I can click and such, which to my understanding is exactly what that app does. But naturally it cannot manipulate what it cannot see, and it sees with adb, and adb can't see my phone. But my operating system can. At least it says it can.
Update: Apparently I had not enabled USB debugging. Now I can see my device but it is not "authorized." I try to grant permission and get "because an app is obscuring a permission request, Settings can't verify your response." I'm working on that now, thanks! I'll make a new thread if that problem persists.
Update: It was the application "Tap'n'turn." Temporarily disabling its permission to display over other apps solved it. (Search for "display" in settings.)
Everything is now working

I'd just like to say that that's a very cool looking app, so thanks for posting your question about it, maybe I'll end up using it myself :good:

NZedPred said:
I'd just like to say that that's a very cool looking app, so thanks for posting your question about it, maybe I'll end up using it myself :good:
Click to expand...
Click to collapse
I know right? It's pretty amazing. Were someone to make an open source and user friendly wrapper for everything else about getting it to work I'm sure it would become immensely popular.

Going back to stock rom, coming from lineageos 16 ????? Lenovo Tab4 10 Plus TB-X704F

Hey guys,
since I dont get neither Netflix nor Disney+ to work on my TB-X704F after having flashed LOS 16, I want to go back to stock rom. I've already tried to use Lenovo Smart Assistant but the flashing procedure always fails. I also tried QComLoader but also fails at 5%.
Is there a working way on going back to stock rom having TRWP ans LOS 16 installed???
Due to the fact that Netflix and Disney+ arent working (already tried Magisk module to change the tablets' fingerprint), I need to go back to stock rom.
Thanks in advance!!!!

Please use this tool to flash the stock rom: https://qfiltool.com/qfil-tool-v2-0-2-3

need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?

I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.

rhchia said:
need help here. I'm flashed LineageOS previously. Can't install NetFlix hence i want to switch back to stock. I've installed the drivers and QFIL software. however when the device is off, i hold the volume up button then plug in the usb, but the QFIL software still show port not available. I entered the TWRP screen asking me to whether i can choose Boot to FFBM. Restart Bootloader.. etc. what should i choose?
Click to expand...
Click to collapse
I've got the same problem. What did you do in the end?

K14_Deploy said:
I assume by "magisk module", you mean the termux props method? That's worked for me on several devices.
Also I really don't know how I can help you past that, most stock firmwares aren't designed to be flashed on modified devices. Very few manufacturers even support that (Samsung, LG and OnePlus are falriy major exceptions)
Edit: just realised the age of the thread, apologies.
Click to expand...
Click to collapse
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?

boomhaueruk said:
What exactly is the termux props method?
Is that to fix Magisk not authenticating? Or to allow the tool QFIL to restore stock?
Click to expand...
Click to collapse
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.

K14_Deploy said:
I mean the MagiskHide Props Config, which requires Termux. Basically you install the module, give Termux root and configure props with it. Then you use MagiskHide to hide magisk from them.
On the topic of reverting to stock, it's not possible. Custom firmware is almost always a one way process, and you understand if you do it things like the OP has described can and will happen. People who want things to "just work" use stock firmware, or an Apple device, it was never designed to not need tinkering.
Click to expand...
Click to collapse
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
Is this going to be a problem?
Magisk is dropping support for hiding root access from apps
Magisk, the popular Android rooting tool, will continue to be developed by topjohnwu, but without its root hiding feature called MagiskHide.
www.xda-developers.com

boomhaueruk said:
Goodness, I'm not a person who needs a 'just work' situation. It took weeks to get this onto stock and I've spent a long time reading up trying to fix Magisk. Surely there has to be a point when you're actually using the device and not just fixing it!
Basic things like being able to download and use apps...that seems like a reasonable request.
I think there's 'tinkering' and 'it doesn't work!'
Also, I've rolled back to stock roms before on various phones, recovery and so on - not with this tablet admittedly. Surprised it seems such a difficult or - as you say - impossible process. But hey.
That said, I appreciate the help! I really do.
So; I need to find 'Termux'. https://termux.com/
This says I get it from 'F Droid'. But I then found a link on their webpage to this;
https://f-droid.org/repo/com.termux_117.apk
I'm assuming that's the right one.
It looks like a terminal?
Googling for Termux Magiskhide props config got me to this youtube video;
It's in Indonesian, but shows you some steps. Would that be the best place to find instructions?
Click to expand...
Click to collapse
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.

K14_Deploy said:
You can install Termux from the Play Store if you have GApps. I did and it worked. And yes, it is a terminal. I've just upgraded to 17.1 on this device so I'm going to be doing it again sooner rather than later anyway.
Click to expand...
Click to collapse
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.

boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
Click to expand...
Click to collapse
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
boomhaueruk said:
Thanks.
I guess my other issue is I'm not actually sure what steps I'm supposed to do next.
That youtube video looks really dodgy!
It's nice to find someone else on this device. Mine has sat unused for months, I've decided to finally either get it to work properly or bin it. Todays the day.
Click to expand...
Click to collapse

K14_Deploy said:
Ok, so...
Make sure Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled. Hide must be disabled. If this isn't the case, do so and then reboot.
Open Termux. Type 'su' to give root access. Then type 'props' and follow the menu for your device. Type '1' for 'Edit device fingerprint'. Type 'f' for 'Pick a certified fingerprint'. Type '13' for 'Lenovo'. Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)'. If you have another device you might be out of luck. Type 'y' for 'yes'. Wait. Type 'y' again to reboot.
Configure MagiskHide to hide these parts of GPS + any other root sensitive apps. The screenshot I have was taken from a OnePlus but it shows the GPS that needs to be hidden. The less you can get away with hiding the better for performance reasons. Also make sure to repackage Magisk as 'Settings' and change the name of the 'TWRP' folder using a root file explorer (for some reason I don't have one) to... I'm partial to 'f**kyougoogle' personally, but anything will do. Reboot again and Disney+ should work just fine. If it doesn't, I can't help you.
I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works.
This isn't without risk. Some apps specifically wanting android 11 might not work right. But it SHOULD fix root sensitive apps that use Safetynet. I also can't say anything about Widevine compatibility as I don't have Disney+ on this device.
Click to expand...
Click to collapse
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
They are Magisk modules, you go to there the puzzle piece is and search for them.

boomhaueruk said:
Thanks.
OK. So, I've attached a few pics to show you where I am.
Booted, checked into Magisk for those settings. I can see 'Magiskhide', so I can untick that, but how do I ensure "Magisk has "MagiskHide Props Config" and "Busybox For Android NDK" and root fully enabled"
Root wise, I'm pretty sure it is, but yes, not sure how I double check!
Click to expand...
Click to collapse
OK, found 'root checker' on the play store. And Termux.
so I have root.

K14_Deploy said:
They are Magisk modules, you go to there the puzzle piece is and search for them.
Click to expand...
Click to collapse
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.

boomhaueruk said:
Ah! Got it. Ok, went into Magisk, went to the puzzle piece, found them both and...
Ah, I've just seen you've said "I'd recommend moving to 18.1 before doing this, you'll have to start from square 1 but it means you're more up to date and won't have to do it again until someone builds 19.1 for this device. Can confirm, that build works."
Right. I'd better go and find all the instructions for that. I've forgotten how I got this thing onto custom firmware, but I've got recovery installed.
Click to expand...
Click to collapse
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer, as you have to wipe internal storage and use ADB.

K14_Deploy said:
Go to the 18.1 thread on this forum and look for the instructions for flashing without being on stock. Also use TWRP 3.4.0.0. You will need a computer.
Click to expand...
Click to collapse
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.

boomhaueruk said:
I may stay where I am on Android 9. I've just seen it doesn't support sim and I sort of need that.
I can always come back and do that later, right?
I'm a bit worried about bricking it too. I might just get myself onto Android 9 working with the fix for now. It took me so long to get it onto custom rom the first time.
Click to expand...
Click to collapse
Yeah of course, but you will have to start over if / when you upgrade

Ah. Hit a snag.
You said "Type '2' for 'Lenovo Tab 4 8 Plus TB-8704F (8.1.0)"
I've got the TB-8704L, the 10 inch.
Let me see if anythings listed.