For a week my G935A worked fine... direct out of the box I flashed ENG Kernel and Rooted, then installed apps and configured - no issues.
Today it was working then it hung on wake.. I tried to reboot and now it gets stuck at the AT&T logo and vibrates 3 times - over and over
I can get to Odin and Recovery screens easily so I tried to flash the ENG Kernel again & deleting Cache Partition few times - didnt fix it.
Also tried booting into Safe Mode - it never gets there, stays at AT&T logo.
When I go into the Recovery menu, I see at the bottom, in red... "dm-verity verification failed"
Anyone know how I can recover from this without Factory Reset? It took 6 hours to reinstall and config all my apps - really want to avoid that.
thx for the help!
as far as I know there is no way to fix and save your stuff. I had the same problem with G930A and even doing a factory reset would only allow my phone to boot but then I get apps crashing and then a reboot puts you back at ATT logo and the vibrates. Best to ditch the whole engboot and go back to stock until a more stable rooting method comes out.
Some searches shows posts that say using Odin to flash HOME_CSC without having to wipe and everything survive
... Where can I get HOME_CSC? I dl'd stock rom and dont see it in there.
thx!
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
I ended up wiping and flashing the T-Mobile firmware and using the ENG bootloader (but not rooted yet). It is WAY faster than the AT&T was. I've only had issues with Wifi Calling (it doesnt seem to work most of the time)
s7 at&t
Hi, did you first flash with eng bootloader and then tmobile rom? I miss this step...I appreciate your help please
Single vibration followed by the 3 vibrations
Hi, were you able to fix the problem? I'm also getting the single vibration followed by the 3 vibrations.
Do you know why is this occurring? I performed a wipe cache and factory reset but still nothing.
bweegn said:
Same here this morning on my 930A w/ PK1....went to watch a youtube vid and everything google related began crashing.
Only been on engboot for a couple days but did flash the v15 debloat last night. hmmmm.
Any luck with the files or procedure LivinOne?
Update: Flashed the PK1 CSC and got into recovery.
Wiped cache and reboot, same failure mode....sad face.
Flashed CSC again, into recovery, factory reset, wiped cache.
Back to setting my "new" device up.
Dec 30 update: Same crash, SEMI same problem.
I get the single vibration followed by the 3 vibrations after I put my pin in from a restart.
Same symptoms prior, all background activities began crashing.
Running all PK1 files from QRhinehardt post.
Any thoughts?
Click to expand...
Click to collapse
Related
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Wildey1771 said:
Hi
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Thanks
Click to expand...
Click to collapse
Data factory reset in recovery.
Wildey1771 said:
I reflashed my S5 with a stock rom to remove all the Carrier blocks and extras. After the flash the device booted up and instantly came up with the error saying acore has stopped working and then around around 5-10 seconds the phone reboots and does it again. What can I do?
Click to expand...
Click to collapse
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
fffft said:
It's hard to answer since you provided no crucial details about your phone, configuration or how you flashed it.
You didn't tell us which S5 model you have or your carrier. Nor what firmware file you flashed, so we don't know if it was a compatible file. No Odin log, so we don't know if the flash had errors or not. And you didn't describe how you flashed step by step so we don't know if you missed essential steps.
At a guess, try wiping the partition cache from recovery mode. Then if necessary, do a factory data reset as well (will delete user files!). If you have ongoing problems, then you should restore your backup and try again from that stable condition.
No backup? That is a bad habit to say the least. In that case, flash a full stock firmware image that matches the carrier that the phone was originally sold for.
.
Click to expand...
Click to collapse
The Model is SM G900F. Its On Three Carrier. I Flashed A STOCK (From SamMobile) Firmware 4.2.2.
The Flash Process Was Successful. No Errors.
Put Device In Download Mode
Connected To Computer
Loaded Firmware Into PDA
Ftime reset
Auto Reboot
Started The Flashing.
Completed.
Phone rebooted. Got Acore has stopped. Then the phone reboots.
But since I needed my phone working quickly I took the path of factory reset and that seems to have fixed it. I did try clearing the cache but no effect.
I believe I know the issue. I used a launcher called Themer. I have reasons to think that was causing the issue because as it was loading in the background I managed to quickly hit the continue button to close the crashed process boxes and as the Launcher finished "Loading" it when it rebooted.
WARNING FOR OTHERS. Always Remove Other Launchers Before Flashing As A Precaution! (Warnings From Newbies Hehe)
Hello everyone,
So here's my story: I got a 6P short after release and it's been amazing. After switching from a S6 I couldn't be happier until 3 days ago.
I was playing around with my phone (checking for updates on the play store if I recall correctly) and I was going to switch from 4g to wifi. I went ahead and pulled down my notification shade and went to press WiFi but misclicked and hit Hotspot which was below it. My phone suddenly froze big time and this is for the first time ever since purchase.
At first I thought I'd wait it out since the device was completely unresponsive, home button didn't work and neither did anything on screen. Buttons didn't make a difference either. 10 minutes went by and I ended up force restarting by holding down power + volume up. First part of my bootup went fine but when it got to the android boot animation after I put in my pin to allow the device to start it dropped from the smooth usual framerate down to 1 frame every 10-15 seconds and it slowed down further until it came to a complete halt around the time the android letters appear.
My first thought was corrupt rom so I went ahead and wiped data from the stock recovery. I was running completely stock with no modifications whatsoever. That didn't do anything. Phone still froze in the same boot phase. Desperate I unlocked bootloader to flash a clean fresh image to try to fix it and to my surprise that didn't change a thing.
As I was getting pretty desperate already I had one more idea and that was to flash up to the Dev preview. To my huge surprise it booted and I jumped from excitement. So I started setting up my phone again. I got past the prompt to insert sim card and I was now at the screen to choose a wifi network. As soon as I clicked into that the phone froze up again and at that point I lost all hope.
I wiped data in stock recovery and shut the phone down for the night. On day 3, today I woke up and tried starting the phone and it worked as if nothing had happened. I went through the setup and set up my phone on the N preview. At a certain point I was planning to go back to the latest official build but for now I was happy my phone was back from the dead. Later today I tried to restart my phone to clear all running apps etc and it froze up on boot.
I'm losing all hope that I'll be resolving this myself so I'm reaching out to the community to see if anyone's had this happen to them before and hopefuly for a solution. It's still under warranty so I can eventually send it back to the retailer but I'd rather not have a phone for 3 weeks.
Any and all help is appreciated.
Thank you for reading through my long and probably pretty boring story!
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
To the OP, is there any reason you did not flash to release version 6 instead of Dev preview ?
Also, any reason you can not simply do the "unenroll" from https://www.google.com/android/beta ?
It will require you to setup certain settings again as you will be back to a "factory reset".
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
DJBhardwaj, i haven't specifically erased those partitions. I was under the impression wipe userdata along with reflashing did that. I will try that tonight when I get home!
Xdafly, I only updated up to N as a last resort because at first I had a locked BL. I was planning to unenrol but that would've been too late as it self bricked after a restart.
DJBhardwaj said:
Have you tried flashing the factory image? If yes, did you made sure to wipe/erase the system, boot, vendor, and cache partition before flash the corresponding img files?
Click to expand...
Click to collapse
Well I just did the erase thingy and my phone booted but wifi won't turn on. Enabling hotspot doesn't brick anymore but I now suspect WiFi might've been the issue. Any tips on how to find out what it could be and possibly fix it?
Edit: 2 restarts and a factory reset later I'm back to bricked same way as before.
try safe mode
mr.dj26 said:
try safe mode
Click to expand...
Click to collapse
That was my first thought, that was the restart that bricked it again. Safe mode shouldn't have made a difference since I hadn't even logged into Google account for apps.
After reading the very first post; sounds like bad WiFi hardware.
All the hanging has been related to WiFi or Hotspot.
I think you should get a replacement
Sent from my Purified NexusixP
If Someone Helped You Then Dont Just say Thanks...Hit The Thanks Button!
Is your phone rooted and did you install Xposed?
Over the weekend I shutdown my 6p (stock rooted with April security patch, Xposed v80) and charged it. When it turned it back up I kept getting "Unfortunately, nfc service has stopped". Long story short: I ended up factory reset my phone and reinstalled EVERYTHING and I still got into bootloop. Then I came across
https://github.com/rovo89/Xposed/issues/113
https://github.com/rovo89/android_art/issues/28
At the end of the second post rovo89 (developer of Xposed) fixed the bug in V83. I wiped my 6p once more and installed everything with v83. Problem solved.
Good luck!
I had rooted my S7 edge (Exynos) a few months ago. I tried installing the ambasadii.zip rom.
I also followed there instructions to the letter.
Upon restarting the phone it started loading the apps, but then stopped halfway and froze. Sometimes restarting to then freeze again.
I reinstalled Recovery ROM and after many tries was able to install via Smartswitch the Stock ROM (Sammobile) 7.0 DQB3
Since then I have had a couple of crashes (average 1 a week). Once when opening Alto (game). The screen froze with a horizontal bar with stripes in it. Booted into recovery and factory reset but had to install stock again via Smartswitch.
Yesterday again a screen and system freeze. Thankfully I was able to restart.
I tried wiping everything with TWRP once I was in TWRP. But it seems that there is something else wrong. I would not mind going right back to full stock (I know the knox counter is tripped). Am I doing something wrong in trying to install the stock fw thru Odin3.12.3? Do I need a specific Revovery file? I am wiping with TWRP but someone else suggested that I had to format with TWRP, could this be the issue?
Or are others also having random crashes?
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.
So i was simply updating youtube through google play, and messenger through messenger it self and suddenly the phone went into boot loop and can't get it out.
opening recovery mode is hard but when i managed to do it, it simply shows the android icon and installing system updates then restarts again. (tried it ~4 times). thanks to that i can't try clearing cache or any of that stuff on the list that is supposed to appear in recover mode.
trying force restart also does nothing.
trying to remove memory card and sim also didn't work.
i read that flashing HOME_CSC from a rom could fix it but the rom websites i know offer limited sizes and speeds and i don't have a strong internet which ends up timing out, can someone help me out? G935FOJV2ERGE is the one i need.
if you have any other ideas that can help, i would also greatly appreciate it, i really don't want to have to buy a new phone atm, and don't want to lose all my data because i don't used backup services cuz they ate up data .
edit: I am on latest official rom, only used OTA updates, haven't rooted the phone.
edit 2: i managed to get a different region's rom and flashed it's home_csc file, and force restarted it and seems to have worked booted, then it started doing it again just 1 second after that. i didn't even have time to unlock it.
edit 3: managed to get into recovery mode list once, wiping cache didn't work. couldn't get into recovery mode again after that. then i gave up and tried flashing a full rom. still the same problem.