Database Users

[Guide] No Boot - No Recovery - No Download Mode Unbrick Guide

No Boot - No Recovery - No Download Mode Unbrick Guide​
Qualcomm HS-USB QDLoader 9008 or Secure booting error (No Boot - No Recovery - No Download Mode) or "QHSUSB_BULK"​
Hi team, if you have come here I'm sorry you are having this problem! But my friend and I have been to hell and back trying to fix this problem and we wanted to share our method of success for any poor soul who is experiencing the same thing! For our situation the USB was unplugged half way through flashing a KDZ or going back to stock firmware and created the No Boot - No Recovery - No Download Mode problem.
This has only been tested on the D855.. Just so you know.​
First off, here are some links which you may need to have a look at if you have not done so already. Most of the bricking problems have already been extensively talked about by people here on XDA. For the method that works, we had to pull information from everywhere and spent a long time looking for the solution.
How to go back to stock - http://forum.xda-developers.com/showthread.php?t=2785089
Link for TOTs and KDZ's from the above thread - http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/
The Main Fix for the problem - http://forum.xda-developers.com/lg-g3/general/fix-unbrick-lg-g3-stuck-qualcomm-hs-usb-t2933853
The G2 version of the fix (for reference if you still have problems 55+ pages) http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830
This is your last stop shop if everything is broken and nothing works, involves hardware fix - http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
The problem we encountered several times with all of the described methods above, is that many do not describe important things. While the main fix thread for the Qualcomm HS-USB QDLoader 9008 mode, which is shown in device manager, is very well written and detailed, the programs which are linked in this thread are questionable and haven't worked for many users with some offering to fix for money. We searched the internet and located a working version of the program which worked without giving a "Device was not found in dload trying to flash programmer" like the one provided on the XDA page. Use the links below for a working version from this thread http://androidforums.com/threads/lg-g2-not-turning-on-help.916865/
My first point is if you are having problems with any of the things, CHANGE YOUR USB CABLE or use the stock cable (I know most experienced users know this). The reason for this problem has something to do with different USB cables being made for different purposes and are of different qualities. Having an error on the USB ports gave us only qhsusb_bulk on windows device manager, without Qualcomm HS-USB QDLoader 9008 as well.
If you are still having problems, check your USB ports. It is really important to make sure this isn't the problem or you will be trying to fix this problem endlessly.
First attach the USB cable to the computer. When you plug your phone in, make sure you attempt to enter download mode by holding the volume up button when you plug the USB into your phone. Even though the phone will not enter "Download Mode" It will allow the phone to be detected by your computer (at which point you can release the buttons, it should then show "Qualcomm HS-USB QDLoader 9008" under ports. If this is not displayed you have a problem with the USB cable or port, or your phone is hard bricked and you need to head to the above guide for the hardware fix. If you have followed so far and are wondering what to do from here, once the "Main Fix" guide ends, head over to the "How to go back to Stock" thread above. Your phone should be showing "firmware upgrade" and you can proceed to flash a new updated KDZ on your device then everything will work and your nightmare should be over!
Working Boarddiag - https://drive.google.com/file/d/0BzkqP9M0LLWQUkEyRkZrVHlEbDg/view
Qualcomm USB Drivers (Essential for the aforementioned "Main Fix" above) - https://drive.google.com/file/d/0BzkqP9M0LLWQblF6Vl9OcUkwUDA/view
LG United Drivers (Phone Drivers) - https://drive.google.com/file/d/0BzkqP9M0LLWQUURDTHlYOW5YRms/view
If this helped you to fix your nightmare don't forget to hit the thanks button!

The "Wroking Boarddiag" asks for PW. aside from that, very good find, thanks

detected as qdloader hs usb 9008
board diag- ap check failed device not in downld mode

For all people with Windows 10 an problems with drivers (device is detected by Windows but app is not connecting). Decompress de correct cab for your Windows version, and update the driver "Qualcomm HS-USB QDloader 9008" with the path you used to extract. Now this driver isn't advertising that isn't signed anymore, and all apps will connect with your LG G3
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x86
Qualcomm HS-USB QDLoader 9008 2.1.0.5 x64

Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?

MrMuli said:
Hi, I have the same problem, except that when I connect the usb, it shows up as "LGE AndroidNetUSB Serial Port". I'm not sure if I should try the Qualcomm route?
Click to expand...
Click to collapse
I just fixed my Lg g3 with this method. Not sure if it will work with AndroidNetUSB
Would like to help for any difficulties. (e.g. Not able to find TOT file) etc.
Thanks to @Orcam & @kryptonite

This did not work. Here's what I tried:
1. Without battery
2. Changed drivers as @shawe_ewahs says
3. With battery
4. Admin and non-admin
5. Changing COM ports
But, every time, I get:
"Device was not found in dload trying flash programmer
TEST Aborted!!"
My LG G3 D851 is in Qualcomm HS_USB QDLoader 9008 (COM 41) so I know it is in the correct mode! Agh, it is very frustrating. Any help is appreciated. Thanks.

Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*

furiify said:
Thanks you SOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO much! <3 I finally was able to fix my device *O*
Click to expand...
Click to collapse
No problem. Hope it didn't take you as long as it took us to find all the right stuff

I'm having this problem, but when I plug in without a battery all that shows up in device manager is "Unknown USB Device (Device Descriptor Request Failed)". I tried to do the hardware fix and was able to force the device to reboot by touching the pins. But all that happens is it disconnects and reconnects from USB without being detected properly.
I should note that when I turn the phone on right now, it stays stuck in the initial LG G3 splash screen. When I plug in without a battery, it shows an empty battery icon with a wire and a triangle question mark.
Any idea what I'm doing wrong? I think if I can just figure out how to get my machine to detect my phone as the qdloader hs usb 9008 I can figure out the rest.

The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.

Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.

Dr1t3r said:
The boarddiag v3.99 version 1 and 2 dont work, they dont even get ejecuted, not eve trying to execute as administrator.
Click to expand...
Click to collapse
phaim said:
Just wanted to reply since I resolved my issue. It turned out that, despite the apparent inability to boot into download mode, I discovered that if I booted up the phone with a battery in it and plugged into a windows 7 laptop, and held the button down to enter download mode, it eventually let me into download mode. I really can't explain why this worked, but just wanted to put it out there. It was at least a few minutes before I noticed that the laptop chirped and it was showing the install screen in download mode.
Hope this helps someone out.
Click to expand...
Click to collapse
Sounds like it may be a problem with windows from what you two have said. Perhaps compatibility mode is the way to go. They did release a pretty major windows 10 update since I posted this guide.

helppp bricked!

Edit*** I fixed it****
no bootloader, recovery or system, its also listed as unkown device on device manager.
i had it unlocked bootloader. and had magisk installed. but i made error of relocking.... i used the axon 7 tool.
Please i really need help maybe even remote desktop. and ill even pay i can't lose this phone i paid way too much for it
okay i have fast boot

WADE13x said:
no bootloader, recovery or system, its also listed as unkown device on device manager.
i had it unlocked bootloader. and had magisk installed. but i made error of relocking.... i used the axon 7 tool.
Please i really need help maybe even remote desktop. and ill even pay i can't lose this phone i paid way too much for it
Click to expand...
Click to collapse
Why did you lock it? There are a bunch of warnings everywhere. you couldn't have missed all of them...
Well try to get into EDL, maybe you can use MiFlash to fix it. But I can't help you more if you don't tell me what model it is...

Choose an username... said:
Why did you lock it? There are a bunch of warnings everywhere. you couldn't have missed all of them...
Well try to get into EDL, maybe you can use MiFlash to fix it. But I can't help you more if you don't tell me what model it is...
Click to expand...
Click to collapse
its a A2017U
miflash doesnt work

WADE13x said:
its a A2017U
miflash doesnt work
Click to expand...
Click to collapse
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes

Choose an username... said:
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes
Click to expand...
Click to collapse
i can't even see it showing up

https://photos.app.goo.gl/SdqJGWGkBE9TYxfE3
What do you make of this?

Turn off your phone. Connect to PC your device. Press volume up+down+power button for a while. You'll hear a sound from PC and check notification light. It should blink for one time. Then release buttons and let us know what do you see on device manager.

WADE13x said:
https://photos.app.goo.gl/SdqJGWGkBE9TYxfE3
What do you make of this?
Click to expand...
Click to collapse
What do I make of that? That's fastboot. I asked you to get to EDL. so nothing

If you want help you need to post more then once an hour and give us the info requested.

lafester said:
If you want help you need to post more then once an hour and give us the info requested.
Click to expand...
Click to collapse
sorry a friend needed me, setting up edl now

it says: unknown usb device (device descriptor request failed)

i got the right driver

Choose an username... said:
But what mode is the phone in when you put it in EDL?
Put the phone in EDL and go to Device manager, open the 'Ports (Com & LPT) tab', it should appear either as "Qualcomm HS-USB QDLoader 9008" or as "ZTE DFU interface". If the latter, you have to follow the 4th categ brick repair manual. And if it appears below 'USB devices' as 'QUSB_BULK', you should uninstall the driver (and tick 'delete driver software too') and restart EDL (hold the 3 buttons until the Device Manager spazzes
Click to expand...
Click to collapse
i have it in Qualcomm HS-USB QDLoader 9008
whats the next step?

WADE13x said:
i have it in Qualcomm HS-USB QDLoader 9008
whats the next step?
Click to expand...
Click to collapse
Run MiFlash and flash a FULL_EDL package
You have to find one for the A2017U, you can't use packages for the A2017 kr the A2017G or you'll mess up even more

Bricked phone but can still get into EDL mode

Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.

Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit

daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason

Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?

daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud

daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible

i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!

A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted

The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.

i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152

DFU Mode - Mystery

Hi,
I know that there are already several threads where this is being discussed on this forum, just wanted to add this one so that people could share how they overcame it, As some let their battery die and then Vol down+Power into EDL, whereas some dismantle the phone and short the testing point, whereas some even got lucky with the Deep Flash Cable.. therefore it would be of benefit to all if all such solutions are shared under once single thread so that anyone suffering from it can look into one single list of options that he or she has!
As someone who is still figuring out how to escape this death trap, this would be great!

It's not a death trap for me ?? I can't even get it to that point. It's an amazing phone and I want to keep using it. I can't tell you how many different combinations I've tried in the last 24 hours and I have yet to get miflash to see my phone. All while adb and Qualcomm things are working exactly how they're supposed to. It's so frustrating that I can't even get my device into a state that needs recovering, especially with soooo many amazing ROMs for it!!
A2017U working on Verizon network with no problem.
Bone stock
Please help

@ CASEY_K Have you tried different USB ports or a different computer?

RUNNERX said:
@ CASEY_K Have you tried different USB ports or a different computer?
Click to expand...
Click to collapse
I have tried both ports on this laptop multiple times. That's my next guess. Only downfall is I only have this one and don't know many other people that have one.
I'm getting the error, "parameter length can't be less than zero"

Had to disassemble the phone and follow the 4th category brick guide for me. I tried everything else, but that's the one that actually worked.
A2017G

Can anyone share on how to get to the FTM mode from DFU ??? how did they achieve it!?

SBFarooq said:
Can anyone share on how to get to the FTM mode from DFU ??? how did they achieve it!?
Click to expand...
Click to collapse
Supposedly fiddle enough with the buttons until it works, for example: https://forum.xda-developers.com/ax...estigation-t3511191/post74092981#post74092981
Some drain the battery first.

My ZTE is put into FTM mode by holding volume + and plugging in a USB cable that is connected to a computer. On some phones FTM mode will have ADB enabled. From ADB the command "adb reboot edl" will put the phone into edl mode without a deep flash cable.
If the phone contains a Qualcomm chip and you have Qualcomm drivers installed EDL mode will cause the phone to register in the device manager as a com port labeled Qualcomm 9008. Miflash recognizes the Qualcomm 9008 mode.
Sent from my SM-G935V using Tapatalk

TysonBeall said:
My ZTE is put into FTM mode by holding volume + and plugging in a USB cable that is connected to a computer. On some phones FTM mode will have ADB enabled. From ADB the command "adb reboot edl" will put the phone into edl mode without a deep flash cable.
If the phone contains a Qualcomm chip and you have Qualcomm drivers installed EDL mode will cause the phone to register in the device manager as a com port labeled Qualcomm 9008. Miflash recognizes the Qualcomm 9008 mode.
Click to expand...
Click to collapse
Don't bump completely dead threads, please??
Also you would be right if this didn't pertain to DFU. FTM almost never works when your phone is DFU bricked

unbrick "dead" tablet Lenovo TB 4 10.1 (X304F/L)

I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).

My tutorial on the Russian forum has been updated, missing the source file for MiFlash.
Today it was added.

Downgrade from Android 8.1 to 7.1.1 is possible!
Applies to tablets with unlocked bootloader.
The entire factory clean version must be reinstalled.
Use the same installation and tools as in the introductory link.
It is necessary to install in EDL mode.
To start EDL mode (driver 9008) from a working tablet, follow these steps:
1) Turn off the tablet
2) run the device manager in windows - ports
3) run and set up MiFlash (firmware path,option "save user data")
4) connect tablet to computer (USB)
5) hold all three buttons on the tablet (power+volumeUP+volumeDown) until the 9008 driver loads in the windows manager
6) run "refresh" in MiFlash without delay and immediately afterwards "flash"
It is important to start recording as soon as the driver is loaded, otherwise the input will close even if the driver remains loaded!
If there is a delay in recording, the EDL mode may close and the recording will not work.
In this case, you must start by disconnecting the tablet and turning it off.
The restored tablet remains unlocked (if you have unlocked it previously) while Lenovo updates work.

Hello i want to contact you are you still alive
I want to unbrixk my tab i accidentally deleted aboot.img

Hello i want to contact you
I want to unbrick my tab are you available???

Just to clarify, the test points on the board are the points you see on the board labeled "FORCE, VDD, TX, RX" and can be different sizes.
One such point was hidden under a folded out frame and that is the correct one. Connect this point with a needle to the metal frame and follow the order of operations in the instructions.
MiFlash - recommended:
Download in progress... | Xiaomi Tips
Thank you for downloading. Your download should start automatically in a few seconds.. Download FAQs Broken download link? Let us know. Is the file safe
xiaomitips.com
System:
TB-X304L_S000035_170703_ROW_QFIL.rar | by yulianto adikragil for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Follow the procedure.
After loading 9008, release the checkpoint as soon as possible.
I used XiaoMiFlash (beta).
You need to prepare XiaoMiFlash before taking action.
"Refresh" and "flash" should start immediately after disconnecting the breakpoints.
The path to the XiaoMiFlash firmware should only be "bat" files, not "images".
The fact that the 9008 driver loads in Windows indicates a functional boot.
You "only" need to complete the remaining steps correctly and on time.
If unsuccessful, repeat the procedure by disconnecting the battery.
If you changed the drivers manually, uninstall them first.
Let them download automatically.
There is a risk that this is not the 9008 driver.

You'll still need this:

The files contained in the image folder TB-X304L_S000035_170703_ROW_QFIL.rar need to be put into the inage folder X304L and then use this folder for MiFlash.

I have to thank You a lot. You saved my good old Lenovo. First when I read Your tutorial, I thought that could never ever work. I was exactly same problem as You were. I tried everything, even raindance. Nothing not helped. Two weeks with drivers, softwares, thousand tutorials...etc. But that did the trick! Now when I know How to unbrick totally dead Lenovo, it is actually only 10 minutes and lenovo fired up again.
Actually it is really easy do with linux by using QDL. No driver hassles or timing when connect or similar. I've linux installed, so if someone gonna try this, Live linux from USB stick working as well. User friendly could be for example Linux Mint Mate, Ubuntu...
1. Install Linux Your USB device and boot it by using Your PC.
2. Get QDL flash tool for Your PC (free and very easy to use).
3. Install QDL depencies: libxml2 and libudev (fastboot is optional, if unlocking bootloader same time).
sudo apt-get install libxml2 libudev fastboot
4. Stop modem manager: sudo systemctl stop ModemManager
5. Start flashing : ./qdl --storage emmc --include <Your Whole Stock firmware path> <Firehose path> <RAW program path (xml format)> <patch0 path (xml format)>
Enter and QDL start waiting for EDL device....
Next open second terminal for monitoring: dmesg and as You can see it is coursed 900e mode.
Next disconnect battery and leave it disconnected whole process time. Now it is time to short testpoint. reconnect device to PC when testpoint is shorted and check dmesg . When You'll see it changing 9008 mode. You're ready to start flashing. At this moment QDL still waiting EDL device > Ctrl+C and start over again ./qdl ...etc and flashing starting.
This is how easily You can hard unbrick Lenovo X304F Tab4 10 or X304L.
In my case I accidently Flashed X704 firmware to my device. It went just fine. But when booting, You know. I tought that's it! But It wasn't. Thanks again @StaryMuz.

I'm glad you found my advice helpful. The Linux tutorial is useful and it's good that you posted it.

i ended up bootlooping on the lenovo logo (tbx304L) and locked bootloader
and is it necessary to be on stock 8.1 to downgrade? @StaryMuz
the recovery shows 7.1.1 but still bootlooping

StaryMuz said:
I managed to identify the test point on the motherboard.
This allows the tablet to switch from Qualcomm HS-USB Diagnostics 900E driver mode to Qualcom HS-USB QDLoader 9008 mode.
My tablet could not be booted into bootloader, recovery or system.
Button vibration did not work.
The tablet only logged on to a PC with the Qualcomm HS-USB Diagnostics 900E driver.
The EDL cable did not help and the buttons of the 900E driver only restarted.
Photos and brief instructions I posted on the Russian forum here:
http://4pda.ru/forum/index.php?s=&showtopic=849554&view=findpost&p=90398828
I attach the photo here.
Only one hidden test point is connected to the metal frame (needle).
Click to expand...
Click to collapse
Many of the links for the rescue files are now missing but I will share how I rescued my TB-X304F in 2023. I followed your photo indicating the test point location/ trick along with the Lenovo Rescue and Smart Assistant program.
Rescue and Smart Assistant (RSA) - Lenovo Support US
support.lenovo.com
1) open the tablet
2) Remove the metal cover
3) Carefully Peel/bend the metal frame around the chip on the right in order to find the hidden test point. It is right under the frame. (the frame should gently move away from the chip, the frame is not difficult)
Now be sure to install the Lenovo Rescue and Smart Assistant program on your PC. Launch it, and look up the tablet's firmware by either S/N or manually looking it up. Download the necessary firmware files within the program until you get to the point of start rescue. Click Proceed, ok, ok, until you get to the screen that says: Find QDLoader COM Port which is asking you to hold the volume +&- but we have already tried that and didn't work so at this point then do the following:
- disconnect the battery
- connect the USB cable to the phone and computer
- Connect the test point with a needle (touch) to the frame and hold
- connect the battery and watch the driver in the windows manager
- as the 9008 driver loads, disconnect the point and let the Lenovo Rescue and Smart Assistant do its thing.
Tablet rescued!