Related
Hello all. Ordered my Verizon Moto x Dev Edition during the painful cyber monday sale. I've been lurking around and reading up on what needs to be done. I have a basic idea of the process. Just making sure it is correct.
So to begin i need to unlock the bootloader, which is done through the motorola website here
https://motorola-global-portal.cust...2LzEvdGltZS8xMzg2MDc1NzQwL3NpZC9KcTFvblVHbA==
Before or after i unlock the bootloader i will ota update to 4.4, so i will be following this guide to achieve root
http://forum.xda-developers.com/showthread.php?t=2536200
This is quoted from the above thread
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. **Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues.** After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (**use the motorola fastboot binary**)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
Click to expand...
Click to collapse
I assume for step 3, I just place the mfastboot.exe in my android sdk platform-tools folder. This is what i really need clarification on. The rest is pretty self explanatory.
After all that i have read and seen the bootloader unlocked screen, looks pretty ugly. So i plan on replacing that also, following this post
http://forum.xda-developers.com/showthread.php?t=2417961
That is a informative thread, but it is a little hazy on what format and what needs to be done to flash a replacement image on a dev edition. Maybe someone could enlighten me more.
I'm sure this is all pretty easy to do once i have the phone to tinker with, I am just preparing myself in advance. I would greatly appreciate some help and tips if one could provide.
Thank you
just run the mfastboot in the same directory as TWRP. Your platform tools folder will work fine. When you open the command window just type mfastboot instead of fastboot.
For the image it needs to be a .bin which it should already be. Place it in the same folder as fastboot, Then fastboot flash logo (logofile).bin
Like you said it is all pretty explanitory. Much easier than attempting to root the locked versions.
Awesome. Thanks so much for the help. Greatly appreciated!
Sent from my Galaxy Nexus using Xparent Skyblue Tapatalk 2
Root away friend.
Sent from my Moto X DE
I thought all you had to do was flash TWRP, and then when rebooting from recovery TWRP would say something like "your device does not appear to be rooted, would you like to root it now?".
Also I thought devices shipping now already have 4.4 on them, but maybe that was bad info.
I know that was true on 4.2.2, didn't check it on 4.4. Just flashed the latest SSU zip and rooted that way.
Sent from my Moto X DE
I am in the same boat as the OP. I was wondering where do you get the mfastboot.exe from to place in your platform tools folder? I am not a noob to fastboot as I have had nexus devices but the mfastboot is new to me. Thanks in advance!
Travisdroidx2 said:
I am in the same boat as the OP. I was wondering where do you get the mfastboot.exe from to place in your platform tools folder? I am not a noob to fastboot as I have had nexus devices but the mfastboot is new to me. Thanks in advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1138092
Got my Moto X DE a few hours ago. Unlocked and rooted
Also got native tethering working. I used the method in this post
http://forum.xda-developers.com/showthread.php?t=2536166&page=4
Used the pre-built exe provided by <:GeeK:> at post #35. Worked like a charm.
I can see why there are not many custom roms, because this phone is great. All you really need is unlock and root and everything is good. That being said........i feel the withdrawls already from find and flashing new roms....
now to research what verizon bloatware i can remove.....
Does anyone know what bloatware is safe to remove. Is there a list somewhere, i seem to not be having any luck finding the proper information about this.
Edit
Also wonder about gravityBox for 4.4. anyone use this on their moto x?
Thanks
Installed xposed and gravitybox. WOW! Its amazing. My need for flashing Roms is satisfied.....for now. This phone rocks.
Still looking for information on bloatware removal.
Edit*****
Was able to rid my device of vzw tones, navigator and something else. Had no luck finding the vzw voicemail apk to delete it, just disabled it in app manger.
Sent from my XT1060 using Xparent Skyblue Tapatalk 2
I've searched a bit and the only root tutorial I can find is locked pending an update.
The phone is on 4.4.4. Is it the same recovery as the non-4G version? Because I've recently successfully flashed recovery and rooted on that phone and wondered if I could use the same files.
I'm comfortable with commands in the terminal so just need to know if its possible and what files to download.
Also, the person it's for isn't bothered about the upcoming Lollipop update so can just wait for a new root method for that.
MilkyJoePD said:
I've searched a bit
Click to expand...
Click to collapse
First you need to unlock the device here:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Then install TWRP through fastboot:
http://forum.xda-developers.com/moto-g-2014/development/recovery-twrp-2-8-0-1-moto-g-2014-t2896165
If you need root, get SuperSU (download the recovery zip)
http://forum.xda-developers.com/showpost.php?p=23427715&postcount=1
Thanks. I've unlocked the bootloader (first thing I did). Is it the same files as the non-4G? Or should I download those specifically?
MilkyJoePD said:
Thanks. I've unlocked the bootloader (first thing I did). Is it the same files as the non-4G? Or should I download those specifically?
Click to expand...
Click to collapse
I have not the slightest idea what you are talking about. There is only one image of TWRP for Moto G (2014).
And SuperSU is universal for all devices.
doppelhelix said:
I have not the slightest idea what you are talking about. There is only one image of TWRP for Moto G (2014).
And SuperSU is universal for all devices.
Click to expand...
Click to collapse
I mean the 2013 Moto G.
I've tried flashing recovery but I'm getting a boot up failed error.
Any idea what's went wrong?
Did you use the TWRP recovery that @doppelhelix posted? If that one doesn´t work you can try philz: http://forum.xda-developers.com/moto-g-2014/development/recovery-cwm-philz-touch-6-moto-g-2014-t2896586
And the Moto G 2 Gen is an almost completely different phone then the 2013 Moto G. Don´t use roms,recoveries etc. made for that device.
MilkyJoePD said:
I mean the 2013 Moto G.
Click to expand...
Click to collapse
Then this is the wrong forum. Please go here: http://forum.xda-developers.com/moto-g .
Wolfcity said:
Did you use the TWRP recovery that @doppelhelix posted? If that one doesn´t work you can try philz: http://forum.xda-developers.com/mot...covery-cwm-philz-touch-6-moto-g-2014-t2896586
And the Moto G 2 Gen is an almost completely different phone than the 2013 Moto G. Don´t use roms,recoveries etc. made for that device.
Click to expand...
Click to collapse
Yep. I'll try this one as well.
Is using fastboot boot command the only way to boot into recovery?
If the phone is off press power+vol.down for 5sec. Custom ROMs or Gravity Box for Xposed will give you a extended shutdown menu
doppelhelix said:
Then this is the wrong forum. Please go here: http://forum.xda-developers.com/moto-g .
Click to expand...
Click to collapse
I'm trying on the 4G version, I just wondered if I could use recovery from the 2013 model because I've recently flashed recovery on one (doesn't work by the way).
I've tried the touch version and get the same error. Using fastboot boot command just boots into the Motorola logo and slowly turns the screen blue.
Why does it just turn blue? All I want to do is root to install Xposed.
After more searching I realised I've been forgetting to adb reboot bootloader before flashing recovery. Could that be why?
Keep in mind xposed is not yet out for 5.0 just so you know
[Q] Having trouble figuring out rooting & recovery works on Moto X coming from Nexus
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
mateopase said:
I'm no noob, I've been rooting for a while, but I can't figure out how to root this damn thing . On a Nexus, I just unlocked, flashed TWRP, then flashed superuser from TWRP, and I was done. How does it work on this phone? Can I just flash TWRP and then from TWRP flash a root zip? I'd rather not use any toolkits and such (which seem to be all the rage on this forum). Running Pure edition btw. On latest Lollipop OTA.
Click to expand...
Click to collapse
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
IINexusII said:
Yes its pretty much the same, the forums are abit immature at the moment there aernt any proper guides, i just did things the Nexus way
unlock your bootloader first through motorola, following the instructions (make sure there are no spaces in the unlock key): https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
flash twrp, then install the superSU zip from adb sideload or from your internal storage if it was already downloaded
youre done
also, you could flash the stock logo image to remove the warning boot image, http://forum.xda-developers.com/moto-x-2014/development/warning-message-unlocked-bootloader-t2871478 to make things look nicer
Click to expand...
Click to collapse
Awesome, thanks. Looks like that's what I'll end up doing. I really messed up my phone though when trying to get back to stock. Hopefully my stock image request will be approved soon and I'll be able to go through the process again.
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
mateopase said:
One more question, if I kinda messed up restoring everything to 4.4.4, but I can boot the phone properly, will updating to 5.0 via an OTA update fix any mistakes I made along the way?
Click to expand...
Click to collapse
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
crpalmer said:
Not necessarily. The ota contains only changed files (not all files) and therefore if something is wrong with a file that wasn't changed (including anything in /data) then it will still be broken after the update.
Click to expand...
Click to collapse
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
mateopase said:
Alright. Do you know of any way to return to stock without going through Motorola's waiting game. It's been a few hours now and I still haven't been approved for the download.
Click to expand...
Click to collapse
Honestly, I haven't looked at what options are available for images to flash.
When I asked for firmware, I believe that I asked on a Friday evening and received access on the following Monday morning. So maybe you'll get access in another 15-16 hours? That is your safest bet if your phone is working well enough to last you until then.
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Asisentr said:
I have a XT1060 (Dev Ed), running Lollipop 5.1, it's rooted, has xposed, and TWRP. I got a notification for a system update, would it be okay for me to do the update? Or would it soft/hard brick my phone?
Click to expand...
Click to collapse
I'm in the same boat (although mine is not dev edition, I have unlocked the bootloader & rooted running xposed) and would love an answer!
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
You can't update if you've modified the system partition, ex. being rooted, having xposed etc.To update you need to be completely stock.
I received the same notification on my XT1060DEV. I chose to ignore it.
Anyone know what the update is for? Someone posted in the general section to "never update a rooted unlocked XT1060 ever" because it bricked it or something. My guess is they didn't know what they were doing. I've been having issues lately with my XT1060 not wanting to connect to 2.4GHz wireless networks, only 5GHz. I've tried removing apps one-at-a-time but no luck. Maybe a reset back to square one and the update is due.
Not sure what the update is for though.
So I'm unlocked and rooted on 5.1 with TWRP... but I don't have stock recovery. XT1060 verizon dev edition doesn't have a stock recovery for anything but 4.4.4. So how do I flash recovery to take the update? I'm assuming that flashing recovery from 4.4.4 is a bad idea? If so, what's the solution?
i have 2 1060s one is retail 16 gb (one daughter) the oher is 32 gig dev tooted twrp expoesd. dev daugher tried to do the update it failed and hten she rebooted. it kept tying to apply booting to recovery after 3 minutes and and failing until I removed the update form cache.
I shoul have captured it so I could examine and fix the script.
retail 16 gb updated just fine.
anybody know what this is?
if it not an image maybe we can apply the frixes directly
Mike7143 said:
Anyone know what the update is for?.......
Not sure what the update is for though.
Click to expand...
Click to collapse
Its the security update patch upto 1st April, 2016.
https://motorola-global-portal.cust...detail/a_id/110538/p/30,6720,8696/reg/1417809
I'm on completely stock 5.1 ROM but I have TWRP 2.8.7.0, Xposed installed. So in order for OTA to succeed I'll have to undo all the modifications including the removal of Xposed? The other changes I've made to the system are the removal of some of the Motorola bloatware.
The trick is now to get the right SBF from Motorola.
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Mike7143 said:
Yeah to take the ota you gotta go back to stock. Honestly, I ended up just dong a factory reset, downloaded a marshmallow ROM for my xt1060, and that was that!
Click to expand...
Click to collapse
Marshmallow?!
So far it's not to bad.
What do you mean by Marshmallow update!? This is just a security update so it should still be Lollipop.
Asisentr said:
So I attempted to install it since no one was giving me any warnings, I flashed it back to the custom recovery, and now my phone is in a bootloop.
Click to expand...
Click to collapse
If you are boot-looping after trying the update with TWRP, you will have to delete the update file using TWRP.
From the TWRP main menu, Choose Advanced, then File Manager.
Go into /cache, and delete the Blur_Versionxxxxblahblahblah.zip file.
That'll stop your boot loop.
Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse
ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...