Database Info

Dead photon?

Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance

Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger

Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.

Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened

kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.

This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.

kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?

arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.

kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.

arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom

Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.

kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.

Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot

kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.

http://i.imgur.com/3XYLngJ.png

kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?

Yes

Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.

I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

Blinking Logo phone not working.

Please help my phone is confused like it is blinking lg logo but not getting on. In charge it gets on but in few seconds it gets off.

I think you are in soft brick state for some reason.. Did you try to do anything prior to this situation?

How did that happened? Similar issue happened to me, heres my post from other thread:
My H955 suddenly rebooted and it keeps on bootloop. It turns on fully and after 10-30 seconds (the hotter it gets, the less time it stays booted up) reboots again. After I left it to cooldown, there was error that root is gone or smth like that, and I had to agree to EULA and terms&conditions but the phone rebooted again. Maybe some kind of update was pushed in or whatever. This is the first time for me to happen. I have not installed new apps or mods on my phone like in two weeks.
Btw, seems like this is soft reboot, because there is no sounds and it didn't asked for SIMs PIN. I guess it has something to do with xposed..
I have used this method http://www.hard-reset.mobi/lg-g-flex-2-hard-reset/#to do factory reset. It seems to work, however phone still reboots. @mnshkpr8 try this to do factory reset, maybe this will help you.
Later I will try this http://forum.xda-developers.com/g-flex2/help/to-unbrick-g-flex-2-ls996-t3286105

Hi. I have similar problem here.
My phone wont pass LG logo if without charging on, the phone keep booting.. And if i charging on the phone just works fine, but if i plug out the charger the phone just turn off and restart again. Mine still using stock rom. Any suggest ?

This happened to me today as i edited one system file so I could get any app on split screen, I used flashtool and flashed the same kdz in normal mode, It flashed and everything is normal again.

any solution to this?

VS995 How to stop the vibration temp fix

I have found that if you hold the volume up and down buttons on the phone and press the power button at carrier boot the device stops vibrating.Give it a try I know its not a permanent fix but thought it might help some of you

Does not work for me.

pspbyer said:
I have found that if you hold the volume up and down buttons on the phone and press the power button at carrier boot the device stops vibrating.Give it a try I know its not a permanent fix but thought it might help some of you
Click to expand...
Click to collapse
i did this before and some times end up in safemode, just let it vibrate it wont hurt anyhting and i know cause i do that root method for videos and most of the time i work on my phone, do new things, test etc.

I rooted the phone and it was all good.
It started to vibrate after i installed all my apps and set everything up.
Reboot>Vibrate.
WTF ?

tonycstech said:
I rooted the phone and it was all good.
It started to vibrate after i installed all my apps and set everything up.
Reboot>Vibrate.
WTF ?
Click to expand...
Click to collapse
The vibrate is only on this device once you root it sucks after you get past the static boot just hold the power button & it'll go away

astonmartin214 said:
The vibrate is only on this device once you root it sucks after you get past the static boot just hold the power button & it'll go away
Click to expand...
Click to collapse
Am sorry i dont understand what you talking about.
Cant you use some punctuation ? I am seriously confused.
Phone is rooted.
No static (flashed VS995_reStock_v1.2.zip in TWRP, thats what fixes it) and it vibrated thru the rooting process and stopped once rooted.
i went thru setup wizard and installed all apps etc. Restarted the phone and it started to vibrate again.
Not to mention, the big warning sign (corrupted or something) was apearing on the screen at boot, cycling thru LG logo and back until it finally booted. It vibrated all the way and never stopped.
I flashed stock firmware 13A back on it and vibration went away, but so is the root.

Another Black Screen, Another New Problem

So I was just doing some hardware tuning using Kernel Adiutor to save battery, restarted, and it booted up (I was using apply on boot obviously) and was running very slowly. I tried to change the settings, but the phone froze. "No problem", I thought as I rebooted via adb command. It reboots and I cancel the apply on boot, and it freezes after five minutes. I reboot again, freezes again. Reboot, freeze. This happens about 6 or 7 times , each time freezing sooner than the last. Then, it freezes one last time, then the screen goes black. I try reboot and reboot to bootloader/recovery with hardware buttons with no success. So I assume it powered off, but I should check adb first. I ran the devices command and it showed up as active. I ran all basic reboot commands and those just sit there and never complete (I sat here for 20 minutes waiting for it).
I also thought it may be stuck in Android with no display, which I've had happen before on another S7, but it doesn't respond to touch or hardware buttons, and doesn't show up in file explorer (I have screen lock off so it shows up even when off normally).
So then I thought it may be stuck in bootloader with no display. I open up Odin and it recognizes the device, but won't flash anything at all.
Also, this device has never been dropped to my knowledge, and has no cracks, so I doubt it's hardware damage.
I've tried everything I can think of, and Google yielded no results thus far
TL;DR
Messed up with Kernel Adiutor and the screen went black after multiple reboots and freezes
Tried hardware reboots and adb reboots
The device shows up in adb and Odin, but not in file explorer (no screen lock, usually shows up even with screen off)
Odin cannot flash anything, so it's not in bootloader
Other Info:
It's obviously a Galaxy S7
It was originally a Sprint phone (G930P)
It now has Unlocked firmware (G930U)
It is also running engboot for root permissions
I have some previous experience with engboot with my other S7 and have had no problems after 2 years rooted
Any help at all is appreciated
Edit:I'm an actual idiot and didn't know about force reboot (power and vol. down for 10 sec.) and that worked :/