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?
Related
Hi, today a have tried to root my htc desire using revoked 2 method. I was unable to install usb drivers. And now i cant even mount desire as hard drive. Computer still reports that device is unknown. I tried different usb ports, 2 different cabels, windows xp and seven. Before everything worked fine. Do you thing it is possible, that i damaged phone, when i plug it out just disconnecting cable?
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
MasDroid said:
Which version of unrEVOked did you try? I seems like a driver issue as you have to install the modified Hboot drivers for unrEVOked in a certain way before unrEVOked will work. If you attempted root with unrEVOked 3.21, did you follow the steps mentioned in thi thread?:
http://forum.xda-developers.com/showthread.php?t=776696
and
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
I used this tutorial http://forum.xda-developers.com/showthread.php?t=788044
and I stuck at 3. point... On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
and after that i am unable to connect desire to pc... no way...seems like something happend with usb driver in phone or i dont know...just i ve tried 3 computers for now and every reports same when I connect usb, that device is unknown
What Hboot do you have?
What is your PVT version? (also check the Bootloader for this info)
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
benefic said:
0.93.0001 and I forgot...I stucked at third point because i got there no option HBOOT USB
Click to expand...
Click to collapse
And your PVT version?
Bravo pvt1 ship s-on
hboot-0.93.0001
benefic said:
Bravo pvt1 ship s-on
hboot-0.93.0001
Click to expand...
Click to collapse
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
MasDroid said:
Ok, thank you for that info.
To tell you the truth, with unrEVOked 3.21, you must install the modified HBOOT drivers for it to work, otherwise it will not work at all.
Please try following this guide as it is definately requied. I asked you above if you had tried going through it, you mentioned that you had only tried using the guide in the first link, but you definately need to have the modified HBOOT drivers installed to proceed.
http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Try what is suggested and let me know if you can proceed past step three after configuring the HBOOT drivers first, as it is a must.
Click to expand...
Click to collapse
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
benefic said:
Well I tried connecting usb cable in bootloader menu but no HBOOT USB PLUG appeared and in device manager i dont have Android 1.0 device. and this is the problem.
Click to expand...
Click to collapse
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
MasDroid said:
Hmm... yes i see what you mean. Unrevoked is fussy regarding drivers. Try the following:
1) Uninstall HTC Sync completely, the HTC Driver Setup, and HTC BMP Driver if present.
2) Reboot and reinstall the HTC Sync software (latest version).
3) Now uninstall HTC Sync Alone. Keep other two (HTC Driver Setup and HTC BMP Driver) installed.
4) Reboot your PC again.
Note: do not connect phone to PC at all and make sure the phone is switched off.
5) Switch your phone to the Bootloader screen. Connect the phone via USB and it should show Fastboot USB.
6) Windows will show the device detection dialog box - at this point, stop Windows from getting the driver from Windows Update, and manually choose the location of the driver as the folder where Unrevoked driver is present.
7) After this is done, diconnect phone again.
8) Go through the unrEVOked guide and connect the phone when advised to.
If this fails, then try unrEVOked 3.22 (in my sig below) and see how that goes and although you have mentioned that you have tried 3 different PC's, you may have to consider trying it on a different OS platform, such as Linux.
Click to expand...
Click to collapse
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
benefic said:
ok, i tried what you suggest, but desire refused any other driver...and keep installing unknown usb device driver
Click to expand...
Click to collapse
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
EDIT:
With the phone connected, try the following afterwards:
Check to make sure that you have USB Debugging enabled on your phone.
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software'. Browse to the folder (extract the zip to the Desktop) i have attached below and see if it installs them.
MasDroid said:
Try downloading the Android SDK: installer_r08-windows.exe
Follow the steps in this video to hopefully get the appropriate USB drivers - http://www.youtube.com/watch?v=N66J6UiN5Pg&feature=player_embedded
Try the following afterwards:
In Device Manager, right-click your Unknown Android device and select 'Update Driver Software' (Make sure you are connected to the Internet to search for available drivers via Windows Update).
Click to expand...
Click to collapse
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
benefic said:
OK, i will try the thing with sdk..i am downloading files right now, but that makes no sense to download any other windows drivers. I think the problem is inside of the phone, because it represents itself like unknown device to any computer with any drivers...if there is a way to restore flash memory or something...well looks like i will have to wait one month for reclamation...how this could happen my god
Click to expand...
Click to collapse
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
MasDroid said:
I agree... it is clearly an HBOOT driver issue or the phone... Windows (PC host) drivers are seperate. I was just running out of ideas really
The only definate way of knowing if it is the device that is causing this issue is if you were to try it on a non-Windows related OS, like Linux and maybe it would work for you using an Ubuntu Live CD.
Click to expand...
Click to collapse
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
benefic said:
well this is good idea...do you think it could also fix the usb issue for windows when i will root my phone in linux?
Click to expand...
Click to collapse
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
MasDroid said:
Yes, because it is not as fussy with drivers as Windows is - with Windows, they have to be properly removed from its cache. With Linux, the phone should be detected ok (unless the phone is at fault).
Here is a simple guide that you can follow:
http://rootmydroid.co.uk/guides/desire/howtolinux-root-your-desire-using-unrevoked-in-linux/
Keep those fingers crossed
Click to expand...
Click to collapse
So, linux didnt work either, system didnt even recognize that anything was plug in. Even crossed fingers dident help Well only last thing I have to ask, if there is any possibility to recover hboot, restore it somehow. Forexample through recovery menu in hboot loader and some kind of .zip file, that i will put to SD card. If not, well I will have to step out to that freezing weather and walk to orange store for reclamation, which I hope would be positive for me, but something telling me it surely will.
I found something about usb unbrick here on xda forum, but is only for root phones
well i found this http://forum.xda-developers.com/showpost.php?p=9056719&postcount=15 i think it could work, just i dont know a way how to discover my CID number..to modify mtd0.img file
ok, i did everything step by step using rageagainstthecage tutorial, but nothing happend at all.
If anyone could help...
Are you able to get into Fastboot?
I suppose running your stock RUU in Hboot won't make a difference then... how about trying the PB99IMG method, which involves renaming the extracted rom.zip file to PB99IMG.zip from your stock RUU, placing this to the root of your SD card and then letting it run from Fastboot mode. This would restore your stock Hboot. You could also try AlphaRev's modified 0.93 HBOOT with S-OFF?
hi,first post on this section . upgraded from the desire bravo,could do with some advice..
purchased a used dhd in good condition,changed housings etc,its running the latest htc 3.12.405.1 sense 3.0 android 2.3.5 .after a good search i realised i would have to downgrade to s-off etc.
my problem is i can't get into fast boot power down volume,pulled battery tried lots of times.
pc will not recognise dhd,installed drivers etc,should be able to sort that one out myself.
but i cant work out why i cant get into fastboot,the phone just restarts
thanks mark
Hi,
Download HTC Sync and install that, that contains all the required USB drivers needed.
As for getting into fastboot, have you disabled HTC "Fastboot"? Its in a setting somewhere. Possibly under Settings>Applications or Settings>Development. Make sure that is unticked.
If you take your battery out & reinsert, hold vol down then press power. That should do it for you. If not, enable USB Debugging and use adb to get into the bootloader with,
Code:
adb reboot bootloader
You will need the SDK or a thinned down adb package. Which you can grab from HERE.
You will need the USB drivers for that to work.
EDIT: Just re-read your post. If you have HTC Sync installed and you still cannot get it detected then there maybe an issue with either the handset or your computer. Check "Device Manager" when its plugged in to see if there is a conflict.
htc sinc was allready on pc from desire bravo,well just the drivers.have tried the htc fastboot uncheck earlier no good,re installed htc sinc as i thought it may be different for dhd,but its not.
pc will not pick up device,says drivers not installed.i know they are as the bravo worked fine.
i had read somewhere that unrooted dhd can be usb bricked,there is a fix by some french chap on here,but i cant do that because cant get into fastboot.
need to get into fastboot first i think,to see whats what,device could allready be s-off dont know.
strange
edit: volume button was not working correctly lol, s-on,now to sort out the drivers,downgrade and flash a nice rom
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)?
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