Database Users

A2017g bricked after bootloader relock

Hello everyone,
So I've read that I can re-lock the bootloadder and tried to do it.
First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.
Since then I cannot boot to the phone.
The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.
Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.
In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".
What can I do?
Please refer me to the right tutorial or guide me.
Thanks

I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)

dnlilas said:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
Click to expand...
Click to collapse
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.

@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169

dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
I'll try all these guides and update with results

dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
So for sure I'm doing something wrong. Can you please guide me with this tool?
Ironically you helped me unlock the bootloader and I need your assistance relocking it.
Edit: I have the 3 files backed up from the unlocking procedure they should help no?
The phone is not recognized in any adb status edl or fastboot

I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?

QuantumFluxx said:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
Click to expand...
Click to collapse
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.
I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it

I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed
What does Windows Device Manager show when you connect the phone to your PC?
Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.
Update:
Have you seen this?
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Sorry that I can't be of more help...

I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery) I'm hoping it makes sense (pretty early in the morning)

So no one can help?
I can't believe the phone is beyond repair

@ItsNewDroid
Sorry I do not have solution, just some idea.
It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.
There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.
So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.
If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.
Qualcomm bulk drivers, MiFlash... are available from Download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
The problem is to find available "EDL packages" recognized by MiFlash to flash.
These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).
This would allow booting to either recovery or system.
The problem is that I did not see many such packages for A2017G, but only for A2017U.
You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").

@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again

@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?

ItsNewDroid said:
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Click to expand...
Click to collapse
Oh no, you unfortunately got the dreaded DFU (device firmware mode).
Looks like it a serious brick. Some topics and articles:
https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
https://community.zteusa.com/thread/14699
https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/
https://www.youtube.com/watch?v=nqF3nr3y-Eg

@dnlilas
Man there are changes!
So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?

Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").
When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.

dnlilas said:
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Click to expand...
Click to collapse
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.
I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.
My guess is that I have twrp recovery and as the bootloader is locked it can not boot.
I need either a twrp for LOCKED bootloader or a stock recovery.
I'm searching the forum but could not find.
You are a wizard! Every time you reply I have good news :good::laugh:

@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!

dnlilas said:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
Click to expand...
Click to collapse
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?

Hell to unlock Bootloader Please...

Hi there,
i'd Like to flash the Ressurection Remix Oreo Rom, but i don't get it to unlock the bootloader. I'm on Stock A2017GV1.2.0B10 Nougat. TWRP and Backups are done, but when i try to unlock the Bootloader i geht this message in cmd:
adb: error: connect failed: no devices/emulators found
Tried with Zadigs Drivers, ADB divers are installed and it is showed as QS_Bulk.
Are there still some drivers missing or what am I doing wrong there???

Did you enable USB Debugging on your phone?

Victor13f said:
Did you enable USB Debugging on your phone?
Click to expand...
Click to collapse
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...

Have you installed the Google USB drivers and checked in Device manager if everything is working okay? Here's a link to a guide: https://www.drivereasy.com/knowledge/solved-adb-device-not-found-error-on-windows/

HeikoNote3 said:
Yes, i have OEM unlock and USB Debugging enabled. Dont understand why this is not working at all. Tried it many times, but every Try I get this message in the CMd. Sideload isn't working too...
Click to expand...
Click to collapse
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

raystef66 said:
Just use the EDL Tool from @djkuz, install it, put your phone into EDL mode and unlock.
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Click to expand...
Click to collapse
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...

HeikoNote3 said:
So, Tried this one too. Doesn't work, phone isn't found, error adb interface not found...
Click to expand...
Click to collapse
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb

raystef66 said:
Uninstall all drivers you see relating to your phone (adb, usb...)
Try install : http://adbdriver.com/downloads/
And https://androidfilehost.com/?fid=24588232905723896
And see if you can perform with the EDL Tool again or adb
Click to expand...
Click to collapse
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...

HeikoNote3 said:
Installed the ADB Drivers but in EDL tool the Phone is not recognised. Dont know what could the Problem...
Click to expand...
Click to collapse
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?

raystef66 said:
First boot into twrp, connect your phone, run the EDL Tool. Normaly the tool should reboot itself into EDL mode
Or try : run EDL tool, instead of power off phone, hold vol down+power, connect usb, just do the same by holding the 3 buttons ( i did that once when my phone was in a state of 'shock' and the 2 button way didn't work)
Btw, did you install the 2 drivers i gave you ?
Click to expand...
Click to collapse
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...

HeikoNote3 said:
Yes they're installed. I'm wondering that edl tool shows first ZTE ADB handset etc. And after boot into edl mode it shows no ADB interface... With axon7tool I can choose unlock Bootloader, then MI flash starts and then I don't know the files to flash for an unlock...
Click to expand...
Click to collapse
MiFlash? Where did you read that you had to use MiFlash? ?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things

Choose an username... said:
MiFlash? Where did you read that you had to use MiFlash?
You need to use EDL Tool
Edit: Okay, I think I got it. You thought "EDL Tool" was actually axon7toolkit. Well, it isn't. Axon7toolkit, axon7tool, and EDL Tool are 3 different things
Click to expand...
Click to collapse
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...

HeikoNote3 said:
OK, then which tool should I prefer now? In EDL tool I was on a good way to unlock the Bootloader, but when I choose Yes, the unlock begins with load programmer something and stucks until I reboot EDL mode. Then it gives me an error message with: your device could be in Sahara mode. I don't understand anything anymore. Tried every driver, every tool but nothing will work. That drives me crazy...
Click to expand...
Click to collapse
Did you enable OEM unlock and USB debugging?
If you did and it still does that error, just use the manual method and follow Controllerboy's guide. That one uses axon7tool, which is much more finicky and ran by commands, but it works

Thanks for all Tipps. Finally did it. Running RR Oreo!

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Need some help after messing up my Lineage OS installation on A2017U

My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?

Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too

OnePlus 8 Pro problem - No OS

Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?

SakasakaHeyhey said:
Hi guys,
I am having an issue with my OnePlus 8 Pro and I hope you can help me. I am open to all suggestions.
My phone bricked after trying to flash a custom rom. I have access to fastboot mode and TWRP. I am operating a linux machine and have windows10 running in virtualbox. I don't know if this is the reason but when I am trying to boot in to EDL mode (ony possibility is via TWRP) my device does not pop up in devicemanager. I followed all the steps in the thread about the MSM tool. When I try to get in to EDL mode with the hardware butons and the original cable from OnePlus I can not get in to EDL mode at all. Tried different cables and different USB ports on my computer but with no success. The correct qualcomm drivers are installed in windows so in theory it should work. Because of this I can not use the MSM tool to get my phone up and running. It simply does not pop up as a qualcomm device in devicemanager when I reboot in EDL mode.
I tried to flash the fastbootrom for my oneplus8 pro but after the last command it restarts and gets into stock recovery. In the command window it says 'waiting for any device' and nothing happens (I waited for about 20 minutes). In the post is mentioned: If the device automatically reboot in Stock Recovery mode don't reboot it and wait the flash end. Because nothing seems to happen I saw further in the post If the rom seems doesn't start go in recovery stock and follow this guideline: English -> Wipe data and cache -> Erase everything.There is no option available to wipe data and cache/ erase everything in the recovery menu. When I choose to reboot to recovery in the recovery menu my phone powers off. The other option is to reboot into fastbootmode. When I do that there is an error in the command window FAILED Flashing is not allowed for Critical Partitions. I don't know how to fix this. I tried both Linux to flash the fastboot rom manually and in windows also and with the flash-all.bat file. Everytime I end up in fastboot mode when I boot up my phone.
Instead of trying to flash the original OS with the fastbootrom I tried to flash different custom ROMS but somehow it will not install any ROM at all...the device reboots everytime to fastboot mode. Last option I tried is a different recovery. I flashed lineage recovery and tried to flash Lineage OS and AICP and this resulted also in only able to boot into fastboot mode.
I spend a lot of time on the web trying to figure out what is wrong and how to fix it but I have not found a solution yet.
Is there a solution available to get my phone up and running?
Click to expand...
Click to collapse
Sounds like a Qualcomm driver issue. You need that for msm

jamescable said:
Sounds like a Qualcomm driver issue. You need that for msm
Click to expand...
Click to collapse
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.

SakasakaHeyhey said:
I am affraid so jamescable. I was hoping for a fix via fastboot mode...
What is strange is that flashing another recovery via fastboot is no probleem but a Rom is... don't know why my device is doing this.
Click to expand...
Click to collapse
You can only install Qualcomm drivers in windows, not linux

jamescable said:
You can only install Qualcomm drivers in windows, not linux
Click to expand...
Click to collapse
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.

SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse

SakasakaHeyhey said:
Hi jamescable,
Thanx for your support.
I am running windows 10 in a virtual machine and installed the drivers. The problem is that my device does not pop up as a qualcomm device in devicemanager when I boot into edl mode.
In fastboot mode my device does pop up in device manager.
That is what I do not understand.
Click to expand...
Click to collapse
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately

Thanx jamescable. I am going to do this as you described later this week and will post an update in this thread.
Have a nice day friend!

jamescable said:
To get to edl mode. Power phone off completely. Then. Use msmtool. Get it ready and hit start. Then hold down volume up AND volume down. Do NOT hit power button at all. Plug phone in. Msmtool should start immediately
Click to expand...
Click to collapse
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?

SakasakaHeyhey said:
Hi jamescable,
Just done exactly as above...my devices boots into edl mode, but msm tool does nothing and in devicemanager my device does not pop up either. I do not hear a sound when I plug in the One+ cable...tried different usb ports on the computer also.
Do you have any ideas what I can do more?
Click to expand...
Click to collapse
It has to be a driver issue then. Windows in virtual machine obviously won't work for this

jamescable said:
It has to be a driver issue then. Windows in virtual machine obviously won't work for this
Click to expand...
Click to collapse
O no then I really have a problem....I only have linux as an operating system....I thought windows in a virtual machine running does the trick but I guess I am wrong.