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?

fastboot mode not working

hi everyone, i'm trying to install CM9 on my LT15i, i've tried using the CM wiki instructions and both the following guides...
androidauthority.com/xperia-arc-lt15i-root-android-4-0-ics-80265/
and
androidforums.com/rezound-all-things-root/506466-scottys-noob-friendly-root-guide-start-finish.html
the phone is already fully unlocked and has CM 7.2.0 anzu installed. i've tried simply using the clockwork recovery mod bootloader to wipe the phone and install CM 9.0.0, but on reboot the phone gets past the boot logo then just shows a black screen, so i assumed i needed to flash an appropriate ROM for CM9; this is where my problem begins.
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone; although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers

WookieInHeat said:
every forum i've read about this process says i must enable usb debugging (done) and "disable fastboot" under settings>power, i do not have a "power" option in my settings and cannot find anything related to fastboot on the phone;
Click to expand...
Click to collapse
There is no such thing. And USB debugging is only required if you want to root stock ROM, every other action can be done without it.
WookieInHeat said:
although i'm not sure this is the problem. when android is running normally and i attempt to list devices with adb.exe on windows, it successfully returns the phone's serial number. when i shut the phone down, hold the menu button and plug in the usb cable, fastboot mode appears to work correctly as the LED comes on blue and "android adb device" appears in the windows device manager (i've tried installing the arc usb/adb drivers from various sources, they all seem to work correctly). but when i attempt to list devices after restarting in fastboot mode, adb.exe says it cannot find any device. fastboot.exe has not communicated with the device whatsoever, but i assumed i might need to get the adb.exe usb daemon/server running correctly first for this to work.
i did this process once already when i installed CM7, it was successful the first time and everything went smoothly. from what i recall i just did exactly as described above and fastboot.exe was able to find the device no problem. but that was a number of months ago, hopefully i'm just missing some obvious step.
cheers
Click to expand...
Click to collapse
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
You do not need ADB server for installing a kernel.
Just open up Command Prompt and install the kernel with command
Code:
fastboot flash boot boot.img
.
Assuming boot.img is in the same folder as fastboot.exe.

Someguyfromhell said:
Drivers, drivers, drivers.
If your phone is in fastboot mode, make sure drivers are installed. Proper drivers.
Click to expand...
Click to collapse
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie

WookieInHeat said:
thanks for the reply someguyfromhell. i've tried every "android adb interface" driver under the sun for the S1 fast boot device that appears in the windows device manager when i put the phone in fastboot. when i try to send any command with fastboot.exe it just hangs at "waiting for device", i've fiddled with this stuff every which way and just cannot get fastboot.exe to see the phone. i've tried switching up the usb ports on this computer, but haven't had the opportunity to try a second computer. you've let me know i'm going in the right direction at least, if i have the same results on a second machine i'll pursue the issue further.
thanks again
wookie
Click to expand...
Click to collapse
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
http://unlockbootloader.sonymobile.com/

Someguyfromhell said:
You need to unlock bootloader, if you want to install CM ROM. Arc S can only have bootloader unlocked via official method, there you can also download the correct driver which you need.
the bootloader is already unlocked, as i said, the phone has CM7 on it currently.
Click to expand...
Click to collapse

No way of installing ROM

I need help getting out of this never ending misery. I'm stuck with my unlocked Desire HD, no ROM, and no idea how to get one working. I can't even get back to stock.
I've been looking for solutions for a week now, but it seems the combination of S-ON, no USB debugging and an unlocked bootloader makes most of them undoable.
I am able to get into boot loader, and the currently installed 4eXT recovery.
See attached file for bootloader screen.
Can anyone help me get my phone to work again? Either by a custom ROM or HTC stock; whatever.
Thanks.

What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.

bananagranola said:
What is the problem? What happens when you install a ROM? If you get stuck on the splash screen read my signature.
Click to expand...
Click to collapse
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.

SageNTitled said:
It gets stuck on the HTC loading screen or on the black screen directly after depending on what I install. Don't I need USB debugging to use fastboot? I'm only getting < waiting for device > when flashing via fastboot.
My device is not listed when using adb devices.
Click to expand...
Click to collapse
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.

bananagranola said:
No. ADB is not fastboot. Access fastboot from the hboot menu. Details in the link in my signature.
Click to expand...
Click to collapse
Yes, I did read your thread. But it doesn't work since it's not getting a connection to the device.
See attached image.

So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.

bananagranola said:
So you're booting into hboot, navigating to fastboot with your volume keys, and selecting it with the power key? If so, and fastboot still isn't getting a connection, I have no idea. Maybe check your cable or your USB port connectivity.
Click to expand...
Click to collapse
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.

SageNTitled said:
Yes. It does say FASTBOOT USB and I can see the device in the Device Manager. I also have the Android SDK Tools as well as the Google USB Driver installed.
I always thought you needed USB debugging on on the phone to get access to the phone's system folders.
Click to expand...
Click to collapse
No, USB debugging (aka ADB) is separate from fastboot. ADB kicks in when you boot the ROM. Fastboot is from the bootloader. Fastboot doesn't access the system's individual folders. It's used to flash entire images.

Not to worry, for I have solved the problem. I was apparently missing a driver that didn't get installed since I was missing USB debugging mode when installing adb and fastboot on my PC.
Going into Device Manager and manually looking up the HTC driver solved it.
Thanks for your time.

Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Sent from my Desire HD using Tapatalk 2

humzaahmed155 said:
Out of interest, did your PC have VMWare Workstation installed? Because on Windows 7 and 8 people are having issues with Android drivers with it installed
Click to expand...
Click to collapse
No, I did not have that installed.

HTC desire in boot loop. PLEASE PLEASE HELP!

My HTC desire 820 keeps restarting itself as it is stuck in an endless boot loop. I have come across threads speaking of the same issue but the solutions don't seem to work on my phone.
My boot loader is locked. When i try to unlock it in fastboot mode, the device doesn't show up on the PC.
I need the boot loader unlocked so that i could push in a custom recovery mode as i cant get into the stock recovery too.
Does anybody have a solution for my kind of problem?
Also, when the phone is in fastboot usb mode, the computer makes a notification sound which indicates it recognizes the phone.
The only thing i can get into is my boot loader and which looks like this now:
***LOCKED***
A51_DTUL PVT SHIP S-ON
HBOOT-3.19.0.0000
OS-3.17.708.3
eMMC-boot 2048 mb
Apr 12 2016, 11:49:54.0
NOTE: I never tried to install a custom ROM. This problem arose on its own for reasons unknown to me. Moreover, my phone is UNROOTED.
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!

themember1993 said:
PLEASE SOMEBODY HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! PLEASE!
I'm clueless!
Click to expand...
Click to collapse
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979

Gibz97 said:
Have you installed the adb/fastboot drivers on your PC?
Sounds like a drivers issue to me.
Try this thread to install the drivers then try communicating with the bootloader again.
https://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?

themember1993 said:
Thank you for replying, friend.
I did what you asked me to do i.e. installed adb/fastboot drivers and then ran the command to identify.
But all i get is this. I have attached a screenshot of the message i'm getting in the command prompt.
What do i do?
Click to expand...
Click to collapse
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx

Gibz97 said:
Still a drivers issue
Try installing HTC Sync Manager from here and try again.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
Click to expand...
Click to collapse
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?

themember1993 said:
I had installed the htc manager again as per your instructions even though i had it on my pc earlier.
HTC sync manager doesn't detect the phone.
Nor does fastboot command in the command prompt.
i have the adb drivers installed as you asked me to install them earlier.
I get the same message "waiting for phone" in cmd. I rebooted fastboot but even that doesn't change anything.
What do i do now? Is it a hardware issue? I do not think it could be a hardware issue because the phone has never undergone physical damage. it just decided to turn itself off one unfortunate day by itself.
Is there another way? another software?
Click to expand...
Click to collapse
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?

Gibz97 said:
Open device manager.
Connect phone to PC. Does the device manager show a new device added?
And BTW why can't you get into the stock recovery?
Click to expand...
Click to collapse
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.

themember1993 said:
When i select "fastboot mode" in the bootloader screen, the PC makes a connection notification sound.
And the device shows up as "Android 1.0" in Device manager.
I have attached a screenshot which shows the same.
Also, when i try any of the options in the bootloader i.e., factory reset, recovery mode, reboot or power down, the device goes back to the endless bootloop and never really lets me do anything.
Click to expand...
Click to collapse
Try downloading usb deview from here. Uninstall all the USB drivers, reinstall them then try again
http://downloads.tomsguide.com/USBDeview,0301-13254.html

Stuck in bootloop and PC won't recognize drivers

Hi,
I recently changed my broken screen and now my phone is stuck in a bootloop. I want to try and flash ROMs but cant because the PC does not recognize the device. I've tried manual installation of drivers in device manager but it said that it cannot find the driver, even though i chose the HTC drivers folder in HTC Sync. So yeah i've tried putting 0P6G(whatever) on the SD card and it doesn't want to install it.
Device details:
Software statusfficial
Locked
m8_ul pvt ship s-on
hboot-3.19.0.0000
radio-1.29.214500021.12g
openDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.401.4
i downloaded the HTC RUU.exe file and copied and renamed the zip file to 0P6G... and tried HBOOT and it didn't work. i've tried looking for the European version with the same radio number but i cant find a working link. Now i want to try flashing but cant, because my PC doesn't recognize the device. And also i tried factory reset and wiping and all that **** it didn't work. I didn't have any CWM or TWRP installed and USB debugging was off.
I have a very basic picture of how this works i'm not a developer and this is why i need your help. I'ts kind of new territory for me.
I'm using Windows 7.
Please help and tell me if you need anymore info i think i gave you everything.(if i didn't, it probably shows the level of noob that i am)
Thank you for your replies!!

Zip name should be 0P6BIMG.zip if you have to use microsd method to install RUU.zip
Here you can get the correct RUU.zip -
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
Zip name should be 0P6BIMG.zip if you have to use microsd method to install RUU.zip
Here you can get the correct RUU.zip -
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
So i tried the SD card method with the file you sent me, it updated in bootloader, but when the phone rebooted it got stuck on starting apps... I tried the same method but in recovery the phone wrote
E:footer is wrong
E:signature verification failed
Installation aborted.
Still no sign of the drivers working. Windows stills sees the phone as an unknown device.

filipm97 said:
the PC does not recognize the device. I've tried manual installation of drivers in device manager but it said that it cannot find the driver, even though i chose the HTC drivers folder in HTC Sync.
Click to expand...
Click to collapse
Just having HTC Sync installed should have installed the drivers.
Is the phone in bootloader-fastboot mode, when connected to PC?
Does the phone show up in Device Manager? Even if just as an unknown Android phone, or something to that effect?

redpoint73 said:
Just having HTC Sync installed should have installed the drivers.
Is the phone in bootloader-fastboot mode, when connected to PC?
Does the phone show up in Device Manager? Even if just as an unknown Android phone, or something to that effect?
Click to expand...
Click to collapse
Yes it shows up in DM as an unknown device and yes i had HTC sync installed. I can access bootloader and fastboot but fastboot doesnt say fastboot-usb. I also clicked ram dump through USB and the computer reacted like a device was unplugged and plugged back in, but it still remains as an unknown device. Ive even tried installing the drivers manually but windows rejects the ones that are in the HTC sync install foldeer

filipm97 said:
I can access bootloader and fastboot but fastboot doesnt say fastboot-usb. I also clicked ram dump through USB and the computer reacted like a device was unplugged and plugged back in, but it still remains as an unknown device.
Click to expand...
Click to collapse
I don't know if there is any different in it saying fastboot versus fastboot-usb or not. Try opening a command prompt (within same directory as fastboot.exe) and do fastboot devices, and see if your device ID is returned. If so, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I've never used the ram dump option. Don't think it will do anything helpful in the current condition.

redpoint73 said:
I don't know if there is any different in it saying fastboot versus fastboot-usb or not. Try opening a command prompt (within same directory as fastboot.exe) and do fastboot devices, and see if your device ID is returned. If so, do fastboot getvar all, and post the result (delete IMEI and serial number before posting).
I've never used the ram dump option. Don't think it will do anything helpful in the current condition.
Click to expand...
Click to collapse
So
-Downloaded SDK tools,
- installed the tools,
- opened a cmd window in platform-tools,
- typed fastboot getvar.
- also fastboot devices.
nothing the getvar was stuck at waiting for device.
Device status in DM under unknown device:
Windows has stopped this device because it has reported problems. (Code 43)
(i dont know if this helps)

filipm97 said:
Device status in DM under unknown device:
Windows has stopped this device because it has reported problems. (Code 43)
(i dont know if this helps)
Click to expand...
Click to collapse
Try right clicking the device under Device Manager. Select the option to update drivers software, if available. Then pick the option to look for the driver (forget what it says exactly) then pick the option to select the driver manually. Pick the option "Android MTP device" or something to that effect. Then after the driver is installed, see if the fastboot commands work.