Database Users

[SOLVED] Republic Wireless (Unlocked) Wireless tether Issues / Problems

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.

How to enable HotSpot without a subscription and without unlocking or rooting.

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.

API3 - can it be rooted?

Hey fellas,
I have been looking around on some threads here and there and decided to change my phone to G935U to get off the Verizon one. I took an update that I probably shouldnt have and it brought me to the API3, can this be rooted? I tried following the known root method (and pretty much the only one I can find) and it doesn't seem to work.
I havent seen anybody else say API3 is unrootable so I figure I would ask.

No root for it yet. Not sure if there ever will be. The current root method for earlier versions is somewhat unreliable and tends to slow your system down and drain the battery so I'm not even sure what the demand would be.

Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.

ShadowyStorm said:
Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.
Click to expand...
Click to collapse
Do you have a link on how to do all this?

Replied to your pm. Regular root method works just fine though. So Lmk what issues you're having.

ShadowyStorm said:
Rooted pi3 checking in. Stock rooted, debloated, running smooth. Kernel auditor is basically a must. I run amplify, greenify, force dose, lean Droid and L speed. The fixes and vvm zip change the csc and what not to g935V and make it say I'm on peh. Runs better than any custom room I've ran, but debloating it to my liking did take some time. In short yes you can root it. You can even manually flash updated supersu binaries through flash fire but you will have to replace the engboot immediately after or your device won't boot.
Click to expand...
Click to collapse
Checking in also-- very similar to yours.
Bought the phone with PI3 already installed. Flashed the U firmware, debloated (only a few really) and rooted. I also use Kernel Auditor set to ondemand (<--must) and L speed. Flashed the two Verizon fixes with flashfire and working great. The phone was laggy and would randomly freeze for 10 seconds or so before I downloaded Kernel Auditor, but that along with .5s animations really makes things snappy.
Knox status - 0x0 - not tripped
Samsung Pay doesn't work, but I just tested Android Pay and it does work!
Snapchat works if installed and run once before rooting. Rooted now and still working.
Xposed installed through Flashfire.
The only thing I haven't had a chance to test yet is VR, but I see no reason why it wouldn't.

I am on PI3 rooted running smoothly. Also did my friends phone the same way. If you are having issues rooting there is a workaround that i discovered which worked for me and my friend because both of use after flashing to PI3 wouldnt root successfully. The workaround is using the Verizon Repair Assitant and "repairing the phone" this will put a new 935u IMAGE from verizon onto your phone and it will reboot. I dont know what the difference is between this image they put on your phone and the one we did but there is a difference. I say this becuase after you do that if you run through the root process again by flashing then installing su over ADB it works flawlessly. PM if you need further help.

I still cant get it to root... Tried it several times, zero luck

What Odin are you using?

ShadowyStorm said:
What Odin are you using?
Click to expand...
Click to collapse
The PrinceComsy one. I have debugging and unknown sources enaqbled. I run the root.bat and nothing happens, it sits at
"adb push SuperSU-v2.76.img /data/su.img"

like it just hangs indefinitely? try a different cord. it doesnt say its retarting the server a million times?
Did you flash the Eng Hboot kernel in the AP slot first? more info needed

ShadowyStorm said:
like it just hangs indefinitely? try a different cord. it doesnt say its retarting the server a million times?
Did you flash the Eng Hboot kernel in the AP slot first? more info needed
Click to expand...
Click to collapse
Pretty much indefinitely. I let it sit an hour and nothing. I transferred about 200gb of audio to the phone with zero issues so I think the cable is fine (but I tried a new one anyway, nothing). It never says restating the server.
Yes I flashed the engineer kernel in the ap slot first.
What other information can I provide?

Did you install the adb drivers in the root thread?

ShadowyStorm said:
Did you install the adb drivers in the root thread?
Click to expand...
Click to collapse
Yes

Hell-Razor said:
Yes
Click to expand...
Click to collapse
Well ****. Try turning off USB debugging and turn it back on again maybe for reason your phone blocked the connection and this would renew that list

ShadowyStorm said:
Well ****. Try turning off USB debugging and turn it back on again maybe for reason your phone blocked the connection and this would renew that list
Click to expand...
Click to collapse
Give me about two minutes and Ill get right back toyou

Aaaand nothing

My phone reboots, supersu is on it but root is not there.

Hell-Razor said:
My phone reboots, supersu is on it but root is not there.
Click to expand...
Click to collapse
Try another USB port on your computer maybe...
If that doesn't work then try opening up a command prompt as administrator on your computer (I know you've tried running root.bat as admin but windows has its quirks) and navigating through the directories until you're in the folder with the root.bat file and type in root.bat once you're there to see if that changes anything. If you need help with commands in the command prompt then ask. I'll gladly help.

That's interesting. It sounds like it's not able to mount the system as writable.
---------- Post added at 08:31 PM ---------- Previous post was at 08:15 PM ----------
http://forum.xda-developers.com/ver...de-flashing-sm-935u-firmware-verizon-t3415145 root files from this thread right? Try re downloading all of it and then flash the rooted tar as ap and then get back to me on the results
---------- Post added at 09:24 PM ---------- Previous post was at 08:31 PM ----------
So I was able to replicate this scenario... I had to restart my computer because the adb server kept going out of date due to Odin being open as well as trying to root the phone. Restarting restored proper communication. Try using smart switch to install your phone drivers

New T-Mobile Firmware Out. --> G930TUVU4PK1

This update brings us up to November security patch.

I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time

So far it does seem like it was the stated update to enable 256QAM and 64QAM. But for me only the upload speeds have increased, up to Just over 50Mbps. The speeds in general have been varying from 30Mbps-150Mbps dependent on site, but Just days ago I would be roughly 80Mbps almost everywhere I went, up to about 130Mbps

thowersome said:
I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time
Click to expand...
Click to collapse
Vulkans been enabled since the September patch update APIA

I assumed it was but it doesn't seem to be picked up by the apps. For example dolphin emu doesn't pick it up

G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ ship_MULTI_CERT.rar
Here are the Odin files:
G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ship_MULTI_CERT.rar

After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work

Okay now the burning question
... does root work??

KillerClaw321 said:
Okay now the burning question
... does root work??
Click to expand...
Click to collapse
That's what I want to know as I updated and now can't get root access...

CWBPHT said:
That's what I want to know as I updated and now can't get root access...
Click to expand...
Click to collapse
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
esjames said:
This update brings us up to November security patch.
Click to expand...
Click to collapse
Can you root? Or did you try?

KillerClaw321 said:
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
Can you root? Or did you try?
Click to expand...
Click to collapse
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Edit - Also, when I type adb devices there are no devices attached, yet I have access to my sd card and phone folders through windows...

CWBPHT said:
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Click to expand...
Click to collapse
Then run the cmd as admin

KillerClaw321 said:
Then run the cmd as admin
Click to expand...
Click to collapse
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?

CWBPHT said:
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?
Click to expand...
Click to collapse
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...

KillerClaw321 said:
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...
Click to expand...
Click to collapse
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.

CWBPHT said:
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
Click to expand...
Click to collapse
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.

m52 power! said:
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work
Click to expand...
Click to collapse
If anyone else can confirm that? You could then send a message to the PDANet app team and maybe they'll work in a workaround of some sort.

KillerClaw321 said:
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.
Click to expand...
Click to collapse
Got it up and running and even debloated it, got xposed on there, and I'm working on the tuning guide here - http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
The only minor annoyance I have as of right now is the phone keeps giving me a "health update" telling me that I have to update Samsung +, but thankfully it stopped giving me the stupid security warnings.
Thanks for the help!

Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.

joachim123 said:
Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.
Click to expand...
Click to collapse
I've not had any lag problems, but I did optimize a bunch of apps from running in the background, which always helps with battery life.

LG v20 hotspot

Hello everyone i need some help i have the LG v20 from AT&T LG-H910 unlock. its a great phone, the problem is that i switch to T-mobile and it wont let me use hotspot it show.
authentication was unsuccessful.
There is a temporary network problem that prevents the enablement of the mobile hotspot function. please retry later
Anyway around this, any help is greatly appreciated thanks.

Have you tried changing the build.prop to OPEN and rebooting
Sent from my LG-H910 using Tapatalk

No but i will try it and let you know if it works thanks

Did this work? I'm having the exact same issue. Do I have to be rooted to change the build.prop?

Yes root is needed. And not many of us have root on our V20's

So there is no other way of making the hotspot work with the H910 on T-Mobile?

dustinbleh said:
So there is no other way of making the hotspot work with the H910 on T-Mobile?
Click to expand...
Click to collapse
I've had a ZTE phone from ATT that wouldn't hotspot on TMobile unless I installed and used the ES File Explorer app which has Network hotspot toggling built in the app. Couldn't hurt for you to try that route I suppose. Forces usage of the app for hotspot toggling instead of going through Android settings to turn hotspot on.

Download the app and tried to use the in-app hot spot but still get this message

daw41 said:
Have you tried changing the build.prop to OPEN and rebooting
Sent from my LG-H910 using Tapatalk
Click to expand...
Click to collapse
I'm having this same issue. Any more info for a noob on what build.prop is and exactly how you'd go about setting it to open? Also what method of rooting would you prescribe with doing this and getting the hotspot working as the end goal? Help is much appreciated!

Have you tried contacting T-Mobile or AT&T

Trousers2 said:
I'm having this same issue. Any more info for a noob on what build.prop is and exactly how you'd go about setting it to open? Also what method of rooting would you prescribe with doing this and getting the hotspot working as the end goal? Help is much appreciated!
Click to expand...
Click to collapse
You have to be rooted in order to use this fix and rooting this phone is not easy. My recommendation is that you do a lot of research on rooting and become familiar with ADB shell before you root. Once you're familiar with those things @runningnak3d has a root method for the H910 in a thread on here but this phone does require you have a working knowledge of android and adb to use it rooted and not screw it up. So I hate to repeat people on here but read read read its very important.

daw41 said:
You have to be rooted in order to use this fix and rooting this phone is not easy. My recommendation is that you do a lot of research on rooting and become familiar with ADB shell before you root. Once you're familiar with those things @runningnak3d has a root method for the H910 in a thread on here but this phone does require you have a working knowledge of android and adb to use it rooted and not screw it up. So I hate to repeat people on here but read read read its very important.
Click to expand...
Click to collapse
Thanks for the advice. I'm definitely not rushing into anything, I'm doing plenty of reading first. I just can't find answers on doing exactly what I want to do. At this stage I'm leaving towards flashing the firmware from a us996 to mine. I just can't find any guides on how to go about that.

Hotspot issue
Hello guys .....i had a same issue ....i got lg v20 at&t and couldn't able to creat hotspot ..... So i find a slution ....
1. Download " setting data base editor" from play store
2. Select system
3. Find " tether_entitlement_check_state "
4. Chage the value "0"
No root need
Thats it

Hotspot issue

@sameerlx - Thank you for posting re Settings Database Editor. I now am able to use wifi hotspot on my V20 no root required.
:good::highfive:

Thanks a lot @sameerlx.
A nice and easy solution to the hotspot issue.
Working flawlessly now.

I opened the build.prop file in the system directory and found an entry: wifi.lge.common_hotspot=true
and wifi hotspot still doesn't work

That worked for me too! Changed value from 5 to 0.