Related
I followed the instructions according to mdalacu
Working great, and all i had to do was to change only 2 lines in buid.prop using ES File explorer with 2 options activated: Root Explorer and Mount File System.
1. Be sure that you have root
2. Install ES File explorer and Options and check this: Root Explorer and Mount File System
3. Navigate to /system. Long press on buid.prop , open as text.
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
5. reboot
6. install from market box (box.net)
7. Create the account. A confirmation message will appear that you have 50 GB capacity.
8. Again from EFS File Explorer navigate to /system. Check that you have a file named build.prop.bak and if so, delete buid.prop. Rename build.prop.bak into build.prop. Now you can disable from options : "Root Explorer" and "Mount File System"
9. Reboot
10. Enjoy your amizing phone
Note: I had done this on KL7 with stock kernel.
Was able to create a bunch of accounts, then deleted the build.prop file and renamed the build.prop.bak back to build.prop, rebooted the phone, and I get to the Samsung Galaxy Note N7000 screen, then it goes black. I cannot boot up the device now.
Any suggestions?
yeahmon said:
4. Edit the file by modifying this lines:
ro.product.model=GT-N7000
ro.product.brand=samsung
into
ro.product.manufacturer=LGE
ro.product.model=VS910 4G
Click to expand...
Click to collapse
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
bnapalm said:
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
bnapalm said:
I don't think you are supposed to change "brand" to "manufacturer". For me, there was already a "ro.product.manufacturer" value (edit: of course, I also changed the "model" value) and I just changed that.
However, I don't see how this could have caused your problem. Are you sure you renamed the backup file "build.prop" correctly? Maybe accidentally left a symbol there, or deleted one too many?
Click to expand...
Click to collapse
It worked, and I was able to reboot back into the Note with these settings.
jayshah said:
Sounds like OP deleted the build.prop and perhaps the rename failed and didn't notice, so now they have no build.prop file whatsoever.
--
Are you able to access the device using a cable via adb (is USB debugging enabled on your phone)?
I know nothing about rooting the Note just yet, though if it's the same setup as G1/Nexus/Desire (I guess it would be) you should be able to get into recovery then use adb at a command line to push a new build.prop file to /system which should allow your device to boot.
Click to expand...
Click to collapse
I think you're right about losing the build.prop file. Fortunately, I backed it up. I am trying to access the device now. I have no GUI on the Note. I am hoping it is just a blank screen and the device is still functioning in the background. I'll be back momentarily with an answer to accessing it.
ok...I can access the Note's file system. However, when I try to copy the backup build.prop file into the system directory via Android Commander, it says I need root access to do this permission.
The Note IS rooted. I don't get it.
This appears to be a problem with Android Commander. There are threads about this same problem, but rather than the software creator place a link to his FAQ that he ridicules everyone for not reading, he lambasts them instead. Thats a real good way to get a donation.
Anybody got any other suggestions for a root file explorer, preferably for Mac, but PC will work too.
be careful, backup buid.prop and restore it after creating Box account.
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
I am having no luck finding a way to get root access from a computer.
deleted post
user error
The tumbleweeds are big around here
There's an app for that
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
But is there an app to copy my file over from my computer?
amincom said:
be careful, backup buid.prop and restore it after creating Box account.
Click to expand...
Click to collapse
vcespon said:
Without having to edit files and without root.
http://www.androidguys.com/2011/12/28/get-50gb-of-free-box-cloud-storage-without-rooting/
Click to expand...
Click to collapse
Please read the OP before posting.
--
The fact that you are using Android Commander implies you have adb access, this is good.
Here's what I would do to fix your problem, it definitely isn't the only way, but it will work.
#1: Get ADB installed on your PC/Mac/Linux
#2: Open a command line and run
Code:
adb devices
as a test, you should get output that one device is connected via cable, if you don't abort here, nothing else will work
#3: run
Code:
adb remount
This will make your /system writeable
#3: I'll put this as a windows instruction because I don't know the Mac filesystem, but it's almost identical
Code:
adb push C:\build.prop /system/
This will push C:\build.prop (please put your backup copy here) into /system/ of your Note. If you're on a mac, you will need to find another place to put it, e.g. if it's /users/bob/build.prop the command just becomes
Code:
adb push /users/bob/build.prop /system/
I hope this helps
Edit: Paste a copy of output here if it doesn't work so I can help debug
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
yeahmon said:
I was onto this earlier but a Command line gets me this:
'adb' is not recognized as an internal or external command, operable program or batch file.
Click to expand...
Click to collapse
You'll need to download/install adb first.
jayshah said:
You'll need to download/install adb first.
Click to expand...
Click to collapse
standby...
its taking forever to install SDK
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
I should have stuck with Dropbox.
yeahmon said:
This is a lost cause.
No matter what I do, I get the same errors. Anything I try to do to remedy the issue only opens another door to hell.
Click to expand...
Click to collapse
You're really going to have to paste the error messages here for any of us to help you further
Alternatively, can't you just reflash your current ROM on top?
Has anyone received N900VVRUBMJE yet?
Not yet. I wonder if it will break root and the free Wi-Fi tethering
Sent from my SM-N900V using Tapatalk
iceman6996 said:
Not yet. I wonder if it will break root and the free Wi-Fi tethering
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
One of the mentioned updates on the little graphic for the update was "Mobile Hotspot reliability has been improved" , so I'll be very surprised if the Home button trick still works
I'm very much looking forward to better Cellular reliability. With MJ7, I often can't make a call. No signal whatsoever. If I change to MI9, I have much better reception and reliability. Not great but much better. I'm hoping MJE will be great. Fingers crossed!
What home button trick? Sorry for the noobiness...
MrWilliams2 said:
What home button trick? Sorry for the noobiness...
Click to expand...
Click to collapse
When you start the mobile hotspot and youre not subscribed it pulls up an error box telling you to subscribe. You just hit the home button and it goes away and the hotspot still stays on and works
NeoMagus said:
When you start the mobile hotspot and youre not subscribed it pulls up an error box telling you to subscribe. You just hit the home button and it goes away and the hotspot still stays on and works
Click to expand...
Click to collapse
Even if VZW fixes Hot Spot, there is a Tether patch available that will allow the hot spot to bypass the subscription check. Runandhide05 made up a .zip yesterday for the N2 running 4.3 and it works flawless.
Does this zip work for non-root, or only rooted N3s?
Cheers,
B.D.
droidstyle said:
Even if VZW fixes Hot Spot, there is a Tether patch available that will allow the hot spot to bypass the subscription check. Runandhide05 made up a .zip yesterday for the N2 running 4.3 and it works flawless.
Click to expand...
Click to collapse
Have a link to this zip? apparently the update did kill the home button bypass
Did you get the update?
NeoMagus said:
Have a link to this zip? apparently the update did kill the home button bypass
Click to expand...
Click to collapse
I got it a few minutes ago. Too soon to tell if there are any improvements.
I took the ota with root survival mode checked on the Super su pro app and kept root just fine..I first unistalled xposed and modules, defrosted the bloat I had froze with titanium, checked ota survival mode with Super SU Pro (Paid Version) while keeping root enabled, Rebooted, took OTA and it works fine while maintaining root.....to early to notice any improvements but I have notice spell checker is enabled on the Samsung keyboard...+1!
Sent from my VZW Note3..ha..ha..
I get an error while its trying to update on my stock slot following jankers method
Sent from my SM-N900V using Tapatalk
NeoMagus said:
One of the mentioned updates on the little graphic for the update was "Mobile Hotspot reliability has been improved" , so I'll be very surprised if the Home button trick still works
Click to expand...
Click to collapse
It will not work since the patch is tied into the frame work. Will need a dev to pull the update and apply the patch.
So I can enable keep root and safely update?
Sent from my SM-N900V
droidstyle said:
It will not work since the patch is tied into the frame work. Will need a dev to pull the update and apply the patch.
Click to expand...
Click to collapse
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Thanks for this. How would I modify my own file instead of copying yours?
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Worked great! Thanks!!!
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Thanks for posting this, you kick ass! I have one question, I thought that KNOX worked in such a way that modifying anything in System could result in bad news for the KNOX fuse.. Just wanted to confirm, this didn't trip it on your device and shouldn't on mine?
Thanks again for posting this.
razzbaronz said:
Thanks for this. How would I modify my own file instead of copying yours?
Click to expand...
Click to collapse
Modify framework-res.apk with apktool
bschrib said:
Thanks for posting this, you kick ass! I have one question, I thought that KNOX worked in such a way that modifying anything in System could result in bad news for the KNOX fuse.. Just wanted to confirm, this didn't trip it on your device and shouldn't on mine?
Thanks again for posting this.
Click to expand...
Click to collapse
Didnt trip it. You should be good
Sent from my SCH-I545 using XDA Premium 4 mobile app
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Fvolfrine said:
Worked for me, but I used Root Browser. Glad to have tethering on N.
Edit: Scratch that, I added the net.tethering line to build.prop, but when I go into settings and turn tethering on, it tries for a few seconds and fails.
Click to expand...
Click to collapse
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
n3ck0man said:
What I did and always do is to modify my APN; where it says APN type i just add DUN and save the file.
Like this: default,supl,mms,dun
After you hit save your internet connection will reset itself, then everything should be good.
Click to expand...
Click to collapse
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Fvolfrine said:
Sorry, no luck with that. I added the dun, now my APN type reads "default,mms,supl,fota,hipri,dun" and the net.provisioning line is in, but when I toggle the tethering switch it fails. I wonder if this is like the dark theme toggle, which requires several attempts before it works.
Click to expand...
Click to collapse
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
hsomnus said:
Try the fx explorer and its root add on...both are free. You just have to change it to open files in r/w in menu before opening the build prop file.
Mine has been working fine and i didnt have to make several attempts...it worked after the first try. Didnt change to DUN either. Only did exactly what i listed in OP...nothing more.
Click to expand...
Click to collapse
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Fvolfrine said:
That worked! I thought that using Root Explorer, which also has R/W capability, would be just the same, but I guess I was wrong.
Click to expand...
Click to collapse
Yeah...i tried root explorer first as well as a few others. This was the only one that worked.
Worked for me. Thanks!
hsomnus said:
I have successfully edited build prop on Android N Preview to allow tethering. My setup is as follows: I was originally rooted on Pure Nexus. I reflashed stock 6.0.1 MM and unrooted my device. I took the Android N OTA and rooted via CF Auto Root by Chainfire ( I had to manually fastboot the CFAR image as the program provided kept failing). I tried various root file managers that did not work. Finally FX Explorer with the root add-on worked. I had to change the file manager to open files in R/W mode via the menu settings. After that I was able to open the build prop file in text editor and added "net.tethering.noprovisioning=true" (without quotes) at the bottom or end of the file. I rebooted and am able to tether without the subscription check. I am on an unlimited data plan. Hope this helps.
Click to expand...
Click to collapse
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Erik Rye said:
thanks! thinking about trying this for 6.0.1 until N and after. I'm on project fi tho and don't know if that's a jinx
Click to expand...
Click to collapse
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Fvolfrine said:
Isn't tethering allowed on Project Fi?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, tethering is allowed on project fi. I was hoping that no subscription check = no data charges but not sure that's possible..
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
wideasleep1 said:
What providers is this succeeding on? Anyone on TMO?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Anyone tried sending the tether command just like on m?
5ghz tethering
blitzerking1 said:
I've successfully unlocked tethering on Sprint but I get a DNS error when I try to load websites on my PC.
Click to expand...
Click to collapse
I'm currently sprint, I input the dun_required 0 by terminal emulator and net.tethering by fx explorer. My tethering wouldn't stay active until I switched to 5ghz frequency in tether settings. I connected my ipad and searched pages to verify.
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
ForeverZ3RO said:
For some reason when I try to mount build.prop as read/write I get an "error: this action could not be completed" within FX Explorer. I can however, mount the system folder with no problems. Seems to be an issue mounting just the build.prop. Any ideas?
Click to expand...
Click to collapse
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
kwdan said:
I tried all of the suggestions in this thread until I found one. I can't remember which one worked.
Click to expand...
Click to collapse
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
ForeverZ3RO said:
Ummmm... ok. I've looked through all of the posts in this thread and can't find any with my issue. Not sure how you got it to work.
Click to expand...
Click to collapse
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
kwdan said:
I used terminal emulator to add the tethering_dun_required 0
And fx explorer, or root explorer or root browser (not sure which one) to add provisioning line. Then rebooted. Tethering would still turn on and off until I went into tethering settings and switched it to 5ghz.
Click to expand...
Click to collapse
Any chance you could post the steps for doing it with the terminal emulator?
Also, didn't you still have to mount the system folder as R/W? That's where it's failing at for me.
Hi after a few days of tinkering with the native hotspot to work, i finally got it working. Im going to try to make it as easy as possible to follow the guide in aiding to get it to work for you.
I'm also going to try to create a automatic script to do it when I get some time.
My device:
Unlocked Pixel XL
Network: Sprint (Should theoretically work for all.)
Requirments:
Hackers Keyboard (From play store)
https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard&hl=en
Termux (From play store)
https://play.google.com/store/apps/details?id=com.termux
Unlocked Bootloader
ElementX Kernel
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/kernel-elementalx-pxl-0-02-t3487072[/URL]
Chainfire's Root method
Forum: [url]http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156[/URL]
Steps:
Make sure you are rooted and have the ElementX kernel installed
Install Termux [From Playstore]
Install Hackers keyboard [From Playstore]
Open up termux
Type in su
Press Enter
Grant SuperSU access
Type mount -o rw,remount /system_root
Press Enter
Type in
cd /system_root/system/
Press Enter
apt-get install nano
Press Enter
This is a symlink binding to the directory that will allow us to modify build.prop
Nano is an editing application that's intuitive and easy to use.
Type in
settings put global tether_dun_required 0
Press Enter
Then type in
nano build.prop
Scroll all the way down to the end of the line, and add the following
net.tethering.noprovisioning=true
Using the hackers keyboard layout in landscape view press ctrl + x then press Y then Enter
Reboot your device and start the tethering, it should be able to turn on a hotspot with no errors. I may or may not work for all, but it did work for me so hopefully those out there that needed this will be able to benefit as well.
All screenshots
https://drive.google.com/open?id=0B94c0AYYx44RTENkcm0wLU5MbEE
RESERVED
Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.
josephcsible said:
Why use nano? You can just do "echo net.tethering.noprovisioning=true >> /system/build.prop" and not have to worry about special keyboards or apt-get installing anything.
Click to expand...
Click to collapse
That work's too I forgot about that
But it needs to be
echo net.tethering.noprovisioning=true >> /system_root/system/build.prop
Since current root is systemless and the partition layout won't let you just touch the system directory without the symlink
This does not work on Verizon's network running Elemental X and build NDE63P
Not looking to thread crap, but just wanted to share my experience and get opinions:
I rooted previously using Chainfire's method. Granted root access to ROOT EXPLORER app----purchased several years ago.
Went into the system folder and opened the build.prop file.
Added the last line: net.tethering.noprovisioning=true and saved and rebooted.
This took a total of 2-3 minutes. I know not everyone wants to spend money, but for those that already purchaed ROOT EXPLORER, was my method OK?
Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?
psychatog64 said:
Let me see if this is right so basically open root explorer then open system_root directory then system directory then open and edit build prop and put that line into the build prop net.tethering.noprovisioning=true >> ? So just that including the arrows?
Click to expand...
Click to collapse
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.
diesteldorf said:
Almost.....
I went in to the system directory and opened and edited the build.prop file
I only added the following line, with no extra arrows.
net.tethering.noprovisioning=true
I saved and rebooted and native tethering works.
Root Explorer will save your original build.prop file as a backup.
Just for kicks....I switched back to my original build.prop file to check results.
As expected, tethering failed. When I re-edited the file and added net.tethering.noprovisioning=true
it was working again. Good Luck.
Click to expand...
Click to collapse
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
Click to expand...
Click to collapse
Or is this meant for like Bluetooth tethering and USB tethering
psychatog64 said:
Now this makes what work exactly the wifi hotspot under setting cause I didn't do this yet and I just clicked it and it turned on so idk what this does exactly
---------- Post added at 02:14 AM ---------- Previous post was at 02:13 AM ----------
Or is this meant for like Bluetooth tethering and USB tethering
Click to expand...
Click to collapse
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.
diesteldorf said:
editing the build.prop and adding net.tethering.noprovisioning=true allows you to turn on the PORTABLE Wi-Fi hotspot from within the settings menu.
Certain carriers disable tethering my default, depending on your plan.
If you are already able to turn it on without making any changes, it's possible your carrier and/or plan already allows tethering by default.
Click to expand...
Click to collapse
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life
psychatog64 said:
Interesting I have the Verizon old xl plan the 12 GB with 12 GB bonus data for life
Click to expand...
Click to collapse
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop
harritaco said:
This does not work on Verizon's network running Elemental X and build NDE63P
Click to expand...
Click to collapse
The bootloader is unlocked and you have the latest chainfire root correct?
diesteldorf said:
You don't have an unlimited data plan and Verizon allows tethering by default. That's why you don't have to make any build.prop changes to enable hotspot.
If you were on a legacy Unlimited plan, Verizon and others will have hotspot blocked, unless you pay extra or bypass the block by editing the build.prop
Click to expand...
Click to collapse
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop
stuntnmore said:
It shouldn't matter about the plan, the additional lines should bypass it. Can you send me a logcat and your build.prop
Click to expand...
Click to collapse
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
Code:
net.tethering.noprovisioning=true
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon
sd_shadow said:
His point is that with Verizon hotspot works out of the box on all plans except unlimited data plans
If you have a Verizon Unlimited data plan just add
to the build.prop and reboot
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
The custom kernel, terminal, and custom keyboard are not needed with Verizon
Click to expand...
Click to collapse
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.
stuntnmore said:
Also this
settings put global tether_dun_required 0
That'll need to be put into termux that's how it worked for me. I tried both the unlocked and Verizon version. And yeah your right about the Verizon part of it.
Click to expand...
Click to collapse
I'm on Verizon unlimited all I did was edit the build.prop
Sent from my XT1254 using XDA Labs
sd_shadow said:
I'm on Verizon unlimited all I did was edit the build.prop
Click to expand...
Click to collapse
Oh that's great to hear glad it works for you
No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.
335Deezl said:
No need for all of this. I just verified that the following works:
1. Install Network Signal Refresher Lite from the Playstore
2. Open both Network Signal Refresher and the Mobile Hotspot in split screen.
3. Hit the Refresh button in Network Signal Refresher and the quickly turn on Mobile Hotspot.
4. Profit!
Hope this helps.
Click to expand...
Click to collapse
It's a need for those who wish for it to work all the time via toggle not to use an app every time, it's a lot more efficient.
Solved Is there a way to disable "10 attempts remain before device data is deleted"
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks
fuzzynco said:
I'm on a VZW 7.0 stock s-off locked rooted (SuperSU systemless) busybox systemless
Is there a way to stop Android from erasing the phone if the lock screen is
misentered 10 times? I mean other than turning off the lockscreen.
Thanks
Click to expand...
Click to collapse
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>
andybones said:
You can edit the system\customize\ACC\default.xml
Code:
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]10[/B][/COLOR]</item>
[B][COLOR="Red"]to[/COLOR][/B]
<item type="integer" name="devicepolicy_max_fail_passwords_for_wipe">[COLOR="Red"][B]0[/B][/COLOR]</item>
Click to expand...
Click to collapse
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?
fuzzynco said:
That worked, but I lost advanced calling, (presumably due to modifying /system), sigh.
Restored system from TWRP backup and advanced calling works again,
I wonder if there is a way to do it with Magisk?
Click to expand...
Click to collapse
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.
andybones said:
Sorry I should had realized that from your OP.
A Magisk module can def be created I'm sure, however I haven't dug into creating any, so I'll take a look - but if others are reading this and don't mind lending a hand that's be great.
Click to expand...
Click to collapse
1. Copy (don't move) default.xml from \system\customize\ACC to a new folder \cache\magisk_mount\system\customize\ACC\.
2. Edit the copied (not original) default.xml in the magisk_mount subfolder as per @andybones' instructions in post 2.
3. You should be good to go.
I have made other tweaks (from time to time) in that file and Magisk mounts it just fine.
.
Works ! with advanced calling.