Related
WI don't know what happened (really, I don't) but last night something really strange happeend to the phone.
I wasn't even using the phone or running any apps (heck, even background data was turned off) and the next thing I know, my girlfriend points out something weird on the screen: my phone had gone into a recovery-like screen. It had a picture of a phone and a red triangle with a exclamation point. Red, I tell you. After more than a year tinkering with Android, I had never seen a red one sign. Also, what the heck? It just reboot into that screen by itself, it seems.
Wish I could explain where it came from, give you a log or show you a picture but none of these I can provide. All I can tell you is the image of a phone with a red exclamation point.
Happed to my girlfriend phone don't know why she was at school when it happened....
Sent from my T-Mobile G2 using XDA App
This happened to me this morning. My phone was just sitting there doing nothing. I came out of the shower and was like ? Its a little concerning. I have a trouble ticket open with tmobile about my reception issues so next time I talk to them I'll bring it up.
phazedplasma said:
This happened to me this morning. My phone was just sitting there doing nothing. I came out of the shower and was like ? Its a little concerning. I have a trouble ticket open with tmobile about my reception issues so next time I talk to them I'll bring it up.
Click to expand...
Click to collapse
Let us know what's up, see if they know what it's about. I have no idea what it was, it was surprising.
I'll see if I can exchange mine for another one this week, I think.
Umm details? How long did it stay on this screen? What did it do after? Reboot, power off, ect. Did you do anything after? I can't offer any answers but anyone that can needs this info and ill be watching mine for the same. You never know this could be an exploit path.
It went all by itself to this screen. It was set on a table, doing nothing. Only telephony was turned on (meaning only phone calls or text could come in); data, BT, GPS, and WiFi were turned off.
It stayed on this screen until I decided to reboot it. It seems to have been on this screen for a while. I did a hard reboot (Power + volume down + trackpad).
rmcsc said:
It went all by itself to this screen. It was set on a table, doing nothing. Only telephony was turned on (meaning only phone calls or text could come in); data, BT, GPS, and WiFi were turned off.
It stayed on this screen until I decided to reboot it. It seems to have been on this screen for a while. I did a hard reboot (Power + volume down + trackpad).
Click to expand...
Click to collapse
Same here, it happened just as i plugged it in last night and I freaked out since I haven't seen that screen before (rooted my G1 two winters ago) but I thought I did something until I read your post. No updates though.
is it possible that maybe that update pushed out to yalls phones without needing approval and it was in recov for a second from it??? just throwing that out there, otherwise im clueless.
User needs to give the phone the approval for update to start. No way in hell this was an update.
rmcsc said:
User needs to give the phone the approval for update to start. No way in hell this was an update.
Click to expand...
Click to collapse
Too lazy to dig it up now, but I recall that there is a provision to make a FOTA update forced install, even possibly w/o user intervention. However I don't think this has ever actually been utilized before, and neither would I expect the update background to use a red exclamation mark.
Logcat of one of these "red exclamation mark" devices would be useful.
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
franshu said:
Hi all,
My first post here and I'm posting it at a pretty depressing mood.
I've just bought my phone from the states and brought it back to Hong Kong for my own use. Last night, I've been toying it for a couple hours with everything going perfectly fine, but suddenly the phone turned itself off. Everytime I try to turn it on the phone just turns itself back off again. I couldn't do anything.
Has anyone come across the same problem? I've done a hard reset but to no avail, the phone still shuts down right after turning on, it's pretty frustrating to turn on your phone just to see it telling you it's turning off, really frustrating tbh.
I've called google and requested for a replacement so problem's kinda solved for the moment. I just want to know if I'm alone here because I've pressed the operator a couple times and she refused to tell me if mine was an isolated incident or not, for obvious reasons.
I haven't done anything to the phone except installing a couple apps like Aldiko, whatsapp, facebook and a Chinese keyboard (since I'm Asian apparently). I've installed all of them in my old phone and none of them caused any problems so I just want to know if I'm alone and what do you guys think the root of the problem is, or solutions to it if there are any.
Thanks a lot!
Click to expand...
Click to collapse
Mine is happening the samething, glad Im not alone. My was running fine on rooted Modaco custom rom for a few weeks then all of sudden the phone auto shut down like it has its mind. I installed Cantonese keyboard and camera mod too and some other apps. Currently Im tracking down the source. Now I have franco kernel and madaco rom on clean install running with no other app install to see if it will shut down or not. If it does Im going back to stock to see if samething happen.
I have to boot it couple times until it doesnt shut down itself anymore. Sometimes it be stable for couple hours or couple minutes or instantly.
I have the same problem, Just got my phone from google everything is stock nothing has been changed and the phone just turns it self off and then i cant turn it back on for sometime.
Does anyone know what causing this problem?
Mine also turns off multiple times a day, sometimes by itself, sometimes during a call, often when taking a picture.
Today every single time I took a picture it would shut down.
I'm f*cking pissed at waiting 5 weeks to get a useless phone... and god know how long it will take to get a replacement if I ca get one.
Hi guys, I have the same problem too
I've used my Nexus 4 for 2 weeks without any kind of problem when suddenly it turned itself off. If I try to turn it on, the phone just turns itself back off again and I haven't solved the problem even with a reset.
But I've noticed that the battery doesn't charging even with the charging cable. I think the phone detects that hasn't enough battey level and for that reason turns itself back off.
Do you think it can be an harware or software problem?
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
kalipedia said:
Damn - i have recently been having the same problem! It only happens (so far) when i'm charging the phone overnight. I wake up and it's off and takes a few tries to get it running again. I'm rooted with stock. Does this mean we all need replacements? Ugh!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Notorious544d said:
The exact same thing happened to me as well. I charged it overnight, unplugged it and it was off. I couldn't even turn it on again - I had to keep holding the power button for ~15 seconds plus try plugging/unplugging the phone to the charger etc. and it finally powered on. I orginally thought it may have been a kernel issue since I had just flashed Franco r29. However, looking at his thread, nobody had that issue.
I'm glad I'm not alone but this issue really worries me, especially if it is a hardware fault. Google will replace it but I don't feel like going through the fuss since God knows when the replacement will arrive. I hope this get's 'magically' fixed as it has only happened to me once so far.
Click to expand...
Click to collapse
You know, I'm looking at my battery history (using battery monitor) and i see the period that the phone was shut down and then when i powered it back up this morning and i notice the battery temp is extremely high so it probably has to do with the phone shutting down due to overheating, which obviously shouldn't happen. I wasn't using the oem charger, so I'll switch to that for the time being and keep an eye on temp. Hopefully it's a software bug and not a faulty battery because it should definitely be cutting off charging when it reaches 100%.
Sent from my Nexus 7 using xda premium
Hey guys,
I've bought my Nexus 4 end of January (first revision) and am having a major issue since I got it:
Sometimes (once a week, first two weeks even more often) it is stuck in standby. So when the phone is turned on, but the screen is off and I try to turn the screen on, it won't react at all. Most of the time, the notificationlight is blinking.
This is totally sporadically, but I think more often, when the timer is set, to get me up (or not^^) in the morning.
It won't even react on charging or attaching it to my PC. I logged it twice, but there was nothing special in the logfile (logged it with su; logcat > /sdcard/log.txt)
This can get quite annoying. All in all, this makes the Phone quite unusable, because, without trying to wake it up, you never know if it's still running and you are reachable or if it's already stuck...
First I thought, this would be, because of some softwareproblem, but I got this issue with every ROM I tried (even stock, where I got this problem the most...)
Should I send it back to Google for RMA or do you have any idea why this could be?
Thanks in advance,
acid_g
Same problem here. Also bought it at the end of January. At least once a week the screen won't turn on, and usually there is a notification light flashing. I've found lots of other people online with the same problem, but no solution. There's a ticket for it here:
code.google.com/p/android/issues/detail?id=52926
I called Google support, and they recommended doing a factory reset, but it didn't help; a couple days later the problem happened again. So yesterday I called them back and started the RMA process. I hope the new unit works. This problem is so annoying and frustrating. You never know if your phone is going to work when you pick it up.
its called sod, sleep of death. it can happen with undervolting, and some apps can bring it on
Yesterday was listening to Pandora via headphones, and the phone reboot itself to the "device may be corrupt screen" when bootloader is unlocked. While rebooting, the screen shut off and now the phone is completely unresponsive. The phone was running the latest Pure Nexus Rom with a Substratum theme.
Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.
TwiggieSmalls said:
Similar experience for me just recently. Last Friday I was out doing Uber/Lyft and upon accepting a call in the Uber app my phone froze, shut off, and then bootlooped. I tried literally everything to restore my phone, including fastbooting a stock image but the phone continued to bootloop and then shut me out of TWRP. Have a refurbished one coming from Google today. Phone just nuked itself while running Benzo ROM, no clue why.
The only thing I recommend is calling Google and go thru their troubleshooting. When it doesn't work they'll send you a new one (you'll be charged for the device until you return yours) and start over. Crazy, I've never experienced anything like it.
Cheers and good luck.
Click to expand...
Click to collapse
yea seems strange, unfortunately I'm unable to do anything with fastboot as mine won't even boot into anything.
This happened to me as well. Phone just booted when to the corrupt screen and died. Obviously freaked me out. I held the power button down for a very long time and it booted back up. Please try that. Phone has been fine since then.
Thats scary. It didnt give any warnings (unusually high temps, glitches, random reboots)? Neither of you flashed anything other than PN in the days/hours leading up to the complete shutdown?
Im a bit paranoid since Im running the same rom. But everythings ok here.
Hi everybody,
So I have a S7 Edge that I buyed in Spain in December 2016, so it has a year and a half by now.
The phone have the Gorilla Glass a bit broken but the display is perfect aswell as the touch, the back is also broken, main issue there was a corner fall but, this either started nor agraviated the issue in hand, it was no difference between before and after that situation.
The phone was submerged in water, less than a meter for less than 5 minutes, again I dont remember that this issue started nor agraviated the issue.
Now the issue I'm not sure when it started but it was this year for sure, maybe 2 to 3 months ago.
As far as I remember the issue started after a Samsung update, a large update like 1 Gb, the phone restarted to install the Update and during the Update it froze while installing the update in the boot and started heating up I wasnt able to do a thing I wasnt able to either restart it nor shutdown it, so I just waited until the batery run out wich it wasnt much time since it was heating up a lot.
After it shutdown I charged it and then started, it was able to update but from that point I didnt want to either shutdown nor update the phone again being afraid of the phone dying, so some day the phone forced another update, and I encountered the same issue, after that once in a while the phone restarted.
From that point I dont actually remember how it happens if I had some issues but one day the phone restarted and entered a boot loop restarting the phone after a second or two of the Samsung ROM splash, so I tried to shut it down and wasnt able to do so, at some point it "shutdown" but with a red led on and I wasnt able to start it, after 3 to 4 days the light went off (batery run out) and then I charged the phone again but wasnt able to boot up, after a few restart it boot up but then restarted and loop again.
After a few tries I was able to Factory Reset the phone and the phone started functioning kinda alright, I installed an app and while using it the phone restarted so I uninstalled the app, after that the phone didnt shutdown, so I used the phone for some days and never shut it down nor let the batery run out, till one day I updated the apps from the Play Store while updating the apps the phone shutdown again, boot loop and subsecuently shutdown with a blue led this time and not being able to start the phone again, so I waited like before, but for some reason the blue light stayed for like 2 weeks, I guess the phone has a lot of charge and the only thing using the batery was the led I dont know.
After all this I decided that the problem was a Software problem since all the main issues apeared while updating apps, updating the system, using apps, etc, so because I didnt have guaranty I decided to install TWRP and then some custom ROM, so I do it so, I installed TWRP, booted into TWRP, backup EFS, wipe dalvik, cache, data and system, in this process the phone rebooted, boot loop and then again blue led and not being able to start the phone, so I was tired by now and I opened the backpanel breaking quite a bit one side didnt care if I fix this I will change the back and front glass, I detached the batery and the phone shutdown then I was able to start it, boot into recovery TWRP and installed HavocOS this time (I will try with another one just in case), I installed it run it and it appears to be working fine... it rebooted one time and after that nothing I installed Whatsapp a 2.3 gb backup started to download alongside 34 apps from the PlayStore I guess the apps that I had in the previous installation.
While downloading the 34 apps the phone restarted I guess while installing Facebook, after that it shutdowns again after apparently working just fine for an hour or so.
So I decided to install again HavocOS but dont instal any APP but Whatsapp, maps and some other things I need (Keepass, Bank stuff, etc) but from here on the phone started to reboot even in TWRP, while installing the ROM sometimes it freezes sometimes it shutdown sometimes it rebooted and antered boot loop but at least it didnt get stuck anymore I was always able to shutdown and start the phone but with boot loops and shutdowns and totally impossible to use.
So now I'm almost totally sure that it is not a Software (free fix) problem, and now I'm thinking in replacing the batery, the batery is not very expensive (compared to a now phone ofc) but it is a bit expensive for my economy and I'm not totally sure that the batery is the problem, can somebody, with all the information given here tell me something like "I'm at least 90% sure that the problem is the batery"?, cause, I'm a PC Technician that didnt know much about phone but they are practically the same as a PC but less modular and sincerilly I think that it might be the Processor or the Internal Storage, both non-easy-removable and change and both more expensive than a batery and both things that I have to buy outside of my country that may or may not come in 1 to 3 months so, is it really worth buying a batery or this issues point to a direction that the phone is almost imposible to fix with the money I have so its better to save money and buy a new one... thing is in this effing country a new S9 for example cost 1000 u$s and my salary is 600 u$s so its a bit anoying to save for something like that, even a new S7 Edge is worth 600 u$s here, and thats what I paid in Spain one and a half year ago when it was the latest Samsung phone available.
Sorry for the long post I wanted to explain everything throughly and I hope my english is ok.
Best regards.