Database Develop

[Q] Bricked my Moto X - can I resurrect it?

My Moto X now refuses to boot. With stock recovery it'll get past the bootloader, then blink an image of a dead android with the message "Error" briefly, and keep doing so every ~10 seconds. If I flash TWRP, any attempt to boot takes me to TWRP, with log messages reading "unable to mount..." for a bunch of partitions (/data, /cache, storage, etc.)
Can I recover my device?
The short sequence of events: I rooted my phone (T-Mobile phone, unlocked it via Motorola's website) and installed TWRP. Later I tried to accept the 4.4.2 OTA update, but the phone wouldn't take the update, because TWRP. Flashed stock recovery tried again, got stuck in bootloop. Tried flashing back the 4.4 / 140.44.3 images from here, now I'm stuck with a blinking error message.
I see there are a bunch of image files bundled into the 4.4.2 / 161.44.25 update - would flashing those do any good?

What version is your bootloader?

Steve-x said:
What version is your bootloader?
Click to expand...
Click to collapse
Version 30.B2.

OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!

Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Fast boot erase cache should work . its trying to flash the it's ,so you need to delete the cache where the ota file downloaded to
Sent on my Gummy running Lenoto X

so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
that is the file you need to flash with RSD Lite or Fastboot and it should get you 100% back up and running.
But then if you want to go to 4.4.2 after you flash the firmware before you add anything or install TWRP just update the phone to 4.4.2 then install the custom recovery and SuperSU.

Steve-x said:
OK, you still have the 4.4 bootloader so you should have no problem flashing the full tmobile/retail/dev edition build of firmware. I'd perform a full flash with rsdlite or with fastboot using all of the commands in the xml file in the same order. Do not skip any files or bypass any files if there are errors.
This will reset your phone and wipe all content!
Click to expand...
Click to collapse
I have tried both RSD Lite, and applying all of the commands from the XML file manually, following the directions from here. Both ways, I still get the blinking error message

The "can't mount..." log messages I get if I flash back to TWRP suggest it could be some sort of partitioning problem, but I'm not sure how to diagnose that.

And the flashing of all files completes successfully?

Steve-x said:
And the flashing of all files completes successfully?
Click to expand...
Click to collapse
I could have sworn that I wasn't getting any errors previously. Now, however, after trying to flash system.img (making sure to use mfastboot, of course), I get an error on the phone, "sp space is not enough". Not sure what it means, and Googling around doesn't turn up any answers.

dray_jr said:
so here is abit more help here are the full firmware links
T-Mobile 4.4
http://sbf.droid-developers.org/download.php?device=0&file=2
Click to expand...
Click to collapse
Yep, that's exactly what I flashed. Made sure the md5sum matched my download and everything.
flashallthetime said:
Did you attempt to clear dalvik and cache, I believe you can do it through fastboot
Click to expand...
Click to collapse
Yep, cleared the cache, no luck

Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.

So I guess more warnings into my noobs guide to accept an ota thread
Maybe I should put a notice not to accept the ota and only flash your carriers sbf firmware when available?
Sent on my Gummy running Lenoto X

Steve-x said:
Ouch, it does kind of sound like the partition table got damaged. I suppose you could try "fastboot erase system" and then try to flash the system partition again.
Click to expand...
Click to collapse
Code:
C:\Users\spiffytech\Documents\sdk\platform-tools>fastboot erase system
(bootloader) Variable not supported!
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.101s

Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.

spiffytech said:
Well, that was very weird. In the bootloader I scrolled through the menu and accidentally selected "Factory". No idea what that's supposed to do, but now my phone boots again! I'm going to really, really, hope I don't break it again...
I want to try the 4.4.2 update now, but given I'm not really sure why my device works again I'm scared to.
Click to expand...
Click to collapse
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X

flashallthetime said:
Good for you, I would wait for the sbf firmware to be available to flash, seems to me a safer way of getting the update
Sent on my Gummy running Lenoto X
Click to expand...
Click to collapse
I'll go with that plan What is it that makes flashing from sbf safer?

So if you perform a full factory reset the phone will boot up normally now? If that is the case then I don't see any problem with accepting the OTA to 4.4.2.

Help PLZ
I had the exact same problem as OP, took the same course of action, and got a successful boot. I do some minimal stuff, check if everything is working, turn on dev mode, etc. I put in my wifi password.
I wanted to check if my bootloader was back to stock, so I turned off my device, and then tried to power on. Pressing the power button does nothing.
So I get into fastboot, and select factory (reset) again. It boots up, but it doesn't seem like it actually did a factory reset, because it automatically connected to my wifi..
Have you any idea what's going on, and how perhaps to solve this weird dilemna?
EDIT: I'm not sure if I actually did anything, but after a couple reboots it just started working normally. I installed the update to 4.4.2 and everything is smooth thus far.

Eventually the phone prompted me to apply the 4.4.2 update so often the phone was actually unusable - it'd go back to the "do you want to update?" screen as soon as I backed out of it. I was thus forced to apply it OTA. Fortunately, the update went through fine this time, and my phone continues to work fine
Thanks for your help, folks!

[Q] I done screwed up big time - the mystery of the unflashable recovery

Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.4.2, TWRP 2.7.0.0 recovery
Objective: wipe everything and flash back to a (rooted) stock for device retail
Why I'm screwed: everything is wiped - phone has no OS, recovery, etc. It simply hangs out on the Motorola M at boot and doesn't move. fastboot loads and will flash recovery (seemingly successfully) but rebooting to recovery always gets stuck at the logo
How I got there:
1. Backed up with TWRP, then flashed new recovery CWM (the one here) and backed up again. Saved both folders of nandroid backups to my PC (yay)
2. Flashed back to TWRP (but this time the new one v2.8.0.1 here, which I downloaded and flashed via that fancy new TWRP app [I selected the "ghost" model]) clicked about every type of wipe option I could get my grubby little fingers on, then adb pushed the ROM and kernel/radio combo from here.
3. Attempted to flash the new ROM via TWRP. It failed. something about an "Error executing updater binary in zip". I sighed, said "meh", googled the problem a bit and figured I'd reboot the recovery and try again. This is where things get weird.
4. Phone hangs out at boot logo (that kaleidoscope "M"). Fine, I accidentally did a normal boot, and there's no OS installed. I go into fastboot and boot to recovery. SAME SCREEN. TWRP has apparently disappeared. No matter. I go into fastboot and flash it again, then boot to recovery. SAME SCREEN. Flash back to CWM. SAME SCREEN. Back to TWRP one more time just for giggles? SAME SCREEN.
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot? Restore either my CWM or TWRP nandroid backups without access to the recovery? Any guidance would be appreciated.
Attachments:
a) boot logo I'm stuck on
b) command line log of commands from flashing recoveries

From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.

VerneVerne said:
From fastboot, flash your recovery and then use the volume down button to highlight recovery and then volume up button to enter into recovery.
Click to expand...
Click to collapse
Perhaps I didn't make that clear - that's exactly what I've been doing.

PHP:
gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman
Click to expand...
Click to collapse
That is what I have.
gerodive said:
No idea where to go from here. Anyone have any idea how this happened and what my options are at this point? Is there a way to manually flash a ROM via fastboot?
Click to expand...
Click to collapse
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.

Wansanta said:
PHP:
That is what I have.
Well I wiped my system partition when I must have been drunk or something b/c I still can't believe I did it. But I did. Then from bootloader mode, I ran the command mfastboot flash system system.img from a command shell on my PC using the system image from the sbf that my bootloader was currently on (in my case, it was 4.4.4). All was good.
Then I could restore my nandroids by moving them to my phone from my PC.
Click to expand...
Click to collapse
Could you elaborate a little more on this? How do I get the system.img file to flash? I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check? Deleting the system partition was definitely what I did. Also, why mfastboot as opposed to just fastboot?

gerodive said:
Could you elaborate a little more on this? How do I get the system.img file to flash?
Click to expand...
Click to collapse
mfastboot flash system system.img
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
In bootloader mode it will tell you on the second line. 30:B7 is the 4.4.4 bootloader version.
gerodive said:
Deleting the system partition was definitely what I did.
Click to expand...
Click to collapse
As long as you can get into bootloader mode you can flash it back.
gerodive said:
Also, why mfastboot as opposed to just fastboot?
Click to expand...
Click to collapse
because the moto x system images are too large to flash with fastboot, you have to use mfastboot.

gerodive said:
Back story: Verizon Moto X, unlocked bootloader via China Middleman, running Eclipse ROM 4.2.2, TWRP 2.7.0.0 recovery
Click to expand...
Click to collapse
gerodive said:
I'm guessing my bootloader would be on the 4.4.2 one since that was what Eclipse was on, but is there any way to check?
Click to expand...
Click to collapse
4.2.2 or 4.4.2?

nhizzat said:
4.2.2 or 4.4.2?
Click to expand...
Click to collapse
yeah he really needs to check b/c it really matters what version of the bootloader he is on.

Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.

Sorry, meant 4.4.2.

gerodive said:
Flashing the 4.4.2 system.img (and boot.img just for good measure) worked! I was then able to boot normally and then upgraded to 4.4.4. Oh happy day. Thanks for the help everyone.
Click to expand...
Click to collapse
So glad!! If you are unlocked, as long as you can get into a functioning bootloader mode and have access to the sbf for your version of the OS you haven't bricked.
I about near had a heart attack when I deleted my system, but no biggie to restore it. I think I only paid $35 to unlock b/c I did it straight through tao bao, but it was the best $35 I have spent in a long time. I drop $35 every time I go for sushi, so I can't imagine not paying to unlock if you have the option.

What rom should i use? for xt1063

I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.

abispac said:
I tried to flash many roms on my cell without any succes, so i wonder if anyone can tell me wich rom should i install via original recovery sideload, I got an xt1063 type MOFB9 ON TITAN_UMTS:4.4.4/kxb21.85-23/21
Please i know i can flash and downgrade many roms via fasboot,or custome recovery twrp or pholz, but i want to know, if in original, i got the latest , or what would be the next rom to flash acording to the system i have. thanks for the help.
Click to expand...
Click to collapse
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case

reefuge said:
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25&page=1ALL MOTO G firmware available (1st, 2nd and 3rd Gen) pick correct XT1063 in your case
Click to expand...
Click to collapse
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.

abispac said:
Thank you sir, but i see this roms end in xml, wich i think are for flashing via fasboot? if im wrong please correct me, im looking for the ota original to flash via original recovery.
Click to expand...
Click to collapse
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?

reefuge said:
thats correct these are via ADB mfastboot (which ignores OTA fingerprint check) as flashes full firmware, not the ota.zip which is only a smaller (not full firmware) update
ota.zip is NOT full firmware, so will not fix a corrupted / altered or non stock firmware
but you say you've flashed many roms.... you need to be on correct rom and matching recovery and also un-rooted to flash a OTA.zip as it checks Recovery version and the build fingerprint inside /system folder of original stock rom. if any of these mismatch it will fail.
also (apologies if wrong) but dont you believe your phone to be corrupted or read only hence why you cant flash images?
Click to expand...
Click to collapse
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.

abispac said:
Chanses are my phone its corrupted, i had the hope that a mayor ota, such a 5.0 (not5.0.2) would rewrite the phone and fix it, as the olny option i have not be able to tried was install an original ota or rom via recover sideload. I got recovery KXB21.85-23. Are there any fixes for read only out there? because i have found non....
Thanks for the help thought.
Click to expand...
Click to collapse
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone

reefuge said:
what error do you get via ADB when you flash?
can you remember what was the original firmware on phone as several for xt1063
or if boots the system version in about phone
Click to expand...
Click to collapse
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Its going to take 5hrs to upload my backup

abispac said:
Phone wont boot, its gets to the point where a blue m apears the goes to a blank screen, when flahing a rom via fasboot, all seems to get right but after restart is like nothing happened, i go back to the same state, same thing happens with twrp or philz, if you want to help, we can continue here but your more then wellcome to read this (nevermind i see you allready did)
So let me make a backup of twrp and see if i can post results, thanks allot, iveen waiting to fix this for so many days now.
A bit of background, i consider myself an advance user, someone that can google problems and fix stuff with it, ivee flashed alot of cellphones in the past ,many xt1064 and other models, just like everybody ealse, easy and no problems, but this one i just cant figure out. Seems like its on read only mode or freezed as a deepfreezed computer, dont mater how many roms i flash and the way i do, everything comes back to the same state, even if i reforma partitions, eeven if i delete pictures or folders, they come back once i reboot.
Click to expand...
Click to collapse
ok ii'm thinking corrupted partitions too.... but if you are willing to try i've made a xt1063 easy installer script for you to try now normally i work on xt1068 and would test on my xt1068 - so have NO xt1063 its UNTESTED - use at own risk.....
just stock firmware / drivers / adb and mfastboot ( same as my xt1068 script) I see no reason it should not be compatible.
download to pc / unzip to folder / read instruction inside
https://mega.co.nz/#!Tok2DJ6T!ggMoQDfAzuA7cmQQjbGCbXolWZTnx_567vG02CiURVsxt1063 4.4.4 easy installer
I repeat it YOUR choice - if it works- great - if runs ok but rom remains same would suggest somethings corrupt - if it doesnt work at all back to square 1....
now im presuming your boot loader is unlocked, as will fail if locked or relocked - if you use and get error please report what they are, i would have done 5.0.2 but its only 50% downloaded with a 1 hr+ to still go, estimate 2 hrs from time of this post until I can post a link

im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...

abispac said:
im uploading the backup, in the mean time i dont know if this is of any use ,its the recovery log zipped...
Click to expand...
Click to collapse
just to let you know TWRP is now 2.5.8.0 fixes some bugs cause older versions know to break permissions in Lollipop!!
https://mega.co.nz/#!Dx03wTbD!3sDFubGomhegQqdoGzNb1RWnQwApzyaTlVq69uX1TqkFlash-able version (unzip to pc and flash from there) 2.5.8.0
https://mega.co.nz/#!n5cUQCAY!uf66vEcQlmtu6VZMLPxksEFMEioZUFpystzTP6kwU4I Temporary boot version (no flash) 2.5.8.0.
will look but cant promise

I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.

abispac said:
I tried your easy install tool, brand new drivers, diferent usb port, all went smooth but after restart, im at the same situation. Funny thing, and ivee done this multiple times, after reflashing a new rom, most of them never give errors, then after nothing happens , i flash twrp and boot it, and all the files (the original ones , not the just flashed ones) are there intact, even pictures and music.
Click to expand...
Click to collapse
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?

reefuge said:
ok have you tried mfastboot erase userdata and mfastboot erase cache? from a command window?
i.m interested in the I flash twrp and boot..... does this mean you are able to replace recovery with a custom recovery ON phone
rather than temporary booting into it?
Click to expand...
Click to collapse
Yeah i tried those erase commands many many times and same result, i cant replace recovery at all, only boot of it, so when i do " mfastbooot flash recovery twrprecovery.img " then try to boot of recovery, i boot into factory recovery not, twrp, but if i do, "mfasboot boot twrprecovery.img" i can see the recovery img gets flashed and the phone boots of twrp. Weird behavior. So when i notice that i tried to flash a rom with mfastboot, and at the end i gave the command mfasboot boot recovery.img (the original rom recovery) then it gets flashed, and phone reboots, but i gets stuck at the motorola logo. This phone its playing hard to get....

heres, my backup https://mega.co.nz/#!md0AwbLR!uWe9PLklIugOziPLV6O_plbU-Zz9EXbqRvUVpYxECk0 hope you can find something.

Im going to take this phone to a shop to see if they can fix it as i have lost all hope, thanks refuuge for your help.

[MoFo IMG] 5.1 Rooted AT&T XT1097 with Tether

Below are the instructions for using MoFo to flash the AT&T XT1097 to 5.1. The rooted image has a modified build.prop file for free tether. Thanks go to @Slack3r for making the ext4 image and @btdownloads7 for developing the root method.
Since this is a 5.1 image, in order to get it to boot, you need to do the following BEFORE flashing the 5.1 system image:
1) Download the stock 5.1 files and extract them:
https://mega.co.nz/#!bN0BjKbI!zzq5b9wZBo-XFGNkcWtgw7mnXZgC5BWrEC-GZcGLELo
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /cache - YOU MUST DO THIS!
3) Reboot into bootloader mode and run the commands below to flash the following stock 5.1 files for the XT1097:
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
Do NOT flash the 5.1 bootloader (motoboot.img) or partition table (gpt.bin) - if you do, you will not be able to use MoFo ever again!!!!!
4) Download the rooted 5.1 image from here, extract it and flash it using MoFo.
https://mega.co.nz/#!ct8DlQxQ!DRMC_TvCcUk7V-FjCBfjsmIoOvw_f0WEdM7gx2waqzM
MD5 of the unzipped file = 146B6A65D925B985857A2F28D4294765
Note that with the XT1096 we had issues if we tried to boot into recovery after initially flashing the 5.1 system image so instead of booting into recovery and wiping cache where you might get weird flashing dead androids, we had to boot into system first.
Obviously if you want Xposed or anything else in the image, someone will need to add it in.

Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?

Casyis said:
Thank you!
Those of us already rooted with mofo on 5.0.2 need to return to stock 5.0.2 first, correct?
Click to expand...
Click to collapse
No, the instructions as written in the OP are complete. Like the instructions say, you need to do step 2:
2) Using a root file explorer (like ES Explorer with root enabled), delete everything in /data/dalvik-cache and /data/cache - YOU MUST DO THIS!
Then you can flash the rest of the 5.1 stock files for your device EXCEPT for the bootloader (motoboot.img) and partition table (gpt.bin). Then use MoFo to flash the rooted 5.1 image for your device.

Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!

Casyis said:
Thanks for clarifying.
I followed the instructions precisely, and the phone won't power up normally. It goes into recovery, and the android icon with exclamation just flashes intermittently. I'm unable to enter options to wipe cache. I can boot into recovery by holding volume down, but normal startup presents this behavior.
Any ideas?
EDIT: I chose BP Tools in boot options, and now the phone at least appears to be booting normally -- currently optimizing apps.
EDIT 2: Okay, so selecting BP tools evidently kicked the phone into booting normally. Looks like everything is just as it should be. Not sure what happened here, but in the end everything is good. Thank you (everyone involved) for getting this done for us!
Click to expand...
Click to collapse
This was happening with the XT1096 - you have to get it into system before recovery. You likely hit the wrong button and ended up in recovery instead of system. But once you get it into system, then it is fine.

Thanks again @JulesJam I am downloading now! Do you notice a big performance difference in 5.1? Will be nice to finally kill these memory bugs, so major thanks for that!

The OS is much snappier than 5.0.2. You can tell by going into multitasking and seeing how quickly the tiles load. Very, very nice. No re-draws at all yet since I flashed.

Step 2 implies that I'm already rooted. If I'm not, I assume I need to start with Step 0: Root the device with a 5.0 IMG?

What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!

bamachevrolet said:
What all would I need to fastboot flash from the stock files to return to stock @JulesJam ? My company just started using AirWatch service to get company email. Problem is airwatch will not work with root. Unfortunatly I will have to lose the ability to use MoFo.. Any help with this is greatly appreciated. Thanks!
Click to expand...
Click to collapse
FYI - like it says in the MoFo Noob Guide - MoFo trips the root checker and it is not able to be undone by flashing back to stock. I don't know how AirWatch works, but if it looks at the qe, then it will see you as rooted even if you aren't.
First thing I would do is flash back to 5.0.2 by flashing the stock 5.0.2 firware (link is in the MoFo Noob Guide)
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1 (repeat this for all of the sparsechunks)
then boot into recovery and wipe the cache. Then boot into system. I believe it will need to downgrade the sensor firmware so allow that to happen.
Then boot into bootloader mode and see if your software status still says modified or not. Then boot into recovery and see what your qe status is. If after that your software status is still modified and your qe is still 1/1, I would do a factory reset and see if that corrects it. It probably won't though.
You will then have to decide whether or not you want to take the 5.1 OTA because your phone is going to want to upgrade. Instead of taking the 5.1 OTA which will upgrade your bootloader and partition table, you have the option of flashing stock 5.1 everything but the motoboot.img and gpt.bin. That would keep you stock 5.1 but still keep your bootloader and partition table on 5.0.2 so that if you wanted to sell the phone later, you could sell it with a copy of MoFo that still works. I put this out there because idk how AirWatch works and if flashing back to stock doesn't change your software status from modified or your qe from 1/1, you may not be able to use AirWatch, idk.

Thank you so much for the detailed explanation @JulesJam . Unfortunately I followed the instructions to the T and didn't run into any issues until I tried to boot into recovery. I got the dead android with a line under saying "no command". So I tried running system first. I got through the boot animation and then a black screen. I let the black screen sit for 30 min and nothing happened. I had the exact issue when installing 5.1, I was able to get it to boot using BT tools. Unfortunately this is not working now. I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!

bamachevrolet said:
I get the same black screen after the boot animation. I tried multiple times with no luck. I can however still get into fastboot without issues
Any ideas how I can get 5.0.2 to boot? Thanks again!
Click to expand...
Click to collapse
For sure you flashed the 5.0.2 logo.bin, boot.img and all of the 5.0.2 system sparsechunks? That sounds like the system partition was not flashed properly.
Perhaps the 5.0.2 system files you have are corrupted? Are you sure the files you have are the stock 5.0.2 files for the AT&T XT1097?

bamachevrolet said:
I got the dead android with a line under saying "no command". !
Click to expand...
Click to collapse
That's OK as long as he is not flashing. When you have the dead android, go ahead and press and hold power then tap volume up to get into recovery and wipe the cache.

Thank you! I was able to get into recovery to wipe cache, but still won't boot.
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.

bamachevrolet said:
Thank you! I was able to get into recovery to wipe cache, but still won't boot.
Click to expand...
Click to collapse
How long do you let the blank screen sit before you try to get into bootloader mode? I remember sometimes it takes awhile for it to boot.
Also, the dalvik-cache may need to be wiped too. That would require a factory reset to do it so you could boot into recovery and do a factory reset. Unless there is some way to wipe the dalvik-cache from bootloader mode.

bamachevrolet said:
Don't think it matters but the sparsechunk starts at 0 in the AT&T file. I flashed the sparschunks in order, and in my case 0-8.
Click to expand...
Click to collapse
That's fine. I wasn't sure what number they started with.

bamachevrolet said:
I downloaded 5.0.2 from your noob guide, and flashed everything in the order of your first replied post. I am going to start over, just in case I missed something.
Click to expand...
Click to collapse
And after you do, let it sit at the blank screen for awhile to make sure that it isn't an issue of needing time to boot up. If it still won't boot, try the factory reset.

Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!!
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
[/COLOR @JulesJam do you have a donation link?

bamachevrolet said:
Thank you so much @JulesJam !!! I'm booted to stock 5.0.2 now. I did have to do a factory reset, but not too big of a deal. Unfortunately I forgot to backup my 48 tasker profiles...lol. So glad to have it back up. Thank you again!!![
Click to expand...
Click to collapse
Glad it worked out, sucks about the tasker profiles though. So it seems like the dalvik-cache has to be wiped, too. I will note that in the future people should delete the contents of the dalvik-cache folder before flashing back to the earlier version of the software.
Does your software status still say modified in bootloader mode? What is your qe when you boot into recovery?

bamachevrolet said:
@JulesJam do you have a donation link?
Click to expand...
Click to collapse
No but thanks for the offer. If you want to donate, please donate to the ASPCA.

official signed 28.2 Fastboot flashable firmware

My phone is bricked, need the complete Fastboot flushable signed 28.2 firmware, Oreo 8.1 May Update for the USA retail model of x4
Mod edit: no trading/payments on XDA please... edited.

I have the OTA. Would you be able to use that?

Why not just flash 28.1 full firmware and just take the ota to 28.2 that it offers immediately?

I thought it was possible to downgrade via the fastboot method with any firmware. Doesn't have to be 28.2 to at the very least get your phone back working.

try flashing OTA. adb sideload it.
https://forum.xda-developers.com/moto-x4/help/moto-x4-patch-captured-opw28-2-t3807679

my phone is boot loader locked, with OEM locking option set to OFF, and it does not boot into anything. just Fastboot works. I cannot get recovery to work.

jpolster2005 said:
my phone is boot loader locked, with OEM locking option set to OFF, and it does not boot into anything. just Fastboot works. I cannot get recovery to work.
Click to expand...
Click to collapse
Flash this: https://androidfilehost.com/?fid=962339331458997429
All you need is fastboot.

ptn107 said:
Flash this: https://androidfilehost.com/?fid=962339331458997429
All you need is fastboot.
Click to expand...
Click to collapse
I tried that, validation failed.

does ANYBODY have the Fastboot complete version of 28.2? Please? I need to unblock my phone!

jpolster2005 said:
does ANYBODY have the Fastboot complete version of 28.2? Please? I need to unblock my phone!
Click to expand...
Click to collapse
Are you not able to flash 28.1?

when I try, it says image validation failed. I NEED 28.2 or higher

see, my boot loader was locked when I tried to flash a different rom. I didn't know I needed to unlock the boot loader I thought that step was optional. now im stuck with a phone that only boots to Fastboot, will ONLY accept SIGNED STOCK 28.2 or higher.

Can try https://androidfilehost.com/?w=files&flid=229118 or https://firmware.center/firmware/Motorola/Moto X4/Stock/XT1900-1/
See if it will accept an earlier version. Couldn't hurt in your situation.

I remember some people helped this file: https://forum.xda-developers.com/showpost.php?p=76918099&postcount=7
Haven't tried myself but just do it. Nothing to lose

I have successfully unlocked my Project Fi phone (Moto X4) and would be happy to share the firmware which is OPW28.2 on the build number... If anyone can tell me how to obtain (extract) it from the phone?
( Motorola version: OPW28.46-18 )

I am in the same boat
jpolster2005 said:
when I try, it says image validation failed. I NEED 28.2 or higher
Click to expand...
Click to collapse
I will also sell mine as well

I have tried flashing every firmware and tried to blank flash but could not

jpolster2005 said:
I have tried flashing every firmware and tried to blank flash but could not
Click to expand...
Click to collapse
Have you tried using a different computer or USB port?
Have you ever unlocked the bootloader before? If not, you could send it to Motorola for replacement.

jpolster2005 said:
I have tried flashing every firmware and tried to blank flash but could not
Click to expand...
Click to collapse
Not sure what to tell you from here. Just make sure not to rush any steps due to frustration or impatience.
I was able to return my first Moto X4 on warranty due to playing around with flashing. I'm sticking 100% stock till we get official lineage.
---------- Post added at 04:29 AM ---------- Previous post was at 04:25 AM ----------
jpolster2005 said:
how long before we see one. I have been relegated to using an iPhone 6 32GB! I really NEEEEEEED my phone to not be bricked. I tried to do the blank flash and boot off sd card and all that to no avail. none of it worked. meow I am getting so frustrated.
Click to expand...
Click to collapse
Bad eticate to post about your issue on multiple threads especially when you have your own. I'm sorry, there is no timetable. Could be tomorrow, could be months. This is the risk in flashing, end even worst in our case since Lenovo has not released factory images.

jpolster2005 said:
see, my boot loader was locked when I tried to flash a different rom. I didn't know I needed to unlock the boot loader I thought that step was optional. now im stuck with a phone that only boots to Fastboot, will ONLY accept SIGNED STOCK 28.2 or higher.
Click to expand...
Click to collapse
What fastboot version use? Use Minimal version, maybe works