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
Related
So I unlocked the bootloader, formatted the data partition so it's not encrypted and flashed Lineage 14.1. Everything good so far.
Now my company is making us install Airwatch to continue using our personal phone with their network, which requires Encrypting it (Settings/Security/Encrypt Phone). Will this have any effect on me access data if I dirty flash Lineage 14.1 ROM updates after doing this?
I don't think it will, but I want to make sure before I take this plunge.
I don't think you will have any problems, because I believe the decryption stuff will still be there.
That said, AirWatch checks for custom ROMs, root, etc, and still threw up flags, even with magisk. I haven't checked it in awhile though, so that may have changed.
Karlinski said:
I don't think you will have any problems, because I believe the decryption stuff will still be there.
That said, AirWatch checks for custom ROMs, root, etc, and still threw up flags, even with magisk. I haven't checked it in awhile though, so that may have changed.
Click to expand...
Click to collapse
Yeah I'm aware of Airwatch's probing of all that. So far with Magisk 14, it's proceeding further than when I tried it before Magisk was installed. If it works then great, else I'm not going to sweat it and I'll just figure out an alternative means.
Thanks!
UPDATE: Please read the next post.
A while back, I rooted my v20 with magisk using this method and everything worked fine for a few months, except for a few issues that reflashing the system would fix. Last night, SystemUI kept crashing (the status bar and the buttons would disappear). After a while, the phone crashed, and then it completely refused to boot. It would very rarely get to the lock screen, but it usually crashes soon after I unlock it. I tried everything I know of that could fix it, such as restoring the boot partition and reflashing magisk, reflashing the system partition, and wiping the cache and dalvik/ART cache. I eventually gave up with this and just reset it through the wipe menu in TWRP. I was able to get the phone to work for about a day without any issues, and then the same thing started happening again. It would take a really long time to boot and the system would crash. I tried using that ~1 minute it gives me before crashing to enable core mode in magisk to prevent any modules from loading, but that didn't do anything. I am really confused as to why this would happen considering that I reset the boot and system partitions multiple times in this process, and eventually did a full reset. It should be like a brand new phone. I really don't know what could possibly be the issue. Any help would be greatly appreciated.
Update: It turns out that Magisk Core Only Mode did not properly apply because of yet another crash. I cleared my cache once more, which gave me enough time to properly apply it, and now my phone is staying on and not crashing. But this still is concerning to me. I was able to run Magisk modules perfectly fine in the past, including after the most recent Magisk zip update, so why is it that I can no longer run modules, and that this issue persists after a factory reset? It can't be an update, because, as I stated, I was able to run modules just fine for at least a week before these issues occurred. Please correct me if I'm wrong, but this makes absolutely no sense and I want to be able to run modules again. I even deleted the modules through TWRP but the only thing that seems to fix this issue is completely disabling all other features via Magisk Core Only Mode.
Update 2: A Magisk update came out recently and I tried updating to that to see if it would fix the issue. This only brought back the original crashes. I tried using the Magisk uninstaller zip (because I found that simply reflashing Magisk isn't enough, there are other files which magisk uses to store data.) After doing this and reflashing Magisk, it worked for a little bit, but, me being me and wanting busybox installed, I managed to bring back the crashes. After that, uninstalling and flashing magisk would work, but only until a reboot. I am at a complete loss. I am currently backing up my internal storage (manually since TWRP doesn't) and I will try a full /data format.
Ok, it has been a few days since I wrote the previous section but I decided not to post it because if the /data format worked, I didn't want to have bumped it for no reason. At first, it worked, and I decided to leave it like that without rebooting it for a few days or messing with Magisk, and my phone worked perfectly. I had to restart my phone because Google photos was acting up, and it started crashing again. I am genuinely confused. I completely formatted my phone and reflashed Magisk several times, and it is still crashing. I just reset my phone again because I attempted to just restore a stock boot backup from before I installed Magisk, which made my phone completely unbootable. I pulled the battery and found that it tried re-encrypting the phone (AFAIK, TWRP doesn't support encrypted data on the v20, which really sucks) so I had to wipe it and flash Magisk so it wouldn't re-encrypt it. I will try to do this again, but I don't want to not be able to restart my phone (which is so far the only thing that's working for me). This time, not even uninstalling and re-flashing Magisk worked this time, as it has all of my previous attempts. I had to completely reset it. Again. I really need this issue fixed. I probably already said this, but I would greatly appriciate any possible help I could get. I really want my phone back.
Ok I forgot to include some basic information about my phone.
Model number: LG-H910
Android version: 7.0
Android security patch level: April 1, 2017
Kernel version: 3.18.55
Build number: NRD90M
Software version: H91010m
According to Kernel Auditor:
Kernel: Linux version 3.18.55-Werewolf-2.0-Basilisk ([email protected]) (gcc version 6.3.1 20170430 (GCC) ) #1 SMP PREEMPT Sat Jun 24 00:56:07 CDT 2017
Bump/Update: This is a small one, but, despite not restarting my phone, Magisk is showing an error "Magisk is not installed". Root access also disappeared. I don't know how much longer I can keep it on without having to restart it due to random issues like these that usually fix themselves with a reboot. I would appreciate any help.
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
toastyp said:
Seems like your phone is all sorts of wacked out. I noticed from the specs your using the werewolf kernel. I had all sorts of performance issues as well as random reboots using that kernel. Since you're losing root and the system is overall unstable I recommend wiping clean and starting over. Wipe system, data, cache, and dalvik in twrp and flash the full stock 10r zip by runningnak3d. It will put you on the latest security patch with the newest firmware available. I recommend installing askerm2000 1.4 kernel as it is very stable and works well on the h910. Flash magisk last (latest 15.3 works great for me) and reboot. Hopefully will solve your problems. The 10r zip for the h910 plus askermk2000 kernel and magisk has served me well for a while now.
Click to expand...
Click to collapse
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
NullBite said:
Thank you. Before I do this, I have a few questions.
1. How do I disable force encrypt with Magisk? I remember when I flashed Magisk 14.0, that managed to disable force encrypt, but any other version of Magisk wouldn't do that when installing fresh (updates kept this setting). AFAIK TWRP is unusable on the v20 for things such as backups, file browser, etc because it isn't compatible with the encryption algorithm used by the v20. How would I turn off force encrypt with the latest Magisk zip
2. Should I do a full format data (where you have to actually type "yes" to confirm it) or just wipe those partitions using advanced wipe?
3. Will the askerm2000 kernel hide modified boot, unlocked bootloader, etc from safetynet just as Werewolf kernel did, and will it get rid of the static boot issue?
4. Will this increment ARB? If anything goes wrong, I want to be able to roll back.
5. If it was working perfectly fine before, what suddenly made everything come crashing down, even after multiple wipes? This is not as important as the other ones, I am just curious.
Sorry if these questions seem over excessive and/or obvious. Doing stuff like this tends to make me a bit nervous and I want to think of everything I can that might affect the outcome.
Click to expand...
Click to collapse
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
toastyp said:
Twrp can properly decrypt the v20. Twrp backup and restore works just fine for me. Never had an issue with this. You format data and then type yes. Wipes the data partition but this is only needed once. Decrypts the device and twrp can then do it's thing. Encryption problems stem from booting into system with a stock boot image that has force encryption enabled without flashing magisk or supersu. They modify the kernel to prevent the device from rencrypting. Latest magisk 15.3 has zero issues keeping the phone decrypted. The modified boot warning has nothing to do with the kernel. This is caused by the debug bootloader used to achieve root on the US carrier v20's. Nothing can be done to change that. ARB has not been incremented on the h910 so that isn't an issue currently. Potentially in the future, but not right now. The problems you're having could stem from a multitude of issues. Could be modifications you made, bad flashes, etc. If you're having issues with encryption and stuff sounds like magisk wasn't functioning properly at the end. I've been rooted since last January and haven't experienced anything like that before so I'm not sure
Click to expand...
Click to collapse
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
NullBite said:
Ok, I cannot possibly thank you enough for this. After this started happening, I seriously thought my phone was at the end of its life. If this were to happen, I wouldn't be able to get a new phone anytime soon. Not only did it fix the crashes (I only restarted it once, I'm not going to try to intentionally make it crash), It ALSO managed to fix my FM radio and (I think) the Google Assistant Voice Match unlock thing, both of which I never even thought I would be able to get back. Let's just hope that it stays this way. I have one last question. Would you say it's safe to download and install Magisk modules now?
Click to expand...
Click to collapse
Yes. I use a few modules myself without an issue. If you're unsure of the stability of a module, you can always take a nandroid backup in twrp prior to installation. If things are stable, and then you flash something and the phone freaks out, it's most definitely the mod you have flashed causing problems. Some modules make changes to the system partition that have the potential to problems. But I haven't had a module cause my device to bootloop or reencrypt. So I think you're good to go. Glad you're phone is up and running as it should. Very strange that it was in such a bad way, but crap happens. I have had zero issues with this setup (10r + 1.4 askermk kernel + magisk 15.3).
I have the stock firmware on the H990 version, I end up on the Crash LK screen error. I can access TWRP, how can I restore access to my device without losing data? Thanks.
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.
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.
I haven't followed development of the 6T since November so please forgive me if this has been answered 100 times.
The steps to flashing custom non-OOS ROM's is to; flash ROM/flash TWRP installer/reboot recovery/flash gapps/flash magisk
The weird issue for me is when I reboot recovery after flashing the ROM and TWRP when I go to install gapps all my files are encrypted. My way around this was to sideload gapps and magisk and everything booted up fine. When I go back to recovery after the first boot all the files are normal again.
This has happened both times I've flashed a ROM.
I'm sure this has an easy answer and it's most likely due to a step I didn't execute properly -- or at all. I did a lot of reading and making sure I understood the process before rooting my device but as far as flashing ROM's I was noticing a lot of conflicting info which I've never seen before on any other device. Anyway, other than this I haven't had any issue.
Thanks for any feedback.
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Deleted
ogkillergreen said:
Security issue. Best way around it is to either format data before flashing and/or remove your lockscreen security pin before flashing.
Click to expand...
Click to collapse
I never use any lock. Always just use Swype to unlock. I'm aware of the issue with using a lock though. I read that people had problems. I just haven't seen where any one brought up my exact issue. It doesn't seem to effect anything so I'm not stressing it too bad. Eventually I'll get around to troubleshooting it.
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
BreathingWounds said:
I've flashed almost every ROM for 6T till now and every time I flash a ROM I'm having exactly the same issue as you. I've also tried formatting data several times, but the issue with unreadable data in TWRP after flashing a ROM returns every single time. I've tried multiple combinations of flashing, wiping etc. and it's always the same. However, what I'm doing in such case is flashing gapps + magisk from USB-C pendrive, no need to sideload, just mount USB and flash files from that as usual. After doing that I can boot to ROM and the data is readable again. I just need to remember to have this pendrive close to me when I'm flashing a new ROM.
Click to expand...
Click to collapse
Thanks for the tip and info. I don't mind sideloading because it's fast and anytime I mess with my phone it's when I'm at my PC. I've been using adb for so many years it's my go-to whenever my phone is acting stupid.
The second time I flashed a ROM I didn't even worry about flashing gapps, just magisk. And I stacked them. So ROM, TWRP, Magisk. Then rebooted system. I actually prefer this anyway because then you boot straight to the launcher with no setup process. Then I go back and flash GAPPS. I actually have used this flashing process for years because I hate the setup after a first time boot.