Related
I was reflashing my phone, while in download mode, the power went off, and now my phone won't turn on or anything. I think my phone is bricked.
I bought the phone a week and a half ago. Will AT&T accept my phone for a replacement if I say it just stopped working? I have the $4.99/month Wireless Insurance, but won't they deny it when they find out I've been messing with it? What should I do?
Thanks!
Before you take it back, make sure it isn't bricked. Remove the battery, replace it, hold both the volume buttons, plug in the usb and see if it takes you to download mode
Sent from my Samsung SGH-i897
Kaik541 said:
Before you take it back, make sure it isn't bricked. Remove the battery, replace it, hold both the volume buttons, plug in the usb and see if it takes you to download mode
Sent from my Samsung SGH-i897
Click to expand...
Click to collapse
It's bricked. Replaced battery, won't turn on no matter what I do to it.
There's a small scratch on the screen, and the micro USB charging port cover is messed up a bit from something sticky getting in there.
What should I tell AT&T? What's the likeliness of them declining my claim? Can they tell that it's been tampered with even though it's bricked?
Wrong forum. But I would use my insurance instead and tell them it just quit on me...
Try plugging into the computer, remove the battery reinsert the battery. Then hold volume up and power till red text comes on the screen from there switch to holding both volume buttons down and power then when the red text flashes to black release power and continue to hold both volume buttons. That should get you back to the downloading digger bot.
Tehwall said:
It's bricked. Replaced battery, won't turn on no matter what I do to it.
There's a small scratch on the screen, and the micro USB charging port cover is messed up a bit from something sticky getting in there.
What should I tell AT&T? What's the likeliness of them declining my claim? Can they tell that it's been tampered with even though it's bricked?
Click to expand...
Click to collapse
They won't give you a hard time on the software side - to them off is off - they can't tell if you bricked it - they will send it somewhere and have it flashed.
BUT - if there is something sticky in the USB port then they do have grounds to deny your claim - for all they know you poured juice in there.
Good luck.
Get it into download mode and flash it again with odin. Likely not bricked.
Sent from my SAMSUNG-SGH-I897 using XDA App
alphadog00 said:
They won't give you a hard time on the software side - to them off is off - they can't tell if you bricked it - they will send it somewhere and have it flashed.
BUT - if there is something sticky in the USB port then they do have grounds to deny your claim - for all they know you poured juice in there.
Good luck.
Click to expand...
Click to collapse
If there is something sticky there it means he put something sticky there lol.
And also, follow thedamn directions people are giving you man. Your phone isntbricked, I dont even know of anyone who has bricked their phone yet..
Mattwp103 said:
Try plugging into the computer, remove the battery reinsert the battery. Then hold volume up and power till red text comes on the screen from there switch to holding both volume buttons down and power then when the red text flashes to black release power and continue to hold both volume buttons. That should get you back to the downloading digger bot.
Click to expand...
Click to collapse
votum said:
If there is something sticky there it means he put something sticky there lol.
And also, follow thedamn directions people are giving you man. Your phone isntbricked, I dont even know of anyone who has bricked their phone yet..
Click to expand...
Click to collapse
I tried everything suggested, nothing happens. The power went out, while flashing new firmware, now the phone won't turn on no matter what I do. I already tried peoples suggestions.
Tehwall said:
I tried everything suggested, nothing happens. The power went out, while flashing new firmware, now the phone won't turn on no matter what I do. I already tried peoples suggestions.
Click to expand...
Click to collapse
The AT&T screen doesn't come up?
Guys we have been told a gazillion times about this...what does this have to do with Development?! Jesus....
Which firmware were you using at the time and which one were you flashing?
also make sure the battery is charged
prestopasto said:
The AT&T screen doesn't come up?
Click to expand...
Click to collapse
Nothing does, I tried every combo, SIM card in and out, replacing battery, USB plugged in and out, download mode, regular power button, recovery mode, what the guy suggested above; everything.
Not a single thing shows up on the screen.
You glanced over my question.
The version of firmware you were using before the flash and during the failed flash can be very pertinent to the key combination you need to get into download mode =P
Zilch25 said:
You glanced over my question.
The version of firmware you were using before the flash and during the failed flash can be very pertinent to the key combination you need to get into download mode =P
Click to expand...
Click to collapse
I had the stock firmware, installed the JM5 firmware, reinstalled the JM5 firmware, while doing so, they power went off.
Just pressing Volume Down + Power got me into Download Mode everytime.
Edit: And yes, the battery was charged, it was at about 67% when I was flashing the firmware. How can I charge the battery for the heck of it when the phone is dead? Normally when you plug in the USB cable there's a charging animation on the screen. Nothing comes up at all, can a dead phone charge a battery, or does the software need to send the power to the battery?
Honestly I've had flashes fail at varying points during the flash and I've gotten the black screen before, ALWAYS I've been able to get it to work by following these steps:
Pull out everything, SIM, SD, Battery, USB, EVERYTHING
Close Odin (If it's open)
Reopen Odin
Insert battery, hold vol down (If this doesn't work hold both volume buttons NO POWER)
While holding the button(s) plug in USB
Don't touch the power at any point, if this fails and you want to try the other key combo, start the process over completely.
Zilch25 said:
Honestly I've had flashes fail at varying points during the flash and I've gotten the black screen before, ALWAYS I've been able to get it to work by following these steps:
Pull out everything, SIM, SD, Battery, USB, EVERYTHING
Close Odin (If it's open)
Reopen Odin
Insert battery, hold vol down (If this doesn't work hold both volume buttons NO POWER)
While holding the button(s) plug in USB
Don't touch the power at any point, if this fails and you want to try the other key combo, start the process over completely.
Click to expand...
Click to collapse
This man speaks the truth, listen to him.
If your insurance covers damage then destroy the phone and call att and tell them its been destroyed.
if not then it is possible that the power outage could have caused your phone to zap.
Flashing or not if you spilled stuff into the usb port your screwed. Week and a half and you scratched the screen and did that? I have tried to scratch mine with no succes. I say ditch that phone and get a GO phone. And have a mod delete this pointless thread already!!!!
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
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
KomuroXV said:
Verizon HTC One
I'll tell you guys the whole story of the phone, in case you find something related to the actual problem in here.
All started when a friend of mine got me interested in ROMs and other modification his phone had.
I learned by myself all I needed to in order to Root, Unlock, and S-Off my phone, also I wrote the SuperCID to it (11111111) and installed the Custom Recovery.
It gave me a little trouble, but it was all good at the end.
Now was the time of the truth. I was about to flash my first Mod ROM, which was Android Revolution HD 71.1 .
Seconds after a successful installation (yay) I go and decide to reboot my phone, only to realize that what I just had installed was a Mod ROM for AT&T (I think, at least not supported to mine) HTC One.
Thanks to this, my phone got stuck in a bootloop, that at first made me panic a little bit, but then I saw that I could still get to the bootloader, and after some days of reading and what not, I got it to work again. Fully working, everything from a stock RUU, all nice and pretty.
"Then, where is the real problem?" you may be asking. Here it goes:
5 minutes after I finally got it fixed, I got all and exited and decided to flash a ROM properly this time.
I put the ROM inside the phone's internal memory.
I reboot phone.
It gets into bootloader.
I go and choose Recovery.
Here's where the "whoops" happen.
Since I had just installed a brand new stocked RUU, the Recovery also returned to stock, which I didn't really think that would happen by then.
Obiously, or at least it was what I thought by then, to flash a ROM I need to flash a Custom Recovery first.
So, following, even though I had already chosen the "Recovery" option, and it loaded, while it was doing a god-knows-what, I turned my phone off, which I guess and would assume that interrupted some kind of important process.
After that, my phone rebooted, and I was like "Phew, ok"
But it wouldn't get past the white screen with the HTC logo. There, after some 6 to 8 seconds, it rebooted, infinitely. It wouldn't turn off either, just reboots.
Like, at first I thought I'd need to call an exorcist, the damn thing seemed like it had the devil inside or something, acting on his own.
Then I realized it was that I had just screwed up everything, again.
So, resume:
I turned off my phone while it was on a Recovery's process.
After that, the phone wouldn't get past the white HTC's logo screen.
It would reboot, load the logo, and, after some 6 to 8 seconds, reboot, infinitely.
It wouldn't turn off either, I had to wait for the battery to die. Also, after this, when I plugged it to his charger, it turned on on his own again (the devil!) and started the same rebooting process.
So, what do you guys think?
Should I really call it a total brick? Do you think there's a way to fix it? Should I consider throwing it into Holy Water?
Notes:
-Can't get into bootloader.
-Can't flash boot
-ADB doesn't works on phone. Yes, I already had all kind of drivers since before, it just doesn't now.
-Can't get to recovery either.
Please answer, I'm lonely, I have no friends.
q.q
By the way, not an usual english speaker, please forgive any gramatical errors you may find.
Thank you for reading.
Click to expand...
Click to collapse
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Seanie280672 said:
Hold down the power button and the volume down together, keep holding them, don't let go, the lights on the bottom will flash 10-15 Times, when the phone goes off, let go of the power button, but continue to hold down the volume down button, the phone should boot back to the bootloader, devil gone, I think you know what to do from there, first get a custom recovery on there, or run the ruu which you ran before to get stock Rom back on it.
Click to expand...
Click to collapse
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Fain11 said:
Press POWER and VOLUME DOWN buttons together to get in bootloader fastboot. Try until it works.
Post a fastboot getvar all as nobody has any ideea what did u flashed...
ERASE your IMEI and SERIAL before posting the report.
Click to expand...
Click to collapse
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
Can't post "fastboot getvar all" since I can't even get to the bootloader and fastboot.
I don't think problem is anything I flashed. Last thing was the RUU, and you can trust it was 100% functional.
Hell came down after I turned off while in stock's Recovery.
Click to expand...
Click to collapse
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Seanie280672 said:
If the phone is getting to the white screen with HTC logo then your bootloader is ok, a brick is when the phone won't switch on at all, you just got to keep trying to get into the bootloader, once there, you can just run the ruu again
Click to expand...
Click to collapse
KomuroXV said:
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
If only I could find a way to the bootloader mode, I would be so happy.
q.q
KomuroXV said:
If only I could find a way to the bootloader mode, I would be so happy.
q.q
Click to expand...
Click to collapse
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
KomuroXV said:
I kinda tried this before... it just reboots before the lights actually get o flash, but I guess it wouldn't hurt to try again. I'll let you guys know if it works.
UPDATE:
Nope, it didn't work. Devil's still inside the phone. Can't even reach bootloader yet.
Also, lights never flashed. As I said, it reboots before the lights even blink.
Click to expand...
Click to collapse
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Fain11 said:
Hold down the power button untill it shuts down.
If not, press POWER and VOLUME DOWN buttons together, don't wait for any blinking lights.
Click to expand...
Click to collapse
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
nkk71 said:
@Seanie280672 you forgot the bright light
OP:
B) Force reboot
Press and hold POWER + VOLDOWN (under a bright light, not kidding!!), after about 5 seconds or so buttons should start blinking, and after 30 seconds or so, the phone will reboot, let go of POWER, but keep holding VOLDOWN to get back to bootloader.
(you may need to try 2 or 3 times to get it right)
the important part is when the phone reboots, let go of POWER but keep holding VOLDOWN
Click to expand...
Click to collapse
Oh... yes, I've heard about the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
KomuroXV said:
I'm not really "waiting" for any lights. Right now it's turned off since the battery ran out a while ago.
What I do is that I:
-Plug it to the wall charger or computer.
-It turns on, on his own.
-But as soons as it tries, yes, I am pressing the Power+ Volume Down and never let it go.
-I also tried to, when the screen is the HTC's logo screen, hold Power + Volume Down until the screen went black, then I'd release the Power button leaving only the Volume Down in hold, didn't work either.
Oh... yes, I've heard abot the "bright light" to the sensor thing. I can tell also that it actually works.
If you hold the power button with the phone in front of a very bright light, you press power button, and no matter what the problem is it would actually turn off after some time. I did it and it worked, as in, it turned off.
But I've already tried pressing Power + Volume Down with the phone already turned off (having enough battery of course), but it didn't really work either, it just went into the same bootloop again.
I'd say it is that since I turned it off while in "stock Recovery" it was in the middle of something, as soon as the phone boots, it tries to boot in recovery, but it's giving me a some kind of error though, which causes it to reboot.
Back to trying a solution, since the phone is off but charged now, I'll try turning it on with Power + Volume Down WHILE I stuck it into a light bulb or something. Could some one please tell me too where is the "sensor" of this thing is located? I don't really know where am I supposed to be facing the phone, if back, or front, or side to the light.
Click to expand...
Click to collapse
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Seanie280672 said:
2 little dots on the left front top, opposite the camera, if you have another phone available to you, use the flashlight on it, that's plenty bright enough at close range.
Click to expand...
Click to collapse
Did just that, right at those two little spots,but now the trick's not working, even though it had before, only I'm not sure if it was flashing to the two-little-spots.
Phone was charged and off. I turned it on holding Power+ Volume Down, with the phone's two spots facing straight to the flashlight.
It went straight into the bootloop still.
Are you sure it is there, and not right in the front or back camera?
Is it bricked?
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
hugof99 said:
So I decided to go running with my phone today in the morning. I used an old nike armband for iPhone, so nearly half of the phone was exposed to my arm. When I took it off, the exposed part of the phone, was sweaty, so I dried it off with my t shirt. The phone had a black screen. I tried to press and hold the power button until the phone rebooted, but all I got was a static screen for about one second. Afterwards, neither the screen nor button lights or LED indicator worked. I tried connecting the phone to the PC but nothing happened. It's an unlocked at&t HTC One m7 bought factory refurbished on ebay, running ViperOne custom ROM.
Click to expand...
Click to collapse
Well, unlike your case, my phone was actually 99.9% clean since I fixed it with the RUU. I don't think there's a ROM related issue with these reboots my phone has now.
Problem: Turned phone off while it was doing something inside stock's Recovery. Now got caught in an infinite reboot because of that,
It is actually something like this.
http://www.youtube.com/watch?v=85HtJYcVAos
http://www.youtube.com/watch?v=rai4nCciKBg
http://www.youtube.com/watch?v=W5PCJYKaCrE
Just that mine is HTC One, and, well, besides from that screen it's also rebooting on his own every 8-10 seconds.
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
iElvis said:
When you say you "turned it off" after selecting recovery, how did you do it?
I don't think that interrupting recovery when it's starting up ought to do anything.
Were you able to boot properly and use the phone after running the RUU?
My gut feeling is that there is some vestige of non-Verizon software on it gumming things up somehow.
You don't actually need to hold vol-down while pressing power. It will work just as well holding power until it stops blinking and then pressing vol-down as soon as the screen goes black. But you're saying that holding power down does nothing at all? It's just stuck in a continuous bootloop?
Have you tried seeing if it shows up in ADB?
Click to expand...
Click to collapse
Just as it sounds. I pressed down the power button to turn it off while Recovery was starting, and soon after that, the infinite bootloop started.
The RUU was 100% good, and I tested everything I could before trying to flash a ROM again.
But, just in case, it was this one:
http://www.htc1guru.com/2013/11/verizon-ruu-zip-1-10-605-10-posted/
Anyway, as I said, after I checked everything around the phone, I went to bootloader, clicked recovery by accident, and on reflex turned it off pressing down the power button.
Since then, there's been an infinite bootloop, rebooting every 8 to 10 seconds.
Sadly, and I guess it's because it was freshly flashed from a RUU, I can't access through ADB either.
q-q
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
iElvis said:
Since it's powering on, your phone should be fixable, but that doesn't mean it's going to be easy.
I think the reason you're getting this bootloop is that it's trying to get into recovery--trying to complete the command you started--but something is preventing recovery from starting up. You likely did corrupt something by hard-rebooting in the middle of the process.
Fixing it will likely require some advanced methods in Linux. There is an unbricking thread in General--I would check in there for help.
Edit: It's in the Orginal Dev forum: http://forum.xda-developers.com/showthread.php?t=2770684
Click to expand...
Click to collapse
I've been trying to do this for days on my own (couldn't get help) but I finally managed to install a Unbuntu and run the sudo ./revive.sh
[email protected]:~$
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ chmod +x revive.sh
[email protected]:~/Downloads$ sudo ./revive.sh
HTC Unbricking Project M7_UL 0.6beta
Detecting bricked device..
Device can't be found, check connections. Aborting
The phone is actually connected to an USB 2.0 port, rebooting on his own still, but connected.
It's not detecting it though.
:/
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
Hey,
so I was running cm13 (some version from november) and i wanted to go back to zui so i restored a backup that i created when i first got the phone. i booted into twrp, pressed on restore and selected my backup. after waiting for the backup to restore i saw that the process failed. then i pressed on the return to system or whatever button and now my phone wont boot anymore. when i hold power it just vibrates and the notification led flashes once. when i plug it in to charge the notification led doesnt light up. also when connecting it to my pc it is recognized (sound when you plug something in/out) but its not recognized as a phone or storage. what do i do?
Hi,
small question.
Did you do a full wipe?
Please delete system and data partition.
Because you come from cm13 to stock.
Are you able to enter fastboot? Press and hold volume down button and then hold the power button. Alternatively if your phone is off just unplug it and leave it for a few minutes, then whilst holding just the volume down button plug it into your PC and then check with "fastboot devices" in your terminal (I'm assuming that you do have adb and fastboot tools on your phone since you had a custom ROM).
@djsven I just went into twrp and tried to restore my back up not more not less. I cant delete the data and system partition as my device isnt turning on and my pc doesnt recognize the phone as a storage device.
@Uivalf39 by holding volume down and power button i cant enter. all it did was vibrate + led flash. I think its on 0% power now because holding power now just makes the led flash once (no vibration anymore). can you tell me what exactly you mean by "check with "fastboot devices"".
thanks to everyone trying to help
mdeoinko said:
@djsven I just went into twrp and tried to restore my back up not more not less. I cant delete the data and system partition as my device isnt turning on and my pc doesnt recognize the phone as a storage device.
@Uivalf39 by holding volume down and power button i cant enter. all it did was vibrate + led flash. I think its on 0% power now because holding power now just makes the led flash once (no vibration anymore). can you tell me what exactly you mean by "check with "fastboot devices"".
thanks to everyone trying to help
Click to expand...
Click to collapse
You'll first need to install adb and fastboot tools, as well as drivers for the phone and google utilities. I assume you already have these since you must have unlocked your phone and flashed twrp to install CM13.
Sending the "fastboot devices" command through an adb/fastboot enabled terminal will show you if your phone is fastboot-enabled. Your phone is bricked, the only way to go back to the original software is to follow the guide (available both here and on zukfans), TWRP backup won't work with stock ROMs.
Don't worry though, you should be able to recover it, but it'll be a lot of trial and error.
Have a read through here and here and here, seems like a lot of good troubleshooting material for bricked devices.
Let us know how you get on.
My phone was recognized as QUSB_BULK in device manager. i installed qhsusb drivers and now its in ports and its called "qualcomm hs-usb diagnostics 900e (com10)". trying to find out what to do now.
mdeoinko said:
My phone was recognized as QUSB_BULK in device manager. i installed qhsusb drivers and now its in ports and its called "qualcomm hs-usb diagnostics 900e (com10)". trying to find out what to do now.
Click to expand...
Click to collapse
Oh dear, from the stuff I found on Google, it sounds like you'll have to disconnect the battery to force the phone to shut down everything before carrying on.
Check out this thread on zukfans, specifically these comments: [1] [2]
This is the danger of having phones with non-removable batteries. Sounds like you might have to remove the back glass, shouldn't be TOO difficult, looks like it's just glued down without any clasps so you'll need a heat gun (hair dryer should do). Here is a guide on doing that.
If you do end up doing that, would you be willing to film it and upload it to YouTube afterwards? I can't find any video of such a feat and it would be useful for anyone else who needs to do that. Maybe even add some comments of whether there are any clasps, how long you had to heat it up, etc.
In the past I've been successful in unbricking my phones by draining them until the battery protection circuitry wouldn't allow for any more power to be drawn. This would roughly be equivalent to unplugging the battery so it might work for you depending what the phone is currently doing. If the screen comes on then you should be able to drain it, if only your notification light flashes then it's a fool's errand.
NB: The zukfans poster's step 1 was to fully charge your phone as you'll need full battery for the solution. What I described above will probably not work but there's always multiple solutions to every problem and if you're weary of removing the back you can try that, don't hold me on this, but I it shouldn't do any damage.
@Uivalf39
I managed to remove the battery connector. after putting it back in and now im trying to do the sequence i still dont understand because of bad phrasing (hold vol up then hold power then after 0.5s plug usb in? hold vol up hold power for 0.5s after plugging in? idk). all i now get is a slow flashing led when connecting it to anything via usb no matter what i press. i dont even know if its charging
mdeoinko said:
@Uivalf39
I managed to remove the battery connector. after putting it back in and now im trying to do the sequence i still dont understand because of bad phrasing (hold vol up then hold power then after 0.5s plug usb in? hold vol up hold power for 0.5s after plugging in? idk). all i now get is a slow flashing led when connecting it to anything via usb no matter what i press. i dont even know if its charging
Click to expand...
Click to collapse
After doing that, what do you have on device manager? Is it still as before with the 900e?
Alright, so from what I understand it goes something like this:
Unplug battery connector
Wait 10-15 seconds with the connector unplugged
Plug back battery connector
Press and HOLD volume up button
Whilst holding volume up press power button and hold it down
After 0.5s of holding power button plug in the usb (connected to the PC) - still keep holding the volume up and power button
Keep holding volume up and power button, and the ZUK logo should pop on the screen and phone should vibrate
Now release buttons and your phone should appear in device manager as port 9008
How did you find removing the glass back? How did you do it and how difficult would you say it was?
@Uivalf39 Im pretty sure im getting the timing right but all i get is a slowly flashing nofication led. no vibration and no logo. also my device doesnt get recognized at all on my pc i cant find it in device manager.
removing the back was pretty easy i just heated the 3 corners (the ones without a camera) on max for like 2 min each with a hair dryer. then i pushed in a plectrum and went around the edges with it.
@mdeoinko That's really strange, maybe we'll need to think a bit outside the box. What version of Windows are you using? Do you have the qualcomm/zuk/google drivers installed properly?
Here's one comment that might be useful.
Also, Francko from zukfans (main ROM guy so I guess he knows his stuff) did some trickery with the USB cable, not entirely sure what it is and how it works, but it looks like it does so you might want to look into this.
I'd say that you should maybe post to zukfans, you'll get more help there.
Godspeed my son!
@Uivalf39 damn i completely forgot about modifieng the cable brb hopefully i can fix it now
@mdeoinko
Hiya, any update? Hoping that your lack of posts means that you solved the issue and no longer need help. If so, could you post here what you did to solve it? Such that anyone else with this issue that comes across this thread might know what works and what doesn't.
Cheers!
i need help, cant signup into zukfans giving error as spam activity, cant go into 9008 mode, tried everything accept removing back of the fone. any guesses...