[Q] Possible Brick - Need Help - Moto X Q&A

Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask

luizdf said:
Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask
Click to expand...
Click to collapse
Dude...this is sad.
You say that you followed @KidJoe 's excellent tutorial, but you missed the BIG ORANGE warning???
"NOTE: If you have Android 4.4.2 or later on your Moto X, do NOT attempt to downgrade the ROM version on your phone! Updated parts included with the 4.4.2 and above prevent successful downgrading to a lower version, causing you to either brick your phone, or set you up to brick later!"
You have very few options at this point. Any attempt to recover is going to leave you with mismatched partitions because you can NOT downgrade motoboot (bootloader) or gpt.bin (partition table).
Why oh why didn't you heed the warning?
Now your only option is to try using the manual method (OPTION 5) to flash everything from the 4.4.2 SBF except gpt.bin (which will leave you in a mismatched, but MAYBE working state) and hope that the 4.4.4 full SBF is released soon. Until then you will have mismatched partitions. And if you successfully flash the 4.4.2 ROM with the mismatched gpt.bin, you have a very good chance of bricking AGAIN if you take the OTA to 4.4.4. Don't do it! Assuming you are even able to get back to 4.4.2 and it works, don't take the OTA. Stay on 4.4.2 until the full 4.4.4 SBF is released....

It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.

luizdf said:
It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.
Click to expand...
Click to collapse
You are welcome. It looks like you got lucky. Just beware that the next OTA you accept could leave your device in a semi-bricked state. Keep your fingers crossed that all is well. There is no way to tell until you attempt to take the next OTA that is released (whenever that happens).

Related

[Q] Kind of a bootloop

Hey, i have my moto x about 2 months and i never experiencied problems with it, it is rooted and has xposed framework installed.Yesterday when i received the notification of the avaible ota update i clicked to download and then when it was over i clicked to install, after that the cellphone restarted all fine but then it was only a mather of seconds untill it power down and then power on . Can someone help me?
And you have a custom recovery?
Anyway...if you altered any system stuff with xposed, then right off the bat you can't do the ota.
You'll probably need to use fastboot or rsdlite to return to stock 4.2.2 with camera update. (The newer 4.2.2)....then do the ota. And yes....you're phone will be wiped...depending what you end up doing.
But...big but....read up carefully first ....you could brick your phone if anything you've done updated your boot loader....and then you take an OTA.
There's tonnes of update threads....best to read them all very carefully. And understand what you're doing before you do it. Several people have bricked their phones on here from not updating properly.
Good luck!
Sent from my Moto X cellular telephone...
Savassi12 said:
Hey, i have my moto x about 2 months and i never experiencied problems with it, it is rooted and has xposed framework installed.Yesterday when i received the notification of the avaible ota update i clicked to download and then when it was over i clicked to install, after that the cellphone restarted all fine but then it was only a mather of seconds untill it power down and then power on . Can someone help me?
Click to expand...
Click to collapse
ok you have 2 options
Custom Recovery
boot into what ever recovery you have and wipe the cache only and reboot your phone will be good as new.
Stock recovery.
boot into bootloader open adb and type command below
Code:
fastboot erase cache
reboot phone should be as good as new
Now to install the OTA you have to be stock with no root
so if you are on 4.2.2 Camera Update then flash that firmware via RSD LITE or fastboot method.
if you are on 4.4 and getting the 4.4.2 update then flash 4.4 firmware via the same as above then then take the update.
if you are just now updating to 4.4 and you want root then we need to complete some steps first so please let me know what firmware you are on so we can get you root also. also is your bootloader unlocked
man if i was a woman i would suck your nipples thank you very much i solved my probled woohoo
Savassi12 said:
man if i was a woman i would suck your nipples thank you very much i solved my probled woohoo
Click to expand...
Click to collapse
lol glad it all worked out enjoy your nipples

[Q] "Partition (recovery) security version downgraded" XT1060 VZW

We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
"Partition (recovery) security version downgraded"
Click to expand...
Click to collapse
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
fonixmunkee said:
We have a Moto X from Verizon. We built it with the Moto Maker and got it in December.
At that time, we immediately did whatever secret handshake to get root (something about downgrading). It's been humming along fine for the longest time. At one point, it appears, we took the OTA update and now root is gone. This has been the case for a while, and it hasn't been an issue. Now, the phone is trying to take the Android 4.4.4 upgrade, and the device keeps rebooting and displaying this error:
We've done some research, and believe I have a path to recover. We don't care about root or custom recovery any longer, we just want a working Moto X.
Question: since I'm on 4.4.2 currently (build KXA20.16-1.25.2), I'm assuming I can use the 4.4.2 FKZ to return to stock?
Here's the thread I used to help me make this determination: http://forum.xda-developers.com/moto-x/general/bricked-attempting-4-4-to-4-4-2-ota-look-t2660441
Can someone validate that I'm going down the right path? Thanks in advance for all replies!
Click to expand...
Click to collapse
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
samwathegreat said:
Use the FXZ that has been posted for your model: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
It is the only safe way to upgrade now that you are receiving the error, which normally indicates that you attempted to downgrade.
If you use one of @SamuriHL 's tools, you can KEEP your data, just like you would if you used took the OTA.
Click to expand...
Click to collapse
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
fonixmunkee said:
Thanks for the reply, samwathegreat. After conducting a bit more research, I saw your name pop up a few times assisting people with a similar error.
So if I may ask a follow-on question, should I use the FXZ for 4.4.2, or can I do the 4.4.4 one? I'm currently on 4.4.2, receiving said error, while attempting to upgrade to 4.4.4.
Click to expand...
Click to collapse
You should definitely use the 4.4.4 FXZ from the link I provided you. If you do this, you will be on 4.4.4 running smoothly in no time at all...
Thank you, @samwathegreat! You had the fix:
1. Download the 4.4.4 FXZ from here, even though we were on 4.4.2: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
2. Follow the steps to use RSD flasher from @SamuriHL. Follow them to the T: http://www.droidrzr.com/index.php/topic/48904-rsd-flasher-beta-windows-only/
Our Moto X is now running 4.4.4 stock. Thanks to @samwathegreat & @SamuriHL!

[Q] Hard Brick? Flashed stock and OTAed

So I didn't read any guides and was following an old YouTube video on how to go back to stock and OTA. Unfortunately the link was for an older version of the Moto X Toolkit and it took me back to 4.2.2 and I accepted the OTA. gg.
I have tried flashing 4.4.4, 4.4.2, 4.2.2 again from fastboot and in the end the result is the same: a flashing dead android popping up every few seconds that says error. After reading the Q/A I think this is a hard brick but has there been any updates on ways to fix this?
I can't USB mount to put in a custom rom either and it won't let me sideload since the USB mounting isn't working. I can flash custom recoveries but that's about it.
Thanks.
Not researching first on any device is a mistake for sure... Especially the X. You've done the procedure that guarantees bricking a Moto X unfortunately.
This thread may be your only hope now...
http://forum.xda-developers.com/showthread.php?t=2629057
Good luck!
I looked into this method but couldn't get it to work since it wasn't recognizing the phone when I plugged it in. I did manage to unbrick it somehow by flashing a 4.2.2 version again using the toolkit (post camera I believe). I managed to boot up again in 4.2.2 but not really sure how to upgrade to 4.4.4 at this point without bricking again.
Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .

XT1053 OTA 5.1 update unsuccessful

Hi
I've run into a problem while trying to update my Moto X (gen 1) XT1053 from 4.4.4. to 5.1. through standard OTA update. Here is the scenario:
- My phone is not unlocked or rooted, nor does it have modified firmware of any type. It is a fully stock XT1053 purchased directly from Motorola in the US that I have not tinkered with in anyway
- My phone downloaded and applied the update on Saturday morning and after the first section of the install rebooted. It sat at the screen with the M and "powered by android" at the bottom and vibrated once, then the screen went off, the same screen came back on and the phone vibrated again. Then an Android on it's back with a red exclamation and "Command" was shown.
- I figured out how to get into the recovery menu and wiped the cache, rebooted and no change. I then attempted to factory reset the phone, it did this but again no change.
- I spoke with a Motorola chat representative who was unable to help but I managed to follow some instructions on this forum to enter the fast boot menu, download and re-flash android stock 4.4.4 using RSDlite and get the phone working again.
- The phone attempted to apply the 5.1 update again yesterday and encountered the same issue again.
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Did you try going to settings and about phone, update
Sent from my Nexus 4 using Tapatalk
Correct, the update was applied through settings > about phone > system update
Delta117nz said:
Would anyone have any ideas about what could be going wrong with the update process? Or ways that I can go about getting this to install correctly. The motorola rep seemed to think it was to do with my carrier, but as it was downloaded over wifi can this be the case?
If not, would anyone know how to stop android from continously prompting me to update to 5.1? I'm happy to remain on 4.4.4. if it means the phone will still remain functional.
Thanks in advance for your help.
Click to expand...
Click to collapse
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Thanks dtg7, I'll give that a try in the next day or so (updating via the recovery menu) otherwise will hold out for the 5.1 firmware and try RSDlite again.
dtg7 said:
If you prefer to stay with a working 4.4.4 then you can try disabling some apps related to the OTA, like I think Motorola OTA used to be there although I don't see it now in 5.1, or Motorola Update Services, which now looks like you can't disable but anything you can't disable you can try unchecking "Show Notifications", and so on. if you check around the forum you'll find something that works.
On the other hand if you want to try to get 5.1 working you could try applying the OTA from recovery. while on 4.4.4 you download the OTA (see this post http://forum.xda-developers.com/showpost.php?p=61304089&postcount=864 ) and then boot into stock recovery and choose to apply update from sd. hopefully it will work that way. ***Be aware however that by going from your failed 5.1 update back down to 4.4.4 as you said you did, you have put your phone at risk of bricking when you try to go back up to 5.1. since you've already tried it once, you might be willing to try it again, but just know that there is that risk and its on you if it bricks and you lose your working 4.4.4
Oh and you do have another option, you can stay on 4.4.4 until Motorola releases the whole 5.1 firmware or someone managed to get it, then you can flash 5.1 firmware with rsdlite like you did with 4.4.4
Click to expand...
Click to collapse
Worked perfectly downloading the OTA update and applying through the recovery screen. Thanks for your help

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution
cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...

Categories

Resources