Stuck in Corrupted TWRP - Coolpad Cool1 Questions & Answers

i tried to update my twrp with this getdroidtips.com/twrp-recovery-coolpad-cool-1 and now my phone stuck at corrupted recovery, only red light when in corrupted recovery. my phone is still detected in device manager as "Qualcomm HS-USB Diagnostics 900E (COM3)". I tried to flash other recovery but it says "Download Fail: Switch To EDL FailFailed to Switch to Emergency Download mode"
hope you guys can help me

Related

Lenovo a6000 plus HARD BRICK please HELP

GUYS first i installed Twrp 2.7 than after getting into recovery mode i flashed TWRP 3.0.2 but after that phone is dead.Not even lenovo logo
when i connect it to PC it shows as "Qualcomm hs-usb qdloader 9008m" (but not detecting as fastboot mode) and many many windows gets opens and tell me to fomate drive but cant formate it shows that disk is read only
when i tried to Flash stock rom using QPST it shows "failed to switch to EDL mode". any key combination isnt working.I cant go to EDL mode maunally as phone is not detecting as fastboot or adb mode
is my motherboard is broken????

A2017G Bricked Oreo

It seems i have bricked my device by flashing a custom recovery.
USB Debugging is enabled but OEM Unlocking is not
Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3)., holding buttons seems to do nothing aswell as the phone has no LED indicator or vibration.
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state

Stuck on stock recovery mode

Hi all, I have a problem with my A2017G
Currently:
- bootloader: unlocked
- booting: ZTE logo -> Can't be checked for corruption message -> ZTE logo -> (very short) fixing Android graphic -> stock recovery
- reboot to bootloader (from recovery): as above
- DFU mode by power&vol-: ZTE logo -> black screen -> ZTE logo -> (very short) fixing Android graphic -> stock recovery
- EDL mode by vol+&vol-: MiFlash not recognize, Windows device manager not recognize, Zadig recognize as QUSB_BULK, red LED light in Axon 7 like EDL mode
- apply update from SD card: Sorry, you can't sdcard update message
What I can do to repair that and have normal stock rom?
ColorfulPoland said:
Hi all, I have a problem with my A2017G
Currently:
- bootloader:unlocked
- booting: ZTE logo -> Can't be checked for corruption message -> ZTE logo -> (very short) fixing Android graphic -> stock recovery
- reboot to bootloader (from recovery): as above
- DFU mode by power&vol-: ZTE logo -> black screen -> ZTE logo -> (very short) fixing Android graphic -> stock recovery
- EDL mode by vol+&vol-: MiFlash not recognize, Windows device manager not recognize, Zadig recognize as QUSB_BULK, red LED light in Axon 7 like EDL mode
- apply update from SD card:Sorry, you can't sdcard update message
What I can do to repair that and have normal stock rom?
Click to expand...
Click to collapse
First of all DFU is not accessible with button combination unless you really bricked the phone. Power and vol- will get you to FTM (factory test) which has adb so it won't really be useful for anything in your situation. if the phone is bricked EDL will be replaced with DFU (power and both vol buttons).
EDL is not working for you because you used Zadig beforehand. MiFlash or EDL Tool use the "Qualcomm HS-USB QDLoader 9008" driver, while axon7tool (i assume you used that to unlock?) needs qusb_bulk. Go to the device manager, find qusb_bulk while on edl, and uninstall device - tick "delete driver software" and go ahead. After that reboot EDL (hold all 3 buttons for like 30 seconds, it should flash the LED and the device manager should refresh. if it doesn't just turn the phone off and get into edl again). The actual qualcomm driver should be installed automatically (or if the "ZTE Handset Diagnostic Interface" one appears then you're in dfu, use MultiDL first to get to EDL). Then use MiFlash (or EDL Tool) and you're done

Help , Lenovo splash screen and the fastboot mode is written on top.

Hello everyone, there is Lenovo K6 Power, which when turned on hangs on the Lenovo splash screen and the fastboot mode is written on top.
1. you can turn it off and hold both volumes to connect to the PC and it will be visible as Qualcomm / Lenovo HS-USB QDLoader 9008,
1.2 but with firmware via qfil - Download Fail: Switch To EDL FailFailed to Switch to Emergency Download mode. (although the body is essentially already in mode)
2. The fastboot devices command is defined in the fastboot. through the fastboot oem command, reboot-edl- switches to the mode, but when trying to flash it repeats p1.2
3. enters the native recovery, tried to make wipes - it does everything, and after rebooting the mode enters the fastboot again.
*
On a third-party resource, they prompted that we should try to update update.zip with 231 firmware from the native recovery. Does anyone have this file?
sorry for my english, I translated google translator)
imprestness said:
Hello everyone, there is Lenovo K6 Power, which when turned on hangs on the Lenovo splash screen and the fastboot mode is written on top.
1. you can turn it off and hold both volumes to connect to the PC and it will be visible as Qualcomm / Lenovo HS-USB QDLoader 9008,
1.2 but with firmware via qfil - Download Fail: Switch To EDL FailFailed to Switch to Emergency Download mode. (although the body is essentially already in mode)
2. The fastboot devices command is defined in the fastboot. through the fastboot oem command, reboot-edl- switches to the mode, but when trying to flash it repeats p1.2
3. enters the native recovery, tried to make wipes - it does everything, and after rebooting the mode enters the fastboot again.
*
On a third-party resource, they prompted that we should try to update update.zip with 231 firmware from the native recovery. Does anyone have this file?
sorry for my english, I translated google translator)
Click to expand...
Click to collapse
What is the exact firmware version that you are trying to download into the eMMC?
I'd suggest you to find a full package for K6 Power (I have the package for K6 Note) and try to download it with QFIL. You can find these on a lot of YouTube videos.
And for entering into the EDL mode, better install a custom recovery (you can find the procedure on XDA) and enter EDL mode from TWRP recovery. This is a better option as you will barely know if you device is in EDL mode as the screen is always off.
Don't worry you will get the stock recovery back when you download the stock firmware into the eMMC.
Thanks,
tfr.

stuck in fastboot after magisk update

My phone was rooted nad has an unlocked bootloader
today, i got prompted to update magisk. I had done this previously with no problem, but something must have changed with magisk, because after rebooting the phone got stuck in fastboot mode.
I tried the "hold power and volume down until the phone reboots 6 times in a row", but it didn't work. I plugged the phone to the pc and it entered download mode
is there a way to fix it myself? is download mode the same as 9008 mode?
the phone is a AWM model cross flashed to ulm, running android 9
nevermind, got the phone to 9008 mode too (detected by pc as Qualcomm HS...)
I have same problem, i get download mode but when i open lgup there is no option to choose kdz or select refurbeshed
So how did you fix it?

Categories

Resources