Related
Hi guys, Trying to get wifi tether set up on my unlocked, rooted Republic Wireless Moto X.
I've followed the guides for the VZW / ATT units, and they partially work but not quite. Seems the RW app has some conflicts with it.
I followed the guide here for "Wifi tether for root users" http://forum.xda-developers.com/showpost.php?p=52664158&postcount=4
It does partially work. It will successfully start tether, but you cannot change the SSID, and cannot enable encryption. No matter what you put in the "SSID" it will always show up as "wlan0" for the SSID, and unsecured. But I can connect and use the tether succcessfully (albeit with no encryption and strange SSID)...
But you CAN successfully connect and use tether. The main problem is that when you STOP tether, wifi will NOT re-enable. You have to reboot the device to get it (wifi) working correctly again. This means you will need to reboot after each time you tether....not to mention not being able to change SSID / enable encryption.
I also tried the Xposed module, and following instructions here: http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-tether-apk-t2601859
Also followed all steps including #6 (SPRINT ONLY - change build.prop file) (since this is sprint MVNO).
This also APPEARS to work correctly, but when I change Wifi tether for root users to use the "Native tethering", it STARTS, then it says (and I quote) "What the hell! The phone just took back wifi control???"
So it seems the RW app is preventing native tether from working.
There must be some kind of solution for us. Maybe temporarily disabling the RW app until after finished tethering, then re-enabling it?
I'd like tether to work mostly seamlessly, and don't want to have to reboot phone after each time tethering.
Any suggestions / ideas?
Thanks
-samwathegreat
samwathegreat said:
snip
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/how-to-wifi-tether-stock-4-2-2-t2449534
Follow this link.
Change the file extension from .man to .apk and install.
Follow the rest of the set up guide for tether.
!
Cyphir said:
http://forum.xda-developers.com/moto-x/general/how-to-wifi-tether-stock-4-2-2-t2449534
Follow this link.
Change the file extension from .man to .apk and install.
Follow the rest of the set up guide for tether.
Click to expand...
Click to collapse
Thanks Cyphir!
I will try this as soon as I arrive home.
I see that this guide is for 4.2.2.....I'm assuming it also applies to kit kat? Also, I checked that link, and it already has the apk extension.... I'm not seeing a .man extension...
Will reply back with results....
samwathegreat said:
Thanks Cyphir!
I will try this as soon as I arrive home.
I see that this guide is for 4.2.2.....I'm assuming it also applies to kit kat? Also, I checked that link, and it already has the apk extension.... I'm not seeing a .man extension...
Will reply back with results....
Click to expand...
Click to collapse
Thanks!!! Ok...very interesting. If I download that file on laptop, it downloads with APK extension, but if I download on phone it downloads MAN extension....
So followed instructions, and it does allow me to set SSID and encryption (THANKS!) But I'm still having some issues. Observations below:
1. When you have just rebooted your device, and click to start tether, it doesn't work (and no SSID is broadcast). But if you stop tether and start again, it does work.
2. If you follow all instructions in the linked post, but ALSO check the box for "Reload Wifi Driver 2", tether still does not start on first attempt after fresh reboot. Again, stopping and starting again works.
3. Wifi is NEVER restored correctly after reboot. It DOES reconnect to wifi, but the android OS doesn't know it. If you go into wifi settings, it will say you aren't connected, and if you try it will 'fail'....but if you check your router, the phone IS connected. But the WIFI icon completely disappears and is not restored. It won't come back until you reboot.
Also, after stopping tether, the Republic app says: "Not Connected to Wi-Fi" and underneath that "Great! Wi-Fi Calls, messages, and data" Very strange. Reboot fixes everything.
So thank you very much! You got me SSID change and encryption. Now I need to find a solution to:
1. I'd like tether to work first time. I still have to (after fresh reboot) start, stop, and start again for it to work.
2. Need to fix Wifi icon after tethering stops without having to reboot.
samwathegreat
samwathegreat said:
snip
Click to expand...
Click to collapse
That is very strange. I set it up just as the link said to, granted SU and it works perfectly the first go around. Make sure that all the settings are exactly as the post says.
It reconnects to WiFi for me right away when turned off as well.
Cyphir said:
That is very strange. I set it up just as the link said to, granted SU and it works perfectly the first go around. Make sure that all the settings are exactly as the post says.
It reconnects to WiFi for me right away when turned off as well.
Click to expand...
Click to collapse
Ok yes, very strange. So you are on 4.4.2 Kit Kat, right? Although I haven't changed *anything* and until a couple days ago I was locked & stock, I'm considering SBFing back to stock and starting over. Before I do, I'd like to make sure you're on 4.4.2 and not jellybean.
So it starts first time for you, and wifi icon comes back immediately after stopping?
Also, does your republic app (in the pulldown status bar) say "Not connected to Wi-Fi, Great! Wi-Fi Calls, messages, and texts"?
samwathegreat
samwathegreat said:
Ok yes, very strange. So you are on 4.4.2 Kit Kat, right? Although I haven't changed *anything* and until a couple days ago I was locked & stock, I'm considering SBFing back to stock and starting over. Before I do, I'd like to make sure you're on 4.4.2 and not jellybean.
So it starts first time for you, and wifi icon comes back immediately after stopping?
Also, does your republic app (in the pulldown status bar) say "Not connected to Wi-Fi, Great! Wi-Fi Calls, messages, and texts"?
samwathegreat
Click to expand...
Click to collapse
Yes, running 4.4.2. I was probably the first RW member with an unlocked bootloader. I fastboot/mfastboot ed back to stock 4.2.2 to remove root when I was still on 4.2.2 then used the update.zip to OTA to 4.4.2 then reflashed TWRP and SU.
Are you safestrapped running 4.4.2 or are you running stock 4.4.2 from OTA with root gained from TWRP and SU?
If you are going to SBF back to stock, just SBF the RW 4.4.2 and then reflash TWRP and SU. If the app still fails after that, then I am not sure.
Cyphir said:
Yes, running 4.4.2. I was probably the first RW member with an unlocked bootloader. I fastboot/mfastboot ed back to stock 4.2.2 to remove root when I was still on 4.2.2 then used the update.zip to OTA to 4.4.2 then reflashed TWRP and SU.
Are you safestrapped running 4.4.2 or are you running stock 4.4.2 from OTA with root gained from TWRP and SU?
If you are going to SBF back to stock, just SBF the RW 4.4.2 and then reflash TWRP and SU. If the app still fails after that, then I am not sure.
Click to expand...
Click to collapse
No safestrap...was never rooted until after 4.4.2 (thanks to china bl unlock).
That was the idea...just sbf, then flash twrp from bootloader, and install su from twrp. I guess I'll try that. I can't imagine why or how mine won't work....but if yours is working, then it must be me. SBF it is. Bummer....because I'm going to have to set everything (apps, widgets, etc) up -again- :/
Will post results.
samwathegreat said:
No safestrap...was never rooted until after 4.4.2 (thanks to china bl unlock).
That was the idea...just sbf, then flash twrp from bootloader, and install su from twrp. I guess I'll try that. I can't imagine why or how mine won't work....but if yours is working, then it must be me. SBF it is. Bummer....because I'm going to have to set everything (apps, widgets, etc) up -again- :/
Will post results.
Click to expand...
Click to collapse
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.
samwathegreat said:
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.
Click to expand...
Click to collapse
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.
Native Tethering
samwathegreat said:
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.
Click to expand...
Click to collapse
FYI, I got stock tethering to work by using the xposed X tether module and by changing the following build.prop variables in "/system/build.prop":
From -> to
"ro.moto.tether_dun_required=1" -> "ro.moto.tether_dun_required=0"
"ro.tether.denied=true" -> "ro.tether.denied=false"
Let me know if you have any questions.
evidenceunseen said:
FYI, I got stock tethering to work by using the xposed X tether module and by changing the following build.prop variables in "/system/build.prop":
From -> to
"ro.moto.tether_dun_required=1" -> "ro.moto.tether_dun_required=0"
"ro.tether.denied=true" -> "ro.tether.denied=false"
Let me know if you have any questions.
Click to expand...
Click to collapse
This method does not appear to work the Republic Wireless variant. Stock tether framework appears to be completely disabled (tether violates their TOS) on the RW model. When you try to activate it with xposed framework module and build.prop mod, the phone automatically "steals" back wifi access, disabling the native tether before it even starts.
I was able to get Wifi Tether for root users to work successfully.
samwathegreat said:
This method does not appear to work the Republic Wireless variant. Stock tether framework appears to be completely disabled (tether violates their TOS) on the RW model. When you try to activate it with xposed framework module and build.prop mod, the phone automatically "steals" back wifi access, disabling the native tether before it even starts.
I was able to get Wifi Tether for root users to work successfully.
Click to expand...
Click to collapse
The app breaks wifi for me once I turn tethering off.
legato89 said:
The app breaks wifi for me once I turn tethering off.
Click to expand...
Click to collapse
You probably didn't uninstall a different version of WiFi Tether for root users. The linked version is signed with different keys, so it is necessary to completely uninstall any current version before you install the linked one.
If you read all the posts in this thread, you would have seen that a similar issue was happening to me until I did a full return to stock. Then everything worked perfectly....and it still does today.
I'm on stock and rooted and I did try the apk linked, as well as others, uninstalling each before trying another.
I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Sent from my XT1049 using XDA Free mobile app
Cyphir said:
I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Sent from my XT1049 using XDA Free mobile app
Click to expand...
Click to collapse
Before I do this, why would reflashing to stock fix everything? Are there any alternative solutions? I am basically on a stock ROM straight from RW, and am curious why it doesn't work for me but works for you guys.
legato89 said:
Before I do this, why would reflashing to stock fix everything? Are there any alternative solutions? I am basically on a stock ROM straight from RW, and am curious why it doesn't work for me but works for you guys.
Click to expand...
Click to collapse
If you read this thread from the beginning, you would have seen that I had to flash the RW firmware before it worked for me. Afterwards, it worked perfectly and it still does today. As long as you flash the correct RW 4.4.2 firmware, it is the exact same stock firmware pre-installed on all RW devices. It is signed with Motorola release keys.
Basically, re-flashing the stock firmware can fix a damaged or corrupted file system. It didn't work for me at all until I did this. For some reason, it worked for Cyphir without flashing anything. My only guess is that something was out of place in my filesystem. I don't have any other explanations.
Save what is important to you and give it a shot if you are interested in being able to tether. I don't have any other advice or options for you otherwise. Follow all the instructions exactly.
samwathegreat said:
If you read this thread from the beginning, you would have seen that I had to flash the RW firmware before it worked for me. Afterwards, it worked perfectly and it still does today. As long as you flash the correct RW 4.4.2 firmware, it is the exact same stock firmware pre-installed on all RW devices. It is signed with Motorola release keys.
Basically, re-flashing the stock firmware can fix a damaged or corrupted file system. It didn't work for me at all until I did this. For some reason, it worked for Cyphir without flashing anything. My only guess is that something was out of place in my filesystem. I don't have any other explanations.
Save what is important to you and give it a shot if you are interested in being able to tether. I don't have any other advice or options for you otherwise. Follow all the instructions exactly.
Click to expand...
Click to collapse
It's really annoying how you assume I haven't read over and tried everything except for reflashing several times now, and just want more information before I h have to spend the time backing up and restoring. It's not unreasonable for someone to expect things to work the first time being on a clean stock build.
legato89 said:
It's really annoying how you assume I haven't read over and tried everything except for reflashing several times now, and just want more information before I h have to spend the time backing up and restoring. It's not unreasonable for someone to expect things to work the first time being on a clean stock build.
Click to expand...
Click to collapse
Annoying?
samwathegreat said:
Wow!! After SBF back to 4.4.2 stock, flash twrp, install root, I updated the preinstalled apps (including RW), installed ES file explorer (to rename man to apk), and installed as per guide. Now it works!!! Not only does it start first time, but just as you said, the wifi icon is restored as well.
I have absolutely no idea what the problem was. As I reinstall my apps, I'll check to make sure none of them interfere, but problem seems to be cured. Many thanks.
Final update: having re-installed all of my apps, everything is still behaving as it should. Whatever the problem is, RSD to stock fixed it. Issue solved.
Click to expand...
Click to collapse
Cyphir said:
I works for both me and @samwathegreat. Could you try flashing back to stock and trying again?
Click to expand...
Click to collapse
It looks quite clear to me. It *worked* out of the box for Cyphir. It didn't for me.
I stated very clearly that *I have absolutely no idea what the problem was*
My expectation was that it would work out of the box for me as well. It didn't. Why? Heck if I know!?
Moral of the story: "Whatever the problem is, RSD to stock fixed it".
That seems cut-and-dry to me. And all of that was outlined here already.
I'm done. Especially after the "annoying" comment you made. Someone else can help you. I've been more than clear that there is nothing else that will get this to work for you.
What is annoying is your unwillingness to do what both Cyphir AND myself suggested. If you are using Titanium Backup, you can backup AND restore in the matter of a few minutes. *FAR* less time than you have no doubt spent "reading over and trying everything except for reflashing".
My last suggestion is **DO NOT** backup the WiFi Tether APK. Install it from scratch from Cyphir's link. Do this before you restore ANYTHING. I bet it works immediately. And you had better save your backups to your PC, otherwise it will all get erased when you flash the SBF (flashing erases internal memory as well). Aside from that, Good Luck.
I agree that " It's not unreasonable for someone to expect things to work the first time being on a clean stock build". That's the same situation *I* was in. I just wasn't too "unreasonable" to try the only possible way of getting it to work -- flashing the stock firmware.
You and I wouldn't be the first people to have something not function correctly on unmodified, stock firmware. I can't tell you how many different individuals, with countless different issues, 100% *FIXED* their issues by simply re-flashing the stock firmware....
What I can tell you is that their issues would have never been fixed if they were too stubborn to do it.
You only need your sim tool and the phone.
1) open the sim tray but don't take out the sim card.
2) push the sim tray back in the phone.
3) wait 4-5 seconds and then activate hotspot in the settings->more->tethering
If these directions don't help you can see my video on youtube.
Don't ask how I found this but it works for Verizon and AT&T. I have not tested this on any other carriers.
This works by turning on the hotspot while the phone is provisioning. If you attempt to do this too soon or too late you will trigger the subscription check.
You will need to perform this everytime you want tethering if you turn tethering off or reboot the phone.
I can confirm this works on 5X connected to Sprint. SIM tool has now been added to my keychain.
Can you not just add the provisioning line to the build.prop to negate the need to do this?
It's worked since as long as I can remember.
Need root for build.prop mod
paperWastage said:
Need root for build.prop mod
Click to expand...
Click to collapse
You should be able to use ADB through TWRP recovery once you unlock the bootloader and flash recovery. Pull the build.prop, edit it, then push it back.
Edit: don't mind me, didn't realize this was if you don't want to unlock anything
br125 said:
You should be able to use ADB through TWRP recovery once you unlock the bootloader and flash recovery. Pull the build.prop, edit it, then push it back.
Edit: don't mind me, didn't realize this was if you don't want to unlock anything
Click to expand...
Click to collapse
is it the same settings for all the previous androids? is there a tutorial on this? thanks!
Does FoxFi work on the 5X?
myphone12345 said:
Does FoxFi work on the 5X?
Click to expand...
Click to collapse
no it does not.
To everyone else saying build.prop editing. It says in the title WITHOUT unlocking and rooting.
For T-Mobile, I'm able to do it while completely stock (non-rooted) but unlocked, simply by issuing the following command:
Code:
adb shell settings put global tether_dun_required 0
And also using a user agent spoof extension in Chrome to report that I'm running as googlebot.
Works like a charm.
Sent from my Nexus 5X using Tapatalk
P3Droid said:
If these directions don't help you can see my video on youtube.
Click to expand...
Click to collapse
What video? I cant find it.
No luck here..
pdelponte said:
What video? I cant find it.
Click to expand...
Click to collapse
Tried this using Straightalk (AT&T)...
no go....
chipk said:
Tried this using Straightalk (AT&T)...
no go....
Click to expand...
Click to collapse
I read somewhere that the latest update patched this. Not official, but stumbled across someone else saying it no longer worked on 6.0.1. Might have been from another post here on xda somewhere.
Hi guys, I have a question,
I have been able to use my data connection without any problem on my firefox OS device. Since I use my nexus 5X, the is not possible (a message it telling me to active this feature on att.com event though i am using H2o Carrier (which uses att network) )
So here is my question, how come the nexus 5x which is suppose to be unlock cannot do internet tethering ? Why did it work with FirefoxOS but not Android ? How do they block that ?
Cheers
O_S
Yeah 6.0.1 blocked it you can do it still but when you connect the device to it you can't get internet connection.. Sucks..
Hopefully there will be a work around, or Foxfi will get updated to work
Thank you OP for the tray trick !!! - works great (wait about 3 sec) on Moto X (2013) running 5.1 on Cricket (was AT&T b4)
Might need to root and make it permanent as it's not convenient to take case off and carry a pin around each time, but better than nothing...
Update: got a Nexus 5x with 6.0.1 and the trick works as well, though more often than not hotspot is on BUT no data/LTE symbol. But I got it to work at times. more finicky.
d.kozzer said:
For T-Mobile, I'm able to do it while completely stock (non-rooted) but unlocked, simply by issuing the following command:
Code:
adb shell settings put global tether_dun_required 0
And also using a user agent spoof extension in Chrome to report that I'm running as googlebot.
Click to expand...
Click to collapse
how can you write to necessary file without root access ? (from command shell I supposed)
When you mention chrome extension, how does that come into play (browsing on your computer, but how does it get wifi tethering access anyway ?)
Please explain (got Moto X 2013 running 5.1 non rooted originally AT&T but unlocked on Cricket now).
Hey everyone! So, I'm new to the whole Nexus and rooting thing but have used Android for a while (mostly HTC and Samsung stock devices). I came to Nexus because I thought I'd give it a shot and I'm super pleased with how it works, how fast it is, etc compared to non-Nexus devices. I went and downloaded the Android SDK tools, copy and pasted all the instructions, and got all ready to make this build.prop edit until I realised that the cable is a USB-C and it doesn't plug into my computer. The entire week I had this device I just assumed the charger was USB-A on the brick side and USB-C on the phone side, but alas, it's not. So, silly question, what cables are you all using to do this stuff? Is there an adapter on Amazon you recommend over another because I see a lot!
Thanks in advance!
Cheers!
Interesting the 5X is different from the OG Nexus 5 in this feature. I'm on the $30/mo t-mobile plan, and I just swipe down from the quick settings menu to turn on the hot spot. My Nexus 5 is not rooted.
I have a Ring Plus line that does not have free tethering but I was able to get free WiFi tethering on this Ring Plus line using my Sprint Moto E 2015 XT1526 running 5.1 by doing the following:
1) unlock the bootloader;
2) flash custom recovery twrp-surnia-3.4.5-r1:
http://forum.xda-developers.com/devdb/project/?id=10398#downloads
3) root the device;
4) change the value of "ro.mot.tether_dun_required" to "0" in the build.prop file;
5) add the line "net.tethering.noprovisioning=true" to the end of the build.prop file;
6) in fastboot mode run the following command
Code:
fastboot oem config fsg-id ringplus
7) install MVNO Slayer through TWRP:
http://forum.xda-developers.com/mot...t/flashable-lte-fix-moto-e-6-x-boost-t3290719
Some of the above steps may be unnecessary, idk, but this is what worked for me.
I'm going to try with stock bootloader, loading TWRP through fastboot but leaving stock bootloader, making the build.prop changes and loading the MVNO Slayer. Basically without TWRP and without the fastboot oem config fsg-id ringplus changes. Let's see if it works.
---------- Post added at 02:02 PM ---------- Previous post was at 01:47 PM ----------
mine worked without the config fsg-id ringplus and without the TWRP flash. I just boot into fastboot then type fastboot boot TWRPxxxx.img so it will boot TWRP without loading it permanently.
wpcprez said:
I'm going to try with stock bootloader, loading TWRP through fastboot but leaving stock bootloader, making the build.prop changes and loading the MVNO Slayer. Basically without TWRP and without the fastboot oem config fsg-id ringplus changes. Let's see if it works.
Mine worked without the config fsg-id ringplus and without the TWRP flash. I just boot into fastboot then type fastboot boot TWRPxxxx.img so it will boot TWRP without loading it permanently.
Click to expand...
Click to collapse
So your bootloader is unlocked but you aren't rooted? Or are you rooted?
JulesJam said:
So your bootloader is unlocked but you aren't rooted? Or are you rooted?
Click to expand...
Click to collapse
I think he is trying to avoid root.
Anyway. Kudos to OP. Worked like a charm. Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
LTE on this Moto E is faster than my daily driver Note 4. wondering if that has anything to do with sim cards......
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
linhnd2000 said:
I think he is trying to avoid root.
Click to expand...
Click to collapse
But why if you have unlocked the bootloader? Is it due to using the phone for work or something like that?
linhnd2000 said:
Anyway. Kudos to OP. Worked like a charm.
Click to expand...
Click to collapse
Glad it worked for you too!
linhnd2000 said:
Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
Click to expand...
Click to collapse
I use ES File Manager, but you have to enable the root features on that and I think show hidden files has to be enabled too.
linhnd2000 said:
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
Click to expand...
Click to collapse
Idk, I just know without it I wasn't able to tether for free on ring plus. I am still on 5.1 so it must have done something to allow me to tether for free.
linhnd2000 said:
I think he is trying to avoid root.
Anyway. Kudos to OP. Worked like a charm. Took me a bit of time trying to figure out how to edit build.prop (needed root and build.prop editor from google play). RUSTY OLD ME!
LTE on this Moto E is faster than my daily driver Note 4. wondering if that has anything to do with sim cards......
Is the slayer only for CM Marshmellow? 'cuz it doesn't seem to do anything on my stock 5.1
Click to expand...
Click to collapse
I'm rooted. I just didn't want to change bootloader to twrp. Heard of people having issues trying to upgrade to newer stock roms when the bootloader is swapped unless you use a custom rom.
All my other devices which are samsung are all rooted,bootloader unlocked and are on TWRP or Philz Touch. All work fine but I just saw others complaining about TWRP And loading stock roms so I thought I would just be safe and just run TWRP from fastboot so I have the features of TWRP without loading it permanently.
Will this work with the Boost Mobile version of this Moto E?
Thanks.
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Ended up using the ROM XT1526_Surnia_5_1_1_Lollipop_v1.zip<-For Sprint, Sprint MVNO, and Sprint subsidiaries on XT1526 or XT1529. from this thread
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
unmesh59 said:
Will this work with the Boost Mobile version of this Moto E?
Thanks.
Click to expand...
Click to collapse
Almost sure OP has the boost mobile version as well
SDRebel said:
Almost sure OP has the boost mobile version as well
Click to expand...
Click to collapse
Good to know. I have a new phone waiting in the mailbox for me when I get home
unmesh59 said:
Will this work with the Boost Mobile version of this Moto E?
Thanks.
Click to expand...
Click to collapse
Yes it will, I have done it on both Sprint and Boost.
SDRebel said:
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Click to expand...
Click to collapse
Did you check the build.prop file to make sure that your edits were saved and that there weren't any typos in your edits?
JulesJam said:
Did you check the build.prop file to make sure that your edits were saved and that there weren't any typos in your edits?
Click to expand...
Click to collapse
yup, i double-checked it and didn't see any problem. I wonder if the difference could be in the rom, given I had to use the one I linked which may be different than the stock one
Thank you for these instruction. It took me a while to figure out how to each steps, but it works out at the end. I can now have free tethering with my ringplus account. However, my phone camera is no longer accessible. I tried different camera apps, still no go. Is anyone experiencing this? Thanks again
Nurakuni said:
Thank you for these instruction. It took me a while to figure out how to each steps, but it works out at the end. I can now have free tethering with my ringplus account. However, my phone camera is no longer accessible. I tried different camera apps, still no go. Is anyone experiencing this? Thanks again
Click to expand...
Click to collapse
Change SELinux to Permissive. http://forum.xda-developers.com/showthread.php?t=2524485
SDRebel said:
I was able to go through all the steps, with a few hiccups, including accidentally wiping it clean, and I'm able to turn on the hotspot, but a device connected to it can't connect to the internet.
Ended up using the ROM XT1526_Surnia_5_1_1_Lollipop_v1.zip<-For Sprint, Sprint MVNO, and Sprint subsidiaries on XT1526 or XT1529. from this thread
---------- Post added at 05:31 PM ---------- Previous post was at 05:30 PM ----------
Almost sure OP has the boost mobile version as well
Click to expand...
Click to collapse
This process works for BoostMobile Moto E as well. Mine was running Android 5.1 build Number LPI23.29-18-S.2.
However, I decided to experiment to see if I could disable root in SuperSu and the tethering still works. As soon as I disabled root, it stopped working. My PC still connects to the phone, but no Internet access. Damn!
I restored to stock firmware, and had gone through the exact same process again. But it didn't help. My PC can still connect to the phone, bu there is no Internet access. I tried a number of things, same result.
Anyone had the same experience and found a solution?
PhoneHero said:
This process works for BoostMobile Moto E as well. Mine was running Android 5.1 build Number LPI23.29-18-S.2.
However, I decided to experiment to see if I could disable root in SuperSu and the tethering still works. As soon as I disabled root, it stopped working. My PC still connects to the phone, but no Internet access. Damn!
I restored to stock firmware, and had gone through the exact same process again. But it didn't help. My PC can still connect to the phone, bu there is no Internet access. I tried a number of things, same result.
Anyone had the same experience and found a solution?
Click to expand...
Click to collapse
Did you wipe the cache/data partitions? Are you rooted now? What firmware version are you on?
Anyone use on Nexus 5x? (originally from Project Fi)
JeffATL said:
Anyone use on Nexus 5x? (originally from Project Fi)
Click to expand...
Click to collapse
You could try the first 5 steps and see how that works - of course use the proper TWRP for the N5X:
1) unlock the bootloader;
2) flash custom recovery TWRP for your Nexus 5X
3) root the device;
4) change the value of "ro.mot.tether_dun_required" to "0" in the build.prop file;
5) add the line "net.tethering.noprovisioning=true" to the end of the build.prop file
So is this undetectable to boost Mobile? They don't limit you to 8gb like the claim for the hotspot on the $60 unlimited plan ? I have it enabled on my recently purchased moto e and I get extremely fast lte at my rural house. This is awesome and works excellent. Better than the Wi-Fi tether router app I've been stuck using. More reliable with the built-in tether and phone doesn't get nearly as hot.
JulesJam said:
Yes it will, I have done it on both Sprint and Boost.
Click to expand...
Click to collapse
Is this metered tethering or can they not detect this? I'm using Boost unlimited plan $60 and just did this modification and tethering is working great so far, but I just want to know if it's going to stay free like this?
Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?
Good luck lol
yeah i saw that site this morning.. anyone have luck?
Jaws4God said:
yeah i saw that site this morning.. anyone have luck?
Click to expand...
Click to collapse
OCR is non attainable on this device.
Too much stuff to do manually.
elijah420 said:
OCR is non attainable on this device.
Too much stuff to do manually.
Click to expand...
Click to collapse
has anyone tried and it fail?
Jaws4God said:
has anyone tried and it fail?
Click to expand...
Click to collapse
OCR is not attainable on this device.
Too much to do manually.
I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app
evo4g63t said:
I always recommend manual methods over one click methods you never know what kind of crap these programs will put on your phone.
Its not the first situation where spyware has ended up on phones from these sites. King Root is a good example.
Sent from my LG-H918 using XDA-Developers Legacy app
Click to expand...
Click to collapse
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!
Jaws4God said:
oh thank you for the heads up.. I was just hoping to find a way to just get simple root on my phone to have access to Gravity Box ... but i do not want to unlock my bootloader and have a custom recovery..
Thanks!
Click to expand...
Click to collapse
It's a scam. My dad (without consulting me) tried it on a moto g4. Not only did it not work, he ended up with spyware and spam that I had to get rid of.
There is no simple root. Any phone going forward that is rootable will have to be connected to a pc and adb or odin used to exploit a vulnerability manually.
One click Root Worked For Me (H91810J) T-MO
sjr19 said:
Curious as to whether anyone has tried this. Suspicious as I haven't seen it here lol. Thoughts?
Click to expand...
Click to collapse
OneClickRoot worked on my T-Mobile H91810J. I've rooted a lot of phones and tried the recowvery and numerous other methods. I couldn't get TWRP to flash because I was missing a few commands not listed. They connect through the program (Oneclickroot) and use a program called Vysor. It has to be manually done by one of their techs. I was able to see and copy their commands and files but again I have a T-mobile not Sprint. To be sure, open a chat session and they will 100 percent verify if they can do it. They ask for everything from the model number, to the build number, security patch info...etc . It has to be done manually by the tech not by the program which will tell you after trying to root that you need to have it done manually by them.
They are legit but not cheap. The up side is they can do it right from your pc or most any pc . It's a 24/7 operation also. Pay the extra for the protection. It isn't cheap but it sure is easy and now I am 99 percent sure I can follow their steps if needed. I see where I messed up in the shell commands. I hate my bootloader locked When I boot though. I still have to access it through ADB unless I am missing something. I also still have the annoying orange oem warning screen. Otherwise full root access. I just don't know what I am going to do if something happens and it has to be reset...etc. I love lux and color changer pro. Completely transforms the device in my opinion. Hopefully we have a solution by then to bypass the entire thing. If I could get a hold of chainfire I'd send the code and files right to him or anyone capable of making this easier on everyone.
I plan on posting the code in the near future I just haven't had time. More to follow. OneClickRoot is legit but not cheap. You also have to have some trust to allow a remote connection. If they say they can do it they can. I tried doing the recowvery step by step and it kept locking up on me do to FRP. I messed up some additional shell commands which I didn't know I needed to actually flash twrp.
I am almost positive they can do the sprint version. Just check with them first via chat which is free.
Unless they have found another exploitable security hole, or your phone has NOT taken the zv6 update, your phone is NOT rootable.
The exploit that allowed dirty cow/Santa/elf, copy on write, has been plugged.
Legitimacy of their operation aside, the exploit was plugged with the zv6 update.
so i am happy to see they got root for the V20 VS995. but i got my V20 today, well i am looking around for root and found a BL method
so i want to know will this method work with VS99513A or is there a better method for this phone, i be so happy to root this phone hehehe
thank you all
LASERWOLF452 said:
so i am happy to see they got root for the V20 VS995. but i got my V20 today, well i am looking around for root and found a BL method
so i want to know will this method work with VS99513A or is there a better method for this phone, i be so happy to root this phone hehehe
thank you all
Click to expand...
Click to collapse
The only way to root the VS995 is to unlock the BL/root using the DirtySanta method. It works with 13A. It will not work if you update to anything past that.
Be sure to read the thread in detail and hope you are proficient with Android, ADB, and fastboot as the process is not for beginners.
It can be a bit nerve racking at times (especially when your phone starts vibrating like crazy....which is normal for the process) but the method does work. Sometimes things don't go 100% according to the description so that's where you need to know what you are doing.
Artimis said:
The only way to root the VS995 is to unlock the BL/root using the DirtySanta method. It works with 13A. It will not work if you update to anything past that.
Be sure to read the thread in detail and hope you are proficient with Android, ADB, and fastboot as the process is not for beginners.
It can be a bit nerve racking at times (especially when your phone starts vibrating like crazy....which is normal for the process) but the method does work. Sometimes things don't go 100% according to the description so that's where you need to know what you are doing.
Click to expand...
Click to collapse
well this will be the 3rd device i have to use ADB on as i rooted a htc evo and a acer iconia tablet 700
but before i touch this method i always look around for answers and ask questions before doing it
while i still get info about this root, is there a way to disable the system update without root, i tried the debloater and it dose not pick up anything. it sees the phone tho so idk y it wont pick up any packages, i dont wont to accidently install 14b
LASERWOLF452 said:
well this will be the 3rd device i have to use ADB on as i rooted a htc evo and a acer iconia tablet 700
but before i touch this method i always look around for answers and ask questions before doing it
while i still get info about this root, is there a way to disable the system update without root, i tried the debloater and it dose not pick up anything. it sees the phone tho so idk y it wont pick up any packages, i dont wont to accidently install 14b
Click to expand...
Click to collapse
You could try "pm disable <package name>". Don't know if it works on an unrooted device though.
There are two system update apks...one can be disabled through the app manager. The other cannot so you will need to use the command above. I believe the package name is: com.lge.lgdmsclient
There is also an option in the developer settings to prevent autoinstall of an update