Database Users

Stuck at boot screen animation... was working fine!

I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.

Flapjack said:
I'm not sure what happened with my US Axon 7. I was getting it ready to give to my son, and now it won't boot. Even with a full wipe (including system) and reinstall of the OS. It tries to boot, but just sits at the Google animation forever.
Here is basically the steps of what happened during the wipe/install of the unofficial RR Oreo build:
- Wiped everything
- Flashed the B32+B10 bootstack (A2017X_BootStack_B32+B10.zip)
- Flashed the latest (at the time) unofficial RR Oreo build (RR-O-v6.0.0-20180511-axon7-Unofficial.zip)
- Flashed opengapps micro (open_gapps-arm64-8.1-micro-20180512.zip)
- Flashed Magisk 16.0 (Magisk-v16.0.zip)
- Booted up and setup the phone for his google account
- Rebooted multiple times during setup
- Installed TiBu and froze the apps I normally freeze for the kids.... things they don't need
- Rebooted one final time and got stuck on the boot screen
- Re-performed steps above (minus setup... because I still can't get it to boot)
The best I can figure is that I froze something I shouldn't have... but a wipe and reinstall should have fixed that. I don't understand why it wouldn't. I've even wiped system.
I'm going to see if I saved a backup somewhere, as it's not on the phone. I can still get into recovery and such, which is good.
Click to expand...
Click to collapse
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?

Choose an username... said:
Which apps do you freeze? If you froze some Google apps you can just use the pico package and avoid having to use TiBU entirely
Click to expand...
Click to collapse
I don't remember exactly... nothing I haven't frozen on their phones before.
You're saying that after doing the whole installation you set up the ROM, but after you freeze apps with titanium and reboot the phone refuses to boot?
Click to expand...
Click to collapse
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?

Flapjack said:
I don't remember exactly... nothing I haven't frozen on their phones before.
It seems to be that way. I had already installed Magisk, but it's not like I installed Xposed or anything "dangerous" to the operation of the phone. The only thing I can think of is I froze something that kept it from booting. But if that's the case, why wouldn't reinstalling the ROM fix it? Wouldn't that fix anything I changed/froze?
Click to expand...
Click to collapse
well, if you wiped and installed everything again it should work...

Something must have been wrong with the ROM itself. I don't get it, since it worked fine the first install. I installed AOSP instead and it booted right up. I'm going to take a full backup, freeze the things I normally freeze, then see what happens.

I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.

beokabatukaba said:
I was having a very similar issue while trying to move to exactly the same ROM. My problem was that I was accidentally encrypting the phone (I didn't realize that this is what the "require pin at startup" prompt was doing). If TWRP is asking you to put in a pin number every time you boot into recovery, then your phone is encrypted. RR ROM (or at least the most common version of it) does not support encryption, so it will refuse to boot.
To get rid of encryption, you have to select the "format data" option in the wipe menu. You can't just wipe the usual partitions.
I can't be certain that this is your issue, but hopefully it helps.
Click to expand...
Click to collapse
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot

Choose an username... said:
Not similar at all. In your case the ROM would boot fine, but it woupd fail to load your data, so it asks for a password that not necessarily exists. In his case the ROM never gets to boot
Click to expand...
Click to collapse
You misunderstand. I could only boot RR once, and if I accidentally encrypted the device during setup or afterward, the next time I tried to restart, it would be stuck on the boot screen. All subsequent reinstalls also got stuck on the boot animation since I wasn't removing encryption even if I wiped data, system, cache, etc. Moving to AEX allowed me to boot with encryption, and it was at that point that I realized my mistake. That sounds precisely like what is happening to flapjack, except that the cause may or may not be the same since he got through multiple boots the first time and presumably had already setup a pin/password on one of the first boots.
Immediately after the pin is setup should be when it asks if you want to require the pin on startup (aka if you want to encrypt), so if he opted to do that after setting everything up rather than on the very first boot, he may have exactly the same issue I had.

Weird bootloop

Have had my OnePlus 2 since 2015, and it's been a solid performer up to today.
I had the crDroid ROM (8.1) installed, along with Magisk, and it's been working fine for over a month with zero issues.
Today, I went to remove an app that was being troublesome, and then rebooted. And it just bootlooped. Animation is playing, but that's it. It sits there for 10-15 mins doing nothing. I hold the Power button to shut it down, and then try booting again. Same thing, just a straight bootloop for 15 mins. So I reboot to recovery (TWRP 3.2.1.0) and flash the Magisk uninstaller, to see if restoring the stock boot partition would help. It didn't, and just gave the same bootloop. So I go back into TWRP, wipe /system /cache and /dalvik and reinstall the ROM and gapps. Reboot. Same bootloop.
Now I'm starting to get a little concerned. Right now I'm restoring a backup from 10 days ago that I made before I last updated the ROM, but assuming this fails, does anyone have any good ideas? I'm not an expert, but I'm not a novice either, and this isn't making much sense. Unless my OnePlus 2 is getting ready to check out, which would suck...

idk if you had any mods like kernel or whatever or what app you removed (and if it had root acces) but first make sure you are on latest twrp, then try to clean flash a rom like normal. try to boot it it should work.

Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.

Gaffadin said:
Thanks for the reply. No mods, other than Magisk. Just a stock 8.1 ROM with Magisk on top. Wiping /system, /cache and reflashing the ROM did not work. In the end, restoring a backup from a week ago was the only thing that worked. I have no idea why or what happened, but I guess it's yet another reason to keep a good backup on your phone in case of situations like this.
Click to expand...
Click to collapse
This means that a date/time overflow occurred in your system
You restored a backup from 10 days ago, I'm assuming an older version of the ROM? So the newer version has an overflow bug
Even if nothing changes on the system your system time is always changing and if the ROM or kernel is somehow messed up then this value can cause an overflow and if a security module of some sort (like fortify_source or stack_buffer_protection) finds out about the overflow it can prevent boot from happening
Note: below example not completely valid in the real world, I've removed some stuff and is just for clear understanding.
Let's elaborate, "signed int" accepts values from -32768 to +32768 (0 inclusive)
What do you think happens when a value below -32768 is passed? That's an underflow and it's not defined what would happen below that limit (actually stuff does happen but see below notice)
If you pass a value over 32768 you cause an overflow
Note: I'm not going to go into details about what exactly happens. This would add too much information and cause more confusion than it would clear
What does this have to do with the date? Well every second your system date increases and if you got one of these limits you're going to run into problems
This is the only possible explanation for what could have happened

Thanks for the explanation. i think I understood most of it.
The backup from 10 days ago was from an older version of the ROM, though I have since installed the latest ROM version on top of the restored backup without issue, as I did when I first made the backup.

HELP! Can't get past lockscreen or decrypt in TWRP

I'm currently running a custom ROM (AOSiP), but this started happening on a different rom (Syberia). With a recent update, I noticed that suddenly I couldn't use fingerprint authentication for apps anymore. Eventually, I wound up having to format data (and sadly lost quite a few recent photos that had not yet been backed up) and start all over because neither the lockscreen nor TWRP would accept my correct pattern to decrypt.
Several wipe and resets later I decided to switch to a different ROM (AOSiP). And now I'm having the same issues with a completely clean flash (I started off with MSMDownloadTool to bring the phone back to factory). The ROM was working fine, as well as fingerprint and pattern unlocks, until I restarted. Now, I can't get past the lockscreen OR TWRP pattern unlocks. Here is what I found in logcat:
Code:
java.lang.RuntimeException: Failed to decrypt blob
at com.android.server.locksettings.SyntheticPasswordCrypto.decryptBlob(SyntheticPasswordCrypto.java:143)
at com.android.server.locksettings.SyntheticPasswordManager.decryptSPBlob(SyntheticPasswordManager.java:1117)
at com.android.server.locksettings.SyntheticPasswordManager.unwrapSyntheticPasswordBlob(SyntheticPasswordManager.java:978)
at com.android.server.locksettings.SyntheticPasswordManager.unwrapPasswordBasedSyntheticPassword(SyntheticPasswordManager.java:907)
at com.android.server.locksettings.LockSettingsService.spBasedDoVerifyCredential(LockSettingsService.java:2426)
at com.android.server.locksettings.LockSettingsService.doVerifyCredential(LockSettingsService.java:1700)
at com.android.server.locksettings.LockSettingsService.checkCredential(LockSettingsService.java:1667)
at com.android.internal.widget.LockPatternUtils.checkCredential(LockPatternUtils.java:374)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:426)
at com.android.internal.widget.LockPatternUtils.checkPattern(LockPatternUtils.java:413)
at com.android.server.locksettings.LockSettingsShellCommand.checkCredential(LockSettingsShellCommand.java:182)
at com.android.server.locksettings.LockSettingsShellCommand.onCommand(LockSettingsShellCommand.java:59)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.locksettings.LockSettingsService.onShellCommand(LockSettingsService.java:2074)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at com.android.internal.widget.ILockSettings$Stub.onTransact(ILockSettings.java:532)
at android.os.Binder.execTransact(Binder.java:731)
Caused by: java.security.InvalidKeyException: Only SecretKey is supported
at com.android.org.conscrypt.OpenSSLCipher.checkAndSetEncodedKey(OpenSSLCipher.java:462)
at com.android.org.conscrypt.OpenSSLCipher.engineInit(OpenSSLCipher.java:296)
at javax.crypto.Cipher.tryTransformWithProvider(Cipher.java:2980)
at javax.crypto.Cipher.tryCombinations(Cipher.java:2891)
at javax.crypto.Cipher$SpiAndProviderUpdater.updateAndGetSpiAndProvider(Cipher.java:2796)
at javax.crypto.Cipher.chooseProvider(Cipher.java:773)
at javax.crypto.Cipher.init(Cipher.java:1288)
at javax.crypto.Cipher.init(Cipher.java:1223)
at com.android.server.locksettings.SyntheticPasswordCrypto.decrypt(SyntheticPasswordCrypto.java:63)
at com.android.server.locksettings.SyntheticPasswordCrypto.decryptBlob(SyntheticPasswordCrypto.java:135)
... 17 more
Obviously my device is encrypted so I my only option is to format again and start over for the 4th time in the past 2 days, only to worry that this might happen again. Can anyone help? Thanks in advance.
NOTE: Sig is outdated.
EDIT: Not sure if it is relevant, but the phone was initially encrypted via OOS, then wiped and set up via AOSiP with encryption already in place.

You didn't say what version of TWRP? Generally when going between AOSP and OOS formatting data is necessary otherwise you will have encryption problems. MSMTool is sort of a drastic measure though.

OhioYJ said:
You didn't say what version of TWRP?
Click to expand...
Click to collapse
Initially twrp-3.3.1-1 but now twrp-3.3.1-7 unofficial
MSMTool is sort of a drastic measure though.
Click to expand...
Click to collapse
I was fed up and figured a bone stock base couldn't hurt at that point since I had lost everything already anyway.
Generally when going between AOSP and OOS formatting data is necessary otherwise you will have encryption problems.
Click to expand...
Click to collapse
I may have just come to the same conclusion. I formatted and left forceencrypt enabled, then set up using AOSiP and now fingerprint auth works in apps again. Initially I never did it this way because forceencrypt would be disabled with fresh formatting, and the in-rom encryption option resulted in FDE rather than FBE for some reason.
Was this a recent development that formatting was required? I had no issues for 7 months with my OOS encrypted data until now.

Any ROM that has the May security patches will require a newer version of TWRP, so 3.3.1-7 may have originally decrypted your data, hard to say. I don't remember which version originally included that fix. It's been in there for a few versions though.
Formatting data has been a thing for a while, essentially the entire time as far as I'm aware (I've always done it that way). Even though it's a pain. It's the only way to avoid problems. This is how to do it. Some ROMs may handle not formatting this better than others, but it seems like skipping that step is when problems happen.
I don't think there is a way to get to FDE on these devices, otherwise your phone would ask for a password on boot.

OhioYJ said:
Any ROM that has the May security patches will require a newer version of TWRP, so 3.3.1-7 may have originally decrypted your data, hard to say. I don't remember which version originally included that fix. It's been in there for a few versions though.
Formatting data has been a thing for a while, essentially the entire time as far as I'm aware (I've always done it that way). Even though it's a pain. It's the only way to avoid problems. This is how to do it. Some ROMs may handle not formatting this better than others, but it seems like skipping that step is when problems happen.
I don't think there is a way to get to FDE on these devices, otherwise your phone would ask for a password on boot.
Click to expand...
Click to collapse
Actually, FDE is what I would initially get with formatted data and a clean install with forceencrypt disabled. If I tried to encrypt via settings, I would get FDE and password before boot. At least initially it was that way (circa when FP first became possible on custom roms 8.1). I had never bothered messing with it after that, as I had no issues with the OOS encrypted volume. Oh well. At least now I can be sure it has been done correctly. Thank you for the insight!
Mods please mark as solved

Unable to restore backup during configuration and cts check failed

Hi,
I have a Oneplus 6T A6013. Yesterday my phone had this state:
bootloader u
nlocked
root installed with magisk
a couple of magisk module installed
latest stable
stock rom (10.3.0)
Then an OTA update (10.3.1) arrived to me and I installed as usual:
OTA full download and
installation, without reboot
Magisk installation o
n other partition and reboot
Here begin problems. My phone reboot and get stucked on OnePlus animation.
I can force shut down, enter stock recovery, enter bootloader.
I can not rely on
Code:
fastboot boot twrp.img
because phone reboots and stucks on fastboot logo.
I decide to do factory reset phone, with Google backup it is not a big problem, during configuration I obviously login in with the same account and obviously backup is on cloud, but phone says "no backup found".
Moreover it seems that magisk root files were still present on the phone, and even "uninstalling" them from magisk manager doesn't remove sucessfully them.
At this point I have tried to make a completely fresh install of the OS:
during configuration still no backup found, even if I have created more backup in the meanwhile, one of them jsut before fresh install and on Drive I can see all of them
Google Pay sais that my system is not right, maybe cause root
using Magisk Manager I have checked that this time root is no more installed, but I can see that "cts check" fails
Play Store -> settings also says to me that "my phone is not certified"
Maybe I am not able to recover backup cause cts check fails. I have still bootloader unlocked.
So here are my questions.
Someone knows beacuse my phone doesn't recognize its own backups?
How can I pass cts check?
In case I should relock bootloader, how can I check that everything is truly stock and avoid a possible brick?
Thank you so much for your future answers, I have searched on internet and made tries for a whole day and contacted OnePlus chat assistence twice, but without any luck.

You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP, and you MUST use the latest one (always use up-to-date tools) which in that case is TWRP 3.3.1-31 - you have to use "Q" version of bootable TWRP image for OxygenOS 10.3.1 which is obviously Android 10 Queen Cake so be sure to use the right one.
Tethered Fastboot TWRP boot works just fine for me, in fact I installed crDroid 6.2 ROM atop OxygenOS 10.3.1 on my converted T-Mobile OnePlus 6T.
As for the bootloader, once it's unlocked, I strongly recommend leaving it alone unlocked unless you really like to use MSMTools more often. Use SafetyPatch in Magisk's module manager, it will fix the CTS SafetyNet issues. Locked bootloader actually causes more problems compared to unlocked one in my experience.
Sent from my ONEPLUS A6013 using Tapatalk

First of all thank you very much for your answer.
Is this type of twrp right?
I thank you really much for your suggestion about locking bootloader. I don't want to specifically remove root, the real problem Is that I am no more able to recover my old backup. I have just supposed that bootloader and root could be tha causes.
Before I fully reflashed OS I was able to Hide robot and pass all checks using Magisk, buy as I said I was not able to recover backup, neither a fresh and new just made backup.
I worry about the future. Now I could set again all the phone, but what will happens if tomorrow I will have to reset again?

Dr. Mario said:
You have to actually wait a few minutes after running "fastboot boot boot.img" command to boot the TWRP
Click to expand...
Click to collapse
I used latest version by fajita downloaded from my previous link. I have waited for 10 minutes stacked on oneplus fastboot mode logo and nothing happens. Now I have the problem that I am no more able to flash magisk...

That doesn't sound good - MSMTools may be necessary. Did you back up all the files?
If your T-Mobile OnePlus 6T is converted, install OxygenOS 9.0.11 and unlock the bootloader once again (MSMTools usually relock the bootloader, so unlock it again), then update to OxygenOS 10.3.0 or 10.3.1 via update zip file (I don't trust OTA updates at all, they tend to cause problems), then install the TWRP once you're at it, and then reboot back into the recovery and install Magisk if you want to.
Unless... You want to install custom Android 10 operating system which then you must do that; First reinstall OxygenOS 10.3.x ROM (in all slots, it is mandatory because you will install the same custom OS on both slots so it boots properly) then boot into TWRP, and do factory reset and data wipe in the Wipe menu, then reboot back into recovery and then plug in the USB flash drive or copy the TWRP, OS installation zip and whatever else you want installed onto the phone via the computer. Then install crDroid, LineageOS or any of OS of your choosing, and TWRP, and reboot back into recovery once again and install the OS and TWRP one final time in another slot. After doing the last reboot, install Gapps and Magisk. Finally, after you are done and reboot the phone after the installation, it will reboot by itself once - that's due to Magisk doing some configuration.
Android 10 apparently have made installation of custom ROM difficult. I have managed to brick my OnePlus 6T eight - ten times before deciding to find out how to do it successfully, thus the instruction for installation of custom OS above.
As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).
Sent from my ONEPLUS A6013 using Tapatalk

Dr. Mario said:
That doesn't sound good - MSMTools may be necessary. Did you back up all the files?
Click to expand...
Click to collapse
Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.
Dr. Mario said:
As for failure to restore the backup, this is the artifact of the Android 10 UEFI bootloader encryption (which is occasionally buggy, and annoying - just installing the LineageOS 17 the normal way, the whole SSD just gets corrupted, so the trick to get it to work is to, yes, remove all SSD encryption keys via factory reset prior to installing any custom ROM). As of now, TWRP backup is broken on most phones running Android 10 which is due to how the encryption works in this OS version (to the point they are so touchy).
Click to expand...
Click to collapse
Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.

Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)
As for MSMTools, I really wonder. OnePlus didn't object before.
Sent from my ONEPLUS A6013 using Tapatalk

Gabriel1495 said:
Yes, my device is actually ready to be wiped and I have already the international version.
The problem is that MSMTools' link are down.
Do you mean "manual backup" such as nanodroid, or "automatic Google backup"?
I have no manual backup, only that one saved on Drive, it should be restored automatically during configuration of operating system.
Click to expand...
Click to collapse
Try this thread
https://forum.xda-developers.com/oneplus-6t/how-to/op6t-collection-unbrick-tools-t3914746

Backup argumentation is now more clear, thank you
Dr. Mario said:
As for MSMTools, I really wonder. OnePlus didn't object before.
Click to expand...
Click to collapse
About MSMTools I have still some problem, fault of my really bad English...
I have not understood your answer, what does it means "OnePlus didn't object before"? Actually I am simply no able to download the tool.
Thank you again for your kindness

Striatum_bdr, that will do. The unbricking tool collection looks good.
Sent from my ONEPLUS A6013 using Tapatalk

Wonderful, I will read the "unbricking tool" thread in order to understand how to install it

Hopefully you get it to work once again.
Sent from my ONEPLUS A6013 using Tapatalk

Here I am with some good update
I have used MSMTools to truly factory reset my phone. Initially I had "sahara connection" error, but install again both Qualcomm and Oneplus drivers do the trick. After execution of MSMTools phone reboot with bootloader locked and as it was out of box.
At that point on Drive I had 3 backup (9 Feb, 10 Feb and 10 Feb) and magically last backup of 10 Feb was seen! Saddly even deleting last two backups I am not able to recover my true backup of 9 Feb (at this point it doesn't matter).
Now I have a virgin and working phone. I have no root and can use Google Pay and banking apps.
Really happy and satisfied, thank you thank you thank you very much!!!!

Dr. Mario said:
Any way you can back it up. TWRP backup (and any nandroid) in general are broken for many Android 10 phones because of the SSD encryption - I suspect that by each reboots, new cipher keys may be generated every time, thus making it hard to be able to successfully reinstall the Nandroid backup at any point in time - they're like the snowflakes, each and every EXT4 ciphers are different. (All that is meant to resist the hacker attack, even on the custom ROMs - Google wanted to be sure they cover everyone in term of computing security, so all that encryption Voodoos are also in the AOSP and LineageOS repositories for that reasons.)
As for MSMTools, I really wonder. OnePlus didn't object before.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
What is up with that? I booted into TWRP the other day, figured I would make a backup before upgrading, and everything was garbled.

That's because of the onboard encryption; all Nandroid backup being attempted on Android 10 only hold half of the overall encryption keys, others just stays on the phone, so when you attempt to put it back on, it is already invalidated because also Android 10 ROM on some phones (particularly the Pixels, and a few OnePlus phones like this one) changes keys upon reboots for security reasons.
Google do not want anyone including the US Government to have their hands on the data thereon as it could be very bad if it falls in the wrong hands so they went extra miles to make it difficult to hack.
Sent from my ONEPLUS A6013 using Tapatalk

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.)