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!
Related
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
I'd try just following the steps to update to super clean 2.4. some kernels act up on your version and drop the vibration. It happened to me. 2.4 is running awesome
Sent from my SCH-I500 using XDA App
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Spazguitar306 said:
Yeah I forgot to put that in the first post. I actual did a complete system wipe. Back to stock DL09, flashed the EB01 modem, and SC 2.4 over it. And still no vibration. I did all that this morning.
Also had a weird glitch where after I installed most of my apps I tried to boot into recovery and instead my phone decided to do a data wipe again, but that wasn't a HUGE issue (as long as it doesn't happen again).
Click to expand...
Click to collapse
Try reverting back to stock again and prior to going back up to eb01 and superclean...wipe a few times.
I had a similar issue
Spazguitar306 said:
Ok, so my phone will not vibrate at ALL anymore. I don't want to pay the $50 to get a new one, and I don't want to have to revert back to stock and unroot and take it to Verizon to see if they can fix it.
So here's the details of what happened. I don't know if it's fixable, but I thought I'd see if anyone could offer some advice.
I was running DL30 Blackhole, very basic. Had a theme installed over it. Everything was running perfectly fine for a while. And then I was getting on the internet to do something, and connected to wifi. The wifi was through my college, so you had to login on their homepage instead of just entering a password, and the page wasn't coming up, internet was being extremely slow. So I tried turning off mobile data to see if it might force me to login to the page for wifi. Turned of 3G. Nothing happened. Turned off wifi. Turned 3g back on. Then I got a google system force close error and my phone rebooted itself.... Now I have no vibration AT ALL. No hatic feedback, no vibration for notifications. Nothing.
There was nothing even related to vibration that should have happened in this situation, my phone just freaked out. Didn't drop it or hit it on anything at all, it was laying flat on a table. So I don't know if something just fried my phone's vibration or what, but I would love it if someone out there had a suggestion for me.
Click to expand...
Click to collapse
I had a similar issue. I actually flashed my phone all the way back to stock. Still no vibrate. I think there could be an issue with the vibrate motor on the fascinate.
I say that because there was nothing I could do to bring vibrate back. All of sudden, it began working again for one day. After that one day vibrate and haptic working, it stopped working for another couple of days. Then, I dropped the phone on accident. Vibrate came back. Eventually, it stopped working again so I took the phone to verizon and they ordered me a new one.. No charge. I bought my phone in Sept 2010.
Good Luck!
hey guys
was using my nexus 4 5.0.1 (stock, bootloader unlocked, not rooted) with no issues this morning. then suddenly i can launch google music. the app launches and i get a white screen with nothing on it. so eventually the app crashes. then i try launching messenger, good play, and many other apps with the same result. my phone begins to get very slow and laggy, nearly non responsive. i restart my phone and i get no service. restart my phone again and a few apps like chrome will launch, and whatsapp aparently, but ive tried so many other apps that will not launch or hang on launch. any ideas? is it a failure of sorts or will a wipe fix the issue?
edit: i think its helpful to note this is a refurb phone. there have been times when my phone suddenly restarts (normal for android) and other times when the screen just goes off and i have to hold the power button till i get red blinks or sometimes i have to plug the phone into the wall for it to restart.
edit2: just restarted my phone connected to the wall. wifi wont even turn on. i waited 60s and it finally switched on. its like the phone has gone limp lol. it wont connect to my mac anymore either ("try reconnecting or restarting your device").
It sounds like your memory chip is failing. I would advise you to extract as much valuable data off of the device while you still can. Then we can troubleshoot to see what the problem really is without having to worry about important data loss.
lolcakes203 said:
It sounds like your memory chip is failing. I would advise you to extract as much valuable data off of the device while you still can. Then we can troubleshoot to see what the problem really is without having to worry about important data loss.
Click to expand...
Click to collapse
i did a full factory reset from terminal. im not having any issues anymore.... yet. however im still concerned about potential imminent memory/storage failure.
Alright that's good to hear. Keep us posted.
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.
So... For no explainable reason my phone has gone into a bootloop, simply from me attempting to restart the phone.
Details of anything I can think of that might be related are below. I need a genius to help me A) figure out WHY this happend, B) help me figure out if there is a way to (non-destructively) get out of this bootloop (i.e. NOT having to do a factory reset), and / or C) tell me if there is a way that I can perform a full system backup using ADB, Fastboot or Odin with a phone that can't get past recovery or bootloader without going into an endless bootloop. I'm not a lazy guy and normally take the time to research problems and figure them out on my own, however at present this is my only activated phone, it's almost 11pm, I have to be up and out the door at 6am tomorrow, I will be judging competitions all day and will not have any opportunity to do anything about this until late tomorrow... In the meantime, I need a functioning PH1!!
My PH1 is the Sprint variant and I have not rooted it nor have I unlocked the bootloader. The only thing I have "done" to the phone is to sideload the latest OTA, NMJ32F (the day it came out, over a week ago, and it's functioned perfectly since that update). My phone has been in use throughout the day today with no difficulties. I went into a building with very spotty service for several hours this evening. On the way home, I noticed that I was stuck in 3G service, despite being in an area I know has good 4G/LTE coverage. I also noticed an unidentified icon on the status bar, a rectangle, which was located (I believe) to the right of the battery icon. It looked like a rectangle, perhaps representing a screen, or a phone? IDK. The other item of note is that I did sign into the guest account on my phone so that my daughter could use the stopwatch for timing competetion events without tampering with anything. She didn't drop it or get it wet or anything along those lines... she used it to time events, returned it to me in perfect shape. I logged out of the guest account, back into my account, rebooted to try to get the phone back into 4G service, and boom, I'm stuck in a frigging bootloop for no apparent reason.... And I'm about to lose my mind over this.
I CAN get into download mode and into recovery mode by holding the appropriate button combinations when it loops, but from there whether I power off and power on again or whether I select reboot from recovery menu, it continues to loop...
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
So I am running O beta rooted and last night this happened to me. I ended up going into fastboot and starting OS through there and I had no issue with the reboot bootloop. However, last night I went to bed with a phone @ 75-80% and woke up 6 hours later with a dead phone. Charged and rebooted this morn and everything seemed normal today. It was super wierd
Had to return mine for this very reason. Less than a week in service and went into boot loop. The reboot happened after it lost all battery power (corrupt filesystem?). Several factory resets did nothing to fix it. Removed the SIM. The phone was also fully charged. Did not try ADB as it was brand new and a return was the safest easiest option.
ccopelan said:
Well folks, still strange, still unexplained, but I had to bite the bullet and factory reset, just can't afford to wait. I'm still open to any thoughts on what might have gone wrong though I suspect we'll never know. This phone has been a bit buggy from day 1, things like BT randomly shutting off, VoLTE wouldn't stay enabled, etc... Hopefully this is the last time this happens. Still love the phone though!
Click to expand...
Click to collapse
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
chray1 said:
Any issues since factory resetting? I'm having the same issue. Not sure if i should just return the phone or not.
Click to expand...
Click to collapse
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
fhlutiis said:
I am stuck with the same problem, and this is my second phone already. This one doesn't stay on long enough even for an attempt to factory reset. I will send it back again, but I have no hope. Time to cut my losses and move on. Going to Pixel. And I sooo wanted Essential to succeed!
Click to expand...
Click to collapse
interesting.
If it's your second phone, have you looked at what applications you install?
The probability of getting two bad phones is pretty slim unless there is a major manufacturing flaw.
Not saying it can't happen, but it would be unusual.
Could it be due to Encrypted Data partition?
It once happened to me on a Huawei Mate 2 which I encrypted data and battery dead, then bootloop.
If that's due to corrupt encrypted partition, there seems only other recovery mode can help you get some files back.
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
SinisterDev said:
This is really starting to get on my nerves now. Ever since I got my new S10+ from AT&T, it's occasionally done this thing where after I reboot the phone, I unlock it, and it briefly says "starting phone" on the home screen, and then will mysteriously do a quick reset, where it skips the AT&T logo and jingle, and just shows the Samsung splash screen , then takes me back to the lockscreen and it's usually fine after that.
However, Just now I decided to reset my phone, like one should do periodically, and it did the strange double reset after unlocking... Then when I unlocked it, after the "starting phone" message I tried to open a browser, and BAM! Quick reset again! Unlocked, let it start up, tried to open an app, BAM quick reset again after the screen briefly shifted from landscape to portrait mode (even though I was still holding it long ways in landscape position). Its never done this before and I'm getting concerned. It's never randomly reset while using the phone, this only happens right after a reset.
Any ideas? I've already tried wiping partition cache after big updates, doing soft resets. I'm worried that I'm going to have to end up resorting to a factory wipe, as others suggested I do when I was having battery drain issues on the ASD3 firmware, possibly because of restoring everything from a backup of my last phone when I got this one. Because supposedly restoring from backups from AT&T, Google or Samsung has caused all sorts of problems for people. I really don't want go wipe everything and spend hours try to get it all back on here manually if i don't have to.
Click to expand...
Click to collapse
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
mtm1401 said:
Had an issue with this early on but seems to have been fixed at some point, I'm I'm exynos though so probably not much help!
Click to expand...
Click to collapse
Dang... So it does appear to be an issue experienced on both Exynos and Snapdragon variants. I wonder if there is or will be a fix for this. I've been asking around and haven't gotten many responses about this problem at all. I'm concerned because it seems to be getting worse than when I first got the phone.
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
macmanui said:
I'm having the exact same problem. Sometimes it goes through quick reset, full reset, a couple more quick, then back to the Verizon logo, then starts up. Opening an app at that point usually does another quick, then full, then everything works. Glad I'm not the only one, but I haven't found any solutions either.
Click to expand...
Click to collapse
Mine does the same. Unlocked bought directly from Samsung. I don't reboot the phone very often so it doesn't bother me that much.