So I am on stock Android 5.1. Had rooted earlier but un rooted. Just got a 4.6 MB update. The update installed properly but my device will not boot. It reaches the boot logo and then I see a black screen. What steps should I be taking now?
P.s It wont boot into recovery, nor is it charging.
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
AGISCI said:
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Is that by holding power and volume down button?
If yes then I just got there..
Should I be flashing stock 5.1 again?
AGISCI said:
Can you get into fastboot mode?
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Or should I be following these steps?
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Yes that is fastboot. As long as you have that your phone is salvageable.
What model do you have? xt1092, 1093, 1095, etc?
To use fastboot you need the android program called fastboot. If you go to the android website you can install it by downloading and installing the android sdk.
You have 2 options and please pay attention so as to not brick your phone.
You can try to factory reset, it may fix the phone but it erases all of your data. To do this type:
fastboot erase userdata
fastboot erase cache
fastboot rebooot
The other option is to flash the full factory image. I need to know your model before I can get you the correct factory image.
Please be aware that right now the new factory image that has this small update does not exist. So you will have to downgrade to the 5.1 without this patch you installed. However do NOT install the OTA patch!!! After a downgrade using an OTA can permanently brick your phone. You will have to wait till the full firmware is released that has this patch then you will be able to safely upgrade.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes that is fastboot. As long as you have that your phone is salvageable.
What model do you have? xt1092, 1093, 1095, etc?
To use fastboot you need the android program called fastboot. If you go to the android website you can install it by downloading and installing the android sdk.
I also have fastboot installed as I had rooted my device earlier and unrooted completely.
You have 2 options and please pay attention so as to not brick your phone.
You can try to factory reset, it may fix the phone but it erases all of your data. To do this type:
fastboot erase userdata
fastboot erase cache
fastboot rebooot
The other option is to flash the full factory image. I need to know your model before I can get you the correct factory image.
Please be aware that right now the new factory image that has this small update does not exist. So you will have to downgrade to the 5.1 without this patch you installed. However do NOT install the OTA patch!!! After a downgrade using an OTA can permanently brick your phone. You will have to wait till the full firmware is released that has this patch then you will be able to safely upgrade.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I have a XT 1095. I have the factory image TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US.tgz from the motorola website. Hypothetically speaking if I do a factory reset I can take the OTA as I dont mind losing any data on the phone. All my photos are backed up to google drive so it is not an issue for me.
Also I have fastboot on my laptop as I had rooted my phone and then unrooted it completely.
If you do a factory reset you will not need to take an OTA because it is already installed. All a factory reset does is erase the cache and your data, it does not downgrade nor uninstall an OTA.
Sent from my XT1095 using Tapatalk
AGISCI said:
If you do a factory reset you will not need to take an OTA because it is already installed. All a factory reset does is erase the cache and your data, it does not downgrade nor uninstall an OTA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So if I factory reset I can take any further OTAs that release without any worries right?
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version. So if you flash that file you have don't upgrade via OTA.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Okay. I shall factory reset and revert. Thanks a ton for the info!
Only revert if factory reset does not work.
Sent from my XT1095 using Tapatalk
AGISCI said:
Yes. OTA is only dangerous if you downgrade. A factory reset is not a downgrade. However if the factory reset does not work to fix your problem, then the other option I mentioned of downgrading will be your only option. That firmware file you have from motorola IS a downgrade because it does not have the patch you installed in it. Which means you would have to wait for the new firmware file to be released before you can patch your phone with the latest version. So if you flash that file you have don't upgrade via OTA.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
So it turns out my phone will not boot even after factory reset via the fastboot method. Comes to the boot logo and switches off.
pulley06 said:
Okay. I shall factory reset and revert. Thanks a ton for the info!
Click to expand...
Click to collapse
Sorry to hijack your thread, but I'm having the same issue. (Shows Unlocked Bootloader screen, then briefly shows Moto logo, boot animation, then blackscreen). I can access fastboot (Power + Vol Up + Vol Down) as well.
Once you're able to try factory resetting, could you post if that solves the problem?
At the moment I'm waiting for permission to access the latest Motorola factory image. Is there another source for these that anyone knows of?
Thanks!
Edit: Your post squeezed in before mine!
malerick003 said:
Sorry to hijack your thread, but I'm having the same issue. (Shows Unlocked Bootloader screen, then briefly shows Moto logo, boot animation, then blackscreen). I can access fastboot (Power + Vol Up + Vol Down) as well.
Once you're able to try factory resetting, could you post if that solves the problem?
At the moment I'm waiting for permission to access the latest Motorola factory image. Is there another source for these that anyone knows of?
Thanks!
Edit: Your post squeezed in before mine!
Click to expand...
Click to collapse
Factory reset does not allow me to boot. It is so surprising :/
So now I have to wait for them to release the factory images to be able to take OTA? And I should not be taking any OTA after flashing this stock file?
AGISCI said:
Only revert if factory reset does not work.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
It isnt
pulley06 said:
Factory reset does not allow me to boot. It is so surprising :/
So now I have to wait for them to release the factory images to be able to take OTA? And I should not be taking any OTA after flashing this stock file?
Click to expand...
Click to collapse
I requested the most recent stock image from Motorola. (Can't link directly: motorola-global-portal.custhelp DOT com/app/standalone/bootloader/recovery-images) Needs to be approved apparently...
My understanding is that this does not contain the recent patch (that is causing our bootloop). Based on what AGISCI is saying, taking the OTA after flashing the factory images is bad news...
I'm guessing that flashing the updated factory images (over these older versions) when they are released will make everything okay?
Pulley:
Use these commands to downgrade the firmware:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
But do NOT take the OTA. You will have to wait for motorola to post a new full firmware before you can upgrade.
Malerick:
Your problem is not the same. His phone does not boot. Yours does.
Your problem is known as the black screen. It can be easily fixed with a factory reset.
Sent from my XT1095 using Tapatalk
malerick003 said:
I requested the most recent stock image from Motorola. (Can't link directly: motorola-global-portal.custhelp DOT com/app/standalone/bootloader/recovery-images) Needs to be approved apparently...
My understanding is that this does not contain the recent patch (that is causing our bootloop). Based on what AGISCI is saying, taking the OTA after flashing the factory images is bad news...
I'm guessing that flashing the updated factory images (over these older versions) when they are released will make everything okay?
Click to expand...
Click to collapse
Yeah I think that is my assumption as well :/ Will have to wait for AGISCI to give his inputs on that. I have access to that file. I can upload it on my dropbox if u want it right now.
AGISCI said:
Pulley:
Use these commands to downgrade the firmware:
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
But do NOT take the OTA. You will have to wait for motorola to post a new full firmware before you can upgrade.
Malerick:
Your problem is not the same. His phone does not boot. Yours does.
Your problem is known as the black screen. It can be easily fixed with a factory reset.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
From what I understand my problem and his seem to be the same to me. Even I have a black screen after the moto boot logo and it does not boot. Isnt that the same Malerick is having right?
Related
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
AbstractXart said:
So one of my buddies took the OTA update for 4.4.2 while being rooted on 4.4 with TWRP as his recovery. Now he is stuck in an endless bootloop. Any idea what we could do to bring his phone back to life?
By the way, he is on Sprint and has his bootloader unlocked
Any advice would help!
Thanks.
Click to expand...
Click to collapse
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
patspdaphone said:
This happened to me too.
Just flash the latest firmware for your device at http://sbf.droid-developers.org/phone.php?device=0
Then accept the OTA.
Re-install TWRP.
Hope this works for you too.
Click to expand...
Click to collapse
So to accept the OTA, did you go through the bootloader/recovery and flash it, or were you able to turn on your phone and accept it? Sorry I don't have his phone on me right now otherwise I would have done it .
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
KidJoe said:
Don't flash the full SBF..
boot the phone into fastboot mode... mfastboot erase cache... the reboot the phone. that will remove the OTA zip file from chache and stop the boot loop.
The bootloop is because the phone has TWRP on it rather than stock recovery.
To take the OTA properly, use mfastboot to reflash stock recovery only. Also have him undo any hacks that might have touched system files or the OTA will fail, (mfastboot system will also get /system back to normal)...
Click to expand...
Click to collapse
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
AbstractXart said:
We actually just ended up clearing the system cache and that seemed to do the trick .
I incredibly appreciate all the info! If anyone makes this silly mistake, all you need to do is clear the cache and everything works as intended.
Click to expand...
Click to collapse
until the next time the OTA downloads and tries to install
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Globalrebel said:
I am having this very same problem. My phone just today went into boot loop. Running KangKat on unlocked 1053 with Faux kernel. No boot logo or anything. The phone just vibrates then after 30 seconds or so, it vibrates again. It does this non-stop.
I can plug my phone into USB and the phone's contents come up on my computer, but I can't get the screen to turn on!! Any ideas?
Click to expand...
Click to collapse
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
KidJoe said:
KangKat wtih Faux kernel? So you are not running the stock rom? I'm suprised the actually OTA installed.
I don't know anything about that rom, or kernel to begin to tell you how to fix this situation, short of reflashing your rom
Click to expand...
Click to collapse
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
samwathegreat said:
He probably flashed the "Flashable 4.4.2 ZIP" that is flashable through TWRP.
@Globalrebel :
You need to try to get into bootloader (AP Fastboot) mode. Try holding the VOL DOWN while the phone reboots (vibrates). Make sure the phone is unplugged from USB. If you can access fastboot, your best best would probably to flash the entire SBF back to stock.
Always check here first before you do something like trying to flash a stock update on a custom rom. We would have quickly informed you that this is ill-advised.
Good Luck
Click to expand...
Click to collapse
any ideas?
I just checked device manager and it shows "ADB Interface" and then MOT Single ADB Interface.
But its not showing up under devices when running command "ADB Devices" in CMD
Globalrebel said:
Ok, so I have held down the power button, and then when vibrating starts, I hold down vol down button. Then, it vibrates 2 times. What now? (Sorry, I'm freaked out as this is my only phones )
How can i check to see if it is actually in Fastboot mode? Since my screen doesn't show ANYTHING at all?
I started up an ADB server and connected my phone and tried "adb devices" but my phone isn't listed.
---------- Post added at 08:49 AM ---------- Previous post was at 08:40 AM ----------
any ideas?
Click to expand...
Click to collapse
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
samwathegreat said:
Fastboot getvar all
If you get a response with that, proceed with the entire Sbf manual method as listed in the return to stock thread.
Click to expand...
Click to collapse
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Globalrebel said:
I got it to show some info after running the command. Now, I have the following guide open . .
[GUIDE][VIDEO] Moto X - Return to 100% stock (using RSD Lite OR manual flash)
But I don't see anything in RSDLite after running it and clicking "Show Device"
Can I just to the manual method?
For manual method, should I copy all the files into the same folder as my mfastboot.exe?
Click to expand...
Click to collapse
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
samwathegreat said:
Yes,I suggested manual method in last post. Faster and easier.
Yes extract the sbf to the folder containing mfastboot and fastboot.
The only thing you will do differently is one of the last lines that says carrier vzw, change it to carrier sprint.
Make sure u are using the 4.4.2 sprint sbf.
Good luck
Click to expand...
Click to collapse
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
No water damage, and the phone was literally working perfectly fine 15 minutes ago. Just all of a sudden stopped showing the screen
Globalrebel said:
I am using Tmobile so I put tmo
But, after doing EVERYTHING, the phone reboots and I see it in PC, but screen is still not working?!?!?!
I did everything...
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier tmo
fastboot oem fb_mode_clear
then
fastboot reboot
The phone boots and the phone is seen by my computer, but the screen is not working AT ALL
Click to expand...
Click to collapse
Bummer. You appear to have used the correct procedure.
This looks to be a hardware failure :/
Sorry, I don't have any further troubleshooting techniques for you...
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Globalrebel said:
Its all good. I think the screen just decided to die on me?!?! Which REALLY SUCKS! I'm still in my 1 year warranty policy. After fastbooting the original 4.4.2, will motorola know I did anything to the phone? IE, can they know I flashed anything?
Click to expand...
Click to collapse
If you unlocked the bootloader they know it. Technically your warranty is void... But they might replace/fix it anyways. Don't mention it and see what happens. Let us know.
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
reno55 said:
I thought I prevented my phone from downloading the OTA to 4.4.3 on my Dev Edition Unlocked bootloader running 4.4.2 and TWRP. I obviously did not and now my phone keeps rebooting into TWRP.
Is there a way to stop this and clear it out somehow?
Click to expand...
Click to collapse
Try using Titanium Backup to freeze MotorolaOTA
samwathegreat said:
Try using Titanium Backup to freeze MotorolaOTA
Click to expand...
Click to collapse
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
reno55 said:
Actually I think I can fix by flashing stock recovery but where can I find the stock recovery image?
Click to expand...
Click to collapse
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
samwathegreat said:
YES, you can fix by flashing stock recovery assuming you haven't heavily modified your system. Flashing the stock recovery will make the phone try to flash the OTA.
You'll need to download the SBF for your phone here: http://sbf.droid-developers.org/phone.php?device=0
Unzip the file. I'm assuming you already have the fastboot and mfastboot binaries as well as the android SDK.
Place the file "recovery.img" in the same folder as mfastboot & fastboot. Make sure USB Debugging is enabled (or manually boot into bootloader).
Type mfastboot flash recovery recovery.img
Done.
Good Luck
Click to expand...
Click to collapse
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
reno55 said:
I think I just did this correctly.......it is on Android is upgrading now.....
I can just flash a custom recovery now right?
Click to expand...
Click to collapse
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
samwathegreat said:
If the upgrade is successful, absolutely.
mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img
download twrp from here: http://forum.xda-developers.com/moto-x/development/recovery-unlocked-twrp-2-6-3-1-android-t2534850
Click to expand...
Click to collapse
Can I flash philz?
reno55 said:
Can I flash philz?
Click to expand...
Click to collapse
Don't see why not. Just substitute the filename for philz recovery instead.
Get Philz here: http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
I have not used Philz personally...I prefer TWRP, but it looks like (unlike TWRP), that there is a different img for each variant of the Moto X. You will need to be careful to download the correct one.
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup, TWRP and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is there no way to complete the OTA without flashing a stock recovery? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
frankie_p said:
I got the XT1053 T-Mobile version, rooted, unlocked with titanium backup and Xposed. I just got the software update notice and I am currently trying to decide if I want to update or not. Correct me if I am wrong, but from what I have read, if I want to get the OTA, is the best way to flash the SBF and update to 4.4.3 and then configure the phone again? Is it worth it? I love this phone, but there are no custom ROM's that are stock based for XT1053 which would be ideal since I don't want to lose all the extra goodies of the stock ROM.
Click to expand...
Click to collapse
YES, that is the best way to do it. You can -try- disabling xposed, and un-doing any major modifications you have done (like freezing or removing any system apps). You want it to be as close to stock as possible before you try to accept the OTA, which includes flashing back the stock recovery.
SBFing back to stock 4.4.2 FIRST, and accepting the update, THEN flashing TWRP and rooting, then re-configuring everything and installing your apps is MUCH safer and pretty much guarantees that your filesystem will be 100% intact.
If it were ME, I would SBF first -- for whatever that's worth...
Good Luck
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
reno55 said:
Ugh! I am having all kinds of issues with 4.4.3. There is not a way to go back to 4.4.2 is there?
Click to expand...
Click to collapse
Sure. It's just slightly more complicated. You'll need the entire 4.4.2 SBF for your carrier.
Do this: Reboot to bootloader
FIRST, JUST flash gpt.bin and motoboot.img:
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
Now you need to REBOOT back into bootloader (to prevent gpt.bin mis-match -- if you don't reboot here, you will get errors). Do this by typing:
mfastboot reboot-bootloader
Now flash the rest of the files:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
Reboot, and you should be back to stock 4.4.2
And finally the disclaimer: DO NOT TRY TO DOWNGRADE TO ANY VERSION PRIOR TO 4.4.2 .....if you don't want a brick.
It's ok to downgrade 4.4.3 to 4.4.2 because the bootloader version did not change. It is NOT safe to downgrade to anything prior (4.4 or 4.2.2).
I'm trying to convert my Moto X 1097 to 1095 pure. When I try flashing files with mfastboot I get hab check failed for boot and hab check failed for recovery. It's running 4.4.4 pure but I assume still has old recovery as it won't boot into recovery. I have abd all and downloaded mfastboot v2. Why am I getting these errors? Bootloader unlocked.
Are you trying to flash 4.4.4 or 5.0?
Motoboot and gpt can never be downgraded, some files will always show they failed the hab check even though they are ok as they aren't the original files.
If you flash the entire 4.4.4 or 5.0 Pure firmware package you will have no radio at all and will need to use the original NON-HLOS.bin from the matching Telus package to get it back.
If you want to try the Pure 5.1 soak/leak then flash the full Pure 5.0 package and then apply the soak update via stock recovery. At that point your radios will work as the 5.1 soak appears to include a modem/radio that works with the XT1097.
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple.
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
matt1515 said:
matt1515 said:
Ok thanks for info. So i flashed over my telus lollipop to 4.4.4 tmobile and then ota. So when I reboot into bootloader and choose recovery it just goes to a white screen with a ? in it. But if I use cmd adb reboot recovery it works and goes into recovery so I was able to ota to 5.0. Do you think I have the wrong bootloader or what? I've ota to 5.1 now and still can't get bootloader to launch recovery. Also once in recovery I chose wipe cache and it rebooted phone not sure if that's normal. I came from nexus phone so just learning this moto stuff. I'll post a couple pictures thanks in advance. Basically if I want to flash back to stock telus or if I brick my phone and need to get to recovery I won't be able too. Hopefully just something simple. Also so what do I have to do to make these commands work [fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img. Only flash these when it's the exact version? /QUOTE]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Stop using the power button to try to select recovery like you would on a Nexus device - use the volume up button and you'll be fine
Hahah dang I feel dumb
So just to conclude if I did want to go back to fresh stock Telus. Would these [fastboot flash partition gpt.bin and fastboot flash motoboot motoboot.img still not work and not be needed? I understand motoboot is bootloader but what is got.bin?
If you go back to Telus firmware those two files likely won't update. I recommend you always go through the motions and if they fail it is fine to continue with the other files. When Telus 5.1 is released you will likely be able to update those two files again - it doesn't seem to really matter though with the 2014 Moto X.
Ok good information one question I have to ask. Does it really matter what fastboot I use and if so what is the best one to use for this phone?
Do you mean fastboot versus mfastboot(motorola specific version) ?
It only matters with the system image which is too large for regular fastboot and required the Motorola specific version which can handle the larger files and/or the sparse files.
Exactly the answer I was looking for. Thanks a lot!
Sent from my XT1095 using XDA Free mobile app
I have a unlocked bootloader US Moto X 2014 Pure Edition with stock recovery and currently non-rooted. No modifications to the system that I am aware of (NO XPOSED, ETC).
I went into SuperSu and did the complete unroot and rebooted and then tried to take the OTA and it was unsuccessful, as I figured it would be.
I am running System Version 22.21.11 victara_tmo.tmo.en.us and Build LXE22.46.11.
My question is this: I have requested the download for the 5.0 factory image from Motorola's website. Can I download it and then flash it with a similar process like I do with my Nexus 5 where I flash system, boot, bootloader, and radio and then take the 5.1 OTA? My goal is not to lose data or apps.
If I follow the commands on Motorola's website, am I going to lose data and apps? The commands would be:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot reboot
Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.
inertiamonster said:
Did you also uninstall BusyBox? I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
As far as flashing the factory image, as long as you don't flash cache.img or userdata.img you should keep all of your data, I just used the same method on my Nexus 9.
Click to expand...
Click to collapse
Thanks I'll try that! As far as flashing, I just follow Motorola's steps minus flashing cache.img and userdata.img and I should be fine right?
I also forgot to mention to make sure if the factory image comes with a flashing script be sure to check that it doesn't have a wipe command!!
Yes, since their method does not appear to use a script (based on what you pasted in the OP) you don't need to worry about it sending a wipe command or flashing images you don't want it to, just follow the manual flashing steps minus those two imgs if present.
I unrooted through Super Su and uninstalled BusyBox and it did not work. I guess I'll have to flash and then take the OTA to 5.1 when I get permission to download the factory image Maybe my root method was different from yours. I don't know.
Hmm, strange. Did you use CF-Auto to root? You rebooted after unrooting and removing BusyBox?
I honestly don't remember what I used to root. I'll reboot and try again and let you know what happens.
No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.
inertiamonster said:
I did the same thing last night, stock recovery, rooted with BusyBox, unrooted through SuperSu and uninstalled BusyBox, the OTA update worked perfectly and I just re-rooted with CF-Auto, good to go.
Click to expand...
Click to collapse
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?
Matthewlawson3 said:
No success. Will try to flash 5.0 and then upgrade via OTA to 5.1.
Click to expand...
Click to collapse
I may have a problem. I made a mistake in the flashing sequence and accidently booted instead of flashed the boot.img. So I reloaded into the bootloader and continued the flashing and now when I rebooted it goes to the logo and then turns off. Help me!
I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.
Matthewlawson3 said:
I reluctantly erased userdata and cache and got it to work again. However, when I booted up it was 4.4.4, how is that possible? I requested the right file.
Click to expand...
Click to collapse
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk
AGISCI said:
Not possible. You requested the wrong file.
Download 5.0 from here:
http://www.graffixnyc.com/motox.php
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
Thank you. I went ahead and just erased everything and upgraded to 5.0 by OTA then to 5.1 by OTA, but thanks again. I appreciate it.
onmyouji said:
Which one should I do first, unroot SuperSu or uninstall BusyBox? Do I need to reboot between those two steps?
Click to expand...
Click to collapse
I removed BB and then unrooted and rebooted, not sure if the order matters but rebooting is a good idea to make sure root is gone.
Hi everyone,
I have a problem with my Moto G 2014:
Many times the screen locks, and when i try to slide to open it, it will not open but gets locked again and again and I can't use the phone.
I had this issue with 4.4.4 and also after i updated to 5.0.2.
I tried:
1) factory reset.
2) clear cache partition.
3) I try to slide the option bar ad get to the settings but its not alway working to bypass the lock.
4) I tried also to cancel the "slide" option in the security setting to "none" but it still get locked..
what causes the issue? problem with the system? with some sensors? is it a fixable problem?
Did you try to flash stock/ custom rom?
Is your bootloader unlocked?
Have you tried re flashing the firmware. It's just a guess but your system partition may be corrupted.
Thanks you both
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
gifnooky said:
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
Click to expand...
Click to collapse
Well, restore to stock firmware with adb and mfastboot at it should be fixed.
Which model are you using? (XT1064 usa single sim, XT1068 international dual sim etc. etc)
The site for the official moto g stock firmwares is down so it is pretty hard to find a legit stock firmware file these days.
Here is one for the xt1064 http://www.rootjunkysdl.com/files/M...AWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
and one for XT1068
http://d-h.st/VOw (use the BLUE download now button not the orange download button. the orange one tries to get you to use dev host's bad download manager)
You can flash it by installing this 15 second adb installer by Snoop5
http://forum.xda-developers.com/showthread.php?t=2588979
If the latest version does not work then use 1.3
After you have everything downloaded open a terminal at the location you extracted the firmware. Reboot you device into bootloader mode by powering it on while pressing both volume buttons. Plug it into the computer and let the drivers install.
Run these commands. It is normal that the first two give you error if you are currently on 5.x firmware.
Code:
fastboot.exe flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img.sparsechunk.0
fastboot flash system system.img.sparsechunk.1
fastboot flash system system.img.sparsechunk.2
fastboot flash system system.img.sparsechunk.3
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
My model is XT1063
Is there a trusted original firmware to this version?
No solution found yet after searching for 2 months .
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
gifnooky said:
Is there a trusted original firmware to this version?
Click to expand...
Click to collapse
sumondhk1 said:
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
Click to expand...
Click to collapse
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
ethanchow said:
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
Click to expand...
Click to collapse
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
sumondhk1 said:
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
Click to expand...
Click to collapse
I know the screen ghost touches is hw problem but u asked for the original firmware.