[Q] Can't boot - Moto G Q&A, Help & Troubleshooting

I have a Moto G 2013 (XT0133).
I was trying to install CM12 on it using TWRP recovery. I used this (youtube: /watch?v=ix7rrKS4keI) method.
It failed. Now I'm stuck on the "Bootloader unlocked" message and my device won't boot. How can I fix this? Do I have to wait for the battery to drain and then recharge my phone, boot into TWRP and flash the backup? Or is my device just bricked?

Can you boot into recovery? If you can, try wiping cache, Dalvik, and data to see if it boots.
If the phone doesn't boot, I suggest flashing back to stock 4.4.4. Do not flash anything lower than 4.4.4. Try to find your ROM here: See if you can find the stock 4.4.4 ROM from here: http://www.filefactory.com/folder/c6...how=100&page=1
Did you update your bootloader from Kit Kat to Lollipop before trying to install CM12?

I can't stop it from booting, it is just stuck on the "bootloader unlocked" screen. I made a backup, wiped everything except for internal storage (CM12 and GApps .zips were there) and then tried flashing the CM12 zip. After it failed, it said "no system" and the phone rebooted.

whatgabe said:
I can't stop it from booting, it is just stuck on the "bootloader unlocked" screen. I made a backup, wiped everything except for internal storage (CM12 and GApps .zips were there) and then tried flashing the CM12 zip. After it failed, it said "no system" and the phone rebooted.
Click to expand...
Click to collapse
There is some 2-3 seconds when device is off, when creen goes dark then turn vol- and power and after 3 sec left power off

You can't boot into fastboot? Booting into fastboot does not show the unlocked warning.

Related

XT1032 brick after downgrade from Marshmallow

Hi guys, that's my first theard.
I installed CM13 a few days ago, the 20160102 nightly, but its didn't like me so much, my past ROM Slimsaber 5.1 had more features so I preferred it, and today restored my backup from that ROM.
It boots well but when finished to configure all apps it reboot into bootloop, i tried to wipe cache/data but nothing happened.
Then I tried to flash the firmware that I was using (BRAZIL 5.1 retail) and it flashed ok, with no problems. But when I reboot it stays in "bootloader unlocked" image. I tried to flash it again and didn't stay at the "bootloader unlocked" image, but its shows me a screen with a broken Android with the phrase "No command" and immediately disappeared, and then again, like an infinite loop. I don't know if this is useful but, when I turned off the phone to restore the backup I did it with the advanced Reboot menu into Recovery, is it related?
I know that it said, in the CM13 theard that IT CAN NOT BE DOWNGRADED, so I did the backup with TWRP, but I don't know why it bricked. Also I though it could be downgraded by flashing.
Thank you. I hope you can help me!
If you need some info about my phone please request it.
PD: Sorry for my bad English, is not my native languaje.
Edit: Now I connected it to my PC in bootloader mode, and force a reboot with fastboot and its shows the screen with a broken Android and the phrase "No command" and immediatly dissapered, cause if I try to "Normal Powerup" in the bootloader mode its shows the white screen of the unlocked bootloader.
Edit 2: Also I tried to install TWRP, and when I reboot with fastboot, the phone goes directly to TWRP, so I think is bugged or something, since I did reboot to recovery in marshmallow.
Have u fixed ur Moto G ?!

T-Mobile Pixi 7 (9006w) - softbricked after OTA attempt-Resolved

Well, I put the tablet back to stock and then ran through the OTA. The update never completed and softbricked it, will only boot into recovery. I have cleared cache/data/userdata/system/boot/recovery and reinstalled stock ones (fastboot flash .IMG files) and still boots to recovery. Stock recovery says "installing software update" and then "Error!" with the red triangle, TWRP and CWM work fine, but it will never load to Android. It is like the Bootloader is stuck in update mode and won't boot to android until it completes. I have tried to restore a Nandroid (TWRP) and it still just boots back to recovery. I have no luck with anything, though the fastboot flash process completes without issue.
Thanks to @aclegg2011 & @YarsRevenge78 for the files and instructions/information. :good:
Any Ideas?
Anybody?? I need to get this thing working again.
I do have another one to pull stock images from.... anybody?
Apparently, all I had to do was just let it sit at the "Error!" screen until it ran through the installation and came back to the stock recovery screen. I then wiped data and cache then it rebooted fine, minus my data. Thanks anyways.
DJ_SpaRky said:
Well, I put the tablet back to stock and then ran through the OTA. The update never completed and softbricked it, will only boot into recovery. I have cleared cache/data/userdata/system/boot/recovery and reinstalled stock ones (fastboot flash .IMG files) and still boots to recovery. Stock recovery says "installing software update" and then "Error!" with the red triangle, TWRP and CWM work fine, but it will never load to Android. It is like the Bootloader is stuck in update mode and won't boot to android until it completes. I have tried to restore a Nandroid (TWRP) and it still just boots back to recovery. I have no luck with anything, though the fastboot flash process completes without issue.
Thanks to @aclegg2011 & @YarsRevenge78 for the files and instructions/information. :good:
Any Ideas?
Click to expand...
Click to collapse
where can i find the fastboot imgs?
http://forum.xda-developers.com/showpost.php?p=62474058&postcount=45

Bootloader,TWRP are not working and device is stuck in bootloop

Hi,I have a XT1033 indian dual sim model(for specifics),It was running cm13 nightly latest,twrp 3.0.0-2 and bootloader 4.18
So I was watching youtube when suddenly the cyanogenmod booting symbol came,At first I thought I may have been holding the power buttton but after muh time i force shutdown it and restarted but it has been in bootloop since then, so I thought maybe it was problem with cyanogenmod and I thought of reinstalling cm13 fresh,so I booted into TWRP and chose wipe, advance wipe and selected to erase all partitions, it says erasing was succesfull but nothing has been erased,So i thought of flashing stock firmware using fastboot and I did everything was successful so I reboot the system but it still showed cyanogen mod bootlogo and it was still in bootloop.I thought it was a hardbrick and tried to use the bootloader bricker and use flash-blank.bat but bootloader bricker too does not work. Please help me,I have a busy week and my phone is very important to me.

Stuck in Bootloader

Okay, so I have a Boost Mobile Moto G (Falcon) and I unlocked it, flashed TWRP, and installed SlimROM. I forgot to activate the phone before flashing it with Slim, so I tried flashing the stock 4.4.4 ROM. When I did, it had an error 70 I believe. I then flashed the ROM manually using CMD, and when I rebooted it, it only flashed the Android with the text "No Command" under it. It's just flashing it over and over till I power the phone off. I've installed another recovery (CWM), but when I try to boot into it, it says "Boot up failed".
Is there any possible way to fix this? I made a backup using TWRP, but I accidentally erased it. Right now I'm stuck in the bootloader.
Internal storage also doesn't show up.

Bootloop

Okay I am in a situation. my Google pixel is constantly boot looping. I have tried custom roms and even stock ROMs and it keeps boot looping. I've done all the tutorials and troubleshooting threads and to no avail am I getting this to stop. My bootloader is unlocked and I cannot flash any firmware that is stock below Android 10. I thought with the unlocked bootloader you could flash almost any firmware. Does anybody have any idea on how to help me and what I could do?
After trying to flash an OTA or a factory image it keeps saying something about user data and then it says press any key to exit.
I finally fast boot twrp and sideload lineage 17.1. after flash it rebooted... usually twrp flashes and waits for you to pick reboot. Phone works but is it a matter of time before it does the bootloop again? Clicking fix bootloop recovery seemed to work.

Categories

Resources