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

[sfhub]

when i try to push back the edited build prop file to the phone i have this error:
failed to copy build.prop to /system/build.prop: couldn't create file: Read-only file system

Mount system partition read/write in TWRP.

You'll need to install root for the build.prop changes to stick around otherwise they will be error corrected back to original.

 

[Lollolollo84]

I think that I have some problems with root/supersu...
Before I will try to flash factory images, twrp and super su again... I hope it solve!

---------- Post added at 05:44 PM ---------- Previous post was at 05:24 PM ----------

Mount system partition read/write in TWRP.

You'll need to install root for the build.prop changes to stick around otherwise they will be error corrected back to original.

My N5X have root (checked with root checker) and was decrypted...
I don't know the reason but system now is RO instead of RW... Can I solve the problem flashing again factory image, twrp and super su?

 

[tabormeister]

I guess my lingering question is... once you do a full unroot and restore the original boot.img, isn't dm-verity reenabled?

Possibly (regarding the build.prop entry and where to put it)

Oh gosh, I didn't see this discussion until right now! I only included the bottom bit about restoring the original boot.img in order to flash an OTA when one comes out. Yes, restoring the original boot image will break tethering again, depending on your carrier. This is more an 'all-carrier' approach, Sprint and Verizon I believe require both of those settings. So basically, run the first part of the guide from stock, then run the second part to flash an OTA if you need to, then run the first part again and boom, tethering and Android Pay working again. Leave the boot.img alone until you need to OTA again, when doing the full unroot I didn't let it reflash that or recovery.img.

 

[sfhub]

My N5X have root (checked with root checker) and was decrypted...
I don't know the reason but system now is RO instead of RW... Can I solve the problem flashing again factory image, twrp and super su?

In the twrp "mount" page there is a check mark to mount system partition read-only. Uncheck that.

 

[Lollolollo84]

In the twrp "mount" page there is a check mark to mount system partition read-only. Uncheck that.

I found this already unchecked...
???

 

[sfhub]

I found this already unchecked...
������

Try renaming and pushing build2.prop.

That will tell you if there is a problem overwriting build.prop (in which case you could move it out of the way, or problem with writing to /system in general)

Also I assume you are doing the adb push in TWRP, not in android.

 

[Lollolollo84]

Try renaming and pushing build2.prop.

That will tell you if there is a problem overwriting build.prop (in which case you could move it out of the way, or problem with writing to /system in general)

Also I assume you are doing the adb push in TWRP, not in android.

I think that the problem is:
Now i have root systemless
But I need to root system also...

How I can solve this problem and have a normal / full root (NOT Systemless!!!)

EDIT:
i found this guide: Some opinions????

Step 1: flash SuperSu 2.71 normally (this will patch boot.img)

Step 2: boot the device and full unroot in Supersu app (device should now
be unrooted, however because of step 1, the patched boot.img is still there)

Step 3: boot into twrp >go to the terminal > and type: "echo
SYSTEMLESS=false>>/data/.supersu" (force the new 2.71 to only install in
system mode)

Step 4: now flash supersu 2.71 in twrp (if you read the logs, it should say
something like "installing in system mode")

 

[sfhub]

I think that the problem is:
Now i have root systemless
But I need to root system also...

How I can solve this problem and have a normal / full root (NOT Systemless!!!)

EDIT:
i found this guide: Some opinions????

Step 1: flash SuperSu 2.71 normally (this will patch boot.img)

Step 2: boot the device and full unroot in Supersu app (device should now
be unrooted, however because of step 1, the patched boot.img is still there)

Step 3: boot into twrp >go to the terminal > and type: "echo
SYSTEMLESS=false>>/data/.supersu" (force the new 2.71 to only install in
system mode)

Step 4: now flash supersu 2.71 in twrp (if you read the logs, it should say
something like "installing in system mode")

You can install SuperSU in system that way, but I don't think that is related to you not being able to place build.prop on /system.

 

[ald040]

Has anyone run into any issues using this method with Android 7.0? I've been getting the factory images, flashing them, installing the OTA and then doing the process to gain no tethering provisioning and has worked flawlessly for the past 6-7 updates, but now doesn't seem to work with the new Android 7.0 update, any help will be greatly appreciated!

Edit: I apologize, I did the unthinkable and asked the question without spending more time researching. I figured the conversation would have been on the last page of the thread, but it appears I updated a lot later.

 

[Ken.Adams]

Great Guide helpful at times!!

 

[andTab]

I wish someone would just start a new guide with 7.0 instructions.

 

[tabormeister]

I wish someone would just start a new guide with 7.0 instructions.

http://xdaforums.com/showpost.php?p=68467873&postcount=189

 

[tabormeister]

The reason the method in the post you replied to works is because the installation of SuperSU (in the default systemless install mode) will disable dm-verity in your kernel/boot.img, which also disables the reed solomon forward error correction.

My workaround was to edit default.prop in boot.img which seems to supersede.

So is there a way we could do this without having to do the systemless root step? I'd really rather do it without having to root at all

 

[DualSportDad]

So is there a way we could do this without having to do the systemless root step? I'd really rather do it without having to root at all

You quoted the way to do it without rooting.

Sent from my Nexus 6P using Tapatalk

 

[sfhub]

You quoted the way to do it without rooting

He wrote the post that he referred to. It requires rooting.

 

[tabormeister]

You quoted the way to do it without rooting.

He wrote the post that he referred to. It requires rooting.

@sfhub exactly! Lame as it is, Android Pay still works with my method but the latest Pokemon Go stopped working. I need my pocket monster fix, so for now I'm using paid Foxfi + pdanet on my laptop...this is actually an awesome solution because it autoconnects when I plug in my phone, but it'd be rad if we could figure out a way to fix the forward error correcting problem (I think the dude I quoted mentioned changing default.prop) without even having to install systemless.

I was approaching this thinking you could only do settings put with root...now I know that's not the case, maybe another echo into default.prop would do the trick? Also, the reason I echo into build.prop is since MM there's like 0 space left in /system so if you try to pull, edit, and push build.prop it errors out

 

[DualSportDad]

He wrote the post that he referred to. It requires rooting.

I'm talking about modifying the boot. IMG

http://xdaforums.com/showthread.php?p=68380897

Sent from my Nexus 6P using Tapatalk

 

[sfhub]

I'm talking about modifying the boot. IMG

http://xdaforums.com/showthread.php?p=68380897

Sent from my Nexus 6P using Tapatalk

I think I may have misread your original reply. Apologies.
...
Just disable dm-verity on the boot.img. You don't need the root portion, just the side-effect of SuperSU disabling dm-verity.

You can modify the SuperSU install script if you don't want to edit it yourself.

Same can be done for the default.prop changes.

 

[DualSportDad]

I have to ask this cause I don't fully understand.... What is the importance of adding the "tether_dun_required 0" ? My mom was using T-Mobile and they started to throttle her tethering so she switched to cricked a couple of days ago and her tethering would connect but not allow data transfer. I ran the adb commands to add the above mentioned and it worked no problem. She is on a 6.0 or 6.0.1 pure nexus ROM. I went to do the same to my phone in fear that's how T-Mobile was able to see her tethering usage (I'm on T-Mobile) but after running the commands I went to check and I don't even have a settings.db folder, I'm on 7.0 stock with elemental kernel, not rooted. I checked my nexus 6 on a 6.0 ROM and it has the settings.db folder and took the dun mod just fine.

Sent from my Nexus 6P using Tapatalk

 

[novacav]

So is there currently no working wifi tether unlock on T-mobile and Metro? I can confirm nothing in this thread works on Metro as of today Seems to have been that way for a while.

As far as I can tell, T-Mobile has successfully thwarted ALL wifi tether limit workarounds. Even Fabio Grasso's WiFi Tether Router root app doesn't get past it. Really upsetting, especially to be on a Nexus and not have uncapped tethering. That's one of the main reasons I got a Nexus.

So.... does anyone have any ideas? Maybe I should create a Bounty thread. Would be worth paying to have a clever or new solution with potential to work long-term, IMO. Really don't wanna have to go back to wired tethering

I suspect the reason they have gone all-out on this is because T-Mobile actually sells unlimited wifi hotspot now, the premium T-Mobile One plan. It's $95 a month though, before device payments. That's a bit steep for me.