Related
Hi,
I bought the Samsung Galaxy S5 and the fingerprint reader works reasonably well (as in it works, nothing in comparison to apple though, so don't buy it for the fingerprint reader ) for unlocking the screen...
However its a work requirement that my phone has full device encryption, as phones are regularly stolen where I travel.... it seems when I enable encryption I lose the ability to use the fingerprint reader to unlock the phone .... I bought this hoping that I could avoid having to type in my complex password just to unlock the screen, as I got so tired of doing that with my S2
Is there any mods to enable finger print reader screen unlock + full device encryption at boot time for the Galaxy S5 yet? ... I saw some references to pattern unlock / pin with device encryption... but I would think the fingerprint reader is different...
Thanks!
S5 Full disk encryption with fingerprint unlock
I also have this question. I believe on the Nexus 5 it at leasts lets you use face unlock with full device encryption. And I read on one article that you should be able to do this but i do not think the author actually tried this. I will say from my own personal experience that you can infact decrypt the device after encrypting it without doing a complete wipe of the device and you can restore the use of fingerprints to unlock your phone. It seems like for security minded people this would be a great feature but if it is unable to be used with full device encryption it seems a little pointless to me. Being forced to use a PIN or password to use encryption is a big pain point for android users who want some type of security.
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
androidpleb said:
Yes I can't believe that no one has really complained about this yet - but I guess encryption isn't' that important to people as I imagined
Click to expand...
Click to collapse
I am having the same pain, as I use my S5 for BYOD.
It makes no sense when you can use fingerprint to make payments with paypal but not unlocking the phone when it is encrypted.
Hope Samsung can enable this feature in next update.
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
sorphin said:
I'd like this too.. as well as, the iPhone has a cydia app (that a friend of mine showed me), that you can basically disable the power button from turning off the phone while it is fingerprint locked. That would definately be nice to have on the S5 (since it's done through an app). That would have stopped the person who stole my wife's S4 from turning it off when it was blasting the locator ring at them!
Click to expand...
Click to collapse
I can't believe that the fingerprint sensor can't be used if encryption is enabled whatsoever. I could understand the iPhone model, requiring a pin before a fingerprint can be used, but by disabling fingerprint lockscreen, boot unlock, and SD unlock, the fingerprint sensor is now wholly useless for convenience.
It's too trivial to extract data from an unencrypted Android. By not supporting encryption with a measure of covenieve, I don't see the point in including a fingerprint sensor whatsoever given the current software limitations.
Please, someone, figure out what sqlite/settings need to be changed so we can make decent use of our phones fingerprint sensor.
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Boot Loop
fabiokino said:
After some experiments, i found out a procedure to enable FDE and fingerprint lockscreen. Root is required (or at least I guess, I didn't try with a non-rooted system...).
These are the steps:
1) set up fingerprint lockscreen
2) with a root explorer, go to /data/system folder, and backup locksettings.db, locksettings.db-shm and locksettings.db-wal to sd card
3) set up password lockscreen
4) encrypt the device
5) when encryption is done, restore the backed-up files to /data/system: you should have fingerprint lockscreen again (no reboot needed, just turn the screen off, and magically the password should be vanished )
CAVEAT 1: with my system configuration, I wasn't able to encrypt the device directly: the encryption procedure started, but after reboot nothing happened, the device just booted normally. I don't know the exact reason, in some forums they suppose that it happens on kitkat when the device is rooted. I was able to bypass the problem only adding these steps to the procedure:
...
3b) with TWRP, backup the /system partition, and restore the stock non-rooted /system
4) encrypt the device
4b) restore the original rooted /system partition
...
I don't know if steps 3b) and 4b) are always necessary, let me know...
If you need these steps, don't worry if before restoring your custom /system partition the encryption password isn't recognized, just restore the partition and all will work fine
CAVEAT 2: once encrypted, I didn't find a way to unencrypt the device, because the unencrypt ion procedure starts, but after reboot the device is still encrypted, similar to what described in caveat 1. I tried to replace the /system partition with the stock one, but the encryption password was no longer recognized.
CAVEAT 3: the current TWRP (2.7.1) isn't able to mount S5 encrypted data partition, and restoring an image made with online nandroid backup doesn't seem to work either. So, if you want to make an image of your phone (and I suggest to do it ), do it before encryption
Click to expand...
Click to collapse
I get samsung boot loop using the above instructions
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
Hi guys! Did someone try this solution? I unfortunately have the same issue and unlock my device each time make me crazy!
Thanks in advance.
Same problem
I purchased a Galaxy S5 and I have the same problem, unfortunately I cannot root my phone due to security policies in my company. :crying:
I hope Samsung will solve the issue. :fingers-crossed:
Have anyone contacted to Samsung Support Center?
Pierreseoul said:
I get samsung boot loop using the above instructions
Click to expand...
Click to collapse
What is the consequence of boot loop if you are using stock boot loader? Odin mode required to recover? Something less drastic? What device model are you using?
I found a possible solution that involves deactivating SuperSU and running encryption from there. Still investigating. I am thinking that the solution from @fabiokino will work in this case too.
I'm curious about this aswell.
Doesn't anyone know a working solution?...
It is really frustrating the very least. I can't believe there isn't a way (or if there is, a guide) to do this (with or without root access).
I have also heard it is doable on the Note 4. See this post for example http://forum.xda-developers.com/showpost.php?p=57103664&postcount=7.
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
How?
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
healpowah said:
I just flashed the stock Lollipop ROM and guess what: It works!!
Samsung finally did it. No tweaking needed and it also works without root access.
Click to expand...
Click to collapse
Nice to see this, hope it will work on my Galaxy tab S too
Did you see this?
https://www.jethrocarr.com/2013/12/29/encrypting-disk-on-android-4/
GermanDoerksen said:
Can you explain how please? I'm on stock lollipop as well and cannot use fingerprint scanner with FDE. Wondering if there's a process to it?
Thanks!
Click to expand...
Click to collapse
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Joker87 said:
Unluckily the trick showed in the previous link only encrytps the main device and not the micro SD
Click to expand...
Click to collapse
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
GermanDoerksen said:
Well for me that really wouldn't be a problem. I don't have an SD card so I'm okay with just FDE. Thing is I really really don't want to root my phone... No particular reason other than every older android device I've done it on always ends up slow and buggy after a few months use until I reflash with stock ROM. I would like my phone to stay buttery smooth for once..
Click to expand...
Click to collapse
You could root then unroot it after you have encrypted it
Joker87 said:
You could root then unroot it after you have encrypted it
Click to expand...
Click to collapse
you're right... plus it's not really the "rooting" process that makes it slow, it's installing another ROM. Having a rooted phone doesn't necessarily have any performance impact... just opens up a few things for me. Interesting. Thanks! Unfortunately I've already encrypted so now I have to find that thread about how to decrypt lol.
Thanks!
Hello all,
Although not clearly encrypted upon receipt of the device from VZW, I located the setting and encrypted the device.
After the last security update from Google/VZW I noticed that the option to encrypt/decrypt device is no longer present, and after rebooting my phone, I am no longer prompted to enter my PIN at boot. Note that I did have the setting as discussed/shown here and here after receiving the device.
The explicit feature I'm speaking of is discussed in this review:
Samsung now supports the PIN to decrypt on boot feature. It must be enabled manually in the lock screen and security settings area under “protect encrypted data.” Also, the S7 and S7 edge are full-disk encrypted by default, and cannot be decrypted.
Click to expand...
Click to collapse
These two things lead me to believe that the "whole-disk" encryption on the device has been removed completely or... is it just the PIN on boot feature? What does it all mean? What is the world coming to?
Am I just paranoid/silly and just forgot where the option was? Or is there a vast global network of government organizations trying to get my cat pictures?
Thanks,
Matt
branded said:
Hello all,
Although not clearly encrypted upon receipt of the device from VZW, I located the setting and encrypted the device.
After the last security update from Google/VZW I noticed that the option to encrypt/decrypt device is no longer present, and after rebooting my phone, I am no longer prompted to enter my PIN at boot.
Matt
Click to expand...
Click to collapse
One thing I can tell you for sure...based on a diff Samsung device: would WOULD KNOW if it got decrypted somehow as it factory defaults the phone.
Could be just different behavior regarding the PIN or even a bug.
I've added my lockscreen pattern, but I'm not seeing an option for encrypting the phone anywhere in the settings. I've added the pattern to needed at startup, but again, not seeing anywhere to encrypt the phone, unless it's set that way as default and I'm missing it. Anyone know of a way to find out for sure what the encryption status is?
scottricketts said:
I've added my lockscreen pattern, but I'm not seeing an option for encrypting the phone anywhere in the settings. I've added the pattern to needed at startup, but again, not seeing anywhere to encrypt the phone, unless it's set that way as default and I'm missing it. Anyone know of a way to find out for sure what the encryption status is?
Click to expand...
Click to collapse
I'm fairly sure it's encrypted by default.
Make sure you encrypt your sd card.
Sent from my LG-H872 using Tapatalk
Saythis said:
I'm fairly sure it's encrypted by default.
Click to expand...
Click to collapse
It looks like it.
https://www.reddit.com/r/lgg6/comments/6a0tbb/encryption/
My US997 is not encrypted, I can boot into TWRP and see my files without typing in the PIN like I had to on my Nexus 6P.
No option in settings that I can find besides encrypting the SD Card.
Anyone get this figured out?
Does anyone have the option to encrypt their phone (not sd card)?
cory733 said:
Anyone get this figured out?
Does anyone have the option to encrypt their phone (not sd card)?
Click to expand...
Click to collapse
I just got a used/refurbished US997 the other day. From what I remember, it came with Android 7.0 and the first time I booted it up it asked me to create a pattern to start the phone (encrypt like our old 6Ps). Once setup it downloaded a major system update and restarted, and asked me for the pattern to start the phone. Once it booted up again it installed another major system update and when THAT rebooted it no longer asked for a pattern to start the phone.
I wonder if it is just the most recent version of 7.1.2 that removed the encryption? I'm pretty sure there is a way to unpack the boot images to see (I was doing this trying to revive my 6P bootloop). I too would like to encrypt my phone given that it doesn't seem to impact performance any more. Perhaps once we get Android 8.0 it will be brought back.
How do you like the G6 compared to the 6P? I'm still getting used to a few items but installing the Google Now Launcher really helped. I find the fingerprint scanner/power button combo to be really lacking (ergonomics and usability) compared to the 6P and I really miss the power button short cut to launch the camera.
Also, what's the point of TWRP? When I was trying to revive my 6P everyone kept mentioning it, but I don't quite understand why I should install that.
Thanks for the detailed response, I'll probably just leave it alone then until we get an update.
For TWRP, I installed it flash Magisk, and whatever else I might want to flash later. Always good to have an efs backup somewhere safe also. If you had a complete backup from twrp of your 6p, it may have helped you fix whatever you were having a problem with.
Compared to the 6p I love it because it fits in my pocket and has an sd card slot. The lack of mods/ dev support for this phone amazes me though.
After some more research, trying some more stuff, I came across some more info:
I turned off OEM unlocking in developer options then turned it back on. This message appears when enabling OEM unlocking: "Warning: device protection features will not work on this device while this setting is turned on."
Then I came across this thread about an S7 where someone mentions that if you enable OEM unlocking, you will lose access to Secure Startup:
https://forum.xda-developers.com/galaxy-s7/help/root-secure-startup-t3729184
Edit: looking through the fulmics thread, which i believe currently uses 7.0? There are posts in there about encryption/secure start not working either.
Can someone with a locked bootloader check to see if they have this setting? Should be settings - fingerprints and security - encryption / secure start.
cory733 said:
After some more research, trying some more stuff, I came across some more info:
I turned off OEM unlocking in developer options then turned it back on. This message appears when enabling OEM unlocking: "Warning: device protection features will not work on this device while this setting is turned on."
Then I came across this thread about an S7 where someone mentions that if you enable OEM unlocking, you will lose access to Secure Startup:
https://forum.xda-developers.com/galaxy-s7/help/root-secure-startup-t3729184
Edit: looking through the fulmics thread, which i believe currently uses 7.0? There are posts in there about encryption/secure start not working either.
Can someone with a locked bootloader check to see if they have this setting? Should be settings - fingerprints and security - encryption / secure start.
Click to expand...
Click to collapse
Ah, you may be onto something there. I did enable unlocking in the developer options, but if I remember correctly I need to perform an ABD or Fastboot command to actually unlock it, right?
u.of.ipod said:
Ah, you may be onto something there. I did enable unlocking in the developer options, but if I remember correctly I need to perform an ABD or Fastboot command to actually unlock it, right?
Click to expand...
Click to collapse
Yes, the fastboot command is what unlocks it. I think the oem unlock setting just allows you to be able to unlock it with fastboot.
cory733 said:
Edit: looking through the fulmics thread, which i believe currently uses 7.0? There are posts in there about encryption/secure start not working either.
Can someone with a locked bootloader check to see if they have this setting? Should be settings - fingerprints and security - encryption / secure start.
Click to expand...
Click to collapse
Yes I have and use that option on my stock ROM, it's available with unlocked bootloader as well. I understand that on stock the G6 is encrypted by default.
TWRP cannot mount the encrypted /data or at least couldn't when I last tried. So when you flash TWRP and try to install a custom ROM that currently works only after formatting /data (where you have to confirm with "yes") and that kills the encryption.
The custom ROMs set Force Encryption = off so that the bootloader does not complain.
The combination of an unlocked bootloader and unencrypted /data is a no go for me, because anyone who knows how to boot into recovery can simply use the TWRP file manager to get/reset fingerprint and password data and can turn off the lock screen. Everything is plain open, I've tried.
I was not able to re-enable encryption on either Fulmics or LOS. Fulmics shows the Secure Boot option but on the next start the keyboard to enter the password crashes (loop) and never comes up so I got stuck and had to reinstall. On LOS official the option to encrypt is available but not functional (yet, they say).
So I'm back on stock. My main interest with alternative ROMs is to get security updates where LG fails badly but I hope it gets better once Oreo is out given that the G6 has been registered for Google's business programme. I'd love to use LOS once it encrypts.
It's a bit sad because e.g. LOS encrypts a Samsung I have just fine but there you go - I'm not bright enough to improve LOS for the G6. The Fulmics guys are simply not interested in encryption, never got a reply when I raised the keyboard issue even though I sponsored quite a sum. I assume Fulmics cannot re-enable encryption, because it's based on stock. Stock (contrary to LOS) has no dedicated encryption option for /data and does not need it normally because it comes encrypted. Fulmics install has to format not just wipe the partition so encryption gone and no way back.
I got encryption back by returning to stock using LG Bridge.
Thanks for that reply, that clears things up a lot.
So now that you're on stock, you didn't flash TWRP? You mentioned that formatting data is what kills the encryption, but do we need to format data to flash magisk? Could I flash stock, unlock, flash twrp, leave data encrypted, then flash magisk? Then just install the app manually after booting?
I only need twrp for efs backup, which I now have, and to install magisk.
Rooted/encrypted stock is all I'm looking to achieve right now.
Moldeb said:
Yes I have and use that option on my stock ROM, it's available with unlocked bootloader as well. I understand that on stock the G6 is encrypted by default.
TWRP cannot mount the encrypted /data or at least couldn't when I last tried. So when you flash TWRP and try to install a custom ROM that currently works only after formatting /data (where you have to confirm with "yes") and that kills the encryption.
The custom ROMs set Force Encryption = off so that the bootloader does not complain.
The combination of an unlocked bootloader and unencrypted /data is a no go for me, because anyone who knows how to boot into recovery can simply use the TWRP file manager to get/reset fingerprint and password data and can turn off the lock screen. Everything is plain open, I've tried.
I was not able to re-enable encryption on either Fulmics or LOS. Fulmics shows the Secure Boot option but on the next start the keyboard to enter the password crashes (loop) and never comes up so I got stuck and had to reinstall. On LOS official the option to encrypt is available but not functional (yet, they say).
So I'm back on stock. My main interest with alternative ROMs is to get security updates where LG fails badly but I hope it gets better once Oreo is out given that the G6 has been registered for Google's business programme. I'd love to use LOS once it encrypts.
It's a bit sad because e.g. LOS encrypts a Samsung I have just fine but there you go - I'm not bright enough to improve LOS for the G6. The Fulmics guys are simply not interested in encryption, never got a reply when I raised the keyboard issue even though I sponsored quite a sum. I assume Fulmics cannot re-enable encryption, because it's based on stock. Stock (contrary to LOS) has no dedicated encryption option for /data and does not need it normally because it comes encrypted. Fulmics install has to format not just wipe the partition so encryption gone and no way back.
I got encryption back by returning to stock using LG Bridge.
Click to expand...
Click to collapse
I have my LG G2 encrypted with LineageOS and TWRP can decrypt the data, in fact it asks for password just after entering recovery.
G2? Why should that be relevant for G6? Totally different hardware...
---------- Post added at 07:25 AM ---------- Previous post was at 07:11 AM ----------
cory733 said:
Thanks for that reply, that clears things up a lot.
So now that you're on stock, you didn't flash TWRP? You mentioned that formatting data is what kills the encryption, but do we need to format data to flash magisk? Could I flash stock, unlock, flash twrp, leave data encrypted, then flash magisk? Then just install the app manually after booting?
I only need twrp for efs backup, which I now have, and to install magisk
Click to expand...
Click to collapse
I don't have TWRP right now, used to have it of course. I've not tried to just root but you can try using Zefie's unofficial version (the official can cause corruption). You'll see whether TWRP can mount the required volumes rw. If TWRP cannot mount or asks a password and yours doesn't work, you have run into LG's ex works encryption...
Moldeb said:
G2? Why should that be relevant for G6? Totally different hardware...
Click to expand...
Click to collapse
Maybe you are running a different version of TWRP or unofficial build?
On my LG G2 D802 I've installed twrp-3.2.1-0-d802-bump-blastagator-signed.zip and it prompts for decrypting password. Try this same version in case it helps on your LG G6. It should look something like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I know what it looks like, will certainly not install any G2 (D802) software on a G6 (H870) and don't recommend anyone does unless they want to brick their G6.
Moldeb said:
I know what it looks like, will certainly not install any G2 (D802) software on a G6 (H870) and don't recommend anyone does unless they want to brick their G6.
Click to expand...
Click to collapse
Look for the version for your G6, I'M NOT TELLING YOU TO USE THE G2 VERSION OF COURSE YOU SHOULDN'T DO THAT WHERE DO I SAY SUCH THING.
All the time basically. The positive experience on your G2 is as irrelevant as on my Samsung where encryption also works. Not on the G6 and I've tried the official TWRP as well as Zefie's. The problem is not that the password dialogue is missing but that your password will not work because LG seems to use something else for stock encryption.
Which is why all ROMs ask to format and not just wipe /data.
Moldeb said:
All the time basically. The positive experience on your G2 is as irrelevant as on my Samsung where encryption also works. Not on the G6 and I've tried the official TWRP as well as Zefie's. The problem is not that the password dialogue is missing but that your password will not work because LG seems to use something else for stock encryption.
Which is why all ROMs ask to format and not just wipe /data.
Click to expand...
Click to collapse
I think I have the same problem. So basically, it's not possible to use a custom ROM with encryption? I
Hi everyone,
I have a LG G6 (H870DS/SEA) and it's a great device. Even better with Oreo, now the device doesn't have the problems we've had on Nougat.
Let me tell a quick story about security and this device. I've upgraded officially (using LG Bridge) to Oreo one month ago, I think. Everything worked at the time: my bank account, Pokémon GO (which uses SafetyNet) and every single application that depends on device certifications.
Recently, after seeing so many posts about the new ThinQ features, the bright camera mode and the rename, I decided to flash the CIS firmware using LGUP and UPPERCUT to make the G6 detectable by LGUP. No problems, SafetyNet was indeed working at the time (attested using Pokémon GO).
After some time w/out using the device, I decided to go back and use it. Yesterday, I tried to open my bank application and it failed several times with the same error code. I thought that it was some kinda of problem with my account, but then I realized that SafetyNet problems actually does the same things when the CTS profile mismatchs or something else prevents SafetyNet to be attested.
With that in mind, I decided to install a "SafetyNet checker" and see what was actually going on. Boom. SafetyNet failing multiple times. It says my device doesn't support SafetyNet (which is a lie, IMO). Initially, my thoughts were that, upon flashing the CIS firmware, something broke and SafetyNet end up broke. Tried to flash the last SEA firmware, no luck. Tried to revert back to the original SEA Oreo firmware (which I flashed the CIS firmware on top), no luck at all.
Apart from my bank application, Pokémon GO and any application that eventually uses SafetyNet for security checking, everything else works. I just don't know what happened with this, as I don't know if my device is still "official" or a red bright light was powered during the flash process (which, IMHO, I doubt, otherwise I'd have seen this on the start).
At this point, I think I'm stuck into this unless a bootloader unlock comes along sometime (this is not impossible, but let's keep hoping for now) and Magisk + its modules are activated in order to hide SafetyNet approval.
TL;DR:
- My phone is failing on every SafetyNet test and I just don't know why;
- It runs official firmware. However, it went through LGUP flashes 2-3 times now;
- There are no root or bootloader unlock methods to this specific model, so there were no unofficial modifications whatsoever;
- The problem started recently, as the SafetyNet depended applications seemed to work after the first flash;
- The first flash actually changed the region (SEA>CIS), so I just don't know if this is the real problem or this is just an unfortunate coincidence;
- I just reverted the phone to its normal region (SEA), and it keeps failing;
- According to multiple SafetyNet checkers, it just says it's uncompatible and tells something about an empty payload. Neither the CTS profile is available;
- Just in case, if someone wonders about the versions I've used until now, the order of the flashing process is:
SEA Nougat -> SEA Oreo (LG Bridge) -> CIS Oreo (LGUP+UPPERCUT) -> SEA Oreo (20C/LGUP+UPPERCUT) -> SEA Oreo (20A/LGUP+UPPERCUT)
If this problem is also happening with someone, or happened to someone else and eventually had a fix, please show the way. If you had the problem, please answer the questions below:
- Have you ever used LGUP with this device? If yes, which firmware did you flash?
- There was a region/carrier change? (eg.: SEA -> CIS, CIS -> EUR, TIM BRAZIL -> BRA and so on)
- SafetyNet dependents were working after the flash?
- Did you wipe your device after the flash? (if you've answered "yes" to the first question).
Thanks in advance.
Mr. I.
(PS: this is NOT a thread to ask for a bootloader unlock. Please don't answer this just to ask for a solution to this. Thanks!)
Hello,
I recently went through the ROOT process for H872 (T-Mobile version) and was able to install custom ROMs (PixelExperience_Plus_h872-10.0-20200326-2210-UNOFFICIAL & Havoc-OS-v3.7-20200711-h872-Official).
Every time I try to "Encrypt" the phone, phone asks for pin, restarts, shows android logo, reboots again and then gets stuck in bootloop (up to LG G6 ThinQ logo).
Only way to recover from this state is to boot into TWRP to format the data; and reflash everything.
Bootloader is unlocked.
Using TWRP 3.2.3 Nebula_Alph_20180813 (one from the root instruction).
Please let me know if there is a way to to enable encryption.
Thanks!
Unfortunately force encryption won't work in Custom ROMs. That's why I am on stock
SkylineDiT said:
Unfortunately force encryption won't work in Custom ROMs. That's why I am on stock
Click to expand...
Click to collapse
Thanks for the reply.
Yes, looks like you are correct.
Wonder if there is a ROM with default encryption.
tejtank said:
Thanks for the reply.
Yes, looks like you are correct.
Wonder if there is a ROM with default encryption.
Click to expand...
Click to collapse
Maybe Fulmics lol, But I dont know if there is version for H872. And Fulmics is outdated. You can try to debloat Stock ROM. Put Nova or other launcher
SkylineDiT said:
Maybe Fulmics lol, But I dont know if there is version for H872. And Fulmics is outdated. You can try to debloat Stock ROM. Put Nova or other launcher
Click to expand...
Click to collapse
Thanks for response.
Anyway to hide or bypass the encryption status ?
Stock Image = Encryption works but outdated security patch
Custom ROM = Encryption doesn't work but updated security patch
Not sure which is better... both have some risk
Encryption helps when you lost your phone, without passcode you cant access data
New security patch - helps in app or ir OS security, it harder to hack or to use holes in software to get access to various data when phone is use.
SkylineDiT said:
Encryption helps when you lost your phone, without passcode you cant access data
New security patch - helps in app or ir OS security, it harder to hack or to use holes in software to get access to various data when phone is use.
Click to expand...
Click to collapse
So in your opinion, encryption is priority over security patch?
tejtank said:
So in your opinion, encryption is priority over security patch?
Click to expand...
Click to collapse
For me encryption is priority, because I have sensitive data on a phone: banking app, email client and so on