My phone froze up twice and this screen keeps poping up. i havent used any method of rooting or have tried to do anything to the phone. Was just browsing web when phone froze and rebooted itself twice before it went to what you see in the picture.
After pulling the battery twice phone started to work again but on occasions it wont let you unlock the phone. it just wakes up but it wont drag the unlock. Also signal has greatly decreased i bearly see the H as before thats all i had
Just trying to see if its happened to anyone else. Gonna be returning phone tomorrow cause its only 4 days old
Related
Anybody know why my G2 randomly just shuts off? It doesn't reboot itself but just turns off. It battery doesn't seem to be loose nor have I ever dropped it.
Very annoying as I depend on my phone as an alarm clock and I would hate for it to shut off randomly overnight
I would just call T Moe and talk to Tech Support. Let them know whats going on and they will maybe send you out a replacement.
Shame I actually did want to avoid this route and find out the cause but worst case scenario I'll unroot it and send it in for a refurb :[
You can always demand a brand new in box one.. I don't know if they will give it to you but you can try... You may get lucky and get a 01 part number phone.
I have randomly had this same issue as well. Before and after the ota update. Mine just reboots itself thou, not a straight shutdown.
Sent from my T-Mobile G2 using XDA App
It's funny that you mention this.. before the OTA update they put out.. I was getting 7 random reboots a day and some shut downs.. and keep in mind I also depend on my alarm clock and phone 24 hours a day even if I am sleeping.. So I can't be having that happen.. but then the OTA came out and I have had ZERO problems with it.. I've been actually waiting for it to happen again, but hasn't happened. I recently just rooted my phone also, and it still hasn't done it.. SO not sure if you did the OTA update, but that REALLY helped my issue with random reboots and shutdowns.
What battery are you using? I know the red batteries with labels removes of will cause the device to turn off if you don't have a piece of tape on between the battery and metal sdcard reader.
Sent from my T-Mobile G2 using XDA App
I'm actually on the stock battery. I've been thinking of getting the red one just to see if it's any better and gets rid of this issue.
check your sdcard slot. the my door wasnt clicked into place and i had problems with random shutdowns. not reboots. it would just shut off without turning back on. i took it to tmobile store, the guy pulled battery, clicked the sd into place, and for 20 minutes could make it shutdown again. still hasnt since.
I can confirm havikx's experience. The one time my phone shut down on it's own, I pulled the battery and noticed my sd card wasn't locked securely in place. Once I locked it in well everything was fine, no random shutdowns since.
I had my Surround lock up twice today requiring me to remove the battery. Once while searching in the marketplace and another when I was typing in a text message. Anyone else have any freezes yet?
I'm only on day 2 with mine, but so far no freezes here.
i've had mine since nov 8th and i haven't had any freezes yet. has it done anything else?
I had a couple freezes 2 days after buying it requiring me to pull the battery once, but other than that, its been running every day since then without a reboot just fine.
I did install several applications from the marketplace which did not work until i booted the phone so perhaps that had something to do with it. Made me wish for a stylus and a reset switch though! Some things never change...
Mine just froze one time after downloading a program and I think it had to do with low signal strength so the download hung then the phone was frozen. Other than that smooth as can be.
Wingnutt54 said:
Mine just froze one time after downloading a program and I think it had to do with low signal strength so the download hung then the phone was frozen. Other than that smooth as can be.
Click to expand...
Click to collapse
I've had the Market freeze a few times on me too, but that's it so far...and I did pull the battery
Ive got a new one for you. The microphone on mine stopped working.... I was in the middle of a call and I could hear "hello...hello..." but he couldn't hear me. I did a power cycle and still no go. So I took the battery out and restarted it and it decided to work again. Now the battery was pretty low, but not dead you think that the noise cancelation crap in the phone could stop working with a low battery?? That was a new one for me
Constant Freezes and Reboots
Mine began locking up after I installed about 20 apps in one day. Then it would randomly reboot itself. Then it got bad, It would reset to default: no apps installed, no accounts, no contacts. But the wierd thing is, randomly it would come back with all my settings. I contacted HTC throug email and got a reply within 20 minutes. Told me to do Hard Reset because OS got corrupt somehow. Hold Volume Up & DOWN while powering ON. Options come up on screen to Hard Reset. I have since reinstalled every app as before and it works flawless now. Loving my Surround!!
I had my first reboot today, I was typing in a text message and it hung on the letter "I" then when dark after 30 seconds or so. It immediately botted back up and has been fine ever since. Strange...
Hey guys, so this has happened the last two nights -- at exactly 2:02am my Droid X locks hard. Just did it again. I have no idea what is going on here but I have to pull the battery.
Last night it was on the charger (And the screen was on) so when I picked it up this morning it said 2:02 on the lock screen. Just now I was listening to music and dead stop -- screen was off but I looked at the clock on my computer and sure enough: 2:02.
Just set the clock manually to 2:01 and started a song -- let us see what happens in one minute.
*SIGH*
My phone has been working generally well..... but then I had a strange issue last night where the phone became super unresponsive accessing the SD, so I rebooted. Then the 2:02 lockup .. and then today the battery drained really quickly. A check of CPU spy and the phone never entered deep sleep. Battery manager showed the phone never going to sleep as the "awake" bar went across the whole screen even though Screen on was less than 1 hour total.
Manual clock set to 2:01 did not result in a freeze as I let it go to 2:03... I just set it to 1:59 to see if that makes a difference.
Stock latest GB, root, debloat done myself (fresh install and debloat a couple weeks ago) .... really at my wit's end with Motorola phones. I have a Droid X2 but find that phone generally unusable due to the extremely lackluster performance including the constant audio dropouts, even with the latest GB release.
Anyone else ever seen this 2:02 thing? Or have any idea where I can even begin to look to fix it? I don't see a crontab file on here. I haven't installed any new apps other than the usual updates that seem to happen every day.
....Manual clock is now at 2:04 (from 1:59) with no freeze. So I don't know WTF is happening. I had rebooted the phone around 8pm tonight .. actually had to pull the battery. Did a "reboot" from the Terminal Emulator and the phone went black and never started rebooting.
I'm so fed up with this damn phone!!
That's not happening to mines
Hard reset your phone n back up SMS, files, etc.
Try different battery!
Sent from my DROIDX
Alright, so like many people, I tried to play Pokemon GO. I was playing for about 20 minutes on my break at work, and I noticed that as I was switching between it and other apps, my phone was getting pretty laggy and bogged down, to a point where the phone just froze for a minute, then when the screen turned off. I couldn't turn it on for a further minute or so. Eventually after a few minutes of this, the phone just crashed, Upon trying to restart it, it went to the odin screen, saying "mmc_read error", or something like that. I pulled out the battery and let it sit for a few minutes and tried again. It started to boot, but it was stuck on the phone's model splash screen for several minutes, which its never done before. After the phone finally got booted up, it would freeze often, and I would not be able to turn the screen back on for several minutes at a time. This has persisted all night, crashing and freezing for the remainder of my shift. After I got home I tried restarting it again, and the phone wouldn't turn on at all, so I again pulled the battery and let it sit for a while. I've done this a few times now.
Sorry it's a bit lengthy, but I tried to recreate the events of what's happened as best I could. If you need any other info just ask
I have uninstalled the game from my phone now, the phone is completely stock, no roms, not rooted. I do not recall it feeling too hot as if it had overheated
I really am not experienced with issues like this, and I really would not like to have to buy a new phone
Hmm, that error is supposedly of the EMMC failing, now you will be lucky if it was a one time incident. Now to be quite honest I don't think anyone could tell you that whether the problem will come back or not, and you can't do much anyway. I will say if the phone is running okay now, let it. Or if you are really unlucky then the problem will come back, the EMMC might fail permanently. But if you see one or two more reboot incidents like that, I think its fair to conclude that your phone is done mate.
Currently I can turn on the phone, but after I turn the screen off, it won't come back on again
Oh darn mate. You could try to wipe the phone completely from recovery (TWRP) and then flash the stock ROM. Now please don't blame me if the phone gets dead or something after that, cause my Note 3 died just few months back, and it took me a good couple of months to get over that fact. However one thing is for sure, if your emmc is supposed to fail, or motherboard, then it will no matter what.
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
I have had this issue on both at&t and t-mobile firmwares, but only while rooted.
Best thing to do is to re-flash the stock firmware again(or go to a different firmware if you'd like) but this is the reason I'm currently avoiding root. It soft bricks about a month in and is an easy fix but its annoying.
Was wondering about that too (flashing the stock firmware). But, will it wipe everything I had on there? Will any of my txt msg's and photo's or summat be lost to the ether?
Stupid question, I know, but had to be asked.
Thinking about flashing stock firmware and rooting agin for the sake of being able to do it again lol.
Well, if you flash stock, it does factory reset. That's why I have backups lol all I have to do is log into my Google account and everything is there.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
Did you have security log or security update disabled as that updates and causes weird after affects.
buntobo said:
Posting here to see if more exposure would help.
Was wondering if anyone has run into this problem?
The phone was fine, rooted and everything, for a month give or take. Then all of a sudden, today, it started acting weird.
It was fine in the morning and everything, was able to use wifi, check emails, and stuff.
Then BAM, I tried to make a call, it didn't go through for the first 20 seconds or so. Then connected and a message kept popping up saying Phone is stopped or something during and after the call.
So, I restarted the phone. It restarted fine and everything, got past the 2 Samsung screens. Then hit the T-Mobile screen. and has been stuck on the T-Mobile screen for ~30 minutes now and just keeps vibrating.
It's getting quite hot, both front and back.
Any advice? Stupid Samsung making this a closed system so can't pull out the battery.
Can't even turn the phone off, only able to get to Download screen.
Weird problem.
Is there any way to pull the data and stuff off the phone at this point?
I'm thinking of going the factory reset route and do that to see what happens and see if it will fix the problem. It would probably not retain root am I correct and I would have to re-root again?
I could get into download mode and recovery fine.
Click to expand...
Click to collapse
These two threads describe exactly your issue and solution - http://forum.xda-developers.com/verizon-s7-edge/help/g930t-updates-unroots-overnight-t3426636 and http://forum.xda-developers.com/tmobile-s7-edge/help/rooted-weeks-rebooted-stuck-t-mobile-t3425814
I had the same problem, twice I had a rooted device totally lock up and had to re-do everything. But after disabling the security updates as advised, I'm currently going on two months without a problem.
Hope this helps!