After updating to CM12 my phone started having battery issues, someone told me to use mfastboot and flash back to 4.4.4 I did this and It worked, after a couple of updates I went back to CM12 It worked fine for about a week until I started to have issues with my battery again, so I tried to update the version of CM12 straight from the phone and it just turned off and died, I read on a thread in this forum that I had to use mfastboot again to be able to get my phone working, I did so but now everytime I get the phone to turn on it does not go past the "WARNING, BOOTLOADER UNLOCKED" screen.
I have used mfastboot to flash a 4.4.4 firmware, a 4.4.2 firmware and a 5.0.1 firmware, everytime I can do this succesfully, but when the phone reboots I see my self stuck in the Warning screen again.
If anyone can help me with this issue I would really appreciate it! :laugh:
Ok so Im thinking it might be a bootloader error, anyway I can flash the bootloader?
Related
I had really hard time naming this thread because I'm not sure anymore what's the problem.
I tried to update my Moto G (unlocked bootloader and rooted) to 4.4.2. First I unrooted the device by flashing stock rom using this guide. After I had succesfully updated to 4.4.2 I changed from dalvik to ART. When I tried to reboot, after the Motorola boot animation there was only a black screen. I tried to downgrade back to 4.3 with no success. Now when I try to boot I only get the "warning bootloader unlocked" sign over and over again. CWM recovery can't mount /sdcard/.
Have I bricked my phone or is there something I can and should do?
Thanks for the replies, I'm covered in cold sweat here.
EDIT: Seems I was too quick to make a thread. After editing the flashall.bat a little like stated in the thread I was able to flash back to stock.
Hey, I'm not really sure what I've managed to do, so any help is appreciated!
I have a UK Retail motog which I updated OTA to 4.4.2. I've unlocked the bootloader and flashed CWM from this thread: http://forum.xda-developers.com/showthread.php?t=2563599
I managed to mess some things up (can't remember exactly what I did now, I know I know... stupid.)
Anyway when I try to start the phone I get the long warning message about the bootloader being unlocked etc, then the screen goes black and it just reboots, again and again.
What should I do next? I still have access to the bootloader and recovery, so I hopefully all is not lost.
Edit: I should add, I tried to flash back to the stock 4.3 stuff from this thread: http://forum.xda-developers.com/showthread.php?t=2542219
But flashboot gives me an error about partition downgrade. I also tried flashing the system image itself but that didn't fix my problem.
Edit 2: Fixed by following these instructions: http://forum.xda-developers.com/showpost.php?p=49227024&postcount=127
Hi everyone,
I recently rooted my moto g and installed TWRP. The next day I get notifications saying that there is an update available and I downloaded it and installed it. The phone proceeded to shut down and install the update, but rather than the Android logo with the blue bar as I expected a long string of messages came from TWRP and I was dumped at the TWRP home screen. So when I reboot my phone the update hasn't installed and I was still being pestered by pop up messages to install the new update. So I came to the conclusion to un-root, install the stock rom as shown in the video "Flash your Tesco Moto G To Stock" by AndroidAndyUK.
I thought I should install the update without a recovery. The only problem is that when I go to install the rom like in the video, something goes wrong i guess and once its finished the "Bootloader Unlocked" white screen with red writing appears to go into an infinite boot loop. I flashed TWRP and wiped cache and everything then tried re installing the rom numerous times. At the fastboot screen three key things show in purple writing rather than yellow like in the video, which are:
version downgraded for primary_gpt
version downgraded for tz
version downgraded for boot
I can flash TWRP from ADB in my C drive but its not recognized by the command "adb devices".
At the moment I have an unusable phone and I would really appreciate any advice on the topic.
At the moment I have an unusable phone and I would really appreciate any advice on the topic.
Thanks very much.
Do not flash gpt.bin
Do not flash motoboot.img
Flash the rest as usual.
Last week I manually flashed 5.1 on my Nexus 5, because it was rooted an OTA update didn't work. It was working just fine, till yesterday. It's not rooted and it doesn't have custom recovery installed. My battery died and phone turned off. I charged it over night and turned it on in the morning. The phone was booting longer than usual so I left it and came back 2 hours later. It was still displaying boot animation. It's not restarting or anything, it just shows boot animation. I restarted it to bootloader, flashed 5.1 with Nexus Root Toolkit, the phone again stopped at boot animation. Then I went to cmd, used fastboot and erased partitions, flashed it again, it still didn't work. Then I flashed 5.0.1, it still stopped at boot animation. Then I flashed 4.4.4, it booted, play store didn't work, but I managed to install 5.0.1, this time over OTA. After it rebooted, guess what happened. It still stopped at boot animation. After that I installed TWRP, went to recovery, wiped ALL partitions and used TWRP partition repair function, rebooted to bootloader, manually flashed 5.1 AGAIN and my Nexus is still stuck at boot animation. I even tried erasing partitions, still didn't work. All flashings were done without any error reported. Any ideas what might be wrong? Bootloader and Recovery are fine, It boots without problems on KitKat. But I was using Lolipop without any problems for a few months now. Suggestions?
This is a strange issue. I did not found any solutions for that. What I have in mind is that backing up modemst1, modemst2, persist and misc partition then erase the whole emmc with boarddiag tool. This is a bit risky because if this error caused by a faulty emmc we may cannot reflash the bootloader after the emmc is erased because it will fail on some I/O error.
Hi guys,
I have a Moto G XT1039 (peregrine) 4.4.4
I unlocked bootloader, flashed Clockwork recovery and rooted.
Tried to flash Cyanogen but failed so went back to 4.4.4 and after updating Motorola Update Services tried to install 5.1 but failed again. Tried reflashing stock firmware and recovery but it still failed to update to 5.1. Maybe I got the wrong stock firmware, EU as opposed to GB...
Anyway, tried to flash 5.1 with XT1039_PEREGRINE_RETGB_5.1_LPB23.13-17_cid7_CFC.xml.zip using the following method http://forum.xda-developers.com/showthread.php?t=2542219
All looked good but after reboot it was stuck on Warning Bootloader Unlocked screen.
I'm now back in fastboot screen and tried again to use the above method but this time for XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip as this appears to be the correct firmware for my phone.
But in cmd I keep getting 'mfastboot' is not recognized as an internal or external command, operable program or batch file.
What can I do to get my phone working again?
Thanks in advance
Just realised I forgot to get the mfastboot... will try again.
Repeated the steps but with the 4.4.4 zip. It looked like a fail at first (had a dead green dalek with an exclamation mark in a red triangle on the screen) but after some waiting it started showing some signs of life and eventually booted up. The only problem is it has like a shockwave line constantly traveling down the screen. Any ideas why and how to fix it?
Repeated the flashing process once more with XT1039_RET-GB-SS_4.4.4_KXB21.14-L1.56-1_cid7_CFC_1FF.xml.zip but this time added mfastboot oem lock begin in front of other commands.
Didn't solve the line accross the screen but was able to download and install the 5.1 through the official channel.
All sorted now.
Was good talking to self
Over and out