Moto E4 HardBoot - qcom 9008 - Moto E4 Questions & Answers

XT1766 hardbrick stuck in 9008 mode would normally require a blankflash. However, as is common in most Motorola models there is a boot from SD option that is automatically defaulted to in the case that the bootloader has been deleted or damaged. To use this boot from SD option, simply extract the bootloader to a blank SD card and insert it into the phone then reboot. Whenever the phone reboots it will use the bootloader on the SD card as the default loader.
Here is a bootloader provided to me (Untested)
mediafire.com/file/t2su47wbd3dizue/XT1766-BOOTLOADER.img/file

Related

How do I unbrick a bricked P9Lite with a locked bootloader and without USB debugging?

Greetings all,
I recently got a P9 Lite but I bricked it trying to install a newer firmware on it (tried to go from 6.0 to 7.0). I've read various unbricking guides over the past two days but to no avail. I'd like to know what my options are at this point and if it is possible to unbrick it and bring it back to a usable state even if on a different rom.
How I got here:
The firmware that came with my phone was L23C605B120. I tried to update it to L23C605B362 and downloaded 2 zips (update.zip and update_data_full_VNS-L23_hw_la.zip). I unzipped update.zip into the dload folder of my sdcard and updated it via the dialer. The update installed and my device rebooted but now to this bootloop state.
What I can do:
If booting up normally, I end up in Huawei's erecovery. I can also boot to recovery mode where I can either "Wipe data/factory reset" or "Wipe cache partition". I can boot to fastboot & rescue mode but it says my phone and frp are locked. When pushing all three buttons I can boot to where the phone will attempt to update with the dload folder in the sd card again.
Stuff I have tried:
In erecovery when I select "download latest version and recovery", I can connect to my wifi but it always fails at "Getting package info failed". In recovery mode the factory reset fails and I don't think wiping the cache partition did anything meaningful. In fastboot & rescue mode it tells me to open HiSuite where there is a recover option but clicking it says "Your device is not supported for system recovery". I can see my device using fastboot on my computer but it seems almost useless here since its useful commands fail with "command not allowed" probably because my bootloader is locked. On my computer I installed the USB drivers adb needs and rebooted but adb cannot see my device presumably because I hadn't enabled USB debugging prior to getting bricked. At this point I'm downloading different roms to my sdcard and trying to flash with the 3 buttons method but pretty much all of them fail at 5% or 7% including the rom with the same version that my phone came with. The only one that doesn't fail at 5% or 7% is the rom I tried to flash that bricked my phone which fails at 99%.
So I cannot flash TWRP because my bootloader is locked, I cannot unlock my bootloader because adb cannot see my device, adb cannot see my device because I probably never enabled USB debugging and I cannot enable USB debugging because I cannot boot to the OS. At this point my only option seems to be trying to flash a working rom with my sdcard but I have yet to find one that works.
Where should I go from here and what are my options at this point? Is there a specific rom I should be looking for? Is there some intermediate downgrade rom I have to flash or is there a way to undo the update I just did? Is there a way to somehow enable USB debugging or to unlock my bootloader without it (perhaps via an exploit)?
Any help would be much appreciated!
TL;DR: title

Help!! Unable to boot...how to fix

so i was trying to root and unlocked the bootloader, but i erased the internal storage and apparently messed up its partitioning scheme. i can nolonger get past the bootloader or fastboot. i can lock and unlock the bootloader but i cannot flash a rom. how do i fix this? also no access to recovery mode
Same problem my phone is booting than restarting and is retrying until the battery dies. Cant get in recovery nothing

Huawei Ascend XT2 booting into Recovery mode and Fastboot&rescue mode only

Hello guys.
It's a Huawei Ascend Xt2. It had TWRP installed with bootloader unlocked.
Since I wanted to have stock rom with no root, so I erased eveything, relocked the bootroom and now the phone just shows Huawei logo when booting and then enters Recovery mode on it's own. If I press Vol - and Power enters Fastboot&rescue mode.
Both Mac and PC recognizes the device as MSM8937_32(with recovery mode) and Google(Fastboot&rescue mode).
Tried installing ADB drivers no luck (waiting for device), tried with huawei drivers no luck.
I have the stock rom downloaded. I'm not able to flash anything on this device.
Is it possible to install from MicroSD?
Windows detects the device as mentioned. I think maybe it's recognizing the device as a different device or wrong driver but not sure what else to do.
Thank you for your suggestions.
PD> In FASTBOOT&RESCUE MODE.... phone says:
PHONE Relocked
FRP Unlock.
Thanks
vinhidalgo said:
Hello guys.
It's a Huawei Ascend Xt2. It had TWRP installed with bootloader unlocked.
Since I wanted to have stock rom with no root, so I erased eveything, relocked the bootroom and now the phone just shows Huawei logo when booting and then enters Recovery mode on it's own. If I press Vol - and Power enters Fastboot&rescue mode.
Both Mac and PC recognizes the device as MSM8937_32(with recovery mode) and Google(Fastboot&rescue mode).
Tried installing ADB drivers no luck (waiting for device), tried with huawei drivers no luck.
I have the stock rom downloaded. I'm not able to flash anything on this device.
Is it possible to install from MicroSD?
Windows detects the device as mentioned. I think maybe it's recognizing the device as a different device or wrong driver but not sure what else to do.
Thank you for your suggestions.
PD> In FASTBOOT&RESCUE MODE.... phone says:
PHONE Relocked
FRP Unlock.
Thanks
Click to expand...
Click to collapse
download this > https://easy-firmware.com/home/browse/category/id/25781/
use 7zip to extract it on your pc until you get the dload folder that contains the update.app
copy dload to your ext_sdcard.
follow instructions found in the zip of check mine here > https://forum.xda-developers.com/showpost.php?p=76902495&postcount=86

Moto g7 twrp touch input not working

I don't have an os right now. I can boot to TWRP, but I can't use it. I'm not sure what to do... TWRP worked before, but then I wiped everything and it won't. (OCD) I don't know if this is a clone, but please don't delete this post. I really need help.
Wrong vendor. Only way to fix it is to go back to fastboot and reflash stock and start over with TWRP installation
Quote:
Originally Posted by NetrixX13
I had exactly the same problem. The Lineage OS installation instructions are missing an important point.
The Moto G7 has two slots, A and B. However, it seems they only come with a bootloader pre-installed on slot A, slot B seems to be completely blank.
When slot A is active and you flash Lineage OS using TWRP, it writes to slot B and switches to slot B.
When you reboot, you cannot boot anymore, because on slot B there is no bootloader.
To mitigate this issue, you have to flash a "copypartitions" zip before rebooting.
My phone also was in 9008 mode and I revived my Moto G7 using the blankflash method, see here:
https://forum.xda-developers.com/mot...reteu-t4020263
I can also confirm saving my Hard bricked, non booting black screen, no life moto g7 with the above blank flash app from above link. then i used the lenovo recovery program to put the original rom back on the phone downloadable here: https://support.lenovo.com/us/en/downloads/ds101291
if you have a black screen hard brick, no life but windows 10 sees it at an unknown or 9008 device then you can bring your moto g7 back to life again. follow all the above links and youre good!

Issue with slots, not able to boot to OS

Hi, I'm on OOS11 and I lost magisk so I booted to TWRP via fastboot but it gave me the error "qualcomm crashdump mode". After that error I wasn't able to boot into the OS. I found out that the twrp I was using is not compatible with OOS11 so I tried again with "fajita_twrp-3.5.2_11-0_test3.img". I was able to enter into TWRP and with no wipes I installed OOS11 + TWRP. The "qualcomm crash.." error is gone but the phone does not boot, it is stuck on a bootloop. When I enter into TWRP in slot B it's asking me for password and I'm able to see my files. When I'm on slot A it's not asking me for password and data seems to be encrypted (folder weird names). Is there a way to solve this without having to reset data?

Categories

Resources