Database Info

[Q] Moto G bootloop on stock firmware (Troubleshooting)

Hi,
I've been searching the web for a few days and tried many things, but so far I haven't been able to fix my Moto G.
My device:
Moto G (XT1032)
DE distribution
single-sim 8GB variant
Stock firmware was Blur_Version.14.71.8.falcon_umts.O2.en.DE or Blur_Version.14.91.11.falcon_umts.O2.en.DE (not sure)
What preceded the problem:
Something like a week ago I turned on my Moto G for the first time, checked for updates to KitKat but no updates were found
I forced checkin several times, rebooted the device, still no updates found.
Updates were available on the web for several weeks, so I thought I would update manually.
I unlocked bootloader (didn't know I didn't have to)
Downloaded KitKat rom for a single-sim variant from o2 DE distribution
Flashed firmware using motorola version of fastboot (didn't forget to clear the cache and userdata)
All went fine and I was able to boot to KitKat
When it happened:
I was tinkering with developer options, probably switched runtime to ART (not sure)
I rebooted the device (manually or when switching runtime)
Device stuck in a bootloop
What doesn't work:
Stock recovery (bootloop, 4.3 and 4.4 firmware)
CWM recovery (bootloop, both with motoboot.img for 4.3 and 4.4)
TWRP recovery (splashscreen flashing, both with motoboot.img for 4.3 and 4.4)
CM 11 (bootloop)
What works:
Philz recovery (http://forum.xda-developers.com/showthread.php?t=2639583, when this recovery is flashed, device boots straight into recovery)
ADB (in recovery)
What I've tried:
Flashing many, many firmwares. Triple checked if I didn't miss anything.
Factory resets, partition formatting (In philz recovery).
Rooting the phone
Checked whether eMMC chip is corrupted through ADB shell (dmesg | grep mmc0), seemed OK, no error messages (http://forum.xda-developers.com/showthread.php?t=1284196)
Using 4.3 motoboot.img with cyanogenmod and recoveries that doesn't work
Flash stock firmware and install OTA 4.4 update in philz recovery (seemed promisingly, took longer than flashing full firmware)
Where I may have had screwed up:
- After few initial attempts to fix my phone failed, I tried corrupting the bootloader to get to download mode as suggested here http://forum.xda-developers.com/showthread.php?t=2623587 and correct it.
I would be glad for any idea C'mon, you are some smart guys, we can do it!

Try to flash stock 4.4 firmware, do not flash any recovery after flashing the stock 4.4 and see what happens
I've experienced something like that, and after reflashing the stock many times i fixed it

sounds like my problem exactly. what did you do, return the phone?
how does flashing stock repeatedly help? which stock? which method (does it matter if you do it from fastboot or in philz or some other way?)

I have the same problem, could u solve this? plsssss HELP MEEEEE

[Q] Help! My moto g is hard bricked after flashing CM12

I rooted my phone by unlocking my bootloader, putting philz touch recovery, and flashing superSU.zip. After using my phone with root for a while, i noticed that some things were really unstable and buggy, such as it wouldn't charge, so i decided that i might as well flash cyanogenmod 12 since i have a recovery. This was my first mistake, as flashing cyanogenmod put my phone into an infinite boot animation screen. I then used adb to sideload the official Motorola 5.1 update. But this also gave me an infinite bootloop. I tried flashing cyanogenmod 12.1, that also didnt work. I tried flashing stock android 5.1, also bootlooping. I did some searching and i found that my bootloader was not recent enough to flash lollipop roms. So i tried again after updating my bootloader, and now its even worse. It doesn't even attempt to start up, it just goes straight into recovery mode as soon as i boot it up. It also has this strange screen flickering/glitching going on, like this. I don't even know where to go from here so any help would be greatly appreciated.
Some extra info:
I did clear all cache before flashing.
Model number is XT1032
Bootloader version is 4118, before it was 4113.

I recommend flashing a stock 4.4.4 ROM to your phone using fastboot commands. Do no flash anything older than 4.4.4.

Flash cm11 first. I had the stuck at bootanimation. On cm 12.1 flashed 11 then wiped and flashed 12.1 and all is Good

[Q] Boot Loop Leads to Other Issues

The issue:
Phone is boot looping regardless of ROM. Additionally, if I use the torch, I have to reboot the phone to turn it off, and the camera is unable to load. -- The boot looping isn't always during the boot cycle, but sometimes a few minutes after the phone starts.
Backstory:
A few days ago my phone started to randomly boot loop. I was running one of the OTA of cm 12.x with TWRP at the time. After the issue started, I originally thought it was due to the upgrade to cm 12 and tried reverting to cm 11. This did not correct the issue, so I've tried a few other things since.
First I tried the method in this thread: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 however, while the batch job was running, the device became unresponsive. After an hour of waiting I unplugged the device which sort of hard bricked it.
To recover from this brick, I tried the method in this forum: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
This allowed me to boot my phone into color OS with no apparent issues (I didn't test extensively). Following this, I tried using fastboot to put XNPH22R on it by flashing the files individually following the first guide.
I am currently left with XNPH22R, and the phone appeared to be working fine - the flashlight bug was fixed, and it wasn't boot looping. Unfortunately, while I was setting it up (I didn't do it at first because I wanted to test first), it began to boot loop again.
Does anyone have any advice? Additionally, while flashing the individual image files, I erased and formatted them first to give myself a clean install. Are there any other ones I may have missed that could be cleaned to fix this issue?
Thanks.
EDIT: Now my phone is freezing up in twrp as well. Additionally, the bootloader is locked and fastboot oem unlock is not unlocking it, and there is no OS because it froze during the flash from twrp.

Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app

tr.supradeep said:
Naturally the first I would ask you to do is:
1. Flash a Custom Recovery
2. Update firmwares to the latest ones (I guess May)
3. Update your ROM to latest Stock ROM or a Stable Custom ROM.
I have a strong feeling that mismatched firmware version could be causing this problem. I had a bootloop problem due to that.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I agree that it is likely a mismatched firmware given the issues I have seen with the torch and camera. However, I think I may have a misunderstanding of what the firmware is on Android. I thought it was the underlying linux kernel, which from what I'm seeing is the boot sector. If this is the case, wouldn't the fastboot flash boot boot.img replace the firmware with the appropriate version for the ROM? If not, can you please explain this further? Usually my experience with custom roms stops at loading a custom recovery and then simply flashing zip files from that.
Additionally, I have twrp as my recovery.

Help: CM 12.1 Nexus 5 stuck in bootloop and freezes on TWRP load screen

I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami

Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?

audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.

Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.

Mi4i Stucked in Bootloop

I attempted to switch custom rom and end up in a brick situation.
What actually happened:
I rooted my device and installed twrp successfully.
Then I found this thread: https://forum.xda-developers.com/mi-4i/development/rom-lineageos-15-0-t3671815
I was really interested in switching to custom rom and downloaded all necessary stuff.
(Here comes my mistake) I boot to twrp and flashed the latest firmware (8.1.5.0), wipe cache, latest rom build (LOS 15.1),wipe cahe,gapps,wipe cache and reboot to system. (all process altogether)
Now device stucked at MI logo and never booted to system again. And unable to boot to twrp mode too.
What i tried to resolve(but failed):
Device was showing lineage battery icon but nothing else was happening. So i decided to return back. I flashed my device with latest stock flashboot rom "ferrari_global_images_V9.2.3.0.LXIMIEK_20180414.0000.00_5.0_global_680c582f20" and successfully flashed it as while charging i got led light back and stock battery icon but issue remain the same. Stucked at boot loop.
I also tried Fastboot Flash Through CMD-Prompt https://in.c.mi.com/thread-334-1-0.html
But still not working. I think it must be due to firmware upgrade to oreo and if downgrade is possible, issue can be resolved but not sure and don't really know how to execute that.
Please help me in solving this issue and whatever suggestion you give please provide proper guidance or link to guidance as I'm still new to all this.
Video showing bootloop on mi4i device : https://drive.google.com/open?id=1ufwk8TNIUmycJUdjTmDBXj38-1cPCrBu