Hello,
I'm using Xiaomi Redmi Note 8 on MIUI Global 11.0.3.
I can't find the encryption option on the phone.
I've enabled developer options. According to other users, they report this option is found here:
Settings - Additional settings - Developer options - Encrypt device using lock screen password
However, there is no such an option although I activated developer options. Which means that is no encryption available (on older Xiaomis, when one activated device encryption, the password is set so when booting up the phone, the user must provide that password in order to decrypt and use the phone).
Any thoughts?
{
"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"
}
Did you ever find out how to do it? I just bought the Redmi note 8, with miui 11... and it's not there. Can't use the phone without this feature.
Dizzee said:
Did you ever find out how to do it? I just bought the Redmi note 8, with miui 11... and it's not there. Can't use the phone without this feature.
Click to expand...
Click to collapse
Nop, I'm still waiting for a solution I don't understand why the feature is not present, and I don't want to use the phone without encryption
Full device Encryption not support on Mi11.0 Note 8
Not able to understand why this basic feature has been removed after 11.x version.
Does anyone has any workaround to fix this issue. I cant use my phone without FDE.
Go to "Settings -> Passwords & security -> Privacy -> Encryption & credentials -> Encrypt phone" , click Encrypt, set up your passcode.
Then go to Developer settings and look for the option mentioned above.
I don't understand why people are confused about this. The phone comes encrypted by default (out of the box) and my redmi note 8 utilises File based encryption so I assume this is standard for all others. There is no option to encrypt using lock screen password as far as I can tell but that does not mean it is less secure. With FBE each file has a different encryption key which is encrypted with a master key, the master key is then encrypted with your lock screen password, at least this is how I think it works but you can find out more online. While your phone is on encryption keys are stored in RAM I believe so if you think your phone will be seized or stolen simply restart it.
---------- Post added at 09:56 PM ---------- Previous post was at 09:42 PM ----------
There is a terminal app called Termux that provides a command-line you can use for checking if your phone has encryption enabled. You can download it from the play store. Once you download, type getprop ro.crypto.state . The output will tell you 'encrypted' or 'unencrypted'. To check if FDE or FBE, Start Termux and enter the following command: getprop ro.crypto.type . If the output is file your device uses File Based Encryption and block if it uses Full Disk Encryption
Related
The Below Instructions are only For Chinese DEV ROM on Redmi Note 3
1 . Go to Setting->Syestem apps->Security->Permissions->Disable Permission manager (Allowing to apps to take permissions without asking)
2. Open Security app->Permission->Root access-> It askes to Allow to Root access -> Okey ( Reboot and Flash automatically , the white flash Progress bar appears , wait to finish and reboot to system ** you must Connect to Internet**) <<It comes only for first time>>
{
"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"
}
3. Click Here , Download and Install Google play Installer 2.0 ( Instructions and Guidance)
4. Open Google Play store and search for Rom Toolbox Lite and Install it
5. Open Rom Toolbox Lite , it will ask for Root Access Permission , Just Tab on Home Button (It needs for being known the app by Security app)
6. Open Security app->Permission->Root access-> Tab to enable Rom Toolbox Lite .( A msg asks 4 times for Next and finally accept <<each takes 5 seconds>>)
7. Open Rom Toolbox Lite ->App Manager -> Find Mi app store and Tab on it ->Tab Freeze
8. Go to Setting-> Installed Apps-> All->Find Mi app store and Tab on it ->Tab Uninstall
9. Open Security App->Permissions->Autostart->Find and Tab on Google Play Store-> Enable Allow Apps to Start automatically and Allow the App to be started by other apps. (Other Apps will address and call Only Google Play Store For Installing another Apps)
Now your Google Play Store is as Default app Store automatically Due to there is no another App Store.
Enjoy !
Works perfectly for me. Thanks man!
Grantius said:
Works perfectly for me. Thanks man!
Click to expand...
Click to collapse
YOUR WELCOME
I've already asked this question in another thread but didn't get any answer yet: do i still have root access on the China Dev ROM or not? If so, does the Global Dev ROM also has root access?
Member
Hi your ideas look great
but i cant find the root access anywhere
plz reply me for this problem
---------- Post added at 06:16 AM ---------- Previous post was at 06:13 AM ----------
yes i am also facing that problem
i cant find it anywhere
I do not have "Secure startup" option in my S7e settings
This is so strange I rooted my phone a lot before
Is it because of flashing drm disabler in TWRP ?
Any Idea ?
{
"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"
}
Sent from my SM-G935F using XDA-Developers mobile app
Hani88 said:
I do not have "Secure startup" option in my S7e settings
This is so strange I rooted my phone a lot before
Is it because of flashing drm disabler in TWRP ?
Any Idea ?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Your device is not encrypted due to what you did, thus secure start up cannot work, there is nothing to secure without encryption lol
Galactus said:
Your device is not encrypted due to what you did, thus secure start up cannot work, there is nothing to secure without encryption lol
Click to expand...
Click to collapse
I understand now dude
Sent from my SM-G935F using XDA-Developers mobile app
Galactus said:
Your device is not encrypted due to what you did, thus secure start up cannot work, there is nothing to secure without encryption lol
Click to expand...
Click to collapse
So, if I turn on the "secure startup" option, will my lockscreen password be my data partition encryption password? If I turn off this option, my data partition is still encrypted, but with a password (or key file) I don't know? Where does this password (or key file) store?
What if I want to update Samsung apps? I doesnt let me only if I enable secure startup.... but since it's missing I cant install the updates... (on SuperMan rom).
If I'm correct, that is the trick intended for android n stock rom with august patch. That is very spesific situation. I think you're out of luck, mate
How can i restore backup google authenticator database to move to another device ? i found few tutorials but 0 vides on this and i still don't know how to do it, my phone is rooted bu even when i go to that map with my file manager i get " access denied" in map so i don't know how to do it
Casper9696 said:
How can i restore backup google authenticator database to move to another device ? i found few tutorials but 0 vides on this and i still don't know how to do it, my phone is rooted bu even when i go to that map with my file manager i get " access denied" in map so i don't know how to do it
Click to expand...
Click to collapse
I don't think there is away to back it up completely. For each account you add into the Google Authenticator, you are usually given a recovery key at setup. You need to keep the key safely and use it for recovery whenever you need it. Once you have configured it, you will usually not have the option to review the key again due to security reasons.
fylim said:
I don't think there is away to back it up completely. For each account you add into the Google Authenticator, you are usually given a recovery key at setup. You need to keep the key safely and use it for recovery whenever you need it. Once you have configured it, you will usually not have the option to review the key again due to security reasons.
Click to expand...
Click to collapse
I founded on some website that i can get database out and with sqelite 3( or something like that) i can find for each account same code that i already used and can use again. But i got database out but i cant open it with that program ☹
{
"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 switched to Authy some years back after having to manually disable and re-enable 2FA on like fifteen accounts following a phone migration.
Now my codes easily move to a new device. No complaints.
Aganar said:
I switched to Authy some years back after having to manually disable and re-enable 2FA on like fifteen accounts following a phone migration.
Now my codes easily move to a new device. No complaints.
Click to expand...
Click to collapse
Damm i have more than 25 2FA accounts i will need 1 day just for that haha
You can transfer your google authenticator accounts from one phone to another, using this method
If our Galaxy Fold phone (SM-F900F) has the Esim option disabled and does not allow adding a second line.
Here we will have the solution. (Factory phone will be restored)
{
"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"
}
1.- We must go to google play and download the application "Google phone".
2.- Once the application is downloaded we will have to open it and give it permissions.
3.- We will enter the following code: "* # * # 27262826 # * # *"
4.- A menu will be displayed in which it will notify us that we have CSC installed and we can verify that our system is not one of the first but one that has the word (single) (in my case MXO (simple) = Mexico 1 line) . That means the esim is disabled and you only have one phone line (PHYSICAL SIM). (Due to this problem, we do not have the esim option enabled).
5.-We will remove the SIM card from the phone to continue.
6.- Now we will select the csc of the country we want (that does not contain the word "single" because those are the ones that will not have the esim deactivated) (in my case I will select INU which is the csc of Inda and is the first to always update )
7.- We will install it and 3 options will appear, we will select the first (Sales & Network Code Change) and click on OK.
8.- Followed by the phone will restart and everything will be erased.
9.- When you request to activate the phone and select the language we will insert the PHYSICAL SIM card
10.- We will add all the data and start the phone.
When going to the phone settings we will notice that the option to add an Esim is already available. y The available imei 2 will appear.
Ready.
we will have concluded.
Hey i have tried but didn't get the menu. I have android 11.
Hey, running this on an AT&T unlocked SM-F900U phone and got the menu of the attached picture. Which shall I choose to keep unlocked and enable eSIM ?
theunf said:
Hey, running this on an AT&T unlocked SM-F900U phone and got the menu of the attached picture. Which shall I choose to keep unlocked and enable eSIM ?
theunf said:
Hey, running this on an AT&T unlocked SM-F900U phone and got the menu of the attached picture. Which shall I choose to keep unlocked and enable eSIM ?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Tried the XAA which is the USA unlocked. It processed the request, rebooted the phone but did not erase it and esim menu is still locked.
Repeated the procedure and the gui shows XAA as preset for Sales/Net, Net2 code.
Hi,
I have an issue with spoofing device information (e.g. manufacturer, device model, Android OS version, etc) on my Samsung Galaxy A03s device. This device was rooted via Magisk.
I tried to use the MagiskHide Props Conf Module (https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf) to spoof the device info, the module can run smoothly without any issue, but after device rebooting, the spoofed device info didn't take effect, so all my device info are still kept remaining.
After I tried to use "Device Faker Plus" app (via Edxposed framework) to spoof these device info, my device info can be changed when I check via CPU-Z or DroidInfo or built-in device info feature as below pictures:
{
"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"
}
In the above picture, there is a strage point that the Model number value was changed when I check from built-in device info, other info are still kept remaining. But these info were displayed differently from view of CPU-Z and Droid Info tool.
But from my testing app (this is a native app designed to collect device info/fingerprint via integrated SDK), I found that the real information are not still changed, it means that my test app can record all the original device info such as: Manufacturer is Samsung, Model number is SM-A037F/DS, Android OS is 11 version.
Finally, I tried to use a tool "BuildProp Editor" to edit manually parameters of Manufacturer, Model number and Android OS version from these 02 files: (1) /system/build.prop and (2) /default.prop as below, the change is ok and the files can be saved, but after rebooting, there is no effect, all information are still kept remaining (although changed parameters are still kept in these files).
After that, I found that there are 2 other files still contains the original device information are: (1) /system/vendor/build.prop and (2) /product/build.prop , I can't use BuildProps Editor tool to change these paramters on this file (1) /system/vendor/build.prop, the file is not able to save after my change as below images:
With the file (2) /product/build.prop, I can use BuildProps Editor tool to change these parameters and save it successfully, but when reboot the device, I am in the trouble with "boot loop" issue (please refer to my attached video).
My questions:
1. Does anyone tell me what is different between these files: (1) /system/build.prop; (2) /default.prop; (3) /system/vendor/build.prop and (4) /product/build.prop ? and which file can be affected to changing device info ?
2. Can anyone use MagiskHide Props Conf module or any tool to spoof device info successfully on this device model - Samsung A03S ?
3. Does anyone know why MagiskHide Props Conf module or Device Faker Plus tool can't change my original device info ? what are the possible root causes here?
Thank you
Anyone please help me in this case ???
Anyone please help me in this case ???
hey brother did you get this to work???