Was installing with the QDL tool and got a D2 error at the end of the log. Im on a 32bit Win7 Ultimate OS netbook. I tried to follow the directions and when it got to the part to pick the Driver manufacturer/driver with the split screen window, mine was just a single frame with a bunch of Qualcom drivers but the 9002 was in the list. I choose 9002 and hit next and the first warning message came up clicked yes but then another warning message in red came up. The window came up and said that the new driver had been installed. During the entire process I could hear my speakers making the sound when you connect/disconnect USB devices. Anyway hit the run button and got the failed install D2 error.
My streak is still running fine on 1.6ATT, but this is my second streak since I bricked my first one trying to do 1.6ATT>2.1O2>2.2DJSteve, so Im a little scared now since this QDL Tool didnt work and this is supposed to e really easy.
Anybody???? Does it matter that my netbook was has both XP/Win7? I was going to try to use QDL Tool on XP side but then I thought that if I used a XP driver would the Streak not be found on my primary machine that runs Win7???
I tried installing the driver again on win7 and the connect/disconnect sound kept happening.
Related
possibly silly question, seeing everyone is saying the rooting problem is something different(drivers(htc/pdanet/android sdk), sdcard, computer(OS)). you guys that have gotten ADB to successfully get the phone recognized in recovery mode:
Did the phone show up in the device manager for windows?
i feel like windows has to register the phone under a certain driver in order for ADB to pick it up(otherwise the OS doesn't recognize it like any other piece of hardware). maybe part of the problem is some people don't have a recovery driver?
just throwing it out there since I have tried every method on the forum except using the original sdcard that came with the phone(it's my my gf's phone at the moment and i haven't been able to get it from her)
also, does anyone know what eugene's setup is? OS, drivers, sdk version? or eugene if you see this, it would be wonderful if you could chime in.
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
What OS are you using? 32 or 64 bit? Do you have HTC Sync installed?
i've used winxp pro 32bit, win7 pro 64bit, win7 ultimate 64bit. i tried the htc drivers, the pdanet drivers and the sdk drivers. i just made a ubuntu boot drive, i think im going to try that later tonight.
and i think chrisinaz is trying to root his friends phone on the same computer he did his on if i'm not mistaken.
Using xp 32 bit and fedora 13. Neither work for his, both work for mine.
-------------------------------------
Sent via the XDA Tapatalk App
chrisinaz said:
Im in the process of trying to root my buddy's phone after successfully rooting mine, and this was the same thing I was thinking. Using USBDeview, there is a device in recovery mode called "Android 1.0".
When my phone is connected, it says "Connected: Yes" on that device, however when his is plugged in it won't recognize it.
I kept thinking it had to do with drivers too... but I'm not sure where to go with it now...
Click to expand...
Click to collapse
Where it says android 1.0 this is the driver that you need to update. I used the PDANet driver to update it.
I am trying to upgrade to ginger bread from froyo using Kies (Phone Galaxy S I9000)
1) I am able to connect to Kies
2) It is telling me that firmware update is available
3) When I try yo back up contacts error message appears
4) It started downloading components but in background i can see device is disconnected
5) Again it starts connecting
6) It gave error message "device not responding.. To resolve this issue, reboot your device"
I repeated steps several times but same result. Any help please??
Please find screens attached
I would suggest that your first action, if there is one available, is to try upgrading via another computer. Although the latest Kies seems to work on more computers, there have been random problems with connecting phone to Kies in the past.
I have tried to upgrade my phone using a computer running XP SP3, never worked, Vista, only works with the latest Kies, and windows 7 64bit, always worked.
Hope that this is some help.
Hello I tried it in two different laptops but result is same
1) Windows XP 32 bit
2) Windows 7 64 bit
There is a long thread on the Kies/Gingerbread update here: http://forum.xda-developers.com/showthread.php?t=1211939. You should have a look through it.
I had the same problem you're experiencing, on 3 separate computers running WIN XP. The cure was to delete the installed Samsung USB drivers (do this via the Add/Remove programs in WIN Control Panel). Reboot the PC, clean up the registry (I use Glary Utlities). Launch Kies and tell Kies to install the drivers. This worked for me.
this driver problem is driving me crazy. it's the same story in XP as well.
i think it stems from the fact i've messed around with so many different drivers that my 7x64 and XP machines just don't know what to install anymore.
it has worked in the past. first time i rooted this phone i had to mess around with win7 drivers (to the point of almost giving up) to get windows to recognise the device at each stage of the root. this was done using a combination of HTCSync 2.0.33 and PDAnet's drivers.
since then i've had to flash to stock for an RMA, then went through the whole nightmare process again a second time. i mistakenly assumed that it would be easy the second time..
I've just accidentally flashed back to stock again, and this time it doesn't matter what i do, i just can't get these f*****g drivers working! same story on XP (which has also had numerous drivers installed over and over again).
i've even taken the phone apart to check nothing's damaged and tried a different usb cable, and un/modded google drivers.
one thing i noticed is that after rooted and flashing cymod, the previously working drivers no longer detect my phone.
has anyone had a similar experience?
Hello all,
I installed the CM9 pre-alpha on my Droid X yesterday, and I missed a step in the installation so that I needed to sbf. However, I cannot figure out how to install the Motorola drivers on my computer which is running the Windows Developer Preview. I've tried compatability mode, Application Verifier, everything. The problem is that the msi installer that puts in the necessary drivers keeps telling me that it doesn't recognize my operating system, and closes afterwards without installing.
Can anyone help? My Droid is, for the moment, bricked.
Hey, I don't know about Windows 8, but if it's in need of a quick fix, I would think about throwing up a Ubuntu partition on your hd and SBF-ing from there. My second suggestion would be to revert to 7, or find a friend willing to let you borrow their computer for an hour or so.
Best of luck, and consider emailing Motorola about drivers for Windows 8 (I wouldn't mention the whole SBF scenario to them however).
You can also use 1kds's Linux method... you'll be booting up from the disc... So no need to worry about drivers or partitioning
Sent from nemo walking solus
I'm planning on installing Windows 8 very soon, so maybe we can come up with a solution.until then try the 1kds Linux method.
Beamed from my TF101 using Tapatalk HD
New Problems...
Well, thanks for the suggestions everyone!
Of course, now I'm in even deeper you-know-what... I found a Windows 7 machine that I could use, and for awhile I had the really scary "code corrupt battery low cannot program" message since the battery was dying.
To bypass this, I used a method employed by users at another forum in which I ran a cut up USB cable to the battery terminal to supply power from the computer while running data through the normal USB cord.
It worked beautifully, and I SBF'ed to .602, but now the battery isn't recognized.
I managed to see the Battery and question mark message the first time I plugged it back into a wall charger, but now, when I plug it in, I only see the green charging light without the display coming on.
Thanks so much guys!
Hi guys,
I want to go back to stock since 4.4 is coming. However, when I try to flash the stock rom+ with Nexus Root Toolkit 1.7.3, I get stuck at the whole fastboot part. Fastboot IS working on my Nexus, but the drivers cause a lot of trouble. Installing the drivers when my device is running normally ( so no fastboot mode or whatsoever) works fine.
I have followed the Full driver installation guide where I tried options 1 till 4 but they all get stuck at the point where my device reboots into fastboot mode. At this point, my computer doesn't recognize my device and gives me an error. My nexus is shown in the device manager as unknown device and updating the drivers manually by redirecting my computer to the NRT drivers does not work. It says it cannot find drivers for the device. Does anyone know what I might have done wrong?
Or is it possible to flash a stock rom through twrp? like this one? http://forum.xda-developers.com/showthread.php?t=2376881
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
issak42 said:
TL;DR: use a machine with Windows 7 installed. Or boot ubuntu from a usb stick.
I've researched a lot about this, I had to downgrade my dad's phone with Flashtool (for Xperias), and after trying about every tutorial I encountered (removing drivers, installing different drivers, changing ports, disabling driver signature verification in Windows, I installed android studio, adb separately, running everything in administrator mode), I remembered I have a W7 machine on the other desk, it worked like a charm.
W8 (or 8.1, it's the same thing) is bad for flashing, I don't know when they're going to fix it.
Click to expand...
Click to collapse
Yeah, I tried the same things you did, including disabling driver signature verification but it won't work. I'll try a windows 7 machine.
Thanks for your answer!