Develop Bugs

[Q] How to recover RECOVERY?

Hi guys!
Today I tried to get the rooted desire with Android 2.2 with unrevoked 3.21
Previosly I updated to 2.29.405.2 SW
When I run the unrevoked it (desire) freezed on "waiting for root" step. Desire freezed in boot progress (white screen with HTC logo on it)
I removed battery and inserted it again. But I cant boot it, desire freezes on the same white screen with HTC logo.
I can HBOOT, but when I go to recovery menu my device goes to reboot and freez.
So it seems that unrevoked spoiled my recovery and I do not know hot to fix it.
Please guide me, the working solution will be donated $20
--------------
Radio version: 5.11.05.27.
SPL/hboot version: 0.93.0001.
product: bravo.
mid: pb9920000.
security: on.
build-mode: ship.
Device model is not SAPPHIRE - flash old/new disabled.
This device does not have s-off nor eng hboot.
-------------
Thanks!

Flash a stock RUU and try again, you can get 2.29.405.2 from my signature. Remember to use a gold card if you had to in the past

How can I flash the RUU without access to recovery?

You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.

3722 said:
You should flash it via fastboot.
Hold the back button and turn on your phone to enter FASTBOOT, then connect your phone to the pc with the usb cable and then run the ruu.
Click to expand...
Click to collapse
Did it as you said, result is the same
After the successful flash procedure thru RUU device went to reboot and freezed at the same white screen state.
Recovery is still unavailable to get into.

Now I will try to get the logged data thru Android SDK.
This thing is really mess me up =( I'm phoneless.
You, guys, are the one and only hope.

I have installed SDK, but I cant see anything in adb logcat but "waiting for device", thogh my device is conneted via fastboot usb.
Any clue?

I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)

Latty said:
I had that same issue, and it turns out it was a problem with the earlier version of clockworkmod (2.5.0.1) that had that issue, where freezing occurred at the HTC splash screen.
Try unrevoked again, with the 2.5.0.7 image here:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.0.7-bravo.img
Make sure you select the image when you start unrevoked.
It might fail a few times (freezing at splash), but if it does, just pull the battery and keep trying....eventually it'll manage to go through.
Good luck =)
Click to expand...
Click to collapse
Latty, how can I run unrevoked with a desired image if I cant boot the phone to get it recognized by unrevoked?

you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).

waebi said:
you have to start the flasher without the phone being connected, then you should be able to select the image (top left of window).
Click to expand...
Click to collapse
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.

hellt said:
yes found it, but when I connect my phone via Hboot usb or fastboot usb - unrevoked does not recognize the connected device.
Click to expand...
Click to collapse
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.

droidzone said:
Follow the unrevoked guide to install the drivers. Also uninstall HTC drivers before that.
Click to expand...
Click to collapse
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.

hellt said:
Already done it. Installed drivers from unrevoked package. But still my phone doesnt get recognized by unrevoked.
Click to expand...
Click to collapse
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..

droidzone said:
It still is a driver issue.
Start from scratch..
Remove all HTC Drivers
Reboot
DC from internet
Connect phone in two modes-Android, Fastboot
It should get recognized but drivers shouldnt be installed and you should be prompted for driver location. If you arent prompted, get Device Manager, uninstall the driver which recognized the device.
Now install Unrevoked drivers as per guide.
Phone should be recognized..
Click to expand...
Click to collapse
Ok, thanks will do it now.
But one more question, should it be recognized from hboot usb mode with "Android Bootloader interface" driver, or from fastboot mode?

Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work

droidzone said:
Cant confirm that without my phone..
But, I believe drivers would recognize it in both..And seperate drivers too..
A small tip..If you have dual boot, try Unrevoked in another OS in which you havent installed HTC. Should work
Click to expand...
Click to collapse
Faced with problems
1) I uninstalled HTC Drivers.
2) plugged phone and deleted Bootloader interface device then Boot Interface device.
3) rebooted
4) disconnected from internet
5) plugged and powered device and got Bootloader Interface driver installed without a single promt!!! And Boot interface as well.
So I had no chance to manually set the path to the drivers. And unrevoked still doesnt see the device =(
It turns out that I should try another OS???
PS and the key point, should it be recognized in hboot mode or unrevoked only works with booted to OS devices only?

Not really..But that's the easy way out..
Difficult to show you what exactly to delete..
Mostly these are driver clashes..When you uninstall the driver you should tick the option to delete the driver from system.
Try again and you know you've succeeded when it doesnt find any driver installed, and asks you for the location, when you can choose the unrevoked drivers..

Hm, I cant find any options prompting to delete driver from the system... But I will look into more carefully.
ADDED
Found it, trying now.

Tried, was promted to specify the path to the drivers, installed again and with no luck =( Unrevoked doesnt see the device.
I will try it tomorrow on another PC and with another OS.
Thanks for help, I really appreciate this, and I hope we will find a solution.
PS. Is this problem called USB brick?

cant get ADB or MTB drivers to work, fastboot is fine

I have 2 htc one x's both were updated to the 3.18 (4.1.1) firmware OTA
The black one connects fine, drivers were easy to install. Fastboot, ADB, and storage all work
The white one works in fastboot, but ADB and MTB will not work. The device shows up as unrecognized device in windows 8 device manager and when I plug it in a popup says there was an error with this device. I've tried so many times to manually update the drivers, but to no avail. Even if I install the same driver as the black phone I will get an error 10 in device manager unable to start device.
I haven't tried a hard reset, it's my wife's phone and she cares more about her apps than the latest firmware, custom Roms, or root. But if I'm missing something simple or anyone else has been down this road before I would like to know the fix, at least to get mass storage working.

dudemaaan said:
I have 2 htc one x's both were updated to the 3.18 (4.1.1) firmware OTA
The black one connects fine, drivers were easy to install. Fastboot, ADB, and storage all work
The white one works in fastboot, but ADB and MTB will not work. The device shows up as unrecognized device in windows 8 device manager and when I plug it in a popup says there was an error with this device. I've tried so many times to manually update the drivers, but to no avail. Even if I install the same driver as the black phone I will get an error 10 in device manager unable to start device.
I haven't tried a hard reset, it's my wife's phone and she cares more about her apps than the latest firmware, custom Roms, or root. But if I'm missing something simple or anyone else has been down this road before I would like to know the fix, at least to get mass storage working.
Click to expand...
Click to collapse
Well, are they both endeavoru ?

desmond1303 said:
Well, are they both endeavoru ?
Click to expand...
Click to collapse
No I thought I posted this in the evita section. My mistake

[Q] Trying to get HBOOT drivers installed on Windows 7

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

GPS lock and Lollipop problems

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.

S-offed and unlocked bootloader via Sunshine...now I can't get TWRP installed...

As the title says, I am stuck here. I CANNOT get ADB to detect my M9 after I type fastboot reboot bootloader or fastboot reboot download...not sure which one I am even supposed to use though tbh, as I cannot find a even half decent guide for this device...I found the download one on the normal M9 page and the bootloader command on TWRP's page for this device. Not that it matters, as neither works as my device isn't detected and they both hand on 'waiting for device'. I have uninstalled and reinstalled about every damned usb driver I can find, manually installed them, used installers, different cables, different usb ports. rebooted my phone and my PC over and over, etc. I am about to pull my damned hair out here lol.
Anyone have any experience with this or a link to a guide for this specific piece of locked down peice of crap?

Welp...after 7 hours of fiddling...it randomly worked. I did literally nothing. Just tried adb reboot download again. And it rebooted and accepted the flash...I suspect there was a weird driver installation issue with windows 10...but I'll probably never know.

I know this is fixed but this post is simply an FYI for others that may have trouble.
I've had trouble instelling TWRP. It would randomly give: the command is not recognized or some sort error message.
*****Before beginning, find your device's firmware number by booting to Download mode. You can do this by restarting your phone and before it begins to reboot, hold the volume down button. Once in the black screen, look for something that says Firmware or "3.37.305.7" The last 4 digits will be different depending on your country and device carrier. This firmware info specifically will tell you which version of TWRP you need to download and which version of SuperSU you'll need. Example, I run a US Verizon phone so I needed TWRP 3.0 or above and SuperSu 2.64 (not anything higher than that). Using the wrong TWRP and/or SuperSU caused my phone to brick to a white screen with red lettering. To fix it, I had to reflash back to stock and then try again. (unfortunately, which combination of the two you'll need is something you'll have to search for as I don't have an exhaustive list. But I highly recommend you verify before flashing the recovery)***********
For me I fixed it by:
- Ensure USB Debugging is enabled on the phone,
- re-downloading the HTC M9 drivers,
- Downloading Android Studio Bundle 145.3
- Searching my computer for "ADB.exe" and found it in "C:\Users\7\AppData\Local\Android\sdk\platform-tools" Your location may be different as I'm running Win 7. They key is that you have to find the exact folder where adb.exe is located and move your TWRP recovery file there.
That's the only way I was able to get TWRP to flash to my phone.

inorite said:
I know this is fixed but this post is simply an FYI for others that may have trouble.
I've had trouble instelling TWRP. It would randomly give: the command is not recognized or some sort error message.
*****Before beginning, find your device's firmware number by booting to Download mode. You can do this by restarting your phone and before it begins to reboot, hold the volume down button. Once in the black screen, look for something that says Firmware or "3.37.305.7" The last 4 digits will be different depending on your country and device carrier. This firmware info specifically will tell you which version of TWRP you need to download and which version of SuperSU you'll need. Example, I run a US Verizon phone so I needed TWRP 3.0 or above and SuperSu 2.64 (not anything higher than that). Using the wrong TWRP and/or SuperSU caused my phone to brick to a white screen with red lettering. To fix it, I had to reflash back to stock and then try again. (unfortunately, which combination of the two you'll need is something you'll have to search for as I don't have an exhaustive list. But I highly recommend you verify before flashing the recovery)***********
For me I fixed it by:
- Ensure USB Debugging is enabled on the phone,
- re-downloading the HTC M9 drivers,
- Downloading Android Studio Bundle 145.3
- Searching my computer for "ADB.exe" and found it in "C:\Users\7\AppData\Local\Android\sdk\platform-tools" Your location may be different as I'm running Win 7. They key is that you have to find the exact folder where adb.exe is located and move your TWRP recovery file there.
That's the only way I was able to get TWRP to flash to my phone.
Click to expand...
Click to collapse
Hi! I'm looking for ways to unlock the bootloader of my verizon's M9. Have been searching here but yet to find any success. Seeing your comment here, i thought you might be able to direct me to a useful thread. Thanks.