This thread here: http://forum.xda-developers.com/showthread.php?t=2473644 has very few details on what software and drivers are required. I attempted to run the rumrunner tool on a Windows 8 and a separate Windows 8.1 machine, neither would recognize the HTC One and start the program.
I've never installed HTC Sync, so check that off. Developer mode is on. So I put Linux Mint x86 on a flash drive and booted to a live environment. Running the rumrunner tool from there now. After the third "pouring", it is sitting on "Waiting for ADB (18/120)" and "Waiting for device". It has been at this point for about 30 minutes now, I feel like something should have happened by this point.
I would've posted in the other thread, but apparently this forum is setup for new users to post in the general board first.
Advise?
Edit: Looks like it's finished. I couldn't wait any longer so unplugged it. Rebooted into fastboot and it shows unlocked. Great!
Related
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
MetroGnome711 said:
Greetings XDA,
I'm trying to hurry and unlock my One before Verizon locks 'er down tight, but i'm having trouble getting the Fastboot driver installed.
I've installed the java run time environment, sdk, and even the HTC my sync settings (with drivers) and am seeing "My HTC" under Android ADB devices while booted normally, but as soon as I jump to fastboot, the "My HTC" receives an exclamation point and the device driver says not installed.
I'm running Windows 8 x64 and tried these instructions here: http://forum.xda-developers.com/showthread.php?t=2232799
Any help? Any one?
Click to expand...
Click to collapse
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Sadly...
eL_777 said:
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
Click to expand...
Click to collapse
Sadly, i don't have such a machine lying around. The wife's comp has the sdk installed as well (she's a nexus user). Although, on her windows 7 machine, in fastboot i do see MyHTC driver as ok, but when i run the "fastboot oem get_token_modifier" command, i get "(bootloader) [ERR] Command error!!! OKAY finished"
so something still quite wrong!
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
.... This probably explains my problem as well. Will try on a Windows 7 computer in the morning and report back to see if that was the problem.
jadesocket said:
I don't think the Fastboot drivers work on Windows 8.
Spent all day trying, and never got recognized in ADB. Used co-worker's computer with Windows 7, worked like a charm.
Click to expand...
Click to collapse
ADB and Fastboot both work fine on Windows 8. I had to install the newest 4.3.0.001 drivers to get ADB to recognize my One on my Windows 7 partition, despite having had the most recent behind that. My Windows 8 partition worked like a charm because I had more recently installed the updated drivers on it. It's also possible you were connecting your phone to a USB 3.0 port. ADB/Fastboot is "wonky" over USB 3.0, and if you don't have the correct USB 3.0 drivers, you have no chance at all. Also, you need USB Debugging turned on, which can be done in this version of Android by going to Settings -> About -> Software Information -> More, then tapping on the build number 7 times, unlocking developer options, then going to Settings -> Developer options, and checking USB Debugging.
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
IceDragon59 said:
And all this may be moot for now, as it appears anyone who wasn't previously unlocked won't be able to for a while.
Click to expand...
Click to collapse
I can confirm. I successfully got fastboot to run on OS X, but when I try to send my token via HTCDev, I'm met with error 160: MID not Allowed..
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...
I meant to say that I found that thread after being stuck in mini poop mode.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now
Okay, I have the M9 through at&t with Software number 1.32.502.9 running Android 5.0.2. I'm stock, unrooted, S-On, locked bootloader.
So, I tried for the past two weeks to get the OTA for my phone and it's always the same thing...No Updates Are Available. Still to this moment, same thing. Did they actually push it out for AT&T?
I resolved to do the manual update with the RUU on HTC's website. On my 64 bit Windows 8.1 PC configured with HTC Sync, factory cable, correct drivers, correct ADB/Fastboot, antivirus/firewalls disabled, salt over right shoulder, seven hail mary's said, NOTHING FREAKING WORKS. I tried installing some C++ thing and it didn't work either. I've done registry hacks...NOTHING. Installscript runs, and then quits. I've watched taskmanager to see if the process is hung up, but after running for two minutes, the process quits and nothing happens. I've run the RUU as admin and not with the same results.
I've done all of the above on a windows 7 32 bit system and a windows 7 64 bit system all with the same results. I've talked to HTC chat people and they can't figure it out. Seriously folks, WTF and I doing wrong?
I WAS able to extract rom.zip out of the RUU on a 32 bit windows 7 machine but there was some failed error message when I tried to flash using the fastboot oem flash rom.zip command.
What country are you in?
USA. I finally got it but I don't know how or why.
Nm
So, I have found a couple other posts on this issue but none of their solutions have worked for me.
Ill start with the set up I am currently on:
-Stock Official Android N (US Unlocked)
-Firmware 2.28.617.8
-T-Mobile with CID changed to run US unlocked
-S-off and unlocked
-Using windows 10 with ABD Fast boot file (not sdk)
So I have the drivers installed. Originally I was just using the HTC sync software drivers but moved to drivers I found in a forum post here, which unfortunately did not work.
USB Debug is checked.
My phone shows as connected and I can run ADB Devices and see it in the list until I ADB reboot bootloader. Once it is booted into bootloader ADB no longer sees the phone. Checking device manager shows that the phone is connected with no exclamation mark or question mark next to it.
I have restarted and reinstalled several times with no luck. I even run a usb bootable copy of Linux Mint hoping that it may just be an MS issue but I have the same problem on Linux whether I sudo or not.
Since I have had the phone ADB has worked whether in fastboot or not. It was only until I ran the official RUU and upgraded to Android N that it has stopped working. If I am not mistaken, in MM there was a popup when you had USB Debug enabled and connected to a pc that asked if you wanted to use that pc (or something like that). I am not seeing that pop in N.
Any help would be greatly appreciated as I would really like to get twrp installed and rooted.
Thanks all.
I have spent the past couple hours fiddling around with this and thought I would add and update.
I downloaded and installed Android SDK, updating everything and adding the Google USB drivers. Unfortunately this did not work. Same result.
I did however just find that if I go to the stock recovery and select the Apply update from ADB option, the device is recognized again in my cmd window.
Am I missing something. Is there a new procedure for flashing things like twrp with command lines? All the forums still show Fastboot as the method.
Anyway, that is it for my feeble brain for the night.
Sometimes it helps to use the usbdeview tool. It removes the link to drivers and gives you a clean start. Worked earlier for me. File is attached.
@Ludolf71
I gave that a try but it doesn't seem to help. Looking through the list of drivers there doesn't seem to be any driver conflicts and the only instances that show up on the list relating to my phone are the vendor drivers and the port that the phone is on.
At this point I am lost. I have spent hours reading forums and searching around for a solution. I am not sure what might have changed between running MM and updating to the current HTC RUU. Prior to installing the current RUU everything worked fine.
Looking though dev options there is an option to revoke USB debugging authorizations, is there a way to see the list of authorized devices? Also, I swear that in MM when I had debug on I had to authorize my pc when I plugged it in the first time after a fresh flash. Is that not the case anymore or is that option somewhere hidden that I am missing?
Has anyone put together an adb zip specific to the HTC 10 and the current firmware? Do to changes in the Android N firmware could this be the cause?
I tried Andoid SDK last night but I have to admit I am not very well versed in their software so I may not done it correctly. I have been modding and flashing custom rom since the poorly name MyTouch but have so far gotten by without having to use Google software suite.
Thanks all for the help.
Tried installing the HTC Sync Manager? That shall provide you with the correct drivers.
Yeah, I have installed and reinstalled the Sync manager several times. Like I said the phone is recognized using ADB devices while booted to OS but the second I adb reboot bootloader it is no longer seen.
I keep coming back to authorizations and i think this may be the issue. I see the option to revoke but I am not getting any options to authorize the PC I am using.
Solved: I was using the wrong command line as pointed out by xunholyx in another thread. Thanks @Ludolf71 for helping as well. Felling pretty dumb about this one
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
---------- Post added at 06:40 PM ---------- Previous post was at 06:40 PM ----------
And why not help others with the same problem with provideing the link?
I'm stuck several hours now with that problem.
So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
hello
RyanCanning said:
are you on a custom ROM or a stock Sense ROM? I had trouble RUU-ing a stock package to update my firmware because of an issue with fastboot and LineageOS. I believe you can place a zip in the root of your SD card (it has to be named 2PS6IMG.zip) and flash it from bootloader mode or some similar mode. Fastboot worked fine while I was on the stock ROM
Click to expand...
Click to collapse
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
korko said:
you cant run ruu if you are bootloader unlocked, and is obligated is relock bootloader -fastboot oem lock that let you run the ruu again,after you relock and run the ruu , you can unlock the bootloader if want,and install another recovery, and rom
Click to expand...
Click to collapse
There is absolutely no requirement to relock the bootloader to flash an RUU or for that matter anything else on HTC 10.
shortyboy said:
So for the past few hours, Ive been having issues running the HTC RUU on my x64 Windows 10 Pro Laptop. After countless downloads and installs, I figure I share my solution for those in the future.
Problem: HTC RUU will not run, It will go to Accept or Decline T&E, then goto InstallShield, but does nothing after.
Solution:
HTC Sync
ADB Drivers
DotNet
Visual C++ 2008 x86
Make sure RUU.EXE has compatibility mode set to Windows 7 or XP SP3 ( tried both and got them to work on each setting )
Ive un-installed and re-installed so many versions of each. But only the Visual C++ is what really matters. Even if you're on x64 OS, you will need to install Visual C++ 2008 x86. Because The HTC RUU looks for the x86 files/directories.
Google the downloads and links.
Hope this saves someone a few hours of headaches or in my case 3 hours.
Cheers
-Wayne
Click to expand...
Click to collapse
I managed to run the US Unlocked RUU (2.51.617.1.exe) yesterday without (too many) issues.
I am on Win 10 Pro x64 (fall creator update).
From working with my previous HTC (ONE), I had already working HTC drivers, adb/fastboot, and registry hack so Win 10 can communicate with HTC devices over USB in fastboot.
Of note, I also do a bit of programming, so I have Visual C++ installed on this computer.
I ran the RUU.exe in admin mode. (NO compatibility modes set.) It was slooooow to load & run. I thought that the program was broken, but it eventually started. It was like 3 minutes before InstallShield open, then some minutes between each of the "questions" screens. I opened hardware monitor and noted no increased CPU/memory/Lan usages, so I am not sure what all the waiting was. <I have a reasonably fast setup - overclocked Intel desktop, SSD, Gb wired internet ... all the time this was running , I noted only like <10% usage of resources on my machine.>
But once the program got to detecting the phone, and actually doing the update, it was quite fast & painless.
I am pretty sure that the RUU running in slo-mo isn't normal, but at least it worked!
The problem sounds very familiar! Will definitely try with Visual C++ 2008 x86
How about all the rest? HTC Sync, ADB Drivers, DotNet… I’m only installing Windows on one of my Macs in order to run this RUU
Also… do you have an idea if I’ll get the same problem in Win 7? I’m not going to use it anyway, so I don’t really care which version of Windows I install.