Database Info

Encryption not asking for unlock on boot?

Hey guys,
A few days ago I encrypted my device running the latest Exodus 5.1 with standard kernel. The first few boot ups I had to draw a pattern for boot (in TWRP as well). Now, after a week or so, it doesn't ask me for my pattern anymore. Not on normal system boot, neither in TWRP. But in settings it still tells me encryption is enabled.
Wth? What am I doing wrong?
Cheers

Settings -> lockscreen -> screen lock -> tap on pin / password / pattern (whatever you have set up) -> next screen you can choose if pin/password/pattern should be prompted for at device boot.

Oh, I see. Stupid me. Actually it's good that this is disabled because TWRP unfortunately does not support my 4x4 pattern (any workarounds got this btw?).
But with this option disabled, is the encryption still useful? Probably not right? So if someone steals my shutdown device he can simply access data through TWRP or booting it up, right? Encryption would be useless in this case?

Twrp does support pattern unlock for decrypt since version 2.8.6.0. If your pattern is to swipe the first row from left to right, this would be password "1 2 3" (just like you are swiping over a dialpad).
If you want to secure your data, then you must use a pin/password/pattern lock. If you don't use it, there is no real benefit using encryption.

Yes, TWRP supports 3x3 patterns, but not my 4x4 pattern. So is there any possibility unlocking your pattern via code then? Would it be like this then:
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
And where do I type the code then?
I use a 4x4 pattern lock. I just don't use the option that it has to be entered before boot (after unlocking the SIM card you have to unlock via pattern).

Sorry I misread. Twrp still can only decrypt 3x3 patterns. If your pin/password/pattern is not prompted for at device boot, someone could still access your data through twrp (and e.g. copy it to usb-otg).

Okay thanks. Then I'll hope TWRP is going to be able to decrypt 4x4 soon, so I can enable the boot decrypt. I don't want to go back to 3x3 neither get locked out of my system if I need TWRP to restore, update or whatever.

Samsung Flow: Failed Registering Fingerprint ROOTED

Hi all!
I am trying to get Samsung Flow to work with my Windows 10 Pro laptop but I keep on getting stuck at the Failed to register fingerprints part and I can't seem to get passed that screen no matter what (registered) fingers I use.
Could it be because I'm Rooted and using a custom ROM + kernel?
Thank you!

I am having the same issue on rooted a5 2017
Pls help!

xxxrichievxxx said:
Hi all!
I am trying to get Samsung Flow to work with my Windows 10 Pro laptop but I keep on getting stuck at the Failed to register fingerprints part and I can't seem to get passed that screen no matter what (registered) fingers I use.
Could it be because I'm Rooted and using a custom ROM + kernel?
Thank you!
Click to expand...
Click to collapse
satnavpt said:
I am having the same issue on rooted a5 2017
Pls help!
Click to expand...
Click to collapse
Are you on the Creators Update? I believe I read you need to be on it for it to work or that might have been to sync between your phone and PC. Could be Know is tripped and it needs a secure login to work.

i'm on creators update (build 16237) and use a NON rooted s8+.
i get the same error, so there must be something else wrong!

A. For Windows Pro > enable secondary authentication
1. Select search box on the Windows task bar
2. Enter "gpedit.msc" and press enter key
3. Go to the "Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Microsoft Secondary Authentication Factor -> Allow Companion device for secondary authentication"
4. Double-click the "Allow Companion device for secondary authentication"
5. Select "Enabled"
6..Select search box on the Windows task bar.
7. Enter “gpupdate /force” and press enter key
B.The phone return an authentication error code.(my phone was rooted and registered the fingerprint after reset to defaults)

qwess said:
A. For Windows Pro > enable secondary authentication
1. Select search box on the Windows task bar
2. Enter "gpedit.msc" and press enter key
3. Go to the "Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Microsoft Secondary Authentication Factor -> Allow Companion device for secondary authentication"
4. Double-click the "Allow Companion device for secondary authentication"
5. Select "Enabled"
B.The phone return an authentication error code.(my phone was rooted and registered the fingerprint after reset to defaults)
Click to expand...
Click to collapse
I'm having the same problem on my g935FD (Galaxy S7 Edge Duos, exynos) I walked through your steps to enable secondary authentication but still got the same error. I also have rooted and installed a custom rom. Do I need to restart my phone/computer?
I'm not sure what the second part of your message means. Do you have to reset your phone?

I tested with two phones(S6 Edge and Note 5), both with root, the registration issue on both, fingerprint scan fail in Windows side.
After I reset one to factory settings (only wipe cache partition does not work) with unroot complete (My Note 5), the registration of the fingerprint in PC worked very well.
Debug log can be sent to the developer:
[How to collect Samsung Flow logs]
1. Download "SamsungFlowLogCollector" , unzip
2. Launch "SamsungFlowLogCollector.exe"
3. Check the "Turn on/off logging" check box.
4. When "The reboot is required to take effect." popup show, select the "Yes" button.
5. Restart your device.
6. Reproduce the problem steps. Launch Samsung Flow. Try to register device.
7. Launch "SamsungFlowLogCollector.exe" again.
8. Select the "Collect Logs" button.
9. Uncheck the "Turn on/off logging" check box.
10. Share the created file(.sfel) to developer..

I'm on a galaxy s6 (7.0) rooted with magisk. I also get the same error .I tried to use magisk hide but this does not seem to matter.

register fingerprint fails with rooted phones!
For rooted devices the only way to register is:
1.Delete fingerprints saved on mobile device.
FLOW apps > Try to register device (without fingerprint)
2.After device has successfully registered with CDF (companion device framework), set it back a fingerprint to unlock phone.
Logging into windows is possible if the mobile device is unlocked- with fingerprint.
Tested with:
Windows : Samsung Flow app v.2.0.79.0, Driver v.2.0.1.6
Android: Samsung Flow v.2.0.41
sorry 4my bad english
---------- Post added at 11:22 PM ---------- Previous post was at 10:57 PM ----------
saluja04 said:
Do I need to restart my phone/computer?
Click to expand...
Click to collapse
No need for restart PC, just update group policy:
Select search box on the Windows task bar.
Enter “gpupdate /force” and press enter key
saluja04 said:
Do you have to reset your phone?
Click to expand...
Click to collapse
yes and unrooted.

qwess said:
register fingerprint fails with rooted phones!
For rooted devices the only way to register is:.....
Click to expand...
Click to collapse
thanks for sharing, i'm able to connect without fingerprints. added fingerprints back and so far, no issue.

just delete old pin code ,and re-create a pin

XDACXW said:
just delete old pin code ,and re-create a pin
Click to expand...
Click to collapse
Thanks alot man! I have struggled with this for a month or so! Such an easy thing. Thanks!!

i have a rooted Samsung galaxy s8+ and i get an error saying samsung flow doesnt work on rooted devices, Is there any way to bypass that?

enable camera 2 api on redmi note 5 pro?

I there any trick to enable camera 2 api without unlocking bootloader and root ??

solanki zeel said:
I there any trick to enable camera 2 api without unlocking bootloader and root ??
Click to expand...
Click to collapse
No,you have to unlock bootloader.

There is no way to do this without unlocking the bootloader first.
You do not need root(certainly not on LineageOS), it is enough to go to twrp > mount > check system, then advanced > terminal and
Code:
echo "persist.camera.HAL3.enabled=1" >> /system/build.prop
And that is that.
Also, I recommend you to backup "build.prop".
I am not responsible for anything you might destroy by this. Please do your research before copying any code.

Secure boot still enabled even after being disabled in the UEFI settings

Hi,
I would like to install a live Kali with persistence on the Surface pro4 internal sdc.
So I've installed ReFind on the system EFI as mentioned in this article:
ceres-c.it/booting-kali-surface
Then I have disabled all the security options of the UEFI bios (no certificate, no TPM), and when I boot on from the internal sdc, I got something like "refind secure boot failure!"
From my understanding (and reading) this should not occur when security options of the UEFI Bios have been disabled.
Did some of you experienced this kind of trouble?
Anyway, advise are welcomed
Regards

How To Guide Samsung S22 Ultra (Exynos) | Step-By-Step Guide | OEM BL unlock | TWRP system r/w

Hi.
Had the pleasure of voiding the warranty of my new Samsung S22 Ultra SM-908B/DS 512GB EUX today. Device is on the currently latest firmware, Android 13, SM-S908B_EUX_S908BXXU2BVL1_fac.
Below, I just document my experience so it may help someone as it was a bit of a tedious trial n error and a bunch of searching for info. ALL THANKS go to the respective developers and those who've been testing it out and posting about it. I've merely collected some of the (hopefully) relevant info.
Your warranty will be void. Don't do any of this unless you know what you're doing. Make sure you have backups. Also something about end of the world.
1) NO DEVICE SERVICES
- Freshly factory reset device.
- No "OEM unlocking" option under Developer Options.
- No "Device Services - Enabled" under "Settings - About phone - Status information".
- Download Mode shows "KG STATE : Prenormal" , "FRP LOCK: OFF" , and "OEM LOCK: ON(L)".
2) OEM UNLOCKING
- As described by Doghan13
- From factory reset, boot normally, without SIM, don't add any accounts, just enable WiFi.
- After the install wizard, go to "Settings - Date and time", set it 8 days earlier, deactivate "Automatic date and time" and "Automatic time zone".
- Under "Settings - Software update" disable "Auto download over WiFi". Check for updates (just check, don't install anything).
- Reboot
- Under "Settings -Date and time", check for updates again (just check, don't install anything).
- Enable "Developer Options", you should now see "OEM unlocking".
- This worked for me, if it doesn't work for you then you either have some restrictions (like "Device Services" enabled) or the wrong region model (like US Snapdragon).
3) UNLOCK BOOTLOADER
- Boot into "Download Mode" status had changed to "KG STATE : Checking" , "FRP LOCK: OFF" , and "OEM LOCK: ON(U)".
- Turn off and then boot again into "Download Mode" but this time, on the first screen long-press "Volume up" instead of the regular short-press "Volume up".
- On the next screen "Unlock Bootloader ?" just short-press "Volume up" [this is followed by factory reset / "Erase", your data will be gone!]
- Phone will reboot into the OS after a little bit. You could go through the steps under 2) and check if "OEM unlocking" is enabled...
- But a quicker way is to reboot into "Download Mode" which in my case then read "KG STATE : Checking" , "FRP LOCK: OFF" , and "OEM LOCK: OFF(U)".
4) VBMETA & TWRP
- Still in "Download Mode" I flashed the latest firmware via Odin3_v3.14.4 (optional). Flashed regular BL, AP, CP, CSC (not CSC_HOME).
- Let phone boot into system. No need to setup, reboot back into "Download Mode"
- Flash at the same time: "vbmeta_disabled_R.tar" via tab "USERDATA" [ by afaneh92 ] and "twrp-3.7.0_12-1_afaneh92-b0s.tar" via tab "AP" [ by afaneh92 ], "Auto Reboot" unticked.
Now, here come some steps that I am a little vague on (probably a few things redundant), feedback appreciated !!!
5) MULTIDISABLER & LP_RW_TOOL
- Reboot into the new TWRP Recovery
- Go to Advanced > Terminal, type: multidisabler. Should see "finished"
- IF error, type: multidisabler again. Should see "finished".
Flash custom kernel and magisk apk in twrp.
- "Advanced Wipe" everything (Dalvik/Art Cache, Metadata, Data, Internal Storage, Cache)
- Go back to "Wipe" > "Format Data" > type "yes".
- Reboot to recovery.
- Reboot back into Recovery, flash "afaneh92_lp_rw_tool_v0.4.zip"
- "Advanced Wipe" everything (Dalvik/Art Cache, Metadata, Data, Internal Storage, Cache)
- Go back to "Wipe" > "Format Data" > type "yes".
- Reboot to recovery.
6) UP_PARAM, KERNEL, MAGISK
- Boot into "Download Mode", flashed "up_param.tar" via tab "AP" [ post by gav83collins ], "Auto Reboot" unticked (or not).
- Back into "Recovery" > Flash custom kernel & magisk
- waipio-gki_kernel_5.10.81-afaneh92-gd8d6af751972_2022_11_08.zip
- OR b0s_kernel_5.10.66-afaneh92-g5f280760558f_2022_11_12.zip [ymmv]
- Wipe "Dalvik/Art Cache, Metadata, Cache"
Reboot and done. Go through setup wizard etc. "Internal storage" should be accessible from within the OS and from within TWRP.
Next: Finishing Magisk install from within the OS, with things like Universal SafetyNet Fix (Zygisk), AFWall, XPrivacyLua (Pro), Zygisk-LSPosed, Shamiko, CloudflareDND4Magisk, a very extensive (manual) debloat, etc etc ymmv.
That's pretty much it. Again, thanks to all these amazing devs and community. Feedback much appreciated.
k

Interesting, I have no oem unlock option and when I check status information I have 'Device Services - Enabled'.
You're saying this is a lock done by Samsung and that only they can unlock this and reveal the oem unlock option?

DanielM1418 said:
Interesting, I have no oem unlock option and when I check status information I have 'Device Services - Enabled'.
You're saying this is a lock done by Samsung and that only they can unlock this and reveal the oem unlock option?
Click to expand...
Click to collapse
I am by no means sure about that. But I have previously come across another device with "Device Services - Enabled" that was purchased directly from Samsung. The device had a history of trade-in of an old device, and that "Device Services - Enabled" never went away even long after the old device was sent in. Samsung support was unwilling to help for "safety and security" reasons. >>rooting bad<< .. Was unable to OEM / bootloader unlock as described above. Pretty good chance this is related to some MDM / KnoxGuard magic by Samsung.
For example:
- https://image-us.samsung.com/Samsun...devices/SBS-TAILOREDFLYER-JUN18T_Final_2x.pdf
- Look into com.samsung.android.kgclient and knoxguard.apk
- https://forum.xda-developers.com/t/com-samsung-android-kgclient-malware.4123033/
- https://docs.vmware.com/en/VMware-W...e_Enrollment/GUID-AWT-KNOXBULK-PREPARING.html
In contrast, my own device was paid-for outright, no trade-in, no financing etc.

kaefers said:
I am by no means sure about that. But I have previously come across another device with "Device Services - Enabled" that was purchased directly from Samsung. The device had a history of trade-in of an old device, and that "Device Services - Enabled" never went away even long after the old device was sent in. Samsung support was unwilling to help for "safety and security" reasons. >>rooting bad<< .. Was unable to OEM / bootloader unlock as described above. Pretty good chance this is related to some MDM / KnoxGuard magic by Samsung.
For example:
- https://image-us.samsung.com/Samsun...devices/SBS-TAILOREDFLYER-JUN18T_Final_2x.pdf
- Look into com.samsung.android.kgclient
- https://forum.xda-developers.com/t/com-samsung-android-kgclient-malware.4123033/
- https://docs.vmware.com/en/VMware-W...e_Enrollment/GUID-AWT-KNOXBULK-PREPARING.html
In contrast, my own device was paid-for outright, no trade-in, no financing etc.
Click to expand...
Click to collapse
Ah I see. My device was purchase direct from Samsung. I had it rooted and one day while rebooting after installing a magisk module I got the 'Custom binary blocked due to remaining instalment balance' error message which ties in with what you described about trade-ins and financing. Not sure why this was triggered though.
Flashed stock and re-locked the bootloader and the OEM unlock option has been gone ever since.
Of course Samsung support were as helpful as you'd expect...
I'm just putting up with the root-free life until my next phone purchase.
Thanks for the informative write-up!

DanielM1418 said:
Ah I see. My device was purchase direct from Samsung. I had it rooted and one day while rebooting after installing a magisk module I got the 'Custom binary blocked due to remaining instalment balance' error message which ties in with what you described about trade-ins and financing. Not sure why this was triggered though.
Flashed stock and re-locked the bootloader and the OEM unlock option has been gone ever since.
Of course Samsung support were as helpful as you'd expect...
I'm just putting up with the root-free life until my next phone purchase.
Thanks for the informative write-up!
Click to expand...
Click to collapse
You could try to contact Samsung support and ask for the contact details of the trade-in / financing department. If you have the original trade-in order number / confirmation number from when you purchased the device, and all bills have been settled, you might be able to convince them to unlock it, after all it's then technically none of the ... business. Worth a try? ... g/l !!