Previously I rooted and switched my htc one m8 to cyanogenmod, but because android pay doesn't work on rooted devices I want to return to stock by using the RUU. Unfortunately, each time I run the RUU on my pc (windows 10) the installer quits after I accept the licence agreement. I have a relocked bootloader and have tried the RUU with usb debugging on and off. I've also tried it with the phone on normally and in fastboot mode. I don't know what else could be going wrong. Any help is greatly appreciated!
(I also have s-on, but I don't think that's the issue)
When you say "the RUU" which one are you talking about (exact file name)?
The latest 4.28.502.2 seems to work better on Win10 (as opposed to the previous Lollipop RUU 4.28.502.1).
But if you are already using that RUU, see if you have USB 3.0, as that is known to cause issues with RUUs. Your computer may have USB 2.0 ports, or I've seen someone say you can "turn off" USB 3.0 (not that familiar with the process for that).
But otherwise, you may need to use another computer. One with Win7 and USB 2.0, if you can find one.
redpoint73 said:
When you say "the RUU" which one are you talking about (exact file name)?
The latest 4.28.502.2 seems to work better on Win10 (as opposed to the previous Lollipop RUU 4.28.502.1).
But if you are already using that RUU, see if you have USB 3.0, as that is known to cause issues with RUUs. Your computer may have USB 2.0 ports, or I've seen someone say you can "turn off" USB 3.0 (not that familiar with the process for that).
But otherwise, you may need to use another computer. One with Win7 and USB 2.0, if you can find one.
Click to expand...
Click to collapse
I am currently using 4.28.502.2 RUU to no success, I actually saw another post of yours with a guy that had the same problem as me. You suggested to try another PC so I think that's what I'll try next. Thanks for all the help so far, I'll be back with results!
redpoint73 said:
When you say "the RUU" which one are you talking about (exact file name)?
The latest 4.28.502.2 seems to work better on Win10 (as opposed to the previous Lollipop RUU 4.28.502.1).
But if you are already using that RUU, see if you have USB 3.0, as that is known to cause issues with RUUs. Your computer may have USB 2.0 ports, or I've seen someone say you can "turn off" USB 3.0 (not that familiar with the process for that).
But otherwise, you may need to use another computer. One with Win7 and USB 2.0, if you can find one.
Click to expand...
Click to collapse
The best I could do was our old desktop running Windows Vista, even though the process took forever, switching computers was the answer! Thank you so much for your help!
xxsniper74 said:
The best I could do was our old desktop running Windows Vista, even though the process took forever, switching computers was the answer! Thank you so much for your help!
Click to expand...
Click to collapse
You're very welcome. Glad to see it worked out!
Related
Good Morning!
Well, I upgraded the ROM on my (previously) Cingular 8525, two days ago, and continue to fail at getting it recognized by both my Dell M170 laptop and my Alienware Area51 Desktop via USB.
Activesync 4.5
Tried it with both Advanced Network Functionality and without.
All firewalls off.
No errors during ROM update.
Tried two different USB cables.
Reinstalled XPpro SP2, fully patched.
Tried removing and rediscovering all USB drivers for both machines.
I've tried everything I could think of, and in every order I could think of.
The OS discovers the device, and ultimately gives me a popup message that the USB device is installed correctly and ready for use, but then 10sec later I get "USB Device Not Recognized" pop up error....
Should I roll back to a previous version of Activesync? Can I roll the ROM back to a previous version?
I admit to surveying the forums here before posting, but it seems a bit confusing to me and I certainly don't want to destroy my phone.
Thanks in advance for your help!
jdtarch said:
Good Morning!
Well, I upgraded the ROM on my (previously) Cingular 8525, two days ago, and continue to fail at getting it recognized by both my Dell M170 laptop and my Alienware Area51 Desktop via USB.
Activesync 4.5
Tried it with both Advanced Network Functionality and without.
All firewalls off.
No errors during ROM update.
Tried two different USB cables.
Reinstalled XPpro SP2, fully patched.
Tried removing and rediscovering all USB drivers for both machines.
I've tried everything I could think of, and in every order I could think of.
The OS discovers the device, and ultimately gives me a popup message that the USB device is installed correctly and ready for use, but then 10sec later I get "USB Device Not Recognized" pop up error....
Should I roll back to a previous version of Activesync? Can I roll the ROM back to a previous version?
I admit to surveying the forums here before posting, but it seems a bit confusing to me and I certainly don't want to destroy my phone.
Thanks in advance for your help!
Click to expand...
Click to collapse
what os is running on your computer?
XPpro SP2 fully patched
jdtarch said:
XPpro SP2 fully patched
Click to expand...
Click to collapse
do you have .NET framework 2.0 installed?
edit removed questions that were answered in first post (guess I should read closer)
Did you flash a WM5 or WM6 rom?
I have issues with AS not being able to connect to my device sporadically when I am running WM5 roms but don't have issues at all with WM6 roms. I have no idea why this is but this problem goes away for me while running WM6.
Can you boot into bootloader and get a constant USB connection that way? if so you may be able to flash to another custom rom or shipped carrier rom.
And I know you said you already did this but uninstall and re-install activesync 4.5 to make sure its drivers are not corrupted. Select yest to overwrite when prompted (if prompted).
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.
So I'm trying to get back to HTC to test a few things.
My keyboard is not working well at all with Froyo for some reason and I'd like to make sure it's Froyos problem (anybody else got this problem?)
I've found this thread: http://forum.xda-developers.com/showthread.php?t=559622
I run the wizard and it can't find my phone, though it's connected to the usb and all.
Is that how it should be done?
There is a thread somewhere by btdag called ruu and usb errors solved. That should sort you out.
Sent from my HTC Hero using XDA App
Looks like this thread covers exactly what I'm looking for (including the keyboard issue):
http://forum.xda-developers.com/showthread.php?t=750318
Basically:
For anyone having issues with Error 155(CID-checks fail, perhaps?) or 171(USB fail) while trying to restore a rooted HTC Hero to stock with an official RUU-exe, this is what worked for me where nothing else did:
- Create Goldcard
- Extract ROM.ZIP from the Official RUU exe you want to use. I downloaded it from their main site
- Rename to HEROIMG.zip
- Boot to flashboot mode (Volume down + Power on)
- Flash.
- Reboot and enjoy your new stock HTC Hero.
Click to expand...
Click to collapse
Haven't tried yet but should do the trick.
Haven't found the "ruu and usb errors solved" thread though.
Thanks!
[Guide] Drivers & RRU Errors Solved
... If you need it...
This is frustrating.
Got stuck in the very first step of both guides.
The one saying to make a gold card, I can't even run adb on windows. It says command not found on cdm.
So I'm going to the more reliable guide with the screenshots.
Right on the first step when you need to uninstall drivers, I select and click "uninstall" and nothing happens.
Gotta love windows.
Anyone who succeded doing this and how?
m4co said:
This is frustrating.
Got stuck in the very first step of both guides.
The one saying to make a gold card, I can't even run adb on windows. It says command not found on cdm.
So I'm going to the more reliable guide with the screenshots.
Right on the first step when you need to uninstall drivers, I select and click "uninstall" and nothing happens.
Gotta love windows.
Anyone who succeded doing this and how?
Click to expand...
Click to collapse
Were you in the correct folder when you tried to use adb? You need to install adb from the sdk, and run it from that folder, else windows can't know what program you are trying to use, unless you add it to $PATH.
I use adb all the time, and have tried millions of driver versions without issue.
pulser_g2 said:
Were you in the correct folder when you tried to use adb? You need to install adb from the sdk, and run it from that folder, else windows can't know what program you are trying to use, unless you add it to $PATH.
I use adb all the time, and have tried millions of driver versions without issue.
Click to expand...
Click to collapse
ยจ
Thanks for the reply.
I didn't use ADB; no idea how to use that.
I managed to get it working after some struggle and what worked was:
- Install HTC Sync. That will install the correct drivers
- Install HTC RUU from the official site
It was many trial and error times but in the end it worked.
Thanks again!
i have same problem. i want back my official soft with now root, but when i tried it with HTC RUU i get error (something about please check the phone has correctly connected on computer) so i don't know where's the problem. And one question more: when i plug my phone with usb cable to computer then which mode should i use? (charge only,disk drive...)
sc0rpp said:
i have same problem. i want back my official soft with now root, but when i tried it with HTC RUU i get error (something about please check the phone has correctly connected on computer) so i don't know where's the problem. And one question more: when i plug my phone with usb cable to computer then which mode should i use? (charge only,disk drive...)
Click to expand...
Click to collapse
Try Installing HTC Sync first.
You using Windows 7 right? I think it's a Windows problem that install wrong drivers. HTC Sync will fix that.
Then you can try again.
The usb you just plug and you're done, no need to set a mode. You should get a (sound) notification that it's plugged.
My major issue with this is the need for a win machine. Everything would be much better if I could just do it in linux.
My phone was sent to repair now You also got trouble with the Hero keyboard?
nope, but the gps is dead. I try to repair it by warranty. But at the moment i have froyo rom with root and as you all knows ROOT=NO WARRANTY :S
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.
My computer is not installing the software it start to install and when it gets to license agreement it stop installing after your agree I tried everything but nothing works ? please help !!
Sent from my HTC One_M8
wuflu23 said:
My computer is not installing the software it start to install and when it gets to license agreement it stop installing after your agree I tried everything but nothing works ? please help !!
Click to expand...
Click to collapse
First of all, saying you "tried everything" is so vague as to be pointless and not even worth typing. What does "everything" mean? If you aren't specific as to what you've tried and what you haven't, it makes it harder for folks to help you.
The most common fixes for USB connectivity issues and/or RUU issues are:
- Try running the RUU in bootloader-fastboot mode, and also booted into OS (if possible).
- Uninstall and re-install HTC drivers
- Try a different USB port
- Try different USB cables
- Disable USB 3.0 if you PC has it
- Try a different PC
- Don't run on a Mac emulating a PC
Also, you haven't provided much info. S-on or s-off? Is the bootloader relocked or locked (a requirement to RUU if you are s-on).
A few folks have reported the issue of RUU terminating with no error at or after the Terms & Conditions screen. If I remember properly, using a another PC is the solution.