Related
Hi,
Yesterday I just wanted to restore a CWM-Backup, but came from a ROM, that had no advanced power options (no choosing between "recovery" and "normal" after holding power button and touching "reboot"). So I used Rom Manager to boot into recovery (4ext touch), and used a superwipe script like "every day", Then, i dont know how, the phone turned off, (normally this script just reboots into recovery)
So I wanted to boot into recovery via bootloader by vol. down+ power button: I had have trouble with vol. rocker for 3 months or so, but always made it (with enough pressure) , to boot into bootlader. But now nothing seems to work anymore, i tried it several times but only got it booting and then freezing (caused by fullwipe). Then I removed the plastic rocker to have access to this "micro button" (dont know how to call it) and push it with a pen, but didn´t work, too.
So i began to research, but just found people that had problems with their plastic rocker (seems to be a very well known problem of htc ace) and not this micro buttons. And if I hadn´t full wiped it, i could boot and maybe get into recovery via adb or any apps. :crying:
So my question is: Does anyone know a solution or is there a way to get into bootloader and recovery without vol. down + power or app?
My DHD is rooted and S-OFF,of course :laugh:
THANKS IN ADVANCE !
am facing the same problem my volume down aint working and cant connect my DHD to usb plz plz plz help
SOLUTION
Hey Guys,
solved it myself with adb!!!
Tutorial
Step1: Download & Intall adb
" 2: Connect Phone (turned off) to PC via USB
" 3: open new cmd on pc
" 4. Type "adb reboot recovery" and you get into recovery ! ( and install/restore a new/backed up rom)
Hans_Schlila said:
Hey Guys,
solved it myself with adb!!!
Tutorial
Step1: Download & Intall adb
" 2: Connect Phone (turned off) to PC via USB
" 3: open new cmd on pc
" 4. Type "adb reboot recovery" and you get into recovery ! ( and install/restore a new/backed up rom)
Click to expand...
Click to collapse
I tried the steps to told us about it didnt work "Error : device not found"
Just try to reinstall adb, maybe it also could be a driver problem (?)
I first turned it off by removing the battery for 10 seconds to be sure, that it´s OFF.
Then connected the PC via USB while red notification LED flashes up (!! Be sure to use a USB 2.0 port, NOT 3.0 and NO usb-hub>typical mistake !!) and pressed windows logo on keyboard: type in searchbar "cmd", and right click on "cmd.exe" and select "Run as administrator". Then type in "adb.exe". Possible commands will show up and then type in "adb reboot recovery".
I think it´s just a driver or connection problem, nothing on the phone itself!
Hans_Schlila said:
Just try to reinstall adb, maybe it also could be a driver problem (?)
I first turned it off by removing the battery for 10 seconds to be sure, that it´s OFF.
Then connected the PC via USB while red notification LED flashes up (!! Be sure to use a USB 2.0 port, NOT 3.0 and NO usb-hub>typical mistake !!) and pressed windows logo on keyboard: type in searchbar "cmd", and right click on "cmd.exe" and select "Run as administrator". Then type in "adb.exe". Possible commands will show up and then type in "adb reboot recovery".
I think it´s just a driver or connection problem, nothing on the phone itself!
Click to expand...
Click to collapse
you are right, am facing a problem with the driver, I get the HTC sync installed good and I have the adb but I couldnt make the the pc read it as android it keeps saying its a storage device "mass storage"
So you are able to boot? or please tell me, what the status of your htc dhd is.
I'm facing almost the same problem.
Adb is set right on the pc (have used it before on this phone and on other phones), usb 2.0 on the back, but phone has adb turned off due to ruu, vol down rocker completely detached.
error: device not found
So, what can I do?
So first try to use a pen to push the micro Button.
I suppose, that you can install apps on your current Rom (?), so try "Rom Manager from market use the in-app "reboot into recovery ".
Sent from my HTC Desire HD using xda app-developers app
Hans_Schlila said:
So first try to use a pen to push the micro Button.
I suppose, that you can install apps on your current Rom (?), so try "Rom Manager from market use the in-app "reboot into recovery ".
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
I only have 2 problems with that :
1. my volume button panel is completely detached, so I don't have any button to push
2. phone does not boot up, unfortunately it's stuck into bootloop
Sorry my fault, havent read your Link to your Problem description, but seems to be a very very hard-to-solve-Problem . The phone has so many "damages", that are connected to each other, that the new cable is maybe the only way out; and just by the way, im from Germany , so in my case the only thing, that worked for me was this ADB command.
Sent from my HTC Desire HD using xda app-developers app
Hans_Schlila said:
Sorry my fault, havent read your Link to your Problem description, but seems to be a very very hard-to-solve-Problem . The phone has so many "damages", that are connected to each other, that the new cable is maybe the only way out; and just by the way, im from Germany , so in my case the only thing, that worked for me was this ADB command.
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Well, the phone in question is from Germany, and I'm in Hungary right now.
Actually, I managed to solve almost all of the problems, except for the booting to bootloader one.
It's an easy one, if your volume button works good.
Zirowe said:
Well, the phone in question is from Germany, and I'm in Hungary right now.
Actually, I managed to solve almost all of the problems, except for the booting to bootloader one.
It's an easy one, if your volume button works good.
Click to expand...
Click to collapse
so whats about "adb reboot recovery ?
Hans_Schlila said:
so whats about "adb reboot recovery ?
Click to expand...
Click to collapse
A s I said: error: device not found.
Then I can't help you, sorry. I'm not a developer, but I suppose that there aren't any possible Solutions anymore... But I hope you will be able to find a way!
Sent from my HTC Desire HD using xda app-developers app
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
7.If this is all fine boot into bootloader again.
From bootloader go to fastboot.
Go back to the cmd window on your PC from earlier, type in:
•Fastboot oem lock
Then type:
•fastboot oem rebootRUU
•fastboot flash zip firmware.zip
•fastboot reboot-bootloader
unlock the bootloader again using the Unlock_code.bin you got from HTC:
•fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
stuck in the same place... before unlocking bootloader pc would recognise the phone. now it doesn't... i think were stuck unless a developer helps us
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, remove and reinsert the battery, and plug it into a computer, don't power the phone on, wait and see if the computer detects it, if it does, try "adb devices" to see if it shows up.
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Windows detects an "Android Phone" in Devices but "adb devices" is still empty.
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Some times guys the firmware.zip file once flash does get stuck on the HTC White screen during the exploit just run ADB and continue with the unlocking of your radio. Its safe.
IBeKay said:
i had the same problem but fixed now. The way i did this was to actually take out the hardware for the volume rocker and check if the contacts are all in place. i then booted into bootloader by connecting my phone to a power source (computer or ac) and pressed the volume down button so that it registered. For some reason it seems to register you clicking the button better when its out of the key. Sorry if you don't understand this, I really don't know how to explain the rocker and the keys separately 0_o
Click to expand...
Click to collapse
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
konungr said:
Wooh!!! It worked !!! Thank you very much!!!
For future reference, this is how what I did to complete the root process:
1. Pull off the battery cover, take out the battery.
2. Rip off the label with IMEI and S/N and then use a toothpick or plastic tweezers to pull out the ribbon cable from the volume rocker (see video here: youtube[dotcom]/watch?v=JfatoeWbMRk&feature=player_detailpage&t=143)
3. Press the volume down button on the cable a few times to make sure it clicks then clean the inside of the volume rocker a bit, put the cable back in, and press volume down a few times to test it.
4. Put the battery back in, connect the USB to your computer, hold volume down and press the power button so that it goes into the bootloader.
5. Go into fastboot and continue the rest of the steps from the guide.
Note: if adb doesn't detect your phone then reboot it and enable USB debugging again in Settings > Applications > Development and then reboot into the bootloader.
Thanks to everyone that helped ! :good:
Click to expand...
Click to collapse
glad I helped
konungr said:
Hi, I know there are a lot of other similar threads but none of them have solved my problem.
I ingeniously decided to try upgrading an old Desire HD to Jelly Bean to use while I'm waiting for a new phone that I actually want to be released. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=2221039 successfully until this part:
After I ran "fastboot flash unlocktoken Unlock_code.bin" my phone restarted and now it's stuck on the htc logo. I'm unable to get into the the bootloader by holding volume down while powering the device (though I was having this problem before starting the root process, instead I was using "adb reboot-bootloader" to get into it). I've also tried to leave the battery out for a while. It's not being detected by HTCSync or "adb devices" either.
Anyone have any solutions to this problem? I'm a complete Android noob so please keep it simple (though I have experience with UNIX and the command-line).
Click to expand...
Click to collapse
Hi
I have followed your all steps perfectly... after done i have reboot my desire hd it shows htc screen and goes to qualcom mode...plz tell what should i've to do now
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..
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
I will pay 20 Euros, if someones solution works.
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
cortezthekiller said:
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
Click to expand...
Click to collapse
Thanks a lot, but i have already known this thread.
The guy, B3NJY, with same problem, could not solve it. At least he sent his phone to repair service.
Maybe someone else knows how to unbrick a softbricked wildfire s.?
I flashed a lot and know how to use fastboot etc., ....
Like i said, backlight is working but nothing else.
appyleptiker said:
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
Click to expand...
Click to collapse
I think you flash wrong RUU. Before flash RUU 100% confirm about it. Otherwise you will lost your device. Anyway let's begin...
[WARNING: PLEASE DON'T TRY THIS WITHOUT HAVING GOOD ENOUGH KNOWLEDGE !! BE SURE TO CHOOSE THE RIGHT RUU OR THIS MAY HARM/BRICK YOUR DEVICE !! I AM NOT RESPONSIBLE FOR ANYTHING !!]
Before you start, you will need to set up your computer to properly recognize the device. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync (only for USB drivers). Make sure that HTC Sync is not running in the background when this process is ongoing. To kill that you can use "Task Manager in Windows"
:cyclops: Do step by step: :cyclops:
1. Download the correct RUU for your device from Here and please 100% confirm you are downloading right RUU for your device. Make sure you download a Marvel_C RUU for a CDMA device (no sim card) or a Marvel RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 80%. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up (step 1). While the RUU wizard is open, don't do anything. Just find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Copy that and keep it on another location. Close the RUU wizard.
Now, open ROM.zip with 7zip and extract "System, Boot and recovery img's" [.img file/s]. Put it in the location were you've installed Android SDK tools.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Flash the stock recovery, boot, system img's using the following command/s:
step by step
For recovery
Code:
fastboot flash recovery recovery.img
For boot
Code:
fastboot flash boot boot.img
For system
Code:
fastboot flash system system.img
Now go back to device recovery and DO FACTORY RESET and reboot your device.
If everything done perfectly then the phone will booted normally on STOCK ROM! Remember Now bootloader is UNLOCKED but NOT rooted. Don't worry, you can root your device and also install CWM as before.
Hope this method will solve your issue.
Thank you very much testmasterbd =) , for this excellent description.
But..... i can`t start my phone into the bootloader. The phone turns on (only seeing the backlight) and suddenly it turns off (again the backlight). It does this ever and ever again until i pull out the battery . =(
how can i get into the bootloader? volume down and power doesn`t work anymore.
Maybe i can connect the phone to the pc, not via usb but via other contacts. Or is there another way to get the phone into fastboot mode?
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
testmasterbd said:
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
Click to expand...
Click to collapse
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
appyleptiker said:
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
Click to expand...
Click to collapse
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
testmasterbd said:
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
Click to expand...
Click to collapse
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
appyleptiker said:
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
Click to expand...
Click to collapse
It is don't be frustrated
In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??
Peppsico said:
In November (just about one week after the warranty was up) the $300++ Kindle Fire HD we bought just stopped working. Amazon basically said sorry, your warranty is up - wanna buy another? (no thanks)
When it's turned on, the Kindle Fire logo appears, then the screen goes black. Nothing else.
We've tried the usual tricks. I bought a fastboot cable and tried the KFHD System.img Recovery Tool and all I get is "device not found." My computer doesn't seem to recognize the device at all.
Is there anything else I can try.... or is it just a lost cause??
Click to expand...
Click to collapse
first of all, is it a 8.9 inch? if so DO NOT use fastboot cable, it can actually CAUSE damage to 8.9 incher. you just need the regular microUSB that came with your kindle. "special" fastboot cables are only required for the 7 incher... if you have the 8.9 inch "jem" i can try to point you to a few threads that may help unbrick it.
Mike
Thanks... Yes it is 8.9! I'd greatly appreciate any help!!
Anybody?
If I could get a computer to recognize the Kindle, I'm sure I could apply some of the fixes and find something to get it going again. It doesn't show up in device manager and makes an 'error' sound.
You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE
skullarc said:
You can recover from this but first i will need to know how you bricked it, which operating system do you have, and do you have a sdk installed.
A few moths ago i ran into the same problem but now my kindle is working just fine.
DO NOT USE THE FASTBOOT CABLE TO DO ANYTHING IT CAN DAMAGE YOUR KINDLE
Click to expand...
Click to collapse
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?
clemsongt said:
In an attempt to not start new threads where they aren't needed. I'm in a very similar boat, so here are the answers to your questions:
I was attempting to flash CM11 to my 8.9 Kindle. I was following the following instructions:
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Parts 1-6 of Step 1 completed successfully, and somewhere between Step 1 and 3 the screen turned off. I have not yet been able to get the screen to turn on again or the device to light up when charging or anything.
Thoughts?
Click to expand...
Click to collapse
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.
turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481
skullarc said:
turn off your device and then connect your normal cable then type
fastboot -i 0x1949 getvar product
in your cmd or shell (if you are using linux or unix based operating system)
it should show
< waiting for device >
then turn on your device
it should go into fastboot then download the neccery files follow step 5 form the link
forum.xda-developers.com/showthread.php?t=2128175
and
follow the installation for cyanogenmod from
forum.xda-developers.com/showthread.php?t=2543481
Click to expand...
Click to collapse
I'm on Windows with minimal adb and fastboot. I get the < waiting for device > but when I plug in in my tablet nothing happens on either end. It doesn't matter if I have the device plugged in before or after running the command.
mrcpu said:
Can you get into fastboot? I was able to recover mine by restoring my backup and then starting over with pushing stack and all that stuff. So getinto adb wtih the getvar, then just plug a normal cable into the kindle, and see if your PC recognizes it, and it drops into fastboot.
Click to expand...
Click to collapse
By get into fastboot, I assume you mean with the command skullarc referenced since there is no button combination one can use to get into fastboot? Then your answer is shown above. The device has been completely unresponsive to anything I throw its way so far.
when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again
skullarc said:
when you turn on your kindle what does it show?
If it does not even turn on then press the power button continuously for 20-30 seconds. Then press the power button again
Click to expand...
Click to collapse
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.
clemsongt said:
It does not respond to anything I throw at it. If you mean to press and hold the power button for 30 seconds, let go, then press and release, that also gets no response.
Click to expand...
Click to collapse
Could it be that your charger is not working and doesn't device even blink when you press the power button
skullarc said:
Could it be that your charger is not working and doesn't device even blink when you press the power button
Click to expand...
Click to collapse
Not a charger issue, as I have used a known good one overnight with no difference.
clemsongt said:
Not a charger issue, as I have used a known good one overnight with no difference.
Click to expand...
Click to collapse
were you able to perform the third step ?
skullarc said:
were you able to perform the third step ?
Click to expand...
Click to collapse
What's the third step?
clemsongt said:
What's the third step?
Click to expand...
Click to collapse
Third step in installing CM11 and did you use fastboot cable ?
skullarc said:
Third step in installing CM11 and did you use fastboot cable ?
Click to expand...
Click to collapse
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
hashcode said:
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/s
Click to expand...
Click to collapse
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.
clemsongt said:
The third step found here?
http://forum.xda-developers.com/showthread.php?t=2128175
If so, I got the response "device not found" when attempting to push to sd card.
I tried with and without fastboot cable (have not verified functionality of fastboot cable as it was bought after bricking my device(.
Click to expand...
Click to collapse
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step
skullarc said:
I was trying to ask at what step did your kindle turn off when you were trying to install cm11 and was bricked in this were you able to start the 3rd step
Click to expand...
Click to collapse
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2
clemsongt said:
Ohhhh...Sorry for being confused.
following these steps, I was able to successfully complete all of step 1, step 2, and step 3. it was in recovery while I was reading up on the "Installing CyanogenMod from recovery" section and when I looked back at the device, the screen had gone black. Since then I have not gotten it to do anything.
wiki.cyanogenmod.org/w/Install_CM_for_otter2
Click to expand...
Click to collapse
Did you check the md5sum for the files that you flashed in step 3 and downloaded in step 2
it will tell you if they are corrupt