Hi there, I am currently in the process of getting my phone back to stock but have not had much luck. I got a new laptop and so I needed to install the HTC Sync Manager with the necessary drivers. Unfortunately, during the installation I get an error 'It appears the HTC driver install has failed, do you wish to continue?' So, I click 'yes' and it installs and opens, but I assume without drivers. So, I went to the next step and got the fastboot files, and tried to get the original version so I could get the right stock ROM, but when I connect the phone up in fastboot usb mode and type the command into command prompt, it just stays at 'waiting for device' and then my phone freezes.
I can install new ROMs and edit through recovery, but that is the extent of what I can do. I currently have MIUI installed and I just want to get back to stock as I am selling the phone.
Any help would be appreciated.
Related
Hi
My Win7 disk crashed some time back and I'm trying to get it back to the way it was which, I believe, had hboot and fastboot drivers for my (now rooted) HTC Desire on it. I can't remember everything about how I did it before but now, when I put the phone into HBOOT then connect it to the PC, it installs as "HTC Serial Interface" and I don't seem to get it to become an "Android Bootloader Interface".
Can anyone suggest anything to help?
As I mentioned, I _think_ I had the hboot drivers installed before, but it's always possible I didn't so if I don't need them any more anyway as the phone's already rooted, please let me know.
What I remember from before was using fastboot to install a custom recovery so perhaps that's the case.
Thanks
John
jgmccabe said:
Hi
My Win7 disk crashed some time back and I'm trying to get it back to the way it was which, I believe, had hboot and fastboot drivers for my (now rooted) HTC Desire on it. I can't remember everything about how I did it before but now, when I put the phone into HBOOT then connect it to the PC, it installs as "HTC Serial Interface" and I don't seem to get it to become an "Android Bootloader Interface".
Can anyone suggest anything to help?
As I mentioned, I _think_ I had the hboot drivers installed before, but it's always possible I didn't so if I don't need them any more anyway as the phone's already rooted, please let me know.
What I remember from before was using fastboot to install a custom recovery so perhaps that's the case.
Thanks
John
Click to expand...
Click to collapse
Install these.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
What are you trying to do?
abaaaabbbb63 said:
Install these.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
What are you trying to do?
Click to expand...
Click to collapse
Those are the instructions I was following but those drivers wouldn't install by the "right click on the .inf file and select 'Install'" method so had to be done by attaching the phone. When I attached the phone Windows went off and installed the "HTC Serial Interface" drivers!
However - I had a bright idea; uninstalled the "HTC Serial Interface" driver from device manager, switched off my wireless (because the "skip checking windows update" option when drivers installing doesn't seem to work very well!) and connected the phone again. This time it said it couldn't install the drivers so I went to device manager and followed the instructions again and now have an Android Bootloader Interface.
Overall what I'm trying to do is just play with different ROMs. I'd s-offed etc and loaded teppick74's (or something like that) Gingerbread ROM some time back to give the phone to my daughter but she had some problems with it and now uses an iPhone so I've got it back. I had to use the AmonRA recovery (I think) for that ROM because it used the older format that EXT4 Touch Recovery didn't support so I'm just trying to get back to the state where I can use that and play about more.
Thanks for taking the time to answer
John
Hey guys,
So, I tried to turn my T-Mobile into a GPE. Everything went OK, pushed the RUU - and it hanged for a long time, so I quit out. Tried pushing it again, ADB not detecting the phone anymore - reinstalled drivers, rebooted everything - phone detected on pc as "My HTC", still no device detected in ADB. Rebooting the phone leads to the white HTC screen, booting into bootloader works but it's black for some reason, and I'm unable to boot into recovery - The OS text is red and reads "OS-3.32.531.2 (2.12.1700.1)". I've been trying to look for a solution for the past couple of hours but all the solutions require ADB to work, and all the solutions to get ADB to work are not solving it, so at this point I'm kinda stuck.
Any and all help would be appreciated greatly.
Thanks in advance!
I don't know if there's a t-mobile ruu available but if so, you can try and run that. I would simulate the battery pull first and then see if it recognizes it. From what you described for your os, mine would show that during the process of upgrading firmware
There is a T-mobile ruu in T-mobile one m8 general
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Salabrin said:
Is it possible to run an RUU when the PC doesn't recognize the device properly?
Click to expand...
Click to collapse
Nope. It uses adb/fastboot.
Try uninstalling all HTC Sync and HTC drivers. Then plug the phone, go to Device Manager, find the device and select the option to manually select a driver, then pick Generic MTP Android Device (or something like that).
Also, bootloader screen on GPE is supposed to be black.
So I ran an RUU, it gives me an image error - I changed the CID earlier to install GPE, is that what might be causing the issue? If so, is there a way to change the CID without adb(Still can't get it to detect the phone)?
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
kanagawaben said:
Wondering if any of you guys can advise me - having strange problems with fastboot (windows 8.1 and Zenfone 2 ze550ml). Wanted to flash the pre-rooted image to my device so downloaded it and extracted to the flashtools folder and renamed system.img then hooked up my phone. Checked adb drivers were installed and adb devices command returns a code string, so assumed all was good to go with flashing. However, on entering any fastboot command it just sits at "waiting for device". Tried manually starting the phone in fastboot and then connecting it, and this did enable me to execute fastboot commands (reboot or reboot-bootloader work). However, fastboot flash system system.img just results in a message about file size and then "failed to load system.img"
Click to expand...
Click to collapse
You need to rename the system image to system.img and put it where the fastboot file is. It's looking for it but can't find it.
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Cause Windows sucks. I'm on Linux and no issues. Maybe someone on Windows can chip in?
I can easily do a quick ubuntu install and try it that way if you think it might work better. At the weekend maybe. Could you give me some pointers on how to do it in linux if I do? Would be much appreciated!
kanagawaben said:
No, don't think that is my problem - as I said I extracted it to the flashtools folder, so it is already where the fastboot file is. And anyway, though I'd like to solve the problem of flashing the system.img, I am kind of more interested in why I can't get past "waiting for device" without first manually entering the fastboot mode.
Click to expand...
Click to collapse
I have encountered that problem with the "waiting for device" while I was flashing pre root rom.
Try the cmd adb devices
Then it will list the device connected to the computer...if it says not authorized, then you need to check the phone which is turned on and a pop up window with the RSA key and tap on trust this computer or something..
Then repeat adb devices and it should say allow or something..then it will allow you to flash.
(double check the commands online, I might missed something)
Nah, don't blame Windows... I flashed mine with Windows 10 and worked wonders.
Also... could it be that PC isn't USB 3.0? Perhaps system.img transfer is stopped somewhere during the copying phase?
Thanks, but actually the first time I tried it I did the adb devices command and authorised my pc on the phone. When I connect and do adb devices now it shows the string of numbers code for the device. However, still can't get past "waiting for device"
My pc has both usb 3 and usb 2 ports. Tried on all of them and with various different cables including the asus issued ones, all to no avail.
Can u post a pic of your flashtool folder?
Sent from my Nexus 7
Here is a snap of my platform-tools folder and cmd window
Did you manage to find a solution to this?
I updated the zenfone 2 via OTA to the latest system update.
Ive read and downloaded all relevant files to install the pre root img from the correct sources.
Now when I hold power + vol up. I can see the droid on its back. I choose the RECOVERY option and press power button to select.
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
All the correct drivers are installed into Windows 7, the phone asks me to allow RSA key connection to laptop.
Ive tried the flash tool installer 1.0.7 with phone connected and system img (renamed) and still nothing.
Anyone got any ideas?
Ive factory reset twice in a row and allowed debugging.
Ive placed the (renamed) system.img into the fastboot folder and tried the open command with line ' fastboot flash system system.img' and the reply is usually unable to read system.img or device waiting.
Ive installed the latest android sdk develppment kit and still unable to root using this pre root image.
Im familiar with android and how to follow instructions on rooting, but this zenfone 2 is mind boggling.
Thanks for reading. I know its someone else post. I didnt want to start a fresh post with the same dilemma.
Any advice on whats going wrong would be appreciated.
tsam19 said:
When phone reboots it goes to droid icon and says installing system upgrade.................then error appears! No recovery mode!
Click to expand...
Click to collapse
Hit power and vol up again, just really quickly. Don't hold it, just press and let go. Sometimes it takes several attempts.
hkdmjack, yes your right managed to do it at last.
Cheers
Hi guys, I am facing quite a difficult problem at the moment.
My friend has "accidentally" attempted to use an Asus Zenfone 5 rooting method to root his zenfone 2 550ML.
When I received it to take a look at it, I instantly noticed that I could not get into fast boot (or droidboot). I expected to see usual droid with text on the left side and also expected to be able to select from a number of options using the volume keys (i have some past experience), but instead am met with this solid usb logo. One like this: h ttp://zenfo ne-blog-forum.2 8820.n7.nabble.c om/file/n4 5/P_20140728_051139 .jpg (remove spaces)
I did some research, and found that there were many "bricked" zenfone 5's which were stuck on this usb logo, however this zenfone 2 can start up normally and be used throughout the day normally. Only when I try to enter fast boot, by either ADB commands or by power + volume up, I cannot get past the usb logo.
I have linked up the ZenFone to my computer, and confirmed that ADB devices correctly lists the device (I have usb debugging enabled), however, when I try to go to fast boot and am met with the usb logo, my computer does register and detect the phone, however, under device manager it has a yellow triangle with the device named "" MOOREFIELD". When the ZenFone 2 is in this usb logo state, I cannot access any fast boot commands. I am quite stumped at the moment.
Any help please? By the way, I use a windows 8.1 computer with usb 3 ports. However, I have tested using different cables, and on a windows 7 laptop with usb 2 ports, still to no avail. Should I try and update the firmware using Asus' software? Or is there a better solution?
Thanks
Edit: My friend claims that he did not see at any point in time, the flashing on the zenfone 2 start. He was faced with a "<waiting for devices>" or something similar message, telling me that the phone was not fully in fast boot yet. If I can get it into fast boot, I am sure I can reflash the custom stock onto the phone, and most issues will be resolved.
same error
i have the same error by my zenfone2 after update
please help
amohammadiazar said:
i have the same error by my zenfone2 after update
please help
Click to expand...
Click to collapse
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
pkvk9122 said:
Could you specify which update you did? From your computer? Or via Asus update on ur phone?
Click to expand...
Click to collapse
my orginal firmware is CN and i wanted to change to WW mode i tried by pc .... now when i conect phone t pc it want moorefeild driver for conection and i dont have those ,,
Whenever I try to flash system.img it gets stuck on "writing 'system'..." and just hangs there. I have left it for over half an hour and it still didn't work. Does anyone know a solution to this problem?
Hey guys,
So after a while without any responses, I headed over to Asus customer service to receive a very unhelpful reply.
I gave up hope of finding an answer online and so I decided to take a leap of faith by updating the firmware via the Asus Update app on the phone.
I upgraded from 2.14 to 2.15 and miraculously fastboot seemed to have restored itself. I am not sure whether or not every single update restores fastboot, or whether the update to 2.15 does, but I'm glad that it has been fixed.
My previous problems of being unable to detect fast boot devices has been resolved. Hopefully others who have experienced the same issue can find this post helpful.
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Bglamb said:
Hi folks,
I previously managed to get Cyanagenmod installed on my HTC One X but since made a mess of it trying to get a stock ROM on there (to unlock my SIM). I have since given up on getting a stock ROM back on there and am now trying to get Cyanogenmod back on there, but I have hit some problems.
I have CWM on there and my PC can see the phone in Fastboot, but not via ADB (which I am trying to use to 'push' the ROM on there so I can install it). My PC (Win 8.1) is giving me a "device descriptor request failed" when connecting to USB when on the boot menu, and is showing up just as "One" in device manager when I load CWM. However neither of these situations are allowing my computer or ADB to recognise the SD card.
I have tried 'mounting' it in CWM, updating drivers through device manager, installing Sync (and uninstalling/reinstalling it), installing HTCDriver_4.10.0.001.msi all to no avail.
Does anyone have any advice to get my PC to recognise my phone or otherwise get a customer ROM installed (if there is another way.)
Thanks in advance all.
Click to expand...
Click to collapse
Flash Philz 5.15.9 recovery use it to mount sd card then to copy the rom you need then flash recovery for your rom for CM12 is one for CM11 is other and for Sense is third. For sense rom you can use Philz 5.15.9. And for the new layout is fourt recovery
Thanks!
I couldn't find it so I downloaded a newer version, but it didn't work, so I looked for longer and found a version, but that wouldn't even boot. In the end I used openrecovery-twrp-2.1.7, which did let me mount the SD and install the ROM.
Then I got stuck on the loading screen, but I discovered I needed to just flash a boot.img (which wasn't in either of the guides I was following, for some reason?!) and now I'm all up and running.
Thank you kind sir!
Hello wonderful helpful android wizards out there! I humbly seek your help.
I recently purchased an unlocked HTC M8 AT&T and had it unlocked so I could use my prepaid carrier (Simple Mobile). I have two issues I would like help with:
1) I cannot get a gps lock at all. I have made sure the device is in high accuracy mode and I have tried downloading and refreshing aGPS data via the GPS status app.
2) I am trying to upgrade to lollipop using the provided RUU file on the HTC website:
http://www.htc.com/us/support/htc-one-m8/news/
I am currently running 4.4.2. I was hoping that upgrading to the latest firmware might solve my GPS problem as a bonus, though I obviously want lollipop anyway to just generally be up to date. HTC sync manager works fine, but when I run the RUU file, it says the phone is not connected. I have tried the PB99IMH solution posted here that seemed to work for many people:
http://forum.xda-developers.com/show....php?t=1928439
The roadblock I have hit is that I cannot copy the zip file onto my Android. I keep getting the error "The device has either stopped responding or has been disconnected." I can copy other file to the phone just fine. I tried fiddling with the permissions of the file, but I honestly don't really know what I'm doing with those.
So those are my problems. I would greatly appreciate any assistance.
While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.
Tachi91 said:
While in fastboot/hboot mode. Is your device recognized?
Where you have adb installed just open up a command prompt and do "fastboot devices" ... If your device's serial number shows up then it's being recognized. If not then your drivers are not installed or not recognized.
Click to expand...
Click to collapse
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.
semantik said:
Thank you for your response.
I never explicitly installed adb. I have sync manager on my computer, and I can see adb.exe in my processes. I tried to open up the command prompt and typed "fastboot devices" while my phone is in fastboot usb mode and nothing showed up. When I tried to run the RUU file while the phone was in fastboot, i never got beyond the "verifying information on your android phone. please wait..." part.
EDIT: I would also like to point out that sync manager doesn't recognize my phone in hboot or fastboot, thought it does recognize it normally.
Click to expand...
Click to collapse
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.
Tachi91 said:
It not being recognized while in the bootloader via the HTC Sync app is normal.
You could flash an RUU from the phone itself. Simply copy the rom.zip to your sdcard and go into the bootloader it'll see it and flash aslong as its named properly.. ie 0PB6IMG.zip or something in those lines.
To get the rom.zip while the RUU is open go into your task manager and right click the ruu process and go to file location. The only zip in there thats ~2Gbs is the rom.
Click to expand...
Click to collapse
Ok, i finally got the update to work, but I am still having GPS issues. Any ideas?
I am also having GPS issues. Everything else on the device works fine, it just never finds any satellites. Any help or updates would be nice.
I'm having GPS problems as well. I'm on CM12.1. It used to work fine, but I've been playing with it trying to get LTE to work, and somewhere in there, my GPS stopped locking.