Database Develop

Moto X TMO Dev Edition Freezing

Hi,
I just got my Moto X Dev Edition GSM TMO last week, but I got it very unstable, while I had try to wipe cache and factory reset few times.
Some problem that I have
Numeric Keypad is not shown while using google keyboard. The problem that my email is using 2FA from google to entry my 6-digit PIN
Chrome freeze while open quite complex pages
Gmail freezing while open communication more than 3 email on the messaging mode
Path also unstable while need to scroll down and request to reload more data.
Whatsapp stuck when there's few message has beeen received
Thinking to downgrade the os to 4.4, but when I read in some thread inform better not to downgrade that might cause device brick.
Is there any other solution so I can use my Moto X for daily, while waiting for T-Mobile latest 4.4.2 rom.
Please share
Thank you

If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

SymbioticGenius said:
If you have to downgrade to 4.4, but you're waiting for T-Mobile 4.4.2, what ROM are you running?
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!
Click to expand...
Click to collapse
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?

tyapeter said:
Currently I'm using T-Mobile 4.4.2 OTA
Is it possible to restore to factory image with T-Mobile 4. 4?
Click to expand...
Click to collapse
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.

eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks

Let me make it easier. Just flash the system and kernel files leave everything else alone. However the ability to go back depends on how you got to 4.4.2 to begin with, OP said he took the OTA, not sure about you.
My advice assuming you're stock is to call Motorola, tell them you took the ota and these are the issues you're having. Get them to send you a new phone. I'd rather see you do that than brick your phone trying to do it yourself.
MotoX Developer Edition went from German 4.4.2 to Great Britain 4.4.2 to T-Mobile 4.4.2 no problem. Fastboot FTW!

eksasol said:
Yes. But don't flash motoboot.img or gpt.img, it won't let you downgrade those. This doesn't means that you won't brick with other version.
Click to expand...
Click to collapse
Are you sure this is correct? I was told in this thread: http://forum.xda-developers.com/showthread.php?p=50330230#post50330230 (see post #12):
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.
Click to expand...
Click to collapse
So the way I understand it one cannot downgrade from 4.4.2 to any other version because bootloader in 4.4.2 was changed and is not compatible with any previous release.

tyapeter said:
Eksasol,
What did you mean with don't flash with those files? Is that means unzip the image files and take out those files and zip again?
Which images is the best one for downgrade, from the sbf Blur_Version.161.44.25.ghost_row.Retail.en.US.zip or TMO_RETAIL_XT1053_4.4-13.11.1Q2.X-69-3_MR2_1FF.xml.zip
And also what you mean with "This doesn't means that you won't brick with other version"? Is that mean that not guarantee that downgrade won't have brick on the devices?
Please advice thanks
Click to expand...
Click to collapse
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366

eksasol said:
If you haven't already unlock the bootloader, then you should just send the phone back. Once you unlock the bootloader the warranty is voided and you'll be stuck with that phone. If you still intend on flashing:
You flash them using mfastboot while in flash mode, do not flash motoboot or gpt, also don't run "fastboot getvar". Manually perform these commands:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase customize
mfastboot erase clogo
After flashing T-Mo 4.4, you can receive OTA update to get back to 4.4.2.
As for downgrading to other versions, read this sticky before flashing anything: http://forum.xda-developers.com/showthread.php?t=2635366
Click to expand...
Click to collapse
Thanks a lot, it works

[Q] Attempted to Downgrade and now bricked [solved]

First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
**EDIT**
If you have done the same bone-head move I made, then follow these simple steps.
1. Use RSD lite to update to 4.4.4
2. Follow this guide to then root your device once you have updated to 4.4.4
This works because your bootloader is unlocked, thanks to sunshine.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.

wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse
RSD 422 means a downgrade. What did it "say"?
Downgrading is the no no.
---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------
http://forum.xda-developers.com/showpost.php?p=55491148&postcount=10

samwathegreat said:
You should have never attempted to downgrade...
Try using fastboot & mfastboot.
Unplug, then turn off the phone. Boot it into bootloader mode. Once in BL, plug usb into PC.
You must have at least minimal adb/fastboot, AND the mfastboot binary (search it).
Unzip the 4.4.4 SBF into the SAME FOLDER that both fastboot and mfastboot are in.
Open a command prompt, browse to the folder containing the unzipped files, fastboot, and mfastboot. Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot reboot-bootloader
[the device will reboot into the bootloader] ignore the fact that some commands are being run twice...
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img [make absolutely sure to use the Mfastboot binary for flashing system.img]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
If you see an error about variable not supported, ignore it. If you get a different error, post back with a screenshot.
Does it boot into android now? You should be 100% stock, unlocked. Ready to flash TWRP and root.
Click to expand...
Click to collapse
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
But I followed the rest of the directions and it still will only boot into fastboot.

wisenick said:
Thank you, however when I try the first command "fastboot flash boot loader moto boot.img" it says "(bootloader) Variable not supported! Then says (bootloader) Permission denied
Click to expand...
Click to collapse
Did you really put spaces in between boot and loader? And Moto and boot?

samwathegreat said:
Did you really put spaces in between boot and loader? And Moto and boot?
Click to expand...
Click to collapse
No sorry, auto correct on the wife's phone.

wisenick said:
No sorry, auto correct on the wife's phone.
Click to expand...
Click to collapse
A "Permission denied" error sounds strange to me....don't recall having seen that one before.
Though I'm rather certain that your downgrade attempt (big no-no) is the culprit, I'm curious if @jcase might have any suggestions...

1) I don't think you are bricked, this should be fixable. This is due to you flashing older firmware to a device that has been updated, nothing to do with sunshine.
2) your title makes it sound like sunshine to blame, this is really bad for me. SunShine CANT brick motorola (nor htc) phones. We simply have too many safety checks, and verification. If you were able to flash and boot TWRP (which you were because you took a backup) then it can't be sunshine. It would be great if you changed the title to be more accurate.
Having said that, I have no problem helping you recover your phone, it certainly isn't bricked
I'm out from 10amPST to 2pmPST tomorrow, but please email me jcase AT cunninglogic DOT com, and I will have you up on your feet in minutes. Probably setup teamviewer and I will just remote in and do my best.
wisenick said:
First: I'm not blaming anyone associated with the sunshine unlock method. This is definitely my fault.
I unlocked rooted my phone and stayed on 4.4.2 and just today I used the sunshine app to unlock my boot loader. I then flashed twrp recovery using the twrp app in the play store. Then I did a backup and then I tried to update the kernel and radio using this utility http://forum.xda-developers.com/moto-x/development/rom-stock-rooted-vzw-212-55-26-t2829123
It said that it worked but when I tried to boot up again it started a boot loop.
I tried manually flashing the 4.2.2 kernels again but that didn't work. Tried manually flashing the 4.4.4 ROM, didn't work. Tried flashing the 4.2.2 ROM, didn't work. Tried flashing 4.2.2 with rsd and it failed.
Now it's stuck in fastboot and won't boot into recovery or even try to boot, even if I try rebooting with adb.
I would love to keep root, but if I have to I'll do the root again if possible.
Click to expand...
Click to collapse

samwathegreat said:
Now execute the following commands in this exact order:
fastboot flash bootloader motoboot.img
fastboot flash partition gpt.bin
Click to expand...
Click to collapse
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.

jcase said:
...nothing to do with sunshine.
2) your title makes it sound like sunshine to blame...
Click to expand...
Click to collapse
That is what I first thought when I read the subject...
 @wisenick, you even mention in your OP you don't blame Sunshine, so why mention it in the subject?
Can you change the subject of this thread to "Attempted to Downgrade and now bricked" or "Attempted to downgrade and now phone wont boot"? That would be more accurate.

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Just checked the XML and it is gpt then bootloader. I'll see if that fixes things.

Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.

Verttex said:
Try flashing an alternate bootloader like TWRP or CWN with mfastboot. My recovery wasn't working for awhile and all I had to do was reflash it.
Click to expand...
Click to collapse
Thank you but I've tried that. It says that it flashed but when I try to boot into recovery it simply boots into fastboot

piccit said:
I don't have the sbf files handy right now, so I can't check -- are you sure the order is bootloader then gpt? I thought it was the other way around. A quick check of the xml file in the sbf will give the correct order.
Click to expand...
Click to collapse
Double checked the order and according to the xml , its gpt first. However I still get an error when I try to flash motoboot

Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
If Sunshine unlocked your bootloader, you should be able to do whatever.

wisenick said:
Well I couldn't handle not having a phone much longer so I used rsd to go to 4.4.4, have I lost root?
Click to expand...
Click to collapse
Yes you lost root! but
If you used sunshine, you turned your consumer phone into a developer phone, meaning you will always be able to root it trivially and properly.

True. if your back in android w/o root
Download Supersu in a zip file
boot to bootloader
fastboot flash new recovery
reboot into the new recovery
flash supersu zip
you have root! Easy w/ an unlocked bootloader!

Coverting Moto X 1097 Telus to Pure hab check failed

I'm trying to convert my Moto X 1097 to 1095 pure. When I try flashing files with mfastboot I get hab check failed for boot and hab check failed for recovery. It's running 4.4.4 pure but I assume still has old recovery as it won't boot into recovery. I have abd all and downloaded mfastboot v2. Why am I getting these errors? Bootloader unlocked.

Are you trying to flash 4.4.4 or 5.0?
Motoboot and gpt can never be downgraded, some files will always show they failed the hab check even though they are ok as they aren't the original files.
If you flash the entire 4.4.4 or 5.0 Pure firmware package you will have no radio at all and will need to use the original NON-HLOS.bin from the matching Telus package to get it back.
If you want to try the Pure 5.1 soak/leak then flash the full Pure 5.0 package and then apply the soak update via stock recovery. At that point your radios will work as the 5.1 soak appears to include a modem/radio that works with the XT1097.

Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple.

matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse

matt1515 said:
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Stop using the power button to try to select recovery like you would on a Nexus device - use the volume up button and you'll be fine

Hahah dang I feel dumb

So just to conclude if I did want to go back to fresh stock Telus. Would these [fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img still not work and not be needed? I understand motoboot is bootloader but what is got.bin?

If you go back to Telus firmware those two files likely won't update. I recommend you always go through the motions and if they fail it is fine to continue with the other files. When Telus 5.1 is released you will likely be able to update those two files again - it doesn't seem to really matter though with the 2014 Moto X.

Ok good information one question I have to ask. Does it really matter what fastboot I use and if so what is the best one to use for this phone?

Do you mean fastboot versus mfastboot(motorola specific version) ?
It only matters with the system image which is too large for regular fastboot and required the Motorola specific version which can handle the larger files and/or the sparse files.

Exactly the answer I was looking for. Thanks a lot!
Sent from my XT1095 using XDA Free mobile app

[Q] Unable to upgrade rooted Nexus 6 to 5.1.1

I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin

rambo8wtv said:
I have a rooted Nexus 6. When I look into the Settings>Aobout Phone I can see that the Build version is LMY47D. When I'm trying to udpate to LMY47Z I'm getting a notification in recovery that my current system version is 5.0.2. Did anybody had a simillar problem? Is there any way to fix this except for flashing factory image?
Thanks for any help!
Martin
Click to expand...
Click to collapse
no matter how many times you try, you will never ever be able to update your rooted n6 via ota. if any system files changed from stock, an ota will download but will always error out. you can update several ways.. a. you can flash a 5.1.1 ROM via twrp. or b. you can fastboot flash 5.1.1.

2 things.
1. You must be 100% stock, no root, no custom recovery to OTA
2. The 5.0.2 message if you look probably.mentions deestroy..this is.because TWRP is using 5.0.2 sources - butnits irrelevant anyway give point 1

I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
twrp can not flash the ota or system img. you flash the system img via fastboot(not adb) and while you're in your bootloader.

rambo8wtv said:
I know I can't do OTA. I have tried to install the file in TRWP and got the same error message. When I try to sideload with adb I'm getting device not connected error. Does this mean that I have to install the factory image?
Click to expand...
Click to collapse
You cannot use the OTA file no matter what vehicle you use.

danarama said:
You cannot use the OTA file no matter what vehicle you use.
Click to expand...
Click to collapse
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data

starfish_001 said:
I did this for 5.1.1 -people seem to be using 5.1.1 (For Sprint, USC ONLY) (LMY47Z)
take factory image - Unzip everything and keep the following images: bootloader, radio, boot, recovery and system.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
fully stock 5.1.1 without losing your data
Click to expand...
Click to collapse
He'll probably want to not flash recovery. And if he has a custom kernel, may not want to flash boot either.

Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.

rambo8wtv said:
Thanks for all the answers! Some sites clearly don't know anything about this as there's a lot of recommendation to use adb for all this. I'll have a go tomorrow! Thanks again.
Click to expand...
Click to collapse
here too, many people try it with adb then claim it doesn't work. but its fastboot that you need, and while you are in the bootloader. adb will never work in the bootloader, only fastboot.

[Q] Clarification on upgrading from 5.0 to 5.1

I have a unlocked bootloader US Moto X 2014 Pure Edition with stock recovery and currently non-rooted. No modifications to the system that I am aware of (NO XPOSED, ETC).
I went into SuperSu and did the complete unroot and rebooted and then tried to take the OTA and it was unsuccessful, as I figured it would be.
I am running System Version 22.21.11 victara_tmo.tmo.en.us and Build LXE22.46.11.
My question is this: I have requested the download for the 5.0 factory image from Motorola's website. Can I download it and then flash it with a similar process like I do with my Nexus 5 where I flash system, boot, bootloader, and radio and then take the 5.1 OTA? My goal is not to lose data or apps.
If I follow the commands on Motorola's website, am I going to lose data and apps? The commands would be:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot

Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.

inertiamonster said:
Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.
Click to expand...
Click to collapse
Thanks I'll try that! As far as flashing, I just follow Motorola's steps minus flashing cache.img and userdata.img and I should be fine right?

I also forgot to mention to make sure if the factory image comes with a flashing script be sure to check that it doesn't have a wipe command!!
Yes, since their method does not appear to use a script (based on what you pasted in the OP) you don't need to worry about it sending a wipe command or flashing images you don't want it to, just follow the manual flashing steps minus those two imgs if present.

I unrooted through Super Su and uninstalled BusyBox and it did not work. I guess I'll have to flash and then take the OTA to 5.1 when I get permission to download the factory image Maybe my root method was different from yours. I don't know.

Hmm, strange. Did you use CF-Auto to root? You rebooted after unrooting and removing BusyBox?

I honestly don't remember what I used to root. I'll reboot and try again and let you know what happens.

No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.

inertiamonster said:
I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
Click to expand...
Click to collapse
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?

Matthewlawson3 said:
No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.
Click to expand...
Click to collapse
I may have a problem. I made a mistake in the flashing sequence and accidently booted instead of flashed the boot.img. So I reloaded into the bootloader and continued the flashing and now when I rebooted it goes to the logo and then turns off. Help me!

I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.

Matthewlawson3 said:
I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.
Click to expand...
Click to collapse
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk

AGISCI said:
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thank you. I went ahead and just erased everything and upgraded to 5.0 by OTA then to 5.1 by OTA, but thanks again. I appreciate it.

onmyouji said:
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?
Click to expand...
Click to collapse
I removed BB and then unrooted and rebooted, not sure if the order matters but rebooting is a good idea to make sure root is gone.