yashsingh1/xdaforums huggingface dataset:
[Moto X Android Development] hachamacha:
Another way to go about tethering with these 5.1 zips is as follows:

The goal is to add the following line to {your-moto}/system/build.prop (at the end of the file is fine)

net.tethering.noprovisioning=true

To do that:

1) use root explorer (or equivalent) to navigate to /system

2) mount /system rw. (read-write).

3) make a copy of build.prop using the copy function and save it with some easy to find name like build.prop.orig

4) open for edit (via root explorer) build.prop and add this line at the end "net.tethering.noprovisioning=true".

5) save the build.prop file

6) verify that the line is in it.

7) remount /system as ro (read-only)

8) reboot and test tethering.

This works fine for me on a Vzn (unlimited data plan) xt1060 dev ed.

Also: You could do that process through adb commands as well, but it'll be a slightly different way of doing the mounts rw and editing.

Good luck.

Oops: I didn't see the post before this that explains the xposed way. Either way is fine.
[Moto X Android Development] kenstyle:
Just did all of this, flashed the latest version of Xposed, installed the Xposed app, found X Tether xposed, installed it, rebooted, and it still says "checking subscription" when I click on Mobile Hotspot, sigh...
[Moto X Android Development] mastarifla:
Try the build prop edits listed above and see if it helps any
[Moto X Android Development] kenstyle:
Wish I had the knowledge, computer skills, and cajones to do all of this...but thank you either way. :good:

---------- Post added at 08:25 PM ---------- Previous post was at 08:14 PM ----------

build prop edits?

you mean re-flashing to an "older" version of Lollipop?
[Moto X Android Development] mastarifla:
No, the steps listed above for modifying the build.prop, the file is located in the /system folder, it's basically a text file with a bunch of key/value pairs that tells you the details of your phone, you can use an app like RomToolbox if you need a more graphical user interface in order to edit the file
[Moto X Android Development] kenstyle:
Yeah I think I'm going to give up on Lollipop at this point, and leave the game of rooting/flashing ROMs. Been doing this for too many years now, and every time the rabbit hole keeps getting deeper and deeper.

Going back to recovery and flashing to my back up one last time.

Thanks for your suggestions again.
[Moto X Android Development] kenstyle:
I've been having some trouble restoring my backup with TWRP.

TWRP gets me past the Restoring Data part (which took a good 10-11 minutes), and then it gets stuck on the wiping cache part.

Any ideas what I'm doing wrong? I did a factory reset before the restoring part if that helps.
[Moto X Android Development] mastarifla:
If you did a factory reset then you don't have to wipe the cache, as it will rebuild once you boot up again, make sure you aren't restoring the cache partition, also make sure your permissions are fixed
[Moto X Android Development] kenstyle:
TWRP automatically wipes cache after restoring the backup, so that's out of my control.

How do I fix my permissions?

---------- Post added 9th November 2015 at 12:03 AM ---------- Previous post was 8th November 2015 at 11:59 PM ----------

Looks like I'm permanently stuck with Lollipop, lol.

I couldn't restore my KitKat backup, so it looks like I will have to figure out how to get this native tethering back in business.

---------- Post added at 12:12 AM ---------- Previous post was at 12:03 AM ----------

I have no idea what's going on.

Flashed the rom clean again, SuperUser, then factory resetted, booted up and I've lost all of my apps, but at least GApps is working and I've started to redownload all of the apps on my account.

When I have most of my settings set back to normal, I will look into RomToolBox to edit the system file. Wish me luck!
[Moto X Android Development] kenstyle:
THANK YOU to the both of you for your AMAZING help.

Just went through a whole emotional rollercoaster Sunday of excitement about upgrading to Lollipop, then losing native tethering, trying to recover a backup that got stuck in recovery, worrying about bricking my phone, and then finally sorted everything out and all is well again.

My phone feels brand new again with the updated software, and is running much faster and smoother. And native tethering is working again with Hachamacha's write through, props to you good sir!

Mastarifla, sent you a little something to your Paypal.

Hachamacha, if you have a Paypal account PM me your email address so I can send you something for your efforts as well.

Cheers! :)
[Moto X Android Development] hachamacha:
Sounds like you had a busy day ;;)

I'm glad you got it working OK. I'm probably good with this phone for another couple of years or until they start making reasonably sized phones again that aren't the size of a house. No donations for me , but thanks.

I think I also managed to destroy my /data partition on my update to 5.1 on the xt1060 once, and I had to reformat it, and restore, etc. Anyway, good deal. Cheers.

--
[Moto X Android Development] kenstyle:
Aint that the truth. :good:
[Moto X Android Development] mastarifla:
Nice work man! I'm glad everything worked out :)

Let me know if you run into any issues and I'll be sure to lend a hand, and thank you kindly for the donation, as it motivates me to help others as well :)
[Moto X Android Development] slavikoid:
Flashed XT1055 US Cellular rom for XT1056 without radio. Works fine!
[Moto X Android Development] kenstyle:
Looks like I'm having the common speakerphone problem that most people have had after flashing this ROM.

Did some reading last night, and it appears that flashing the new radio will solve this issue.

I know TWRP 2.8.7 has been causing problems for a lot of people, so I will be upgrading from 2.6.3 to 2.8.6 instead before I flash the radio.

Do I need to update the bootloader as well? And if anyone can provide a quick tutorial to update TWRP (and the bootloader if necessary), I would really appreciate it. It's been a while and my mind can use a refresher.. Thanks!
[Moto X Android Development] hachamacha:
If you download and unzip the *verizon*modem*.zip* file from the same place you pulled the xt1060 ROM's, you'll see a README in there that has these instructions in it:

1. To flash, put the phone in fastboot mode: Power OFF...then Power ON+Volume Down. Alternatively, you can reboot into fastboot mode if you have adb... adb reboot bootloader
2. Next flash the images using fastboot:

$ fastboot flash modem NON-HLOS.bin
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot

Optional: flash these images if you are encountering boot-loops or unusual problems. Plesae backup before flashing, and keep in mind that you may not downgrade (flash a lower version firmware) after flashing these files.

$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot

I would try the first batch and reboot, and then if that didn't help with the speakerphone, do the last batch (bootloader) and reboot. It worked for me. To use fastboot, you just have to plug in the phone to a PC and use adb so : "adb reboot-bootloader" should get you there, then use fastboot commands. Put all the files you want to use including "fastboot.exe & adb" in the same spot to make it simpler.
[Moto X Android Development] rodohmes:
Are you using it on the Sprint network?
[Moto X Android Development] kenstyle:
Is there a way to do all this with a custom recovery like TWRP instead?

I am on a Macbook Pro...unfortunately for once.
[Moto X Android Development] hachamacha:
I'm not aware of a way to do this (well not without writing some custom code full of low level "dd if=? of=?" commands) using TWRP. But I'm wondering if there's some reason why this (adb and fastboot) should be any tougher on a Mac. I found this link: https://seo-michael.co.uk/how-to-setup-adb-on-os-x/ and also this one which takes into a account a couple of typo's in a Mac script: http://lifehacker.com/seems-like-the-mac-script-has-some-typos-it-is-being-t-1588051572

Anyway, once you install it on a Mac which is pretty much a pretty GUI over BSD, the commands ought to be the same as what I quoted. If there's a difference (I don't have a mac these days), then it would be more like a linux box so if the following command (as an example) didn't work:

---- on PC ----

fastboot flash modem NON_HLOS.bin

--------

Then if you were sure all the binaries (.bin files & fastboot.* and adb.*) were in the same spot and you had changed your path to be there (cd {path_where_stuff_is}) in a "shell windows" (or whatever it's called on a mac) , then a sure-fire command to make this work in the command or shell window would be something like this:

--- on Mac in shell ----

./fastboot flash modem ./NON_HLOS.bin

-----------------------------------

And so on. I'm sure there are a few tutorials on using ADB/FASTBOOT while on MacOS.

Good luck.

Actually, I just read the 2nd link I referenced and saw this:

Seems like the Mac script has some typos. It is being to told to move Mac/adb_Mac to /usr/bin/adb and Mac/adb_Mac doesn't exist (same for fastboot).

Changing the script on the affected lines to the following corrects the issue:

line 19: sudo mv Mac/adb /usr/bin/adb

line 22: sudo mv Mac/fastboot /usr/bin/fastboot

That (/usr/bin) would almost certainly be in the executable path for any shell (almost..) so the command should just be (e.g.):

fastboot flash modem ./NON_HLOS.bin

And.. If anyone here has a Mac and has something to add about using ADB & Fastboot from it, now might be a good time to speak up.

-------------edit #2 or 3) ----------------

I just noticed this link that is on XDA and is a sort of tutorial for using a Mac with fastboot & adb: http://xdaforums.com/showthread.php?t=1917237

It looks much more "macos-like" than the other ones I supplied. I pretty much do all this stuff in a VM running Ubuntu 12.04 that is running on a PC. I just have the USB routed via a filter so that it goes to the VM if it's booted. You could do the same from the OSX download of Virtualbox.org.
[Moto X Android Development] RohanAditya:
Hi

Can you please post the stock ROM for XT1052 Asian Retail version?

Thanks
[Moto X Android Development] kenstyle:
Appreciate all your help Hachamacha, I've got ADB and Fastboot installed on OS X, booted the phone up in Fast Boot mode, opened up a terminal, typed in ./Fastboot devices but instead of getting a serial number from my phone I get an Illegal Instruction: 4 message.

Doesn't seem like there's any communication between my phone's Fastboot to my laptop. Not sure what to do at this point..
[Moto X Android Development] hachamacha:
So what happens when you type in something that doesn't rely on communicating to the phone at all, like :

./fastboot

## Look at how I did it and the output in the window below this.

It should give a list like this:

$ fastboot
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message

options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable

What I'm wondering is whether you somehow were able to install a machine dependent version of fastboot? If fastboot can at least spit out the regular help text (fastboot with no parameters), then it's probably OK, but if it can't, then we've got some sort of mismatch. None of this yet has anything to do with the phone (although later, it may be a problem as well).

I'm guessing that something like a) wrong word-size (e.g. Macs were once 32 bit, now are 64 bit) or b) The fastboot executable could have been built for an older Mac running another chip-type. Mac's went through some sort of progression like this: first group were all Motorola 68xxx series chips for years, then all powerPC's for years, and now Intel for years. Of course, if there's a mismatch from when the utils were built, then we'll have to run down the right version of adb & fastboot.

Also if you could try (in a shell window) doing this command and post the output back here, I'll check it tomorrow:

$ uname -a

also

$ cat /proc/cpuinfo

(it's possible that either or neither of them is supported by their version of BSD, but it's worth a shot. Any info is good.)
[Moto X Android Development] kenstyle:
I'm sorry, but your post is too intricate for me Hachamacha. I am a complete newb at ADB and Fastboot to be quite honest with you.

If it helps, this "tool kit" was what I had used to root my Dev Edition when I bought it in 2013. http://xdaforums.com/moto-x/development/toolkit-moto-x-dev-edition-mac-osx-v2-02-t2666560

Think I could flash the Modem with this?

---------- Post added at 07:26 AM ---------- Previous post was at 06:33 AM ----------

OKAY Update!

After getting some lightning quick help from VitaTaf, there is a command in the terminal you have to input for OS X to detect the Moto X.

chmod a+x fastboot

then type: ./fastboot devices

and you will see the serial number!

from there, I just followed the rest of the directions with flashing the NON-HLOS.bin, fsg.mbn, rebooted it...and it got stuck on a loop.

went back to Fast boot mode, flashed gpt.bin, motoboot.img, rebooted again, and all is well! Just tested the speakerphone and it's working again! :)

HUGE thanks again to Hachamacha and VitaTaf for helping me out (and any other fellow OS X users who upgraded to 5.1) with this speakerphone issue! :)
[Moto X Android Development] hachamacha:
Cool. I forgot that BSD is basically Linux so far as file protections go and "might" need +x (execute permission) out of the archive file but am happy it worked. Good to VitaTaf. Good deal ;;)
[Moto X Android Development] slavikoid:
I use it with Intertelecom [UA], will work fine with Sprint. Just don't touch radio.
[Moto X Android Development] CristianLeon:
Error executing updater binary in zip '/sdcard/XT1052_5.1_RETEU_Debloated.zip' ... Device is xt1052
[Moto X Android Development] mrdunlop:
[MENTION=2658922]hachamacha[/MENTION] As was pointed out by [MENTION=2921769]kenstyle[/MENTION] I need to update my radios and bootloader? to get speaker phone working again. I am currently on AICP 5.1, Verizon Moto X Dev edition and I am confused as to which files I need to flash and where I can find them. I have done adb before so I am sure I can figure it out, its just been a while. Is there a thread with specific instructables?

I have been out of the phone game for well over a year and just now getting back into it, I have lost a lot of my knowledge.
[Moto X Android Development] hachamacha:
The easiest way to get the files , probably all of them, is to go to the OP (link: http://xdaforums.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843 ) and in the OP, look for your phone model, and I think "modem software" under that model. Click the link and download the .zip file.

The file you'll end up downloading although it might appear to be one, is not anything you could use custom recovery on. It's just a zip file full of the stuff you need (.img files for radio, bootloader, etc and some versions for various platforms of adb & fastboot (I think)). So unzip that file, and put them all somewhere handy where you can open a shell or cmd window.

If you read the readme (from that .zip file) or even one of the above posts about modems, you'll see the rest of it. --- Good luck.

note: It seems that some people can get away with installing everything up to the "bootloader" section but some people have to go the full route of flashing everything via fastboot. Mine (xt1060) just worked after the first part and a reboot. Well, there's no way to do fastboot without doing a reboot after ;;)
[Moto X Android Development] ChavitoArg:
Hi everyone. Ive flashed this over 4.4, now im in a bootloop. Did a miss something? ive flashed modems + motoboot.img. Should i flash motorola stock 5.1 first? Thanks in advance

nevermind: i was missing this... lol

$ fastboot flash partition gpt.bin

$ fastboot flash motoboot motoboot.img
[Moto X Android Development] amanmajeed:
I am going to try the same now.. (on XT1053)

Did this fix speakerphone and bluetooth for you ?
[Moto X Android Development] ChavitoArg:
Im not aware of those problems, 2 days with the device

Enviado desde mi XT1058 mediante Tapatalk
[Moto X Android Development] RohanAditya:
Thanks man,

Also do you know if there is a google drive link to this?

Filefactory downloads are really slow
[Moto X Android Development] athulele:
I have the 5.1 Europe Retail in my Mega. But it's not the latest one.

Can't upload due to slow speeds though.
[Moto X Android Development] RohanAditya:
Let me start off with this: I'm new to this.

I accidentally erased everything in the TWRP Wipe section while I was doing a factory reset and now it says 'No OS installed'.

Do you know how I can fix this?

I tried using RSDLite as suggested in this link: http://xdaforums.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515 but it is not recognising my device.

I have Motorola Device Manager installed.

And can you please tell me what the XML file is and where this particular line is- <step operation="getvar" var="max-download-size" /> ?

I desperately need some help.

Thanks in advance.
[Moto X Android Development] athulele:
Okay, sure.

If you want to flash the modded rom, download the xt1052 one from the first post in the thread.

Then flash TWRP through fastboot and boot into it.

Connect device to computer and transfer the files and flash it like a normal rom.

If you want to return to stock,

Here's the link to 5.1 EU XT1052 image - https://mega.nz/#!U9lRFBgD!POchMYI96ZTy16M_PGSZ4aIjo6ktpaHKaJAmp6XBUR4

1. Download mfastboot from here - https://drive.google.com/file/d/0B3mZm7hSf2QbcWE4VnRCUF81OVk/view?usp=sharing

2. Extract it in a folder.

3. Download factory image from above MEGA link and extract that into the fastboot folder.

4. Open a command prompt in that folder (Right Shift + Click -> Open command window here)

5. Here are the commands you need to perform - (there's also output so you can confirm that it's successful)

http://pastebin.com/5RQZsPuj

Follow that order and you'll be fine.
[Moto X Android Development] RohanAditya:
Quick question:

This is the actual stock ROM right?

http://www.filefactory.com/file/334o0odl6iup/XT1052_GHOST_RETASIA_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
[Moto X Android Development] athulele:
Yes, thats the Asia Retail version.

The one I gave a link to is the Europe Retail.

Don't worry though, since they are both for XT1052 they just work fine. I've tested both.

I gave the Mega link since I already had that uploaded and you can download faster from there
[Moto X Android Development] RohanAditya:
Ok thanks.

I'll try it and tell you what happens.

---------- Post added at 12:37 PM ---------- Previous post was at 11:47 AM ----------

I got it working again. * Huge Relief!! *

Thanks a lot man.

I really appreciate it.
[Moto X Android Development] athulele:
Glad to help :)
[Moto X Android Development] rodohmes:
I flashed back to stock to take the OTA. When (if) I get it I'll do what I can to get it to him.

To be honest, Kit Kat isn't as bad as I remember, haha. Being able to use the Moto apps is really refreshing too. I thought I'd miss the look of Lollipop more.
[Moto X Android Development] DanRo80:
I really enjoy the stock Moto apps. That is the main reason that I like stock Moto on this phone. I use the text while driving and not touching my phone everyday.
[Moto X Android Development] kenstyle:
Discovered a small but not much of significance "bug" with 5.1 on Verizon.

If your hotspot is on and you make a call, the hotspot notification will say "Paused because of phone call." After the call is finished, the "paused" message does not go away even though the Hotspot does continue to work.

Small issue, not a big deal, but just something I noticed.

Everything is still working very well and smoothly. :)
[Moto X Android Development] hachamacha:
I saw this and wondered if it could still be that old thing of Verizon's where you can't use data + talk simultaneously without some sort of problem. I guess it's not like that anymore because I tested your scenario with my xt1060 (which is hacked for hotspot via the extra line in build.prop). I turned on the hotspot and setup another phone with it and then a) made an outgoing call, b) made an incoming call and c) looked up some websites on Chrome on the hotspot phone.

I didn't get the error message about pausing. That seems kind of curious. I also should mention that I don't have any "plan" that includes the hotspot. I've got the old grandfathered .. unlimited data plan where they'd like me to pay another XX dollars / mo. for tether, but of course, I haven't.

Doing that above got me curious about this stuff. I had picked up a cheap used Galaxy Alpha (Brazilian even..) (GSM) and paid for one month on their cheapest prepaid plan which allows no tether as well. I realize this is a completely apples to oranges comparison, but I've hacked the Alpha exactly the same way and tether works fine, so I did the above tests on that as well without any noticeable glitches. I just used this phone to work on one problem that got my attention in the Google issues bug-base. Both those phones are on Lollipop, rooted & unlocked but fairly stock aside from cleanup of junkware.

It may have been about 5 years ago when you had to use some carrier like ATT to get voice & data, but I'm not sure. It just stuck in my head when I saw this.
[Moto X Android Development] kenstyle:
I am the same, grandfathered unlimited data plan on Verizon. Never had this issue with hotspot on the original Google Nexus and HTC Incredible (both rooted of course).

Anyway, like I said it's not a big deal. Just have to do a reboot to get rid of the Paused Mobile Hotspot notification if it starts to bother me. Turning hotspot off and then back on does not seem to get rid of the notification either. But hotspot still works regardless both during and after the call is over, so in the end I'm not one to complain.
[Moto X Android Development] hachamacha:
This is kind of nutty sounding, but it sounds insane enough to be possible. The thing we need (both in our phones and in our network) to use simultaneous voice & data (LTE only) is called SVLTE (or advanced calling (1,0)) and in our case, the Moto X 2013 had that ability (which was slightly unusual for a Motorola phone then), but the network (Vzn) only supposedly started rolling out the network changes in mid-2015. I guess it could also matter where in the country we are (regarding the rollout). In whatever page I was reading about this, it also mentioned that in some cases you could call to have advanced calling enabled because (according to what sounds like an urban legend to me now) even if both network and phone have it, there is some switch or flag that requires flipping to enable/disable it.

And a supposed list of phones that do NOT have SVLTE capabilities (Verizon network phones): It works on all Verizon LTE phones except the iPhone 5/5S/5C Moto X 2014 and Droid Turbo. (go figure)