Soft brick? - Moto G Power Questions & Answers

Well great. Device soft bricked. Bootloops endlessly. Can get into fastboot but the moto recovery tool thinks it’s fine and will not do a recovery. I was trying to downgrade from stock a11 to 10 but obviously failed Thinking the recovery tool would bring back to stock. I even put the imie number in and the software still thinks I have the latest firmware but I can’t force it to recover anyway. Help please

Got it back by downloading the latest stock a11 firmware and manually flashing in fastboot so I’m back to stock. Question is can I install any custom rom at all?

Related

Soft Bricked Moto E on downgrade

So i have this brazillian xt1022 with official ota updated lollipop, which i tried to root (sorta long story), it boot looped after a complete discharge on the boot image. After it, i did the downgrade to 4.4.2 and no progress has been done, just the recovery has gone tottaly useless, it now is boot looping quickly on the no command screen . Now i do not have any access to recovery, neither to adb (obviously) and just have the fastboot. I tried flashing again the downgrade rom, but there's that gtp error about trying to downgrade. Tried to flash boot.img too.
Ps: the update command won't work since no roms i found have the android-info.txt.
Any idea about what to do? Or any official rom to send me? it has to be a lollipop rom to the things work?

Stuck on TWRP recovery:(

I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
you should write this in other section but i want to help you.
maybe try to flash stock kdz again if you still can then check if bootloader method you use is correct but if was not you will brick your phone.

How 'thorough' is a factory image flash via EDL?

I'm just curious as to whether anyone knows how 'thorough' an EDL flash with original Xiaomi fastboot firmware is. As in, is it bit-for-bit identical to a factory fresh unboxed phone? Or are there unique partitions which can become damaged - ones that EDL can't reflash?
I'm asking this since I had one of those 'softbrick' adventures in the wee hours.
Longer version; CM13 to AOSP caused the phone to go barmy but restoring an Official TWRP backup of CM13 didn't fix this, so I reset the device using the CN DEV MIUI8 fastboot files via EDL, pushed alka TWRP and tried again with my original CM13 alka backup from yonks ago after coming from MIUI7. Only to get something like 'E:extractTarFork() process ended with ERROR=255' with the firmware partition. I'm guessing this is essentially since it's attempting a MM to LP downgrade. Anyway, I reflashed via EDL, went straight to a Nougat ROM but left wondering if there's any damage done from those bootloops, CM firmware zips and failed restore pushes even after an EDL reflash. No symptoms anyhow.

Moto E XT1528 Bricked (help)

I have an XT1528 that I tried to flash stock onto but it ended up not starting from the bootloader and stays black. I have tried installing the newest firmware, older firmware, and the Verizon's tool to install the latest firmware. All have failed to get the phone to boot. The only thing I can get to is the bootloader, the system won't boot, recovery won't boot. Is there anything else I can try/do to get this phone working again? Thanks.
0o0will0o0 said:
I have an XT1528 that I tried to flash stock onto but it ended up not starting from the bootloader and stays black. I have tried installing the newest firmware, older firmware, and the Verizon's tool to install the latest firmware. All have failed to get the phone to boot. The only thing I can get to is the bootloader, the system won't boot, recovery won't boot. Is there anything else I can try/do to get this phone working again? Thanks.
Click to expand...
Click to collapse
Try flashing stock rom via adb or else flash twrp and install a custom rom.

SHT-W09 Fastboot Not Available

So I think I have a new one here! I magically was able to flash EMUI 9.0 and then 9.1 onto my SHT-W09 432. I have previously rooted the device so recovery doesn't really exist anymore. I received a notice to upgrade the firmware on the device so I tried to do that via HiSuite using the correct firmware that was being announced via OTA. The installation technically failed, but I got no warnings at all. The device rebooted and everything seems to work. I then tried to install several other firmware builds to see if I could get one to stick. None of them did.
This is when I decided I would try to boot into Fastboot and then flash the firmware from my PC like I had previously done on my P20 Pro. When I tried to boot into Fastboot, I got a big white screen stating that software failed to install. No Fastboot commands worked.
Any thoughts, suggestions, or direction?
At this point i think you should did a full factory reset, restoring firmware 9.1.0.335 (this is the latest firmware of own Mediapad M5 wifi 8").
I cannot tried it, i know there is an eRecovery mode but i don't know what it does.

Categories

Resources