Database Users

How to decrypt the Axon 7?

OK so this is totally self inflicted. At some point I was dinking around in the settings and the device asked me if I wanted to set a pin at startup. I went along with it and did that thinking it was a good idea. What it seems to have done (besides the startup pin) is encrypted the phone. Now technically everything works I can just enter my pin to boot to ROM or TWRP. But I want to remove the encryption and for the life of me I cannot find how to do that.
Any help would be GREATLY appreciated.
Here are notes on my situation:
-yes i searched the internets and XDA and mostly found stuff about the Nexus and OnePlus devices
-under security settings it just says "encrypted" there is no option to decrypt
-i have tried wiping and even formatting to different formats on data and system partitions
-tried different roms as well
-this is a Axon 7 U device
-running TWRP 3.1.1-0
-ROMs RR and Dark Rom
-obviously boot loader unlocked
Thank You

DarkQuark said:
OK so this is totally self inflicted. At some point I was dinking around in the settings and the device asked me if I wanted to set a pin at startup. I went along with it and did that thinking it was a good idea. What it seems to have done (besides the startup pin) is encrypted the phone. Now technically everything works I can just enter my pin to boot to ROM or TWRP. But I want to remove the encryption and for the life of me I cannot find how to do that.
Any help would be GREATLY appreciated.
Here are notes on my situation:
-yes i searched the internets and XDA and mostly found stuff about the Nexus and OnePlus devices
-under security settings it just says "encrypted" there is no option to decrypt
-i have tried wiping and even formatting to different formats on data and system partitions
-tried different roms as well
-this is a Axon 7 U device
-running TWRP 3.1.1-0
-ROMs RR and Dark Rom
-obviously boot loader unlocked
Thank You
Click to expand...
Click to collapse
Remove your PIN and then add it back but this time when it asks you if you want the startup pin choose no thanks.
Startup pin IS encryption.

bkores said:
Remove your PIN and then add it back but this time when it asks you if you want the startup pin choose no thanks.
Startup pin IS encryption.
Click to expand...
Click to collapse
I had tried that earlier and it did not work. What did work was doing doing a format data in twrp. I think mine was just stuck.

DarkQuark said:
I had tried that earlier and it did not work. What did work was doing doing a format data in twrp. I think mine was just stuck.
Click to expand...
Click to collapse
i believe that's the only way to decrypt the phone. You can have your phone encrypted without jt asking for a pin or pattern and startup, and it happens every damn time you forget to flash supersu or magisk on first boot. If you flash another ROM later you'll have to format data, or it will fail if it is encrypted.
If your phone has TWRP I suggest that you go to it and format data, then install supersu/magisk via sideload or an sd card or otg without rebooting.

Weird Issue when Flashing ROM's

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.

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

Redmi Note 7 with LineageOS bootloop it self out of existence

Hi, first thing I'd like to say is that I used phones with other OS since 2015, first one was Cyanogenmod on HTC ONE (M7), loved the experience so when the time for new phone came I had no doubt that my next phone need to be the one that utilize LineageOS. For the three last years I used Lenovo P2 with LineageOS on it. I'm responsible for OS changes on all my phones and untill recently I had no issues with custom roms.
I am still boggled what happened. I installed LineageOS 17.1 on Redmi Note 7, all according to the LineageOS installation guide, and everything worked just perfectly.
Used redmi for 2 weeks but I had a chance to get on the cheap Asus Zenfone 6, so I grabbed the opportunity and use now Zenfone 6 with LineageOS.
The problem is I left 80% charge on Redmi note 7, shut it down and placed it comfortably back in a box for a week. After 7 days I tryed to boot the phone to reset it and give it as a gift but after redmi logo phone go black.
I could open Lineage recovery so I tryed to recover LineageOS, but result was the same, black screen after redmi logo no matter how long I wait.
So I tryed to reinstall LineageOS according to the guide, same result as above.
I though maybe there is something wrong with LineageRecovery so I changed to TWRP, went trough the installation of fresh batch of LineageOS from site this time using TWRP and had the same result phone dead after redmi logo.
Then I tryed to install MIU from xiaomi, everything went according to the manual but result was the same as mentioned above, well except for the part where I did a blunder and now the phone is locked back again, but still die after redmi logo. Oryginal Xiaomi Recovery don't help either.
Did anyone else expierience something like that?
And please correct me if I'm wrong but I think it must be a hardware issue not the software issue, right?

Arkilius said:
... And please correct me if I'm wrong but I think it must be a hardware issue not the software issue, right?
Click to expand...
Click to collapse
Did you format (not just wipe) the data partition? Try formatting the data partition (or try flashing a fastboot MIUI 11 Pie ROM with the Mi Flash tool).

DarthJabba9 said:
Did you format (not just wipe) the data partition? Try formatting the data partition (or try flashing a fastboot MIUI 11 Pie ROM with the Mi Flash tool).
Click to expand...
Click to collapse
I did format data properly, system and cache partition as it is one of the steps in LineageOS official instalation guide, before every system reinstall. I even tryed after moving to TWRP changing partition format from f2fs to ext4 but nothing helped.
Now phone is oemlocked and without opening it I can't do anything, just were wondering if anyone else had LineageOS dying on them out of nothing, even if it worked for week or two perfectly.

Arkilius said:
I did format data properly, system and cache partition as it is one of the steps in LineageOS official instalation guide, before every system reinstall. I even tryed after moving to TWRP changing partition format from f2fs to ext4 but nothing helped.
Now phone is oemlocked and without opening it I can't do anything, just were wondering if anyone else had LineageOS dying on them out of nothing, even if it worked for week or two perfectly.
Click to expand...
Click to collapse
Please be aware that Format data is different thing to Wipe data

RaizenrG said:
Please be aware that Format data is different thing to Wipe data
Click to expand...
Click to collapse
"Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one)."
Factory Reset, then Format data / factory reset are 2 separate steps not one.
Did step by step installation of LineageOS from Official LineageOS instalation guide for Redmi 7 Note.
Later on TWRP I did almost every format or wipe there is including repairing or changing partition format, nothing helped.
Still be nice to know if anyone had the same experiance of working LineageOS dissapearing from device after phone being off for full week?

Wrong pin issue

Hello,
last week i decided to upgrade to A11 rom (PE+). Before i ran PE+ A10 for months without problems.
I upgraded my ofox to latest 11.1 stabile. Then Format data, wipe etc.
Now whenever i installed a rom, after a short time when rebooting system my pin isnt recognized anymore from screen lock. Theres always this "wrong pin" warning. So i cannot access my phone.
Ofox cant decrypt seither, because oft wrong pin...
Since then i Tried many different Roms (A11 and A10) and even different recoverys (twrp, los, older ofox) and firmwares.
I also reverted back to my old PE+ A10...and now even there the bug appears!
I also tried deleting all files with "lock" in it under data/system...but that leads to neverending boot-time...
It is so annoying..i dont know now i can get my phone back to function properly...
Maybe anyone has a clue?