Database Info

My quest for a new power button with a twist!

So my story begins with me purchasing a used white Nexus 5 for $155 from swappa over a week ago for my wife. *
Phone arrives in perfect condition.
I first unlocked and flash twrp via adb. I proceed with installing Chroma and elementalx. Spend few hours on making the new Nexus 5 the same as my wife's current Galaxy Nexus.
Phone is running great. Zero issues for about 3 days while the phone was just at home running. She throws the phone into her purse and goes to work. Within hour she calls that her phone won't stop rebooting…. *Oh no…. The dreaded power button issue… right?
So I'm assuming the seller did the old “whack against a solid object” temp fix and sold it. I have no proof of that so I'm assuming.
So what do to? Well fixing the power button is still cheaper than buying another Nexus 5 phone. Everyone one quoted me $60. It is what it is… at this point I could have gotten a refurbished phone but what can you do…
So you would think this is the end of my story, right? Wrong.
I go to a cell phone repair place close to my work. They have this tiny power button in stock and replaced it many times before. I come back later that day to pick it up and they have bad news… of course they do.
After the switch replacement, the phone did the same reboot. Goes to Google logo and reboot. If I fiddle with the power button I can get to the OS but reboot right away. The guy proceeds with that it is me rooting it that caused it and I need a new motherboard, price $100.
I started questioning if he really did replace the switch. If it was OS related, the phone would not have worked for couple days and then break randomly. It would not boot to the OS sometimes or at least it would let me boot into TWRP, right?
Long story short, I left with spending the $100 on getting this used $155 phone fixed. Super annoyed at this point.
So after this long story, is there any chance this was really OS related and not a faulty power switch or did I just got lied to and the power switch was never replaced?

For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk

Curiousn00b said:
For sure, you should've attempted to restore the phone through Google's factory images first. My power button went super wacky twice since I've had it(day 1 model). I just pulled it out, and now the problem is gone all on it's on.
When it kept rebooting, did you try booting into the bootloader at all?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I sure tried to get into recovery but wouldn't work. Just kept rebooting. I had a nandroid backup done a day before but the phone would not stay powered on for long enough to do anything. It was the equivalent of having no battery left and phone just shut down and attempted to reboot constantly. I took out the motherboard and played around with the button before I went out to repair it but it was the same results. If I "massaged" the button then maybe the phone would get past the Chroma logo and get into the OS, but as soon as I attempted to touch the power button again it would reboot.
I tried reviewing the old motherboard and unless this shop's soldering skills are top notch, I can't tell that the switch was replaced. The soldering point were identical to the volume buttons. When I questioned the store owner, he stated they are that good with their infrared soldering He took out a package of 3 Nexus 5 switches and one was missing... meaning he installed it.
I highly doubt it was OS related. If you brick a phone when flashing, then it would just be constantly in a boot loop, right? I know I can easily go into recovery and flash whatever .img I need to, but this was just nonstop reboot and different times

Damn phone stuck in bootloop!

Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.

thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).

follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...

Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.

My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app

bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????

My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app

This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.

Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?

Stuck in a bootloop, but I didn't do anything to my phone

Hello, Nexus 5 forums. This is my first post on here, because I never even tried to root or install a custom ROM on my Nexus 5, having bought it for the official updates from Google and all that stuff (I had a Galaxy SII before this phone, and I frequently visited the XdaDev GSII forums because I installed CyanoGenMod on it).
I'll go straight to the point. My phone suddenly started rebooting randomly today, and by the end of the day it was stuck in a weird kind of bootloop. The Google logo would pop up, and right as the MM boot animation started the phone would reboot and the Google logo would show up. Right now, the phone's battery is probably dry, so that's why the phone isn't bootlooping, but it has done so for 3-4 hours before shutting down. I tried opening the phone, removing the battery and putting it back in, but the phone just kept bootlooping. I tried both getting into the stock recovery and into download mode, but the phone keeps on rebooting as soon as I get into download mode.
Can I do anything to fix this or is my phone doomed to the eternal bootloop?
Thanks in advance for any and all replies.

Sounds like there may be a problem with the power button.

Same thing happened to me like 5 times now. It is the power button. What I do is knock it on the side of a table below the power button. I just need it to last until the new nexus is released, so I never investigated the proper fix.

I understand, so my problem is more a hardware than a software issue. I tried knocking the phone on the side of a table like @NicksSpleen said, but maybe my problem is more serious. What can I do to fix this? I need it to last until Christmas, as I'm going to get a new phone then (maybe the Nexus Sailfish, if the price is acceptable).

EDIT: Double post.

I disassembled my phone and fixed the problem by cleaning the power button. Works like a charm. Thanks for all your suggestions!

Anything other than the power button?

[Q] Acatel 4060a "Ideal" Stuck at Boot Logo

My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !

Silicon Knight said:
My Nexus 6P was recently broken but my GF (on accident lol but still she's lucky I love her. If it had been anyone else, like one of my guy friends, I prolly woulda had to hit em haha j/k)
Anyways, borrowed a friend Acatel 4060a IDEAL. He dropped it off last night. I then factory reset it and all that, hooked up my google accounts, downloaded WoW - Hearthstone and my Drastic DS emulator, and everything was fine. Then this morning I was bored and figured I would see about if this cheap POS is rootable. Which it is, and I proceeded to do so. Everything worked fine the whole morning, til bout 45min ago, I was leaving to run up to the AT&T store to get a SIM card so I could hook it up to my account, and on the way out the door I reset it cause I just had finished updating some apps in the play store. It then became stuck at the Bootlogo. So I then did what you always do in this case, try taking the battery out and the SD Card, then putting just the battery back in, see if that works. Didn't. Tried just resetting it a few more times, and let it sit for like 20min hoping maybe it was just taking extra long. Nope. So I then booted into the stock recovery wiped the cache and did a wipe/factory reset. Still nothing, still stuck. Tried a couple more times. Still nothing. And this phone apparently doesn't have a download mode, so I can even plug it into my laptop cause it can't make a connection obviously without being in download mode, or fully booted into the OS. I am at my wits end.
I'm hoping one of you fine peeps might have a suggestion of something I could try that I perhaps have overlooked or didn't know about. Learn something new every day right So please HELP ! lol its gonna be at almost 2 more weeks til I get paid and will be able to afford the Insurance Deposit for them to send me a replacement Nexus 6P, and I got way too much going on right now and I can't go two weeks without a phone.
I'm All Ears !
Click to expand...
Click to collapse
I'm assuming you used Kingroot to root it? It's a common issue for Kingroot to cause a bootloop.
Typically, this is fixed by re-flashing the stock firmware but you have to get it to connect to PC to do it, and that's only if the stock firmware is even available.
Sent from my SM-S903VL using Tapatalk

Phone got stuck in a boot loop but is now powered off, not sure what to do now

I have only had it for about 16 months now. It is a MetroPCS GS7 so it's a T-Mobile variant if that matters. Never been rooted or modified in a similar way. The same thing happened with my previous phone, a GS4 which never got fixed. I was just using a video downloader app when it suddenly restarted. It only shows the first screen for about 5 seconds then restarts. I have some experience using ODIN and flashing ROMs but I don't know what I should try with a GS7.
After a few tries to get it into recovery, this is what happened. The blue recovery message in the top left showed up but I didn't let go of the buttons this time. Then this rotating white circle showed up and said something like "applying system update". After about 20 seconds then I got a screen with the dead android and it said "no command" below it. Then I don't know what happened but then suddenly the recovery menu showed up. So I picked to just power off so it is just turned off now and no longer in a boot loop. I don't know what to do from here. I won't turn it back on until I get advice on what to do next.

If you just want to fix it without worrying about losing data, see if you can get it onto download mode and full a full stock flash with all 4 firmware files in Odin.
If anything is corrupt, Odin should give you an error message which might be enough of a clue as to where to look next.

OK so I flashed it once and it didn't work, it was still stuck. After that I just gave up on keeping anything and wiped all data. I flashed it a second time and it still got stuck, but after about 10 restarts it finally worked. However it is now on the T-Mobile firmware instead of the Metro PCS one and also I am having weird problems now. I would like to go back to the Metro PCS however I cannot find any firmware for a G930T other than T-Mobile. The problems I have experienced so far is the auto brightness does not work anymore, I have to manually set brightness even when it is switched on, the screen turns on for a few seconds when it's done charging now, and also I restarted my phone to fix an app and then it got stuck in a loop again. It took 10 restarts then worked again, but that is still a problem. I don't even know if I should still be wasting my time trying to fix this. I really don't want to buy a new phone right now but I also feel hopeless in fixing this one.