Database Users

[Q] S5 Reflash - acore has stopped working REBOOTS

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)

[i9505] Cannot enter Recovery after Format Data

My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.

vizavalk said:
My i9505 was running stock KitKat from Samsung and I tried to install CM13 ROM.
So I used Odin to root the phone and installed TWRP 2.8.6.0. After that I flashed the CM13 ROM and the Gapps Nano.
I got as far as rebooting into CM13. But then the "Google Play Store has stopped working" message keeps popping up starting from the initial setup phase. I ignored the message and went on to setup the wifi but couldn't progress any further. The wifi was detected and connected but then it was stuck on the Checking Connection/Software Update step.
I tried to reflash the rom and gapps again to no avail. The third time to Format Data from TWRP before reflashing - still didn't make a difference.
What's worst is now I cannot even get into TWRP! Whenever I press Vol Up + Power + Home, it will show the small 'entering recovery' message momentarily on the top left corner but then it phone simply restarted again.
I tried re-flashing TWRP using Odin, but still didn't work.
I'm stuck now, cannot get into the OS nor the recovery. Any suggestion as to what to do?
Thank you.
Click to expand...
Click to collapse
Format Data from twrp sometime corrupts the file system and brick the phone. (It's happened to me once)
The best way is to flash official firmware via odin and start from there.

I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.

vizavalk said:
I see - I'll try re-flashing the official rom. Btw, would you recommend CWM recovery instead then? Honestly, I'm not very proficient with this whole thing. The reason why I formatted was because I still could see all of my old folders in the phone memory. So I thought Factory Reset didn't really clean up my old rom data.
What do I have to do if I want to start with a really clean slate with CM13 (after reflashing the official one first)?
Also, I still have the issue of CM13 setup being stuck at the Software Update step (right after Wifi setup). Any clue why that happened?
Thanks for taking the time to reply.
Click to expand...
Click to collapse
CWM is outdated. Your best bet is TWRP. Try version 3.0.0.
Factory reset doesn't wipe your internal memory, if that's what you mean, you will have to do it manually.
Also, I recommend wiping data, cache, dalvik and system partitions manually from the advanced wipe menu. Factory reset only wipes data and caches, not system.
Oh, and about that stuck at setup issue, just skip that step if possible, you can still change that crap later

If you are unable to set up the ROM, you could flash back to a completely stock ROM and start over.

OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.

vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.

vizavalk said:
OK, I'm back on stock Android now.
Before I try flashing CM13 again, I just need suggestions about these two issues I had from previous try:
Unfortunately, Google Play Store has stopped
I have searched for similar issues but can't quite pinpoint the cause. I used the correct GApps for my device and I also removed my SD card prior to installing.
Stuck on Check Connection/Software Update step
Last time I was stuck at this point and, responding to GDReaper, this step couldn't be skipped. The option was grayed out.
Click to expand...
Click to collapse
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/

GDReaper said:
The sd card has nothing to do with it.
Sometimes gapps don't work on certain roms.
Just try another package.
If you use A-Gapps, the whole first time setup step will be skipped altogether. So that means that you won't run into the risk of getting stuck at that step again.
Or, after flashing the rom, you could use the recovery file manager to delete the setupwizard.apk after you flashed gapps. That should also prevent the initial setup process from initializing at first boot.
Click to expand...
Click to collapse
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Lennyz1988 said:
You probably used Opengapps. That also gives me a lot of errors.
Use Bankgs Gapps instead. They always work for me.
http://download.dirtyunicorns.com/files/gapps/banks_gapps/
Click to expand...
Click to collapse
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?

vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
There are two files - one says Dynamic. But the file sizes are exactly the same. Is there any difference?
Click to expand...
Click to collapse
Not that I know. Just pick the one without Dynamic.

vizavalk said:
I used Open GApps, as was recommended in the CM13 post. So are you saying that my two issues were caused solely by the GApps? Because I thought me being stuck at Software Update was due to something else.
Click to expand...
Click to collapse
The initial setup process is related to gapps. And I don't recall there being any software update requests during the initial setup. It tells me to wait while it scans for network and WiFis, but I always skip those steps.
Open gapps sometimes work and sometimes they don't. It varies from day to day, since they are updated daily.
Just find a gapps package that works and stick to it until another version of android.

I just want to report back that my CM13 works perfectly with Banks GApps. Thanks to everyone who has helped!

Verification Failed, Unable to restart your device.

This dreadful error: "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data."
And a "Reset" button.
Nothing seems to have caused this. One minute phone was sitting on my desk happily, the next it rebooted itself (I assume) and this error appeared. Given that I'm not interested in losing my data I haven't pressed the factory reset button... because that's just silly.
- Phone is S5 Neo (W version). Rooted (CF-autoroot) with TWRP installed. Has been this way for months.
- Software updates are turned off
- ADB is disabled but I can access terminal using TWRP.
- Data partition is encrypted
What I've done so far:
- Backed up my Data partition using DD; but as it's encrypted I can't access the data
- Attempted terminal "twrp decrypt mypassword" using the password I used to unlock encryption at boot (result: "Failed to decrypt data")
What do I do now? Is there any way to decrypt this partition on my PC (I have linux and windows available to me) to at least rescue my data?
Thanks in advance...

I just had the same thing happen to me with the exact same model with the exact same settings as well today about a couple hours ago EXCEPT I never rooted the phone like yourself. So it isn't developer mode or anything like that. That can be ruled out. It's such f**king BS!
I heard rumors about nonsense like this years ago and the only way to supposedly fix the problem is to send the phone into samsung where they fiddle with the phone, never fix it, keep it (for whatever reason ??), and send a new phone back out IF we fall into warranty.
With all the corruption in the world and the shady happenings with government and businesses, why in the hell would any logical person send their phone back in to an OEM after it's been used? I'm a good person and come from a good family and all that, but ever since I had my information stolen from me a little over 5 years ago I really don't want to send my phone in and have my life in shambles again. No damn chance!
I'm thinking about calling in but I want all my info! I have important work related documents on here!
Only thing I am going to ask you is what software did you use to back it up (DD?)

Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!

Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Shameera_N you sound pretty smart....but why didn't you read the comments we posted and actually try and answer what we asked? WE DO NOT WANT TO WIPE OUR DATA and there is no way that wiping is part of the solution.

For this do we need a rooted phone?

This happened to me on a completely stock SM-G903F with data encryption enabled. So it has nothing to do with custom recoveries or root. It seems that the encryption method is flawed.
I don't think there is a way to get out of this one, so I wiped it. I don't have all that much stuff on the internal SD of my phone except for apps and messages. Your SD card won't get formatted, so if you save your photos there, they should be safe.
It's a pain, but this means you can't really safely use data encryption unless you regularly take backups (and even then, factory resetting a phone is no fun), even if errors like this only happen once in a blue moon.

This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss.

Same problem with a samsung galaxy s5 neo. Envrypted partition, Stock firmware, no root and updated.
At least i understood what caused it. I was listening to a youtube video. While the video was playing, i pressed the power button and switched off. When i switched on, i could not start android anymore

Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Thanks for the link, do you know who built this? Need update for 7.0...

githyanki said:
Thanks for the link, do you know who built this? Need update for 7.0...
Click to expand...
Click to collapse
You can use same for 7.x.x Use latest version from the link

I know this isn't exactly related to the issue in this thread, but I'm not having much luck elsewhere.
My completely stock J3 (2017 model, J327A) was hit with verification failed. From what I've seen, I can fix my issue merely by flashing the original OS back into my phone. I have the files and programs I need to do this.
But I can't get the phone into download mode. I can boot it up to the warning screen. It tells me to press VolUp to enter download mode, or VolDn to cancel and restart the phone. However, neither pressing nor holding either of them does anything. I know they aren't broken, as I can boot into recovery mode as well, which requires VolUp. The buttons just don't respond when I'm at the warning screen. Is this something I can work around, or something I have to be patient with, or something I can't fix?
(Data partition is encrypted, though. Not sure if that will affect this.)

Simply long press the Shut Down Button !!!!!!!!
I simply pressed the shut down button and restarted my phone and it worked !!!!!

A light at the end of the factory reset error tunnel!
Well I had an encounter with that dreaded 'factory reset losing all data' message and I'm telling you I was furious! Anyways, after a few seconds of gasping and wondering how the heck am I gonna retrieve all of my data and stuff, the thought came to me to try some 'old school tactics' which involved removing the battery and pressing the power button to drain any residual power remaining on the phone's circuit board and then try powering up after reinserting the battery. Low and behold, the phone booted up with no issues at all. I was able to log in and access my phone as if nothing happened. It's funny how that one message can just change your whole outlook on things. I just hope that folks out there will try this and perhaps it will work for them instead of losing all their data and jumping through all sorts of hoops. Most importantly, BACK THAT THING UP!! You never know what next will come out of the woods at any given time!

Resolved error without loss of data
Hi,
I came across this problem today as soon as I woke up today, but was able to solve it.
I have a Samsung J5 prime phone and did the following steps:
Why this occurs?
The system thinks you wish to root your phone.
How to solve this?
1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button.
you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it.
NOTE: I did not want to root my phone.
2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data.
Hope this helps!

if u can boot into recovery, go ahead and wipe cache/dalvik cache and reboot
this worked for me without any loss (i used twrp recovery to wipe and my device is SM_C900F /INS variant)

zay2046 said:
This happend to me on my SM-G920P. I just odin flashed stock rom and back to new no data wipe or loss.
Click to expand...
Click to collapse
Sir, can you guide me a bit further ? it just happened with my J7 prime and i don't want to loose data.

Same Problemo
I Jst Had The Same Issue, Bit I Fixed It Straight Away, Jst By Restarting It, Hold Both "Up & Down Volume", "Power Button" and "Home Button", And It Restarted & Worked

This works!
This worked with my daughters J7. THANK YOU!
udit_e said:
Hi,
I came across this problem today as soon as I woke up today, but was able to solve it.
I have a Samsung J5 prime phone and did the following steps:
Why this occurs?
The system thinks you wish to root your phone.
How to solve this?
1) when you have the verification failed screen, press "power" button + "Home" button + "Volume Down" button.
you'll be presented with a new screen which gives you 2 options-first, installing a custom OS and second, canceling it.
NOTE: I did not want to root my phone.
2) Hence, I chose the 2nd option and after that, my phone restarted with no loss of data.
Hope this helps!
Click to expand...
Click to collapse

Shameera_N said:
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disabler https://build.nethunter.com/android-tools/no-verity-opt-encrypt/, Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Click to expand...
Click to collapse
Came here to thank you with all my heart, this worked. I've been using TWRP for years on several phones, and I never knew that Wipe > Format Data did something different than Wipe > Advenced Wipe > Selecting Data > Swiping. I thought it served the same purpose. I don't know if the script did anything, though (because I used it before, but without formating data, and it didn't help at all).
Anyway, thank you so much!

how to remove Verification Failed or root in the TWRP file manager without losing data

My rooted samsung galaxy s4 is soft bricked, Can I save the data?

Yes this post is correctly dated. I've had this device a LOOOONNNGGG time.
The device has been rooted since shortly after I bought it new years ago. I've had very few problems since... which is why it's never been replaced.
I believe I have the stock ROM, sorry it's been a while.
When I start the device it gets stuck at the splash screen with the sprint logo.
I can get the device to "download mode" but I don't know what to do once there and I'm not sure I can do anything from here.
I can get the device to "android system recovery."
I know I installed TWRP when I rooted and installed the rooted ROM but when I boot to recovery it doesn't go there.
I've wiped the "cache partition" but the problem remained. I'm not sure what else to do from here and still be able to salvage data.
I'm trying to salvage the data on the internal storage. I'm pretty sure I could successfully "wipe data/ factory reset" and get it to "function" again but that's not the priority. I'm going to replace it regardless of success or failure. Data recovery is the priority here. (pictures and videos of my young children as well as less important stuff like contacts.)
I have an old laptop with an old version of ubuntu I can use or a newer one with windows 7 to work with. I mention this in case it makes this easier to help?
Thank you very much if you try to take a stab at this or refer someone that might!

Update:
So I managed to install TWRP via Odin.
I booted to this recovery and my data partition appears to be empty?
When I try to back up I get the error message "unable to mount '/data'"
I tried doing a wipe, not one of the fancy extra options ones just the regular wipe and it failed.
Any guidance will be extremely appreciated.
Edit:
So I've come to the conclusion that the data isn't accessible because of encryption and my pass code. Is there any way to enter it via recovery and access this info?
Is anybody out there?
Edit 2:
I hope this helps someone someday. I haven't solved the problem but I think I'm making progress.
First I had an old version of TWRP. I installed the latest for my device and tried backing up again. I'm not sure but I think it's working. TWRP dosen't seem to need my password for the backup. I imagine I'll just need it to access the data later.
Edit 3:
No sooner did I save the last edit and my backup failed.
Process ended with error : 255

S5, Flashed TWRP and custom ROM, restored stock from another phone, how to unmess?

Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine. (And yes, TWPR's check md5 option was disabled, so this wasn't the problem)
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
EDIT: Even if my description of the procedure looks like I flashed a ton of stuff all at once I have just WRITTEN A RESUME AS CONDENSED AS POSSIBLE - the procedure took me more than a week of flashing ONE THING AT A TIME and testing if everything works fine. At no point in my flashing procedure there were more than three things present on my phone: TWRP, ROM and MAGISK as kernel and camera mod refused to flash anyway. To exclude Magisk being a problem I clean installed everything so I had just TWRP and ROM and I was getting the same problem. Then I reflashed TWRP only, using the IceMan version (because it presumably solves all flashing problems) retested, then flashed /e/ only, retested, Havoc only, retested... well, you got the picture!
I was doing everything under the guidance of Intelli kernel Telegram support group members until I understood the problem was not the kernel, nor TWRP/IceMan, nor /e//Havoc and went with the stock recovery through TWRP and messed my phone beyond Intelli kernel Telegram group's scope.

ShalaMala said:
Hello.
This is my first post as I've done everything myself till now, but now I'm really lost in some uncharted territory.
All I wanted is to have a second DeGoogled phone and I messed my Samsung Galaxy S5 beyond my understanding
So, I flashed TWRP to my SM-G900F klte through Odin and then installed /e/ ROM through zip method and everything was working fine, then I wanted to flash Intelli kernel, but I got an error saying "Digest failed to match on '/external-sd/Intelli-Kernel-v15-klte.zip'. E: Aborting zip install: Digest verification failed. Error installing zip file '/external_sd/Intelli-Kernel-v15-klte.zip'". I double checked the md5 of TWRP, /e/ and Intelli Kernel zip's, reflashed TWRP, flashed IceMan's TWRP recovery, wiped all partitions, formatted data and re-installed /e/, tried Havoc ROM, but I still got the same message. The problem wasn't only with the kernel, but also with some (not all) other zip's like A2camforS5_TWRP_v1.4.zip and even Magisk (which flashed fine) modules like A2camforS5_Magisk_v2.zip were not flashing (the procedure got through, but once the phone restarted the module wouldn't show up). On my previous SM-G900F klte phone everything was working fine.
After a bit of chatting on Intelli kernel and /e/ Telegram support groups I found out it wasn't the kernel or /e/ problem and that I should go back to stock and start all over. I had a full NANDroid backup from my previous phone so I renamed the backup folder to match the new phone serial (so it would show the partitions to restore in TWRP) and as I (and nobody else) didn't know where the problem was I restored all partitions. Everything went through as it should except modem, which showed an error saying something about being read-only and efs, which went half way through and then gave an error I don't remember (but can reproduce if needed). The phone wouldn't boot to OS (it was stuck on SAMSUNG logo), so I re-flashed TWRP and /e/ again and tried to flash the kernel or other zips but they were still giving me "digestion" problems... but it got worse! Now when I boot to /e/ I'm not even able to use the phone normally as a pop-up saying "Bluetooth app has crashed" and "Bluetooth app keeps crashing" shows up continuously even if Bluetooth as other wireless connection work just fine. Did I mess something up with the unfinished efs restore?
How can I diagnose the problem and unmess my phone? What steps should I take? I'm afraid of bricking my phone if I just start to do random stuff so any useful information would be appreciated! Please help!
Click to expand...
Click to collapse
Idk what your phone's actual issue is, but you should probably not have restored efs from previous phone.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card. If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
DO NOT INSTALL TWRP APP
Also, try to do things in small traceable steps to make it easier to see what is causing your problem.
Eg:
Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
That's all the advice I can think of right now, how it is some help to you.
Good luck! :good:

you should probably not have restored efs from previous phone.
Click to expand...
Click to collapse
Yeah, I assume that was the stupidest thing, but an online guide suggested it's ok to restore from another phone's NAND backup as long as it's the same model, so I thought it was safe.
At this point, I would probably Odin back to latest stock firmware, to see if the phone will boot and recognize sim card.
Click to expand...
Click to collapse
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM.
Click to expand...
Click to collapse
Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
DO NOT INSTALL TWRP APP
Click to expand...
Click to collapse
Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Also, try to do things in small traceable steps to make it easier to see what is causing your problem. Eg: Flash just the bare ROM, nothing else, no Magisk, no hacky crap, just the ROM. Test it.
Click to expand...
Click to collapse
Yeah, I was doing the things one step at a time, my message is just a condensed resume of all the steps I did to make it shorter. I stopped adding things once I was unable to flash the kernel, camera mod and Magisk modules - I didn't just add everything I was trying to understand if the problem was just with kernel or my phone wouldn't flash also some other zips.
If everything is satisfactory, then try the next step and test again, working your way up to your desired ROM/kernel/Magisk/apps solution that makes you happy.
Click to expand...
Click to collapse
Yes, yes, that was the plan, but now the bare ROM doesn't want to work anymore without giving me Bluetooth app crashes
For maximum stability it's always preferable to format data (Advanced wipe>format>type yes) when flashing a ROM to ensure a clean slate for everything.
Click to expand...
Click to collapse
I did that before every flash.
Also, try not too let your phone get too hot with lots of flashing. I've seen good phones do odd stuff when overheated.
Click to expand...
Click to collapse
Good to know!
That's all the advice I can think of right now, how it is some help to you. Good luck!
Click to expand...
Click to collapse
Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot. I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?

ShalaMala said:
My phone works fine with /e/ ROM as before - SIM, Wi-Fi, Bluetooth and all, there is just a constant pop-up saying that the Bluetooth app has crashed interfering with everything I do that wasn't present before the stupid restore to stock.
Click to expand...
Click to collapse
"If so, I would go from there, flash latest official TWRP, format data, and either restore the backup sans modem and efs, or try a different ROM."
A: Did all this except trying a different ROM, because it wasn't producing the Bluetooth app has crashed problem before restoring to stock, so I assumed it's not a ROM problem. The digest problem was present also in Havoc ROM.
Click to expand...
Click to collapse
Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
https://androidfilehost.com/?w=files&flid=59628
You can flash that without wiping and it only touches the baseband/firmware files, so should not affect anything else
"DO NOT INSTALL TWRP APP"
A: Why? Is this a general issue or just a problem in my case? Anyway I have disabled the option before restarting to system.
Click to expand...
Click to collapse
It's a general issue. The app is bloatware and is known to sometimes cause bootloops see @curiousrom 's post here:
TWRP App Causing Bootloop or Fail To Boot
It's frustrating that TWRP is setup to facilitate easy swiping to install the app
A: Thank you. So now I flashed the latest .tar.md5 file for my model and my CSC through Odin and the phone wouldn't boot to stock ROM (I guess because it had /e/ Pie on it already and the latest stock ROM is just Marshmallow so it's considered downgrading), got stuck at SAMSUNG logo and phone went extremely hot.
Click to expand...
Click to collapse
Unlikely due to /e/ ROM, I have had this happen before. Just pulled battery, hold power button with no battery or charge cable for at least 10 sec to clear remaining charge (I have one phone that will get itself so out of shape that I have to leave it overnight with no battery before it will boot), let it cool, reinstalled battery and try again. Usually it will boot after this.
I pulled out the battery, went in download mode, flashed TWRP, wiped all partitions, formatted data, flashed /e/, booted /e/, the message about Bluetooth app crashing persists, went to TWRP, tried to flash Intelli kernel, got the "digest" error, tried camera mod, got "digest error" again, magisk flashed fine, so flashing works... so what now? I checked inside the .tar.md5 file and there is no efs partition so I guess it wasn't written over by flashing through Odin
Should the phone be able to boot to stock? Is that even necessary - would it fix anything?
Click to expand...
Click to collapse
Flashing stock ROM can sometimes help fix EFS issues, so that is why I suggested that. I also like to see the stock ROM boot with all functions working to make sure the hardware is ok.
I don't assume you haven't done any of the things I suggest. I'm just brainstorming to see if I can help you from my personal experience with my S5s.
Hope you can get yours working:good:

Maybe try flashing just the baseband with latest modem, etc from haggertk's archive on AFH, here:
androidfilehost.com/?w=files&flid=59628
Click to expand...
Click to collapse
I'm reading some instructions: ohthehugemanatee.org/blog/2015/04/04/how-and-why-to-update-the-modem-slash-baseband-firmware-on-a-samsung-phone about how to flash baseband as this is something I've never done before and I'm afraid to mess my device even further... They say "Note that each carrier handles their own updates, so they package their own modem firmwares with slightly different serial numbers. There shouldn’t be any significant difference, but check which one comes from your country and provider".
So I searched for the CSC of the firmware you've linked and it seems to be XXU: samfrew.com/download/GALAXY__S5__/1l88/BTU/G900FXXU1CRH1/G900FOXA1CRH1, which turns out to be a "Multi-CSC for some of the countries and regions (“O” refers to Open)"... is that "some" that bothers me as XXU is not listed under my country's CSC list.
Should I worry? Is it possible to try out if this baseband solves my problems and if it will not work return to the previous version flashing the stock ROM again or am I risking to brick my phone? I didn't find a baseband for my country's csc (SIO) as I will not be receiving any official updates anymore should I change my phone's CSC to XXU first?
(I'm not able to post URL's yet, so they are truncated.)