Database Info

[Q] Screen won't turn on.

I've been running the latest CM10 M release for a couple weeks now. Today I upgraded to the latest modems. Everything was working great for a few hours when my phone randomly shut off and now won't turn back on.
I've tried pulling the battery and charging. Can't ever see anything on the screen although it does vibrate sometimes when I hold the power button. LED will turn on when charging.
Any ideas or suggestions?

See if you're able to boot straight into download or recovery, thus will show intact boot and recovery systems.
One other test, pull battery and with phone off plug into your PC if it shows a red light its likely hard bricked.
I had the unfortunate experience of flashing wrong kernel and bricked my phone was not going to recovery or download. However if you can get to these then it may be a soft brick and restore with odin
Sent from my VS920 4G using Tapatalk 2

One my phone got stuck
jerhurwitz said:
I've been running the latest CM10 M release for a couple weeks now. Today I upgraded to the latest modems. Everything was working great for a few hours when my phone randomly shut off and now won't turn back on.
I've tried pulling the battery and charging. Can't ever see anything on the screen although it does vibrate sometimes when I hold the power button. LED will turn on when charging.
Any ideas or suggestions?
Click to expand...
Click to collapse
Once my phone got stuck because I flashed a new recovery that wasn't compatible with my phone so each time I tried to boot into recovery or tried to turn on the phone nothing would happen. The only thing that got my phone working again was to go into download mode (Odin) by holding power, volume down and home buttona and than canceling it. from there the Rom started working again. I don't know if it will help in your case but you can always try.

That was a strange experience. Left it plugged in for a few hours. Came back, and was able to boot normally... although the battery was extremely low despite being plugged in for a few hours. No problems since then.

Congrats =)
Seems like disaster was avoided.

jerhurwitz said:
That was a strange experience. Left it plugged in for a few hours. Came back, and was able to boot normally... although the battery was extremely low despite being plugged in for a few hours. No problems since then.
Click to expand...
Click to collapse
Do you know what percent your phone turned off at? Around what percent? Was it 23-25%?

[Q] Rebooting phone causes pseudo-brick

This is going to be a long question/story thanks for your patience!
Whenever i try to reboot my phone, regardless of method, it takes an elaborate set of actions (elaborate as in it requires a power cord, a complex series of button presses, chanting, chicken blood, etc...) for the phone to turn back on.
I'm going to include a lot of details, relevant or not, i cannot decide.
I was using SlimBean Build 7 for weeks. I was able to reboot normally. I had heard about an app, WifiKill, installed it, caused short lived havoc at work, no issues so far. A few hours later, I attempted to tether my laptop using the hotspot function (something I've done many times before with no problem). The wifi turned off immediately and would not come back on. My exact thought was "Huh, that's weird" and attempted to reboot the phone, it seemed to shut off normally but did not come back on. At this point i believe the battery was at 60% or close to it.
No matter how I tried the phone would not power back on.
I charged the phone over night, and it actually came back on. Of course the first thing I tried to do was reboot the phone. Same result.
Now the phone is still not starting when turn off or rebooted with the power button command, it will not reboot when done with adb, it will not reboot when I try within the recovery. Any of these things cause the phone to act as if "hard bricked" with no response from any of the buttons or screen.
My first thought was to flash a stock rom with odin, when i plugged it into my PC (windows 7 ultimate 64bit) it asked for QHSUSB_DLOAD drivers. I tracked those down and installed them of course they did not work for odin.
I ordered but have not received a download mode jig.
I thought maybe it had to do with the act of charging the phone that sparked the brief show of life so i drained my battery using another phone and then charged it in the skyrocket for two days. Battery at 100% at this point.
At this point, I've discovered that if I hold the power button long enough while plugged in the phone will vibrate over and over until the button is released and by accident I learned that if i unplug the phone wile doing it's little vibro-trance it will start normally.
If I try to reboot the phone with any of the methods I listed above, I have to pull the battery, wait 10 minutes, plug in a power cord (not connected to a computer) hold the vol+ and vol- and power buttons, wait till it starts buzzing and insert the battery, if the charging icon appears the phone will power on, if not, I have to start again.
Once I learned that trick I was able to boot the phone into download mode and flashed back to stock JB and twrp.
I have since flashed slimbean build 8 and twrp 2.6.0.0. The phone is working fine but I don't have the guts to attempt WifiKill, tethering or reboot.
If you're still with me, good on you. I think the universe is mad at me for messing with people's wifi connection.
Anybody got any ideas?
THANK YOU!!!

ilike3point14 said:
Anybody got any ideas?
Click to expand...
Click to collapse
Yeah, I'm guessing that wifi kill app had something to do with it. I've tethered on slim bean 7 & 8, so I doubt it has anything to do with that or the ROM. Is say it's like you said, karma rearing its ugly head for playing wifi gatekeeper on unsuspecting individuals
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

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?

Galaxy S7 won't turn on but will charge(kinda)

I've had this phone for about 2 months now, and from the beginning, it's had an issue where it would randomly freeze, restart, and get stuck in a boot loop for random amounts of time. Sometimes it would be fine after 2 minutes, sometimes it would need 10. I kept thinking this was a firmware issue - the phone WAS rooted with TWRP installed, but none of my past phones have had this issue and hardly anybody online seems to have had it, either - and just thought that maybe installing a custom ROM would fix it, but never got around to doing so.
3 days ago, my S7 went into a boot loop again, so I just decided to put it down and let it do its thing. After 20 minutes, however, it still wasn't booting, so I booted into TWRP, and cleared the cache and Dalvik cache. Another 20 minutes later, I went into panic mode and started doing Nandroid backups of my stuff. I decided that I had no other choice but to commence with finding a ROM to replace stock. In the meantime, I just plugged it in and let it keep looping, hoping against hope that it would just fix itself like it always did.
About half an hour later, I was ready to install the ROM I'd decided on. I went and picked up my phone, but all that I saw was the screen was black, and the blue notification LED was lit up. I tried holding Vol- + Power to start booting it into TWRP, but nothing happened. The phone didn't vibrate, the screen didn't change, and the LED stayed lit. I tried holding every button combination possible, for even as long as a minute, but the phone refused to respond. I tried plugging it into my computer, but Windows didn't detect anything.
Skip to today, and the phone's battery has long since died(the LED isn't lit up, so I can only assume...), and I just decided to plug the phone in for the hell of it just to see if maybe it would maybe work again. To my astonishment, 2 minutes later, the battery icon came up on the screen, but the charging animation wasn't there. When I held Vol- + Power, the phone actually responded and restarted! Though, it wouldn't boot past the Galaxy S7 splash screen, and when I tried to boot it into TWRP, it went back to being a brick. I let it sit for about 10 minutes, plugged it in, and this time tried to get it into Download Mode, and it worked!
I downloaded the Switzerland version of the G930F firmware, flashed it in Odin, and everything seems to have worked. Odin says it succeeded, but when the phone tried to restart, it got to the splash screen, and after a few minutes, the screen went black again. When I plug it in now, the Galaxy S7 screen will come up, but now I can't seem to get into Download Mode anymore(though, it DOES still seem to respond to me pressing Vol- + Power).
Does anyone have any idea what's going on? I can only seem to find 3 or 4 other threads on various forums about this problem, but none of them have any answers. People just keep saying the usual "Hold Vol- and Power to make the phone restart", but in case I haven't made it clear, THAT ISN'T WORKING.
And before you suggest that I return it to where I bought it for a replacement or refund: I bought this phone on eBay from a seller who said it was in pretty much mint condition. When the phone arrived, there was not a dent or scratch anywhere on the phone, even around the charger port, so I have no reason to believe he was lying. When I asked him about any possible problems with the phone's operational stability the other day, he says he tested it for about 2 weeks, and that he didn't notice anything.

Sounds like a hardware fault, not much else you can do other than flashing stock and factory resetting, which you've done
Considering it had a fault from day 1 it sounds like that fault finally caught up with it
Likely scenario if sent for repair, new motherboard replacement needed

Rooted Pixel 1 won't turn on, isn't responding

I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?

alienjon said:
I purchased my Google Pixel (first generation, regular (ie: not XL)) about a year and a half. It's been rooted for most of that time and I recently updated to Pie. When I woke up this morning I found that the phone had restarted on it's own. After a few minutes I noticed that it was running slowly and, eventually, to the point of non-responsive. I forced the phone off (held the power button until it turned off) and turned it back on. It seemed to load okay, but a few minutes later the phone was off again (which it did on it's own) and I cannot turn it back on. Holding the power button doesn't do anything and plugging it into be charged doesn't show any indications that the phone is charging. I haven't installed anything in at least a week and until this morning I didn't notice any problems with the phone. Any thoughts as to how to get the phone back on and what the problem might be?
Click to expand...
Click to collapse
See if you still can get your phone into download, fastboot or recovery mode. Here you can see the button combos: https://m.youtube.com/watch?v=YFaq4g-oa2Q
If you can get to recovery mode, click on wipe cache and reboot. If your phone still is stuck afterwards, go to recovery again. There is an option to wipe and reset the phone. Note that your data will be lost!!! Do it at your own risk. But a reset often is the last working choice when your phone behaves strangely.
If you get none of the three mentioned modes to work, I think your Pixel has a hardware fault.
Hope this helps.

check the charging port first....whether it is charging or not......try to connect to PC
i guess the phone is not charging

So the bottom line is this is still somewhat ongoing, though I’ve confirmed the phone is definitely bricked. I brought it into UBreakIFix and after taking it apart (noting that the device seemed physically in great shape) that there wasn’t anything obviously wrong with any of the particular hardware (they mentioned that replacing the motherboard would likely do it, but it would be about as expensive and effective as buying a new phone anyway...).
I ended up writing back to Google and am in back and forth talks with them now. I’m not sure what they can or will do, but my final answer will have to be getting a new phone one way or the other.