Related
I had been running cognition 2.2 beta1, put phone into download mode using vol up vol down and put in usb cord and flashed back to stock. Then I flashed Shep211's JPM\JI6 ROM via rom manager. Reflashed a JI6 kernel, then tried to use rom manager to flash to cognition 2.2 beta7. The update failed and now I only get the phone exclamation computer screen and I cannot get my phone back into download mode! I have tried almost every combination of vol up vol down power and usb I can think of to no avail. Can anyone at XDA help before I return the phone to ATT?
Any help is greatly appreciated!!
Pull battery. Just keep trying to get into dl mode. That's all I think you can do.
Sent from my SAMSUNG-SGH-I897 using XDA App
Have you tried doing it via the SDK? Really easy that way.
mrwoofus said:
Have you tried doing it via the SDK? Really easy that way.
Click to expand...
Click to collapse
through ADB you mean?
I just get error - device not found whenever I try and run any adb command.
Yes, I had to do the "adb reboot download" with the SDK running.
mrwoofus said:
Yes, I had to do the "adb reboot download" with the SDK running.
Click to expand...
Click to collapse
can you be more specific? I can't get adb to recognize this phone in its current state.
1- Pull battery and USB cable out..
2- Press Vol Up while you connect your phone to the USB
3- Insert battery, and keep pressing Vol Up!!!
or
1- Pull battery and USB cable out..
2- Press Vol Down while you connect your phone to the USB
3- Insert battery, and keep pressing Vol Down!!!
or
1- Pull battery and USB cable out..
2- Press Vol Up while you connect your phone to the USB
3- Insert battery and, keep presing Vol Up, press the Power button..
Keep pressing Vol keys means that you must keep pressing the buttons until you get the Download Mode Screen.. And keep trying.. Sometimes it take some time to work..
What I did was download and install the SDK in the C:\Android directory
Then open a windows command prompt and navigate to the "Tools" directory
Then just run the adb command.
Not sure what to tell you if the phone isn't recognized, I'm pretty new at this myself. I'd start hitting Google.
Good luck.
mrwoofus said:
What I did was download and install the SDK in the C:\Android directory
Then open a windows command prompt and navigate to the "Tools" directory
Then just run the adb command.
Not sure what to tell you if the phone isn't recognized, I'm pretty new at this myself. I'd start hitting Google.
Good luck.
Click to expand...
Click to collapse
You can go to Download mode from Recovery.. But not from the Phone+Computer screen.. I think..
SnakeHaveYou said:
1- Pull battery and USB cable out..
2- Press Vol Up while you connect your phone to the USB
3- Insert battery, and keep pressing Vol Up!!!
or
1- Pull battery and USB cable out..
2- Press Vol Down while you connect your phone to the USB
3- Insert battery, and keep pressing Vol Down!!!
or
1- Pull battery and USB cable out..
2- Press Vol Up while you connect your phone to the USB
3- Insert battery and, keep presing Vol Up, press the Power button..
Keep pressing Vol keys means that you must keep pressing the buttons until you get the Download Mode Screen.. And keep trying.. Sometimes it take some time to work..
Click to expand...
Click to collapse
Thanks for the suggestions, I tried these all several times, waiting about 1 minute before I gave up each time. Should I wait longer, or do you have any other suggestions? I'm about ready to give up and make a trip to AT&T
johnnyb138 said:
Thanks for the suggestions, I tried these all several times, waiting about 1 minute before I gave up each time. Should I wait longer, or do you have any other suggestions? I'm about ready to give up and make a trip to AT&T
Click to expand...
Click to collapse
Strange.. Every time that my phone got stuck on that screen (3 times ) i tried these steps.. And after some time (and others combinations, Vol Up+Down, Only Down, etc, etc etc..), it works..
SnakeHaveYou said:
Strange.. Every time that my phone got stuck on that screen (3 times ) i tried these steps.. And after some time (and others combinations, Vol Up+Down, Only Down, etc, etc etc..), it works..
Click to expand...
Click to collapse
this is my second time being stuck at this screen, but I'm having absolutely no luck this time around (have been trying for about an hour now). I guess I'll be making that trip to att.
Try this, or see the Thread answers
http://forum.xda-developers.com/showthread.php?t=775911
SnakeHaveYou said:
Try this, or see the Thread answers
http://forum.xda-developers.com/showthread.php?t=775911
Click to expand...
Click to collapse
I've tried all of the suggestions in this thread already, I have somehow managed to completely brick this thing. Thanks for all of your help!
If you were going to Cog 2.2.7, why wouldn't you just have wiped, flashed to stock, rooted and then flashed with Clockwork Recovery?
Anyway, good luck.
-Did you try to start pressing the Vol button AFTER you plug the USB cable? And before you plug it?
-Did you try another USB port or another PC?
Here is the Fix
I was in this same situation last week. Here is how to get it back into download mode.
•Be sure the Samsung USB drivers for the phone are installed on your computer.
•Remove and replace the battery.
•Connect the phone to the computer with the USB cable. The "phone-exclamation mark-computer" picture should display on the phone's screen.
•Hold the Volume Up+Volume Down+Power buttons down simultaneously.The screen should go blank, then the picture should appear again. When the screen goes blank a second time, release the Power button while continuing to hold the Volume Up+Volume Down buttons down
praetorrian said:
I was in this same situation last week. Here is how to get it back into download mode.
•Be sure the Samsung USB drivers for the phone are installed on your computer.
•Remove and replace the battery.
•Connect the phone to the computer with the USB cable. The "phone-exclamation mark-computer" picture should display on the phone's screen.
•Hold the Volume Up+Volume Down+Power buttons down simultaneously.The screen should go blank, then the picture should appear again. When the screen goes blank a second time, release the Power button while continuing to hold the Volume Up+Volume Down buttons down
Click to expand...
Click to collapse
This is the only method that consistently works for me. I use the exact same method. The key is whatever picture (att, battery charge, etc....) comes up the second time and then goes blank, then release the power button.
praetorrian said:
I was in this same situation last week. Here is how to get it back into download mode.
•Be sure the Samsung USB drivers for the phone are installed on your computer.
•Remove and replace the battery.
•Connect the phone to the computer with the USB cable. The "phone-exclamation mark-computer" picture should display on the phone's screen.
•Hold the Volume Up+Volume Down+Power buttons down simultaneously.The screen should go blank, then the picture should appear again. When the screen goes blank a second time, release the Power button while continuing to hold the Volume Up+Volume Down buttons down
Click to expand...
Click to collapse
Thanks for the suggestions, I really do appreciate them. I just tried this a few times but still no avail. I tried it with two computers just to be sure and still nothing. I guess I really have bricked the seemingly unbrickable phone
Have you tried Odin3?
Sent from my SAMSUNG-SGH-I897 using XDA App
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.
SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.
polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.
First of all sorry for my english
I have bricked my inspire 4g eng s-off i was just trying to root my inspire 4g without unlocking bootloader noob i just know nothing about unlocking bootloader i used htc quick root software when the process start the software requested me an hboot image and unfortunatly i located to recovery image and phone turned off now when ever i try to turn it on it gives three vibrates vol down +pwr five vibrates please help m
volume up +voldown+pwr button five vibrates and a stable green led vol down +pwr three vibrates and red blinking led just pwr on button three vibrates red blinking led
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
turboyoshi said:
If your bootloader wasn't unlocked, I don't see how you could have bricked it. Also, do you know if you had usb debug mode turned on? You couldn't have flashed an image with a locked bootloader and the scripts won't work either since the adb/fastboot utilities cannot talk to your phone if debug mode is off.
At any rate, pull out the battery for a few minutes, reseat the battery, connect the phone to your pc, hold down vol- and power and see if you can get to a bootloader screen. Even if it seems to boot but hangs at the green htc logo, you should still be able to issue adb commands and recover.
Once the phone boots, on your pc, open a command prompt and type the command "adb devices" without quotes to see if your phone is recognized. Let us know the status then.
Click to expand...
Click to collapse
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Branded badmash said:
the bootloader was lock but eng s-off and there is is no adb no fastboot boot i have tried all methods putting battry out for 15 mints i have checked with another battery with no luck when ever i try to turn on my phone it give three vibrates and my pc recognize it as QUALCOMM DIAGNOSTIC 900e when i press vol down +pwr it gives three vibrates vol down +up+pwr five vibrates is there any way to flash the rom in qualcomm diagnostic mode and the usb debug was on last time kindly help me !!
Click to expand...
Click to collapse
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Gizmoe said:
Qualcomm mode is what happens when you hold volume down instead of up while booting. A common issue with the inspire is the volume rocker malfunctioning and becoming "stuck". Usually it is volume up that gets stuck. Either way you will have to probably repair the volume rocker by replacing it. With the age of the device though I don't think it's worth it to spend any money on repairs. It's almost 3 years old now. I know it seems concidental to happen at the same time your trying to unlock it but it can happen. If it is something that went wrong while you were trying to unlock it your pretty much in the same boat. If it only goes to Qualcomm mode there is nothing you can do.
Click to expand...
Click to collapse
i have checked the volume rocker and replaceed it with no luck
Branded badmash said:
i have checked the volume rocker and replaceed it with no luck
Click to expand...
Click to collapse
Then something happened when you tried to unlock it. If you can't access the device via fastboot or adb then it is not fixable. Reflashing a boot img or hboot would be what you would want to do if you could gain access.
Hello everyone.
Yesterday I tried to flash my nexus to f2fs. After that I wanted to go back to the stock, but forgot format filesystem to ext4 and run flash_all.bat.
Flashing was stopped on system write with error: "Unknown chunk type". After that i can't open recovery or turn on phone.
On 4pda i read, that bootloader reopen can help fix this problem.
When I flash new boot, nexus was died.
Can you help me?
Hi,
Please provide a link to exactly what you've flashed? Can you access the bootloader?
i flash google original rom
no, i haven't access to bootloader
no-tactic said:
i flash google original rom
no, i haven't access to bootloader
Click to expand...
Click to collapse
you need to put your device in fastboot mode, keep retrying
then to go back to EXT4 :
- Flash back an official custom recovery (CWM or TWRP)
- Format Data from recovery
- Flash a kernel compatible with your ROM
- Reboot.
no-tactic said:
i flash google original rom
no, i haven't access to bootloader
Click to expand...
Click to collapse
What happens when you hold down Power + Vol down keys together? Hold them until you feel a vibration. May be the battery has died? Keep it on charge for an hour and then try to enter bootloader?
vin4yak said:
What happens when you hold down Power + Vol down keys together? Hold them until you feel a vibration. May be the battery has died? Keep it on charge for an hour and then try to enter bootloader?
Click to expand...
Click to collapse
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
Your memory is no longer accessible unfortunately, you most likely need to have it repaired (new motherboard) :crying:
no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
If all the key combinations don't work, them your device is done for! Since it's totally dead there shouldn't be any problem to RMA it! Good Luck
no-tactic said:
nothing happens. When I put the phone on charge, it starts to warm up a bit in the camera, but even the display does not light up.
when i connect the phone to computer, it is defined as qhsusb_bulk or unknown usb device
Click to expand...
Click to collapse
Press and hold volume up while you connect usb cable to pc.
can you see download mode on device screen?
if yes read this thread entirely http://forum.xda-developers.com/showthread.php?t=2515760
Edit: try this also:
connect your phone to the pc, open device manager.
hold your power button until QHSUSB_BULK disappears, then in that split second press and hold both volume key while you still press the power key. it may end up into the second bootloader
thank you all!
I have a verizon htc one m8 and i tried to update the ota from 4.4.2 to 4.4.4 with ruu. First time it gave me an error and second time the phone didn't reboot. It won't charge and it won't eneter in h-boot. What should i do? I tried key combination, nothing works.
Will it power on at all? If you plug usb to your computer does adb devices command give output?
cypryan1217 said:
I have a verizon htc one m8 and i tried to update the ota from 4.4.2 to 4.4.4 with ruu. First time it gave me an error and second time the phone didn't reboot. It won't charge and it won't eneter in h-boot. What should i do? I tried key combination, nothing works.
Click to expand...
Click to collapse
So the screen doesn't boot at all?
bjoostema said:
So the screen doesn't boot at all?
Click to expand...
Click to collapse
Yes, the screen doesn't boot at all. I observe that when i press for 15 seconds volume up or down and power one orange led blink once, and when i put on charge but it blinks only once.
This is what i get on adb ->
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
That does sound like a brick. Maybe enquire in this thread: http://forum.xda-developers.com/showthread.php?t=2363516
cypryan1217 said:
Yes, the screen doesn't boot at all. I observe that when i press for 15 seconds volume up or down and power one orange led blink once, and when i put on charge but it blinks only once.
This is what i get on adb ->
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
Assuming you have left it charging for a while, does it show up in device manager as. Qsusb device?
dottat said:
Assuming you have left it charging for a while, does it show up in device manager as. Qsusb device?
Click to expand...
Click to collapse
How can i check this? In device manager in windows 8 doesn't show anything like that. But whe i connected now at the pc le orange led just was on like 15 seconds.
cypryan1217 said:
How can i check this? In device manager in windows 8 doesn't show anything like that. But whe i connected now at the pc le orange led just was on like 15 seconds.
Click to expand...
Click to collapse
Are you sure you just don't have a really dead battery? That's what they do until they get a decent enough charge.
Check device manager for movement when you disco and reconnect the phone. Also see if you get it to show in fastboot money.
dottat said:
Are you sure you just don't have a really dead battery? That's what they do until they get a decent enough charge.
Check device manager for movement when you disco and reconnect the phone. Also see if you get it to show in fastboot money.
Click to expand...
Click to collapse
Nothing happend in device manager...
And in adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot mooney
< waiting for device >
I let it charging a night but nothing apper on the screen.
cypryan1217 said:
Nothing happend in device manager...
And in adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot mooney
< waiting for device >
I let it charging a night but nothing apper on the screen.
Click to expand...
Click to collapse
Do you have a different cable and charger to try?
dottat said:
Do you have a different cable and charger to try?
Click to expand...
Click to collapse
nothing happend....
cypryan1217 said:
nothing happend....
Click to expand...
Click to collapse
Do you have a Windows 7 pc you can connect to?
dottat said:
Do you have a Windows 7 pc you can connect to?
Click to expand...
Click to collapse
No... Only windows 8.1
cypryan1217 said:
No... Only windows 8.1
Click to expand...
Click to collapse
Have you tried unplugging it (no usb cable at all) and waiting 20 seconds before pressing and holding vol up and power for 60 seconds.
dottat said:
Have you tried unplugging it (no usb cable at all) and waiting 20 seconds before pressing and holding vol up and power for 60 seconds.
Click to expand...
Click to collapse
Only the orange led blinks once... that's it.
cypryan1217 said:
I have a verizon htc one m8 and i tried to update the ota from 4.4.2 to 4.4.4 with ruu. First time it gave me an error and second time the phone didn't reboot. It won't charge and it won't eneter in h-boot. What should i do? I tried key combination, nothing works.
Click to expand...
Click to collapse
Alright, I didn't read everything, but did you try holding down both volume keys and pressing and holding the power button for a couple of seconds to boot it down? If not, try that and if it works, then maybe I can help you from there.
cypryan1217 said:
Only the orange led blinks once... that's it.
Click to expand...
Click to collapse
If it's not detected by your pc and after what you've tried you likely need to swap it.
venom4843 said:
Alright, I didn't read everything, but did you try holding down both volume keys and pressing and holding the power button for a couple of seconds to boot it down? If not, try that and if it works, then maybe I can help you from there.
Click to expand...
Click to collapse
I didn'"t try thaht... i will try this when i go back home... thank u...
I hope i cand fix it