I'm am certainly not a pro, but I have rooted a few phones before.
I was doing nothing unusual with my phone, i went to wake the screen and since then it just never turned on again
Here's whats wrong:
-Phone won't boot AT ALL
-No Recovery or Fastboot
-Device was recognized by both windows 7 and XP as QHSUS_BULK for a day, the next unknown Device
-No response on PC, accept drivers not found
-One doesn't recognize Drivers on PC (Samsung, Color Driver, Google ADB)
Have tried:
-Over 5 minutes of Power Button pressing (also + volume up and down)
-Tried Color.zip and Samsung Drivers on Windows 7 and XP. No luck, drivers change nothing (still unknown device)
I have 0 more ideas and am getting desperate
I really need some help, non of the forums here have solved my problems...
This should sort it
Looks like you have hard bricked your One and messed up the partitions on the phone. This link will fix it for you.
http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136
Related
Ok so I have an ATT LG G2 (d800) I have CWM touch recovery and yesterday I flashed the latest cm11 update 2-21. After that my phone never got past the CM loading screen.It would load for hours. I tried wiping from recovery and I ended up deleting everything, now all I get is my LG screen. I have no zips on the phone that I can flash. I am still able to get into recovery and into download mode, since I have CWM I think that means I can't flash from an OTG. I know I can push files through adb which I already have setup, however no computer I connect my phone to can see it. It shows up in device manager as Unknown USB Device (Device Descriptor Request Failed). I have downloaded the google adb drivers, the koush drivers, the unnaked drivers, the lg drivers, NOTHING WORKS. On 64 bit computers it tells me make sure the driver is support for 64bit systems, I try the same exact driver on a win 7 32 bit and it tells me to make sure it is for 32 bit computers. I have opened up the phone and left the battery unplugged for 2 hours, that didn't help. I've actually read that people clean the inside of their usb port on the phone and that fixes that, I'm desperate and tried it, did nothing. I have tried on my windows 8.1 x64 (yes i tried disabling signature veri), windows 7 32 bit, and a virtual windows xp 32 bit.
Windows 8.1 doesn't support many devices in fastboot or recovery mode. I had to switch my computer to windows 8 just to use fastboot on an xperia play.
Using a virtual windows xp wouldn't work either. Cuz the device has to be recognized by your main OS first. And after your main OS recognizes the device it will connect it to the virtual machine.
So stick to your Windows 7 for now. Make sure again that you're correctly installing the 32 bit drivers and then try pushing zip files into your phone through adb
As long as your phone can boot into recovery or download mode then it's fixable so don't worry about that.
Sent from my One X+ using XDA Premium 4 mobile app
Hi Guys,
I've had a few problems with my N5 recently...
If I plug my N5 into my PC via the stock USB cable and boot into the Bootloader (PWR+VOLDN) then it will allow me to flash the original N5 firmware, located here: https://developers.google.com/android/nexus/images, this would indicate to me that there is no issue with the actual devices ability to transfer files via USB connection... Right?
No!
For some strange reason my phone will allow me to push a full factory image to it and will also process any Fastboot commands that are sent to it but as soon as you boot into something like TWRP and try to control the phone's ADB functionality it will not find the device at all! The new MTP option in TWRP 2.8 will allow my computer to see my phone's MTP connection for about 1 second and then will immediately disconnect, the same happens when trying to connect to MTP from within Android too.
USB debugging doesn't show that it is connected when my phone is plugged into my PC and Windows makes the 'device connected' sound and then straight after makes the 'device disconnected' sound...
Any ideas? I am certain that this is an issue with my handset's hardware or software rather than any of the computers or cables... I have tried 3 different cables (including the stock cable) and also three different computers (Windows 8.1 @ Work, Mac OS X @ Work and my own personal PC running Windows 8.1 & Ubuntu @ Home)... All OSs and all computers run into exactly the same issue, device connects briefly and then disconnects.
I have troubleshooted issues relating to the driver. This is not the issue... Device Manager cannot even see the hardware after the disconnect.
Thanks for any help in advance,
Lewis
Also:
-Android does not detect that the USB is charging the device unless the device is booted with the cable attached (if it's not attached before the 'Google' screen then it can't see the USB input at all, within android or TWRP, of course...).
Having the exact same problem. Did you find a solution?
EvilBetty said:
Having the exact same problem. Did you find a solution?
Click to expand...
Click to collapse
It's most likely a driver issue.
Elluel said:
It's most likely a driver issue.
Click to expand...
Click to collapse
Not a driver issue.
3 different Nexus 5s, 5 different workstations. Other two Nexi are fine on all 5 PC's.
1 PC used for ADB forensics, 2 used for ADB development work, one known working for ROM'ing / rooting.
Phone has been factory reset, factory ROM'd from Fastboot. Connects fine on Fastboot. Will not connect on ADB / MTP.
On a fresh PC / phone reboot, the PC will detect the phone for just a second and then it will not reconnect until process is completed.
-EB
What's your adb version?
Went on for about 2 weeks, then suddenly went away on its own. I have no idea what the problem was or the solution. Sorry.
i have a nexus 5 which has stock ROM and blu spark kernel . i locked the bootloader while on the same kernel and again unlocked it . . the phone is bootlooping into twrp and the google logo . in twrp it says unable to mount data . i can access twrp . . i am unable to flash anything . it says unable to mount data/ . please the attachment
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
Hi mate, am in exact same situation as yours.
Did you have any luck fixing it?
Maximuseml said:
Hello! Im new here
The thing is that I bought a bricked OPO today hoping that I could fix it. I've been like 4-5hrs straight trying and nothing!
The real problem is that my OPO is not being recognized by my computer. (Im running Windows 8.1)
When I connect it to the PC the device vibrates but no sound, I go to device manager and it's not there (not as QHSUSB_BULK, not as UNKNOWN DEVICE, not as nothing, it just dont exist)
I installed the Samsung drivers, OnePlusRestoreTool, Bacon Root ToolKit, OnePlus One Toolkit and nothing seem to work...
I tried to get it into FastBoot mode but it ony vibrates every 10 consecutive seconds I hold the vol up + pwr button and NOTHING happen, screen remain black and no sound by my PC recognizing the device...
I tried alternate USB, alternate cable and nothing...
If you guys can help me that would be awesome!
Thanks, and sorry for my bad english.
Click to expand...
Click to collapse
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
sid_844 said:
1st of all uninstall QHSUSB_BULK this driver,after this download qualcomm 9008 driver google it and install this driver then you can connect your #bacon it going to detected and dont forgot this process has to be done test mode and refer thia thread also http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Click to expand...
Click to collapse
First of all thanks for your reply.
I have seen this thread but as you can see to uninstall the old driver I need to:
' Go to Device Manager, right click on the bricked USB device (QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008) and go to Properties, click on Driver, then select Uninstall. Check the box to remove driver files, if prompted...'
But the device is not seen by the device manager.
Someone suggested in an other thread that I need just to press (not hold) power + volume button.
I will try that and let you know.
By the way what is 'test mode'?
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
cy80rg said:
Afternoon all,
Have been out of the rom'ing scene for a while...
I have a number of devices (Galaxy Tab 2 10.1 and Nexus 7 2012, to be exact), that I want to flash a new ROM onto (the Tab's stuck in a boot loop, the N7's due for Dirty Unicorns Nougat Rom).
All pretty straight forward - I've done it in the past - BUT...
Can I get Windows 10 to even *see* new hardware's been connected, let alone recognize it?
Can I fook
To confirm, I plug the USB between the PC and the device, and all that shows this is connected is that the device realises it's being charged, no "ding ding" from Windows, no USB confirmation from the device...
Both devices have USB Debugging enabled.
Have tried different USB cables
Have tried different USB ports
Have tried - many! - different USB drivers, including that from both Asus and Google's own dev kit.
Have ADB installed, "adb devices" shows no devices (blank).
The thing that's really pi**ing me off is that this is such a basic thing to be stuck by, I really cant figure out what I'm missing!
Any help appreciated gents...
Click to expand...
Click to collapse
Windows 10 is very buggy. Download lobit Drive Booster to see if you are missing any driver for your pc. Your pc is probably missing some drivers for the motherborad or outdated. If this does not work, clean install windows 10. Let windows 10 install all the drivers for you while it is installing. Best method. Good internet connection required.
its damn easy,the problem lies in Windows,just boot into repairmodus/system recovery its the blue menu for troubleshooting,there u choose Startup Setting and there u choose number 7,thats for disabling the digital driver signature checking,after the reboot all is fine,boot note u must do it everytime new after reboot.
please next ask and post in right section,thanx.
Nvidia USB driver (ADB and Fastboot) is the only one that works for me
https://developer.nvidia.com/shield-open-source
Hello. If you're on Windows 10 like me, you're probably having an issue unlocking your bootloader because the device is undetected in fastboot mode.
I downloaded LG drivers, Google drivers, etc and nothing worked. I finally resolved the issue by
1. Uninstalling all Lg driver software I downloaded
2. Installing the LG PC SUITE software (*This should do it*)
3. Ran PC suite & hit "connect" - it told me my LG USB DRIVER was missing and offered to install it for me from within itself. I hit the button to install said driver.
I ran the installation twice and suddenly my laptop made a sound indicating my device was recognized. (I also watched my Device Manager refresh with the correct devices). Also, LG PC SUITE has adb built into it so the driver was certainly there.
After this, I ran fastboot devices and mine was good to go!
I hope this helps!