I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Knight71 said:
I think I bricked my phone but im not sure if its a soft or hard brick. I got the phone and it had Droid 4.2.2 on it and then unlocked the bootloader. I then installed all of the updates to it and then rooted it with TWRP and SU. I got a stock image for my phone for 4.2.2 then I flashed the system image and all was ok when I rebooted the phone It just hung there so I then tried to go into recovery and that worked and I then tried to do a factory reset and it just got stuck in a bootloader loop it would turn on and then the bootloader warning came up and then it would be blank screen and then the bootloader warning would come up again and repeat. I am able to still go into fastboot and TWRP but I did not back up the image. Any ideas...Im a noob and I dont want a 650 dollar paperweight.
Click to expand...
Click to collapse
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Lokke9191 said:
Don't worry. There is no such thing as a soft brick. It's either bricked or its not. If a phone is bricked, it does nothing at all. In your case download the factory images to your pc again to make sure you have a clean download and fastboot flash them onto your device. I'd flash the files individually and restart the bootloader between each file. Then clear the cache and reboot.
Click to expand...
Click to collapse
Ok...I got my phone up and running again. If I told you what I did to get into this situation you would just laugh. So I redone everything typed out the code and 2 items failed...I dont know if this is good or bad but my phone is up and running sort of....
OK..........fastboot oem fb_mode_set
FAILED....fastboot flash partition gpt.bin
FAILED....fastboot flash motoboot motoboot.img
OK..........fastboot flash logo logo.bin
OK..........fastboot flash boot boot.img
OK..........fastboot flash recovery recovery.img
OK.......mfastboot flash system system.img
OK..........fastboot flash modem NON-HLOS.bin
OK..........fastboot erase modemst1
OK..........fastboot erase modemst2
OK..........fastboot flash fsg fsg.mbn
OK..........fastboot erase cache
OK..........fastboot erase userdata
OK..........fastboot erase customize
OK..........fastboot erase clogo
OK..........fastboot oem config carrier vzw
OK..........fastboot oem fb_mode_clear
I then rebooted the phone and went threw the whole set up new phone process. I then unlocked developer mode did the google playstore updates. Meanwhile the phone is downloading OTA update. I did not want to install that update because I am now on 4.2.2 - 12.15.15 because I want to use FoxFi to teather my phone to my laptop using Wifi and KitKat turns off Wifi. I am having some problems with that app because now I have to set a pin password to lock the phone instead of swipe. And the other problem is that when I went back in fastboot and setup TWRP in the recover partition it just keeps rebooting into that partition like a loop not the system partition like it should. So now I dont know how im going to root my phone so I can freeze my OTA update with Titanium Backup. unless there is another way of doing it to get rid of the OTA. But I still want to be rooted im just not sure how to do it now.
Hello,
I am new to flashing roms, but today I tried flashing cm12(cm-12-20150224-NIGHTLY-falcon.zip) on my moto g XT1032. I installed clockworkmod recovery and made a backup of my stock rom. I then coppied the buckup to my computer and deleted it from my moto g, and that was a huge mistake. I then wipped the data, cache and the dalvik cache and installed the new rom. After 10 minutes it was still showing the cm logo so I waited an other 10 minutes but nothing changed. So I think it is in a boot loop. I can still boot into fastboot and recovery but I cant get my device to show up on my computer in ADB fastboot works fine. I really hope that you can help me.
I fixed it because of this:
I cant place links yet sorry
I updated my Moto G (XT1032) to the new Lollipop (5.0.1, I think). I left the phone plugged in to let it download and install, and when I came back to it after about a half hour, the phone was displaying the screen with 'Google' and an unlocked padlock on it. I left it for another 20 minutes or so, but it stayed on the same screen. I couldn't power it off at all, every time I tried to, the screen would turn off, but then come back on and vibrated once, only to go back to the padlock.
I ended up going through the Flashboot menu and cleared the Cache Partition, but that made no difference. Also tried a factory reset, but that seemed to make no difference. Currently, the phone is still sitting at the padlock screen.
The Flashboot menu says that the phone is unlocked, but I have no memory of doing this. Maybe it's something to do with the update failing?
Just wondering if anyone has some advice on how to proceed with this.
5.0-lollipop motorola
shareimprove this question
asked Dec 18 '14 at 5:02
thechunksalot
62
add a comment
1 Answer
active oldest votes
up vote 0 down vote
Well, there are two ways to fix this one out:
Requirements:
You need to have a custom recovery (CWM/TWRP) installed
You are going to require Stock firmware zip file for Moto G XT1028, XT1031, XT1032, XT1033 and XT1034 which can be downloaded over here
ADB and Fastboot
Method 1:
Boot your phone into custom recovery mode. Recovery will have adb on by default, so leave recovery as it is.
Connect your phone to your PC and open command prompt and issue the command: cd directory-with-adb.exe-and-fastboot.exe
Now, issue the command: adb devices. If Moto G drivers have installed properly, the phone will show up. If not, get it over here and install it over your device
Now, from recovery wipe /data and media
Open command prompt and execute: adb push rom.zip /sdcard/rom.zip It will take some time to install the ROM. If you face a not working SIM or WiFi, extract the downloaded ROM zip file and navigate to extracted firmware folder using cmd and issue:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Method 2:
Extract the downloaded firmware file to a folder.
Download and extract mfastboot and copy its content to the same folder where the extracted firmware files.
Reboot your Moto G into the Bootloader Mode. To do so, turn off your phone and then press and hold the Volume (-) and Power buttons simultaneously for a few seconds.
Connect your phone to your PC via USB cable.
Now, launch a command window from inside the firmware folder (click shift key, right click and select open command window here option).
In the command window, issue the following commands one by one:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
mfastboot reboot
Note: If firmware includes four ‘system.img_sparsechunk’ or you do not want to erase the userdata, you can modify the command. You have now successfully installed a fresh ROM on your Moto G and the phone the phone should work as usual.
Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess
I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.
audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.
fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.
worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban
Hi
I have Nexus 5 (Hammerhead) 16GB. After Marshmallow latest update my phone begun to restart randomly, So I tried to do factory reset. When I entered recovery mode It did not show android lying on its back with label "No command" , instead It showed standing android with some rotating cube (or gear) on its tummy. I tried to flash factory image in several ways, using nexus root toolkit and fastboot. I even tried different versions of android to flash but no result. My phone still shows Android with rotating gear on its tummy. Today I found this Thread and did everything that was told but no luck. :crying: If anyone could help I would be very grateful. Sorry for my bad English.
What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?
exninja said:
What is "everything that was told"? Did you erase everything then flash everything new? How long are you letting it sit with the rotating cube/gear thing?
Click to expand...
Click to collapse
thank you for your reply.
I used this commands as it was described
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
astboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
every operation was successful.
I waited for this rotating gear more than 10 hours, nothing changed Still shows same
When I click power button + up volume key It says "Formatting /data"
Did you erase and reflash userdata img file?
audit13 said:
Did you erase and reflash userdata img file?
Click to expand...
Click to collapse
yes I did that, but still shows Android with rotating gears.
It does not matter whether I start my phone normally or boot a recovery mode It still shows this Android animation.
Does the phone's bootloader remain unlocked after rebooting?
Hey there,
Yesterday my stock Moto G (xt1032) running android 5.1 bricked.
I started to browse the forums as well as a multitude of other ressources before posting. Nevertheless, I'd like to apologize if this topic has been covered before.
So far, it looks like all advice is directed to telephones that got root/got bricked through flashing and have installed some kind of custom recovery.
What happened:
My Moto G was working fine for years, but it wouldn't start an app, so I decided to reboot it.
It took quite a while to turn off.
And since than i can't boot it. It is stuck on the logo screen. No boot animation, no whatsoever.
I also can't turn it back off and have to remove the battery connector to do so. I cleared the cache partion from recovery, but that wouldn't help.
It charges fine.
Here is what i tried so far:
I installed all the drivers (at least i hope so) under windows 7 (64-bit). The Moto G is listed as falcon s in the windows control panel. The control panel indicates that it is working properly. I disabled my pc's firewall and virus scanner.
On the phone i can still get into the boot loader "fastboot (vers. 41.1A)" and from there into recovery. The device is locked.
Fastboot says "USB connected"
USB-debugging is disabled on the phone.
I tried to access the Moto G via adb in the bootloader, but i get a "device not found" error (EDIT: Ok, I just learned that I can only access the phone using fastboot in bootloader as ADB is for Recovery and within the OS usage).
I can access it in bootloader via fastboot, but that doesn't help me to get my data, aight?
I can enter recovery from bootloader, but ADB is not working there either (maybe due to USB-debugging being disabled)?.
All i want right now is to pull some important data. Can anyone tell me what to do?
Thanks for any advice!
This was solved thanks to lost101's input in this thread:
http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
Get retail image from here:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Get mfastboot to run on your computer, boot into bootloader and perform the following commands:
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
Doing only the above commands will not erase userdata, only reinstall Android.
Click to expand...
Click to collapse