Database Info

[Q] restoring bricked oneplus one problem

First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks

gl411 said:
First of all, when I'm in the wrong thread, sorry!
So here I go. I guess i bricked my 1+1. Doesn't turn on, only black screen and if i push a button, it vibrates. Looked up for solutions, and found one here somewhere. It's with the recoverytool or with ColorOS.
So I tried to follow the steps. Everything works fine, in Device Manger, the phone is now recognised as Qualcom HS_USB QDloader 9008 (COM3). Til here no problems at all. Then I installed the set-up file, compatibilitymode, run as admin.
I open the recoverytool, and i scan for the device. It should appear as COM. But nothing shows up. It's weird because Windows recognises the device.
What am I doing wrong? What can help?
Thanks
Click to expand...
Click to collapse
Have you installed the Qualcomm driver?Its very tricky,Windows wont allow to install it easily.

Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?

gl411 said:
Yes I did, I was able to switch to non signed in Win8 via F7 in a menu. Thats why it changed from BULK to qualcomm qd9008 on a COM port. Or cant I be sure its done propermy when the name changed?
Click to expand...
Click to collapse
It should be the driver problem,no other choice.

maskelisuvari said:
It should be the driver problem,no other choice.
Click to expand...
Click to collapse
The easiest way for unbricking oneplus (yes, I tried it): http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
ColourOS firmware has all needed files for proper flashnig, including right tool for doing that.
Only thing that didnt work on my Win 8.1 x64 was drivers mentioned in post above.
I had to use this QHSUSB_DLOAD drivers from member DallasCZ (that I used for unbricking ZTE v9180). Only with that drivers my Windows recognized bricked phone and Flash tool could find and flash it.
Flash tool in only on chinese, that is a bit problem, but instructions given in post I linked are more/less usefull.
This is a link to DallasCZ shared folder with qhsusb drivers:
https://drive.google.com/folderview...&usp=sharing&tid=0B1T7tp6tJ_3kQkZSWjNsazJZbGc

If you are sure the driver is okay,plug in the usb cable and out and in,until you see the green line on the tool.Also you can follow the guide as in below link:
http://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
The same thing but this time you can flash CM11s instead of ColorOs.Also there is a video.Pls check it.

Ok so I did the process over and over again, the sixth computer did it right! I was back on ColorOS and now back to CM11S.
This thread can be closed, thanks for the help!

No problem,glad to hear you solved the problem

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?

Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.

broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )

Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!

broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541

help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????

redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...

Got fully bricked oneplus one. Is it possible to flash fastboot through UART pins ?

Hello, guys I am noob af so when I was flashing Ubuntu Touch I disconnected my phone and now its don't even show up as USB it just dead no lights no anything but battery is full I checked with multimeter. So I was wondering if its possible to use UART pins to flash kernel so it can boot. Thank You all so much and if it possible just point right direction were i can find more info on serial connections.

mark1320 said:
Hello, guys I am noob af so when I was flashing Ubuntu Touch I disconnected my phone and now its don't even show up as USB it just dead no lights no anything but battery is full I checked with multimeter. So I was wondering if its possible to use UART pins to flash kernel so it can boot. Thank You all so much and if it possible just point right direction were i can find more info on serial connections.
Click to expand...
Click to collapse
There are other ways to start your device from hard-brick state; I once hard-bricked my opo and used ColorOS (Can't remember exactly) with some chinese tool and it then showed fastboot mode from there you can pick it up.

anaskhan27 said:
There are other ways to start your device from hard-brick state; I once hard-bricked my opo and used ColorOS (Can't remember exactly) with some chinese tool and it then showed fastboot mode from there you can pick it up.
Click to expand...
Click to collapse
Yes but it requires to show up as some weird usb in device manager but my don't even show when i plug it in

Charge your phone for 5 to 6 hours, this is what I did then my phone showed up in that device manager. Also follow each step on the unbrick guide on xda

thank you for help
Rex2688 said:
Charge your phone for 5 to 6 hours, this is what I did then my phone showed up in that device manager. Also follow each step on the unbrick guide on xda
Click to expand...
Click to collapse
Its now connecting but stuck in 8974_msimage_mbn loop it just trying to flash 8974_msimage_mbn and resets. Please Help.

Suggestion:
Connect with USB to Linux PC.
Big chance that yr PC sees memory card of OPO.
Copy Rom to the card.
Install with TWRP, if available, or with other similar.
That worked for my OPO brick.
Arvie

Color OS method worked for me. Just install the correct drivers and your good to go.

T-Mobile OnePlus -- Hard (HARD) Brick

Sorry for lack of details, but I'm not sure it will help anyway. Feeling pretty bad right now.
T-Mobile Oneplus 7 Pro. 256GB version.
I wanted to go to stock OxygenOS after buying the branded version two weeks ago.
I successfully got T-Mobile to unlock my SIM, and got OnePlus to send me unlock code for my bootloader after a week.
Successfully unlocked via fastboot. Tried several times to flash TWRP and no success using fastboot.
Tried MSM-Downloader from guacamole_21_O.07_190512_repack and successfully held volume both buttons to connect to the PC. MSM-Downloader said it was successfully connected.
I cannot find the exact error message I got from MSM-Downloader, but it said it didn't match plus another error message. At that point, my heart sank.
USB Device Not Recognized keeps popping up on windows again and again, while the connect sound plays. Doesn't matter if I hold down the volume buttons or not.
Can't get into qualcomm EDL mode. My guess is I hosed my boot and now it restarts endlessly when connected to anything at all.
Is this the end of my journey? I did tons of research on the best phone and the best deals available to save money, but looks like I played myself here with lack of caution.

I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.

bmg1001 said:
I would suggest following this guide to attempt reflashing of the international firmware (use the androidfilehost download).
If that also fails, you could always just reflash the TMO firmware with this guide.
Click to expand...
Click to collapse
I cannot get into EDL. Regardless of what buttons I press (I am holding both volume buttons down in excess of 5 seconds) when connecting USB to the phone, Windows makes the "connect" sound endlessly and the driver isn't recognized.
If I can get into EDL, I will definitely try the above.

Do you have the proper drivers installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.

bmg1001 said:
Do you have the proper URL installed to use EDL mode?
Also, if you go into the Device Manager, do you see the phone in there? Should pop up as something like "Qualcomm HS-USB 9008" or some variant of that.
Click to expand...
Click to collapse
Ok. I may be making progress thanks to your help but do have some hurdles I can see.
I do see the device when I hook it up to another computer. It shows up as Unknown USB Device (Device Descriptor Request Failed).
When I go to device manager to manually update the driver, and browse to the location I extracted the CAB file into, I see lots of devices to choose from, but the Qualcomm driver cab file list does not show "Qualcomm HS-USB QDLoader 9008" as an option. I see many Qualcomm USB Composite Devices in the list but none I have chosen seem to work (install fails).

Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?

bmg1001 said:
Hmm. I know it may be an obvious question, but just to be sure, you're using the cable that came with the device correct?
Click to expand...
Click to collapse
Yes, that is correct. Same cable i used to get into fastboot, etc... The original PC I caused the problems with recognized the device differently (showed up as a Qualcomm device) when I got into EDL with it before.
Edit: First event when plugging it into this second PC under device properties:
Device USB\VID_0000&PID_0002\5&3c8d678&0&2 was not migrated due to partial or ambiguous match.
Last Device Instance Id: USB\VID_0000&PID_0000\5&1AE39384&0&2
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path:
Migration Rank: 0xF000FFFFFFFFF000
Present: false
Status: 0xC0000719

I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.

bmg1001 said:
I just did some googling and found this article. Perhaps you can try the drivers in this guide? They are .exe files so they should be easy to install, but I'm not sure if the other drivers I provided have any OnePlus specific stuff in it, but it's worth a shot.
Click to expand...
Click to collapse
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?

unluckyoneplus7pro said:
I've already tried the .zip version with no success. I am loath to install an .exe file (don't want to make the problem worse by infecting my PC) but may as well. I will restart and report back. Thank you again for your attention.
If this doesn't bear fruit, I may be SOL, correct?
Click to expand...
Click to collapse
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
I'll try there next. Can't seem to get any of my windows machines to recognize the thing.

bmg1001 said:
Mmm. The link I gave seems to have been blocked by XDA when I tried to access it from my post. Never had a problem myself with that site, but who knows.
You should be able to ultimately recover the phone though. Perhaps asking in one of the unbrick threads? OnePlus phones are theoretically unbrickable because we have good access to our EDL mode.
Click to expand...
Click to collapse
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.

unluckyoneplus7pro said:
OK! I found on reddit that if you hold your vol up + down + power for 30 seconds, it will boot back into fastboot, which it did! Holy **** I'm so happy. Haven't even seen if the PC recognizes it but will check now. If it does, I just need to not screw up the conversion to international.
Thank you for your "unbrickable" comment. That gave me hope to not give up.
Click to expand...
Click to collapse
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.

razorshiv said:
I just wanted to share a tip. After you load the msmtool and before you connect your phone with the cable, click the start button, the message will read "waiting for device". Then, as soon as you plug in the cable while holding the p-up and p-down, the msmtool will automatically start. No more rushing to hit the start button before EDL mode times out.
Click to expand...
Click to collapse
That's pretty cool. Makes the whole process much less stressful.
Got it up and running with international version. Now to see if I can get LOS installed. My sincere thanks to all and apologies for crapping up the board with my panic. I thought I had really screwed up, but it appears it was just stuck in EDL mode and needed a hard (HARD) reset.

Hey man, thanks for the donation. Glad you were able to get your phone up and running!

Holy Sh*t man. I know 5 bucks ain't much but I wanted to thank you so much. I thought I was fukd

help !. Bricked OP8 t-mobile unlocked

Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks

kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks

kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !

solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF

JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.

Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.

JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......

kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha

JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you

kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.

kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.

kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!

JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol

I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com