I have an HTC Incredible 4G LTE. I underwent the process detailed here to unlock the bootloader.
When i got the HTCDev website, i ran a fastboot command and it just says <waiting for device>. I tried to detect the device with adb devices, and fastboot devices, but with no success. the THC Sync manager is not installed. HTC drivers should be installed. I am plugged into a USB 2.0 port, the same one used through out the process (i even tried the other one).
I am at a loss as to what is happening. I do know that the device manager sees my phone, and shows the drivers as the latest version. It does give this message:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
The device manager is listing the driver as version 2.0.7.3.
EDIT: Was able to get driver updated to 2.0.7.18
Also, when connected to the computer normally an orange light shows near the speaker. I wasn't concerned at first as I know the Android OS is not actually up and running on the phone, but do wonder if it doesn't indicated a problem.
Another note, I am running Windows 8.
EDIT 2: More research has yielded the following "Android Bootloader Interface". Every reference installing this from the usb_driver in the ../extra/google/usb_driver folder. When I attempt to do so from the device manager Have Disk ui I receive the following error
The folder you specified doesn't contain a compatible software driver for your
device. If the folder contains a driver, make sure it is designer to work with
Windows for x64-based systems.
Click to expand...
Click to collapse
EDIT 3: Removed entire android sdk, redownloaded and installed. Removed all HTC software and drivers. Booted phone into fastboot, and windows detected an "Android 1.0" device, installed the Android Bootloader Interface driver from the google usb_driver successfully. However, fastboot devices still does not detect the phone, and device manager still shows code 10.
As of now:
No HTC Sync, or HTC Driver
phone booted into fastboot, phone displays "FASTBOOT USB"
phone is set to usb debug
phone is connected to pc with good cable to a usb 2.0 port
I have:
rebooted pc, re-installed drivers, changed usb cords, changed usb ports, even tried a usb 3.0 port, i have tried some generic fixes for code 10 errors, and completely run out of ideas
EDIT 4: After using a different computer running Windows 7 I was able to complete the process, however, i would very much like toresolve the issue with my own PC, as the Win7 laptop is not mine. I utilized the adb/fastboot/winapi files from my Win8 machine. Win7 automatically found HTC drivers (2.0.7.18) and everything seemed to work just fine. Any ideas?
Related
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
killfire72 said:
Hello,
I cannot get the bootloader unlock working on my Win 8.1 laptop by any means. If I try through hasoon2000's toolkit, I get the error that the ADB server did not ACK (whatever that means). If I try using the command line and HTC's official method of getting the TokenID, I get a message that a certain ADB-related dll is not installed. I have installed the USB drivers that come with hasoon2000's toolkit about 4 times now. I installed the Android SDK and even Samsung USB drivers. I'm going to uninstall everything, can someone walk me through the step-by-step to get things working? I've read that USB 3.0 is the problem, but I only have USB 3.0 ports on my laptop.
Click to expand...
Click to collapse
Use another computer if you can.
I had similar problems until I used this version of adb
http://www.mediafire.com/download/e5mieo2vxjd71ws/android-tools.zip
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
ashyx said:
Run everything from the downloaded folder.
First of all ensure you have USB DEBUGGING enabled in DEVELOPER OPTIONS in the phone settings.
Open the downloaded folder then right click inside the folder while holding shift then choose 'Open command Windows here'
Plug in the phone using the original HTC usb cable then in the command window type ADB DEVICES. The response should be a device comprised of letters and numbers.
If you don't see any device attached try swapping the cable to another usb port. If you see your device attached then follow the unlock instructions at HTCDEV as its the most reliable way.
If still no device then it could be a usb driver problem. You should here a ding when you plug your phone in.
Make sure the Unlock_code.bin is in the above folder when unlocking.
Click to expand...
Click to collapse
That version of ADB didn't work for me either. Anyway I was able to get fastboot to work but not ADB so I was able to unlock and root and everything through a strange method using only fastboot.
Second question, if I am switching between AOSP roms, say for example CM to PA, can I dirty flash or do I have to reset?
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
xeron72548 said:
ADB does not work with USB 3.0 ports yet on Windows 8 or 8.1. You have to use it on a USB 2.0 port. I have had best results with Windows 7. Fastboot, however, works just fine on 8.1 and 8
Click to expand...
Click to collapse
Not so, I and others have ADB working fine on USB 3.0 ports.
The problem is Windows 8 driver signing enforcement blocking the install of drivers. You need to go to advanced startup options to disable it.
Download these drivers first and extract: http://www.mediafire.com/download/i3lcm7dwl581518/ADB_Fastboot_Drivers_Win81.zip
Follow these instructions to disable driver signing enforcement: http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
Once fully booted go into device manager and you should see a device called 'Android 1.0' with an exclamation mark.
Right click 'Android 1.0' then 'update driver software' then 'Browse my computer for driver software'
Click the 'Browse' button and then browse to the driver folder 'ADB_Fastboot_Drivers_Win81' extracted earlier then click next to install the driver.
You will get a warning about unsigned drivers, just ignore and continue.
The drivers should install and you should see a new entry in device manager called 'Android phone' which means the ADB driver is installed.
ADB should now be working.
Thank you so much for this. Have been wondering for a very long time
Sent from my HTC One_M8 using XDA Free mobile app
It sounds like you've got plenty of technical help already, but I will say that I use ADB perfectly fine on my desktop with Win 8.1 so it's possible. I also use hassoon's toolkit occasionally with no issue.
Before I could get the desktop to recognize the M8 I had to completely uninstall all drivers related to my previous galaxy nexus as well as remove any mention of the device in Window's USBdeview. After a reboot, I just plugged in the M8 and windows automatically installed the necessary M8 drivers. I can then run fastboot and adb from the toolkit.
I ended up uninstalling the MSFT USB 3.0 drivers and use the Intel USB 3.0 drivers instead on my Win8.1 laptop that has only USB 3.0 ports. Works great.
I've been eager to try Scott Crosler's new CM11 but didn't have time until tonight. To ensure cleanliness, at the bootloader I erased cache, system and userdata. I've flashed ROMs dozens of times, and as usual, there were no problems with fastboot recognizing the device.
I then entered CWM, and it was the darndest thing: three fast USB connection beeps and this error:
"Windows could not install driver software for your device."
But I've had the generic USB drivers installed for two years! At first I thought it was interference from the Samsung drivers when reflashing my wife's tablet, but I tried our two laptops, same result. No matter that I right-clicked "Nexus 7" in Device Manager and pointed it to freshly downloaded drivers, even that I tried installing drivers using the SDK Manager,
"Windows could not install driver software for your device."
I've read that turning off USB debugging helps, but um, with an erased /system, I had nothing to boot into!
Normally I prefer flashing via ADB sideload. To get up and running again, I flashed TWRP and used its feature of mounting USB-OTG and flashing from an external drive. Once I got into CM11, I turned on and off USB debugging, but I still can't install the USB drivers, and ADB can't recognize any devices. At least there's flashing via external flash drives.
Has anyone had the like?
didn't see win 8.1 mentioned but thought this may help? http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908. I have had problems with drivers in past. adb composite are the ones that work for me. I simply removed drivers under android devices in device manager then plugged in device. GL.
Windows 7 here, but thanks for the suggestion anyway.
This morning I can connect it as a media device, and it's in Device Manager just fine as "Nexus 7." But turning that off, it becomes "flo" in Device Manager and can't find the updated drivers. And either way, I still can't get it recognized while in recovery mode. Ah well, as I said, at least TWRP has the option to mount USB OTB and flash files from an external drive.
Let me add that I already tried another cable (for our Samsung tablet), and tonight I see that I can connect it in MTP mode. In MTP mode, it shows up just fine in Device Manager (under Portable Devices), but turning off MTP throws it under Other Devices with the dreaded ! (and I just can't get it to install the driver no matter where I point it to). And no matter what combination I try, I still can't get ADB to recognize it at all.
Although this is for Windows 8.1 it may apply to your situation: http://forum.xda-developers.com/nexus-7-2013/general/windows-8-1-users-careful-t2856908
As I e-mailed you, sfetaz's suggestion of USBDeview is part of the solution! I still can't get it recognized in booted Android as anything but a media device, but now it's fine during recovery. Darndest thing I ever saw in 19 years of dealing with Windows drivers.
http://www.nirsoft.net/utils/usb_devices_view.html
Then in an old bookmark, I tried Koush's universal ADB drivers.
http://download.clockworkmod.com/test/UniversalAdbDriverSetup.msi
Even if USBDeview hadn't helped, it was still good to clear out all the old devices I no longer use. Definitely a handy utility to keep around and recommend.
I am new to android, HTC One VX being my first phone ((Got it like Last year as a gift iirc)).
Using Stock rom and my os is 8.1 pro x64
I am trying to unlock the bootloader.. I went to HTCdev, followed the directions for unlocking the bootlader.
1. Got the Android SDK and installed
2. Got the HTC SYnc Manager for the drivers.
3. Got Fastboot and moved it to where the ADB .dll file is.
I get my phone into bootloader after making sure USB Debugging is enabled, then I plug it into my computer. After a few moments, Windows pops up with USB Device is not recognized. I check Device Manager, it shows "My HTC" under unknown devices. I manually point the thing to where the W8 x64 driver is , and it says the driver is up to date. Bring up the Property info of the device, this is what is showing int he text box,
Code:
A request for USB BOS descriptor failed
Just to make sure, I navigate back to the ADB folder, bring up CMD there and type in
Code:
adb devices
. No device was listed despite my phone being connected to my computer. Tried it with 3 different cords, front and back of my computer. ((USB 3.0 ports.))
I put it in one of my USB 2.0 ports and the issue persists, the device status shows
Code:
A device which does not exist was specified
.
Is there anyway to fix this, its quiet annoying, Apparently doing clean reinstalls of everything isn't going to fix it for me.
My oneplus 3 isn't found in com/ports on windowsill 10. It's unable to load recovery and won't boot to system. Fastbook still works and has a unlocked boot loader. Trying to install stock firmware to restore the device for se again. Any help would be greatly appreciated.
Try loading drivers, have no issues here. Also run cmd prompt by right clicking on cmd.exe and selecting "Run As Administrator"
Sent from my SM-N930T using Tapatalk
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Also make sure USB debugging is enabled in the developers settings and you have the correct USB mode enabled (not charging)
Sent from my SM-N930T using Tapatalk
jaydubya24 said:
Ok. Thanks. I'll try that once I'm back home. But the drivers have been installed several times with no sucess.
Click to expand...
Click to collapse
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Will_Xda said:
If you have still have no luck it may be worth showing whats seen in device manager when OP3 is plugged in. (Possible unknown device)
Don't have any issue with WIN10 myself along side OP3 but have had numerous driver related issues on other devices with WIN10
Click to expand...
Click to collapse
here is the device manager
setup driver and try in twrp
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
jaydubya24 said:
Thanks. I'll give those a try tomorrow. Just to mention in case I wasn't clear with my info. The OP3 can't boot into recovery. It'll say oneplus powered by android then a blank screen. And yea, I did mean fastboot lol. Thank so for all the info also. I'll post what I discover asap.
Click to expand...
Click to collapse
One more thing. Connect the phone to a USB 2.0 port and not a 3.0 port. It may not be recognised in a 3.0 port.
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what I found on USBDeview. There are two other versions of the OP3 on this list. But they do not show as being connected while the phone is in Fastboot. Im unable to access the OS to enable anything that may help with it being seen on my computer.
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Win7 works and i dont tryed the nice tip on site2.
i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
update on the op3
peterk-1 said:
A few pointers:
Is this a "home/personal" computer - USB devices can be prevented from connecting via registry hacks and the Group Policy editor ( wonder if some av software could require authentication???).
With Windows 10 you should have native "Microsoft" drivers and no external drivers need to be loaded,
It should be detected when the usb connection is "charging" and you should see/hear Windows "changing" drivers as you change the usb connection to MTP,PTP,Midi.
I presume you've tried different usb ports and if possible alternative cables
If you plugged in the OP3 powered off and then switch it on then it should be detected by Windows before Android boots - otherwise you could never connect a bricked device or follow Oneplus.net flashing instrutions (connect device booted in recovery mode)
Try running USBdview from http://www.nirsoft.net/utils/usb_devices_view.html Note 32 and 64bit versions!!!! The program will show all usb drivers that have been used and show which ones have their device connected. You can select and delete drivers. You can see which drivers have been used for the OP3 by looking at the Vendor and Product Id's (VID/PID) columns . OP3 has a VID of 2A70 and a PID of 9011 (may be others). If you have in the past connected the OP3 on the computer then look at the Hub/Port columns this shows the USB socket that worked.
In Device Manager I would expect the OP3 "out of the box" to just show up under "Portable Devices" as "ONEPLUS A3003" and with usb debugging enabled as a second entry either as an ADB device under "Android devices" or as "ADB interface" under "Universal Serial bus devices" You said that "Fastbook" worked - Did you mean Fastboot? - if so then the device should be showing up somewhere in Device Manager. Try "fastboot devices -l" for any clue.
Click to expand...
Click to collapse
This is what shows up after the one plus boot logo appears.
I had similar problem. I was rooting my 1+3. I went to device control settings in WIN 10 and removed 1+3 drivers. Next time when i was in fastboot mode windows installed drivers. :highfive:
I used the ones that came with 1+3
jaydubya24 said:
This is what shows up after the one plus boot logo appears.
Click to expand...
Click to collapse
I think this thread will supply the solution. "your" problem is at this post https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/page-4#post-15169580