Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Sakura90 said:
Hi,
I just got a new Moto G, but it's the XT1064 version. I'd like to root, but it seems there's no XT1064 option for CF-Auto-Root from Chainfire. Should I use the XT1063 one?
http://autoroot.chainfire.eu/
motorola XT1063 titan_retuglb titan_umts MSM8226 msm8226 KXB21.85-17 4.4.4 11 720 230 Download a71b95caf989138032a5c4f0dad83519 2 387
Thanks
Click to expand...
Click to collapse
I have had a huge amount of frustration attempting to root the XT1064 over the past couple of days. If you're not afraid of reflashing your phone then you can try it but I highly doubt you'll be able to get it to work.
You can easily upgrade it to Lollipop with "official" firmware, but rooting has given me bootloop after bootloop.
After purchasing the Moto G XT1064 and spending 8+ hours trying to update and root the phone and remove all of the Motorola crapware, I eventually gave up. Right now I have version 22.11.6 installed, which is named "Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip", it makes sense to include the old version number, but they should at least call it "Blur_Version_from.21.11.17.titan...".
I really wish Google would REQUIRE manufacturers to release a stock android rom and an easy way to flash it with every consumer Android phone sold. Then developers could focus on improving the phone instead of millions of programmer-hours wasted on trying to remove the crapware and get it updated.
If you're a developer who wants a clean phone and don't want to waste dozens of hours screwing with flashing roms, just get a GPE or Nexus device, it's not worth saving $200. It's a great phone, but if you were looking for a phone that is easy to develop with, this doesn't seem like the right one. After my Droid X I swore off non-nexus devices, but the Amazon sale got me.
A couple of people claim to be able to get UPDATE-SuperSU-v2.16.zip working, (yes, SuperSU v2.39 exists now, it probably won't work though), but many more people (including myself) were not able to get it working.
Good luck! Please report back if you find a good solution, I'm guessing that many people are tired of the hoops we have to jump through to get a non-crapware stock Andorid device.
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Sakura90 said:
The seller kindly told me he can exchange my XT1064 for an XT1063, as rooting is my first concern (need to get Japanese fonts on it). So I hope to easily root with CF-Auto-Root now. I'll get my new phone in two days. I'm already crossing my fingers . Rooting should be a readily available option by the manufacturer, just like Motorola offers you to unlock the bootloader. Otherwise you're extremely limited. For example, to change a font. Samsungs let you do it in the original firmware, something as basic as this should already be in stock Android. And at least ext2 support, it's a Linux FS from 1993. We are stuck with crappy FAT32.
Btw, I just found this tweet by Chainfire: https://twitter.com/chainfirexda/status/533298320647925760
@ChainfireXDA are you going to be doing a CF-Auto-Root for the moto g xt1064? or will the one for the 1063 work? @Bobboman_2000 1063 version should work
Can you try it on the XT1064? I don't know the risk, but if you say you can reflash the firmware, maybe you can go back?
Click to expand...
Click to collapse
I'll probably try it tonight. Will let you know the result.
You can change the file systems using: TWRP2.7.1.1-titan-motog-2014.img as your recovery.
I agree about the manufacturers. I thought it was growing pains in the early days of Android but we millions of us have to waste several hours trying to get decent security, privacy, and performance out of our phones. All anybody wants is stock Android.
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Sakura90 said:
Great if you try, I've seen no feedback of someone using it on XT1064. Won't changing the recovery affect future OTA updates? I was thinking of trying Stickmount with NTFS-3G. It only needs rooted device.
Click to expand...
Click to collapse
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Can you go back to stock recovery after installing SuperSU? As to have future OTA updates. I'm mean, only use TWRP for rooting.
derekm_ said:
I was able to get 5.0 rooted. Not with CF Auto Root though.
I used TWRP2.7.1.1-titan-motog-2014.img and BETA-SuperSU-v2.38.zip but SuperSU had to be put on my internal storage.
Click to expand...
Click to collapse
You put SuperSU on internal storage because that's the only way TWRP can flash it or because that's the only way you could get root (I.e., flashing from external storage didn't work)?
I have tried both CFAutoRoot and flashing SuperSU from external storage. SuperSU resulted in bootloop. AutuRoot worked but I couldn't power off my phone without the next power up throwing things into a bootloop. I chose not to leave my phone on all the time, so flashed a non-root backup.
I haven't tried flashing SuperSU from internal storage. So maybe that's something to try.
Related
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.
Does new phone come with JB? If so should I stay with it and not to accept OTA?
It seems that Kitkat update introduced several issues (problem with email syncing, bluetooth incompatibility wit some cars, etc). Is there anything else? I am fine with not having the latest and greatest.
Also: is it possible to downgrade Moto X DE (GSM) back to JB? I am not 100% sure from reading this forum.
The kit Kat update had issues but nothing on the scale of the Samsung galaxy family's 4.3 update. I haven't noticed any issue on mine nor any on customers. Totally worth upgrading it.
Sent from my Lumia 928
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
texanman said:
The only issue I am having with mine is that while it says its connected to web (either lte or wifi) it won't actually connect. A reboot fixes the issue until it comes back.
Click to expand...
Click to collapse
Did you have this issue while on JB?
Dont know as mine came with 4.4 which did not have this weird issue. It may be something I installed so a wipe may be in order.
Go to KK, no question
tapped out via XT1053 DE
The only issue I had was Google maps not showing my direct location with high accuracy on. It was hard for me to distinguish if I needed to go right or left then it has a hard time rerouting. Which pissed my wife off lol.
MOTO X Slapped
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps.
Sent from my XT1053 using HoFo mobile app.
---------- Post added at 07:45 AM ---------- Previous post was at 07:36 AM ----------
@rbiter said:
Don't forget text reflow has been deprecated. Major loss in browsers and reading apps. Blink is in web view. Also means invert lost.
Sent from my XT1053 using HoFo mobile app.
Click to expand...
Click to collapse
Sent from my XT1053 using HoFo mobile app.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Mine arrived with 4.2.2 installed, (2 weeks ago) and it took two updates to get to 4.4, 1'st 4.2.2 then 4.4. No regrets on the update for me, but then again I let the updates fly when I turned on the phone.
eksasol said:
It will come with KitKat, and good luck not bricking the phone trying to downgrade it.
sent via tapatalk
Click to expand...
Click to collapse
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Teksu said:
Just got my vzw DE wednesday, 2/12/2014. Came with 4.2.2 pre-camera update. soon as it booted it took the 4.2.2 camera update, then shortly after that came 4.4. did all the updates then unlocked the bootloader, installed twrp and rooted. happy as a clam!
Click to expand...
Click to collapse
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
dray_jr said:
let me make this blunt before you even get your phone
your phone is a DE so you can root any version
is you come with 4.2.2 camera update or 4.4 you can upgrade and downgrade between thouse two versions only
if your phone comes with 4.4.2 you can not downgrade at all so just root it and enjoy because most people are trying to get there and bricking there phones half the time.
if you have any other question please post or PM me
Click to expand...
Click to collapse
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
JoeSchmoe007 said:
That makes it very clear. But can you elaborate on why downgrade from 4.4.2 is not possible? I currently use rooted Droid Incredible on Verizon with CM 7.1 and if I am not mistaken I can flash pretty much any previous ROM I want (I really haven't tinkered with it for last couple of years, so I may be wrong).
Click to expand...
Click to collapse
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Moto X DE - mine coming soon as well - some questions
dray_jr said:
Moto changed the bootloader in 4.4.2 and they dont allow you to downgrade
Click to expand...
Click to collapse
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition. Why go back to 4.4.2 if it ships with a later release?
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
dmm108 said:
My VZW Moto X DE is on its way to me, and I've spent a bunch of time on the forums yet still have the following questions and hope you can help. My current phone is an original Droid Incredible, which I rooted, mostly for recovery, backups, tethering, and system monitoring. This site was a great resource back when I did that and I greatly appreciated the information.
RE: the Moto X, I've read the steps for unlocking the bootloader and which paths for upgrading/downgrading are safe given the release shipped with the phone. That information was for the standard Moto X. If the DE is unlocked, can I just go straight to rooting the phone? If the OTA updates won't work with root, is it best to accept the latest OTA pushes once my phone is online and then root? I want to be clear about what I've gained by getting the DE edition.
I have no plans in the near future for changing ROM's. I'd just like to initially install what I am using on the Incredible - the clockworkmod recovery app (or current equivalent), titanium backuip, and a good tethering program. I currently use android wifi tether.
Thanks for any help.
Click to expand...
Click to collapse
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
edthesped said:
I have a dev ed and keep mine the same way you intend... What I've gleaned so far is that the each update includes a new bootloader version that cannot be downgraded, i.e. if you take 4.4.2 you cannot downgrade to 4.4. At this point the VZW version only has 4.4.
As far as getting the phone to how you want it after you take the upgrades the material in the following two links should get you right where you want to be...
Custom recovery...
http://forum.xda-developers.com/showthread.php?t=2424110
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
He kind of muddied it up by adding other cleanup tools that I'm not interested in, if you're like me and only want the tether hack you will need to go to the 140.45.5 folder in his link and download xt1060-140.45.5-vzw-removal-s.zip He also has an undo zip that you might want to download and stash away just in case.
This part is speculative and potentially dangerous so take with a grain of salt and correct me if I'm wrong.
My understanding is that the big issue from the downgrade is that there will be a partition table mismatch if one takes an OTA upgrade and the phone will be bricked, though I can find nothing solid on this. Being that I plan on keeping a custom recovery I don't have to worry about accidentally taking an OTA and for some reason prefer to have the ability to downgrade, when 4.4.2 comes out I'm going to try to flash everything but the bootloader and I believe the partition table, (I need to read more and understand more before I speak with authority) to see if I can get away with it.
Also, on a side note, I found that freezing pre installed apps/bloat destroyed the wonderful battery life I was getting so I would suggest you keep your phone stock for a few days to get a feel for how the phone behaves before you begin freezing bloat.
Enjoy your new toy!
Click to expand...
Click to collapse
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
dmm108 said:
Thanks for that information. The last paragrapht seems counter-intuitive. I froze apps on the incredible so that it would reduce battery drain, why would freezing apps increase battery drain?
Click to expand...
Click to collapse
No idea, but freezing moto apps killed the battery. I haven't figured out what the culprit is yet as I'll be travelling this week and I don't want to jack up the phone while I'm on the road. I suspect another system app was spending effort looking for a missing app. Had I not ran my phone stock for a week I may have assumed that was just the phone as the high battery use was about the same as what I typically got on my S3. However, once I started freezing apps battery life went way down. Battery is good again after defrosting all Moto stuff that I assumed to be garbage. Once I get off the road I'll start freezing apps one at a time to see if I can isolate the culprit.
My thought is if you run it stock for a week you'll have a pretty good feel as to how the phone performs so you'll know whether your tweaks are helping or hurting you.
edthesped said:
Verizon boot animation and tether hack...
http://forum.xda-developers.com/showthread.php?t=2645343
Click to expand...
Click to collapse
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
edthesped said:
Now that I'm looking at a full size computer I see that you are not getting a VZW version, The link above is not good! Sorry
Click to expand...
Click to collapse
Yes, I am getting the Verizon DE. (VZW, 1st post).
Q&A for *TOOL* Moto X 2014 (XT1095) Pure Edition Recovery FlashTool and Root
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Moto X 2014 Pure - Still have to unlock?
I am very new to the Android world. Just came over from years of iPhone. I've searched all around but haven't found the exact answer. I purchased the Moto X 2nd Edition Pure version. I'm on ATT. I'm trying to root my phone. Is the pure version already unlocked (I thought it was) or do I still need to go through the unlocking process?
Richard.G.Smith said:
I am very new to the Android world. Just came over from years of iPhone. I've searched all around but haven't found the exact answer. I purchased the Moto X 2nd Edition Pure version. I'm on ATT. I'm trying to root my phone. Is the pure version already unlocked (I thought it was) or do I still need to go through the unlocking process?
Click to expand...
Click to collapse
You need to unlock the bootloader. Your phone is already sim unlocked, but that's a different thing. I hope that answers your question
Also, welcome to Android . I'm curious, what made you switch?
sent from my Nexus 7
Ok, that explains a lot and makes perfect sense. Thank you.
I decided to move to Android because of a few reasons. I was impressed at many of the features, especially the Moto X I got. I also just wanted to play with all the different toys of another platform to be honest. I still have my iPad for anything iOS I want to do, and my Moto X for my daily use stuff. I'm already fairly fully committed to Google so all my stuff is there, and the integration of the Google services into Android made everything super simple.
I'm loving the experience so far.
Richard.G.Smith said:
Ok, that explains a lot and makes perfect sense. Thank you.
I decided to move to Android because of a few reasons. I was impressed at many of the features, especially the Moto X I got. I also just wanted to play with all the different toys of another platform to be honest. I still have my iPad for anything iOS I want to do, and my Moto X for my daily use stuff. I'm already fairly fully committed to Google so all my stuff is there, and the integration of the Google services into Android made everything super simple.
I'm loving the experience so far.
Click to expand...
Click to collapse
I am glad your experience is going well.
I am always interested to see why iOS users switch to Android. I come across and work with iOS users who always bash Android, and their reasons are unjustifiable. it's good to read some iOS users' experience with Android, like you :good:
First, thanks a lot. I was able to recover my stock recovery on XT1097 (Brazilian Pure Edition Version) with no problems at all
Second: Is there a possibility to adapt Philz or TWRP to our device??
I'm waiting too for a version of Philz Recovery
mega download not working
can you check your mega files. cannot download.
Tested link. Downloading fine
Richard.G.Smith said:
I am very new to the Android world. Just came over from years of iPhone. I've searched all around but haven't found the exact answer. I purchased the Moto X 2nd Edition Pure version. I'm on ATT. I'm trying to root my phone. Is the pure version already unlocked (I thought it was) or do I still need to go through the unlocking process?
Click to expand...
Click to collapse
I made the switch last year too, namely so that I had a better experience with Google Glass. I love it and won't be going back. Just so you know, your service provider is AT&T, as is mine, but your Pure Edition phone take the T-Mo updates, not AT&T when they are available, so don't get confused. I rooted and totally enjoy it, although it's a little scary doing all this ADB stuff, I had to break out an old Windows computer as not much is written or explained for Mac, lol. But everyone I've encountered is really helpful.
I'm debating rooting again do it now or wait for Lollipo, I want to unlock the bootloader, but don't want to lose my personalized bootscreen in exchange for the ugly bootloader warning screen. Don't know how to save it so I can put it back, lol. Welcome to Android, enjoy the freedom.
Did anyone tried to root on XT1097? Did you guys used the Pure version ? (XT1092)
adb not recognized
'adb' is not recognized as an internal or external command, operable program or batch file.
any suggestions? i've copied everything into the adb folder
tdalias said:
'adb' is not recognized as an internal or external command, operable program or batch file.
any suggestions? i've copied everything into the adb folder
Click to expand...
Click to collapse
Adb is in tool folder just leave extracted folder on desktop
I want to confirm before start that we can use the updated tool to upgrade to 5.0 even if we are on a rooted version of 4.4.4 with an unlocked bootloader?
Can anyone confirm success? Is there data loss?
Thanks
fastboot oem lock begin....
tdalias said:
'adb' is not recognized as an internal or external command, operable program or batch file.
any suggestions? i've copied everything into the adb folder
Click to expand...
Click to collapse
I couldn't the script to run any commands even though adb devices was recognizing my moto x. Just did it manually. Don't forgot to put "fastboot oem lock begin" before flashing anything and "fastboot oem lock" after the final file....(i noticed these commands are not in the script)
titanium backup not working
Anyone having issues with titanium backup and not having su access even though it does?
I've got adaway installed and working, not sure why TB isn't working. Tried installing busy box and SU to various locations.
Multi-Tool Error
Hey guys, I used the multi-tool to downgrade from the first 5.0 to 4.4.4, worked fine. Now when I select option 6 to flash 5.0 OTA i get the error "device not found" did I miss something?
RUNME.BAT
Just downloaded v4.1 from the main mirror but there is no RUNME.bat. Does anybody know if there are special instructions to run the updated version?
I own an XT1097 with lollipop. I unlocked boot loader then used Moto x 2014 Tool to flash stock unroot and then I flashed radio from Brazilian firmware to get signal back. If you want I can make a tuto 4 u.
---------- Post added at 04:36 AM ---------- Previous post was at 04:31 AM ----------
ppphfwhatever said:
Hey guys, I used the multi-tool to downgrade from the first 5.0 to 4.4.4, worked fine. Now when I select option 6 to flash 5.0 OTA i get the error "device not found" did I miss something?
Click to expand...
Click to collapse
To flash 5.0 OTA ZIP you must first run option 4 or 5.
Asyd said:
Just so you know, your service provider is AT&T, as is mine, but your Pure Edition phone take the T-Mo updates, not AT&T when they are available, so don't get confused.
Click to expand...
Click to collapse
So is this confirmed, as I asked in another thread and was told the update would come from Motorola, not TMO. Given that the software on the phone is ID'd as TMO, it makes sense. I was surprised, though, given the label "Pure Edition," that the software isn't generic. But I'm guessing it only refers to the unlocked SIM and lack of carrier bloat (?).
Sent from my nexus 10 using Tapatalk
Hi, First off, I'm super rusty in the custom rom and kernell scene so explain things as easily as you can please.
Now, I have a moto x XT1053, the unlocked variant that they sold on the moto website that came with a net10 chip.
The thing is that I obviously unlocked the bootloader and installed the TWRP recovery. I have (almost) stock android and by that I mean stock with Xposed. I want to know if any of you guys could point me in the right direction, I mean, do I install the OTA update or do I return my phone to stock, and if it's the later, How do I return my phone to stock to do a proper OTA update?
Thanks in advance!
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
varxx said:
I have the same phone and was in pretty much your situation, including being rusty in flashing roms, kernels and such. I went with the OTA and am very glad I did. My subjective impression is that it's faster and at least as stable.
I thought my phone was close-to-stock, as I had removed some stuff (Xposed, notably) a while back to receive the 4.4.2 OTA. But the new Lollipop OTA wouldn't install, so I took the bull by the horns and flashed stock system.img that I got from Motorola's official firmware repository. I had to request access, and it took about 12 hours for that to come through.
After I downloaded the firmware zip file, I unpacked it and located the system.img file. Search on Google or this forum for the way to flash an img file to your phone, if you've forgotten (as I had). When I have time later today, I'll try to post a link to some clear instructions. I don't want to try to tell you from memory, as this is something I do about once or twice year since I got a Moto X (I tinkered a *whole* lot more when I had an HTC Sensation, but I've decided that if I want to keep my wife, I'd better stop playing with my mobile phone.)
I did this at the advice of a Motorola technician, who said the "most definitive way to return to unroot" was to flash stock system.img for 4.4.4. (I was part of last week's U.S. soak test, so Moto techs were handling questions from people like me who were wrestling with the OTA.)
I had worried that I might lose apps and data by flashing system.img, but I didn't lose a thing. I *did*, though, lose root, and I haven't re-rooted yet. Before I root, I'm waiting for the stock Lollipop 5.1 firmware to be made available on the Motorola repository so that I can have a backup of stock recovery.img.
Meanwhile, I'm enjoying Lollipop, which is like having a new phone.
Click to expand...
Click to collapse
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
mundofeliz said:
So, should I:
Delete GravityBox and Xposed
Install the .img file found within the zip for the Moto X dev Edition
Then I'll be able to install the OTA withouth losing data?
Click to expand...
Click to collapse
The sequence you describe worked for me, assuming "deleting" GravityBox and Xposed is the preferred way of removing them. I can't remember.
The .img file to flash is system.img. You need to know how to get to fast boot/bootloader mode and perform the flash, of course.
If your experience is like mine, after receiving and installing the OTA, you'll have Lollipop without having lost any apps or data.
But you may want to wait for someone whose more up on this procedure to weigh in. When I updated, I proceeded as if I might lose all my apps and data, so I was pleasantly surprised.
BTW, I've since re-rooted, and I haven't had any problems. It's reassuring that the 5.1 ROM image is now available officially from Moto and elsewhere (info courtesy of dtg7: http://forum.xda-developers.com/showpost.php?p=61800775&postcount=11).
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
mundofeliz said:
I'll do a Nandroid just in case. I'll do the steps above too, since all I've done is unlock bootloader, root and xposed I think this'll work for me. Kinda did only that originally for that reason but that was sooooo long ago. And also because the Moto X is such an amazing phone to begin with, I never saw the need to install other roms. Did you flash just the system.img, the recovery.img or both? I requested the firmware from moto and they approved but in the meantime I also downloaded the original too from filefactory, the exact same firmware I'm running (without modifications I mean.
Click to expand...
Click to collapse
IIRC, you'll need to do the Nandroid backup before you unroot, right?
I just flashed system.img. Won't that effectively restore the stock recovery? EDIT: According to the readme.txt file bundled in the stock ROM's zip file, recovery.img is flashed separately from system.img, so system.img will *not* restore the stock recovery.
I always feel safer running official firmware from Moto. For one thing, the labeling on the Moto dl site is very explicit, so you know exactly what you're getting.
I agree that the Moto X is a cool enough phone with a stock ROM that there's little need for custom ROMs. I was a flash-aholic when I had an HTC Sensation. But the Moto X pretty much has everything I need. Under KitKat, I did use XPosed to kill the Google search box, but otherwise I've been happy with the stock ROMs.
Oh, and I usually eventually run a custom recovery (TWRP) so I'll have more boot options. But I don't see that as essential now. I find I'm actually using my phone more than tweaking it, which is a change from previous phones.