Related
Dear All,
After I did repartition sd-card with rom manager i can't boot my phone. I mean i can't even get to download or recovery mode. I think it also repartition internal sd too. Right now when I plug in to charge or usb even the red light does not turn on but windows 7 does recognize it as QHSUSB_DLOAD, if can find a driver I think I can flash it with odin but after several hours of searching I could not find any driver suitable for it. Can anybody help me with this?
Yep, odin is probably the right program to use
Here's another thread with the same story.
I know but as I don't have that weird driver Odin does not recognize phone. So I need the drivers called qhsusb_dload...
Actually I would only use Odin with Samsung...
I hope somebody can find solution to this problem, that we flash entire phone without recovery mode... if somebody has the driver please post it...
Ya, I have the same issue.
I wasn`t able to find the driver for my device too. Sad Panda!
...seems like there`s no solution right now. I ll give it to HTC this evening if noone could give THE advice to repair it on my own.
Does anyone know why the desire is crashing when trying to use ROM Manager to partition the sd-card?
Well, I think I will give it to HTC a few hours later today seems to me there is nothing we can do about it.
All the drivers that are needed are installed with HTC Sync. Odin won't find your DHD because it's meant for Samsung phones (and even they have to be turned on in download mode). As your phones won't boot to either recovery or bootloader there's not much you can do.
You are right, I already sent it to HTC. I hope they don't recognize that it's rooted. But as it has already repartitioned the sd-inside, I don't think they will try to recover any data and try to understand it.
xsdenied said:
You are right, I already sent it to HTC. I hope they don't recognize that it's rooted. But as it has already repartitioned the sd-inside, I don't think they will try to recover any data and try to understand it.
Click to expand...
Click to collapse
so what happened? did they replace it for you?????
was there ever a solution to this? did anyone have luck with htc?
Yes they give me new one 3 days later, so everything went ok.
duarab said:
was there ever a solution to this? did anyone have luck with htc?
Click to expand...
Click to collapse
yes there is a solution: go to your carrier and tell them my phone is NOT WORKING. they will keep you waiting for 2 weeks, then will give you a new phone. i did this and got my phone a new
I don't know if this helps anyone...... I found the drivers for "QHSUSB_DLOAD" but I haven't been able to do much else. If anyone else finds a way to recover the device please post.
Koush confirmed that this was an issue with older versions of ROM Manager and has since been fixed. However, this happened toe yesterday using the latest recovery and the latest ROM Manager. He hasn't responded to me as of this post. A new phone is on its way from tmobile.
vcglmcg143 said:
I don't know if this helps anyone...... I found the drivers for "QHSUSB_DLOAD" but I haven't been able to do much else. If anyone else finds a way to recover the device please post.
Click to expand...
Click to collapse
is this work for Motorola Arix...
thanks for advance ....
aaurnab said:
is this work for Motorola Arix...
thanks for advance ....
Click to expand...
Click to collapse
The device is bricked. The drivers don't help. The only fix it to send it back and get a new one.
Update: I can now repair the Desire HD with advanced JTAG recovery. If you need help with a bricked Desire HD, please PM me...
Riff Box Jtaging recovery im guessing.
Now i Dont have riff box, but I have x64 drivers installed and working for the qualcomm port, and QPST sees the phone properly. The only thing im missing are the files to flash.
Edit:
If anyone is needing them; Attached are the x64 drivers for "qhsusb dload"
You can't flash the phone when it's in CPU mode. The only devices that can really do that are the NVFlash units that are the Tegra 2 chipsets. From what I know, JTAG is required. And yes I use the RIFF box and advanced micro-soldering to recovery these particular models. The Desire HD is a very difficult phone to take apart and requires skill in small electronics to not damage components. Despite the build quality, HTC makes phones that are very difficult to dis-assemble.
When I plug in my T999 Galaxy S3 into my laptop, it doesn't reconize the phone at all, it charges that's all I have the drivers installed and have debugging on and rebooted my computer and phone still no difference can somebody please help thanks!!
Go her to find your answer
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
TRY THIS
nynexelf said:
when i plug in my t999 galaxy s3 into my laptop, it doesn't reconize the phone at all, it charges that's all i have the drivers installed and have debugging on and rebooted my computer and phone still no difference can somebody please help thanks!!
Click to expand...
Click to collapse
go to samsung.com an in the search spot type kies download install it could be bad or not installed prop. Drivers if still dont work put the phone into download mode see if the computer reconize it that way.
I've downloaded my drivers and Kias from the samsung website, and still doesn't make any differance at all, it's really strange, i'm starting to get worried, I have tried using anther usb cable and even a different computer and still no good so I don't know what to do
sdsdqbam said:
go to samsung.com an in the search spot type kies download install it could be bad or not installed prop. Drivers if still dont work put the phone into download mode see if the computer reconize it that way.
Click to expand...
Click to collapse
Mine is the same I actually have to the mass storage utility app on my phone for it to read it on my desktop. Now if I use it on my iMac with windows it reads or just fine
Sent from my iPad using Tapatalk HD
nynexelf said:
I've downloaded my drivers and Kias from the samsung website, and still doesn't make any differance at all, it's really strange, i'm starting to get worried, I have tried using anther usb cable and even a different computer and still no good so I don't know what to do
Click to expand...
Click to collapse
____________________________________________________________________________________
First , did you follow EXACTLY the steps in this link?
http://forum.xda-developers.com/showthread.php?p=32906335#post32906335
You need do do EACH STEP IN SEQUENCE and ALL of them
If you jump and skip around, it most likely will not work.
If you follow the directions, It WILL work.
If there are any error messages on the procedure, post them, and I will get you going in the right direction.
Really, it isn't hard to get this to work! Just be sure you do each step in sequence, and follow the list!
Post whatever comes of your effort.
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Use wugs program but tick tablet is in bootloop.
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!
Hello, my phone has been completely dead after switching to slot B via TWRP.
But major problem is that it is not recognized by PC, no nothing like port 9008 into device manager.
Already tried different combos, but no luck.
Tried with deep flash usb method, still no luck.
Please help if anybody has any idea or method how to bypass this situation.
Also, if anybody knows about the test points in our z2 force please please provide us, Thanks!
If we successfully deal with this situation, many many major problems will be solved or dealt with ease on xda regarding our device.
smartybro7788 said:
Hello, my phone has been completely dead after switching to slot B via TWRP.
But major problem is that it is not recognized by PC, no nothing like port 9008 into device manager.
Already tried different combos, but no luck.
Tried with deep flash usb method, still no luck.
Please help if anybody has any idea or method how to bypass this situation.
Also, if anybody knows about the test points in our z2 force please please provide us, Thanks!
If we successfully deal with this situation, many many major problems will be solved or dealt with ease on xda regarding our device.
Click to expand...
Click to collapse
same issue here m8, no fastboot , no q-usb, nothingg....
im on the verge of recyling my device for like 250rs(less than 4$)
I know it's a given but...u installed Qualcomm drivers for edl mode right?
Dany XP said:
I know it's a given but...u installed Qualcomm drivers for edl mode right?
Click to expand...
Click to collapse
i did
no response
my issue was i disconnected and rebooted the device while reflashing the firmware(mid way)
and its been dead ever since
<deleted>
Accidentally flashed the wrong blankflash (so I can't flash Android) and I didn't find any way to put the phone back to EDL mode... Only Lenovo/Motorola knows...
Yep, I'm having the same issue. I was on Stock Oreo, and tried to OTA to Pie (my phone is RETBR), OTA was detected and download, but the install fails every time, seems to be an error with partition B (logs are above), so I intended to flashall the slot B to "correct" the partition, but as soon as I marked B as active and rebooted to bootloader again, the phone didn't startup anymore, and nothing is reconized on PC.
Anyone got any progress on this?