XT1092 flashing (as in on screen flashing) recovery "no command" screen. Bricked? - X 2014 Q&A, Help & Troubleshooting

XT1092 flashing (as in on screen flashing) recovery "no command" screen. Bricked?
Apparently I did something stupid. I had 5.1 which didn't OTA on its own to 6.0. So I thought it maybe had something to do with a past root i had and TWRP recovery. As solution I went and flashed a stock 5.1 rom in fastboot, which worked fine. Still no OTA though, and adb sideloading gave a status 7 error. Then I fastbooted the 6.0 stock rom, but that wouldn't boot (phone would hang in the white "unlocked bootloader" warning screen. I re-flashed 5.1 in fastboot.
Probably not a smart move, cause now I'm stuck in a bootloop to recovery mode where it's flashing the "no command" recovery screen for a fraction of a second, then black screen for 4 seconds, repeating over and over. I can trigger some orange log error by pressing VOL*UP like when you go to recovery mode, but it disappears in the bootloop. (it says qe 1/1 though, which suggests its rooted I read somewhere). So I can't do anything with it anymore. I read tons of threads here of which I found 2 with a similar problem:
http://forum.xda-developers.com/moto-x-2014/help/xt1092-flashing-command-boot-attempt-to-t3259287
http://forum.xda-developers.com/moto-x-2014/help/possibly-soft-bricked-moto-x-flashing-t3195103
It's the same problem I have now, and one of them says that "with some luck" he got into fastboot, but doesn't describe how.
Googling "flashing" related to recovery and/or "no command screen" in this context does'nt yield much result unfortunately.
For the love of god, I can't get it into fastboot mode anymore to do something/anything about it. I pressed, hold, tapped POWER and VOL*UP on countless ways, and it does a "deeper" reboot with appearance of the white unlocked bootloader screen, but it just keeps bootlooping.
How can I fix this? Did I brick it by fastboot flashing 6.0 and then fastboot flashing 5.1? Is it hard bricked and useless?
What do I have to flash when I manage to get in fastboot?

OK, I fixed it. Discovered it when the battery was drained. When the phone is OFF, holding POWER+VOL*UP+VOL*DOWN for 5 seconds and then releasing triggers the fastboot. Problem then is that you can't flash anything cause the battery is nerely depleted. So I let it charge in the bootloop for a bit and I found out I can hard reboot and get into fastboot by holding POWER+VOL*UP+VOL*DOWN for about 10 seconds and then releasing it. It probably turns off and then triggers the fastboot/bootloader mode.
Afraid of bricking it with OTA as I've downgraded to 5.1 from a (non-functioning) 6.0 I've manually flashed a 6.0 stock ROM in fastboot using this guide including mfastboot. So no sideloading or anything. Now it properly boots and I've got a stock 6.0.
Hopefully this helps someone in the future.

Related

[Q] Cant get into recovery, Logo graphical error on boot

Hey guys, I'm having trouble with my nexus device, I was watching youtube on it and it froze and now doesnt boot. I can access hboot, but recovery just shows the X logo and restart. I've tried reflashing boot.img, reflashing the recovery, reflashed stock hboot, flashed new roms from fastboot. I've also tried passimg.zip, and flashing a different radio but it stops 90% the way through, and it gets stuck in loading passdiag.zip if I use the volume down button to boot instead of the trackpad button.
The graphic abnormality is like an artifacting. If you search youtube its called "Nexus one stuck on X, can't boot to recovery.", I cant however post a link.
Anyone encountered this before? Any insight is appreciated.
well I've managed to remove blackrose at least, and to get to the blackrose menu. You have to access it from command prompt with "blackrose.exe skip" while in fastboot. Though I'd put it here incase it helps someone else in a similar circumstance.

[Q] stuck on 'Erasing...', flashing doesn't help

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.

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.

Can't get into recovery

Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
ibphantom said:
Hey all
I'm updating to May Updates using This Guide and then plan to update to June.
Problem is that I send 'adb reboot recovery' and the phone restarts, shows the start up screen, then the Google logo, then restarts without ever showing the android logo.
I can get into Fastboot mode and try to select recovery with the volume and power, but again, it boots to the google logo, then back to the unlock warning and boots to my lock screen, never going to the android logo.
Ideas?
Click to expand...
Click to collapse
Make sure you are using the latest adb/fastboot binaries (April, 2020). Flash the stock boot.img from the same guide. You will be unrooted but will be able to boot into System. Now read up on how to patch your own boot.img, it really is very simple. Personally I do not depend on, wait on, or use OTA's. The full image is available the first Monday of every month, and I extract/patch the boot.img from it. The whole operation including rooting takes just a few minutes. It's just one extra step. Once you get the pattern down it can be done very quickly, consistently and you're not depending on someone else's files. If you are bound and determined to use this method, you should seek out more guidance in the tutorial thread itself. Good luck. :good:

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