[Q] stuck on 'Erasing...', flashing doesn't help - Moto X Q&A

Hi
I have an AT&T XT1058 with locked bootloader, on 4.4.4
I tried to rest it to factory, but it got stuck on 'Erasing...' (with the little droid) for more than an hour, so I reset it.
Since then it won't boot, only keep stuck on 'Erasing...'. I've tried reflashing it with ATT_XT1058_4.4.4-KXA21.12-L1.26_CFC_1FF both using RSD lite and manually using mfastboot, but no luck - the phone still boots to 'Erasing...' and sometimes after that to the recovery.
I didn't find anything in relevant threads. Does anyone have an idea?

Selecting 'Factory' in the bootloader seemed to fix it.

It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery

mokagi said:
It is more comlicated than that
The phone does boot after selecting 'factory' in bootloader, but only once - turning the phone off and on again brings it back to its 'erasing...' state. Besides that the phone seems to not be able to charge the battery
Click to expand...
Click to collapse
Were you able to get this resolved? I have a xt1095 doing the same thing when I flash a stock recovery. Just shows the android guy and just stuck at erasing... When I flash TWRP it doesn't get stuck at the "erasing..." anymore but just boots straight into TWRP.

Sorry for the late response, I missed the notification on your message.
I wasn't able to fix it, returned it to motorola.

Related

[Q] NEED HELP!!! moto x screen went black and is unresponsive

can somebody please help me? my screen just went black at work today and it does nothing at all now. if I hold the power button it vibrates once. if I hold power+volume down I get to recovery. I tried to reboot from there and I get the unlocked bootloader warning screen and from there it just goes to a black screen. so I get back to recovery and installed my back up and that didn't help at all. somebody please help me.
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
jeb192004 said:
Im not getting the M logo. Not bootlooping. just get the warning bootloader unlocked screen. sits there for 10 seconds or so and then screen goes black. that's it.
to flash the system, boot, and recovery images. am I getting those form here:http://forum.xda-developers.com/showthread.php?t=2452246
Click to expand...
Click to collapse
just downloaded and opened that up. I don't think that's it....
Steve-x said:
So the bootloader is unlocked, what else have you done to the phone?
You may need to reflash it with rsdlite.
Click to expand...
Click to collapse
the only thing ive done to the phone is put xposed framework on it and gravity box. that was prob a month ago tho. this is the first prob ive had with the phone.
You may want to follow this guide to return the phone to stock firmware:
http://forum.xda-developers.com/showthread.php?t=2446515
You could also try commenting out the line that overwrites user data so you don't lose your data.
Try plugging your phone into the original charger and then boot to recovery, from their try rebooting while still plugged in. If that doesn't work try this again but wipe just the caches and reboot while plugged in. I have had a screen go black before on other devices and plugging the original charger(car and most others didn't work) in and booting to recovery then rebooting would get it working again.
PS When you boot to recovery check your battery level.
well...I used the moto x toolkit and returned to stock using that. everything booted up. so far everything is looking good. lost all my data but that's not that big of a deal.
640k said:
OP you need to provide more details. are you getting the M logo? is it bootlooping? is the phone doing ANYTHING but getting in to recovery?
load the fastboot menu and use mfastboot to flash the system, boot and recovery images. you should be able to bring the phone back to life without losing data.
Click to expand...
Click to collapse
Well im with the same problem but i got the M logo and is not stuck in bootlooping.... right after the boot it goes black...

Bricked; cannot get into fastboot

So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
slak? said:
So today I set about unlocking the bootloader and rooting my Moto X 2014 Pure Edition XT1095.
Unlocking the bootloader went just fine. Then I went to root it. I booted the pure2014sb.img but it didn't work. The phone would just hang on the Motorola logo. Then I read somebody later said that doesn't work on lollipop, so I booted the CF-Auto-Root-victara-victaratmo-xt1095.img instead. That showed me the rooting status page thing before it rebooted, and then rebooted again, but when it fired up after that it was still hanging on the Motorola logo.
Then I attempted this http://forum.xda-developers.com/showthread.php?p=56928477#post56928477
Now the phone will not even hang on the logo, it gets to the animated moto logo part and then turns off half way through. I cannot get back into fastboot state either. It just doesn't respond to power + vol down at all.
EDIT: Actually scratch the not being able to get into fastboot state thing. I just had to hold the buttons down for way longer than normal. I just kept holding them until it showed something. It ended up being like 15 seconds instead of 3-4 like usual.
Help!
Click to expand...
Click to collapse
Same happened to me early this morning when I was trying to install 5.0.2
You have to flash any firmware you want just avoid to flash the modem and there ate several post here in the general section
Just remember. Don't flash the modem unless is the same firmware you have or else you will lose signal.
Regards
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
slak? said:
Thanks for the input. I used the instructions in this thread to get my phone back to working condition:
http://forum.xda-developers.com/moto-x-2014/general/guide-update-xt1095-pure-edition-to-t2937074
I was unable to get it to pick up the 4.4.4 to 5.0 update zip in recovery mode, so I just used the regular OTA update to do it. After that I booted the CF-Auto-Root-victara-victaratmo-xt1095.img and it worked!
Click to expand...
Click to collapse
Great! Glad it helps
Enjoy the lollipop Sweet my friend.

Phone memory seems to be read only

As I said in the title. The phone's memory seems to be read only.
I can access the fastboot mode of the phone and issue commands like flashing the recovery but it doesn't seem to update anything on the phone even though I get the "OKAY" message.
My phone is unlocked and until last night I was running CyanogenMod on it just fine. But now I can't flash a new recovery or access it. I have TWRP installed but everytime I try to boot into recovery the phone gets stuck on the logo screen and flashes every couple of seconds.
If I try to start my phone normally I get the cyanogenmod logo on start up (even after flashing stock) and the phone never actually boots up.
Anyone had the same problem before? If you need more details I'll reply ASAP.
My phone is the retail European XT1068 Dual Sim. Thank you in advance for any help.
Same issue here (I'm MrPowerGamerBR on Reddit), the more I read about trying to fix this issue, the more I start thinking "this phone is dead, move on..."
There isn't no fix for this, the only way to fix is replacing the logic board.

Stuck on LG Bootscreen only download mode, LGUP didn't work

Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Ditto
FUZER384 said:
Hey Xda-ers,
I'm freakin out about my phone. I was using hangouts this morning and it just rebooted itself and got stuck on boot screen. It has NEVER done this before and always worked fine. I was on USS Enterprise ROM I believe. I can only get into download mode, so naturally I tried to flash stock h81120o (the version I was already on and rooted) and LGUP completed fine. Only my bootloader was still unlocked and it still was stuck on boot screen. Does anybody know what I can do to at least relock the bootloader so I can do a warranty claim with T-mobile....or get my phone back working if this is not catastrophic.
Oh I also tried holding down & power, no recovery...and cannot use the buttons to factory reset either. Then it loops and get stuck again.
Click to expand...
Click to collapse
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
hypervi said:
Did you ever find an answer to this ? Almost the same thing happened to me , i updated H81120p Extreme and phone booted back into Boot Screen and stayed there forever. I tried flashing H81120p using LGUP but am stuck on boot screen still.
Click to expand...
Click to collapse
infamous bootloop, hardware issue.?
raptorddd said:
infamous bootloop, hardware issue.?
Click to expand...
Click to collapse
How can i tell if this is indeed a hardware issue ? I am guessing it is though also the serial number falls in the problem range.

Pixel 4 XL won't boot anymore

Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.

Categories

Resources