Database Users

HUAWEI P9 lite (VNS-L21)-ROOT PROBLEMS

Hi!
First of all, I'm sorry for my English...
I have unlocked and rooted my device (Huawei P9 lite).
I have install the TWRP bootloader and I tried to install a new costum ROM, but my device was turned off and never opened again. (Maybe: Low battery).
I try to charge my device but it didn't recognize the charger. So, I removed the battery from device (with the help of a technician) and charging it.
After all, I tried again to root and install TWRP but the device doesn't open or recognized of my PC...the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
What am I doing?

First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?

Schlengge said:
First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?
Click to expand...
Click to collapse
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612

Use <[DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim> and try again to da all from begining...
- check bootloader - lock/unlock
- flash stock recovery/twrp
- root it if is necessary
- copy update.app to SDcard into dload folder and try to reflash device.

I tired... but it didn't recognized my device!

Vangeliskar1 said:
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612
Click to expand...
Click to collapse
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?

Schlengge said:
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?
Click to expand...
Click to collapse
No...
I can't!
It doesn't work (Volume down + power key)

Vangeliskar1 said:
No...
I can't!
It doesn't work (Volume down + power key)
Click to expand...
Click to collapse
So the device does not respond in any way?
Hmm...
Maybe refer to the CM thread and hope that someone there can help you.
Don't know if Meticulus checks out this forum section.

You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?

gtdaniel said:
You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?
Click to expand...
Click to collapse
Maybe...I don't know!
I have this message:
C:\adb>fastboot devices
9JT0216627000650 fastboot
C:\adb>

Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...

gtdaniel said:
Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...
Click to expand...
Click to collapse
I had tried bu it doesn't work...
I have this massage:

Drivers on PC are installed right? Just to make sure...

May be I'm wrong, there is two options to active in develloper menu ? USB debug and OEM I don't know why ?
Excuse me if I'm off topic.

Schlengge said:
Drivers on PC are installed right? Just to make sure...
Click to expand...
Click to collapse
Yes everything is allright!
I have install and Hi suite!

Phone have any control? Reboot? Power?
When you conected to PC at Devices on PC appear something?

No...it is dead....
On PC: yes! It is apeared to devices

Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)

gtdaniel said:
Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)
Click to expand...
Click to collapse
It is apeared at devices with that name: android Bootloader Interface
Tool?
Which tooL?
In comand window?

That tool: VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim
You attached a image with phone in fastboot mode. Can you replicate again that stage?
In that stage use that tool and see if phone appear there.

Oneplus 5 trouble with unlocking bootloader and TWRP

Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.

hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader

I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.

bro do u find solutions for this

I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!

jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.

Bricked or what?

Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance

TrelosEisai said:
Hello guys. I have the x720 leeco. My problem is that i wiped all and no rom is installed and when i connect the phone to the pc i cant get it done with the drivers so i cant see the internal storage. I can boot on REcovery and Fastboot. Can anyone help me??
Thanks in advance
Click to expand...
Click to collapse
Put the rom on an USB stick, connect the stick to the phone with adapter, go into TWRP and flash the rom.
Easyest solution.

Okk i ll try it

Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it

TrelosEisai said:
Unlucky cant read otg, just putted an micro usb to typec adapter and a micro usb flash drive and cant see it
Click to expand...
Click to collapse
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5

Oel said:
Ok. Than try to flash a stock rom through all in one tool:
https://www.google.com/amp/s/forum....ment/tool-tool-one-mauronofrio-t3580611/amp/5
Click to expand...
Click to collapse
Agreed,
You are not bricked.

i cant see my device thats the problem

TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Worst case you can use Qfil.
But first disconnect all unneeded peripherals, and try another cable if possible. Go read the unbricked tested and working. Search the thread for my name, to everything you need in 3 or four posts
Sent from my Pixel XL using XDA Labs

TrelosEisai said:
i cant see my device thats the problem
Click to expand...
Click to collapse
Yeah, but did you installed the all in one thing with the right drivers?

Oel said:
Yeah, but did you installed the all in one thing with the right drivers?
Click to expand...
Click to collapse
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.

TrelosEisai said:
which drivers?? i cant do the qfil cause i cant see the phone in pc. when i open it in leeco logo when i connect the phone to pc it says windows cant recognize it.
Click to expand...
Click to collapse
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.

tsongming said:
Go read the unbricking thread, it is going to take you days to read, understand, and finally unbrick it. If you are not seeing the device in the system manager of your computer ( Assuming you have a PC) then maybe you are actually bricked.
But, you own a phone that can be unbricked, no not a big deal. It can be resolved, the instructions in the unbricked tested and working thread are explicit go read it.
I create several how to's within that thread on unbricking, and have updated the links on the software tools needed. I have personally unbricked 7 leeco, and several others unbricked their phones by following the advice of everyone who contributed to the thread.
Everything you need and more is there that thread, waiting for you.
Go there get the files, read the instructions and soon you phone will work again. Do not download the qfil from the Original post...it doesn't work. I don't have the links to paste at the moment, nor the time to search for you Just use the thread search bar and type my name to get consolidated steps read through all of the posts, because its a progression.
There are three methods you can use to unbrick, the easiest method is probably Qfil, and Flash 2.0
Essentially you need the Qfil: le_zl1_qfil_ufs_fix , FlashOne2.0 files, go ahead and download prog_ufs_firehose_8996_ddr just in case. But it should download automatically. You need to follow the steps to get your computer ready to unbrick the phone...all in the thread instructions.
Once you do it once successfully, it will become easier with each try.
Click to expand...
Click to collapse
Ok i am starting now i will come back with the results

As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.

TrelosEisai said:
As i understand my phone is not bricked cause i can go into fastboot and REcovery. The problem is i dont have OS installed so i stuck at Leeco image. The other problem is when i connect the phone with the Pc this happens on device manager. So how i can make it to see the internal storage and put inside the phone the rom.
Click to expand...
Click to collapse
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.

Ascertion said:
Install Google's USB ADB and Fastboot drivers.
https://developer.android.com/studio/run/win-usb
Can you boot into download mode (I think it's volume down + power) and then connect to PC. After that, you should see the unknown device on device manager. Try to right-click on it and update drivers. On the next screen, select that you have drivers and you'd like to pick your own (not the Windows Update option!) Then select Manufacturer Google and Fastboot/ADB debugging option. Device might work in fastboot now, you can test by doing "fastboot devices". If that works, then you can install ROM via Fastboot.
If this doesn't work, you can revert changes by going into device manager and uninstalling the driver for that device.
Click to expand...
Click to collapse
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options

TrelosEisai said:
I cant find the option for Manufacturer Google for the Fastboot/Adb debugging options
Click to expand...
Click to collapse
Hi, sorry for the late reply.
Are you able to see these in screenshots? Between steps 2 and steps 3, you might need to select Android ADB or Android Device before you can see Google in the dropdown.
Maybe after these you might be able to see device in fastboot?

Cannot unlock bootloader, phone not recognized in fastboot (RN7)

I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?

Same here

connect it through a USB hub, it worked for me

Cicciocap94 said:
connect it through a USB hub, it worked for me
Click to expand...
Click to collapse
A usb 2.0 hub did the trick for me, using a usb 3.0 only laptop. It did not work with my usual usb3 hub.

N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.

Maybe it's helpfull to install a VPN, in my case flexvpn from playstore, before starting unlock- process...

I solve with an old PC...but I wait for 270h to unlock...

thank you all for your comments, I don't know exactly what happened but Mi unlock recognized the device and asked me to wait for 33 hours to finish the unlocking process.

arunbiju969 said:
Hello,
sorry to hear that I'll try to help you but I'll need a screenshot shot of your device manager page (assuming you are using a windows PC). Make sure that you connect your phone in fastboot mode before taking the screenshot.
Click to expand...
Click to collapse
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim

N7Witcher said:
I don't know how but today Mi unlock recognized the device and asked me to wait 33 hours before unlocking.
This is my first time flashing a device and I'm feeling a bit nervous, if it's not much to ask, could you help me out with some questions? I would be very, very grateful
Can I wait 48 hours before attempting to unlock the bootloader again just to be sure? or it has to be exactly 33 hours?
I plan to flash the global RN7 rom found on en.miui.com/a-234.html to my device (Model M1901F7H), is this the correct one?
How can I lock the bootloader again after flashing this rom? I don't want to keep it unlocked
Do I need a custom recovery? I'd like to keep the stock one if possible
Is there a way to backup my current ROM? In case I need to issue a warranty claim
Click to expand...
Click to collapse
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?

arunbiju969 said:
These stuffs seems quite tough and tense at first but its quite easy and safe if you understand what you are doing...and yes I'll answer them one by one
1)The wait period shown by the unlocker is the minimum time you would have to wait to unlock your bootloader so any time after that wait period is fine(But is a chance that even after the wait period the unlocker would give you some error if that happens PM me or quote me)
2)The device code name for Redmi note 7 is lavender so just flash the rom made for lavender I'll give the link to download the stable rom https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv10/
From the above link download the latest version for HMnote7 ,in my opinion European is better than the original one but best rom so far is mokee.
3)You can lock your bootloader using fastboot commands or by flashing the device with miui using Flash tools...but that is not necessary open bootloader is better
4)Yes you need a custom recovery and after flashing the rom from your link the custom recovery will be replaced by the one given in the rom(Don't flash that one! Use the one i gave you if you still want miui but if you like stock then go for mokee)
5)No need to backup it is available online and it can be flashed using flash tools also doing these things and keeping the bootloader unlocked won't void your warranty so there is nothing to loose warranty will be give as per your purchase invoice date! Also if you backup that rom using a custom recovery then it can be use as failsafe if you get into a bootloop or something..but that rom is not mandatory any roms bqckup would do just fine
If you still have doubts I'll be happy to clarify ?
Click to expand...
Click to collapse
Thank you very much for taking the time to answer all of my questions! You've been very helpful.
I've been thinking about what you wrote but I think I wanna install the official global ROM via Mi Flash. If I select the "clear all and lock" do I risk bricking my device? That's my main concern.
I didn't mention it earlier, but the only reason I want to unlock the Bootloader is so I can flash the official global Rom, (my carrier takes ages to update the rom they install, and it's also full of bloatware) this is my main phone (less than a month old), and while I understand that keeping the bootloader open and using custom ROMS could enhance my user experience, for the time being I want to keep things simple and safe. Maybe in the near future I'll start tinkering with custom rom and recoveries.

Thank you everyone for your suggestions! I don't know exactly what did the trick, but I was able to unlock the bootloader and flash a global ROM. I've encountered some issues with it but that's another topic.
Once again, thank you all!

N7Witcher said:
I've been trying for almost two weeks to unlock the bootloader on my Redmi Note 7 (Model M1901F7H) because I want to flash the official Global ROM (it has a carrier modified ROM) But Mi unlock REFUSES to recognize the phone when it's connected in fastboot mode.
I've searched the web for a solution and tried a dozen things, including following every single step on this thread: https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751
But I haven't been able to solve the Issue. The device is recognized by all the computers I've been using while plugged in file transfer mode, but none of them recognize the device while it's in fastboot.
Some of the things I've already done include:
Trying 3 different PCs (both AMD and intel)
Disabled signature driver enforcement
Trying USB 2.0 ports
Installing old versions of Mi Unlock
Installing Xiaomi Usb Drivers
Installing 15 seconds ADB drivers
Intalling Mi unlock directly to C://
Enabled OEM unlocking and USB debugging on the device
Linked my Mi Account to the device
Restarting the device and computer multiple times
Re installing drivers over and over again
I know this is the first and supposedly easiest step of the whole process, but I'm stuck and close to giving up (but I really don´t want to).
Can anybody please help me out?
Click to expand...
Click to collapse
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection

Anirban Kopty said:
I have finally understood the problem. What you need to do is not install the ADB Drivers separately, but you need to check for the unknown Android device that is shown under the USB devices when you connect the device (via USB port).
You have to update that driver with the ADB Drivers.
That will only solve the problem of the fastboot detection
Click to expand...
Click to collapse
Can you give detailed instructions on how to "update that driver with the ADB Drivers"? After installing the 15 secs ADB drivers and Xiaomi drivers, my Note 7 is still being recognized as an "Android" device with the yellow caution sign.

"Sahara communication error" on Msmdownload tool with Hard bricked Oneplus 6T locked bootloader with custom rom (allowed on DivestOs)

Hi,
As in the title i've tried to install DivestOs and everything was fine until the relocking of the bootloader (very likely skipped a step).
Now i'm trying to use Msmdownload tool to flash stock rom and reflash DivestOs after that. My hardware is a laptop with usb 3.0 ports OS: Fedora 36 (which i used to flash divestos) and a windows 10 VM ( i use this for msmdownload tool). The phone error says "your device is corrupt. It can't be trusted and will not boot".
But i continue to get the "sahara communication error", i tried to follow guides and tutorials but it doesn't work. I tried to reinstall qualcomm, oneplus drivers, Windows 10 VM and i also tried the volume up (+) and power button trick. I also tried different msmdownload tool for oneplus 6T. Is there a solution or should i just bring it to a repair shop? Is there a linux msmdownload tool alternative?
Thanks for any help

Have you tried simply unlocking it first? The unlock ability won't go away once locked.
As for flashing via VM, it works, but you need to pass a USB host controller into the VM as there are multiple VID/PID pairs used for EDL.

Hi, thanks for answering, i tried to just unlock it as said on the official site,( i also asked the dev that created the rom). So i should find the drivers for usb controller for windows? Thanks again

ASPi-3 said:
Hi, thanks for answering, i tried to just unlock it as said on the official site,( i also asked the dev that created the rom). So i should find the drivers for usb controller for windows? Thanks again
Click to expand...
Click to collapse
DivestOS *is* my project.
I presume this was you asking here?
https://www.reddit.com/r/DivestOS/comments/xp9ggo
I gave the links there

SkewedZeppelin said:
DivestOS *is* my project.
I presume this was you asking here?
https://www.reddit.com/r/DivestOS/comments/xp9ggo
I gave the links there
Click to expand...
Click to collapse
Yeah it's me, i'm gonna try to solve the problems with the usb host controller than i'm gonna flash the stock rom and redo the flash "properly" this time . Thanks again for the help