Related
This is just a simple build.prop mod to fix the fingerprint back to the working ERE27 one used in CM. Everything in Settings still shows FroYo, but the Market sees you as ERE27 & thus gives you your protected apps back
To install run this from the directory you unzip the file to:
ADB Method:
Code:
adb remount
adb shell rm /system/build.prop
adb push froyo.prop /system/build.prop
adb shell reboot
Then, once it reboots, go into the dialer, and type
Code:
*#*#CHECKIN#*#*
which is
Code:
*#*#2432546#*#*
for those of you who are too lazy to read the letters
A message should pop up into the status bar after a few seconds depending on your connection speed saying checkin succeeded.
Now you're good to go, open Market and download away
EDIT: Since I know some of you will wonder what this does, it just changes the ro.build.fingerprint & ro.build.description settings back to ERE27. This alone would normally be enough, but you're depending on luck to when you next check in. Dialing that code in the Dialer will force a checkin.
EDIT 2: Thanks to Shafty023 here is a method for the shell:
LINUX SHELL METHOD
Copy froyo.zip to /sdcard, then open a Terminal shell on your phone
Code:
su
mount -o remount,rw /system
cd /system
mv build.prop new.build.prop
unzip /sdcard/froyo.zip
mv froyo.prop build.prop
rm /sdcard/froyo.zip
reboot
Upon booting back up, open Dialer and type in the following code
Code:
*#*#2432546#*#*
Once you see a notification in the notification bar that says checkin succeeded you can now open Market and are done.
Nice! Trying it now.
EDIT: Working great so far. Thanks!
athereal said:
Nice! Trying it now.
EDIT: Working great so far. Thanks!
Click to expand...
Click to collapse
testing it in a few minutes too.... [UPDATE: works like a charm!]
Nice job Geniusdog254! really nice
thanks!
Thanks, works great!
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Part Four said:
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Click to expand...
Click to collapse
Use one of the root file explorers to unzip the file, delete the old build.prop, put the new one in, and then type the command in the dialer
Works like a charm, thanks!
Worked great, THANK YOU!!!!!
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
dudebro said:
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
Click to expand...
Click to collapse
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Mikey1022 said:
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Click to expand...
Click to collapse
yeah, I was wondering if it worked because I was getting checkin failed.
bluehaze said:
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
Click to expand...
Click to collapse
Apps don't have to be updated to take advantage of JIT at all. They can be optimized but they can be optimized without JIT too. There are no different versions. JIT just converts the Java/Dalvik code into native code at app launch, instead of running it through the slower virtual machine. Its like C++ vs Java on a desktop, the native code (C++) is much faster when executed.
The only thing this will lead to is when apps start showing up in the Market as 2.2+ only, but by that point Google will have updated the market to recognize the new footprint.
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
Pure calender widget (agenda) is a protected app taht doesnt show up in the 2.2 market
Edit: Works perfect! Thanks.
If you are having problems with the checkin, make sure your on 3g and not WiFi.
Mi|enko said:
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
Click to expand...
Click to collapse
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Geniusdog254 said:
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Click to expand...
Click to collapse
Yea, im not getting any of the GameLoft games.
serialtoon said:
Yea, im not getting any of the GameLoft games.
Click to expand...
Click to collapse
Even after this?
I'm trying to view my AAA password on my ZTE Warp but haven't been able to find a method that will work. I've tried the usual methods: 1) QXDM via the command "requestnvitemread ds_mip_ss_user_prof". Results in "error response received from target". 2) QPST EFS Explorer, but the nvm folder is locked so I cannot access. 3) CDMA Workshop via reading nv items, but 466 and 1192 both show "Access denied". Hopefully someone can offer some help on this?
AAA password for N860 ZTE/warp
I know ths post is from November, I just had to go through this myself. You can use "logcat" to read this. Start logcat then enter ##3282# open data profile tap on password keys you can then cancel, go back to logcat, read through and you will find the dialer info ##3282# soon after that you will see the HA ,AAA passwords in hex format, problem solved
Thanks for the suggestion. I will try this.
*update: This method worked for me, but only for profile 1 AAA password. Thanks joey716. Still searching for a method to access profile 0 AAA (32 character hex)
did you ever get your aaa key and ha key from logcat??? i need some help
GothTech said:
did you ever get your aaa key and ha key from logcat??? i need some help
Click to expand...
Click to collapse
Yes. I used the procedure described above in post #2.
budgreen24 said:
Yes. I used the procedure described above in post #2.
Click to expand...
Click to collapse
did it work for you i can seem to make heads or tales of mine at all
GothTech said:
did it work for you i can seem to make heads or tales of mine at all
Click to expand...
Click to collapse
Here's basically what I did:
After creating my logcat file (which was saved to my sd card) I connected my phone to computer and copied the file to my pc. Then I opened the file with notepad and in the menu bar selected Edit > Find. In the box I typed in "aaa" without quotes, then clicked Find Next. Notepad then takes you thru the logcat stopping everywhere it finds "aaa". It takes a few clicks on Find Next, but soon you will see something like "init AAAPassword=xxxxxxxxxxxx" . And you should see your 12 digit AAA password instead of the xxxx's. Do the same thing for your 32 digit AAA password. If you look just before those entries you'll see "init HaPassword=736563726574". That's your HA password, which should be 736563726574 like mine. Write them down and you're all set. If you are still having trouble pm me.
ok so now i just need to get to profile 0 now
GothTech said:
ok so now i just need to get to profile 0 now
Click to expand...
Click to collapse
Any luck with profile 0 AAA?
warpjavier said:
Any luck with profile 0 AAA?
Click to expand...
Click to collapse
im still looking for a way to get it
GothTech said:
im still looking for a way to get it
Click to expand...
Click to collapse
Same here.
NVM folder is locked.
warpjavier said:
Same here.
NVM folder is locked.
Click to expand...
Click to collapse
use logcat to get profile one i just cant seem to find profile 0
GothTech said:
use logcat to get profile one i just cant seem to find profile 0
Click to expand...
Click to collapse
That is what we are trying to retrieve, Profile 0 AAA key.
I bet there is a way to unlock NVM folder with a method like HTC phones.
warpjavier said:
That is what we are trying to retrieve, Profile 0 AAA key.
I bet there is a way to unlock NVM folder with a method like HTC phones.
Click to expand...
Click to collapse
how would this be a please tell
GothTech said:
how would this be a please tell
Click to expand...
Click to collapse
On some HTC devices, you create a folder with a "Specific name" in the root of EFS, reboot the phone and NVM folder is accessible. Some samsung devices, you can dump a partition and extract it with magic iso, and see NVM folder, other newer Samsung devices, you downgrade the Modem/Radio and you gain access to EFS file system via QPST.
So I bet there is a method like those mentioned above for the ZTE warp.
Hopefully, someone finds it and post it online. I've tried everything to my knowledge without success.
warpjavier said:
On some HTC devices, you create a folder with a "Specific name" in the root of EFS, reboot the phone and NVM folder is accessible. Some samsung devices, you can dump a partition and extract it with magic iso, and see NVM folder, other newer Samsung devices, you downgrade the Modem/Radio and you gain access to EFS file system via QPST.
So I bet there is a method like those mentioned above for the ZTE warp.
Hopefully, someone finds it and post it online. I've tried everything to my knowledge without success.
Click to expand...
Click to collapse
I was thinking the exact same thing. I've even tried the above methods plus a few other things and no luck.
I was finally able to get my profile 0 AAA password on THE ZTE Warp. I did it with CDMA workshop. All I did was read/save nv item 1192. Opened the file with notepad, and there it was! What's weird though is thats one of the first things I tried a long time ago and it didn't work, just said access denied or whatever. But for whatever reason it worked this time. The only thing I can think of that's different is the rom I'm using.
Sent from my N860 using xda app-developers app
budgreen24 said:
I was finally able to get my profile 0 AAA password on THE ZTE Warp. I did it with CDMA workshop. All I did was read/save nv item 1192. Opened the file with notepad, and there it was! What's weird though is thats one of the first things I tried a long time ago and it didn't work, just said access denied or whatever. But for whatever reason it worked this time. The only thing I can think of that's different is the rom I'm using.
Sent from my N860 using xda app-developers app
Click to expand...
Click to collapse
Please tell us more, because I tried it and it failed.
What OS / Build are you on?
Where you rooted when you were able to read 1192?
Thanks
gadgetdaddy said:
Please tell us more, because I tried it and it failed.
What OS / Build are you on?
Where you rooted when you were able to read 1192?
Thanks
Click to expand...
Click to collapse
Ok, phone is rooted and running this rom : http://androidforums.com/boost-mobi...0-based-viii-ii-full-install-1-23-2013-a.html
Like I said, I tried to read my aaa with CDMA workshop (v2.7) months ago, and it didn't work. I got the "access denied" message for nv 1192. And it worked for me now and the rom is the only thing thats different I think. Hopefully that helps for now. I'll update this later when I get back to my computer.
Sent from my N860 using xda app-developers app
budgreen24 said:
Ok, phone is rooted and running this rom : http://androidforums.com/boost-mobi...0-based-viii-ii-full-install-1-23-2013-a.html
Like I said, I tried to read my aaa with CDMA workshop (v2.7) months ago, and it didn't work. I got the "access denied" message for nv 1192. And it worked for me now and the rom is the only thing thats different I think. Hopefully that helps for now. I'll update this later when I get back to my computer.
Sent from my N860 using xda app-developers app
Click to expand...
Click to collapse
just did that and ran cdma and its still being denied
Heya,
Just wondering how to change the mDNIe profile now that CM10.2 has had the individual device settings removed. Dorimanx has it set to dynamic, which is a bit too bright for my tastes. There are multiple options to tweak the colour with stweaks, however nothing to change the entire profile.
I cant find the mDNIe switcher apk anymore, and the soft tuner app no longer works. Does anyone have any information on how to manually change it back?
Thanks in advance!
I put the device settings apk from 4.2.2 back into 4.3, and used it. Worked fine for the touch keys, I guess it would for the mDNIE profile too. Check my past posts today and yesterday, I've posted it a couple times now. That's including the apk and how to launch it. I'm on mobile now so no link sorry.
The original time I posted it, I set it out with details, but the basic idea is to paste to system/app, set permissions, reboot, then use terminal Emulator to launch it. I posted the terminal code this morning or yesterday, can't remember. If you see the version which is only one line of code, make sure to type "su" & hit enter before typing the second line.
Sent from a galaxy far, far away
Script.
Thanks Hopper, you've solved my issue. For future sake in case anyone else finds the thread. Here's hopper's instructions plus a link to the apk.
Hopper8 said:
1. Download attached apk (I took it from Rootbox 4.2.2, but it works just the same on 4.3).
2. Paste it into /system/app, set permissions to rw-r--r-- and reboot.
3. Enter terminal Emulator, and type:
Code:
su [enter]
am start -n com.cyanogenmod.settings.device/.DeviceSettings [enter]
(obviously don't type [enter], press the enter key....)
4. Device Settings will open up, set whatever you desire
Note: to re-open the app, you will have to do it throught Terminal Emulator again. There's no other way of launching it that I could find, even Titanium Backup doesn't recognise it as able to run.
Big thanks to Unisexist6969 and Markox89 for helping figure this out
Edit: most users of a launcher such as nova or similar should be able to add a homescreen shortcut using nova activities shortcut. Personally this doesn't work for me, I'm not sure why. The method above will work regardless of using a different launcher, or if someone (like myself) doesn't have the option to add a shortcut, or if they plain don't want a homescreen shortcut (also like myself).
Click to expand...
Click to collapse
Morphello said:
Thanks Hopper, you've solved my issue. For future sake in case anyone else finds the thread. Here's hopper's instructions plus a link to the apk.
Click to expand...
Click to collapse
Good man! Glad you found it & it worked
Morphello thanks for digging this up.
Hopper8, thanks for figuring this out.
I was able to use this on the Verizon Note 2 (sch-i605). I was a bit worried that it was specific to the Galaxy S II, and it may be...but it still worked.
Thanks again guys!
sroemerm said:
Morphello thanks for digging this up.
Hopper8, thanks for figuring this out.
I was able to use this on the Verizon Note 2 (sch-i605). I was a bit worried that it was specific to the Galaxy S II, and it may be...but it still worked.
Thanks again guys!
Click to expand...
Click to collapse
Which ROM are you running, and how did you get it to work on your VZW Note2?
I copied it it to /system/app and changed the permissions and rebooted, but when I run the commands in terminal emulator i get an error:
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
I cannot find the activity shortcut in Nova either.
Thank you
mising said:
Which ROM are you running, and how did you get it to work on your VZW Note2?
I copied it it to /system/app and changed the permissions and rebooted, but when I run the commands in terminal emulator i get an error:
Error: Activity class {com.cyanogenmod.device/com.cyanogenmod.device.DeviceSettings} does not exist
I cannot find the activity shortcut in Nova either.
Thank you
Click to expand...
Click to collapse
I apologize for the VZW Note II turn this GS II thread has taken.
I didn't do anything special other than follow the instructions laid out by Hopper8. I'm using a PAC rom (pac_i605_4.3-build.1.RC_20130830-090438) I got from gchild320.
sroemerm said:
I apologize for the VZW Note II turn this GS II thread has taken.
I didn't do anything special other than follow the instructions laid out by Hopper8. I'm using a PAC rom (pac_i605_4.3-build.1.RC_20130830-090438) I got from gchild320.
Click to expand...
Click to collapse
I followed exactly also, but I am using CM10.2 nightly...Good excuse to try another ROM though.
Oops, didn't realize I was hijacking, I will move this question to the VZW Note 2 section.
Root:
1. Enable Unknown Sources under Security
2. Unlock Developer Options
3. Enable Usb Debugging
4. Install Kingroot
http://www.kingroot.net
5. Run the app and follow instructions until root
6. Download mrw folder
http://www.4shared.com/zip/HucTEoJoba/mrw.html
then place it in the root of Device Storage using the Default app "MyFiles"
7. Install ROM Toolbox Pro
http://www.4shared.com/mobile/c87lgrS4ba/ROM_Toolbox_Pro_v6065.html
8. Run the app and Grant Root Permission
9. Open Terminal Emulator under Tools tab
Enter Commands as follow:
su
sh /sdcard/mrw/root.sh
10. Let it run
11. After is done it will open SuperSu
12. Update Binary as Normal
13. Reboot
14. Your done :good:
Enable Tethering
Using a root file explorer such as ES File Explorer or your preferred file manager, mount /system rw. Navigate to /system and find and open the build.prop file.
Find..
Code:
# Disable Tethering (Tracfone)
ro.tether.denied=true
Change to...
Code:
# Disable Tethering (Tracfone)
ro.tether.denied=false
Save the file, make sure its permissions are set to -rw-r--r--, reboot and Tethering will be available in the settings menu.
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Koenji said:
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Click to expand...
Click to collapse
Nope, any SIM other than a Verizon Wireless one will simply say Invalid SIM.
bfoos said:
Nope, any SIM other than a Verizon Wireless one will simply say Invalid SIM.
Click to expand...
Click to collapse
If you don't mind telling me, what process is the one required so that the phone recognizes SIMS from other companies? Flashing? Sorry for the amateur question.
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
bfoos said:
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
Click to expand...
Click to collapse
I guess i will wait a bit for those tools before i give up and try to sell this device since its no use to me, being unable to use SIMS for other companies.
Koenji said:
I guess i will wait a bit for those tools before i give up and try to sell this device since its no use to me, being unable to use SIMS for other companies.
Click to expand...
Click to collapse
You may use a verified online website to sim card unlock the phone to any company
Koenji said:
Excuse me, does this "Rooting" process allows me to use the micro Sim of any company?
Click to expand...
Click to collapse
No sir im sorry
ordinarykid23 said:
You may use a verified online website to sim card unlock the phone to any company
Click to expand...
Click to collapse
I can confirm that this does in fact not work. Invalid SIM. No unlock menu.
bfoos said:
I can confirm that this does in fact not work. Invalid SIM. No unlock menu.
Click to expand...
Click to collapse
Thanks for the information fellas. So basically we have to wait until someone with the knowledge can extract those files (Roms, kernels, recoveries).
By some of the comments i've seen here, i get the impression that only the high-end phones are the ones that the community gets behind? How unfortunate if true.
By the way i saw in a different post someone uploaded a Rom http://forum.xda-developers.com/grand-prime/development/rom-download-sm-s920l-straight-talk-usa-t3265004/page2
Yes, and that ROM will turn your Grand Prime into a Core Prime (Franken Prime) with lots of things not working. There are no stock roms available for this variant.
bfoos said:
Yes, and that ROM will turn your Grand Prime into a Core Prime (Franken Prime) with lots of things not working. There are no stock roms available for this variant.
Click to expand...
Click to collapse
Thanks for the warning.
i cant get the build.prop to save after editing the data tethering line... idk how to set the permisions on the file
Galaxy Grand Prime Value Edition 5.1.1
Hello guys can you help me. ? Android os is draining battery like hell .About 4-5% and it's the second after screen. Before this facebook messenger and facebook was sucking my battery . I uninstalled them.. but android os is still draining my battery.. what I should do ? It' draining about 10-15 % overnigh . I have installed greenfy and i just have only wifi opened.. but it's still draining. Please helpp
Spartacus first you have to be root, then es editor to edit the build.prop, close out and reboot...should see the the tether option enabled...worked flawless for me
NullByte04 said:
Spartacus first you have to be root, then es editor to edit the build.prop, close out and reboot...should see the the tether option enabled...worked flawless for me
Click to expand...
Click to collapse
i actually was able to do it, using the rom tools thing that the guy provides in his steps
Yea that works to both shouldn't have a issue with
Can someone pull all system files from a (preferably) completely stock or factory reset device via adb? Please! Thank you!
Sent from my HTCD200LVWPP using Tapatalk
bfoos said:
I have no idea. There isn't anything to flash. No roms, no kernels, no recoveries no nothing. There appears to be zero interest in this variant by the dev community.
Click to expand...
Click to collapse
yeah ik theres alot of interest but no ones developing for it id love to but i dont know much for baking android os id take a look into the s5 and s6 area since it uses a bit of the same software.
For anybody that cannot get tethering working on your phone, follow these steps. This is for stock rooted 6.0.1 roms. May not work on "n" preview.
1. Edit build prop and add the following line
net.tethering.noprovisioning=true
2. Download terminal emulator from play store. Open terminal emulator and type in "su" without the " marks and press enter. Grant terminal emulator super user privileges. Next, type the following line into emulator.
put settings global tether_dun_required 0
Press enter, it will pause for a second and then return to command line. Close out terminal emulator.
3. Reboot phone and you should be good to go. I have to do all this to get it working on Sprint.
Sent from my Nexus 6P using XDA-Developers mobile app
Damn. It works fine for me on Verizon with my UDP out of the box.
Sent from my Nexus 6P using Tapatalk
I have read it works out of the box as well. Then you ask more questions and find out they have tethering included in there plan in some capacity.
Sent from my Nexus 6P using XDA-Developers mobile app
Micronads said:
For anybody that cannot get tethering working on your phone, follow these steps.
1. Edit build prop and add the following line
net.tethering.noprovisioning=true
2. Download terminal emulator from play store. Open terminal emulator and type in "su" without the " marks and press enter. Grant terminal emulator super user privileges. Next, type the following line into emulator.
put settings global tether_dun_required 0
Press enter, it will pause for a second and then return to command line. Close out terminal emulator.
3. Reboot phone and you should be good to go. I have to do all this to get it working on Sprint.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
actually i tried that command in adb and for some reason it would not have any effect on the provisioning pop up screen..i was not able to tether. i am on Android N preview II and i had to go into root explorer and delete the " entitlement.apk" and added to build.prop : net.tethering.noprovisioning=true . thank me later...
I am on ATT unlimited plan, they do not offer tethering on that plan AT ALL.
I have not tried on n preview. I will change first post to indicate this is for stock rooted 6.0 roms
Sent from my Nexus 6P using XDA-Developers mobile app
i42o said:
actually i tried that command in adb and for some reason it would not have any effect on the provisioning pop up screen..i was not able to tether. i am on Android N preview II and i had to go into root explorer and delete the " entitlement.apk" and added to build.prop : net.tethering.noprovisioning=true . thank me later...
I am on ATT unlimited plan, they do not offer tethering on that plan AT ALL.
Click to expand...
Click to collapse
I'm on AT&T grandfathered unlimited plan and trying to get tethering going on my Nexus 6P. Would this still work on 7.1.1?
rsnyc said:
I'm on AT&T grandfathered unlimited plan and trying to get tethering going on my Nexus 6P. Would this still work on 7.1.1?
Click to expand...
Click to collapse
yes. i believe that the entitlement app is what authenticates the hotspot feature . once you delete it go in to system> build prop and add the line and it should work.
for me tethering with foxfi and pdanet on computer via usb cable and tmobile cannot detect this yet. only way to tether without detection
att grandfathered unlimited
I need help. I have no idea what I am doing. I am reading as I go along. I have rooted my phone and would like to learn how to tether my att I927. I understand you guys are extremely advanced and I am NOT trying to get ripped a new one. So please tell me where I should go on here for beginners. Please, Thank you.
rsnyc said:
I'm on AT&T grandfathered unlimited plan and trying to get tethering going on my Nexus 6P. Would this still work on 7.1.1?
Click to expand...
Click to collapse
i42o said:
yes. i believe that the entitlement app is what authenticates the hotspot feature . once you delete it go in to system> build prop and add the line and it should work.
Click to expand...
Click to collapse
It worked! I used root explorer as my file manager, deleted the entitlement apks, added the build.prop line, rebooted and success. I was able to test it with my laptop and it worked. Thanks!
---------- Post added at 06:56 AM ---------- Previous post was at 06:54 AM ----------
i42o said:
actually i tried that command in adb and for some reason it would not have any effect on the provisioning pop up screen..i was not able to tether. i am on Android N preview II and i had to go into root explorer and delete the " entitlement.apk" and added to build.prop : net.tethering.noprovisioning=true . thank me later...
I am on ATT unlimited plan, they do not offer tethering on that plan AT ALL.
Click to expand...
Click to collapse
It worked! I used root explorer as my file manager, deleted the entitlement apks, added the build.prop line, rebooted and success. I was able to test it with my laptop and it worked. Thanks!
On magisk you got a tethering enabler module in the download section, but I'm sry, I can't test it for US providers