[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks.

[Builtfordtough1]

Before and after running your command

Row: 0 _id=2918, name=internet, numeric=310120, mcc=310, mnc=120, apn=n.ispsn, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=, authtype=-1, type=default,supl,mms,ims,cbs,ia, current=1, protocol=IPV4V6, roaming_protocol=IP, carrier_enabled=1, bearer=0, bearer_bitmask=12288, mvno_type=, mvno_match_data=, sub_id=1, profile_id=0, modem_cognitive=0, max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=4, user_visible=1

Still no data flowing to devices

 

[Fenny]

Before and after running your command

Row: 0 _id=2918, name=internet, numeric=310120, mcc=310, mnc=120, apn=n.ispsn, user=, server=, password=, proxy=, port=, mmsproxy=, mmsport=, mmsc=, authtype=-1, type=default,supl,mms,ims,cbs,ia, current=1, protocol=IPV4V6, roaming_protocol=IP, carrier_enabled=1, bearer=0, bearer_bitmask=12288, mvno_type=, mvno_match_data=, sub_id=1, profile_id=0, modem_cognitive=0, max_conns=0, wait_time=0, max_conns_time=0, mtu=0, edited=4, user_visible=1

Still no data flowing to devices

Ahh, you're not on the main Sprint MNC MCC.

content update --uri content://telephony/carriers --where "_id=2918" --bind type:s:default,supl,mms,ims,cbs,ia,dun

 

[Builtfordtough1]

That did it sort of, the changes to telephony.db are not changing when running the commands see my next post for the fix.

 

[Builtfordtough1]

I finally got the hotspot working for sprint with a lot of help from Fenny.

These steps are ONLY for SPRINT and only tested on NDE63V, NPF26J and NMF26O

These are the steps I followed

Open Root Explorer and navigate to:
/data/user_de/0/com.android.providers.telephony/databases

Copy telephony.db to your computer

Restore phone back to stock

Install TWRP, Root, and Tethering Mod

Boot Phone

Copy your backed up telephony.db to

/data/user_de/0/com.android.providers.telephony/databases

Overwrite the currently in that location and leave the permissions rw-rw-rw-

Run the command:

content update --uri content://telephony/carriers --where "_id=2918" --bind type:s:default,supl,mms,ims,cbs,ia,dun

After running the command you will see the phone drop data then pick it back up at this point reboot and your all set.

 

[Fenny]

I finally got the hotspot working for sprint with a lot of help from Fenny.

These steps are ONLY for SPRINT and only tested on NDE63V and NPF26J

These are the steps I followed

Open Root Explorer and navigate to:
/data/user_de/0/com.android.providers.telephony/databases

Copy telephony.db to your computer

Restore phone back to stock

Install TWRP, Root, and Tethering Mod

Boot Phone

Copy your backed up telephony.db to

/data/user_de/0/com.android.providers.telephony/databases

Overwrite the currently in that location and leave the permissions rw-rw-rw-

Run the command:

content update --uri content://telephony/carriers --where "_id=2918" --bind type:s:default,supl,mms,ims,cbs,ia,dun

After running the command you will see the phone drop data then pick it back up at this point reboot and your all set.

Great!

Just to add to your explanation and to generalize the fix a bit more.

If your carrier prevents you from editing your APNs
You can change permissions on your telephony db with this command:

adb shell
su
chmod 666 /data/user_de/0/com.android.providers.telephony/databases/telephony.db

Grab the ID of your current APN using the following command:

adb shell
content query --uri content://telephony/carriers/preferapn

If the type doesn't contain "dun", copy the existing type string and add ",dun" to the end:

In the following command you would substitute
your current type string for "your_type_here",
and the _id for your_id_here:

adb shell
su
content update --uri content://telephony/carriers --where "_id=your_id_here" --bind type:s:your_type_here,dun

 

[Builtfordtough1]

Try setting it to lte-only and then rebooting.

Ahh, you're not on the main Sprint MNC MCC.

content update --uri content://telephony/carriers --where "_id=2918" --bind type:s:default,supl,mms,ims,cbs,ia,dun

Great!

Just to add to your explanation and to generalize the fix a bit more.

If your carrier prevents you from editing your APNs
You can change permissions on your telephony db with this command:

adb shell
su
chmod 666 /data/user_de/0/com.android.providers.telephony/databases/telephony.db

Grab the ID of your current APN using the following command:

adb shell
content query --uri content://telephony/carriers/preferapn

If the type doesn't contain "dun", copy the existing type string and add ",dun" to the end:

In the following command you would substitute
your current type string for "your_type_here",
and the _id for your_id_here:

adb shell
su
content update --uri content://telephony/carriers --where "_id=your_id_here" --bind type:s:your_type_here,dun

I had changed the permissions and the db still refused to update its almost like its checking for newer time stamps.

 

[Fenny]

I had changed the permissions and the db still refused to update its almost like its checking for newer time stamps.

Hmm, could be. I think the selinux context would be switched from

u:object_r:radio_data_file:s0

to

u:object_r:system_file:s0

by that process you describe.
Might be able to chcon the file in place if that is the needed change.

Should be able to "ls -lZ" to check and see which owner, and context the db has on your system after the fix.

 

[sickboy82]

Not working on Sprint. It installs and tethering will enable but connected devices will not get data.

I haven't rooted mine yet, but I know with my previous Nexus devices on Sprint after editing the build prop I had to t

Not working on Sprint. It installs and tethering will enable but connected devices will not get data.

I haven't rooted mine yet, but I know with my previous Nexus devices on Sprint after editing the build prop I had to run in terminal emulator "settings put global tether_dun_required 0" to get it fully functional. I'm not sure if this will help with this method or phone, but it's worth a shot.

Sent from my Pixel XL using XDA-Developers mobile app

 

[Builtfordtough1]

I haven't rooted mine yet, but I know with my previous Nexus devices on Sprint after editing the build prop I had to t

I haven't rooted mine yet, but I know with my previous Nexus devices on Sprint after editing the build prop I had to run in terminal emulator "settings put global tether_dun_required 0" to get it fully functional. I'm not sure if this will help with this method or phone, but it's worth a shot.

I had tried that also did not work

 

[Fenny]

I had tried that also did not work

Well, for now we have a working solution for Sprint users on your particular MNC MCC. I've linked your solution in the OP for now. We can add refinements as we find new or better methods.

 

[Builtfordtough1]

Btw thanks for all your help :laugh:

 

[njinstantkarma]

Already Rooted but looking to root systmenless

I have already unlocked my bootloader installed twrp and also installed SU. (not systemless)
Can I just flash systemless root in twrp. with the flashable zip. OR do I need to uninstall SU (not sure how) and then flash Pixel-PixelXL-Systemless-TetherMod-1.0.zip.
Or is this provided zip file just for tethering assuming you already have SU installed as systemless... Sorry for the confusion

 

[Fenny]

I have already unlocked my bootloader installed twrp and also installed SU. (not systemless)
Can I just flash systemless root in twrp. with the flashable zip. OR do I need to uninstall SU (not sure how) and then flash Pixel-PixelXL-Systemless-TetherMod-1.0.zip.
Or is this provided zip file just for tethering assuming you already have SU installed as systemless... Sorry for the confusion

The zip is for tethering and assumes you have a systemless root that supports su.d. It works by overlaying the modified system files in a bind mount.
SuperSU, by default, roots in systemless mode. However, if you have modified the system partition, you should probably flash it back to stock.

 

[njinstantkarma]

Thanks for the clarification but curious as to why u recommend the following? However, if you have modified the system partition, you should probably flash it back to stock. Is there a way to unroot SU then instal systemless root or is it too late since I modified the system partition

 

[Fenny]

Thanks for the clarification but curious as to why u recommend the following? However, if you have modified the system partition, you should probably flash it back to stock. Is there a way to unroot SU then instal systemless root or is it too late since I modified the system partition

Modifying /system breaks dm-verity. If you want the full benefits of a systemless root, you will want to make sure /system is stock.

Simply undoing changes to the file-system will not make block-based dm-verity pass. All you should need to do is flash system partition and the kernel, you do not need to wipe data. After that, you can flash supersu without issue.

 

[njinstantkarma]

Wow thank you for the Info. I will give it a try. Do I need to add TWRP again or will it stay like my data?

 

[Fenny]

Wow thank you for the Info. I will give it a try. Do I need to add TWRP again or will it stay like my data?

If you flash a stock kernel, you will need to reflash TWRP.

 

[Builtfordtough1]

Works on 7.1.1 on sprint with the sprint workaround.

 

[cjkacz]

How did this work on Verizon? Any APN edits needed?

 

[jasoraso]

Does this method require root after installation of the .apk (or this .zip)? Is it possible to uninstall root after installation?

I'm on VZW and looking for a method to have tethering w/o root (so I can have Android Pay). I want my cake, and eat it too

I tried the method of modifying build.prop, and then I uninstalled root (used the SuperSU uninstall, then flashing stock boot.img, then elemental kernel to mask the unlocked bootloader). However, upon rebooting > I lost the ability to tether