Root htc desire a8181 stuck on htc logo

sargodhianhawk · Dec 30, 2014

when i press switch button to turn on my htc desire a8181 it stuck on htc logo and vibrates 7 times but i can acess to hboot factory reset didn't solve problem when i go to recovery mode it restart and again get stucked & vibrates its hboot setting is Bravo pvt4 ship s_off
HBOOT_0.93.0001
microp_051d
touch panel_synt0101
radio_5.09.05.30_2
Aug 10 2010 17:52:18

Hadron · Dec 30, 2014

I'm sorry, but there's nothing you can do: 7 vibrates on startup indicates a motherboard failure.

sargodhianhawk · Dec 30, 2014

Hadron said:
I'm sorry, but there's nothing you can do: 7 vibrates on startup indicates a motherboard failure.

but before this problem often my phone while using any app or game restart automaticaly and stuck on htc logo and vibrate 7 times.but at that time i pulled the battery out and restart it and it started normally but now i have tried reset many time and get tired of pulling battery in and out it does not starting.I think this problem can be solve because i can access hboot(by pressing switch and volume down button) and red coloured fastboot by pressing switch and back button

Hadron · Dec 30, 2014

I wish you were right, but I'm afraid that to me this just sounds like a problem that is getting worse. If the problem is temperature related you might get it booted again by letting it really cool down before reinserting the battery (it's usually PVT1 handsets that have that rather than PVT4, but if it's crashing while running apps that's a possibility), but at some point this will fail permanently, if it hasn't already. We've seen a lot of these over the years, and honestly it is hardware, not software, and the best you can hope for is a temporary fix.

If you want to try something you could try reflashing with a ROM Upgrade Utility, loading a complete new set of software. The 2.3 Upgrade RUU from shipped-ROMs should work on most Desires (otherwise we need to know what network the phone was on and see whether we can find one that is new enough). The actual RUU is a .exe inside that zip file: download to a PC, check the md5 sum to ensure that you got a good download, unzip, connect the phone to the PC, put it in fastboot mode, then run the ruu .exe on the PC. Please note though that if the phone glitches during the flash and corrupts a vital partition that really will be game over, and if you use that RUU you won't be able to try a Froyo (android 2.2) one later if it fails.

sargodhianhawk · Dec 30, 2014

Hadron said:
I wish you were right, but I'm afraid that to me this just sounds like a problem that is getting worse. If the problem is temperature related you might get it booted again by letting it really cool down before reinserting the battery (it's usually PVT1 handsets that have that rather than PVT4, but if it's crashing while running apps that's a possibility), but at some point this will fail permanently, if it hasn't already. We've seen a lot of these over the years, and honestly it is hardware, not software, and the best you can hope for is a temporary fix.

If you want to try something you could try reflashing with a ROM Upgrade Utility, loading a complete new set of software. The 2.3 Upgrade RUU from shipped-ROMs should work on most Desires (otherwise we need to know what network the phone was on and see whether we can find one that is new enough). The actual RUU is a .exe inside that zip file: download to a PC, check the md5 sum to ensure that you got a good download, unzip, connect the phone to the PC, put it in fastboot mode, then run the ruu .exe on the PC. Please note though that if the phone glitches during the flash and corrupts a vital partition that really will be game over, and if you use that RUU you won't be able to try a Froyo (android 2.2) one later if it fails.

respected

Hadron said:
I wish you were right, but I'm afraid that to me this just sounds like a problem that is getting worse. If the problem is temperature related you might get it booted again by letting it really cool down before reinserting the battery (it's usually PVT1 handsets that have that rather than PVT4, but if it's crashing while running apps that's a possibility), but at some point this will fail permanently, if it hasn't already. We've seen a lot of these over the years, and honestly it is hardware, not software, and the best you can hope for is a temporary fix.

If you want to try something you could try reflashing with a ROM Upgrade Utility, loading a complete new set of software. The 2.3 Upgrade RUU from shipped-ROMs should work on most Desires (otherwise we need to know what network the phone was on and see whether we can find one that is new enough). The actual RUU is a .exe inside that zip file: download to a PC, check the md5 sum to ensure that you got a good download, unzip, connect the phone to the PC, put it in fastboot mode, then run the ruu .exe on the PC. Please note though that if the phone glitches during the flash and corrupts a vital partition that really will be game over, and if you use that RUU you won't be able to try a Froyo (android 2.2) one later if it fails.

i am very new to android devices i had also not rooted my device i have read a lot about installion of roms on internet but not tried until now.I have dwnloaded milwid 14 rom but i didn't know how to install a rom some people said that i can't install a rom without rooting my device and for rooting the device the phone must start for usb debugging and my phone is stuck so sir please brief me because reflashing a new rom is only the hope left that could may solve the problem

Hadron · Dec 30, 2014

They are correct: you need to get the phone running with a stock ROM before you can root, and you need to have a custom recovery installed before you can flash a ROM, which is normally installed as part of rooting. If the phone were already "S-Off" (security off) you could install the recovery now and then the ROM, but if the top of the bootloader screen says "S-On" you need to get it booting before you can do anything else.

Your best bet for rooting this device is this guide. What this does is tells you how to use a tool called "revolutionary" to bypass the security (making the phone S-Off), which lets you install a "custom recovery". Once you have the custom recovery installed you can use it to flash unofficial software zips, such as the Mildwild ROM you have downloaded (basically put the ROM .zip on the SD card, boot the phone into hboot, select recovery, then use recovery to factory reset then install the ROM).

But this won't help with your current problem. The "7 vibrates" is happening before it's even loaded the bootloader, which happens before the Android ROM is loaded, so changing ROM will not make any difference to this. An RUU package (the one I linked or another one from that site, if there is another that will run on your phone - see below) will replace all of the software: the ROM and the lower-level firmware (bootloader, recovery, radio firmware), so if it were any sort of software problem that would fix it.

As for RUUs, these need to contain at least as new a software as the phone currently has - they won't let you downgrade - and also need to match the branding of your phone. So if it was sold through a carrier with their branding then you need an RUU for that network. The RUU will check your phone's current software and "customer id" and will not run unless they match. That is why I suggested the 2.3 RUU, since that works for many different brandings, but if you know the phone's branding, or perhaps list all of the information from the hboot screen, I can see if I can identify a different one that might work.

sargodhianhawk · Dec 31, 2014

Hadron said:
They are correct: you need to get the phone running with a stock ROM before you can root, and you need to have a custom recovery installed before you can flash a ROM, which is normally installed as part of rooting. If the phone were already "S-Off" (security off) you could install the recovery now and then the ROM, but if the top of the bootloader screen says "S-On" you need to get it booting before you can do anything else.

Your best bet for rooting this device is this guide. What this does is tells you how to use a tool called "revolutionary" to bypass the security (making the phone S-Off), which lets you install a "custom recovery". Once you have the custom recovery installed you can use it to flash unofficial software zips, such as the Mildwild ROM you have downloaded (basically put the ROM .zip on the SD card, boot the phone into hboot, select recovery, then use recovery to factory reset then install the ROM).

But this won't help with your current problem. The "7 vibrates" is happening before it's even loaded the bootloader, which happens before the Android ROM is loaded, so changing ROM will not make any difference to this. An RUU package (the one I linked or another one from that site, if there is another that will run on your phone - see below) will replace all of the software: the ROM and the lower-level firmware (bootloader, recovery, radio firmware), so if it were any sort of software problem that would fix it.

As for RUUs, these need to contain at least as new a software as the phone currently has - they won't let you downgrade - and also need to match the branding of your phone. So if it was sold through a carrier with their branding then you need an RUU for that network. The RUU will check your phone's current software and "customer id" and will not run unless they match. That is why I suggested the 2.3 RUU, since that works for many different brandings, but if you know the phone's branding, or perhaps list all of the information from the hboot screen, I can see if I can identify a different one that might work.

so i can not flash a rom & flashing rom is also not the solution of this problem and you said that this ruu will solve the problem but sir i did not know anything about this ruu and please brief me in detail how do i solve the problem with this ruu.I had gone to the link of this ruu which you told above but at that link there was a long list of this ruu i think that it is the second last named "HTC_Desire_Android_2.3_Upgrade.zip" in the list which you suggested that it work on mostly htc desires so i am downloading this and sir you tell me what should i do after downloading it and how do i solve the problem with this ruu

Hadron · Dec 31, 2014

Post number 4 in this thread (the one with the link) tells you how to use it. Note though that I didn't say this would solve it: I said that it would solve any software problem, but that this is hardware.

It's possible that if the failure has corrupted the system software this may get it working temporarily, but the underlying problem will still be there and it will fail before long. But that's the best case. It's more likely that it won't make any difference, and quite possible that it will fail during the installation due to the problem the phone has, maybe leaving you unable to even get into the bootloader. If you want to try this, make sure the phone is cold (but not damp!) before you start because your problem sounds like it might be thermal in origin.

sargodhianhawk · Dec 31, 2014

Hadron said:
They are correct: you need to get the phone running with a stock ROM before you can root, and you need to have a custom recovery installed before you can flash a ROM, which is normally installed as part of rooting. If the phone were already "S-Off" (security off) you could install the recovery now and then the ROM, but if the top of the bootloader screen says "S-On" you need to get it booting before you can do anything else.

Your best bet for rooting this device is this guide. What this does is tells you how to use a tool called "revolutionary" to bypass the security (making the phone S-Off), which lets you install a "custom recovery". Once you have the custom recovery installed you can use it to flash unofficial software zips, such as the Mildwild ROM you have downloaded (basically put the ROM .zip on the SD card, boot the phone into hboot, select recovery, then use recovery to factory reset then install the ROM).

But this won't help with your current problem. The "7 vibrates" is happening before it's even loaded the bootloader, which happens before the Android ROM is loaded, so changing ROM will not make any difference to this. An RUU package (the one I linked or another one from that site, if there is another that will run on your phone - see below) will replace all of the software: the ROM and the lower-level firmware (bootloader, recovery, radio firmware), so if it were any sort of software problem that would fix it.

As for RUUs, these need to contain at least as new a software as the phone currently has - they won't let you downgrade - and also need to match the branding of your phone. So if it was sold through a carrier with their branding then you need an RUU for that network. The RUU will check your phone's current software and "customer id" and will not run unless they match. That is why I suggested the 2.3 RUU, since that works for many different brandings, but if you know the phone's branding, or perhaps list all of the information from the hboot screen, I can see if I can identify a different one that might work.

so it w

Hadron said:
Post number 4 in this thread (the one with the link) tells you how to use it. Note though that I didn't say this would solve it: I said that it would solve any software problem, but that this is hardware.

It's possible that if the failure has corrupted the system software this may get it working temporarily, but the underlying problem will still be there and it will fail before long. But that's the best case. It's more likely that it won't make any difference, and quite possible that it will fail during the installation due to the problem the phone has, maybe leaving you unable to even get into the bootloader. If you want to try this, make sure the phone is cold (but not damp!) before you start because your problem sounds like it might be thermal in origin.

so it will also n

Hadron said:
Post number 4 in this thread (the one with the link) tells you how to use it. Note though that I didn't say this would solve it: I said that it would solve any software problem, but that this is hardware.

It's possible that if the failure has corrupted the system software this may get it working temporarily, but the underlying problem will still be there and it will fail before long. But that's the best case. It's more likely that it won't make any difference, and quite possible that it will fail during the installation due to the problem the phone has, maybe leaving you unable to even get into the bootloader. If you want to try this, make sure the phone is cold (but not damp!) before you start because your problem sounds like it might be thermal in origin.

my device is same as i bought it .i have made no changes to it uptil now.i have not rooted it once.is this ruu need no driver and for installing it i have to only connect my htc to pc via usb cable while fastboat open by pressing switch and back button. if i flash rom through this ruu then it will erase the original rom and there will be no way to came to the original rom and if ruu doesn't work then i will also loose the original room yes or not?if yes then is there any way to save the original rom are you sure sir that it is motherboard problem and ruu will not solve it .if it is motherboard problem then what is the price of new motherboard which is suitable to this htc desire a8181

Hadron · Dec 31, 2014

I don't think you need to install anything else first. If it doesn't find the phone maybe install HTC Sync (to install drivers). Otherwise yes, all you need to do is connect to PC when in fastboot mode and run the RUU .exe on the PC.

There is no way to back up the current rom without rooting, which you cannot do in this state.

The ruu will replace the phone's software completely, even the bootloader. There is no way back, and if it fails you will at best be in the same state you are now in, at worst the phone may not even respond to USB or let you into the bootloader (it depends on what part of it fails). In event of failure your only option is probably to try again. Note that if it does fail it's almost certain that the reason it fails is the same reason the phone is in its current state.

I am absolutely sure it's a motherboard problem. There is a chance that the ruu might get the phone working temporarily, though it is more likely that it will not. There is no chance that it will actually fix the problem - if you get the phone booting again it will fail again, probably soon, and sooner or later it will fail completely. We've seen this problem many times before (though it was more common in the early devices than later ones like yours).

sargodhianhawk · Dec 31, 2014

Hadron said:
I don't think you need to install anything else first. If it doesn't find the phone maybe install HTC Sync (to install drivers). Otherwise yes, all you need to do is connect to PC when in fastboot mode and run the RUU .exe on the PC.

There is no way to back up the current rom without rooting, which you cannot do in this state.

The ruu will replace the phone's software completely, even the bootloader. There is no way back, and if it fails you will at best be in the same state you are now in, at worst the phone may not even respond to USB or let you into the bootloader (it depends on what part of it fails). In event of failure your only option is probably to try again. Note that if it does fail it's almost certain that the reason it fails is the same reason the phone is in its current state.

I am absolutely sure it's a motherboard problem. There is a chance that the ruu might get the phone working temporarily, though it is more likely that it will not. There is no chance that it will actually fix the problem - if you get the phone booting again it will fail again, probably soon, and sooner or later it will fail completely. We've seen this problem many times before (though it was more common in the early devices than later ones like yours).

sargodhianhawk · Dec 31, 2014

Hadron said:
I don't think you need to install anything else first. If it doesn't find the phone maybe install HTC Sync (to install drivers). Otherwise yes, all you need to do is connect to PC when in fastboot mode and run the RUU .exe on the PC.

There is no way to back up the current rom without rooting, which you cannot do in this state.

The ruu will replace the phone's software completely, even the bootloader. There is no way back, and if it fails you will at best be in the same state you are now in, at worst the phone may not even respond to USB or let you into the bootloader (it depends on what part of it fails). In event of failure your only option is probably to try again. Note that if it does fail it's almost certain that the reason it fails is the same reason the phone is in its current state.

I am absolutely sure it's a motherboard problem. There is a chance that the ruu might get the phone working temporarily, though it is more likely that it will not. There is no chance that it will actually fix the problem - if you get the phone booting again it will fail again, probably soon, and sooner or later it will fail completely. We've seen this problem many times before (though it was more common in the early devices than later ones like yours).

i connected my phone with the pc runing windows 8.1 pro and run ruu.exe but it give error 120:low main battery power but my phone battery was fully charged i recently a moment ago removed the charger after this error i again plug the charger and the notification light was green(means battery is full)then i pulled the battery out for a minute and replaced it again and then again connected the charger and the notification light was green again .then i connected it again with pc and again this low battery error appear.please sir help me what to do now why this is happenig?

Hadron · Dec 31, 2014

I don't know why it is doing that. The RUU will check that the battery has a minimum charge level before running because if it were to run out of power while updating the phone it could cause serious problems. It might be that because of the hardware problems the phone is unable to report the battery voltage correctly to the PC.

You could test that theory if you wanted. This guide, in particular the second post, will tell you how to set up the "fastboot" command on your PC (I'm not a Windows user, but assume it will work with 8.1). Once you have the "fastboot" command working, you can use the command "fastboot getvar all" to get information about the phone. That ought to include the battery voltage - if it's unable to retrieve a value for that, or gives a very low or nonsensical one, that would identify the problem (for a fully charged battery it should report about 4100-4200 mV, while a bit over 3600 mV means the battery is completely empty).

However, if it is reporting an invalid voltage I cannot think of anything you can do about it. And if it isn't then I've no idea why the RUU is reporting low battery. So either way this wouldn't let you fix it, it would just be testing an idea about why you are getting this error message.

sargodhianhawk · Dec 31, 2014

Hadron said:
I don't know why it is doing that. The RUU will check that the battery has a minimum charge level before running because if it were to run out of power while updating the phone it could cause serious problems. It might be that because of the hardware problems the phone is unable to report the battery voltage correctly to the PC.

You could test that theory if you wanted. This guide, in particular the second post, will tell you how to set up the "fastboot" command on your PC (I'm not a Windows user, but assume it will work with 8.1). Once you have the "fastboot" command working, you can use the command "fastboot getvar all" to get information about the phone. That ought to include the battery voltage - if it's unable to retrieve a value for that, or gives a very low or nonsensical one, that would identify the problem (for a fully charged battery it should report about 4100-4200 mV, while a bit over 3600 mV means the battery is completely empty).

However, if it is reporting an invalid voltage I cannot think of anything you can do about it. And if it isn't then I've no idea why the RUU is reporting low battery. So either way this wouldn't let you fix it, it would just be testing an idea about why you are getting this error message.

my phone is running android 2.1 (elair) so can i try ruu froyo?.may be it would not give any error if you agree then give me suggestion that which ruu froyo i should select from the list which will be suitable to this phone

Hadron · Dec 31, 2014

Yes, you can try a Froyo RUU. What country/region was it first bought in and was it bought through a carrier/does it have a network logo on the splash screen during booting? The RUU will check this information too, and only run if it matches, so we need this information in order to suggest one you could try.

If you don't know, what is the software information on the hboot screen? A quick web search on the build number might identify the carrier or region.

sargodhianhawk · Dec 31, 2014

Hadron said:
Yes, you can try a Froyo RUU. What country/region was it first bought in and was it bought through a carrier/does it have a network logo on the splash screen during booting? The RUU will check this information too, and only run if it matches, so we need this information in order to suggest one you could try.

If you don't know, what is the software information on the hboot screen? A quick web search on the build number might identify the carrier or region.[/QUOT

Hadron said:

Yes, you can try a Froyo RUU. What country/region was it first bought in and was it bought through a carrier/does it have a network logo on the splash screen during booting? The RUU will check this information too, and only run if it matches, so we need this information in order to suggest one you could try.

If you don't know, what is the software information on the hboot screen? A quick web search on the build number might identify the carrier or region.

Click to expand...

it is made in taiwan and bought this 2nd hand from a seller

Hadron · Dec 31, 2014

Unfortunately they are all made in Taiwan. Is there a network logo when it boots up, and what country are you in?

Otherwise, if you can list all of the information from the hboot screen I can try to work it out. Or the software information from "fastboot getvar all" would help (especially the "cid" information), but if you don't have fastboot set up then just the information from the top few lines of the hboot screen (above the menu of options) should suffice.

It is surprising it is still on Eclair: almost all would have been upgraded to Froyo back in 2010. And the radio version you quoted in your first post is actually a Froyo radio (actually the hboot version also corresponds to Froyo now that I think of it). If there's no sign of network branding you could try RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe from shipped-ROMs. That's for English language handsets that were not branded to a specific network. Worst that will happen is that it will refuse to run with a "cid error" ("customer id" = region and/or carrier the phone was originally sold to).

sargodhianhawk · Jan 1, 2015

Hadron said:
Unfortunately they are all made in Taiwan. Is there a network logo when it boots up, and what country are you in?

Otherwise, if you can list all of the information from the hboot screen I can try to work it out. Or the software information from "fastboot getvar all" would help (especially the "cid" information), but if you don't have fastboot set up then just the information from the top few lines of the hboot screen (above the menu of options) should suffice.

It is surprising it is still on Eclair: almost all would have been upgraded to Froyo back in 2010. And the radio version you quoted in your first post is actually a Froyo radio (actually the hboot version also corresponds to Froyo now that I think of it). If there's no sign of network branding you could try RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe from shipped-ROMs. That's for English language handsets that were not branded to a specific network. Worst that will happen is that it will refuse to run with a "cid error" ("customer id" = region and/or carrier the phone was originally sold to).

are you talking about sim card networks?now a days i have inserted no sim card in it.i had inserted the mobilink jazz and warid sims 2 months ago when it was working properly but now there is no sim inside it there is only sd card of 8GB in it.there is no network logo when it boots up i am in Pakistan i have written all information from hboot in 1st post other than menu of option on hboot screen.i have made no changes to this phone since i bought this and it is written on its box that it is android 2.1 eclair.And in fasboot(by pressing switch and back button) i have same hboot information and menu of options( which are bootloader,reboot,reboot bootloader and power down) and i did not know how to find cid from fastboot.Can you tell me how can i find cid and try the froyo ruu and i did not know anything about this fastboot setup but few days ago i downloaded a zip folder inside which were four files named adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll and fastboot.exe but when i opened fastboot.exe and adb.exe a window like command prompt black colured window appear with a sudden system error that error said that "the program can't start because AdbWinApi.dll is missing from your computer.Try reinstalling the program to fix this problem"this error occur while opening both these exe file.Sir please tell me is this fastboot setup about which you are talking.And plz tell me how can i find this cid to try this froyo rru which may helped me

Hadron said:
Unfortunately they are all made in Taiwan. Is there a network logo when it boots up, and what country are you in?

Otherwise, if you can list all of the information from the hboot screen I can try to work it out. Or the software information from "fastboot getvar all" would help (especially the "cid" information), but if you don't have fastboot set up then just the information from the top few lines of the hboot screen (above the menu of options) should suffice.

It is surprising it is still on Eclair: almost all would have been upgraded to Froyo back in 2010. And the radio version you quoted in your first post is actually a Froyo radio (actually the hboot version also corresponds to Froyo now that I think of it). If there's no sign of network branding you could try RUU_Bravo_Froyo_HTC_WWE_2.10.405.2_R_Radio_32.44.00.32U_5.09.05.30_2_release_142828_signed.exe from shipped-ROMs. That's for English language handsets that were not branded to a specific network. Worst that will happen is that it will refuse to run with a "cid error" ("customer id" = region and/or carrier the phone was originally sold to).

Hadron · Jan 1, 2015

OK, the box says 2.1 but it's almost certainly been updated since then.

It's not the SIM's network, unless the phone is locked to the original network still. The phones are originally sold to particular carriers or particular regions, and it's that rather than what SIM is in it that determines the CID. Shipped-ROMs do have a HTC-Asia RUU that might work, RUU_Bravo_Froyo_hTC_Asia_WWE_2.13.707.1_Radio_32.44.00.32U_5.09.05.30_2_release_143921_signed.exe, but again that's only a guess (the radio version matches what you currently have, but that's all I have to go on).

As for installing fastboot on Windows, I've never done that myself: I use both Linux and Mac, but not Windows. I would guess from what is said in post 2 of the ADB FAQ thread that you unzip the mini-SDK, then open a terminal (command prompt), change directory to the folder you unzipped it into, then run the commands from there. So if you unzipped it into C:\sdk-tools as suggested there I'd try something like:

(connect phone via USB when in fastboot mode)
(open command prompt on PC and type the following)
cd C:\sdk-tools
fastboot getvar all

and hopefully because you are running the command from the directory that contains the dlls it will find them. The printout you will get in the terminal window if the "getvar all" command is successful will tell you the CID, and should also tell you the battery voltage (which I suspected earlier might be the problem with the other RUU).

sargodhianhawk · Jan 2, 2015

Hadron said:
OK, the box says 2.1 but it's almost certainly been updated since then.

It's not the SIM's network, unless the phone is locked to the original network still. The phones are originally sold to particular carriers or particular regions, and it's that rather than what SIM is in it that determines the CID. Shipped-ROMs do have a HTC-Asia RUU that might work, RUU_Bravo_Froyo_hTC_Asia_WWE_2.13.707.1_Radio_32.44.00.32U_5.09.05.30_2_release_143921_signed.exe, but again that's only a guess (the radio version matches what you currently have, but that's all I have to go on).

As for installing fastboot on Windows, I've never done that myself: I use both Linux and Mac, but not Windows. I would guess from what is said in post 2 of the ADB FAQ thread that you unzip the mini-SDK, then open a terminal (command prompt), change directory to the folder you unzipped it into, then run the commands from there. So if you unzipped it into C:\sdk-tools as suggested there I'd try something like:

(connect phone via USB when in fastboot mode)
(open command prompt on PC and type the following)
cd C:\sdk-tools
fastboot getvar all

and hopefully because you are running the command from the directory that contains the dlls it will find them. The printout you will get in the terminal window if the "getvar all" command is successful will tell you the CID, and should also tell you the battery voltage (which I suspected earlier might be the problem with the other RUU).

i have done all the process same as you told but after giving cammand its written that waiting for device and nothing happened i wait for 3,4 minutes and nothing happen

frosthax1 · Jan 4, 2015

i have a working fastboot folder.it was made for the htc one sv but fastboot is fastboot.assuming you know how to use proper commands this is the most easiest installation of fastboot ever just extract into a folder named fastboot on your desktop.then you go inside folder hold right shift and right click and youll see an option open command prompt here.this will give you the correct prompt to start typing adb and fastboot commands.hope this helps you on your quest.also make sure you have the drivers installed for your phone if it cant connect and your on fastboot-usb it prolly doesnt have drivers installed.did you get an error device has malfunctioned usb error?i dont have the desire so this is a speculation atm but this should be a generic problem not phone specific for why it wont connect unless you do have drivers installed and like hardon says its hardware related.it may not work with anything.

edit upload failed but sounds like fastboot is working so not needed

nicka3200 · Jan 4, 2015

Hadron said:
I'm sorry, but there's nothing you can do: 7 vibrates on startup indicates a motherboard failure.

Hadron was absolutely right in his first post. I've never heard of as Desire booting after 7 vibrations. It's a credit to his commitment to these forums that he's provided 2 pages of support since then.

sargodhianhawk · Jan 8, 2015

frosthax1 said:
i have a working fastboot folder.it was made for the htc one sv but fastboot is fastboot.assuming you know how to use proper commands this is the most easiest installation of fastboot ever just extract into a folder named fastboot on your desktop.then you go inside folder hold right shift and right click and youll see an option open command prompt here.this will give you the correct prompt to start typing adb and fastboot commands.hope this helps you on your quest.also make sure you have the drivers installed for your phone if it cant connect and your on fastboot-usb it prolly doesnt have drivers installed.did you get an error device has malfunctioned usb error?i dont have the desire so this is a speculation atm but this should be a generic problem not phone specific for why it wont connect unless you do have drivers installed and like hardon says its hardware related.it may not work with anything.

edit upload failed but sounds like fastboot is working so not needed

when i connect my phone to pc while fastboot open a balloon apear at task bar said that usb device not recognize but i have installed latest sync manager from their site and driver also

frosthax1 · Jan 8, 2015

are you on windows 8.1? unfortunately that is a windows 8.1 bug.i got so tired trying to fix that issue i went back to windows 7 64 bit.works fine each time now

sargodhianhawk · Jan 11, 2015

frosthax1 said:
are you on windows 8.1? unfortunately that is a windows 8.1 bug.i got so tired trying to fix that issue i went back to windows 7 64 bit.works fine each time now

dude you were right it got connected with pc running windows xp and on windows xp i try to updated my phone to "HTC_Desire_Android_2.3_Upgrade" via ruu file but it failed in radio updating and give 152 error and i got stucked at black screen with htc written on it and there was one triangle at each corner with ! mark and then i tried again (2 to 3) times ruu file but same thing happen so i disconnect my phone and next day i pick up phone press it switch button but nothing happen then i connect it via charger and pc but at that time also nothing happen even its notification lights not glows(when it connected to pc or charger) and nothing happen by switch button while it connected to pc or charger

Root htc desire a8181 stuck on htc logo

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Spacecorp test pilot

Newbie

Android Enthusiast

Android Expert

Newbie

Android Enthusiast

Newbie

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads