TELUS Moto X (XT1097) doesn't boot after last OTA. Help! - X 2014 Q&A, Help & Troubleshooting

Hey guys,
I have rooted my Moto X 2014 (XT1097) with Chainfire auto root method about 6 months ago and I decided to accept the OTA update I got today from TELUS (22.121.11.en.CA). If I remember correctly I was on 5.0.1 before accepting this OTA.
Now the phone is stuck in the custom boot logo screen that I installed after rooting and even if I try to shut it down, it just boots up and gets stuck in the logo screen.
What should I do? I can access the bootup screen by holding power and volume down.

bobitza said:
What should I do?
Click to expand...
Click to collapse
Let me reply myself so that maybe others can use this info to fix their devices as well.
Step 1: You need to install the ADB platform tools (should be plenty of threads about that)
Step 2: You need to find a system.img and a boot.img to match your needs. I have a XT1097 with TELUS in Canada, so I have found this thread and downloaded the big .zip file (big thanks to Steve-x!). For US people the graffixnyc site has images for XT1095 that you can use. Move those .img files where your fastboot.exe file is found
Step 3: Boot your device in bootloader mode (hold power and volume down) and connect it to your PC
Step 4: Install the images with the fastboot command by typing this in a cmd window
fastboot flash boot boot.img
fastboot flash system system.img
Click to expand...
Click to collapse
Or in the case of the TELUS image, the system image is split into 7 files ... just flash system them one after the other. Steve mentioned something about the recovery.img, but wasn't sure how to flash that so I did it this way.
Step 5: (Optional) If you had something else installed you will get some errors, here's how to fix them. Boot back in the bootloader and choose Recovery, then when you see the screen with the "sick" Android, keep Power pressed and tap on Vol Up to enter Recovery Menu. Choose to delete data and delete cache. Reboot.
If you used Steve's image you should be booting into TELUS Android 5.0.1, just before the cursed update. You can even do now the 5.0.1+ update OTA. You're back in stock ROMs world

Glad you got it fired up again. I haven't taken the OTA yet myself with my Moto X's, was hoping to get the entire image with Motorola Device Manager.

Le sigh
Man i'm having nothing but issues. I've done everything that i was supposed to do, but i cant get the files to load.

Related

[Q] Bricked Phone

Hi,
I recently got asked by a friend to flash his google nexus one phone. like a mug i said yes and now i have a issue where it turns on, vibrates 7 times and stays at the splash screen with the x on it. I can boot into the fast boot / recovery mode but nothing works.
this happened after i tried to root the phone, it said waiting for device and didnt do anything so i killed the app (Superoneclick) the phone disappeared from device manager and now wont go past the splash screen.
Does anyone have any idea how i can get it back? .. thanks in advance for any help.
James
I'm guessing, since you used S-O-C, the bootloader is not unlocked. The only way I know how to fix it is if you OEM unlock it. You'll need fastboot and your Android SDK setup correctly.
Once you have the setup done, change directories to the tools folder, wherever you put your sdk. Boot your phone into fastboot by holding the trackball while powering it on.
Code:
cd C:\asdk\tools\
Plug your phone into USB, and check if the computer sees it
Code:
fastboot devices
Unlock the bootloader (THERE IS NO GOING BACK! You can never re-lock a Nexus)
Code:
fastboot oem unlock
Now you can flash a boot.img and system.img (preferably pre-rooted) from fastboot, and it should boot normally. If the phone boots, the phone is perma-rooted, and won't need any other rooting procedure (you just need to flash a rooted rom). Next time, be a little more careful
Hi wdfowty
at running the risk of asking for more help and making you cross could you post some links to these downloads?
I am a total newbie to these phones and want to make sure i have the right apps.
thanks again for the help and the quick response... and if i manage to get this phone back believe me it will be the last one i try to flash !!
cheers
James
Nah, you've got me wrong. I'm all about helping people that are willing and able to be helped.
Follow this guide, it'll walk you through the steps to set up your sdk and unlock the bootloader. The guide is a little dated, so the info might not be 100%, but it's generally everything you'll need to know. If you get stuck, feel free to ask.
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
jamesabennett said:
Hi again,
when i run the command fastboot devices i get an error AdbWinApi.dll is missing.
it tells me to reinstall the app but i have done that and also run all the updates and i still get the same error?
Interstingly i also get the phone to fastboot and it says in red text on the phone fastboot.usb but i cant see anything in device manager that says Nexus one etc?
any more help appreciated.... worst case you dont fancy a christmas break over in England do you?
cheers
james
Click to expand...
Click to collapse
With the latest version of the SDK tools, they changed the directory for adb and fastboot. Unfortunately I'm not on my Windows machine... but check in the directory where you have the SDK extracted to and look for a platform-tools directory (iirc). From there, you should see fastboot.
So basically where it says this "Type: cd C:\android-sdk-windows\tools" change it to "C:\android-sdk-windows\platform-tools". Keep in mind that directory name may change... again, I'm not on my Windows machine right now.
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
jamesabennett said:
Hi again,
thanks for the continued help. I have managed to get past that, i have OEM unlocked the phone and managed to copy the flash image to the device using the commands in the link you sent me.
problem i have now is when i go into recovery the phone again just pulls up the splash screen and vibrates 7 times.
i believe what should happen according to the link is to follow the 6 steps below.. even i can do that, but the phone doesnt get that far
//Turn phone off -> Hold Volume Down, hold Power button
//Press Volume Down to highlight Recovery -> press Power to select Recovery
//Backup/Restore -> Nand backup
//Wipe -> Wipe data/factory reset
//Wipe -> Dalvik Cache
//Flash zip from sdcard -> alpha-r##-update-modacocustomrom-nexusone-desire-withadditions-signed.zip (Or whatever other ROM you're using.)
another point is it runs a couple of lines of blue txt relating to the sd card, but it flashes up and dissapears too quickly for me to be able to read it and send across to you.
thanks again and if you can work this out i owe you a beer !!
James
Click to expand...
Click to collapse
Have you flashed the recovery image using fastboot, or did you only copy the recover image to the sdcard? Step IV in that guide.
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
I ran the fastboot command and used the flash image ending 2.0.0
this is driving me round the bend !!
What happened when you used the fastboot flash command? Did you see a bar on the top right of the phone?
wdfowty said:
It sounds like you need to reinstall your recovery.
Download the recovery found here: http://forum.xda-developers.com/showthread.php?t=611829
Rename that file to recovery.img and place it somewhere you can remember
Boot the phone into fastboot by holding down the trackball and pressing power button.
Code:
fastboot devices
Code:
fastboot flash recovery C:\path\to\recovery.img
If all went well, there should be no errors. On the phone, use the volume keys to select "Bootloader". It will take you to a white screen with the blue text (ignore it, it's looking for update files like "PASSIMG.zip"). Select recovery, and it'll boot into recovery. If you see menu items, you are good!
Click to expand...
Click to collapse
i do that and it accepts the recovery file and the progress bar goes up on the right hand side and the cmd prompt says its all good. then when i select recovery the phone goes to the black background with the four coloured cross and the unlocked padlock, vibrates 7 times and just hangs on that screen
beleive it or not it booted up a moment ago and the phone worked like it did before with v2.2 on it. so i am happy now it can be recovered... i just dont know what to do to straighten it out!
yes. the bar goes up on the right hand side of the phone. and i have definitely unlocked it as it now says unlocked at the top of the menu.
Have you tried to reimage the phone with the passimg method? Directions are provided in the wiki, under the unlock/restore heading:
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Follow PASSIMG method (filename is case sensitive).
The link to the files is on the word "here" on step 2.
Use FRG33.
Sent from my Nexus One using XDA App

[Q&A] [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition

Q&A for [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition
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:
MotoX Pure - UnRoot To Update Firmware
I used the Jcase method (fastboot boot pure2014sb.img) to root my new MotoX Pure. Worked great. However, the next day I received a notification on the phone that a firmware update is available: "New FIrmware Available" "Update to get the lastest Motorola Sensor. . ."
Because this method uses fastboot boot vs fastboot flash, I don't understand how I can go back to stock in order to update firmware.
Wondering if someone could school me on what the heck it actually means to fastboot boot vs fastboot flash. Basically looking for a way to be able to un-root, apply firmware update, and then re-root.
A
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
tyea said:
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
if they said they would, then i'm glad. getting worried here lol
root moto x 2014 followed by ota lollipop update
The moto x is delivered with KitKat initially and then updated via ota later once powered up etc. If I follow your method as soon as I get the phone and then later accept the ota update to lollipop, will it cause problems or lose root?
bootloop
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
deelv said:
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
Click to expand...
Click to collapse
The same thing happened to me but I've gotten out of the boot loop by getting to fastboot (hold down the power button till the screen turns off and then you have to guess and hold the power and volume down button for about 5 seconds and then release the power button but hold down the volume button until you see the fastboot. If it doesn't get to fastboot try it again.)
When you're at the fastboot, connect to a computer and cmd a command "fastboot erase userdata" and then "fastboot erase cache" to pretty much factory reset and get you out of the boot loop. Then it should boot and tell you to set up the device.
I would recommend looking for the root boot image from chainfire them self, they recently released it. Just look for your model # (e.g. xt1095) and "fastboot boot (insert boot image)"
My Moto x 2014 is currently rooted with chainfire's boot image. It works like a charm.
XT1092 bootloop after OTA
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
HamRack said:
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
Click to expand...
Click to collapse
Boot this boot.img : http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Its for xt1095 but some have confirmed working on xt1092
Sent from my Moto X 2014 Pure Edition
does it work on Android 5.0?
Yes, I'm currently running Android 5.0 Lollipop.
Sent from my Moto X 2014 Pure Edition
Bootloop
Stuck in a bootloop. Followed all your instructions carefully. :/ Not able to boot into bootloader.
Formatted Telus Moto X (2014) SD card and all data ... recovered.
I might make a tutorial video on how to recover from a mistake like mine, and I may not have done it correctly, but the phone is back operational.
What I did to screw it up :
1) Unlocked the bootloader and installed TWRP without doing research about development for the phone
2) The phone is already almost stock android and that's one of it's selling points so I don't know why I wanted to unlock and root
3) Got frustrated and wiped / formatted internal SD ... since I use to flash ROM's on my older Huawei this way ... it must be the same right ... smh.
4) Freaked the eff out, had thoughts of just running it over with the car because that qualifies under my 2-year warranty, since I voided it by unlocking.
5) Thought I knew it all when I really don't understand most of the lingo still
What I did to 'TRY' to fix it :
1) Scoured the internet for ROMS / Zips.
2) I was in 'Android Studio' ... unnecessary.
3) Tried flashing .zips in TWRP by draggin and dropping .zips ... contanst 'FAILED' signs.
4) Tried sideloading as I was grasping at straws by this point. 'FAILED'
5) Considered buying an OTG cable.
6) Spent hours going in circles
What I did to fix it :
1) Downloaded the SDK ... 'adt-bundle-windows-x86_64-20140702'
2) Installed the 'Google USB drivers' as I checked 'Device Manager' and there was an exclamation ... this is why when I went typed 'ADB devices' nothing showed up. I 'manually' installed the drivers. VOILA, first step.
3) Found a .ZIP file I believe was the correct one ... ;RETCA_XT1097_4.4.4_KXE21.187-42_cid14_CFC.xml.zip' (From this website I believe)
4) Watched a few youtube tutorials on how to flash from within 'SDK' > 'Platform-Tools'
5) Extracted the .ZIP file into 'Platform-Tools'
6) Had phone booted into fastboot mode
7) Opened the CMD from within 'Platform-Tools' with that .ZIP file within that folder, held 'SHIFT' 'Right-click" > 'Run CMD'
8) This is where I didn't do it properly, but the phone is booted for now and working ... with these Commands
- fastboot flash boot boot.img;
- fastboot.exe flash system system.img_sparsechunk.0
- fastboot.exe flash system system.img_sparsechunk.1
- fastboot.exe flash system system.img_sparsechunk.2
- fastboot.exe flash system system.img_sparsechunk.3
- fastboot.exe flash system system.img_sparsechunk.4
Got that nice Motorola earth screen and booted to the welcome screen. Froze. I reset. Froze. Walked away from phone, came back and tried to see if I could press 'OK' and it worked.
All-in-All , not worth it for the average consumer and not worth it for someone such as myself who was stupid and just wanted to 'play around' with a brand new 2-year warrantied $500 phone.

In need of xt1060 dev 4.4.4 sbf

So here is what happened...
my phone was running krypton 1.4.1 (4.4.4) rom. i decided to try a cm12 rom. the cm12 rom was bootlooping so i decided to go back and restore a nandroid. however my phone was encrypted on the 4.4.4 rom and when i went back into twrp and it asked for my password before the nandroid, it said wrong password. i was basically locked out and couldnt nandroid restore.
i then did some readying to try to push the rom adb but that wouldnt work. so i did a user erasedata to get rid of the encryption (it worked). so then i tried multiple different things for adb and fastboot to try to fix it. my device would not show up in adb so i tried to reinstall drivers. they installed but my phone will still not show in adb.
at this point it just bootloops at the twrp screen or i can just have it sit at bootloader....
does anyone have the xt1060 4.4.4 sbf? all the links do not have it anymore.
thanks
Check Motorola's website
Skeetch79 said:
Check Motorola's website
Click to expand...
Click to collapse
they dont have the sbf. i downloaded the whole zip from them already. they just have the file for adb. i cannot get adb working since phone is messed
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf
Skeetch79 said:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images download the right one for your device and use this to sbf
Click to expand...
Click to collapse
oh ok this is what i downloaded from them. i didnt see an sbf file in it though. is the whole package considered the sbf?
I think this is only OTA, but it's the only thing I could find..
http://motofirmware.center/files/file/151-vzw-xt1060-444-kxa2112-l126-cfc-1ffxmlzip/
I'm sure someone has a copy of the SBF that they had downloaded somewhere.
Also refer here: http://www.droidrzr.com/index.php?/topic/61124-House-of-Moto-[4.1]
Use the link to the zip file and the above link to restore your device
Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/
the problem i have is adb wont detect my device. i think it was because when i flashed cm12 i was not able to boot it up and select debugging even tho i have the drivers installed
fury683 said:
Those might be FXZ, but this one appears to have FXZ files too, which should be flashable with RSD Lite: http://www.drdevs.com/devs/FXZ-files/XT1060 (Moto X VZW)/
Click to expand...
Click to collapse
thanks i got it downloaded. rsd lite wont detect my device though. either will adb.
@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd
Skeetch79 said:
@sruel3216 Isn't the flashing done through fastboot? Mabually Power off device and the hold power button and volume down for 4 seconds then release both! Connect device while in fast boot to pc.
Once is fast boot and successfully connected to pc with drivers installed and device recognized then start flashing with rsd
Click to expand...
Click to collapse
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...
sruel3216 said:
thats whats not working. it wont recognize there is a device through fastboot or adb. it was working today and then once i tried to restore back through twrp it would not let me becuase i needed my password since my phone is encypted. i entered my password and twrp said it was wrong. so people told me to do a user erasedata through adb. it got rid of the encryption but now my phone just bootloops at twrp screen and adb or fastboot or rsd lite cannot see my device...
Click to expand...
Click to collapse
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
All i can get to is bootloader. however adb and fastboot will not detect my phone is plugged in even when i power off and hold down volume + power.
I cant really get to twrp. all it does is bootloop at the twrp splash screen
I have all drivers, sdk, etc installed on my comp and it worked earlier that day. once i went back from 5.0 rom to 4.4.4 rom, the encryption i had on my phone got all messed up and it got screwed up from there
KidJoe said:
If Fastboot and RSDLite wont see your phone, you can not flash an SBF.
If your phone boots to TWRP, it should be capable of booting to fastboot mode. Under the REBOOT option in TWRP is BOOTLOADER. What happens when you try it?
Or... can you power your phone off? (if it doesn't respond to normal attempts to power off, press and hold the power button until it does.) Then without any cable connected to your phone, press/hold the power and volume down buttons simultaneously.
If you can get your phone to the AP Fastboot (aka Bootloader) screen, then visit -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and use option 5 (skipping step 2,3 and 4, since you've done them if you can see the Fastboot screen)
And to revisit an earlier part of this thread....
SBF, FXZ, Recovery Image, today all mean pretty much the same thing. What Moto has as "Recovery images" at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images are just that. They are the FULL ROM Images used to fully flash a phone. Call them SBF, FXZ or Recovery, its the same thing.
In the past, Moto did include an XML in the Recovery Image ZIP file for the 1St Gen Moto X that could be used with RSDLite to flash. With the 4.4.4 Recovery Images, Moto instead included only a BAT file to flash via mFast boot, and does NOT include an XML. If you want to flash via RSDLite, you either need to make your own XML, borrow the one included in the 4.4.2 image, or download the SBF from another source that had created the XML and included it.
Click to expand...
Click to collapse
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition
sruel3216 said:
OMG sir i think you may have saved me!
EDIT: It has booted!!! thank you sir! Will i need to unlock my bootloader again? it is a dev edition
Click to expand...
Click to collapse
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.
KidJoe said:
If you got the unlock code from Moto and used it to unlock your bootloader, then no. You will not need to unlock again. Once the bootloader is unlocked, it will stay unlocked unless YOU relock it (fastboot oem lock), even then, if you have the code from Moto, you could unlock again if you needed to.
If you used a tool like Sunshine to unlock the boootloader, my understanding is that the bootloader will also stay unlocked. However, if you relock it, you wont be able to unlock it again.
Click to expand...
Click to collapse
Sweet got it all rooted again and running. thanks a lot!

Took OTA with custom recovery

Hi all, I did a dumb thing and I took the recent Verizon OTA on my dev ed moto x with a custom recovery installed (TWRP).
Now my phone seems to always stop booting at recovery, then if i hit 'reboot system' from recovery, I can get into my system for about 2-3 minutes, and then it reboots to recovery again.
Any help would be greatly appreciated!
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
KidJoe said:
boot your phone into fastboot/bootloader mode, then flash stock Recovery on your phone and reboot normally.
Click to expand...
Click to collapse
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
switch81 said:
Thanks KidJoe - I'm reading through your post on xda right now to see how you flash back to the stock recovery and I'm currently downloading the stock image from one of your links.
While I'm waiting, I'm going over my options for how to actually flash the stock recovery - your post said that i should try Rashr - however my device probably won't stay 'on' long enough for me to get through that process. After it boots into the system (e.g. I see my launcher and apps), it wants to restart since I guess it's trying to the upgrade. So I'm thinking of instead using adb to flash the recovery.img file. Is that the right path to take?
Also - would it be okay to use adb to flash the recovery.img using TWRP's adb sideload feature? I seem to be able to connect using adb that way, but for some reason 'adb devices' doesn't list anything under fastboot.
Click to expand...
Click to collapse
First, if you can't boot your phone into Android, you can't use Rashr.
Next... ADB needs you to be up in Android, and have the "USB Debugging" options checked. Also, it can not be used to flash the components of the SBF/ROM like recovery.img.
Fastboot mode works with Fastboot.exe or mFastboot.exe... ADB commands do not work when the phone is in fastboot mode.
Here is what you want to do AFTER you have the stock reocvery.img you want to flash... (this is pretty much exactly what you did to flash TWRP on there in the first place, except you will be flashing a stock recovery.img instead)
have the latest Moto drivers installed. You can get them from -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Make sure you have the Android SDK/Platform Tools installed (don't know how, see -> http://mark.cdmaforums.com/ADB.htm )
You need the latest version of Moto's fastboot, and it needs to be put in your windows Path (there are steps on -> http://mark.cdmaforums.com/ADB.htm )
Once you have that... do the following...
Unplug phone
Power down phone.
Hold Volume Down and Power
After a few seconds release Power, you should be in fastboot menu on phone.
Connect to PC.
open command prompt file and change to the folder you have your recovery.img you want to flash
type the following, pressing enter after each command, and wait for it to finish before going onto the next...
mfastboot flash recovery recovery.img
mfastboot reboot-bootloader
The device will display different BOOT OPTIONS
Use the VOL DOWN Key to SCROLL to Recovery and VOL UP Key to select
The device will display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key
You should enter STOCK recovery.
use the VOL DOWN Key to scroll and the POWER Key to select reboot.
The phone should reboot and and be ready for the update
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
I'm sure KidJoe will respond, but I found this thread of his very useful:
http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
switch81 said:
Thanks! I'm back up and running!
Sorry for the confusion on the adb vs fastboot stuff - I always mix those kinds of things up since I do it once ages ago to get myself into this mess, then I forget how I did it and what tools I used.
So basically what I did was use fastboot like you said and first booted into fastboot, then did a 'fastboot flash recovery recovery.img' from a stock recovery.
After a full reboot, android ended up giving me a 'update was unsuccessful' which I am totally 100% okay with. I ended pushing 'update' the first time really because I was tired of getting nagged - this time i just said 'don't install' and hopefully it won't bother me agian.
Thanks again!
Click to expand...
Click to collapse
I was able to flash back to stock recovery and take the 212.166.3 build KXA21.12-L1.26-3 (which is still 4.4.4) OTA that Verizon is pushing out.
I didn't even have to disable Xposed or anything else. Then again, other than Xposed, root and twrp, I'm running stock. No tethering hacks, build.prop changes, no system files removed or renamed, etc.
---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------
slynke said:
I did the same thing and was able to undo it by clearing the cache. Now I'm back to where I was before, with the constant notification to update.
Wondering what the correct way to go about updating is..
*Edit: Thanks!
Moto X Dev
Click to expand...
Click to collapse
Yup., Clearing cache will delete the OTA ZIP file that was downloaded. So the next time you reboot, it wont try to install, instead you'll be back to being notified that an update is available asking you if you want to download it.
But yup, those instructions I just typed should work...
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
switch81 said:
This OTA seems so minimal in changes, any suggestions/recommendations if I should take it at all?
I'm also pretty much stock now as well - only root, xposed installed.
Click to expand...
Click to collapse
The release notes on VZW's page only seems to mention bug fixes.. no real details.
So far I haven't noticed any changes.
It will likely be a required step to get to lollipop. So either take it now, or wait and take it later, just before you upgrade to Lolliop

I have been trying to root my metro Moto e5 plus

I was successful in getting the bootloader installed and also twrp but SU and Magisk kept giving error, somehow in the last boot I am now on a boot loop of bad key cannot boot to OS of phone and the backup of the OS will restore but it still will not boot past the bad key loop. I can get to the twrp recovery and the bootloader but no functions work in bootloader twrp works flwlessly but I have no image for my device. Does anyone have the stock rom for the metro verision of moto e5 plus. I have found one for the Cricket version but specs are all wrong. Any help would be appreciated
edit resolved with
cant post link to resolution
archnemesis2099 said:
I was successful in getting the bootloader installed and also twrp but SU and Magisk kept giving error, somehow in the last boot I am now on a boot loop of bad key cannot boot to OS of phone and the backup of the OS will restore but it still will not boot past the bad key loop. I can get to the twrp recovery and the bootloader but no functions work in bootloader twrp works flwlessly but I have no image for my device. Does anyone have the stock rom for the metro verision of moto e5 plus. I have found one for the Cricket version but specs are all wrong. Any help would be appreciated
edit resolved with
cant post link to resolution
Click to expand...
Click to collapse
Hey, even if you can't post a link to the resolution I'd love to have more info! Please either PM me or post a tut, since this looks to be a bit problematic and I'm gonna jump on a freebie from MetroPCS.
Would really appreciate it thx!
Those of you who seek root on the MetroPCS Moto E5 play, I got you
I was working on a simple, straight forward walk through. Maybe just pm me for the details. Would be easier to do it that way being as I'm currently @ work. I can't figure out how to post a pic directly from my Moto E, but if you pm, I'll send you some verification. I soft bricked mine 3 times trying to get it figured out. You know what they say though. 3rd time is the charm. PS, don't flash anything other than recovery!!! The no-verity will cause you to boot loop.
Walkthrough
Okay so here goes keep in mind I cannot post links so mentions of the downloads will be just that, only mentions. The method I used to resinall the os is below. Keep in mind I still had access to both the boot loader and TWRP and that prior to my boot loop no os error I did have developer options and both usb debugging and oem unlock on
How To install Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo OS
Before you begin, it is important to have all the tools at hand. you will need:
Recharge your phone’s battery well(with more than 70% battery)
Save all your personal data (SMS, contacts, applications, settings, documents, music, photos, etc.)
install Motorola USB drivers,SDK drivers
Download Motorola Moto E5 Plus XT1924-# variant stock firmware
ENABLE USB DEBUGGING:
1. Go to Settings> About phone
2. Find the Build number and press 8 times on it:
3. Return to the previous screen. You will see that a line has appeared: “Developers Options”
4. Press and check “USB Debugging” & “OEM unlocking”
Procedure I used to reinstall OS starts below keep in mind I cannot post links as such you will need to google your phones product/variant to find the correct file, in the case of both the ATT and Metro/Tmobile version of the E5 Plus that is Hanna XT1924-7 and is visible in the bootloader.
Update Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo
1- Open the folder where ADB and Fastboot are located on your computer & Unzip the downloaded zip file in it preferably in its own directory.
2- In an empty area inside of the unzipped file directory hold down the shift key and right-click with the mouse, the context menu will contain an entry Open command window here:
3- Restart your Moto E5 Plus XT1924 in Recovery mode:
Press & hold the “Volume Down + Power button” at the same time for about 5 seconds
The device enters on Bootloader mode.
4- Connect your Moto E5 Plus XT1924 to your computer
5- Verify that the phone is recognized in Fastboot mode: Type in the command: “fastboot devices”
6- To Install Moto E5 Plus XT1924 Android 8.0 Oreo OTA, Type the following commands removing any bin, img, and sparsechunk commands that don't match your download. The Flash process might take about 25 minutes to complete.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
fastboot flash system_b system_b.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.# (do this for each numbered variant normally starting with 0)
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Click to expand...
Click to collapse
7- Once the update process finishes, reboot Moto E5 Plus XT1924 by selected Reboot system now.
8- You have successfully installed Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo OS
archnemesis2099 said:
Okay so here goes keep in mind I cannot post links so mentions of the downloads will be just that, only mentions. The method I used to resinall the os is below. Keep in mind I still had access to both the boot loader and TWRP and that prior to my boot loop no os error I did have developer options and both usb debugging and oem unlock on
How To install Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo OS
Before you begin, it is important to have all the tools at hand. you will need:
Recharge your phone’s battery well(with more than 70% battery)
Save all your personal data (SMS, contacts, applications, settings, documents, music, photos, etc.)
install Motorola USB drivers,SDK drivers
Download Motorola Moto E5 Plus XT1924-# variant stock firmware
ENABLE USB DEBUGGING:
1. Go to Settings> About phone
2. Find the Build number and press 8 times on it:
3. Return to the previous screen. You will see that a line has appeared: “Developers Options”
4. Press and check “USB Debugging” & “OEM unlocking”
Procedure I used to reinstall OS starts below keep in mind I cannot post links as such you will need to google your phones product/variant to find the correct file, in the case of both the ATT and Metro/Tmobile version of the E5 Plus that is Hanna XT1924-7 and is visible in the bootloader.
Update Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo
1- Open the folder where ADB and Fastboot are located on your computer & Unzip the downloaded zip file in it preferably in its own directory.
2- In an empty area inside of the unzipped file directory hold down the shift key and right-click with the mouse, the context menu will contain an entry Open command window here:
3- Restart your Moto E5 Plus XT1924 in Recovery mode:
Press & hold the “Volume Down + Power button” at the same time for about 5 seconds
The device enters on Bootloader mode.
4- Connect your Moto E5 Plus XT1924 to your computer
5- Verify that the phone is recognized in Fastboot mode: Type in the command: “fastboot devices”
6- To Install Moto E5 Plus XT1924 Android 8.0 Oreo OTA, Type the following commands removing any bin, img, and sparsechunk commands that don't match your download. The Flash process might take about 25 minutes to complete.
7- Once the update process finishes, reboot Moto E5 Plus XT1924 by selected Reboot system now.
8- You have successfully installed Motorola Moto E5 Plus XT1924 Android 8.0.0 Oreo OS
Click to expand...
Click to collapse
so i have the very exact issue as the OP, i tried this step, all i got was a error after using fastboot, doing the whole command in the cmd window, once it was done i got a endless moto start up icon, i rebooted, it kept giving me the " bad key" blank black page, then N/A, i booted back to twrp wiped and cleaned data to try again, then this time when i tried again i every command was met with errors saying " downgrade verifaction, or something like that, each line was basiclly and error. wont let me try to do the stock install again... im kinda at a lost end here.
stock187 said:
so i have the very exact issue as the OP, i tried this step, all i got was a error after using fastboot, doing the whole command in the cmd window, once it was done i got a endless moto start up icon, i rebooted, it kept giving me the " bad key" blank black page, then N/A, i booted back to twrp wiped and cleaned data to try again, then this time when i tried again i every command was met with errors saying " downgrade verifaction, or something like that, each line was basiclly and error. wont let me try to do the stock install again... im kinda at a lost end here.
Click to expand...
Click to collapse
People don't really tell you how to fix the issue so if you still need help getting your phone back to normal
I will help
Every post I have tried has been flawed or wrong or won't work
Sometimes people just post **** and don't think
PM me, i'll help you as well if you need it. What you have to do is download a platform tools folder and extract it because you need to open it and open up a command prompt within the platform tools folder for the restoration of the phone's stock ROM can be successfully flashed on the phone. I have everything you need to get your phone back operational again. I'll even help you root it successfully if you need more help, and i'll help you decrypt it. there's even a successful custom ROM that i'm using now that's better than the others since the others have so many problems booting up or issues within the ROM itself.
Moto e5 play root
Lord_Worm said:
I was working on a simple, straight forward walk through. Maybe just pm me for the details. Would be easier to do it that way being as I'm currently @ work. I can't figure out how to post a pic directly from my Moto E, but if you pm, I'll send you some verification. I soft bricked mine 3 times trying to get it figured out. You know what they say though. 3rd time is the charm. PS, don't flash anything other than recovery!!! The no-verity will cause you to boot loop.
Click to expand...
Click to collapse
I interested in rooting my metroPCS Moto e5 play but I don't really know what to do & I don't want to end up using a rooting program that will mess up my phone or not have at least a little knowledge of what I'm doing. Your post was the first one I came across and I was wondering if you might be able to help me with a little bit of knowledge. Please & thank you, I'd really appreciate it...
TalkNerdy2Me said:
I interested in rooting my metroPCS Moto e5 play but I don't really know what to do & I don't want to end up using a rooting program that will mess up my phone or not have at least a little knowledge of what I'm doing. Your post was the first one I came across and I was wondering if you might be able to help me with a little bit of knowledge. Please & thank you, I'd really appreciate it...
Click to expand...
Click to collapse
Shoot me a private message and I'll walk you through it
dominoeflux said:
PM me, i'll help you as well if you need it. What you have to do is download a platform tools folder and extract it because you need to open it and open up a command prompt within the platform tools folder for the restoration of the phone's stock ROM can be successfully flashed on the phone. I have everything you need to get your phone back operational again. I'll even help you root it successfully if you need more help, and i'll help you decrypt it. there's even a successful custom ROM that i'm using now that's better than the others since the others have so many problems booting up or issues within the ROM itself.
Click to expand...
Click to collapse
If you could help me out with rooting my moto e5 plus I would be grateful I have a question though my baseband version says M8940TMO_32.22.11.69R
HANNAH_NA_TMO_CUST and the Official TWRP app says my device is Hannah so do I use the James varient or the Hannah one is the plus and one is the play correct? Thank you for any help you might be able to give me.
toscrewed2matter said:
If you could help me out with rooting my moto e5 plus I would be grateful I have a question though my baseband version says M8940TMO_32.22.11.69R
HANNAH_NA_TMO_CUST and the Official TWRP app says my device is Hannah so do I use the James varient or the Hannah one is the plus and one is the play correct? Thank you for any help you might be able to give me.
Click to expand...
Click to collapse
yes, the plus is hannah and the regular e5 is the play...you have the hannah version.
None of this helps me. I unlocked the bootloader tried to install magisk or supersu, but it keeps bootlooping to n/a. I can only get into bootloader and from there to TWRP. That's it. I do have adb access...
Sent from my SM-G955U1 using Tapatalk

Categories

Resources