I'm trying to run Revolutionary to gain root, but running into some driver issues. I've never had a problem connecting as a disk drive and transferring files from PC to TB or vis versa, so I haven't encountered this yet. But when I run Revolutionary I get stuck at "Identifying Device" (or finding, or whatever it says first). Uninstalled HTC Sync, uninstalled and reinstalled drivers. Installation process says everything goes along fine, but when I look in Device Manager I have an /!\ with this error message:
"Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 37."
Tried 2 different cables, 3 different ports (could they all suck?) Shows up in "My Computer" as CD Drive (K Verizon Wireless.
Running Windows Vista
Searched around a bit and saw some similar problems but under different circumstances and with solutions that didn't seem to apply. Anybody seen this? Know how to get it going?
Also, I'll run into the same problems trying to root through ADB, correct?
May have some corruption issue.
From the command prompt (on your PC), try running this:
sfc /scannow
Let it run then reboot and see if it fixes anything.
Good Luck
Nope....
Tried that, said there were some errors that were fixed (surprisingly vague about what), rebooted, but same problem. Any other ideas?
Unplug device.
Uninstall all drivers related to the device and reboot the computer.
Install the newest driver package from the HTC website (sync not required). *Optionally, you can just update your current driver using the inf located in step 12 here instead of the driver package from HTC.*
Reboot if prompted.
Turn on USB Debugging in settings->applications->development.
Plug phone in.
Try again.
Related
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
msiviter said:
Hi,
Using the old HTC wwe RUU (I've tried the two different recommended ones from the guides here at unlockr and Modaco) the RUU goes to the bootloader then on the PC is says 'waiting for bootloader' which then goes to error [171] USB connection error after about a minute (handset displays USB RUU). I've got adb and all the drivers. What am I doing wrong, I establish a sync with HTC sync (latest version ) before launching the RUU? Can I use Droid Explorer to help me or are these RUUs the only way of getting an old ROM on?
Can anyone suggest anything?
Thanks
Matt
I've trawled the forum with search but can't find a resolution.
Click to expand...
Click to collapse
You are probably running the wrong driver. Follow my driver guide part iv. (You should be on My HTC not ADB driver)
If not then probably your gold card hasn't stuck (check it) or you'll need to use windows xp instead (can use a virtual machine).
I had this issue when using windows 7 64 bit.
Download the drivers in the attachment in the noob guide. Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
oliwan said:
Then reboot your phone into the htc bootloader (power on while holding back button).
Then connect your phone to the pc and use device manager (have disk) to install the drivers you downloaded. then run the HTC RUU with the phone still in the htc bootloader.
The drivers had to be installed whilst I was in the bootloader for it to work for me.
Might be worth adding this to the noob guide?
Click to expand...
Click to collapse
Depending on whether this works for this guy, might be a simpler method than the alternative.
@msiviter - please try the above quoted method first
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Try This
While trying to flash the RUU the phone reboots.
When it is rebooted you see RUU.usb on your phone screen. But no flash process.
While phone is still connected to pc and is still in RUU.usb mode.
Go to device manager on your pc. Right klik android devices and renew the USB driver to HTC driver.
Reboot computer and reboot phone.
then try to flash again.
This was the solution for me.
Tried all the above, spent 6 hours on it, I've got the closest by going to a (win7 64bit) pc that has never had the sdk on it then the RUU goes further but terminates with error [140] Incorrect Bootloader. I've made my goldcard again to no avail (Sandisk 512mb) and checked the goldcard data which was OK, I'll try it tomorrow on a different (Kingston 8gb) card.
Any other ideas?
Thanks for your help so far.
Matt
Update: New SD card and goldcard now gives 'Error [131] Incorrect Customer ID' on my Win7 x64, I'll try on my dads old XP laptop later!!!
I suspect it is a windows 7 issue. On the first attempt I managed to downgrade when I moved to my Vista machine.
I must have tried for about 6 hours with Win7 then moved back to my old Vista PC and it worked first time.
From observing the process on Win7, when the phone boots to the bootloader, the RUU program then gives it 180 seconds to confirm Bootloader is loaded "waiting for bootloader...1-180sec". Looking at the system tray the USB driver that is used for HTCsync disconnects and the device now says it is Android 1.0 and Win7 needs to find a driver for this. Win7 fails to find a driver for "Android 1.0" so it never allows propper communication between the phone and the computer.
(There are separate Win7 64-bit drivers - check you are using these?)
P.P.S. The stock card that came with the phone worked fine as a Goldcard for me and I think most people.
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] whether trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
You installed the latest version of HTC Sync while your phone was unplugged/ Then you plugged the phone in to detect new drivers. Waited for the drivers to successfully install and then ran the RUU?
msiviter said:
OK I've now tried on a sp3 x86 XP machine and I still got Error [140] and [131] wheter trying from phone synced to pc or phone booted in Fastboot USB.
I've given up. I'll wait until June!
Click to expand...
Click to collapse
What drivers are reading in device manager when in the normal os? And same question when in fastboot mode?
I did exactly that on my win7 x64 and xp mce sp3 x86 pc's both had 'My HTC' in Device manager and had a sync relationship established with the latest 'Legend' HTC sync software.
Both gave the almost random error messages although now the bootloader almost finishes now so I'm past the [171] usb (driver) errors and I'm on [131] and [140] errors which pertain to bootloader and incorrect customer errors which I think are goldcard related. Although like most people I do rush through things and not read instructions! I've now made 4 goldcards via the various guides and I'm sure they are OK.
My Bro is getting his desire this week and I was determined to beat him to eclair but it looks like I'm in the lap of the T-mobile gods waiting until June (or july....September.... December etc).
Matt
I have same issue with msiviter, CUSTOMER ID ERROR.
I was able to run RUU regarding to guid from btdag (section IV).
What can I do now?
try deleting the drivers and then starting again perhaps?
I have the same issue here, can't downgrade to the previous Orange RUU, also using Win7 x64.
Have tried reinstalling drivers, and using other ROMS, nothing seems to work. I also find that when I run the RUU it loses connection to my phone before it even tried rebooting the phone into the bootloader.
shotgunfool said:
I had this issue, and the solution for me was just to swap to a new computer, and it installed instantly
Click to expand...
Click to collapse
this is how i've done 2 of mine, 2 dev laptops on 2 differnt hero's ... didnt work, with adb, sdk everything loaded for android dev ...
desktop worked fine for both hero's.
Same Issue
The trick to get the RUU to actually update the phone, for me, was to make sure that in Device Manager the ADB Interface driver was showing "My HTC" and not "HTC Bootloader". I was able to switch between drivers using the update driver button, and didn't need to download any new files or specify a folder or anything.
use windows xp and try my method of downgrade from 2.1 in my sig.
I installed latest version of Kies in my Windows 7 Professional 64bits (UAC disabled, install was "ran as admin")
In the end of the installation process, Windows shows a balloon saying it is installing the driver for the device (note that there is no phone connected to the computer at that moment), but it fails saying that it could not find the driver for the device.
After installation finishes, I can connect the phone, open and use Kies normally, but if I go to Windows device manager, in the "Other devices" branch, it still lists an "Unknown device".
Any idea about how to solve this? I already searched the forum, but could not find anything that worked for me.
Thanks!
PS: I'm using the original USB cable from Samsung.
As long as you are able to connect and work via Kies just leave it. Just check how many people are having problem with Kies, you should consider yourself lucky that you don't have a connection problem
Regards.
Leave your phone plugged in and do a windows update. It should find the missing drivers.
You can find the drivers inside the dir where kies was installed, alternatively a copy is stored on my 4shared, link in my sig.
You can try installing the drivers and see if that helps.
Kies is a huge PITA, you may need to swap USB port and uninstall/reinstal for it to get its act together.
Thanks all who answered.
Unfortunately, Windows Update can't find any driver (already had tried that), and also asking to update the driver and setting it to search in the Kies driver directory has no effect either.
I just got a Motorola Droid RAZR and have been scouring these forums as well as other websites and they all seem, to me at least, that there is no kit to root a RAZR on 2.3.6
I have downloaded DooMLoRD_v2_ROOT-zergRush-busybox-su as well as MotoFail and it is just not working. I am using Windows 7 64-bit and the first issue that I run into is that it will not recognize my device when I plug it in. Now you may be saying, well go to Motorola's site and download the v5.4 drivers you idiot, well I am one step ahead of you, I did. Still not being recognized. Tried manually installing the drivers and telling me it is not being recognized.
If any of you out here now of a way to have the RAZR recognized by my computer and root this device, I would gladly donate to the cause.
Maybe you could try this.
When you plug your device in. On the Razr itself. Pull down the notifications menu and tap on USB Connection. Make sure it's not on "Charge Only".
I don't have that option in my notifications menu. I have selected "Allow installation of unknown sources" as well as enabled USB debugging within the application setting menu and still it will only charge the device.
Gotta ask...........you do have the 64bit drivers, right? And your logged into the PC as an admin?
Yep. I am the admin. of the computer and I am trying to install the 64-bit drivers as well. I just don't understand what I am doing wrong.
Thinking of maybe testing on a new user profile and seeing if that changes anything, if it does, then I can narrow it down to being a user issue, but I am sure I will run into the same problems on a new user account.
Can you check Device Manager and see if you have the "yellow triangle" showing for MTP USB Device?
I did check the USB drivers list and there was one where it had the yellow triangle. I tried right-clicking on it and uninstalling it then re-installing, still same issue, not being recognized.
Ok, try this. Go back to device manager again. Locate the MTP USB Device that's showing the yellow triangle. Right click and choose select update driver. Select 'browse my computer for drivers' and then choose "Let me pick drivers to install". You will get two options; select the USB controllers and click OK.
See if that helps. And make sure your phone IS NOT connected to the PC while doing this.
I think the problem may be that Doomlords hack doesnt work on 2.3.6 no matter which version of the exploit you try. It happend to me with my Australian Optus Razr when I tried to run the exploit after the OTA update and it kept failing. I have since been able to get root but theres a few things I had to do which I'll list now:
1. Install the Android SDK.
2. Install the Moto drivers.
3. Install RSDlite 5.6.
4. Find a stock 2.3.5 ROM to flash to your RAZR then do it using RSDlite.
5. Run Doomlords exploit and you should now have root.
This worked for me after alot of f***ing around but now Im running a stock rom (SPDREM_U_01.6.5.1-167_SPU-15-M2_SIGNEuropeAustraliaEMEA_USASPDRRTGB_HWp2b_Service1FF_fastboot.xml) and it works brilliantly.
Hope this helps.
Alright, give me about an hour to get it all downloaded. Using Barnacle WiFi tether right now on my Incredible to download everything necessary. If all goes well, someone will be getting a donation from me as this is causing me a lot of stress and I just want CyanogenMod 7 on this phone.
I'm sorry if this is a bad post, I'm new to these forums. I used the viperMod tool to install CWM, rebooted, and I now get the 1a brick error described the the developers section. However when I try to fix it using adb (which I have installed correctly), it doesn't work.
To be specific, my computer (running windows) doesn't recognize that I've hooked it up in devices. I do an adb devices and get "List of devices attached" and nothing shows up. Each time I plug in the prime, I get the usual beep that windows recognizes it is attached, however it does 3 real quick beeps and then nothing happens. I think if I could get it hooked up properly the fix described in the developers section would work, but for some reason my computer doesn't like it.
Any suggestions and/or help would be greatly appreciated!
This might sound a little silly but have you installed the drivers?
If you have the drivers installed windows should detect the device correctly and you'll be able to use adb. There is a link to universal drivers in the dev section, or you can get ASUS' from their support website.
I had the drivers installed properly prior to the CWM installation. However, the 3-tone beep does indicate that the drivers are not installed. Unfortunately the prime isn't showing up in device manager at all, so I need to figure out how to re-install the drivers and see what happens from there. Is it possible to install drivers for a device that doesn't show up in device manager?
Ok, so I can't install the drivers for the device. The only thing device that pops up in device manager is "Full Android on Emulator" in "Other devices". I try to install drivers for it, and it does not like either the universal drivers or the drivers from ASUS.
Why would windows not recognize it as an android device like before? I haven't touched the drivers which I had installed and previously worked. I feel like the only thing stopping me from unbricking the device is a connection issue. Any suggestions?
Well, here was my fix in case someone else had this problem:
In device manager under "Other Devices", I selected "Full Android on Emulator". I selected to install drivers, and browse to drivers. Now where the stock ASUS drivers would not work, the universal driver posted in the dev section worked, although it thought the device was some samsung phone.
It turns out that was OK. I followed the unbrick instructions from 1a in the dev section and all is well.
I appreciate the geniuses who post all these fixes and mods. Great work!
The phone and cables are good as I can get HTC Sync to work on my old PC and this one worked just a few weeks ago and I can even get it to work in a VMware session. But for whatever reason the phone just keeps showing up as Unknown and is put under Other devices as “Android phone”. On the other PC and in the VMware it is added as "My HTC" under Android USB Devices in Device Manager.
I’ve tried a bunch of uninstalling and rebooting and so on but something on my new Windows 7 PC is stuck when connecting the phone. It thinks it has no driver for it but it does. If I try and point any of the HTC INF files Windows just says they are not for this device.
Help!
Thanks.
Tanquen said:
The phone and cables are good as I can get HTC Sync to work on my old PC and this one worked just a few weeks ago and I can even get it to work in a VMware session. But for whatever reason the phone just keeps showing up as Unknown and is put under Other devices as “Android phone”. On the other PC and in the VMware it is added as "My HTC" under Android USB Devices in Device Manager.
I’ve tried a bunch of uninstalling and rebooting and so on but something on my new Windows 7 PC is stuck when connecting the phone. It thinks it has no driver for it but it does. If I try and point any of the HTC INF files Windows just says they are not for this device.
Help!
Thanks.
Click to expand...
Click to collapse
make sure you have the correct drivers for you phone, if you using the latest version download and install an lder version of the drivers then try to connect
That’s the thing though. The drivers were just fine a few weeks ago. The same drivers work on another PC with this phone and they work now on this same PC in a VMware session. There is something stuck in my Windows host install that no longer allows any new devices to be installed. Like one of the fixes I found on line was to remover your USB hubs and let Windows find and install them again but then they could not be installed and were added to the Other devices. I had no mouse or keyboard. I had to run a system restore under the F8 options on boot up. Unfortunately I don’t have a restore point older than the issue. Even if I unplug my working mouse and put it in a different USB port it too is added to Other devices and no longer functions. I just get messages about it being an unknown device and that no drivers can be found.