Related
Is there a reliable app or even one that works to tether wirelessly if you're rooted with the temporary TowelRoot method? I'm on KitKat 4.4.2. All the reviews on the Play Store for the various WiFi apps have negative reviews. I don't want USB tethering either. Need it for my Nexus. Any help would be great.
Sent from my Moto X
Have you tried FoxFi?
danny39 said:
Have you tried FoxFi?
Click to expand...
Click to collapse
I have. Unfortunately I get the message:
"Your carrier has blocked WiFi mode in latest phone update. Please use USB mode or bluetooth mode instead. "
use the xposed module "Moto X Hide Carrier for 4.4+" it hides the carrier label in the status bar as well as enabling native tethering.
msk said:
use the xposed module "Moto X Hide Carrier for 4.4+" it hides the carrier label in the status bar as well as enabling native tethering.
Click to expand...
Click to collapse
Ok awesome. Now my only question would be.. Will xposed modules work with something as finicky as TowelRoot? I'm gonna give it a shot now until I'm able to get unlocked. (fingers crossed)
Sent from my Moto X
i thought towel root doesn't work on moto x? i had been using the jcase root method, and on occasion i have lost root when enabling subsequent xposed modules, but they work fine if i reroot and enable them again.
msk said:
i thought towel root doesn't work on moto x? i had been using the jcase root method, and on occasion i have lost root when enabling subsequent xposed modules, but they work fine if i reroot and enable them again.
Click to expand...
Click to collapse
It is. It's not the greatest and a bit unreliable at times, but it's working for my Titanium Backup and root version of Greenify.
To find out if the xposed module installed successfully, how can I test tethering? I'm not sure where native tethering is located.
Sent from my Moto X
this is a beauty app.. doesnt get any easier http://forum.xda-developers.com/showpost.php?p=53295927&postcount=36
I'm using moto X under att contract, now the android version is 4.4.2
I recently rooted my device with the towel pie root, and it works fine on my phone
But when I tried to use the Xposed, here comes the problem. The xposed apk can be installed perfectly, but when I go in there and tried to install the frame work, it shows as the picture below
Please help me find out why, many thanks!
are you root.. maybe that is the problem...
give privileges of root in settings
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
bilalrajput said:
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
Click to expand...
Click to collapse
https://youtu.be/nF_lJTGKFP0
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
I'm limited to 8 thanks per day. I'll come back later.
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
rnwalker7 said:
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
Click to expand...
Click to collapse
I'm making it a personal goal to respond to as many questions with youtube videos as possible.
I use Google Hangouts and their add-on app for WiFi calls. Have to have Google voice number to do this.
Sent from my MetroPCS Turbo
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Sparksys said:
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Click to expand...
Click to collapse
Advanced calling menu
It's not there..no advanced calling menu anywhere
I'm on computer freeks mm.1.0.4 stock based ROM
It's under advanced calling as mentioned.
Not for me :/
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
I see the same behavior. I'm also unlocked, rooted with twrp. No exposed though.
Sent from my XT1254 using Tapatalk
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
Have you tried turning Wi-Fi back on after Airplane mode turns it off?
Airplane mode turns OFF Wi-Fi.
https://www.howtogeek.com/194421/what-does-airplane-mode-do-and-is-it-really-necessary/
Enabling airplane mode always disables Wi-Fi. However, on most devices, you can enable Wi-Fi after enabling airplane mode. Cellular signals will still be blocked, but Wi-Fi will be working so you can connect to that in-flight Wi-Fi network. Some devices also allow you to enable Bluetooth when airplane mode is enabled.
Click to expand...
Click to collapse
Yeah tried that.
Would there be any way to turn off the radio other than using airplane mode? Also does this feature actually work using verizon wifi calling built into marshmallow?
Sent from my XT1254 using Tapatalk
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Hyperbomb64 said:
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Click to expand...
Click to collapse
What version of SuperSu did you use? And if it was the older beta 2.62, did you then update it to the latest version afterwards?
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per @TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Click to expand...
Click to collapse
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't
Click to expand...
Click to collapse
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
ChazzMatt said:
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
Click to expand...
Click to collapse
I have done both ways meaning flashed beta version of SuperSU, booted, confirmed that I have root, then update. Also I have flashed both and can confirm that I still have root.
So I'll run through it again and check, but I should be able to flash stock firmware, check if wifi calling is working, flash Beta SuperSU, confirm that phone is rooted, update to latest SuperSU, then check if wifi calling is working. Would those steps be correct?
Sent from my XT1254 using Tapatalk
Hi and I'm sorry for a duplicate questions (and for my bad english)
I just Updated to B370 by defaul updater.
All is ok but the bluetooth don't work. When I tap on the icon , it's matt.
What's the problem?
I come from a C900 firmware, after I changed oeminfo to C432B181, then I updated to C432B370.
Thank you
Sal
For me work bluetooth
Inviato dal mio VIE-L09 utilizzando Tapatalk
Also for me no problem
Are there any settings that could create conflict or simply disable the bluetooth attivayion?
How about try going to Settings and Apps and System Apps then look for bluetooth and clear their cache and then restart? Not sure if it works or not with your issue. I got this on trying to connect to my car's bluetooth audio.
No
prismfire said:
How about try going to Settings and Apps and System Apps then look for bluetooth and clear their cache and then restart? Not sure if it works or not with your issue. I got this on trying to connect to my car's bluetooth audio.
Click to expand...
Click to collapse
Thank you for your answer.
I followed your advice but I haven't any positive results.
I'm going to re-flash previous firware B360 by twrp.
I hope it isn't an error.
any advices?
Ok, I flashed C432b360 (on b370) by twrp method.
All ok! Bluetooth and others sensors works
Now I'm on bootloader unlocked, twrp installed but not rooted yet.
I checked for update to b370 but updater says that I'm on latest firmware available.
Why it don't update to b370?
How did you install via twrp?
First, i'm sorry for my bad english.
I have the same problem on my Huawei P9 Plus.
Yesterday i was trying to root my phone. I have unlocked the bootloader, installed TWRP but after that, i didn't know how to enter into the recovery mode, so i leave it. Today i discovered how to enter into recovery mode. I tried to flash supersu .zip, all good, but don't have root acces. I did a factory reset aagain, from TWRP and then i flash supersu .zip.
Now, bluetooth not work, i lost some apps from huawei and also i don't have root acces.
I don't know how to slve this.
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
One very simple solution....only one that works.
Flash back stock rom.. and try process again. If it doesnt work....then obviously rooting or magisk is corrupting some partition. So only way to fix this is stay stock...
jasonc417 said:
Yesterday I got to know the latest Android 10 firmware for my SM-A9080, A9080ZCU2BTCA, and flashed it.
And surprisingly, I managed to get it rooted with Magisk by patching the boot.img, since there is no TWRP for the SM-A9080.
However, one new issue occurs: I get the phone paired via bluetooth to other devices, but after the phone is rebooted, those paired devices disappear from the list.
I searched for two methods, replacing libsecure_storage.so directly or flashing a Magisk module. But unluckily, neither worked.
Thus, is there any more solution? Thanks in advance!
Click to expand...
Click to collapse
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Thanks for your advice.
I found the module in Magisk and it does work!
yomama163 said:
Look up Bluetooth Library Patcher on the Magisk Downloads (or use this link). I use it on Android 10 and never had any issues with my bluetooth devices being forgotten.
Click to expand...
Click to collapse
I'm using a Samsung Galaxy Note 10 Plus (SM-N975) running One UI 3.1 on Android 11.
I rooted my phone with Magisk and experienced this same problem.
After installing the Magisk Module 'Bluetooth Library Patcher' by 3arthur6 and that solved the problem.