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...
Related
So, messing around with kernels and stuff, I wound up with a bricked device (wouldn't turn on, no response to anything, etc [I did eventually manage to get it functional again through a combination of button mashing and praying])
However, when plugging it into my computer, it showed up as "Qualcomm HS-USB QDLoader" which seemed interesting.
Searching the internet, I found several things. The QPST (Qualcomm Product Support Tool) Software suite, as well as other less useful links about the LGFlash tool, etc.
The programs also makes reference to debug and other modes, but there isn't a lot of documentation on the internet.
What I want to know is, is there a way to put the device back into the QDLoader or other QPST related modes so as to either update the firmware again, or just make backups for future use?
If there is, this seems like it would be a great tool for undoing any damage to the phone that isn't hardware related (the documentation says this part resides on a read only chip[which it seems fastboot doesn't])
It looked like you borked your phone to the point where there was nothing recognizable as Android left on it. I don't know anything about this loader but based on my past experiences dealing with proprietary OEM tools (Samsung KIES), I hope I never find myself in a situation where I'd need to learn. :crying:
Turn off your phone. Press all the keys if nothing happens your phone bricked. If you end up qualcomm 9008 mode we cant do much, because we dont have a working flash programmer and a working bootloader which would be flashed to the phone with the flash programmer. You can do 2 things. Replace your motherboard, or find the emmc pins on the motherboard to get direct acces to the storage then with a modified sdcard reader you could have access to the storage content then you could restore the bootloader. This is pretty hard method almost impossible.
If you have qualcomm 9006 mode then you can restore the bootloader with any kind of linux, because in 9006 mode the phone acts like a external hdd.
May I ask how exactly you messed around with the kernels to get this? Did you flash an incompatible kernel or something?
It sounded like he resolved his issue and wanted to know if this hidden mode can be used.
Wakamatsu said:
It sounded like he resolved his issue and wanted to know if this hidden mode can be used.
Click to expand...
Click to collapse
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off
It works!
bitdomo said:
to enter qload mode you have to turn on the phone then press everykey at the same time until the screen turns off
Click to expand...
Click to collapse
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...
caffeinatedangel said:
Thank you! This works!
It still only puts it in download mode, not the diagnostics or anything else. Although.. That may just be a project for when there's better documentation, or I don't actually need this phone for normal use...
Click to expand...
Click to collapse
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.
Well darn
bitdomo said:
To achive diagnostic mode you need a working flash progfammer and bootloader which can be loaded with flash programmer. We will never have these files unless someone at qualcomm build it for nexus 5 then share it here on xda.
With LG G2 if something goes wrong during ota update the phone starts in qualcomm 9006 diagnostic mode.
Click to expand...
Click to collapse
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!
I've never bricked my phones that bad man when I was a noob I installed safestrap on a device with an unlocked boot loader and tried to flash a ROM it didn't work out to well,man that was about two years ago
caffeinatedangel said:
Ah, darn. I suppose we can just hope though. Maybe someone with too much time will find a way to do it on their own. Oh well. Thank you!
Click to expand...
Click to collapse
There were two placed where qualcomm documentatiosn could be found. One was a chinese forum where you have to be veteran or admin to get access to the files. This forum not exist anymore. The other is a chinese ebay like website where they are selling qualcomm documents for 3000 usd.
If you search for msm8974 boot flow or sahara protocol you will find file names for qualcomm pdf documents. Sadly just file names no download possibilty.
Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!
HTC m8
danielr324 said:
Hi there,
I accidentally flashed (inside twrp) my HTC m8 with a bootstack/modem of a different phone (39a,LG G2). I'm pretty embarrassed about it, didn't mean to do it...I thought I was following instructions to install a new rom for the m8,except I was in the wrong forum..
details: in TWRP I flashed the wrong file, then went on to install a new rom and an error appeared: this is not vs980, this device is m8wl...so I thought, what? strange....
I turned off the phone (without realizing yet what happened. Sorry, stressful couple of weeks) and when I tried to turn it back on, it wouldn't. No matter how long I held the power button, or power and vol down. It will not go in download mode, neither detect it is plugged in to charger or a computer. Basically totally off without any response.
My question: is there any way possible to resuscitate this phone? please help me! any advice is appreciated.
before I had the m8 with s-off,rooted,with a 5.1 rom installed.
Thank you in advance!!!
Click to expand...
Click to collapse
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0
ok_then_so said:
You need all in one kit 2.0
M8 firmwareTWRP or probably RUU file
my choice will be firmware TWRP
you can flash it with help of All in one tool kit 2.0
Click to expand...
Click to collapse
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk
beaups said:
No, a toolkit won't help. He needs a new phone.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,
danielr324 said:
thanks for the help so far guys!
Here's another funny thing. After a few attempts of plugging it in to a computer, it was recognized and it showed up in the device manager. The phones still did not turn on though. Additionally it seems that the phone is seen as an LG model (even though it's not), but I am not sure yet. I will get the HTC drivers installed,and if it doesn't work, I will try the LG drivers.
by the way, isn't there a way to flash the correct modem/bootstack with ones of those kits? i also remember from downloading the wrong LG G2 modem/bootstack that it didn't come with fastboot in it.
I will try a few things and report it back.
thanks again,
Click to expand...
Click to collapse
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
I got it to be recognized on a computer again, and windows installs a driver. The name of the device is forge hs-usb qdloader 9008.
I tried the all in one 2.0 kit, adb sideload, etc but anything I try I get a "device not found".
I think I am giving up unless someone finds a way to unbrick this kind of severe problem in the future. I also researched a bit on google, and there's a way to unbrick the LG G2 when it's seen as forge hs-usb qdloader 9008, which is known as a board unbrick. I found nothing for the HTC m8 though.
We tried all we could Thanks all for the help, it's very much appreciated! You guys are the best and this forum is awesome. I also ordered a new phone...and I will root it too
dottat said:
If your device doesn't light the power button but for a single flash when you try to power it on your board is toast.
If it shows up in device manager as a qusb bulk device the board is toast.
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.
BadUsername said:
Might be completely wrong on this.
Wouldn't he be able to JTAG the appropriate boot image back onto the device?
Also, I know we had a hard brick recovery for the S3 back in the day. Worked consistently on full hard brick's.
http://forum.xda-developers.com/showthread.php?t=2581166
Isn't it possible to dump a debrick image from a working device and follow the guide with that? I know the two devices are completely different, but the premise is the same.
My technical know-how isn't anywhere near your level, just thought I'd throw these ideas out there is case it hasn't been thought of yet. I'd be happy to put together a guide on how to do this if it can work on the M8.
Click to expand...
Click to collapse
Not likely with the nand used on this device.
Sent from my HTC6535LVW using Tapatalk
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Did you try msm download tool? If not, nead that thread and good luck
whizeguy said:
Did you try msm download tool? If not, nead that thread and good luck
Click to expand...
Click to collapse
Hi!
Thanks for your reply, but I think you do not read my entire post
As I said, i've already tried at least 8 different versions of msmDownloadTool.
If you have any other suggestion, I'll appreciate.
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
EarthquakeXS said:
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
Click to expand...
Click to collapse
Yes, I am unable to enter into Fastboot Mode.
When I try, the logo saying "fastboot" appears, but after 4 seconds, the systems stucks on CrashDump error screen again.
That way my PC cannot find my phone with ADB or FASTBOOT commands.
The only tool that works is msmDownloadTool, but even with a success run with that tool, my system does not start and stills under CrashDump error.
I was thinking if exists some version of msmDownloadTool that justs restore the fastboot and unlock bootloader with brute force.
Thats my last hope
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
sanaulla jauhar said:
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
Click to expand...
Click to collapse
Hi!
Can you please provide some link to this tool?
Thanks for your help!
mikesmarcos said:
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Click to expand...
Click to collapse
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Hi dude are u here ? i will help u
Try this
Rhach1d237 said:
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Click to expand...
Click to collapse
Source is a videotutorial. google oneplus 6 hardbrick and click the video of Max Lee
(it worked for me)
the download takes an awful lot of time
first get your phone into qualcomm download mode by holding down volume up + power button and plug your device in your PC.
(first unzip the hardbrick zip folder) then the oneplus 6 folder and than the .exe file and click 'start' if it detects your phone.
That is flashing every chip and Hydrogen OS 5.whatever.3 but that is not important. Your phone should boot and than you can install Oxygen OS with android 10(thats the other zip folder) using the local upgrade feature.
(make sure to enable google play services after upgrade from hydrogen OS)
Hope it will work for you too if you haven't tried it already.
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
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