[Q] Native hotspot not working after root - T-Mobile HTC One (M8)

I just recently rooted my HTC one m8 from T-mobile, it is on Lollipop.
After rooting I downloaded the app "WiFi Tether Router" I know it works, because I've used it in the past with an older phone. But this time it didn't work after implementing the settings suggested by the developer on the device configuration site, I got curious and decided to check the native hotspot app, all it does is show a message saying "PROCESSING..." but never turns on, if I leave it working eventually the screen will turn off and the process will stop.
On the website, it is recommended to remove an app named "TetherGuard" I tried to do it, but only found a file named "Tethering Guard" I tried to remove it using "ES File Explorer File Manager" but couldn't do it, at the end I ended up using "Titanium Backup" to freeze it.
I'm new into rooting, all I did with my older phone was to root it in order to install "WiFi Tether Router" ... Can anyone please help with this?

I am having same problem with Verizon M8 rooted and running SkyDragon on T-Mobile. :crying: Everything else is working fine.

Related

No WiFi Tether after UnrEVOked?

I just rooted my Evo, using the unrevoked method, and my main reason for doing so was to be able to use the Google WiFi tether app.
The root appears to be successful by all counts, but after installing the WiFi tether app, I cannot use it. I get an error saying "Unable to start tethering" and this is even after using the very latest v2.0.2 build from 6/12.
Anyone else run into that? How can I fix it?
Thanks in advance,
-R
Run unrovoked again, make sure its rooted for sure and that the superuser is in the app list. I ran into the problem before, and for some reason the superuser wasnt working correctly.
I use this with unrevoked. Tethers two simultaneously.
Has wpa security.. It's also fun. lol

Has anyone lost root access (temporarily) after installing latest 2.2 roms?

I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday. All apps are working fine after the re-flash.
Anyone else have this?
unknown_owner said:
I installed a rom that was based off the released 2.2 that was released on Friday. I had root already and everything worked fine no problem. I flashed the latest radios and wimax and really nothing else. Well today I went to use Titanium Backup and it wouldn't run; just got a black screen. got the FC message. I then tried to use QuickBoot to reboot and that also didn't do anything. I manually powered off and rebooted and still the same actions from both apps. I then tried Wifi tether and that wouldn't start the sharing. Said that it was unable to Start. I think at that point my root access wasn't working properly. I looked at the Superuser permission app and it looked ok. I then tried another app that required root called Ad-Block and it said that it couldn't get root access.
The only way to get the apps working again was to flash the same rom I flashed on Friday.
Anyone else have this?
Click to expand...
Click to collapse
That is possible. I had the same issues. To get the ad-free host files in, I had to do it in recovery mode and push the files which is like having the nand lock. I try to do some programs that require root and it reboots the phone.

[Q] WiFi tether stopped working.

Hey all.
If this has been posted already, I am sorry for a repeat post. I haven't seen a fix.
I recently did the OTA update on my Galaxy S3 to Android 4.1.2 and I think that is pretty much the only thing that I have changed.
I had to go back to my stock recovery in order to get the update, but I never changed my recovery back to CWM.
The phone says that I am still rooted, I have the superuser icon in my apps so I assume that I am rooted.
Whenever I click on the app it says that I am granted superuser permission.
I am using the WiFi tether TrevE Mod and it worked in the past with my ipad.
It starts to tether, stating that I have superuser permission, but then it says:
"Tethering started with Errors!
Please check 'showlog'.
I check for the WiFi option on my ipad and my ipad is not there.
I unistalled and reinstalled the program and it has the same issues.
I go to the "show log" and it says "unable to open the log-file. File does not exist"
I am out of ideas what to try next and I ask the forum for advice.
Thanks to all!
Mike in St. Louis
This is a kernel issue. Some stock kernels don't allow wifi tethering, even if you are rooted. Flash a different kernel and profit.
http://forum.xda-developers.com/showthread.php?t=1643826
That'll help you if you don't know how
The problem was that I lost root. Thanks!

[Q] How to get "Wifi Teather" to work with ICS ?

Can anyone tell me how to get Wifi Teather to work with an ICS kernel ? I don't want a non-root solution that requires some additional software on the clients, and if possible, i'd avoid having to install some non-ICS ROM.
I've wasted a whole day but always run into the same issue:
rooted GB works fine: Download "Wifi Teather" from market, configure for Device Profile "Samsung Galaxy S2", perfect!
Using rooted ICS (I927UCLJ3_I927UCALJ3_I927UCALJ3_HOME.tar.md5), same configuration of "Wifi Teather" results in a
red "failed" in "Enabling NAT rules". Everything else stays green. And of course this means that clients can tether with the glide, but they do not get routed correctly (eg: can ping only the glide but nothing further from the tethered client).
This was the rooted stock ICS installed from Odin after clear data/cache/dalvik, format root. I also tried to apply the tethering fix for the leaked ICS kernel (i927_9SEP12_tetheringFix.zip) (of course after another clear data/cache/dalvik/format-root). And i tried to overwrite the kernel with LiteKernel-4.0-20130121.zip, and i tried to remove with Titanium Backup the Tethering Manager apk.
All this stuff did not change the output of "Wifi Teather" at all.
Then i install IcePop ROM, and "Wifi Tether" works fine there, no problems with "Enabling NAT rules". Alas, i can not use IcePop because it has removed Exchange Email, and thats one of those pieces you can not re-install from market or backup AFAIK.
So, what the heck is needed to make "Wifi Tether" work with stock ICS rooted ? Does it work at all ? I've been reading forum posts up and down the wazoo, but any claims to it working have been very unspecific.
*sigh*
Interesting
Been playing around a bit more:
The stock ICS built-in Wifi Hotspot option (under settings) does actually work fine once i applied i927_9SEP12_tetheringFix.zip. Before installing that fix a popup window from the provider comes up telling me i should pay $611/min - or some other text with the number 611, can't quite remember .
But the "Wifi Tether" app does not work with stock ICS neither before nor after installing of that framework fix. I wonder whether this indicates an error in the "Wifi Tether" app. Then again, it works in IcePop.
Wrt. to the way the provider sees or does not see tethering - does it make a difference whether one uses the built-in tethering option or the external app "Wifi Tether"
Learning by doing
So, now i flashed dmans stock ICS rom UCL33-ATT-NEW.zip from here, and lo and behold, the "Wifi Tether" app works, and the build-in tether option does of course not work (not applied the framework fix).
So... The only difference over the real stock update from ATT (rooted with su binary) seems to be that dmans stock is deodexed, zipaligned and batch optimized. "Wifi Tether" is stating that it's installing some stuff binaries et. al. Is it possible that it fails to do so on a system thats not deodexed/xipaligned or batch optimized ? I don't quite understand this.

[Q] "could not obtain root" message on startup

Have a stock S3, Sprint-branded, running 4.4.2. As of yesterday, I can't get mobile data (apps say no internet connection). It works fine on WiFi.
I noticed on startup, towards the end of the process, a "could not obtain root" message briefly flashes.
Only recent change was I tried an app called "Automate". I have since uninstalled it, but the problem still exists.
Any suggestions? Help would be appreciated.
retiredguy1945 said:
Have a stock S3, Sprint-branded, running 4.4.2. As of yesterday, I can't get mobile data (apps say no internet connection). It works fine on WiFi.
I noticed on startup, towards the end of the process, a "could not obtain root" message briefly flashes.
Only recent change was I tried an app called "Automate". I have since uninstalled it, but the problem still exists.
Any suggestions? Help would be appreciated.
Click to expand...
Click to collapse
Sounds like it was rooted at some point, and an app requiring root access is still installed. Install SuperSU from playstore and see which app it is

Categories

Resources