Have T-Mobile version of the S7 Edge, stock, never rooted. Yesterday Samsung apps did a few updates, and a few hours later the phone began to have:
(A) apps crash with the message "Unfortunately X Has Stopped"
and(B)reboots, some of which are stuck on T-mobile logo (until I reboot the phone a few more times)
A lot of the apps that are crashing are official Samsung/Google apps, including Play store, Google Play Services, Samsung Pay Framework, com.samsung.faceservice, and etc. Usually this happens when opening a new app. Sometimes it happens in succession and a dozen messages will pop up over each other.
The reboots happen right after the phone freezes for a few seconds (often does this when entering settings > applications. Often the reboots get me stuck on the tmobile logo, with it vibrating every ten seconds or so. Holding power + left vol to reset it works half the time, then it boots normally.
The only other symptom I've noticed is in recovery I see the following message: "dm-verity verification failed"
---------------------
Things I have tried which have not helped:
1. Going into Google web services, Play, Play service and wiping cache.
2. Rebooting into recovery and wiping cache.
3. Rebooting into recovery, and doing full wipe/factory reset.
3.1. Made sure to wipe cache before and after
4. Using Odin to flash stock firmware
4.1. Used the right firmware, (G935TUVU4APK1)
4.2. Made sure to wipe cache + factory reset before and after
5. Using Odin to flash stock firmware + full nand wipe + repartition
5.1. Made sure to wipe cache + factory reset before and after
Still have the same issues. Not exaggerating, each time, as soon as the phone boots past the tmobile logo, and gets to welcome screen, some of the app crashes begin (most consistently com.samsung.faceservice, and almost every round, the phone reboots at least once before I finish setup.
---------------------
I am completely out of ideas. haalp
I am experiencing something similar. Android 6.0.1, with December security patch (7 is not out yet for my Norway TEN phone..). Has happened since purchase.
Every time I update applications in the Play Store, the entire phone freezes.. sometimes I also get a horisontal line across the screen, about 3mm in width. After about 20 seconds the phone reboots into the Samsung logo and starts booting up. At that point, it will reboot about 3-20 times depending on the app that I update. Sometimes clearing the cache works, but only about 1/4 times. It gets insanely hot if connected to a charger (about the temperature of burn marks on skin).. I tried master reset, and it vanishes for a little while before it returns, even if I don't install any applications at all. Been handing it in to Samsung a few times, but they always just tells me that either it is normal, or nothing is wrong.. I don't really know what to do anymore. I am suspecting a hardware failure that happens when it is put under stress.. but since it happens 1 or 2 times per day, the workshops don't have the patience to just keep testing it hard, instead they just run a normal stress test and say that everything is fine.
StOrigen said:
stock, never rooted.
Click to expand...
Click to collapse
StOrigen said:
"dm-verity verification failed"
Click to expand...
Click to collapse
StOrigen said:
Used the right firmware
Click to expand...
Click to collapse
If that all three are as you said then your NAND may be damaged.
Related
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]
You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.
Ended up "solving" this by doing a stock restore via Odin, after which TouchWiz would never load an icon (crash loop). Reinstalled TWRP via Odin, then flashed ViSiON X N3 via TWRP.
--
Morning guys,
I've had some reboots lately and a weird situation last week where I had to do operating system surgery to get the thing to boot at all.... HOWEVER things were going quite well for some time, and it's been rooted and non-stock for months.
Nevertheless I woke up this morning and it was off, I figured the battery had died so I swapped batteries... It boots, it gets to the launcher and it loads the app icons then freezes and reboots... over and over again.
edit: to be clear, as soon as the slider bar touches the right-hand side the phone freezes, the vibration holds for several seconds, and then the device reboots. obviously not what one expects from this operation (having done it before). I was able to wipe the Cache separately... trying to wipe the Dalvik cache all by itself in an advanced wipe does this reboot thing.
OK I said, i will just clear and reflash this.
Going into TWRP, attempting to do a factory reset wipe just freezes, buzzes, and reboots immediately (to the not working OS)... in order to make this all stop I pull the battery, because now the button on the side won't seem to do a hardware poweroff for anything. Just ends up resetting the current reboot.
--
Any advice would be helpful now. I was just going to say forget it and grab the tiniest ROM i could find and ride it out until I upgrade the device, but now I'm just concerned with getting it active. The rebooting in recovery when trying to do a wipe does not make me feel too great. First and only problem I've had with android roms.
Thanks,
Chris
Hello.
I have bought a galaxy note 4, but I am experiencing the following problem: almost every application crashes ("unfortunately, application has stopped") really frequently - it's a matter of minutes, sometimes seconds. I can launch browser, open a couple of pages, then it crashes. Setting up google voice search crashed about 3 times before I could set it up. Play market often crashes just when I open it (sometimes it doesn't). S-voice can crash just after booting the phone. Even launcher often hangs a few seconds then reboots.
The device originally was on android 4, but the issues I am experiencing were manifesting already. I thought that updating it to android 5 could fix them, but the problem remained.
I have tried factory resetting the device and clearing cache - no effect.
Is there anything else I can try or my only option is to go to official service?
Thank you in advance.
Sounds like data partition corruption to me. I had that on my note 2, which, funny enough, was caused by a bad battery. But once I got a fresh battery, I flashed the stock rom in Odin with a pit file to repartition and it's been fine ever since.
So as a last resort you could try that. I don't think your situation is as severe as that. Have you factory reset stone updating?
You could also try to format the data partition via recovery (and wipe the other partitions + reinstall your current stock rom on the device after it's good and cleaned). See if that resolves it. If not you'll have to go the Odin route.
I've got a Canadian G2 D803. I have been using AICP 10 (aicp_d803_lp-10.0-NIGHTLY-20151225), the last lollipop release. I used this because in January when I tried MM release, it caused random soft boots at the time.
With the AICP 10 lollipop, it was mostly working fine until Friday when it all of a sudden doing soft reboots. It wasn't just a single isolated instance. It began doing it constantly. Every time it finished booting up, after a minute or so, it would soft reboots itself. In addition, when it constant soft reboots, the time would reset to linux default of 1970-01-01. Because it only stays in boot completed for only a minute, it wasn't long enough to sync time with service provider or ntp servers. Manually correct the time and a few soft reboots later would reset back to default 1970-01-01.
I should also note that this is not the first time it happened. I traveled to China in May, and this soft reboot loop kept happening. But the problem stopped after I disable auto time sync. But this time, I disable time sync and it's not working.
My main issue right now is I want to backup all the apps and data with Titanium Backup before wiping the phone or moving to another phone. But it only completed boot for 1 minute before it soft reboots by itself again. Within the 1 minute time, for multiple reboots, I uninstall some recent apps. However, so far it doesn't have any effect. I've also tried clearing dalvik and data cache in TWRP. While the phone boots and runs through the "optimizing" app on boot, it doesn't soft reboot, not until it completes booted into the OS. Here is a more detailed list of things I have tried so far without success:
I'm completely at a loss right now as I just want to backup the apps and data first. Does anyone experience something like this before? Anyone has any clue about this or similar issues?
I do have a logcat and kmsg. I don't think I'm allowed to attach to the post because I'm new to XDA. Where can I post it?
Thanks in advance for any help.
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
You should of wiped system and cache also might be your problem. Also if you where using any substratum themes remove then manually as well. Not sure if they would cause reboots.
coolsid8 said:
I installed 8.1 last week. Everything was working smoothly. Was trying magisk youtube mod. Screwed something up. Phone went into bootloops. Reinstalled everything .Wiped data. Now my phone reboots randomly. Everything stock .Rooted with Magisk. Mainly it happens whenever i launch a new app(An app which was not launched before). After few tries, the app opens up and doesnt' result in reboot.
Any ideas what could it be ?
Click to expand...
Click to collapse
FC's are one thing but random reboots are a completely different animal. I would completely wipe the phone and apply the latest factory image using flash-all.bat. If that doesn't fix it you may have a hardware issue (eg. degraded battery).
Wiping caches helped
I'm running SUPERXE-8.1.0-OPP5.005_v1.5.1.
My 6P was going crazy, restarting every 5 minutes or so. It rebooted so quickly it felt like a soft restart, so I thought powering off and rebooting to recovery using the power + down volume to clear the cache in TWRP would help.
Cleared system and Dalvik and powered down. Full reboot and (for now) it feels much happier and hasn't spontaneously restarted yet. That was about 15 hours ago.
Hope I didn't just Jynx myself, but I think it helped...
I've flashed the final 8.1 images to upgrade my 8.0 unmodified system. Now I've random reboots, usually when I've leave home to go to work or vice versa. Something related to wifi, that I'm connecto on both my work and home?
Same here I had to factory reset I'm having a feeling it's going to happen again. I am on factory, rooted with magisk. I always use SuperSU not saying that is what it is however it did happen when I got home from work and just kept rebooting before I could unlock.