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
Moto G 2013 Keep reboot to recovery after bricked
HI, I have a Moto G XT1034 on hand with strange issue.
One day the phone was not able to boot up correctly, it stuck on Android screen and keep rebooting.
I managed to root the phone, and install TWRP, and load up 5.1 version ROM.
But every time phone reboot, it will boot to recovery mode, and I have to select reboot to bootloader and in bootloader select BP Tools (or other option) in order to boot up the phone
I made a boot up process video below
What is wrong with my phone? I have try re-flash the ROM, but nothing changes.
I can't post the link, but if you go youtube and search "YzxAe9WpwOw" you can see the boot up video
Go to bootloader, use cmd : mfastboot.exe erase cached
mfastboot.exe erase userdata
instead of flash whole ROM.
Hope it help.
Didn't work, tried it and it just reset my phone. Every time I power cycle the phone, it still boots to recovery mode
thuybang said:
Go to bootloader, use cmd : mfastboot.exe erase cached
mfastboot.exe erase userdata
instead of flash whole ROM.
Hope it help.
Click to expand...
Click to collapse
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?
Hello,
I was trying to install TWRP custom recovery 3.4.0-0-violet on my Xiaomi Redmi Note 7 Pro.
The problem was that I could flash it with fastboot (with my bootloader unlocked), but it simply would not boot into it.
In the official TWRP forum thread someone used the command
Code:
fastboot erase userdata
TWRP still did not boot, so I tried another command mentioned:
Code:
fastboot format userdata
Currently the phone will not boot into anything other than fastboot. No MIUI recovery, no android.
Once again, erasing userdata works, flashing recovery works, but now just stuck on fastboot and that's it.
Probably shouldn't have formatted userdata.
If someone could guide throw me a lifeboat, I'd appreciate it.
Graphical00 said:
Hello,
I was trying to install TWRP custom recovery 3.4.0-0-violet on my Xiaomi Redmi Note 7 Pro.
The problem was that I could flash it with fastboot (with my bootloader unlocked), but it simply would not boot into it.
In the official TWRP forum thread someone used the command
Code:
fastboot erase userdata
TWRP still did not boot, so I tried another command mentioned:
Code:
fastboot format userdata
Currently the phone will not boot into anything other than fastboot. No MIUI recovery, no android.
Once again, erasing userdata works, flashing recovery works, but now just stuck on fastboot and that's it.
Probably shouldn't have formatted userdata.
If someone could guide throw me a lifeboat, I'd appreciate it.
Click to expand...
Click to collapse
Fixed.
Was told the phone was a Redmi Note 7 Pro (violet), when it was a regular Note 7 (lavender) global.
Flashed TWRP, phone is fine.
My realme 5 pro bootloops and never boot to recovery, I've flashed
stock .img files (system, vendor, boot, dbto, vbmeta, recovery) from
ROM(RMX1971EX_11_OTA_1080_all_29hQ1fOMjgyl) (C.08 RUI 1.0) and various custom recoveries(TWRP-OrangeFox) using fastboot mode but nothing.
Also it was booting into fastboot directly nothing else, but after erasing system partitions
(system, boot, vendor, recovery, dbto, cache, userdata)
via fastboot commends then flashing them using C.08 ROM files and disabling verification,
it began to bootloop on "powered by android" screen after it was booting into fastboot only so i think it's good step forward, but i need some help to know what should i do next.
What happended exactly ?
Well, yesterday i had an OTA update for android 11 RUI 2.0, after update done and system boot up, it began flashing the lock screen then a black screen; so i used commend
Code:
fastboot erase userdata
after that i couldn't go recovery mode again.