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?

[Q] Help with ADB....Question

I am trying to get ADB to work so I can do the unlock bootloader. ADB recognizes my phone while booted up with usb debugging enabled, but when I reboot to fastboot, it does not recognize it.
I've tried different drivers, uninstalling and reinstalling.... no luck.....
Is there anyone that is knowledgeable in this area to assist me? Is there any kind of IRC channel available to get real-time answers?
Please help,
Thanks,
Bob

i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.

diablonyc2 said:
i am in the same boat. Using windows 7(64 bit). Cannot get the phone recognized in boot loader mode.
Click to expand...
Click to collapse
Yeah, im on 7 64 bit also..... i've tried disabling digital driver thing at bootup...
device manager see its just fine.... I can access it with adb while the phone is booted up.... as soon as I reboot to fastboot screen the phone cannot be seen by adb devices..... still shows up just fine with no ! in device manager....
... is there anyway to push a stock image and load a factory stock image from the stock recovery? says it needs to be in /cache folder.... i tried pushing a stock image there but it tells me access is denied.... i tried enabling root.... says root not available on production builds..... im lost....

I just tried it on my xp machine and it worked just fine..... weird.. something with 7 64 bit? i tried pda net drivers, samsung, samsung naked 1.7.... all said they were working fine....

adb is for android or recovery
fastboot is for bootloader
adb won't recognise the device when it's in fastboot mode.
Try:
Code:
fastboot devices
And you don't need adb to unlock the bootloader, the command is:
Code:
fastboot oem unlock
So not entirely sure why you're chasing adb...

I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit

j1mmyg88 said:
I am in the same boat, what happens for me is that fastboot doesnt even recognize the device. So all in all I can't oem unlock my device.
Using win7 64bit
Click to expand...
Click to collapse
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.

copkay said:
The usual recommendation (and what worked for me) is to install PDANet first, just for the drivers. Then fastboot will see your device. You can remove PDANet afterwards and the drivers will remain.
Click to expand...
Click to collapse
fyi - this is what I did, with 64 bit windows 7 - the driver install didn't complete 'til I actually connected the GN in fastboot mode, then win7 installed the driver and I was able to run fastboot successfully.

fastboot usb not connected

good afternoon friends my htc one x not recognized on any pc connected the USB cable and just starts charging the battery and I made a mistake and now WIPI mobile system is to the home screen (HTC quietly brilliant) that I do I'm desperate I would appreciate if you help me a lifetime. to excuse my English

We need some more info.
Did you unlock bootloader at htcdev?
Did you install cwm recovery?

TToivanen said:
We need some more info.
Did you unlock bootloader at htcdev?
Did you install cwm recovery?
Click to expand...
Click to collapse
4.1.2 aokp if I come from I suddenly stopped working I have installed v2.1.7 TEAM WIN RECOVERY PROJECT

Can you access recovery or bootloader screen? (hold volumedown + power)
Sent from my HTC One X

TToivanen said:
Can you access recovery or bootloader screen? (hold volumedown + power)
Sent from my HTC One X
Click to expand...
Click to collapse
if I can and I can also access the recovery but when you connect the phone to the pc does not recognize usb fastboot

Latest drivers installed? Phone in fastboot mode? (should say fastboot usb)

TToivanen said:
Latest drivers installed? Phone in fastboot mode? (should say fastboot usb)
Click to expand...
Click to collapse
it matters that the USB cable is not the original phone? I have installed the new drivers on the pc but the pc does not flinch when I connect the phone. load only

Does
Code:
fastboot devices
return anything?

Drivers installed?

TToivanen said:
Does
Code:
fastboot devices
return anything?
Click to expand...
Click to collapse
I do not understand the problem is that the pc does not recognize the phone and therefore does not give me the usb fastboot think

elwilliam said:
I do not understand
Click to expand...
Click to collapse
Write fastboot devices to fastboot command prompt. Do you even know what fastboot is?

TToivanen said:
Write fastboot devices to fastboot command prompt. Do you even know what fastboot is?
Click to expand...
Click to collapse
if it is placed fastboot folder in local disk c fasboot inside the folder with cmd Habro connected mobile device fastbott put me appear a series of commands but which is not to give

htc one x not found on pc when connected via usb
elwilliam said:
if it is placed fastboot folder in local disk c fasboot inside the folder with cmd Habro connected mobile device fastbott put me appear a series of commands but which is not to give
Click to expand...
Click to collapse
Hi, I have the same problem as you. I treid root my one x and now, it has clockworkmod on it, but no back up, no stock rom and no rom on the phones hd. I can confirm that in command prompt the device is found, but the phone is not visible on my computer/usb wise for me to put a rom/files onto the phone so I could get a rom on it and make it work again. Right now my phone is just an expensive brick. I tried doing the recovery option but says failed due to low power, the dman thing was plugged in all day and would not even turn on at first. Can anyone help me? Thanks and sorry for adding to your original thread/problem post.
Cheers

Ate you charging using USB connected to your computer or outlet? Try outlet.
Sent from my One X using xda app-developers app

If you have clockworkmod older than 5.8.4.0, you should update it. Then you can charge from recovery and mount the drive as USB to copy ROMs on.

Just know that cheap USB cables, although looking solid may not be good enough to transfer data. THe phone detects this and defaults to a non-data enabled mode. Get a different USB cable and try again.

Fastboot Not Working and CWM Not Installing

Hello, I'm having some problems with my HTC One X.
When trying to send commands to the phone while it is in fastboot, cmd says "waiting for device" and doesn't change.
My bootloader is unlocked and CWM Recovery is installed although when I try and install one of the 4 ROM's I have on my phones internal storage the installer looks like it's working until it gets to around 20% and then says it is complete. When the device restarts it gets stuck on the "HTC quietly brilliant" screen. I am however still able to mount the phone and put files onto it through CWM. I have tried to use RUU and this just gives an error about USB not connected.
If you think you can help, thank you and if you need to know anything else I will try and give you as much information as I can.
Thanks,
Andy

Here's a checklist for you:
Phone in fastboot mode
Correct drivers installed
ADB/fasboot up to date
What does 'fastboot devices' return?

Yeah, it was all working earlier today but it just seemed to stop. fastboot devices returns
"c:\Fastboot>fastboot devices
c\:Fastboot>"
TToivanen said:
Here's a checklist for you:
Phone in fastboot mode
Correct drivers installed
ADB/fasboot up to date
What does 'fastboot devices' return?
Click to expand...
Click to collapse

What OS is your computer running? Does it say FASTBOOT USB on phone display?

I have a macbook pro as my main computer but all things to do with rooting I do on a windows desktop.
This display says fastboot usb but all fastboot commands do nothing and it still doesn't show up in fastboot devices.
TToivanen said:
What OS is your computer running? Does it say FASTBOOT USB on phone display?
Click to expand...
Click to collapse

Reboot pc and phone if you haven't already.
You could try it with your mac, there's plenty of guides out there on how to setup.
Make sure to use sudo!!

Tried it on mac like you suggested, still no devices listed. And installations still only get to around 20%.
Do you think it's bricked?
TToivanen said:
Reboot pc and phone if you haven't already.
You could try it with your mac, there's plenty of guides out there on how to setup.
Make sure to use sudo!!
Click to expand...
Click to collapse

Are you using the original delivered HTC usb cable ?

Mr Hofs said:
Are you using the original delivered HTC usb cable ?
Click to expand...
Click to collapse
No, I lost it ages ago. I have tried several cbales now though and they were all working fine yesterday.

Alwsys use the original. Try again then

Mr Hofs said:
Alwsys use the original. Try again then
Click to expand...
Click to collapse
Tried a friends original cable for the same phone, still nothing. Anything else that you think might work?

[Q] Can Not get ADB and Fastboot drivers to install

Windows 7 x64
Galaxy Nexus i515, BROKEN SCREEN, USB DEBUGGING WAS NOT TURNED ON. The phone is completely stock I just turned it on and used it until I broke my screen. Screen lock is on.
I have been trying to access my phone, using Fastboot, to wipe it before I send it in for warranty. I can not seem to do this at all. It seems that I can not install the drivers because I have not enabled USB debugging. Is this true? I have been following this guide : http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/2/ When i go to manually install the drivers, from SDK, I get, "The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure that it is designed to work with Windows for x6-based systems." I then tried the driver from Samsung and got the same response.
So then I hold VOL+ _ VOL- and Power and tried to install the drivers for Fastboot with the same outcome as above. Also when I boot in Fastboot mode the drivers that are installed make my phone a modem. The driver is called, "SAMSUNG Mobile USB Modem." I can not get this to change.
So to summarize I can not get the ADB Drivers to install, because I do not have USB Debugging enabled, that in return will not allow me to install Fastboot Drivers because when I plug the phone in the computer sees it as a Modem.
Any suggestions? I am just trying to erase the info on my phone I have given up all hope of recovering any data.
Thanks,
qualm

USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.

beekay201 said:
USB debugging drivers/interface have nothing to do with fastboot drivers/interface. What's a screen lock?
a manta wrote this.
Click to expand...
Click to collapse
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.

_qualm_ said:
I meant a screen pattern lock. When you wake up the screen you have to connect the dots in a certain pattern before your screen unlocks and you can use the phone.
As far as, USB debugging drivers/interface having nothing to do with fastboot drivers/interface, then what am I doing wrong? I can not get my computer to see my phone as an android device.
Click to expand...
Click to collapse
I know what a screen pattern lock is.
Uninstall all drivers, reboot pc.
Assuming device is off: press power+vol up+vol down, until you feel the vibration. Wait 2 secs or so. Device will be in fastboot mode.
Read this thread, i say again, READ this thread, obviously start with the first post! - http://forum.xda-developers.com/showthread.php?t=1812959

Thanks for the link. I read it and followed instructions for installing the drivers. Here is what I did:
1.Uninstalled all drivers
2.Rebooted my PC
3.Downloaded these Drivers, as suggested: http://forum.xda-developers.com/showthread.php?t=1379875
4.Followed these instructions, on how to install the driver without windows trying to find one automatically: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
Everything seemed to go well under the Device Manager, when I plug my phone in in fastboot mode, it shows Android Phone -> Samsung Android Interface. This is way better than what I had before, when it was showing up as a Modem. Now when I try to use fastboot.exe and I type "fastboot devices" nothing shows up. I reset the computer and replugged in my device, in fastboot, and the same thing nothing shows up in fastboot.
Thanks for you help.

Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.

beekay201 said:
Did you miss the part about having to feed windows the same driver again, when connecting the device for the first time, in FASTBOOT MODE?
a maguro wrote this.
Click to expand...
Click to collapse
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.

Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus

W8 a sec, do you even have your bootloader unlocked???
You said you're running stock, so that should have been my first question, because to unlock your bootloader through the usual way, you need to confirm a dialog on the device... which in your case, doesn't have a working screen.
_qualm_ said:
Not sure if I understand what your asking.
I followed all of the steps here: http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 I connected the phone booted normally and let windows find a driver so that the driver reads Portable Devices -> Galaxy Nexus. Then I unplugged the Nexus and booted it in fastboot mode and plugged it in. Next I followed the directions to install the Universal_Naked_Driver, in fastboot mode. I can not install the driver for ADB because I can not enable USB Debugging with my broken screen.
Thanks Again.
Click to expand...
Click to collapse
....
Lets see:
That post shows how it's done, correctly. (I think, from what i've read)
pay attention to part 3)
3)
NOTE:
- The method described here can be used to install the "Samsung Galaxy Nexus ADB Interface" driver as well as the "Samsung Galaxy Nexus Bootloader Interface" driver.
- Differences between the two procedures. One is done with the phone booted up normally and "USB Debugging" is enabled, and the other is done when the phone is in fastboot. I will cover the "USB Debugging" part here.
Click to expand...
Click to collapse
then...
We will now install the two drivers that efrant talked about in his post.
A) (FOR ADB - WHEN RUNNING ANDROID OS):
Enable USB debugging on your device
- Goto Settings > Developer Options > Check "USB Debugging"
- Connect device, manually update driver to Naked driver by 1wayjohny, done. On 4.2 and above, you'll need to confirm that you accept the host's (your pc) RSA key.
B) (FOR FASTBOOT - WHEN RUNNING FASTBOOT MODE)
boot into fastboot mode - power off phone and hold vol up + vol down + power
Click to expand...
Click to collapse
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.

Pirateghost said:
Why is it so difficult for people to understand that USB debugging has nothing to do with anything outside the booted OS?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I am learning this ^. I am having trouble getting my computer to see my phone, in fastboot mode. All of the instructions that I have read start with installing drivers for ADB, which requires the phone to be USB debugging mode, and then the drivers for fastboot. So I thought my trouble was, since I can not install the drivers for ADB, and that I was having trouble with all of my drivers, that it was probably the fact that my phone can not be put into USB debugging mode. I now realize that USB debugging has nothing to do with fastboot, as fastboot is before the OS is booted. I am still just having trouble with my fastboot driver and seeing my phone with fastboot.exe.

beekay201 said:
W8 a sec, do you even have your bootloader unlocked???
Both for A) and B), you need to do the "Update drivers manually" part!
Right now, your only option is B), that is to use fastboot to either:
- Flash stock images.
- To get your data back, boot a custom recovery (which won't require the RSA key confirmation for ADB) from fastboot, then use ADB to pull your /sdcard/ or whatever.
Click to expand...
Click to collapse
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.

_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus

Pirateghost said:
No. Fastboot should be able to see your device if the proper drivers are installed. Fastboot is REQUIRED to unlock the bootloader
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
If you used odin to flash something, that will unlock the bootloader. Flashing a section of edited param using OMAP flash will also unlock the bootloader.
Beamed from my Maguro.

I also have the same problem with my galaxy C5.
_qualm_ said:
No my bootloader is not unlocked. Is this the reason that my phone is not detected by fastboot.exe? Do I need to unlock my bootloader?
I have been trying option B, as I know this is my only option. I have been doing the "Update drivers manually" part I even tried on another PC with windows 7, to no avail. What ever I seem to do I can not see my device in fastboot.exe.
Click to expand...
Click to collapse
My galaxy C5 is also not recognized as a bootloader interface while in fastboot mode, after installing all the drivers correctly. Samsung usb driver v1.5.63.0 makes the changes i think, and it makes it as a modem instead of bootloader. maybe the solution is i have to manually update the driver of that modem into bootloader, right click on the modem in device manager and change it's driver into bootloader of your phone, maybe it works. I will try it this way.
Let me know if this solution has worked for someone.
Thanks