Related
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!
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.
Hi everybody,
A few days ago, I rooted my Mexican XT1225. I shut it down for a day (my main cellphone is the new Moto X), turn it on again and now it's stuck on fastboot.
I could boot into TWRP (by flashing it temporarily with fastboot on Linux) and then I decided to wipe data and then install the new lollipop zip file. But it failed saying it could not mount /system /data or anything really, I basically have it without format, all partitions say 0MB.
So I tried flashing with fastboot, but it gave me an error when flashing the partition gpt.bin, it didn't give me an error when flashing other files. Still stuck, now I cannot even access the recovery menu, it goes just into fastboot mode and does not show the little recovery menu anymore.
Then I tried flashing with RSD, still same problem. It fails when setting the fb_mode_set and when I delete that line from the xml it fails again on flashing gpt.bin
EDIT: I am attaching a log file of TWRP evidencing this.
Any ideas on how to get back to normal? How can I redo the partition in another way?
Thanks in advance,
Gustavo
Unlocked bootloader? Just remove the got. Bin flash line
Jaocagomez said:
Unlocked bootloader? Just remove the got. Bin flash line
Click to expand...
Click to collapse
Yes, unlocked bootloader. Removed the gpt.bin flash line and still no luck. Tried flashing several files, the Indian Lollipop, the Mexican Kitkat, nothing has worked.
gusbeto37 said:
Yes, unlocked bootloader. Removed the gpt.bin flash line and still no luck. Tried flashing several files, the Indian Lollipop, the Mexican Kitkat, nothing has worked.
Click to expand...
Click to collapse
After re reading your post I understood what's wrong, you have to flash the lollipop OTA on stock recovery not twrp or rsd lite, once you flash it you can put back twrp
Jaocagomez said:
After re reading your post I understood what's wrong, you have to flash the lollipop OTA on stock recovery not twrp or rsd lite, once you flash it you can put back twrp
Click to expand...
Click to collapse
I have the xml.zip file, extracted it and manually flashed partition by partition. Something I have previously done with my 1st gen Moto X, my Razr HD and even my Atrix, if I remember correctlly. Even RSD Lite should work with those files.
Still, I will try to boot with the stock recovery, since right now I cannot access it. I will also seek a way to get the xml.zip file inside the storage, since I cannot even mount it with TWRP (It shows 0mb drive)
gusbeto37 said:
I have the xml.zip file, extracted it and manually flashed partition by partition. Something I have previously done with my 1st gen Moto X, my Razr HD and even my Atrix, if I remember correctlly. Even RSD Lite should work with those files.
Still, I will try to boot with the stock recovery, since right now I cannot access it. I will also seek a way to get the xml.zip file inside the storage, since I cannot even mount it with TWRP (It shows 0mb drive)
Click to expand...
Click to collapse
Twrp for this device it's not very stable I got that errors too
Just flash mexico firmware then the OTA zip on stock recovery and you will be good to go.
If you can't access recovery press vol- and power with the phone turned off and you'll be able to select recovery
Hi,
I have tried the vol+power and cannot access recovery.
When I try to flash Mexico's firmware (through either RSD or manually in Linux using fastboot), I am unable to flash partition gpt.bin, but I can flash everything else. Yet, in spite of flashing everything else, I cannot get out of the fastboot loop.
I am attaching some photos of what happens. The first one is the only thing that boots, cannot access recovery, cannot boot normally. The second photo is what happens when I press the volume button many times.
So when you select recovery does it power off or just go back to fastboot again?
Steve-x said:
So when you select recovery does it power off or just go back to fastboot again?
Click to expand...
Click to collapse
Hi, I dan only go yo fastboot. The menú does not appear. The only thing that appears is the photo of my previous post.
I can boot into TWRP by manually doing fastboot boot twr-recovery.IMG
Hmmm, doesn't look good. The fastboot screen doesn't even load the picture of the green Android. I am thinking the partition table is messed up. I know I saw something similar with the original(2013) Moto X a while back. You may want to do some searching in that forum.
gusbeto37 said:
Hi, I dan only go yo fastboot. The menú does not appear. The only thing that appears is the photo of my previous post.
I can boot into TWRP by manually doing fastboot boot twr-recovery.IMG
Click to expand...
Click to collapse
flash mexican stock rom with rsd lite
Steve-x said:
Hmmm, doesn't look good. The fastboot screen doesn't even load the picture of the green Android. I am thinking the partition table is messed up. I know I saw something similar with the original(2013) Moto X a while back. You may want to do some searching in that forum.
Click to expand...
Click to collapse
Hola Steve,
Indeed, it looks like the partition table is messed up, I will look for that Moto X thread.
@Jaocagomez I have tried that, but it fails with gpt.bin partition flash and even after flashing everything else (RSD, fastboot or TWRP) it does not work.
After reading quite a lot on the Internet, it seems that my problem happened to some Moto G and Moto X users. Seems to be that I am trying to flash a gpt.bin that is older than the one already in my phone. I will try again when the Mexican Lollipop image is released in xml.zip format.
In the mean time, I will continue to search for solutions.
Hi
I think I have the same issue.
I have XT1225 bought it from Amazon (I asked the company and they said Puerto Rico origin) factory unlocked. had 4.4.4 and tried to upgrade to 5.0.2. Here is what I exactly did:
devices not rooted, locked bootloader
downloaded RSD Lite
downloaded the official 5.0.2 India Firmware
tried to flash it using RSD
got an error in flashing boot from RSD
I tried to do it again and I get the same issue, I tried to flash the Puerto Rico 4.4.4 and it didnt work (it get stuck in partition gpt) and my device is dead. I tried to unlock the bootloader using the code from motorola and it says allow oem unlock from developer menu
tried doing it manually using mfastboot with both 5.0.2 and 4.4.4 and still didnt work.
please let me know if you managed to fox your problem or if anyone can help us get back our devices
Stuck in fastboot
rehaili said:
Hi
I think I have the same issue.
I have XT1225 bought it from Amazon (I asked the company and they said Puerto Rico origin) factory unlocked. had 4.4.4 and tried to upgrade to 5.0.2. Here is what I exactly did:
devices not rooted, locked bootloader
downloaded RSD Lite
downloaded the official 5.0.2 India Firmware
tried to flash it using RSD
got an error in flashing boot from RSD
I tried to do it again and I get the same issue, I tried to flash the Puerto Rico 4.4.4 and it didnt work (it get stuck in partition gpt) and my device is dead. I tried to unlock the bootloader using the code from motorola and it says allow oem unlock from developer menu
tried doing it manually using mfastboot with both 5.0.2 and 4.4.4 and still didnt work.
please let me know if you managed to fox your problem or if anyone can help us get back our devices
Click to expand...
Click to collapse
I am facing the same problem
Though my device is different : XT1254 (verizon locked)
As bootloader is not unlocked, i cannot flash any software any way. Tried all the software from all the countries but to no avail.
The Phone is stuck in fastboot mode.
Please help
You 1225 folks might want to wander into this thread... http://forum.xda-developers.com/droid-turbo/general/tutorial-to-kk-soak-lollipop-t3041129 ... I've hashed my phone out a couple times between CM, lollipop, exposed, playing with the kernal and so on and it got me back up and running.
guys I need ASAP help, stuck in reboot after update, got intsallation error 7. now im stuck on logo reboot, cannot enter recovery (I see "dead" android icon. Please help!
jazzus said:
guys I need ASAP help, stuck in reboot after update, got intsallation error 7. now im stuck on logo reboot, cannot enter recovery (I see "dead" android icon. Please help!
Click to expand...
Click to collapse
We need more information. What is your original firmware, what did you try to update to and is your bootloader unlocked?
Steve-x said:
We need more information. What is your original firmware, what did you try to update to and is your bootloader unlocked?
Click to expand...
Click to collapse
Ok fixed, after 20 or 30 tries I was able to enter recovery Thx!
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.
Hello I'm new to rooting and really all of this and I can't flash TWRP onto my Moto X 2013 (on 5.1). My phone's bootloader is unlocked, but I've been having trouble actually rooting it. I have no problems getting to fastboot and I'm confident I've been following instructions accurately.
I've been following this guide: http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
I've made sure I have everything installed, and my adb and mfastboot are set-up correctly for use in CMD. I'm even using TWRP 2.8.6.0 since the guide I'm using said there's an issue with 2.8.7.0. However, when I use the command mfastboot flash recovery twrp.img (I renamed TWRP) it says:
(bootloader) Variable not supported!
target max-download-size: 768MB
error:cannot load 'twrp.img': No error
Can someone give me a pointer as to what I'm doing wrong please? I'd really like to get my Moto X rooted. I've tried tons of guides and I always get to this step and this is where it goes wrong.
Qivine said:
Hello I'm new to rooting and really all of this and I can't flash TWRP onto my Moto X 2013 (on 5.1). My phone's bootloader is unlocked, but I've been having trouble actually rooting it. I have no problems getting to fastboot and I'm confident I've been following instructions accurately.
I've been following this guide: http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217
I've made sure I have everything installed, and my adb and mfastboot are set-up correctly for use in CMD. I'm even using TWRP 2.8.6.0 since the guide I'm using said there's an issue with 2.8.7.0. However, when I use the command mfastboot flash recovery twrp.img (I renamed TWRP) it says:
(bootloader) Variable not supported!
target max-download-size: 768MB
error:cannot load 'twrp.img': No error
Can someone give me a pointer as to what I'm doing wrong please? I'd really like to get my Moto X rooted. I've tried tons of guides and I always get to this step and this is where it goes wrong.
Click to expand...
Click to collapse
Your could try this version of twrp=> https://mega.nz/#!cFJw1LAQ!y5tfv6aGzsabFsKkFSJLl0xF8T7G148HpBBG4FILmQY
I use it ?
Sent from my Moto X using Tapatalk
Just tried it, got the exact same message as before.
Qivine said:
Just tried it, got the exact same message as before.
Click to expand...
Click to collapse
Very strange. Have you tried philz recovery?
Sent from my Moto X using Tapatalk
---------- Post added at 10:07 AM ---------- Previous post was at 09:49 AM ----------
It's possible that the adb and fastboot you're using isn't working correctly. I recall seeing the same error.
This is what I used at first=> https://mega.nz/#!lEARkTyT!Jx-ZXnMMk0Cyq0i3Yv56LT3AWv-s5s-cRdJAMQATKT4
Sent from my Moto X using Tapatalk
After some googling around I finally got TWRP to work, thanks for the help though!
How did you solve it?
Qivine said:
After some googling around I finally got TWRP to work, thanks for the help though!
Click to expand...
Click to collapse
Qivine,
I'm having the same issue I think that you had...
I am able to successfully flash twrp to my phone, but then when I boot into fast boot and choose the recovery option, it just goes black.
What steps worked for you to root your phone?
Thanks,
Fishmaniam
fishmaniam said:
Qivine,
I'm having the same issue I think that you had...
I am able to successfully flash twrp to my phone, but then when I boot into fast boot and choose the recovery option, it just goes black.
What steps worked for you to root your phone?
Thanks,
Fishmaniam
Click to expand...
Click to collapse
Once I was able to flash twrp I was able to get into recovery no problem and flash roms/the supersu.zip.
I never had the issue with my phone just going black, sorry.
Plz brother help me?
Qivine said:
After some googling around I finally got TWRP to work, thanks for the help though!
Click to expand...
Click to collapse
Please brother, how did you solve it out, help me plz?
Zabihullah Xabih said:
Please brother, how did you solve it out, help me plz?
Click to expand...
Click to collapse
I can help. Just flash TWRP. What model is your Moto X. If the bootloader is unlocked you can flash recovery