I have a problem with my nexus 5, I try to install the recovery and it stays black screen does not enter the bootloader or anything, my pc recognizes it as android adb interface some help.
me to having same problem dont know what to do
pc not recognising my device
Follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
I hope you have an efs backup somewhere if you don't keep trying..
also how did you try to install recovery? there is a multitude of ways and knowing what you did could help a lot.
Jo_Jo_2000 said:
Follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
I hope you have an efs backup somewhere if you don't keep trying..
also how did you try to install recovery? there is a multitude of ways and knowing what you did could help a lot.
Click to expand...
Click to collapse
Hello thanks for your help I will try, I did the procedure with the tool nexus root toolkit I followed the steps my phone stayed so now it vibrates and reboots constantly my pc only recognizes it as mtp usb or android device.
soujirock said:
Hello thanks for your help I will try, I did the procedure with the tool nexus root toolkit I followed the steps my phone stayed so now it vibrates and reboots constantly my pc only recognizes it as mtp usb or android device.
Click to expand...
Click to collapse
Follow the thread and stop using toolkits since they might do obscure things and people cannot help you if you just say "i did it with the toolkit"
Jo_Jo_2000 said:
Follow the thread and stop using toolkits since they might do obscure things and people cannot help you if you just say "i did it with the toolkit"
Click to expand...
Click to collapse
Hello try to perform the steps but in the device manager I do not get any of that I only recognize the phone as android device.
soujirock said:
Hello try to perform the steps but in the device manager I do not get any of that I only recognize the phone as android device.
Click to expand...
Click to collapse
Thanks for your help, download one that said repair nexus 5 dead and now I get this I think I should do something more because now the pc recognizes me so if you could guide me I would thank you very much.
what happens when you try to open the mtp device?
if not try uninstalling all drivers with google..
you should always be able to reach the dload mode even if it's fully working as long as you follow the steps.
Jo_Jo_2000 said:
what happens when you try to open the mtp device?
if not try uninstalling all drivers with google..
you should always be able to reach the dload mode even if it's fully working as long as you follow the steps.
Click to expand...
Click to collapse
Hello what happens if it opens like a usb but on the screen of my cell you can not see anything even I recognize it in fastboot mode but on the screen I see nothing.
How can i get into dload mode
I try to flash it with the method you gave me but I get a message from device was not found in dload mode trying flash programmer.
maybe your screen is just broken?
also citing the thread linked: "If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide."
Jo_Jo_2000 said:
maybe your screen is just broken?
also citing the thread linked: "If you dont see Qualcomm HS-USB QDLoader 9008 click on the CLICK TO SHOW CONTENT button bellow, otherwise don't and follow the guide."
Click to expand...
Click to collapse
Hello my screen is not broken or anything I already recognized the pc driver qualcom 9008 and perform the procedure of the post now my cell recognizes the pc as nexus 5 in usb mode but I do not have the system.
soujirock said:
but I do not have the system.
Click to expand...
Click to collapse
Aka no reaction or no fastboot or a missing partition?
is recovery working?
is bootloader working?
what has appeared on your screen to show you that it isnt broken?
Jo_Jo_2000 said:
Aka no reaction or no fastboot or a missing partition?
is recovery working?
is bootloader working?
what has appeared on your screen to show you that it isnt broken?
Click to expand...
Click to collapse
Hello, it seems that the fastboot mode works because in the pc it recognizes me as android device and I download a program that is called dead nexus 5.bat and this recognizes me and writes the system and performs other operations more but still nothing appears I do not know if the system can be flashed by this method.
i try with this method https://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 but nothing
can you execute fastboot commands?
what does that script tell you, where is it from?
Please stop using toolkits, they perform obscure unpredictable things.
Also what makes you so certain your screen isn't broken given that everything works except the screen?
Jo_Jo_2000 said:
can you execute fastboot commands?
what does that script tell you, where is it from?
Please stop using toolkits, they perform obscure unpredictable things.
Also what makes you so certain your screen isn't broken given that everything works except the screen?
Click to expand...
Click to collapse
thanks man i solved my problem
Related
I have Samsung Galaxt Tab 2 7". Yesterday to install custom firmware, I flashed some wrong recovery on it.
Now, when I turn it on it is stuck on Samsung Initial boot logo and stays there as long as possible.
If I turn it off and bring it to download mode (Press and Hold Power and Down Volume Key), it comes into download more but when connected to PC, it says USB Device Not Recognized.
I tried charging my Tab whole night, it became warm and till morning it was warm only. Now I am completely stuck and don't know what to do.
Is there any solution for this? Is there any button combination which can take the tab at-least to stock android?
Since USB is not been recognized, so I am helpless to do anything here.
Sent from my RM-917_nam_usa_100 using XDA Windows Phone 7 App
anshumangoyal said:
I have Samsung Galaxt Tab 2 7". Yesterday to install custom firmware, I flashed some wrong recovery on it.
Now, when I turn it on it is stuck on Samsung Initial boot logo and stays there as long as possible.
If I turn it off and bring it to download mode (Press and Hold Power and Down Volume Key), it comes into download more but when connected to PC, it says USB Device Not Recognized.
I tried charging my Tab whole night, it became warm and till morning it was warm only. Now I am completely stuck and don't know what to do.
Is there any solution for this? Is there any button combination which can take the tab at-least to stock android?
Since USB is not been recognized, so I am helpless to do anything here.
Click to expand...
Click to collapse
Hm, Odin needs Samsung USB Drivers to be able to recognize device, did you already install them?
If not, you can download it here.
(If you're using Windows 8, tell me, because you will need some special method to install the drivers.)
fr4n said:
Hm, Odin needs Samsung USB Drivers to be able to recognize device, did you already install them?
If not, you can download it here.
(If you're using Windows 8, tell me, because you will need some special method to install the drivers.)
Click to expand...
Click to collapse
Thanks, I have tried and it is the same. Yes, I am using Windows 8. Please let me know what special things needs to be done with this.
Thanks again. Your English is better than me, though it is also not my first language :laugh:
anshumangoyal said:
Thanks, I have tried and it is the same. Yes, I am using Windows 8. Please let me know what special things needs to be done with this.
Thanks again. Your English is better than me, though it is also not my first language :laugh:
Click to expand...
Click to collapse
I bet you tried to run the .exe file and the installation didn't even start, no? xD
Follow installation method 3 explained in this thread.
If you can't do it, let me know and I can help you!
I'm not pretty good with English too... I know only basic skills, but I bet I can't go to English-speaking countries with them :laugh:
fr4n said:
I bet you tried to run the .exe file and the installation didn't even start, no? xD
Follow installation method 3 explained in this thread.
If you can't do it, let me know and I can help you!
I'm not pretty good with English too... I know only basic skills, but I bet I can't go to English-speaking countries with them :laugh:
Click to expand...
Click to collapse
I followed all steps. But still I am getting my USB Device is not been recognized. It is showing "Unknown USB Device (Device Descriptor Request Failed)"
Till now I am unable to find any solution.
anshumangoyal said:
I followed all steps. But still I am getting my USB Device is not been recognized. It is showing "Unknown USB Device (Device Descriptor Request Failed)"
Till now I am unable to find any solution.
Click to expand...
Click to collapse
Hm, that was totally unexpected.
I hope I'm wrong, but it sounds like your board got damaged. But if the board was damaged, it won't ever turn on. So my mind is a bit twisted here.
I will try to look for solutions. For now, you're stuck with a paperweight :s
anshumangoyal said:
I followed all steps. But still I am getting my USB Device is not been recognized. It is showing "Unknown USB Device (Device Descriptor Request Failed)"
Till now I am unable to find any solution.
Click to expand...
Click to collapse
Do you have a Linux computer? Of you do, PM me and I will send you instructions that you can try to follow.
Sent from my SGH-T989
jrc2 said:
Do you have a Linux computer? Of you do, PM me and I will send you instructions that you can try to follow.
Sent from my SGH-T989
Click to expand...
Click to collapse
I don't have a linux computer. But I can install a virtual machine for that. Can you please send me instructions how to do that. Thanks again.
anshumangoyal said:
I don't have a linux computer. But I can install a virtual machine for that. Can you please send me instructions how to do that. Thanks again.
Click to expand...
Click to collapse
Sorry, I must have missed this post. I don't know if a VM will work or not. I think the problem is windows 8 as there have been lots of problems reported with Odin and Heimdall (probably the drivers) on windows 8.
Sent from my SGH-T989 using Tapatalk
EDIT: I have a thread in the general section for the tab 2 on rooting in Linux. Do everything up until flashing SuperSU. That thread has the instructions on how to install recovery. Still do it with no reboot checked and manually boot into recovery and wipe cache and Dalvik cache. Hope this helps!
EDIT 2: Here is the link to the thread: http://forum.xda-developers.com/showthread.php?t=2828080
today i accidently wiped my nexus 5 OS.Butnow i cant restore stockrom as adb and fastboot not showing.My pc not installing drivers and otg is not mounted in twrp .anyone help
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Jo_Jo_2000 said:
Have you really wiped your bootloader / partition table? Please double check that.
Try plugging it into your pc. if you get the qhsusb 9008 dload mode, follow this thread: https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if you don't, make sure you shut down your phone completely as described in the thread above
I hope this will help you.
Click to expand...
Click to collapse
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
jude_ferolous said:
but my problem is my pc aint detecting my device its shwing like unknown usb (device desciptor failed).I have tried NRT but fails in adb connectivity.help spmeone
Click to expand...
Click to collapse
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Jo_Jo_2000 said:
have you tried holding the pwr button 20 seconds? if you didn't, try following the thread *litteraly*
Click to expand...
Click to collapse
I have tried but still tht google logo
jude_ferolous said:
I have tried but still tht google logo
Click to expand...
Click to collapse
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
Kk will try and thanks
Jo_Jo_2000 said:
Having that logo = having fastboot mode.
Try uninstalling all drivers or use a virtual machine or another pc (even a raspberry pi works)
Click to expand...
Click to collapse
jude_ferolous said:
Kk will try and thanks
Click to expand...
Click to collapse
I have also tried in windows 7 &windows 10 but no luck still showing unknown device (device descriptor failed).Whether my device hardbricked and can i go back to factory version without any luck in adb connectivity and no otg help someone...
It's a stock phone, unrooted bootloader locked. The phone was updated to the latest firmware a few days ago and was working well since.
Today I left the phone on the desk for a while. When I came back, the phone had rebooted and was in the fastboot mode screen.
I tried to restart but it just loops back to same screen. Does not even go into recovery!!
What snapped it, cant understand!
Is it bricked? How do I revive the phone now?
Please help!
Thanks
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
sms2000 said:
Could be some CRC glitch in the main memory which prevents your phone from boot.
Being in FB mode try to flash some stock ROM (download the latest stock or Beta 9). Don't try to go to Recovery, flash from FB with fastboot utility.
https://downloads.oneplus.com/devices/oneplus-6/
Click to expand...
Click to collapse
Do I also need to flash stock recovery from fastboot?
Thanks again.
observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
No, recovery is part of the ROM, so not needed.
If it's a completely stock device, why not contact OnePlus and get a replacement?
Are you guys suggesting ADB sideload command? My USB debugging seems to be off, returns empty on "adb devices"
I am unaware of fastboot command to flash the stock rom, googled it but could not figure out the right command.
Thanks
maigre said:
If it's a completely stock device, why not contact OnePlus and get a replacement?
Click to expand...
Click to collapse
That's right.
If am not able to fix it myself with members help, I'll have to go through customer support drill.
observingi said:
Do I also need to flash stock recovery from fastboot?
Thanks again.
Click to expand...
Click to collapse
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
jerrywmilton said:
(a) there is no such thing as "bricked" when it comes to any OP Qualcomm devices
(b) as with ANY OP Qualcomm, OnePlus can reflash remotely directly to the Qualcomm or you can do the same thing yourself. Just follow the simple instructions.
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
Fingers crossed mate! Hope you get it right!
observingi said:
Thanks for the assistance.
I tried the unbrick tool, but device manager (Windows 7 64bit) shows the device as Oneplus Android Bootloader Interface (under Samsung Android Phone )
Therefore, MSMDownloadTool does not show any device in the list.
Driver https://androidfilehost.com/?fid=889964283620777981
Edit: Phone recognized now
Click to expand...
Click to collapse
yeah, I was gonna say....just follow directions carefully....it works....same set up has been working for years for each different model.
Thanks to each one of you.
The issue is resolved
I used the unbrick tool i.e. MSMDownloadTool to fix the problem. Hope it does hot happen again!
Thanks
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.
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