Tried to flash Carbon rom. Fastboot flashed boot.img then when I tried to flash rom in recovery it failed. So when I tried to go back to fastboot mode and flash another boot.img to restore a nandroid my phone isn't being recognized. Interestingly, when I go back into recovery my phone is recognized. But I need to install the boot.img first but can't d/t phone not being recognized.
Any help out there? Where's Mr. Hofs when I need him? lol
Used the original cable ?
Not used a usb hub ?
Try it on another windows pc ?
Mr Hofs said:
Used the original cable ?
Not used a usb hub ?
Try it on another windows pc ?
Click to expand...
Click to collapse
Ha! There you are.
Yes, original cable. What you mean by a usb hub? And don't have another PC...
scott62185 said:
Ha! There you are.
Yes, original cable. What you mean by a usb hub? And don't have another PC...
Click to expand...
Click to collapse
Yep hi mate
I mean using a direct usb 2.0 port on the pc ....
Otherwise reboot everything ! And can you erase cache first ?
Fastboot erase cache
What's the exact error ? Waiting for device ......
Mr Hofs said:
Yep hi mate
I mean using a direct usb 2.0 port on the pc ....
Click to expand...
Click to collapse
Okay, I'll try it in a usb port on the back of my computer.
It says, "device driver was not successfully installed" even though it was before I started this whole process.
Also, when I put it into recovery and plug it in, the charging light still does not come on...
scott62185 said:
It says, "device driver was not successfully installed" even though it was before I started this whole process.
Also, when I put it into recovery and plug it in, the charging light still does not come on...
Click to expand...
Click to collapse
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
Mr Hofs said:
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
Click to expand...
Click to collapse
Okay, I'll try that. be right back
Didn't work...
Weird .....
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Mr Hofs said:
Weird .....
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
I had it so fastboot was in blue text...is that wrong?
Okay, changed it so the fastboot is in red text (duh! lol). Tried the whole process and carbon rom still aborted (didn't flash). But at least I was able to apparently flash the boot.img via fastboot. Unfortunately, I still don't see the charging light while in recovery, and I need to leave to go take care of something. I did see it once when it was plugged in on the bootscreen...
scott62185 said:
I had it so fastboot was in blue text...is that wrong?
Click to expand...
Click to collapse
Well there is a text that says "fastboot" and as soon as you connect it to the pc it should turn into "fastboot usb"
What does this command give back
Fastboot devices
Mr Hofs said:
Well there is a text that says "fastboot" and as soon as you connect it to the pc it should turn into "fastboot usb"
What does this command give back
Fastboot devices
Click to expand...
Click to collapse
Should I leave it plugged in w/ the boot screen since that has the charging light on?
It should be in the bootloader where it says
All bootloader info
Here it should say "fastboot usb"
Hboot
Reboot
******* (can't recall)
Power down
Then perform the command
Fastboot devices
Mr Hofs said:
It should be in the bootloader where it says
All bootloader info
Here it should say "fastboot usb"
Hboot
Reboot
******* (can't recall)
Power down
Then perform the command
Fastboot devices
Click to expand...
Click to collapse
So, I had to leave the house and now I'm out and about. I left it plugged in with the splash screen as that enabled the charging light. I hope that was the right decision. I'll check back in tonight when I get home. Thanks!
Sent from my Nexus 4 using xda premium
scott62185 said:
So, I had to leave the house and now I'm out and about. I left it plugged in with the splash screen as that enabled the charging light. I hope that was the right decision. I'll check back in tonight when I get home. Thanks!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
the device won't charge if it is in the bootloader
So, I'm able to get fastboot mode working (flashed boot.img) BUT whenever I try to flash a rom (I've tried Carbon and Slim), it says "installation aborted" [assert failed: getprop ("ro bootloader")]
Any ideas on what's going wrong? Do you guys have advice on which other rom to try and flash?
My hboot is 1.23, by the way.
scott62185 said:
So, I'm able to get fastboot mode working (flashed boot.img) BUT whenever I try to flash a rom (I've tried Carbon and Slim), it says "installation aborted" [assert failed: getprop ("ro bootloader")]
Any ideas on what's going wrong? Do you guys have advice on which other rom to try and flash?
My hboot is 1.23, by the way.
Click to expand...
Click to collapse
Okay, now it's completely dead. I guess I didn't figure it out in time. Do I have any recourse?
Yeh the hboot is to low, we get it charging. Leave it on the charger while the phone is off. We will pick it up on gtalk
Mr Hofs said:
Yeh the hboot is to low, we get it charging. Leave it on the charger while the phone is off. We will pick it up on gtalk
Click to expand...
Click to collapse
Okay, I plugged it back in. But can it charge if it's already dead?
Related
Hey guys, I was flashing a rom on my One x but for some reason it got stuck in a bootloop. After that, I tried restoring to my earlier rom using CWM but I forgot to flash the boot.img from cmd first so it didn't work. After that I tried restarting my phone but it wouldn't turn on after turning off. When I plug in my charger the red light comes up but I can't turn it on. I left it to charge for a few hours but it still won't turn on, the only sign of it working is that it vibrates when I attempt to turn it on. I also tried connecting it to my pc and it senses it but I get no results when I type adb devices in cmd. Can someone please help me with this issue? Thanks!
What can you see in windows device management? Does
Code:
fastboot devices
give you any info?
No, nothing, but when I connect to pc it says installing device software
Oh yeah, I also forgot to mention that it did turn on before and I got into the bootloader but then it turned off again
I mean the device management in the control panel. It should be there if it says something about drivers.
It says MTP USB Device
What ROM are you on?
I was attempting to flash Blade rom when it got stuck in bootloop
MTP should be only available when the phone is booted. I really don't know what is the problem here, sorry.
Ok, Thanks anyway
I just restarted my pc and after running cmd and entering adb devices I get: SH24KW107359 recovery. But the phone is still off. Any ideas?
If the phone vibrates and your computer sees it like MTP that it might be a hardware failure. Contact HTC for further assistance, or try search the forum. I am sure many faced the same problem, and some got it working finally.
I'm no longer getting MTP, it now says E:\
Wait, were you on android 4.0.4 just before you tried flashing Blade?
BlueSingA said:
Wait, were you on android 4.0.4 just before you tried flashing Blade?
Click to expand...
Click to collapse
No, I was not. At least I don't think so. It's my sisters phone so I'm not sure. Why?
I believe that the phone is switched on, but the screen remains off. Try this:
Code:
fastboot getvar all
I tried turning it on and it turns on then it shows the HTC logo, then when I try to get into CMW it shows a dark screen but u can tell its on.
Ok, if your in cwm, from a cmd prompt run:
adb reboot bootloader
That should put you in the bootloader.
From there use fastboot to flash the kernel to boot as you should have done earlier.
When your done just:
fastboot reboot
-SLS-
When I type fastboot devices in cmd i get: SH24KW107359 fastboot. Can I flash a boot.img by using fastboot flash boot boot.img?
Yes, and also reflash cwm. Dl from clockworkmod site and flash using:
fastboot flash recovery nameofthefile.zip
Sent from my HTC One X using xda app-developers app
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
bump
thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?
thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .
ah nice works, thanks. stay with me in case i get stuck again.
thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.
more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?
davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions
finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.
Hi, :cyclops:
I received a second-hand HTC Desire from a family member as my Samsung Galaxy S3 got stolen. The phone won't turn on, I don't know if it had previous problems but if someone could give me a list of things to try, and explain how to perform these things, that'd be great.
Here's some details about the problems and what I've tried:
I have plugged in the phone to a wall charger without a SD card or simcard in the phone. The LED light turns solid orange and stays on, the buttons on the phone light up and remain that way. The screen stays black and the phone makes no sound.
Sometimes if I hold down the power button, it vibrates once and nothing happens.
If I plug it into the pc, the pc registers the phone but nothing else happens.
I have tried battery pulls.
I have also held down the volume down button and power button together, I just get a continuous vibration for about 10 seconds and then nothing
I have tried holding down the power button for an extended period of time, but nothing.
Anything else I could try? Or maybe perform the tasks I have tried differently...
Any help would be appreciated I'm not fond of the alternative phone I would have to use.
Thank you
try pull the battery out for 10 seconds n put back in then press n hold back button then press n hold power button (both same time) see what happens, hopefully it will boot into fastboot. ur vol down button could be dodgy thats why wont boot into bootloader. The led comes on when plugged in and vibrates so thats a good sign. Why it only shows black screen? i dunno. Maybe u just need to flash a ruu. try the back button combo first
jmcclue said:
try pull the battery out for 10 seconds n put back in then press n hold back button then press n hold power button (both same time) see what happens, hopefully it will boot into fastboot. ur vol down button could be dodgy thats why wont boot into bootloader. The led comes on when plugged in and vibrates so thats a good sign. Why it only shows black screen? i dunno. Maybe u just need to flash a ruu. try the back button combo first
Click to expand...
Click to collapse
I tried the back button and power button combo, it vibrated once and then nothing. What next?
JeanFlea said:
I tried the back button and power button combo, it vibrated once and then nothing. What next?
Click to expand...
Click to collapse
Looks to me, like the phone is booting, but the screen isnt displaying anything. Pull the battery, then follow what jmcclue said to get into fastboot. Then setup adb, install this driver, plug the phone into your computer, and run "fastboot devices". See if your phone shows up.
Ok, So I'm downloading and installing these things on my pc and plugging the phone into the pc and doing it from there? Because nothing happens on the phone when I try the fastboot thing.. I'm not sure what these programs are or what they do.
JeanFlea said:
Ok, So I'm downloading and installing these things on my pc and plugging the phone into the pc and doing it from there? Because nothing happens on the phone when I try the fastboot thing.. I'm not sure what these programs are or what they do.
Click to expand...
Click to collapse
Yes. Adb/fastboot are executables which allow your pc to communicate with your device. You need to do this:
-setup adb
-install the driver that i linked
-follow the steps in jmcclue's post above to get your phone into fastboot mode
-plug the phone into the pc
-on the pc open up a command prompt window, and enter "fastboot devices"
-post a screenshot of the output of the command
Chromium_ said:
Yes. Adb/fastboot are executables which allow your pc to communicate with your device. You need to do this:
-setup adb
-install the driver that i linked
-follow the steps in jmcclue's post above to get your phone into fastboot mode
-plug the phone into the pc
-on the pc open up a command prompt window, and enter "fastboot devices"
-post a screenshot of the output of the command
Click to expand...
Click to collapse
The SDK Manager and the driver are both installed, however is there something else I could type in the command window? It says that "fastboot" is not a recognized command.
JeanFlea said:
The SDK Manager and the driver are both installed, however is there something else I could type in the command window? It says that "fastboot" is not a recognized command.
Click to expand...
Click to collapse
Did you completely follow the guide I linked above?
Chromium_ said:
Did you completely follow the guide I linked above?
Click to expand...
Click to collapse
Ok, I went over everything again and made sure I didn't miss anything. This was the output of the command:
HT07CPL02294 fastboot
JeanFlea said:
Ok, I went over everything again and made sure I didn't miss anything. This was the output of the command:
HT07CPL02294 fastboot
Click to expand...
Click to collapse
Aha, my prediction was correct. So the phone is actually booted into fastboot mode, but the screen is not on.
Lets get some more info out of this phone. Run this command and post the outptut "fastboot getvar all"
Chromium_ said:
Aha, my prediction was correct. So the phone is actually booted into fastboot mode, but the screen is not on.
Lets get some more info out of this phone. Run this command and post the outptut "fastboot getvar all"
Click to expand...
Click to collapse
Done.
JeanFlea said:
Done.
Click to expand...
Click to collapse
I would suggest running an RUU. Download it here: http://www.htcdev.com/process/legal_download/152
Let the phone charge for a bit though before you start.
Chromium_ said:
I would suggest running an RUU. Download it here: http://www.htcdev.com/process/legal_download/152
Let the phone charge for a bit though before you start.
Click to expand...
Click to collapse
So I let the phone charge for a while, how long would you suggest? And then I run the RUU. This should work?
JeanFlea said:
So I let the phone charge for a while, how long would you suggest? And then I run the RUU. This should work?
Click to expand...
Click to collapse
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick
Chromium_ said:
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick
Click to expand...
Click to collapse
Thank you so much for your help and patience I will try this. It's busy downloading, the LED on the phone is green so hopefully I won't have to let it charge for too long. I'll let you know if it works.
Chromium_ said:
Yea let a charge for at least an hour. Then run the RUU. I cant guarantee that itll work, but if this doesnt work, I would think that there is some sort of disconnection with a screen cable. In that case, i would suggest dissembling the phone and making sure that all screen cables are connected properly. But hopefully the RUU will do the trick
Click to expand...
Click to collapse
My guess is that who ever had the phone had it s-off and rooted then tried to run a ruu but the wrong one, thats why black screen. I seen this before (bout a year ago) Droidzone wrote a good guide explaining everything and how to fix it blind :cyclops:
My pc makes that sound when I plug in the phone but the HTC sync Manager and the pc doesn't revognize the device, nothing comes up. Will this be a problem?
JeanFlea said:
My pc makes that sound when I plug in the phone but the HTC sync Manager and the pc doesn't revognize the device, nothing comes up. Will this be a problem?
Click to expand...
Click to collapse
Make sure HTC sync isnt running in the background when you run the ruu (open task manager and kill any htc stuff before starting the ruu).
Check once more to see if "fastboot devices" recognizes the phone. If it does try the ruu. The ruu will tell you if it cant detect the phone. If that is the case, i have other solutions
Chromium_ said:
Make sure HTC sync isnt running in the background when you run the ruu (open task manager and kill any htc stuff before starting the ruu).
Check once more to see if "fastboot devices" recognizes the phone. If it does try the ruu. The ruu will tell you if it cant detect the phone. If that is the case, i have other solutions
Click to expand...
Click to collapse
It didn't detect the phone
JeanFlea said:
It didn't detect the phone
Click to expand...
Click to collapse
The ruu didnt detect it? Or fastboot devices?
Hmm, could be because its in fastboot mode. Try this:
-pull the battery then reinsert
-turn the phone on normally (hold power for a second, then release). Wait a few minutes for the phone to boot, then plug it in and try the ruu again.
Hi to all
I have a big problem. My HTC Desire HD is now "dead". So, everything is working normally, just fine, on JellyTime, but this afternoon everything get broken. Suddenly, after the boot animation is finished, nothing happens, the screen is "black". The phone works, because when I connect USB to the computer sound. I can not get into Recovery (Home + Volume Down), can not do anything. I tried to remove the battery, but it does not help. I tried with adb, but there is "error: device not found". So I installed the drivers, asking me activate USB Debugging on the phone, and I can not access the phone.
Do you have any idea how to access recovery mode and install the new ROM?
Please help!
Thanks in advance.
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
JJeamy said:
just turn on your device with press volume down + power to get into the bootloader..then from there you can select recovery
Click to expand...
Click to collapse
I try, but I can't. :crying:
SkipperRi said:
I try, but I can't. :crying:
Click to expand...
Click to collapse
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
I finally managed this problem. I pulled off the battery over the night, and this morning I can booted into the recovery. So, I installed new ROM, all my apps, and now I performed backup to the my PC.
Thanks for help!
Regards.
Again same problem. For few hours everything seems fine, but just now my HTC has "blank" screen... Nothing to do. Again, I can't go to Recovery, nothing... What's going on with this phone?!?!
JJeamy said:
can you explain more cleared about this..?, did you mean your volume rocker is already broken or what else..?
what is the last you know the state or your phone bootloader..?, unlocked with s-on or already s-off..?
and what about the stock RUU..did you had already tried to flashing it through the pc..?
Click to expand...
Click to collapse
How to do this? And, if I do that, will be my phone still rooted after that?
SkipperRi said:
How to do this? And, if I do that, will be my phone still rooted after that?
Click to expand...
Click to collapse
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
JJeamy said:
no..you will lost it
what the state of your phone bootloader..?
unlocked or locked or nothing ?
s-on or s-off ?
hboot - ???
n your phone still can't go to bootloader with press volume down + power..?, is that the new rom you've already installed earlier..already by default it had enabled usb debugging under system settings..?
Click to expand...
Click to collapse
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
SkipperRi said:
No, I can't go to bootloader with volume down+power. About state of phone... S-off, that's I know. The ROM is installed earlier, but today I perform full wipe, and then installed ROM again, not backup/recovery, but fresh install. USB debugging is, as far I know, disabled... What should I do?
Click to expand...
Click to collapse
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
JJeamy said:
did you already try it adb is connected or not..?, just try first with "adb devices" (while the phone is on booting and had a black screen)
anyway why your phone can't go into bootloader by pressing volume down + power..?, is that already broken with your volume rocker..?
what happen if your pull out the battery first just a few minutes..then put in back again..and try it again pressing volume down+power..
Click to expand...
Click to collapse
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
SkipperRi said:
I don't know why can't go into bootloader with volumeD+power... I pulled battery, but everything is same. Can you please explain to me how can I try with adb?
Thank you so much for help!
Click to expand...
Click to collapse
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC.. if not just downloading from here..
and already had installing the latest HTC driver on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
JJeamy said:
i assume that you already had SDK/ADT or adb.exe and fastboot.exe on your PC..
firstly your let the phone is boot like normal..then after you see the black screen..try connecting it to your pc..
then open your SDK folder (place of adb and fastboot.exe) then run cmd and source to your adb folder.. example : if your adb folder is in "C:/android tools/" then you must change source to that folder with typing "cd C:\android tools", now you ready to used it..don't closed it..just let it open
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
if your phone is detected..then you had prompt after that is your phone serial number that on list of attached devices
if success connected..then you can typing "adb reboot-bootloader" or "adb reboot recovery" (all command w/o quote)
Click to expand...
Click to collapse
Thank you so much! I'll go and try right now and let you know what's going on.
JJeamy said:
while your phone already booting n had black screen..then already connecting it to usb on your pc..then firstly try typing "adb devices" to check that's the phone is already connected with adb..
(all command w/o quote)
Click to expand...
Click to collapse
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
lexuz said:
wel on my windows 8 i also get that blank line whre the serial number from the device should be but in my case its connected 'cause i can push files and to adb commands with it.
try to do adb reboot-bootloader and see if if does that
Click to expand...
Click to collapse
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
SkipperRi said:
Hm, I'm also on Windows 8, when I try command: adb reboot recovery then I get error: device not found.
But, when I connect/disconnect phone via USB there is a sound that detect connection...
Click to expand...
Click to collapse
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
SkipperRi said:
Nothing. Here is what I get in CMD:
Code:
C:\adbfastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
What now?!
Click to expand...
Click to collapse
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
lexuz said:
sorry can't help you more its up to the gurus here, try the thread ace think tank here on the forum
Click to expand...
Click to collapse
Thank you anyway...
JJeamy said:
you sure that your pc already had latest HTC driver right and support with your OS..?
if so..maybe that's the usb debugging is not already active on your phone indeed..
because what i know is that just had two option to access your phone again:
1. with your volume down+power to access bootloader of your phone..and you can do it everything from there..
2. with adb command on android home of your phone..
while both option that is doesn't work..i'm sorry..i don't know more how the way to access your bootloader again beside the two way above..
anyway maybe you can try it again like the first way you success go into bootloader with pull out the battery over few hours like before..
and when you've already success flashing new rom again..don't forget firstly to enable it usb debugging from system settings..and connect as charge mode only..
and don't forget to disable fast boot mode too from system settings if you using sense rom
Click to expand...
Click to collapse
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
SkipperRi said:
Thank you anyway...
Yes, I have valid drivers, because before this disaster it was possible to connect phone with PC without any problems.
Have you any idea why the phone go "dead" after few hours working just perfect? Hardware or ROM related issue, what do you think?
I pulled battery out just now, for tommorow morning I giving up, maybe I'll be lucky and again I can with volume down + power booting into Recovery Mode.
Thank you, my friend!
P.S. Do you have any suggestion for some stable and good ROM?
Click to expand...
Click to collapse
i'm not sure about that..until now..what i see is still software related..but i don't know what software exactly had the problem is..
can be from the recovery that you had installed the rom..or else..
to make sure what exactly is.. you must return the phone to the stock..stock bootloader, stock rom and stock recovery too..all back to the stock..with flashing stock RUU while your phone back in normal condition..
you know the forum rule is doesn't give any permission to all member for compare the rom..
Good day!
After searching everywhere in the web and using different methods, I decided to create an account and ask you guys how to solve my problem
Basically, I have a HTC Desire HD phone, this is unlocked, rooted and using cm-Jellytime_42_R11 ROM. I decided to change ROM and go back to Android Revolution. What I did first was I deleted a couple of folders in my clockwork folder, I deleted both backup to free space. Afterwards, I was trying to connect my phone to my laptop but to no avail (it only charged) then I decided to just boot into recovery. After a couple of tries trying to access and going to bootloader/recovery mode it just wont push through. So I decided to normal boot, then the phone won't boot anymore. It just hanged in the Jellytime loading screen.
Note: I removed the battery a couple of too many times since I was trying to boot into recovery.
Thanks in advance to anyone who can help me with this problem
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Gussta said:
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Click to expand...
Click to collapse
no, i couldnt go to Hboot while holding down volume - and power.
The phone gets stucked in the Jellytime loading screen. It just stops. help me please
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
bananagranola said:
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
Click to expand...
Click to collapse
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
richardrip10 said:
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
Click to expand...
Click to collapse
WHen it getts stuck in the roms boot animation, connect usb to the phone and try
Code:
adb devices
Most devices show up via adb during the boot animation.
If the device shows up there, enter
Code:
adb reboot bootloader
then go here and download 4ext recovery.
extract the .img file from the zip. Rename it to recovery.img and place it in your adb directory and enter this whiles in fastboot
Code:
fastboot devices
to make sure your device shows up
then
Code:
fastboot flash recovery recovery.img
after it has successfully flashed reboot to recovery ad try and flash the rom u want.
hope i helped. Click on the thanks buttton.
You can ask if you still have problems.
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
richardrip10 said:
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
Click to expand...
Click to collapse
What recovery were you using before this happened?
mickeyasamoah said:
What recovery were you using before this happened?
Click to expand...
Click to collapse
cwm sir.
richardrip10 said:
cwm sir.
Click to expand...
Click to collapse
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
sorry, it still didn't work. Is this a bricked phone?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
btw, my computer really cant detect my phone. It doesnt make any sound when it is connected through USB. but other devices can be detected by my computer. I tried inserting the usb into a 2.0 and 3.0 usb.
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
hey bro, I actually made it work. problem is when im flashing the recovery, it shows Failed<remote: not allowed>
what should I do?
mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
richardrip10 said:
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
Click to expand...
Click to collapse
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
mickeyasamoah said:
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
Click to expand...
Click to collapse
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
richardrip10 said:
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
Click to expand...
Click to collapse
I am happy i was able to help.
Instead of saying thanks only, you could actually hit the thanks button.
Have a nice day.