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.
Related
Hello all!
I am currently running triforce rom on my s4, i really like the rom it just doesn't work with some apps i use. For example Ent online banking app and nfl fantasy football app. But my question is, if i restore my phone back to stock rooted rom, will i still be able to use the wifi tether app? without sprint finding out that is?
Thank You
you should as long as you retain root
and if wifi tether doesn't run properly, you can just flash the hotspot mod instead. That bypasses the carrier check as well.
jj14 said:
and if wifi tether doesn't run properly, you can just flash the hotspot mod instead. That bypasses the carrier check as well.
Click to expand...
Click to collapse
What/which is and how do you flash the hotspot mod. Please teach me, I am on MDL and have other oxdex method and have failed. Thanks...
sprintomatic said:
What/which is and how do you flash the hotspot mod. Please teach me, I am on MDL and have other oxdex method and have failed. Thanks...
Click to expand...
Click to collapse
Assuming you are rooted, and have a custom recovery installed, it should be a quick update.
Are you planning to install MF9? or stay on MDL?
Regardless, download the appropriate version from the thread below (check your settings -> More -> About device, and look at the build number. Also, check and make sure you download the right odex/deodex version (the thread below has detailed instructions on how to identify the right version)
Download the right version to your phone's internal storage, and boot into your custom recovery, and flash it from there. (I assume you have a nandroid backup of your current software - if not, you should make one before you flash anything)
http://forum.xda-developers.com/showthread.php?t=2256950
(again, I cannot stress this enough - make sure you download the right version - there are a LOT of folks who downloaded the wrong version, and then start a thread asking "Why is my phone stuck at the yellow Sprint screen?" etc. It is still recoverable, but adds unnecessary headache)
jj14 said:
Assuming you are rooted, and have a custom recovery installed, it should be a quick update.
Are you planning to install MF9? or stay on MDL?
Regardless, download the appropriate version from the thread below (check your settings -> More -> About device, and look at the build number. Also, check and make sure you download the right odex/deodex version (the thread below has detailed instructions on how to identify the right version)
Download the right version to your phone's internal storage, and boot into your custom recovery, and flash it from there. (I assume you have a nandroid backup of your current software - if not, you should make one before you flash anything)
http://forum.xda-developers.com/showthread.php?t=2256950
(again, I cannot stress this enough - make sure you download the right version - there are a LOT of folks who downloaded the wrong version, and then start a thread asking "Why is my phone stuck at the yellow Sprint screen?" etc. It is still recoverable, but adds unnecessary headache)
Click to expand...
Click to collapse
Thank you for the reply! The farthest i have gone on this and other phones just is to root as I got wifi tether on it and was a happy camper. But with that said, I am open to going further and doing all these flashes. Also, I downloaded the correct version and made sure I m going the right path and did the replacing odex.bak files and all the other ones, But nothing happened. I will prob maybe update for 4.3 but for now MDL will do. I Just need a good guide for a noob on how to do a nandroid backup. Thanks for all the tips.
Update: just did the flash method and it still does not show up, any help would be appreciated it. As a side note dont know if this can help, but my phone has been unlocked for international use, it was manually activated and sprint apps not installed. on MDL stock rom.
What recovery do you have? (TWRP? CWM? something else?)
Are you sure you are rooted?
Are you on the Stock MDC ROM?
When you flashed the MDC hotspot mod, did you see any errors in recovery? Or did it indicate successful flash?
After flashing the mod, do you see the hotspot icon under settings-connections? What happens if you turn it on?
Also, I noticed that you said "it was manually activated and sprint apps not installed"
What is the manual activation that you referred to? Typically, after activation, the phone downloads the Sprint network updates etc, and I believe it is at that time, that it downloads the necessary files for the regular hotspot. These are the files that then get modified by the hotspot mod that I had linked to. Are you saying that you skipped the part where it would have downloaded the Sprint updates? If so, that may be why the hotspot mod isn't working (since it doesn't have anything to modify).
Unlocking for international use (assuming it was done by Sprint) should not cause any issues. I'm unlocked as well.
jj14 is right, without the sprint apps installed there is no hotspot to mod. You will have to find an alternative wifi tether app or redo the activation process and let the Sprint apps install.
The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.
Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache
KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC
Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X
Just got the notice. Updating now!
About damn time.
Sent from my XT1058 using XDA Free mobile app
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Yay, now do I unroot and try the OTA or do I wait for the full image.
ChrisAG said:
Yep, bought mine outright through Fido, updated tonight.
I'm using it on Bell, nice to see you can finally get rid of your carrier label in the status bar.
Click to expand...
Click to collapse
You can? How? I didn't save the link to the release notes, and can't find them now.
thedosbox said:
You can? How? I didn't save the link to the release notes, and can't find them now.
Click to expand...
Click to collapse
Removing provider name from the Status bar:
Settings > Wireless & Networks > More > Mobile Networks > Show Mobile Network (check on or off)
I completely forgot about the carrier being removed. Really cool.
Sent from my XT1058 using XDA Free mobile app
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Steve-x said:
Install went fine, I unrooted, upgraded and then rooted again with no problem. The show carrier on/off is a great upgrade, I don't have to mess with modifying APK's anymore.
The new dialer will take some time to get used to.
Click to expand...
Click to collapse
Ugh... I have TWRP on mine. Can I just unroot, or I need to remove TWRP? (read: flash stock 4.4.2...)
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
R3dbeaver said:
OK. Ended up flashing the whole damn phone again.
So which root method works for us, Rogers users?
Click to expand...
Click to collapse
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
R3dbeaver said:
Ah you used TWRP's.
OK cool. Will give it a shot. Will try. I'm assuming I need SuperSU and BusyBox installed beforehand? Remember, I'm starting clean here.
Click to expand...
Click to collapse
If your bootloader is unlocked then it is very simple. Just go to fastboot and flash the TWRP recovery, once flashed you can access it from fastboot. TWRP will load, then you can just select to restart the phone from it and it will ask if you want to root the phone, swipe to confirm and it will do it and restart the phone for you. Once the phone is booted you will need to finish the process - it should prompt you to update SuperSU, I selected the play store option, it downloaded and installed and was done. From there do yourself a favor and install AdAway
waiting for the firmware image..... anybody knows where to get it?
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Steve-x said:
It has been posted to one of the various sites. I grabbed it the other night but couldn't tell you which site it was from as I am at work right now. Enough searching should find it.
Click to expand...
Click to collapse
Would you please send the download link when you are convinient? I searched and find this http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25, but looks something wrong with the system.img.
Steve-x said:
I removed root using the option in Super SU and then flashed the system.img and recovery.img from 4.4.2 in fastboot.(probably didn't need to do anything with Super SU because I reflashed system.img)
I then let the phone update. When it was done I went back into fastboot and flashed TWRP to recovery, went into recovery and let it begin the root process. From there boot up and update Super SU and finish rooting.
Overall a pretty painless way to go from 4.4.2 to 4.4.4 without losing any data or settings. All of this assumes you have an unlocked bootloader of course.
Click to expand...
Click to collapse
Thanks, works a charm, went from rooted 4.4.2 to 4.4.4.
PS- I grew up in Langley.
I don't know if it's dumb luck or not, but I didn't even unroot and was able to accept OTA to 4.4.4.
This is what I did to prepare the phone:
- Uninstall Xposed Framework from within the Xposed installer itself. Left the installer app in place.
- Changed recovery from TWRP back to factory.
- Enabled all apps previously disabled.
At this point my phone was still rooted. I accepted the OTA and everything worked fine.
Afterwards, I re-installed Xposed from the installer app, and re-disabled the apps I don't use. But left the factory recovery in place since I don't have a need to go into TWRP for now.
Everything is working fine.
No Rogers Update?
I just picked up a Moto X (Brand New) It came with 4.2.2 Im with Rogers, It is a Rogers phone , its been 2 hours now still no software update notification. When I try to check manually in about phone, system update. Keeps telling me my device is up to date??
Any one experienced this before? Or am I being to impatient
Now, a dummy question: what is Rogers?
Rogers is the Canadian phone company that's selling the original Moto X
Last week I took the plung and rooted my phone. I was on PD8 and followed that video I was seeing around then I went and installed xposed along with my favorite apps for xposed. Didn't realized it until today that wifi calling was a no go and then I saw others were having problems. I ended up doing a factory wipe. Then Using the modified Odin I installed PG1 using the BL, AP, CP, and CSC. I tried once without the CSC but I didn't even have an option for wifi or voice of LTE. So then I tried using all 4 files. From there I ended up using the zip floating around on XDA that says it's for all S7s with QC chips. follow the readme instructions and so far I've still got wifi calling. Wifi calling was the one deal breaker for me and I'm so glad to see it's working now. Before I install Xposed this time I will make a backup with Flashify just in case.
do you have the link? i rooted my phone and installed the only rom for the galaxy s7 but the wifi calling is gone. Thanks!!!!
Corwinder said:
Last week I took the plung and rooted my phone. I was on PD8 and followed that video I was seeing around then I went and installed xposed along with my favorite apps for xposed. Didn't realized it until today that wifi calling was a no go and then I saw others were having problems. I ended up doing a factory wipe. Then Using the modified Odin I installed PG1 using the BL, AP, CP, and CSC. I tried once without the CSC but I didn't even have an option for wifi or voice of LTE. So then I tried using all 4 files. From there I ended up using the zip floating around on XDA that says it's for all S7s with QC chips. follow the readme instructions and so far I've still got wifi calling. Wifi calling was the one deal breaker for me and I'm so glad to see it's working now. Before I install Xposed this time I will make a backup with Flashify just in case.
Click to expand...
Click to collapse
Why did you root might I ask? You can get Hotspot easily, and remove bloat with the U firmware? Without the bootloader unlocked I can let figure out why I would want to. Backups are nice, some root software, but damn if my phone doesn't run fast as hell on this U software, package disabled pro and master shortcut lite to change apn_ for hotspot. Just kind of curious. We don't even need root to make our sd the internal partition now with a good guys help. I need to some incentive I guess cause I figured the only reason to root was to change boot screen, modify files and find msl, flash custom roms and make backups and try out AOSP. WHY Trip Knox before we fully bust a nut?
heathmcabee said:
Why did you root might I ask? You can get Hotspot easily, and remove bloat with the U firmware? Without the bootloader unlocked I can let figure out why I would want to. Backups are nice, some root software, but damn if my phone doesn't run fast as hell on this U software, package disabled pro and master shortcut lite to change apn_ for hotspot. Just kind of curious. We don't even need root to make our sd the internal partition now with a good guys help. I need to some incentive I guess cause I figured the only reason to root was to change boot screen, modify files and find msl, flash custom roms and make backups and try out AOSP. WHY Trip Knox before we fully bust a nut?
Click to expand...
Click to collapse
Really? So many posts about why or why not to root and yet you ask again anyway. Viper4android comes to mind. If you take a look you will see with root you could change your boot screen, modify files, and make backups. Although it's so close to the original rom there is a modified rom you can install. All this without tripping Knox.
Corwinder said:
Really? So many posts about why or why not to root and yet you ask again anyway. Viper4android comes to mind. If you take a look you will see with root you could change your boot screen, modify files, and make backups. Although it's so close to the original rom there is a modified rom you can install. All this without tripping Knox.
Click to expand...
Click to collapse
Viper4Android alone is enough to make me want to root..
Can you please put some links to the files you mentioned floating around?
I'd like to take the plunge and root this baby.. Thanks @Corwinder
Orsteezy said:
Viper4Android alone is enough to make me want to root..
Can you please put some links to the files you mentioned floating around?
I'd like to take the plunge and root this baby.. Thanks @Corwinder
Click to expand...
Click to collapse
By far the best guide I have found is over in the Verizon forums but the guide is for all Snapdragon Galaxy S7s. Go here and just follow that guide. Be sure to install that S7 fixv15 you will find under Recommended Steps. Although it's buried in there you will want to freeze The Security Policy Update agent. That bugger alone will cause a bootloop about a week after you have rooted. The Viper4android version that works with our phones can be found here. ViperAtmos is what you'll be looking for. Download it and stick it on your sdcard then use Flashfire to install it.
pixelsinnovations said:
do you have the link? i rooted my phone and installed the only rom for the galaxy s7 but the wifi calling is gone. Thanks!!!!
Click to expand...
Click to collapse
Sorry, I missed this post. Go here and first thing I'd do is return to stock to get your wifi calling back. Sammobile has the stock rom for this phone . Be sure to Odin all 4 files. use the csc file and not the home_csc file.
Awesome!!! Thanks for the help, much appreciated.. Let's hope I make it smoothly, I've waited long enough to root.
I don't have wifi calling. Did the same as you.
mikeyinid said:
I don't have wifi calling. Did the same as you.
Click to expand...
Click to collapse
Well, I finally got wifi calling even after installing xTouchwiz. Of course when I tried disabling DVFS I lost wifi calling. I was worried I was going to have to wipe the phone and start over but all I ended up doing was reenabling DVFS and rebooting. Wifi calling was there again so I'm quite happy with it. True test will be to see if disabling the security policy will stop the bootloop I'd been getting after a week.
Corwinder said:
Well, I finally got wifi calling even after installing xTouchwiz. Of course when I tried disabling DVFS I lost wifi calling. I was worried I was going to have to wipe the phone and start over but all I ended up doing was reenabling DVFS and rebooting. Wifi calling was there again so I'm quite happy with it. True test will be to see if disabling the security policy will stop the bootloop I'd been getting after a week.
Click to expand...
Click to collapse
I'm not sure what happened but I woke up this morning and wifi calling was miraculously working. Very strange. I hope I don't get the bootloop you speak of after a week. That could be disastrous. Does it happen during use or randomly overnight?
mikeyinid said:
I'm not sure what happened but I woke up this morning and wifi calling was miraculously working. Very strange. I hope I don't get the bootloop you speak of after a week. That could be disastrous. Does it happen during use or randomly overnight?
Click to expand...
Click to collapse
the two times I ended up getting the bootloop was when an app appeared to be crashing and the phone was unresponsive. I don't believe it was the app that caused the problem because the two times I had bootloops I was doing different things when the phone just appeared to freeze and I ended up hitting the buttons to power down the phone. When it came back on it was bootlooped both times. After someone claimed it was the Security Policy update program that was causing this and they said either freeze or uninstall it. I't's frozen for now and so I'm just gonna hold my breath and see if it passes the one week mark this time.
Corwinder said:
the two times I ended up getting the bootloop was when an app appeared to be crashing and the phone was unresponsive. I don't believe it was the app that caused the problem because the two times I had bootloops I was doing different things when the phone just appeared to freeze and I ended up hitting the buttons to power down the phone. When it came back on it was bootlooped both times. After someone claimed it was the Security Policy update program that was causing this and they said either freeze or uninstall it. I't's frozen for now and so I'm just gonna hold my breath and see if it passes the one week mark this time.
Click to expand...
Click to collapse
What's that apk called so I can go ahead and do that now lol
mikeyinid said:
What's that apk called so I can go ahead and do that now lol
Click to expand...
Click to collapse
You need Titanium Backup or another program to freeze or uninstall system apps. Freeze or uninstall Securtity policy updates 4.1.69 While you're in there do the same to SecurityLogAgent 4.3.34. That one isn't as concerning but it does give you that irritating message about your unauthorized system changes and reboooting to fix them.
Is anyone experiencing issue with calling? Do you use a kernel governor? Are you on the rom? I'm looking to get my phone in top shape but something is wrong.
undercover nerd said:
Is anyone experiencing issue with calling? Do you use a kernel governor? Are you on the rom? I'm looking to get my phone in top shape but something is wrong.
Click to expand...
Click to collapse
I unrooted. My phone was painfully slow even after applying the fixes floating around.
mikeyinid said:
I unrooted. My phone was painfully slow even after applying the fixes floating around.
Click to expand...
Click to collapse
You probably still have the eng kernal xD just download all the firmware files and flash in Odin to the corresponding files good luck (you can find firmware on SamMobile)
KillerClaw321 said:
You probably still have the eng kernal xD just download all the firmware files and flash in Odin to the corresponding files good luck (you can find firmware on SamMobile)
Click to expand...
Click to collapse
Huh? If you flash the firmware you're unrooting your phone.
mikeyinid said:
Huh? If you flash the firmware you're unrooting your phone.
Click to expand...
Click to collapse
Oops meant reflash the kernal xD sorry ... When I unrooted I still have the eng kernal and my phone ran like dirt ... If you really want performance I recommend re-rooting and using a bunch of forums posts I can link you to that will increase battery life and performance.
KillerClaw321 said:
Oops meant reflash the kernal xD sorry ... When I unrooted I still have the eng kernal and my phone ran like dirt ... If you really want performance I recommend re-rooting and using a bunch of forums posts I can link you to that will increase battery life and performance.
Click to expand...
Click to collapse
Wait, flashing the T-Mobile stock kernel back to the device after rooting doesn't cause bootloops?
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
stumbows said:
Hey guys,
I've had some experience rooting other phones but never a Moto X before so I tried following this guide: https://forum.xda-developers.com/moto-x-style/general/guides-how-to-guides-beginners-t3200808
Then I got to the bit where it says if running 6.0 I need to follow these steps: https://forum.xda-developers.com/mo...t-moto-x-style-xt1572-br-marshmallow-t3259380
Went through that successfully and it seemed to work OK until I realised I had no wifi. It was toggled off so I tried turning it back on with no success. It just instantly toggles off as soon as I turn it on. So I just tried to revert back and try again by using the provided boot_orig.img but same thing. It removed the root but Wifi still has issues so I am thinking the img is probably wrong for my model despite it saying it is for the XT1572 model.
I searched for the wifi issue problem and found a few people having the same issues. Followed the guides about flashing twrp and loading SuperSu 2.62 which some stated fixed their issues. Unfortunately it didn't work for me. I'd still like to root but at this stage I just want to get wifi working but I think I'll need a proper boot image for my model of phone.
Anyone got any suggestions?
Thanks!
Click to expand...
Click to collapse
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
acejavelin said:
So basically, you followed an ANCIENT guide that had you replace your kernel with one that is too old for your modem firmware. (That's a statement, not a question)
Hopefully you did a full backup in TWRP before you rooted, because you need to restore it, and then root properly... otherwise you need to reflash the stock firmware, but if you were on the latest version there no current firmware image available, so we have a conundrum.
Can you tell us your radio baseband and kernel versions from Settings - About Phone please?
Click to expand...
Click to collapse
I didn't take a backup as TWRP broke during the process but the root worked. I am only on 6.0 so is that ok to resolve? I can't see the baseband details at the moment as I am boot looping due to trying to follow another guide on resolving my issues. Trying to load a stock rom on to my device through TWRP now. Will report back soon.
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
stumbows said:
OK I have managed to restore the phone to stock and got wifi working again which is great. Now to attempt rooting again. What method do you recommend for this phone running 6.0?
Click to expand...
Click to collapse
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
acejavelin said:
Magisk is probably the easiest now days, and most flexible but I haven't tested it... or the method in my signature which I know works.
Get the latest version of TWRP, and backup, and get it off the device... it can be a life saver later.
Click to expand...
Click to collapse
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
stumbows said:
OK yep installed TWRP, performed backup, flashed supersu, booted and confirmed root, updated supersu, downloaded and installed magisk.
Now what I want to do is load the sony framework and get a root cloak. Any ideas of best way for that?
Click to expand...
Click to collapse
Nope... Not a clue, sorry.