WARNING

Edited to add information:

Quote: Originally Posted by picowoodworm Originally Posted by This was pretty simple. Got it to root and got Hotspot to work. Thanks!

Quote: Originally Posted by picowoodworm Originally Posted by I am grandfathered Verizon unlimited. Hotspot never worked for me before. I used the Entitlement Bypass app and have hotspot now.

Quote: Originally Posted by picowoodworm Originally Posted by No problem. I just thought I'd give it a shot and it worked. The app actually says "failed", but it works and it shows this.







Here's the link. Here's the link. http://forum.xda-developers.com/moto...1-5-9-t2705152

Quote: Originally Posted by Caketray Originally Posted by How safe is this root?

UPDATE

Quote: Originally Posted by Caketray Originally Posted by Is there a decent chance that I'll break something beyond repair?

Quote: Originally Posted by Caketray Originally Posted by How do you reflash the stock image?

my qe = 1/1 now!!! So this trips the root checker. And even though I am unrooted now, it still shows as a modified system.All you need to know is here:and here:Please see @ btdownloads7 , @ mikeoswego and @ ClydeDroid threads for the latest 5.0 images!!!!Below is for historical purposes only (or until I get around to editing it, lol!):- success on 5.0 flashing the images that @ Slack3r made from the fxz that @ slogar25 uploaded. Slack3r made a stock ext4 image and a modified ext4 image having a modified build.prop to allow for free WiFi tether on UDP lines. Attached is the screenshot of me using myWiFi Hotspot on my XT1096 on my UDP line!!!!! Yipeeeeee!!!!!!! Thanks so much Slack3r and slogar25!!! maiko1 - will you open up MoFo for XT1096 running 5.0? We don't have a pre-rooted image yet but we have one that has a modified build.prop that allows for free wifi tether, which is what many of us want out of this anyhow.I just tested MoFo for @ maiko1 on my Moto X 2014 running 4.4.4 and it is a SUCCESS!!!!!!! Attached is the root checker screen shot. I was able to modify the build.prop but of course it doesn't survive a reboot. And I used Titanium B/U to uninstall MotorolaOTA 2.0 to stop the OTA from downloading. Of course, it comes back on reboot.And my software status shows Modified so it trips the root checker on the phone. Same thing happens with the DT so it is to be expected.Planning on testing the image for Lollipop next!!!! Wish me luck!!!!The pre-rooted 4.4.4 does not bypass the subscription check to allow for free WiFi hotspot if you have a UDP line. I know I tried it.Thank you!!! I didn't know there was an Entitlement Bypass app. Can you link to it?Keep in mind the big picture of what you get with MoFo - you get a version of fastboot that will let you flash unsigned files to the system partition of your phone. It doesn't flash any other partition - just system.You are not getting a root method with MoFo - you are getting a piece of software that lets you flash unsigned ext4 images to the system partition and only to the system partition of your phone. It does not disable write protection. But if you know how to, you can mod an ext4 system image using linux to have any feature you want in it including the su binary, modified build.prop file or Xposed Installer. And THAT is how you get root and the other features you want on your phone.For 4.4.4, the pre-rooted image gives you root access, but nothing else. Anything else would have to be added to it, including a modified build.prop that would bypass the subscription check and allow for free WiFi hotspot if you have UDP.- You can use the Entitlement Bypass App to get free WiFi hotspot if you have UDP.above.As long as you can get your phone into bootloader mode, you can flash complete garbage to the system partition using MoFo - I know I did it - and then reflash the stock system image using fastboot and your phone will be fine. Or connect your phone to your PC and run Motorola Device Manager and MDM will flash your phone back to stock system.I flashed both the 4.4.4 and 5.0 stock images after flashing the pre-rooted images so I know they are fine. The only image that doesn't work is the pre-rooted 5.0 image. But the stock 4.4.4 and 5.0 are fine as is the pre-rooted 4.4.4 image on Root Junky's site. Although the pre-rooted 4.4.4 image only works if you haven't upgraded to 5.0 yet. I know b/c I tried to downgrade the system and kernel back to 4.4.4 after I upgraded to 5.0. Doesn't work, but doesn't hard brick either.If you are on 4.4.4 and flash the 4.4.4 pre-rooted image, you should immediately uninstall or freeze MotorolaOTA 2.0 to stop the 5.0 OTA. The first thing I did was install Titanium B/U on my phone and uninstall MotorolaOTA 2.0. You can freeze MotorolaOTA 2.0 too if you pay for the Ti B/U pro key.Now having said that, if you are on 4.4.4 and used MoFo to flash the pre-rooted image and then take the 5.0 OTA will you brick? Idk but since you don't have write protection disabled and there is no working pre-rooted 5.0 ext4 image, I don't see what good it would do for you to take the 5.0 OTA while running the 4.4.4 pre-rooted image. So I would uninstall or freeze MotorolaOTA 2.0.I started on 4.4.4, then flashed the pre-rooted 4.4.4 image and tested that it worked using the root checker and by downloading Ti B/U and uninstalling MotorolaOTA 2.0 and modifying the build.prop file. Then I rebooted and confirmed that my changes were lost on reboot. Then I flashed back to stock 4.4.4 using fastboot and the 4.4.4 stock image on RJ's site and took the 5.0 OTA. Everything worked fine, no problems. I didn't run into problems until I used MoFo after I took the 5.0 OTA to flash the pre-rooted 5.0 system image - that image won't boot. So I flashed back to 5.0 stock using fastboot and the 5.0 stock image on RJ's site and then tried again to flash the pre-rooted 5.0 image using MoFo and got the same result - it wouldn't boot.Read my other posts to see what all I flashed with MoFo - Pure Edition system images, images that weren't ext4 files, 4.4.4 system images after upgrading to 5.0, etc. No matter what I flashed using MoFo - even when MoFo told me not to flash the PE system image - I could get into bootloader mode and reflash the proper stock image for my bootloader version. I could also connect my phone to my PC and MDM would repair my phone.The only time MDM couldn't repair my phone was after I flashed the PE system image using MoFo and the PE kernel using fastboot - then MDM just said unknown or something like that. But since I could get into bootloader mode, I just reflashed stock system and kernel using fastboot and was GTG.First you get the most recent version of fastboot and adb on your PC and install the Moto X 2014 drivers. You can get fastboot and adb from the Android SDK. You can get the Moto X 2014 drivers from Root Junky's site here:You should do that before even trying to verify for MoFo.After you have the Moto X 2014 drivers installed, have enabled USB debugging on your phone and have tested that the drivers indeed work by putting your device into bootloader mode, opening a command shell, changing the directory to where fastboot.exe is and typing:fastboot devicesto see that indeed your device serial number is returned by fastboot, then you download the stock image from Root Junky's site here:and unzip it. Then I place a copy of fastboot.exe, adb.exe, AdbWinApi.dll and AdbWinUsbApi.dll from the Android SDK in the same folder as the unzipped stock image. Open a command shell, change directory to where the stock image is and then type the commands:fastboot flash system system.img_sparsechunk.0and keep repeating that for each sparsechunk until they have all been flashed.If you are on 5.0, to put your phone in bootloader mode, you turn it off, then press and hold the volume down + up buttons simultaneously with the power button for about 4 seconds and then release both and you get into bootloader mode.All of what I typed above is very basic info. You should do some reading here to make sure you understand what you are doing.