Related
I don't really know what happened. When I press the power button my phone's screen lights just black then goes blank. When I press my buttons they vibrate but nothing happens. I've tried pulling the battery out several times, leaving it on the charge and all other kinds of things. It is just not working. Does anyone have the solution to this problem?
I'm not sure if this is the same issue..but along the process of rooting my rogers raider I encountered thus during a regular restart. I thought I bricked my phone but realize that the back light was just off and my phone was actually in the recovery menu. I put the phone under bright light and I could just barely see the headings in the recovery menu. It took some tilting and angling the phone just right to see it, but I was able to run a nandroid recovery and get back to a point before this happened. Once again, not sure if its the same thing but try tilting the phone around and using the volume keys to see if you can see the recovery menu in the blank screen.
Hope this helps
Sent from my HTC Sensation Z710e using XDA
Phazd said:
I don't really know what happened. When I press the power button my phone's screen lights just black then goes blank. When I press my buttons they vibrate but nothing happens. I've tried pulling the battery out several times, leaving it on the charge and all other kinds of things. It is just not working. Does anyone have the solution to this problem?
Click to expand...
Click to collapse
richieroo said:
I'm not sure if this is the same issue..but along the process of rooting my rogers raider I encountered thus during a regular restart. I thought I bricked my phone but realize that the back light was just off and my phone was actually in the recovery menu. I put the phone under bright light and I could just barely see the headings in the recovery menu. It took some tilting and angling the phone just right to see it, but I was able to run a nandroid recovery and get back to a point before this happened. Once again, not sure if its the same thing but try tilting the phone around and using the volume keys to see if you can see the recovery menu in the blank screen.
Hope this helps
Sent from my HTC Sensation Z710e using XDA
Click to expand...
Click to collapse
This doesn't seem to be the situation I'm having but thank you anyway. +Thanks.
when you plug it in to charge, does the orange charge light come on for 4-5 seconds then go out again? have you tried to hold the vol down key and the power button to get into HBoot? If you can get into HBoot, you might be able to get into recovery.
flip4life39 said:
when you plug it in to charge, does the orange charge light come on for 4-5 seconds then go out again? have you tried to hold the vol down key and the power button to get into HBoot? If you can get into HBoot, you might be able to get into recovery.
Click to expand...
Click to collapse
Yes, that is exactly what is happening. I tried what you said but it is not working. My phone won't go into Hboot.
I think your battery isn't charging (at least that was the issue I was having). Your battery will only charge when the orange light goes on, and if it's anything like what was happening to me, when the orange light went off, that's when the buttons would vibrate. If this is the case, it may sound tedious, but you have to watch the phone. When the orange light goes off, push the home button several times and the vibrating will stop. Then you should see the orange light come on again to signify the charging state. It'll go off again after 4-5 seconds and the buttons will vibrate. Repeat the process of pushing the home button and letting the orange light come on and eventually, the phone should try and turn on. You can try and see if it'll boot, but mine never had enough juice to turn on. So I would pull the battery when the HTC Logo came up and repeat the process with the orange light. This time though, I would hold the vol down button knowing that when it tried to turn on again, it would load into the bootloader. I can't guarantee this'll work for you, but give it a go. What might make it easier is borrow a charged battery from someone and see if it'll load into the bootloader. That might save you from that tedious process.
flip4life39 said:
I think your battery isn't charging (at least that was the issue I was having). Your battery will only charge when the orange light goes on, and if it's anything like what was happening to me, when the orange light went off, that's when the buttons would vibrate. If this is the case, it may sound tedious, but you have to watch the phone. When the orange light goes off, push the home button several times and the vibrating will stop. Then you should see the orange light come on again to signify the charging state. It'll go off again after 4-5 seconds and the buttons will vibrate. Repeat the process of pushing the home button and letting the orange light come on and eventually, the phone should try and turn on. You can try and see if it'll boot, but mine never had enough juice to turn on. So I would pull the battery when the HTC Logo came up and repeat the process with the orange light. This time though, I would hold the vol down button knowing that when it tried to turn on again, it would load into the bootloader. I can't guarantee this'll work for you, but give it a go. What might make it easier is borrow a charged battery from someone and see if it'll load into the bootloader. That might save you from that tedious process.
Click to expand...
Click to collapse
Thank you, this method you gave me fixed my issue. +Thanks.
flip4life39 said:
I think your battery isn't charging (at least that was the issue I was having). Your battery will only charge when the orange light goes on, and if it's anything like what was happening to me, when the orange light went off, that's when the buttons would vibrate. If this is the case, it may sound tedious, but you have to watch the phone. When the orange light goes off, push the home button several times and the vibrating will stop. Then you should see the orange light come on again to signify the charging state. It'll go off again after 4-5 seconds and the buttons will vibrate. Repeat the process of pushing the home button and letting the orange light come on and eventually, the phone should try and turn on. You can try and see if it'll boot, but mine never had enough juice to turn on. So I would pull the battery when the HTC Logo came up and repeat the process with the orange light. This time though, I would hold the vol down button knowing that when it tried to turn on again, it would load into the bootloader. I can't guarantee this'll work for you, but give it a go. What might make it easier is borrow a charged battery from someone and see if it'll load into the bootloader. That might save you from that tedious process.
Click to expand...
Click to collapse
I tried your method.. And when you said to tap the home button several times... It never stops vibrating.. It just keeps going.
flip4life39 said:
I think your battery isn't charging (at least that was the issue I was having). Your battery will only charge when the orange light goes on, and if it's anything like what was happening to me, when the orange light went off, that's when the buttons would vibrate. If this is the case, it may sound tedious, but you have to watch the phone. When the orange light goes off, push the home button several times and the vibrating will stop. Then you should see the orange light come on again to signify the charging state. It'll go off again after 4-5 seconds and the buttons will vibrate. Repeat the process of pushing the home button and letting the orange light come on and eventually, the phone should try and turn on. You can try and see if it'll boot, but mine never had enough juice to turn on. So I would pull the battery when the HTC Logo came up and repeat the process with the orange light. This time though, I would hold the vol down button knowing that when it tried to turn on again, it would load into the bootloader. I can't guarantee this'll work for you, but give it a go. What might make it easier is borrow a charged battery from someone and see if it'll load into the bootloader. That might save you from that tedious process.
Click to expand...
Click to collapse
OK I get what you have to do now.... but it wont work... I plugged in my charger.. The light would go for 5 sec. then I would touch the buttons and they vibrate.. So I tap the home button constantly. And the orange light didnt come back up.. HELP! PLEASE!
help the charging light doesn't come back again.. vibration has stopped.. but still no charging light
help pleaseeee
Try different battery fully charged and see if your phone turns on. It it does then plug your phone for charging and see if charges.
Try connecting your phone with usb cable in computer and see if your computer recognize the phone.
there can be three issues.
1. Your battery is dead and won't charge
2. Your charging port on phone is not working
3. your phone backlight is not working.
http://forum.xda-developers.com/showthread.php?t=1717766
http://forum.xda-developers.com/showthread.php?t=1479060
http://forum.xda-developers.com/showthread.php?t=1531208
http://forum.xda-developers.com/showthread.php?t=1694017
http://forum.xda-developers.com/showthread.php?t=1769616
http://forum.xda-developers.com/showthread.php?t=1652689
http://forum.xda-developers.com/showthread.php?t=1732268
http://forum.xda-developers.com/showthread.php?t=1754534
EDIT: I have stopped looking for these threads. The more I look, the more I find. If the above threads don't convince you that there is a serious issue with the vivid, then adding more of the same problem will no longer help.
I have added this thread to a growing list of similar threads. Please read the other threads and see if your issues seem familiar.
From what I understand... Don't let your battery run out on this phone. Some Vivids kill batteries.
Solution? None yet.
1. Buy a new battery once a couple of months-ish, until someone figures out why some Vivids are eating batteries. YMMV
*OR*
2. You might invest in a external charger and see if that can bring the "Vivid munched" battery back to life. YMMV
I vote to thread merge the above threads if this proves to be the issue.
Hello
I hope to get an answer here to avoid a new thread. I was trying to return my vivid back to gb from ics. I had booted into the bootloader and i dont even remember at this point what i thought i was going to do. I think i got distracted. But anyway i pressed vol down to boot recovery because i was going to do a backup and i looked away from the phone for a minute and when i came back to it the phone was black screen. i hit the power thinking it was just on standby but nothing. I notice it was backlit on the screen but nothing would happen when i press anything. I pulled the battery waited a few min put it back and now totally black with no activity at all. no lights no vibrating no power on, no adb. I have played with a lot of phones and even iphones too so if this thing is fried i guess i will consider myself lucky that its the first ive actually killed out of probably 30 phones. I have searched and tried many things but i cant believe there is no way to recover it. I have recovered a lot of phones I thought I bricked before. any help is greatly appreciated. I was on ics and rooted. I also relocked the bootloader. (i was planning to go back to gb) I thought i had a recovery installed but maybe not. i posted in another thread that i was unable to get hboot by power + vol down method. i could only do it through the tool kit. so i dont know if any of that matters
pinkmini said:
Hello
I hope to get an answer here to avoid a new thread. I was trying to return my vivid back to gb from ics. I had booted into the bootloader and i dont even remember at this point what i thought i was going to do. I think i got distracted. But anyway i pressed vol down to boot recovery because i was going to do a backup and i looked away from the phone for a minute and when i came back to it the phone was black screen. i hit the power thinking it was just on standby but nothing. I notice it was backlit on the screen but nothing would happen when i press anything. I pulled the battery waited a few min put it back and now totally black with no activity at all. no lights no vibrating no power on, no adb. I have played with a lot of phones and even iphones too so if this thing is fried i guess i will consider myself lucky that its the first ive actually killed out of probably 30 phones. I have searched and tried many things but i cant believe there is no way to recover it. I have recovered a lot of phones I thought I bricked before. any help is greatly appreciated. I was on ics and rooted. I also relocked the bootloader. (i was planning to go back to gb) I thought i had a recovery installed but maybe not. i posted in another thread that i was unable to get hboot by power + vol down method. i could only do it through the tool kit. so i dont know if any of that matters
Click to expand...
Click to collapse
I hope someone resolves this issue, I've messed with lots of phones. But this is really weird. But I got the same problem where all that happens is that there is backlight on but no boot IMG no HTC logo, no bootloader, recovery. Completly non responsive. At first it wouldn't even power on until I would unplug from a power source. Whether it was unpluging the charger or removing the battery. That's when the backlight would flash. All this happened in the process of flashing a PH39IMG.zip
Is there no other fixes for this? Anyone? Please
pinkmini said:
Is there no other fixes for this? Anyone? Please
Click to expand...
Click to collapse
I once got stuck on the HTC screen (White background) and found out I could access the device in adb.
So, connect your phone to your pc and check if you can access it from adb (adb devices). If you can try get to the bootloader from here and see what happens (adb reboot-bootloader)!
And if you can access bootloader,
>If you need to get back to stock, get your carrier RUU, put rom.zip from it in an external sdcard and use reboot into hboot again, OR
>if you need a custom ROM unlock bootloader, flash a custom recovery (TWRP is cool) and you may use TWRP to install your ROM
I hope this helps... lets know...
I did mention I cant get it to recognize the phone. So no adb I tried all that before posting. Im afraid im just dead
So I am having the same problem. I eventually got it on yesterday but I turned off my phone and I am back to square one. Would using the vivid toolkit work to reboot to hboot? or am I stuck like this until i replace battery?
4 hours later I am back on!! never turning this thing off again
Had the same problem and just left the at&t store and its the battery. Once he exchanged batteries it worked fine
Sent from my HTC PH39100 using xda app-developers app
I'm stuck in a pretty crappy situation. The phone is on some weird bootloop. When it boots, the AT&T screen comes up, then some weird multi-colored screen comes on, the phone turns off, and this process repeats.
I know how to put it into download mode, but the phone turns on as soon as I put the battery in. I'm not sure how to have it powered off with the battery in long enough so I can hold the volume buttons down and plug the USB in. If I could at least get into download mode and flash something via Odin, I could possibly fix it.
Any suggestions?
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
adobrakic said:
I'm stuck in a pretty crappy situation. The phone is on some weird bootloop. When it boots, the AT&T screen comes up, then some weird multi-colored screen comes on, the phone turns off, and this process repeats.
I know how to put it into download mode, but the phone turns on as soon as I put the battery in. I'm not sure how to have it powered off with the battery in long enough so I can hold the volume buttons down and plug the USB in. If I could at least get into download mode and flash something via Odin, I could possibly fix it.
Any suggestions?
Click to expand...
Click to collapse
fractaline said:
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
Click to expand...
Click to collapse
(psst, he said his power button is broken)
You dont need to use the power buttons to enter download mode. Just hold both volume buttons and plug in usb. Though tbh I haven't had to do it in so long my memory is a bit foggy on whether it was both volume buttons + usb or just volume up + usb. Either way one of those should work. Im pretty sure you should be able to do it without the battery inserted.
When all else fails, jig it. Jig it hard.
Herp derp Captivate Tapatalk 2
fractaline said:
did you try, remove battery, plug in usb, hold power and both volume buttons then insert battery? or even just hold vol down and power then insert battery?
Click to expand...
Click to collapse
Well, the power button doesn't work, so I haven't tried the latter. It's not rooted, so trying to get into CWM wouldn't really do much. When I try to plug in the USB, hold the volume buttons, and plug in the battery last, the phone just goes to the battery charging screen. If I take the USB out.. it stays there.
I'm not sure why the phone turns on by itself as soon as I put the battery in. My sister has the same model, and she has to hold the power button to turn it on. :/
I just turned it on, and it's stuck on the AT&t screen instead of bootlooping. This is the first time it has done this after the bootloop began. Odin recognizes it. Is this ninja download mode? If so, could you please point me in the right direction of getting out of this mess? :x This is my sister's fiance's phone, I own a SGS4G. Really don't wanna risk this phone any more than I already have, lol.
Thanks, guys.
--Edit--
To be more specific, I attempted using this to root the phone, which resulted in this situation. Not sure if that's even helpful, but it can't hurt.
I feel for ya, I hate having hardware issues when a software issues happens..
follow fractaline's instructions: Odin ON, battery out, Good USB cable with good USB port Insert, (this is where it gets tricky), hold down volume up and volume down, whilst 2 seconds later putting the battery back in.
if you see the screen with something that looks like this, http://movilzone.org/files/2011/09/Captivate-Download-Mode1.jpeg
or this,
http://1.bp.blogspot.com/-BwmbWV5u6h8/TvNq1jXT7oI/AAAAAAAAMpU/_Mh4V9LMYd8/s1600/Semi-bricked.jpg, Then you can flash a kernel.
Were you on gingerbread 2.3.5? if so I would recommend this http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn
if you flash corn there is an option in CWM to install root I believe.
I used to flash the corn kernel all day to fix my 2.3.5 problems.
it really depends which version you previously were running. which is hard to tell since it wasn't your phone... more info needed, i'll be back in the morning. hope this helps.
Oh and on the hardware side of things, you could take the back plate off, the plate under the battery, and clean all the crap out. i find with mine i often get dust particles that interfere with my power button. there is a guide to properly tear down a captivate on xda somewhere... I've posted on it before as well.
or, take your fingernails and try and peel back the plastic on the edge of the glass up by the power button, if you can pull it back enough to blow air in there sometimes you can dislodge/clean out whatever is obstructing the power button.
Edit: if you do get it rooted, bring it up to ICS, it's fantastic up here
adobrakic said:
Well, the power button doesn't work, so I haven't tried the latter. It's not rooted, so trying to get into CWM wouldn't really do much. When I try to plug in the USB, hold the volume buttons, and plug in the battery last, the phone just goes to the battery charging screen. If I take the USB out.. it stays there.
I'm not sure why the phone turns on by itself as soon as I put the battery in. My sister has the same model, and she has to hold the power button to turn it on. :/
I just turned it on, and it's stuck on the AT&t screen instead of bootlooping. This is the first time it has done this after the bootloop began. Odin recognizes it. Is this ninja download mode? If so, could you please point me in the right direction of getting out of this mess? :x This is my sister's fiance's phone, I own a SGS4G. Really don't wanna risk this phone any more than I already have, lol.
Thanks, guys.
--Edit--
To be more specific, I attempted using this to root the phone, which resulted in this situation. Not sure if that's even helpful, but it can't hurt.
Click to expand...
Click to collapse
I think you were not on Gingerbread and you attempted to flash a gingerbread kernel. That is why it is bootlooping. You can flash back to stock (Gingerbread or froyo) and that should solve your issue. I'm trying to download and get the stock froyo kernel for you so you can flash that again. Just an FYI, applying root through CWM would require the use of the power button.
Try flashing this in the PDA in Odin. It is the stock froyo kernel.
https://www.dropbox.com/s/vx5r7hr3iokj764/zImage.tar
@Bacon, it was version 2.2. I can't get to download mode because the phone turns on as soon as I put the battery in. I'm not sure why it does this. Also, I don't get the bricked screen because it just bootloops. The AT&T screen comes on, then this comes on, the phone turns off, and this repeats. I'm assuming that the multi-colored screen would be the SGS screen, or something similar.
Oh and on the hardware side of things, you could take the back plate off, the plate under the battery, and clean all the crap out. i find with mine i often get dust particles that interfere with my power button. there is a guide to properly tear down a captivate on xda somewhere... I've posted on it before as well.
or, take your fingernails and try and peel back the plastic on the edge of the glass up by the power button, if you can pull it back enough to blow air in there sometimes you can dislodge/clean out whatever is obstructing the power button.
Click to expand...
Click to collapse
If it comes to that, I'll definitely keep this in mind.
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
adobrakic said:
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
Click to expand...
Click to collapse
You're not stupid. I added that after reading your post to prevent others from getting into the same situation.
As for download mode, if you don't have a jig, try this:
Take battery out
Plug phone into computer
Hold down Volume Buttons
Put battery in
adobrakic said:
@Red Wow, I'm stupid. -_- I don't know how I missed the "Requirements" on that page. Thanks, I'll try your .tar now.
--Edit--
Ah, unfortunately that AT&T screen wasn't download mode. I guess I'm just gonna have to keep trying until I finally get it into download mode. I just don't get why it's this difficult.
Click to expand...
Click to collapse
I can't tell you how many times i flashed the wrong kernel because i didn't read that it was for my version! lol!
that screen is unsettling...
well it's tough to say what to do next... just keep trying for a download mode. I've never used a Jig, perhaps that would be a good investment. Maybe use a one click.. I don't know..
I don't suppose this could be a bootloader issue could it?
EDIT: You're sure you have a reliable USB port/Plug? it's very important that both are good.
Red_81 said:
You're not stupid. I added that after reading your post to prevent others from getting into the same situation.
As for download mode, if you don't have a jig, try this:
Take battery out
Plug phone into computer
Hold down Volume Buttons
Put battery in
Click to expand...
Click to collapse
When I do that, I get to this screen. I'm assuming that's the battery charging screen, but the picture of the battery never comes up, just that refreshing icon.
If I keep holding the volume buttons, the phone seems to turn off in this state. I tried immediately unplugging the USB cable and letting go of the volume buttons once it does this. It stays off (if it's actually off). However, when I hold the volume buttons down and plug the USB back in, it just goes back to that screen. No download mode.
@Bacon
I don't suppose this could be a bootloader issue could it?
EDIT: You're sure you have a reliable USB port/Plug? it's very important that both are good.
Click to expand...
Click to collapse
To be honest, I have no idea if it could be a bootloader issue. I'm knowledgeable of Android as far as a user goes, I know nothing about the OS past rooting it, and tweaking it to OC/UC, etc. Also, I believe that the USB port/plug is reliable. It's the same combo I used prior to bricking it (lol). However, I have about 8 different ports and a few different cables as well, I'll give those a go.
Thanks for the help guys, I really do appreciate it.
adobrakic said:
@Bacon
To be honest, I have no idea if it could be a bootloader issue. I'm knowledgeable of Android as far as a user goes, I know nothing about the OS past rooting it, and tweaking it to OC/UC, etc. Also, I believe that the USB port/plug is reliable. It's the same combo I used prior to bricking it (lol). However, I have about 8 different ports and a few different cables as well, I'll give those a go.
Thanks for the help guys, I really do appreciate it.
Click to expand...
Click to collapse
Man I wish I could help more, i tend to be a hardware guy so i'm not much help other than telling you how to fix you power button... just keep flashing the crap out of it i guess. see if anything sticks...
Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)
Type:
Code:
adb wait-for-device reboot download
and hit enter.
Now try booting the phone with it plugged in again. If the computer recognizes it during the bootloop, it will issue it the command to boot into download mode.
Otherwise, I would suggest getting a download Jig. It will put you into download mode every time.
@Bacon
All good buddy, thanks so much for your help.
@Red
Holy ****, that worked perfectly. I'm in download mode right now, and am in the process of using a one click to get back to stock.
I'll post back with results.
--Edit--
This is the one click I was using. It won't flash bootloaders at first to prevent bricking, so I'm now in Android system recovery. I'm wanting to get into download mode again, but I guess since it's not in bootloop, the command Red gave me doesn't get me there. I need to get back into download so the bootloaders can be flashed. Any suggestions as to how I could get there again?
the most success I've had is using kies mini up to 2.3.5 and then using corn from there on.
Sent from my SGH-I897 using xda app-developers app
Does it always boot to recovery? You could just pull the battery and then try to let it boot normally.
Sent from my SAMSUNG-SGH-I897 using xda premium
@Bacon
Don't I need the phone to boot up for kies, though?
@Red
Yes. As soon as I put the battery in, the AT&T screen comes on, and then the Android System Recovery <3e> screen comes on.
When I try to plug in the USB, hold the volume buttons down, and plug in the battery last, it simply goes to the battery charging screen. I don't know why it doesn't go to download mode. I've tested the volume buttons in the Android System Recovery screen, both work just fine.
If you could get that power button to work you could try wiping data. That might get it out of that funk.
Try this:
Open a dos window and go to KK4_Root\Tools (probably on your C:\ drive)
Code:
adb reboot recovery --wipe_data
Crap, my computer doesn't seem to recognize the device when it's in the Android System Recovery screen. Should I try prying open the power button and seeing if I can get it to work? Don't see any other way out of this. I wish the soft-key buttons could be used for 'enter' instead of just the power button. :|
adobrakic said:
@Bacon
Don't I need the phone to boot up for kies, though?
Click to expand...
Click to collapse
Shoot, sorry i misread i thought you said you had gotten it partially fixed... my b.
I was just commenting how I'd had the most success using a one click to stock and moving up with kies. I'm afraid you may have to wipe data, which would suck.
Try the power button first. It's really easy taking the hardware apart. Just don't strip the tiny screws.... i only have three of the 6 holding my back plate in. You really don't need them all
Sent from my SGH-I897 using xda app-developers app
Honestly man, at this point, I wouldn't care if I had to repurchase all of the apps that I had if it was necessary to get the phone working. I'll YouTube some instructions for disassembly. Hopefully it'll get me out of this jam.
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Amazing trick
Thanks a million times!
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away.
Just incredible!
(I might be too noob, but what's the hidden logic for it?)
Thanks again !!
Thanks a million mate, it worked like a charm. God Bless you !!
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
These are only soft bricks
Bricks!
MacHackz said:
These are only soft bricks
Click to expand...
Click to collapse
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
himhz said:
Incredibly for me, the light-bulb-and-play-with-buttons trick worked for me straight away. what's the hidden logic for it?
Click to expand...
Click to collapse
It apparently has something to do with resetting input awareness. Either there's a photodiode that picks up on light levels, or the IR diode detects the heat from the bulb. Thus, when the phone's diode is fully activated, it apparently activates that reset. I haven't heard from anyone, but I strongly suspect if the battery were completely drained somehow, then it might allow you to charge it and turn it back on regularly. Otherwise, the option 2 bypass should still work even on a dead battery refusing to charge till it resets, since it may current from light/heat. I'm also curious to find if anyone can tell if the handset is actually still accepting a charge despite the lack of LED activity while its in the soft-bricked state, or if the charging circuitry refuses to allow current to pass to the battery. HTC? HTC?
Thumbs ups appreciated!
See you all at XDA: DevCon
RDshift said:
Yep. A real hard brick is a brick. Make a "I dragged my phone behind my car and this is how little it got beat up in my Otterbox" video.
See you all at XDA: DevCon
Click to expand...
Click to collapse
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic
Matt said:
A real brick is when hboot is not accessible no matter what you do, and there is no sign of life.
Don't get sarcastic
Click to expand...
Click to collapse
I've tried the two steps from above and my phone still just flashes the Back and Home lights when I hold down power.
I was running a cyanogen nightly (from maybe 3 weeks ago) when the phone shut off randomly (not dead battery) and wouldn't turn back on.
When plugged in via usb the device shows up in the eject devices system tray but "fastboot devices" lists no devices. I have the phone plugged into a rear usb2.0 port.
Starting to get nervous...not sure what my options are.
EDIT: Holy smokes option two worked after a third try. That's so wild. Thank you!
XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
WOW after an hour of trying to fix the issue option number 2 worked for me lol i can't believe it. sounds so ridiculous
None of the options worked for me... Please help!
My HTC One shutdown and now I can't turn it back up.
Hardware is in flawless condition.
I tried all combinations and options and still my phone is dead.
I know it's not the hardware problem. Checked voltage regulator, phone is charging, voltage and amps are ok. Logic board is in excellent condition, checked with microscope and multimeter.
Was used regularly and one day just turned off by itself.
Also I haven't messed around software because I don't have need for that kind of work.
Again please help me, I'm pretty desperate.
dude!
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Option 2 did the trick for me!you'r a life saver mate!kudos
My is stuck in a reboot loop. It was running GPE which cause the sim unlock code not to stick. One person told me that I need to go back to stock so I tried to flash the stock RUU and now stuck in reboot loop.
Neither method work for me! I can get into fastboot screen but can't flash anything. Having a hard time trying to install adb driver though
HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.
whitetiger_0603 said:
HOLY BEJEEZUS!! I just tried your option 2! I thought i just bricked this thing, and i need to return it for the warranty exchange in a few days. Holy cow thank you!!!! I had the capacitive lights blinking and the red charging light on. Coudln't run commands. Held it up to a CFL bulb, played with the power and volume buttons and BAM!! Booted back up. Thanks tons!! Phew!!!
Now to get rid of the frigging tampered stamp in fastboot. Can't get rid of it for the life of me. Tried using just Revone, Tried the All in One toolkit. Nothing. Thanks again.
Click to expand...
Click to collapse
Are you S-Off? if yes, you can either use adb commands (if your comfy with that): http://forum.xda-developers.com/showthread.php?t=2477792
or just use this tool: http://www.htc1guru.com/guides/guru-bootloader-reset/
RDshift said:
Just bricked my phone. Non-responsive except for capacitative home and back flashing, no charge light nothing.
Option 1) Hold Volume Up & Down, then hold power for 90 seconds. Should vibrate/flash/respond somehow. Sometimes takes some time and a few tries with long waits in between.
Option 2) Hold phone up to bright light (headlight or lamp bulb) and hold power for 15 seconds. Orange charge light will illuminate. Play with power & volume buttons till it boots.
Option 3) If plugged in on USB because you were working in Fastboot, (optional: wait 30 seconds to ensure whatever is going is complete so you don't ACTUALLY brick it), then unplug USB: reboots.
Option 2 resurrected my phone right before I was about to give up. Hope this helps some of you!
Option 3 resurrected my phone the next time.
Click to expand...
Click to collapse
Unfortunately, neither of these options worked for me. My phone is completely unresponsive with no charge light, no reaction to light, no USB recognition, no hard reset functionality, inability to access bootloader or anything for that matter.
I am uncertain as to what the problem is, but the phone had <40% charge when it failed. Are there any other alternatives?
[pending update(s)]
THANK YOU!!!!
Dude thank you so much, I just formatted my internal storage using the new TWRP 2.7 and for some reason I had a black screen with only the red light on. After a few minutes of failure, not being able to boot up to both recovery and bootloader, I tried OPTION 2, which saved my phone.
THANK YOU SO MUCH!
No OS Installed.
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.
Thanks a ton
Option 2nd worked... i installed insertcoin 2.1.4 and it happened.
flashed back to renovate.
once again thanks mate. cheers
Crazy way to unbrick M7
XeoNiCaLiTy said:
Did not expect Option 2 to work, but it was the only one working in the end (accidentally flashed a Sprint zip).
Thanks!
Click to expand...
Click to collapse
Sounds like urban legend, but i tried everything else. Worked right quick.
BTW, my soft brick came from just trying out droidwall blocking a puzzle game. App must have crashed badly.
No OS Fix
heyAmirulS said:
Hi guys. I was flashing ARHD Rom and it was suddenly failed. Now I stuck at recovery mode, twrp 2.6.3.3. I forgot to do back up. and I did some factory reset and now that's how I stuck at the recovery mode. So yeah. I need help. Thanks.
Click to expand...
Click to collapse
Try sending a rom using adb, then flashing to that rom. That's what I had to do when I had no OS installed on my Kindle Fire.
Hey guys,
I left my HTC One to charge and when I tried to unlock it, it wouldn't respond. Right now it's a blank screen, the red LED is on even when I unplug the phone, and the hardware buttons are lit. I've tried to restart the phone by holding the power, holding power + volume down, but nothing is working. Device isn't showing up under adb or fastboot devices. What is going on? How can I fix this?
Help me out. Thanks!
-Coby
Edit: Recently this has been happening to my phone frequently, but I am usually able to get it to restart doing the methods said above. This is the first time I can't get it to do anything.
Put it under a stronger light and longpress power + vol-
Try this
I was actually searching through old threads and found that same answer and tried it. I can't believe it worked! Thanks! Why does this happen though? And will this hopefully prevent it from happening later on?
Are you rooted with a custom rom?
However, idk why it happened
Guich said:
Are you rooted with a custom rom?
However, idk why it happened
Click to expand...
Click to collapse
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
COBYATCH said:
I have 4.3 Google Edition on my phone with TWRP.
I'll remember this trick next time though. Thanks again!
Click to expand...
Click to collapse
:good:
Strange that you had this issue, but :good:
Guich said:
Put it under a stronger light and longpress power + vol-
Try this
Click to expand...
Click to collapse
Why the stronger light? Im confused! :cyclops:
This has worked for me a ton of times too, I guess it must just trigger something with the light sensor the phone has and wakes it up.
TwinAdk said:
Why the stronger light? Im confused! :cyclops:
Click to expand...
Click to collapse
It's a tips
Maybe the light sensor is always on...
Sent from One with Tapa4
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
kungfudavie said:
It happened to me when i was rooted and used CWM.
It happened everytime i let the battery run down completely.
I havent rooted my replacement yet and when i let it run down, charged it for ten minutes and it booted straight up.
Seems to be an issue with the phone reading the charge state of the safety circuit in the phone. Mere speculation but i havent heard of it happening to anyone who wasnt rooted with custom recovery....
Click to expand...
Click to collapse
Can you please give me a little bit more details?
I have exact the same issue: The battery ran out completely, then I can't charge it or turn it on.
I have tried
1. with charger connect to outlet, power + vol-
2. with charger connect to PC, power + vol-
3. under desk light, without charger connected, power + vol-
Nothing worked for me.
Some questions:
- Should I connect the cable when I attempt to turn on the phone?
- Is normal desk fluorescent light "bright enough"?
- Should I move the phone under the light first then press the button, or the other way around?
Thank you for your help!
i have the same problem in my htc eye. i tried your solution. but it won't worked for me. phone still on blank screen and red light is on. how can i fix it?????
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM