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.
Hi!
I have (had maybe) officail Android 2.1 with sense. Yesterday an OTA update showed up, so I updated the system and the phone is now down.
System doesn't start at all... Only HTC logo shows up, I can't flash any official HTC rom.
Errors:
140: wrong bootloader version, 131: wrong client ID
the only error information from HTC phone is... as I show on picture... very informative and descriptive
I've tried 6 offficial update rom's from HTC.
The phone error statement is red error sign...
Graphic, no text :/
I attached a photo with this
All the thing is quite recent, any ideas?
Cheers!
Paweł Lipko
What you need to do is download the android recovery system, see my sig (RA-hero-v1.7.0.1 Recovery). Install that and then let us no when you have. This will enable you do do other things and then we can go from there.
Hi again!
At the beginning I would like to say thanx for help
Ok following "RA-hero-v1.7.0.1 Recovery" thread I've downloaded SDK with ADB.
To be correct with the timeline, I'll tell that this PC already has got HTC drivers coming with HTCSync software. Probably I write too much, but it's better to have too much of information than too less
Before the problemm which we are trying to solve here - phone worked fine with windows. Now XP says, that "device hasn't been recognized succesfully and the gear could not work correct. (I don't know english version for that, Polish Windows I have )
Next - ADB doesn't see the phone:
\Android SDK\tools>adb shell reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Restarting windows - doesn't help
Trying to list devices in ADB - none
restarting AB daemon - doesn't help
Removing HTC Drivers and HTC sync (it was old version for android v.1.5 and 1.6. Still it worked before disaster with 2.1 )
Rebooting XP
Installing HTC Sync for Android 2.x. This include: HTC BMP USB Driver 1.0.5375 (32Bit), HTC Driver Installer 2.0.7.018
After installation new HTC Sync, XP says that it recognized the phone correctly, but still I have no access to SD Card storage. Only drive letter shows up. Lets take it as progress
still yet ADB gives output:
\Android SDK\tools>adb shell reboot bootloader
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've tried to puty the same command with FastBoot and HBoot - but - nothing new comes with that...
At this level I think I'm stuck.
knock knock - any ideas?
What operating system are you running? Definatly a driver issue.
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Shadow_82 said:
Windows XP SP3 Polish ver.
HTC Drivers as I wrote earlier - latest from htc.com
As for now I'm downloading HTC Sync also for older Androids - 1.5 and 1.6.
I'll try to remove this HTC Sync for And 2.1 with drivers and install that for 1.5 & 1.6.
If You say, it's a drivers issue - maybe there is a mess on my PC, I'll try using another one or two with both HTC Sync versions and give You a reply.
But when the disaster happened I tried to flash Hero with official ROM and I've had only info's like error 131 or 140 - as I mentioned at the beginning.
And it was other PC, with brand new HTC Sync, so the driver problem could be... no the clue...
I'll post when I'll try to install HTC Sync on other PCs.
Cheers!
Paweł
Click to expand...
Click to collapse
ah in that case error 131 or 140 is nothing to do with drivers, for error 140 as far as I know the ROM is not compatible. You will need to try find a version that is suitable. try the HTC website for updates.
Hmm.. You say that it's not drivers problem?
Well...
I already tried to flash these ROM's listed from XDA Developers:
[ROM] Official HTC Hero RUU ROM + Radio Links
WWE: (World Wide English)
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_ NoDriver.exe
RUU_Hero_HTC_WWE_1.76.405.6_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoD river.exe
RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_No Driver.exe
RUU_Hero_HTC_WWE_2.73.405.61_WWE_test_signed_NoDri ver.exe
RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe
I've tried also ROMs from official htc.com website.Europe website and Polish website - still its the same, but when something doesn't want to work...
ROM version 2.73.405.5
All of them gave me errors:
140: wrong bootloader version,
131: wrong client ID.
All of these ROM's weren't able to say which version currently is installed on my HTC Hero...
Total HTC Hero Eclipse
I'll try to flash them once again, right now I take my pendrive, I'll go to my friend and let's roll
God damn it - another Q - by the way
How I'll be checked to be able to post external links?
Should I ask some moderators?
Or it'll happen just like that in a month or year?
ok.
another PC, completetly not known to this HTC Hero.
first windows told me that it doesn't recognize the phone. It's ok. it doesn't have any drivers.
I've installed latest HTC Sync with drivers - the one for Android 1.5 and 1.6, filename:
_HTC Legend_HTC_Sync 2.0.40.exe
Rebooting windows and...
Windows still doesn't recognize the phone
Trying to flash it with one of official ROMs
Yup - error 170 - no connection with phone
adb devices - no devices...
next: uninstalling this HTC Sync
rebooting windows
installing new one for android 2.1
filename: _HTC Wildfire_setup_3.0.5422.exe
rebooting windows
once again windows doesn't recognize the phone
Trying to flash it with official ROM
filename: RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
Connection error... damn...
ADB:
\HTC SDK\tools>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
After some fight with USB I managed to make Windows recognize the phone, a drive letter shows up, but I can't acces data on SDCard.
ADB after restarting it's daemon doesn't see the phone
Another try to flash it with official ROM
ok. there's any progress - RUU App sees the version on the phone
trying to flash the phone
and... error 140 - wrong bootloader ver.
ADB: error: device not found
I'm starting to be confused...
Any ideas?
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello Friends!
I'm from Argentina, and recently bought an oppo find x (chinese version].
The first thing I wanted to do was install more locale 2, so that I can have most of my apps in Spanish.
Of course before I created this topic I searched if there's a solution out there, and I found this thread:
https://forum.xda-developers.com/find-X/help/install-locale-t3818383
I followed that, step by step but doesn't work.
Indeed I tried the "long" version of it here: https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
But with no luck. The problem is that I never get the prompt notification on my phone allowing usb debuggin (step 11).
So I think the problem must be in the drivers, that for some reason my windows doesnt install the drivers of my phone (but I can Transfer files with no problem....that's strange).
But where can I get those drivers? They're not even in oppo page.
This problem is driven me crazy, even more cause I think I'm the only one with this issue!!!
PLEASE HELPPPP
New information: I tried with another PC (with Windows 10) and with another cellphone (vivo x21). With both devices and both PC the problem is the same: when I write the command adb devices no devices appear, despite I have the USB debugging enabled in my phone. If I write the command adb shell it says no devices/emulators attached.
I'm have no clue what to do now.
Hello everyone.
I have found a solution. I leave it here, in case someone is in this 1% like me with problems with adb:
The problem was the drivers: apparently my windows doesn't have the correct driver to support ADB android interface, and it doesn't get installed automatically with windows update.
So, what I did was download the drivers from here: http://adbdriver.com/downloads/
And ready, problem solved.
Now my google assistant doesn't work with more locale....but that's another problem...
Hello I recently purchased a used TF201. The device will not boot however and only shows the key driver missing..... and boots into usb fastmode. I have installed ADB minimal and have the stock rom ready but the drivers for the TF201 refuse to start. They install correctly but every driver brings back error code 10 device cannot start. Please Help
ASUS provide their own version of ADB drivers. Use the one that matches.
https://www.adbusbdriver.com/asus-adb-drivers-for-windows/
jwoegerbauer said:
ASUS provide their own version of ADB drivers. Use the one that matches.
Click to expand...
Click to collapse
i have tried them and got the same result, "Device cannot start error code 10" i have tried literally every driver i can find