Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
metalheadbk said:
Hello everyone,
This morning while I was having coffee, my phone started playing jokes on me. At first it got really slow while doing the easiest things, like checking a mail, send a text and make a phone call. 10-15 After that I get a notification, Phone was locked, I tried to unlock it. I did spam the button like 5-10 times, Screen won't come up, but notification LED was working. At that point I thought that the power button was pretty much done for. Nope not the case. I held it down for 10 seconds, phone actually powered down. No chance in hell I could turn it back on. At that point I just went home. Got home plugged the phone into my PC. As soon as I did that, Windows started to check for a driver, had to wait almost 5 minutes to find QHSUSB_BULK.
Now, doing a bit of a search I found out that this could be the result of different problems, One that has to do with the memory just dying cause yeah, Nexus 5 and the eternal memory problem +Lollipop screw around with Data partitions, another that has to do with Roms, another that had to do with custom recovery.
What the hell is in my case? I run a custom Rom and a custom recovery, Atm I have Cyanogenmod 12.1 and lateste TWRP recovery.
I have a handful of tools at my disposal, a Cable, a good keyboard and a iron will.
In this case, Can I do something to fix my phone from home? Can't really send into warranty as I have custom software that's running on it and I'll just get a generic response that basically tells me that my warranty was voided due to custom software running on the terminal. We all love generic response like that, Don't we?
TLR: Phone died this morning, I couldn't unlock the screen and I thought it was the power button be cause, the notification led was still working. At that point I just powered it down by holding the power button down for 10 sec.
I wasn't able since to power it back on. If I connect it to my PC I get QHSUSB_BULK.
Hopefully there's some one who can point me in a direction ASAP. I have no backup phone atm and I really need this one to actually be ALIVE again.
Can't send it to Warranty because I run custom software on it. GSM Services/Fix Shops are out of the question too.
Pls halp ASAP
Will pay in Galactic Credits.
Thanks!
Click to expand...
Click to collapse
Have you tried booting into secondary boot loader?
Sent from my Nexus 5 using XDA Free mobile app
But the phone won't turn on.
jd1639 said:
Your best bet is to try this, http://forum.xda-developers.com/showthread.php?p=51823398. Good luck, your device is not in a good state.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same problem but this answer doesn't help. This solution requires that you can turn your phone on in the first place. He specifically said he can't turn the phone on at all. Same with me, no matter what I've got nothing. Need help!
metalheadbk said:
Hello everyone!
Click to expand...
Click to collapse
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
bitdomo said:
this is what you are looking for http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
leopoldstotch25 said:
Thanks to everyone.
I used the board diag - clicked Start and... it said "failed to open partition from EMMC". The test aborted. I think my phone is gone for good.
Oh and I had to take the battery out, plug it in, and sometimes re-attached to latch that goes over the battery several times before I could even get it to read anything in Device Manager. Before that it would say "failed USB connection".
This all started yesterday when the phone just spontaneously put itself into a boot loop while on charge. I tried to do a factory reset but it froze. After several hours I tried to cancel it. The Nexus went full brick.
Thanks again
Click to expand...
Click to collapse
I am afraid the emmc tied then. You have to buy a new motherboard.
Tapatalk-kal küldve az én Nexus 5-el
Thanks for your help.
Related
Dear Geeks,
I need your urgent help/advice. i'm three weeks far to my wedding and have a lot of troubles to handle, of course i need this phone.
let me describe the matter i have.
My nexus s is not booting, not starting, nothing.
what i did?
Last night, power button stopped working. I have experienced this 4-5 months ago. I don't know why, the problem has been solved by itself after few days later. i did nothing at those days. the power button came back. (as to my opinion, this is happening due to software problem) Anyway, i have used the market and installed ''fix power button'' application to use volume buttons for opening the screen.
I slept and when i woke up, i saw that phone needs to be charged but i waited. there was %11 something. i tried to handle the power button, pressed many times on it, thought that it may come back again same as 4-5 months ago it happened.
I removed battery and replaced again. i tried this many times. removed, replaced, used the usb cable via AC charger and phone started but there was no result. power button still was not working.
i thought that if the battery runs out, and then, when i charge the phone, maybe this matter may be solved. (ok this was stupid idea)
phone started to charge. when i plug the usb cable, phone was booting and displaying the google and animation and later it was ok to use.
meanwhile i keep on removing battery and replacing battery while the usb cable connected. but when phone starts to boot, i removed battery and replaced again. phone was ok, it was booting. few times it was booting.
but baaaam.
it is now not starting not booting, nothing.
now, when i replace the battery, phone is getting hot, especially sim-card area. i m removing the battery and connecting the usb. same again phone is getting hot, same sim-card area again.
i have waited enough not to connect the battery or usb charging cable. but no result.
what can i do now? what are your opinions?
my opinions/guess:
-i am using 3500 mah lithium polymere battery. maybe the battery died. i m using that battery more than 1 year, around 15 months. i dont turn off wi-fi so i m charging phone everyday.
- phone crashed during booting. and now the phone is totally brick.(i dont wanna believe this, this phone can be usable, believe me i feel it i think whatever happens, this phone can be usable via software installing or rooting... of course if you dont throw it towards a wall etc.)
by the way, my phone was not rooted. no time to root these days. and of course the phone was not starting.
what is your idea? what happened phone? what should i do?
if you reply, i will be appreciated.
A big advice for people reading this, dont remove the battery when your phone is booting.
I hope someone has a solution, since I have the same probelm...
I searched everything and tried every tool in this forum, but no success...
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
same thing has happened to me since updating from JB. Just past one year warranty too lol!
greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.
captainirmak said:
Actually, it was power button failure issue but now, i believe it is not.
But thanks i will try it.
Click to expand...
Click to collapse
what is ur theory then?
u might find something here as well http://forum.xda-developers.com/showthread.php?t=1504501&highlight=power+button+conspiracy
greg2826 said:
use search button, there is tens of similar threads...
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
Click to expand...
Click to collapse
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.
captainirmak said:
dude, unfortunately those solutions not working on my device.
when i connect charger and i replace the battery, within seconds phone boots itself without power button. it should be this way. removing and replacing the battery helped me to start to boot.
i sense this case a bit different from that solutions.
i need to try with a different battery. my wife has nexus s also. she is very lucky she has no problems i have experienced so far. i will try with her battery.
i think there is a matter with mainboard.
by the way i forgot to say that i dropped my phone last evening. just after then phone was acting that i'm pressing long onto power button. and power button finally stopped working when i remove the battery.
i think this is happened because of dropping the phone from my belly high.
but the last thing i have done which removing the battery while the phone is booting, i wish, i should not have done. i could use it without the power button.
Click to expand...
Click to collapse
If you have not rooted your device, you should have you warranty, right? Take the phone back to the carrier, and tell them about your problem. o.o Sorry, I'm of no help, but you're in a horrible situation. Wanted to at least give a little help.
Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110
Tried another battery - no luck
Did the resistor removal and converted to a dev board - Unbrickable now detects the board!
trying to get the device into fastboot - will update
ru1dev said:
Same exact problem here.
2nd of August - mom's phone turned of and just would not boot or prompt at all. The modem heats up when power is turned on or connected.
Tried
The unbrickable methods (but the computer would not detect the device in any form)
A JTAG - I was able to write the recovery and bootloader - assembled the phone and it just won't boot or prompt
Need to try
Another battery to see if it solves the issue.
Removing the xOM5 resistor and converting to a development S5PC110
Click to expand...
Click to collapse
I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.
Any update? I'm curious to see if you get it working. Had the same happen to my NS a few days ago and would like to see if I can get it going again so I can give it to my stepson.
Sent from my Galaxy Nexus using xda premium
I've given nexus s to samsung service. Actually, power button may be handled by replacing with new one, but with no hope, it will not come back when i read messages about mainboard failure. I will update news whenever it's possible.
we'll see.
I would like to hope it is kind of software matter.
Pls god give my nexus s back, i got extended 3500mah battery.
grrr....
anshumandash said:
I had the same problem few months ago. Power button had died. While I was able to boot with remove battery and connect to charger option and I was rooted. But after a week I decided to take the phone to Samsung service center to get the power button replaced. My phone did not have warranty. Samsung took few hours to get the power button replaced and it costed me about $7. I think that's the easiest method. They did not have a stock of I9020 power button, so they fixed a I9023 power button.
Click to expand...
Click to collapse
So with the hardware mod - instead of selecting Nexus S -> I tied the Galaxy S in unbrickable - first time I've seen the screen alive! - puts the phone into download mode and I can disconnect from the usb and it stays in download mode! .. when i tried to flash odin I get a "There is no PIT partition" error -> this ofcourse is with re-partition and bootloader update UNCHECKED
When I tried Heimdall it wouldnt let me flash without a pit file. So trying Heimdall 1.1.1 - I get Failed to Access device Error: -3
Any chance some one with an i9020T can do me a huge favor? Use Heimdall 1.3.2 - download your PIT file and upload it here?
reaching for string ends out here :/
@ru1dev
i`m in the exact situation right now...
did you solved your problem?
jokkergsm said:
@ru1dev
i`m in the exact situation right now...
did you solved your problem?
Click to expand...
Click to collapse
The power button had to be replaced. I shorted the connection when ever I had to press the power button during the boot sequence. That's how I fixed mine.
i have a nexus s 4 g from sprint. it is hard bricked. i tried to root it and change recovery.then it shut off and wont power on, light up at all. I would like to know if i am able to achieve download mode, what do i need to do, what files and how to install to return this phone to stock?? please help!!!
Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849
kozmo2k4 said:
Take out the battery for a few seconds and put it back; then while holding Volume UP (+) press the Power Button.
See what happens...
One helpful tool is found here:
http://forum.xda-developers.com/showthread.php?t=1984849
Click to expand...
Click to collapse
Nothing. Happens it don't light up or power on at all. It is not reconized on computer either. It's hard bricked.
Make sure the Battery is charging...
How can I make sure the battery is charging when no lights come on at all? All I do know is I had it plugged in for a while yesterday and it got really warm. But no lights whatsoever. The screen doesn't light up at all neither does the led.
??????
There are no notification lights on the D720, but when you plug it in with a charger, you should see a battery bar on the display.
Other than that, you are probably right about hard-brick.
I, luckily, never had a "brick" on the Nexus S, so someone else with experience may wanna chime in. But Google and YouTube are your friends.
Sorry...
Sent from my NookColor using Tapatalk 4
Hey man, did you have any luck with this? I'm experiencing the same problem.
Talal916 said:
Hey man, did you have any luck with this? I'm experiencing the same problem.
Click to expand...
Click to collapse
Please help me, i have the same problem
been awhile since any action here. saved mine with JIG method once but this time it won't work ??!(why) , in search of a solution again! -> hardbrick #2 on this device!
You guys can try a USB Jig. If that does not help, I think JTAG is what you need.
Jesus... just to revive this thread (and this concept of hard bricking), I think I just accidentally bricked mine as well.
Here's exactly what I did:
One moment, it was working spectacularly - fully stock, but unlocked. I had just listed it on eBay, too.
So I ran a factory reset on it (from the Settings menu), also "erase USB storage".
Then, after it shut down for the reboot, I pulled the battery.
...
That was it. Now it doesn't turn on for anything whatsoever. No device detected on USB when plugged into PC. Remove, replace battery, hold VolUp+Power, nothing. Plug into power adapter, nothing. Nothing at all.
But the back does get lukewarm after a minute or so, as if it's alive in the head but frozen, unable to start the bootloader.
WTF? I also have 2 more of these Nexus S 4G's, and both of them seem to have Flash storage chips that exhibit the same behavior when their chips are placed in (this) working motherboard. They can't boot. When I try to "hot-flash" it by booting the bootloader then swapping the Flash chips, they can't flash anything (this is probably to be expected). So, if I can get my ONCE-WORKING phone back to life, there's a good chance I can get another working as well (one just has a cracked glass, otherwise working mainboard & peripherals).
It's old, yes, but it's a damn shame to E-waste these things for a stupid software problem like this!
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.
Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.
I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.
In my mind, this validates my decision to go over to the CM11 nightlies and never look back.
Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.
I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk
It isn't necessary to hold both volume keys, just volume up and power.
Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.
andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.
This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.
This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app
Sounds like SOD.
Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
http://youtu.be/FEixpssggCY
What if you boot it pressing vol up + vol down + power?
Sent from my Nexus 5 using XDA Premium 4 mobile app
J.Diogo said:
What if you boot it pressing vol up + vol down + power?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If on battery, then the phone does nothing. If plugged in to charger and the key combination is tried then the phone keeps on doing as shown in the video.
Don't know what's going on.
Try doing that but with the phone connected to a PC that has adb and fastboot installed.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I would leave the phone plugged in for an hour and don't touch it. Then try.
Trust me.
1ManWolfePack said:
I would leave the phone plugged in for an hour and don't touch it. Then try.
Trust me.
Click to expand...
Click to collapse
Tried that already. No change. Any other ideas?
steelbreeze said:
Tried that already. No change. Any other ideas?
Click to expand...
Click to collapse
You have a fauilty or a stucked power key.
If it is just stucked then you can unstuck it by abusing the power key or taking the phone apart.
If it is fauilty then you have to claim your warranty.
If you disassemble the phone you will void your warranty
bitdomo said:
You have a fauilty or a stucked power key.
If it is just stucked then you can unstuck it by abusing the power key or taking the phone apart.
If it is fauilty then you have to claim your warranty.
If you disassemble the phone you will void your warranty
Click to expand...
Click to collapse
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.
steelbreeze said:
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.
Click to expand...
Click to collapse
Then you have to visit that local repairer guy pay him to replace the power key again or pay LG to replace the mother board.
steelbreeze said:
A few days back, she had got the power button fixed because the power button response had become intermittent and the phone was rebooting randomly. She had taken the phone to a LG service center first, but they told her that changing the button or trying to fix it might damage the board and told her to change the board altogether. So we took it to a local repair guy who fixed it and the phone was working fine till yesterday when it shutdown all of a sudden and then the rest is history.
Note: The phone is not under warranty as the phone was bought from Dubai and we stay in India. No international warranty.
Click to expand...
Click to collapse
Yeah the repair guy you dealt with must have fixed the button short-term but in doing so inadvertently caused it to short out. Meaning it needs to go back to a repair shop (better one) and cross your fingers that it didn't short out more important components
bitdomo said:
Then you have to visit that local repairer guy pay him to replace the power key again or pay LG to replace the mother board.
Click to expand...
Click to collapse
kbroh said:
Yeah the repair guy you dealt with must have fixed the button short-term but in doing so inadvertently caused it to short out. Meaning it needs to go back to a repair shop (better one) and cross your fingers that it didn't short out more important components
Click to expand...
Click to collapse
Okie. Will take the phone to LG tomorrow or over the weekend.
Guys please clear my one doubt. If it's the stuck power button, what does it have to do with the phone not doing anything when on battery but decides to go till 'Google' when plugged in?
steelbreeze said:
Okie. Will take the phone to LG tomorrow or over the weekend.
Guys please clear my one doubt. If it's the stuck power button, what does it have to do with the phone not doing anything when on battery but decides to go till 'Google' when plugged in?
Click to expand...
Click to collapse
My phone behaves the same way if I constantly press the power button
steelbreeze said:
Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
Did you get it fixed? I have the same issue and I've tried many ways to bring it back to life. My last step will be taking it to the tech support, because I live in Brazil, and I'm pretty sure they will charge me expensively as hell.
Click to expand...
Click to collapse
hebert_hrs said:
steelbreeze said:
Guys my gf's Nexus 5 shutdown today and just refuses to boot up. It doesn't do anything with any of the keys pressed in any of the combinations that are defined. But once it is plugged in to the charger or USB, the google logo pops up and the phone keeps on rebooting to that logo. If the volume down key is pressed when this is happening, the fastboot mode is visible for a second and the phone keeps rebooting. No action can be done in the fastboot mode due to the quick reboot. I am attaching the video of the problem. Any help guys?
Did you get it fixed? I have the same issue and I've tried many ways to bring it back to life. My last step will be taking it to the tech support, because I live in Brazil, and I'm pretty sure they will charge me expensively as hell.
Click to expand...
Click to collapse
I'm in the same boat, unfortuantely i'm at a loss in what to do, i'm going to send it back to Google and await a replacement, meanwhile i'll get my hands on some cheap old phone for now.
Click to expand...
Click to collapse
Had my Nexus 5 for about a few month now, and have loved it till this morning, it decided to just shut off (full battery too) and i tried to turn it on and it is now just constantly starting up to the "Google" splash screen then shutting off.
Sometimes it gets to the the 4 color circles then shuts off.
I want to enter into recovery mode, but I have no time to click recovery mode as it reboots frequently
One thing i noticed when it did boot up was the power button seems to be extremely sensitive and volatile
I had this same problem.. It constantly rebooted and wouldn't let me get into recovery.. Every time I plugged in the charger it would reboot also. You have to let the battery completely drain.. I gave it a couple weeks.. then tried it again and it worked.
Found a solution
Well same thing started to happening with me yesterday after installing android L's developers' preview in my nexus 5. It worked well for first 4-5 hours but then after terminating a phone call when I put it back to my pocket problem started. I searched many forums for solution then I decided to re-install from image. I connected my phone to My PC (Which had driver installed & fastBoot setup) dramatically my phone started working well. And I detached my phone from PC. So I thought it might solved because after supplying charging. But after 3-4 hours it started again so I directly plugged in to electric socket but it kept on rebooting. Then I turned on my PC and attached my nexus 5 with it. Again it started dramatically.
Still I don't know the exact reason behind it. But good new is my phone is still working since last 16 hours... But I took care of not to launch some apps listed risky for developer's preview. So I thing some incompatible app launch may be a reason... but still its only "may be"
---------- Post added at 05:46 AM ---------- Previous post was at 05:42 AM ----------
dueltothedeath said:
I had this same problem.. It constantly rebooted and wouldn't let me get into recovery.. Every time I plugged in the charger it would reboot also. You have to let the battery completely drain.. I gave it a couple weeks.. then tried it again and it worked.
Click to expand...
Click to collapse
If it happens again try what I just answered and let us know if it worked for you? So we can come to know if solution was nexus 5 specific or android L specific. Also mention the OS version, please.
hbb20 said:
Well same thing started to happening with me yesterday after installing android L's developers' preview in my nexus 5. It worked well for first 4-5 hours but then after terminating a phone call when I put it back to my pocket problem started. I searched many forums for solution then I decided to re-install from image. I connected my phone to My PC (Which had driver installed & fastBoot setup) dramatically my phone started working well. And I detached my phone from PC. So I thought it might solved because after supplying charging. But after 3-4 hours it started again so I directly plugged in to electric socket but it kept on rebooting. Then I turned on my PC and attached my nexus 5 with it. Again it started dramatically.
Still I don't know the exact reason behind it. But good new is my phone is still working since last 16 hours... But I took care of not to launch some apps listed risky for developer's preview. So I thing some incompatible app launch may be a reason... but still its only "may be"
---------- Post added at 05:46 AM ---------- Previous post was at 05:42 AM ----------
If it happens again try what I just answered and let us know if it worked for you? So we can come to know if solution was nexus 5 specific or android L specific. Also mention the OS version, please.
Click to expand...
Click to collapse
Thats very strange..since it started happening to me since yesterday. I managed to flash it again (and that i suppose should have cleared everything) but problem persists. Ill now try to restore factory image.
same thing happened with me one month ago............tried everything except opening it up and finally i got it replaced.................you cannot fix it on ur own take it to a service center asap........thank me if this helps!!
ironclad1911 said:
same thing happened with me one month ago............tried everything except opening it up and finally i got it replaced.................you cannot fix it on ur own take it to a service center asap........thank me if this helps!!
Click to expand...
Click to collapse
Thanks. I restored it to the original nexus 5 build - but nothing seems to fix the problem. will reach out to service center.
For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
sounds as your power button is "stuck'.
Try the LG RMA. Worked for me here in Belgium
brom25 said:
Try the LG RMA. Worked for me here in Belgium
Click to expand...
Click to collapse
Where did you both your Nexus, and in which country did you send RMA request?
DTFuser said:
For quite a long time I did not make any change on Nexus ROM or applications, but yesterday my Nexus turns off while I was web browsing. I tried to turn it on but it refuses. It is only possible with USB cable plugged in, but then it constantly turns on for 1 second and then turns off, and this is going in endless loop as soon as USB cable is plugged in. But with unplugged cable NEXUS can not be powered on.
The video can be seen on this link
https://www.dropbox.com/s/cvyxii4ctm4aqgu/VID_20141110_190522.mp4?dl=0
Yesterday I somehow manage to get in recovery mode and I wipe cache and Nexus boot ROM, but after 30 minutes of usage it again turns of by itself. After that for more than 100 times I tried to get to recovery mode but I could not.
So, I think that my only chance to wipe cache and put new ROM is through ADB. But I do know how to do that. Can anyone help me?
P.S. I both my NEXUS in US, but I live in Croatia (EU) and Google tells that they can not make exchange for other NEXUS (although my phone is under warranty) because they can only do that for postal address inside US. Because I do not live there and any of my friends or relative will travel in US soon my only way to get my NEXUS working is through ADB.
Click to expand...
Click to collapse
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
topgeardave said:
Shake your phone vigorously for a minute, I've been using that as a temp fix for a dodgy power button exactly as you've described
Click to expand...
Click to collapse
And what you did after shaking? I try but I did not helped.
DTFuser said:
And what you did after shaking? I try but I did not helped.
Click to expand...
Click to collapse
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
topgeardave said:
It usually helps the button back out again, I think you should RMA to LG, I'm sure they're worldwide. You could always open up the phone and try unsticking the power button if you can't be bothered sending it back.
Click to expand...
Click to collapse
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes of working phone turns off and now I'm not able to get even into recovery.
DTFuser said:
Power button is not what cause the problem. I found many reports about the same problem, like on this page
http://www.reddit.com/r/Nexus5/comments/29tr5n/nexus_5_wont_turn_on_google_screen_keeps_flashing/
but nothing which I tried did not helped. But certainly power button is not causing the problem.
When the problem appears for the first time I manage to get into recovery and wipe cache, and after that phone booted ROM. After 30 minutes ow working phone turns off and now I'm not able to get even into recovery.
Click to expand...
Click to collapse
Ah damn, sorry to hear mate. Go to LG, only solution you have left.
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
meechieballer said:
im in the same boat my phone was just working for the past since i had it and now just like 20 minutes ago it just shut off and now doing the constant turning on and off crap
and im rooted with the latest build from pac-man (a clean install), cant even get into the fast boot and recovery to recover to stock since its doing this bootloop thing
any more help would be amazing
Edited - problem fixed it was something up with the power button, got a couple hard wacks and it booted up perfect
Click to expand...
Click to collapse
So, since shaking, hard wacks, and anyting physical did not helped after your post I dismantle my phone and without back plate and upper plate on chips my phone works perfectly. So it seems that upper plate which covers chips is the cause of the problem.
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Dancsi said:
For me, not even disassembling has helped, so I bought another motherboard and put it into my phone.
Click to expand...
Click to collapse
the problem occured and i found what it was my power button it wasnt staying in place like its tilting so now i got to buy a new button for it :/
As far as I remember, the button is soldered to the board, and can not be bought separately. I know the second thing for sure, since I was also only searching for a separate button in the beginning...