Database Info

I'm not sure if my Z5 is encrypted anymore?

Hi,
I always used to have full device encryption on my Z5 turned on, but after update to Nougat I'm honestly not sure if it's enabled anymore.
You see, with Android 6.0 the device would always ask me for the encryption pin when turning on, so before Android starts booting up - presumably to decrypt the system partition.
But after upgrading to Nougat it doesn't do that anymore - it just boots right into the system, where obviously it asks me for my pin to unlock the screen, but that lack of the pin input screen on boot is worrying to me.
In the settings, it still says that encryption is enabled.
Does anyone know if if this is expected?
{
"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"
}

gambiting said:
Hi,
I always used to have full device encryption on my Z5 turned on, but after update to Nougat I'm honestly not sure if it's enabled anymore.
You see, with Android 6.0 the device would always ask me for the encryption pin when turning on, so before Android starts booting up - presumably to decrypt the system partition.
But after upgrading to Nougat it doesn't do that anymore - it just boots right into the system, where obviously it asks me for my pin to unlock the screen, but that lack of the pin input screen on boot is worrying to me.
In the settings, it still says that encryption is enabled.
Does anyone know if if this is expected?
Click to expand...
Click to collapse
Disable and enable again, thats the reason to always wipe between updates.

Hi, thanks for replying - I don't think I can disable encryption, clicking on the "encrypt device" doesn't do anything. I guess I need to do full wipe, restore from backup, then encrypt again?

gambiting said:
Hi, thanks for replying - I don't think I can disable encryption, clicking on the "encrypt device" doesn't do anything. I guess I need to do full wipe, restore from backup, then encrypt again?
Click to expand...
Click to collapse
Yes, that would be best.

I had the same issue, the problem was I was using an app that isn't by sony or google and was enabled as a device administrator. Uninstalling it solved the problem

Hardbricked - System destroyed!

Hello!
I was disappointed about some missing features in MIUI ( unable to unlock by bluetooth by not Xiaomi devices, no reliable notification LED,.. ) so I decided to flash Android P ( I know, it´s beta, but it´s AOSP ) by using the Xiaomi Flash Tool. I left the button at 'clean and lock', because I don´t wanted to go back in the near future - and this was a big mistake! The tool shown after flashing 'successful', but since then the Mix2s shows 'system destroyed - push power button to switch off' on booting. I get access by fastboot, but the bootloader is now locked....
I´ve tried to get access by deepflash, but the problem is, that if I connect it to USB the phone switches on and shows the mentined message - again and again. I´m not able to switch it off, to get the connection by qualcomm drivers to USB. I tried to push and hold the power button very long, push all buttons together and so on...
Has anyone an advice or can tell me about testpoints of the Mix2s ( if it has? )
{
"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"
}
When in edl mode, only nop and sig tags can be recevied before authentication.
Thanks!

In this thread, some users speak about test points. There is a photo of it
http://en.miui.com/thread-3123002-1-1.html
Edit: Method for Mi Mix 2, maybe this can help you...
http://en.miui.com/thread-1351514-1-1.html

You should send it to customer servt

You can try to contact xiaomi support, they can grant you access to unlock the bootloader without adding an account... However, there were only one or two guys in miui forum who were successful with that, for all the others xiaomi said they can't allow it

What happens when you try to unlock your bootloader? And why cant you unlock it again?

Enter Fastboot and unlock your bootloader again by using xiaomi mi bootloader unlocking tool.

same problem when i've flashed the beta, i had to unlock the bootloader again and the phone boots

[Firmware][Android 9][Moto G8+][No-Official Installation]

{
"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"
}
Disclaimer:
I'm not the one who build this method I just wanna share the only way I found to downgrade this phone to android stock. I'm not responsible for any brick or bad use you may have with your phone.​
Requirements:
* Bootloader Unlocked
* Motorola Drivers Installed on your PC.
* USB Debugging Enabled on your Device
* A Moto G8+ XT2019-2 Compatible with this firmware version
(All your information and data will be erased from your device. Please make a backup before proceed).
Your can download the firmware build without bloatware or pre-installed apps from my one drive storage here
After decompressing the file your can read the "DOHA" .txt to see all details of this android 9 build. Also you can right click to "Flash ROM" and "edit" to check all command line on the main file.
The last step its connect your Moto G8+ on fastboot mode to your PC and double click to "Flash ROM.bat" a CMD window automatically open to flash your device. DO NOT CLOSE THE WINDOW. Wait until finish and the device will be downgrade to android 9 stock.
If everything was fine the CMD window will automatically close and the device will be restart.
Additional Notes:
* With this firmware version will NOT work some moto gestures.
* The system goes more smoothly and apps open more faster.
* Battery life improved a lot more compared to android 10
* You can still receive OTA updates

Does it work if I have latest update with Android 10 version? QPIS30.28-Q3-28-26-4-1-7 (amxmx)

micklov said:
Does it work if I have latest update with Android 10 version? QPIS30.28-Q3-28-26-4-1-7 (amxmx)
Click to expand...
Click to collapse
Sorry for the late reply.
I was on android 10 at the moment of flashing the rom and since then i'm still using it. Not problem at all if u follow the steps on this post.

Pixel 4a w/ May 2021 Security Update - Passing SafetyNet check

Hey everyone, I just got back into rooting and well I would like to share some useful information that helped me pass the saftynet check within Magisk in 2021 with the latest security update (May 2021).
First off, I followed this guide to unlock my bootloader and gain root: google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet
I did run into some issues were I was not able to run fastboot in the cmd terminal.
To fix that, I downloaded
Google Pixel 4A Driver for Flashing Firmware
Google Pixel 4A USB Driver for normal connecting to PC
from here: google-pixel-4a-usb-drivers and it fixed my issues with not being able to run fastboot cmds.
​After that, I was able to unlock my bootloader and root my Pixel 4a.
I followed the last step in the thread google-pixel-4a-how-to-unlock-bootloader-root-pass-safetynet on how to pass the safetynet check but it did not work for me. Installing MagiskHide Props Config and enabling MagiskHide did nothing.
So I downloaded an app from the PlayStore called Turmux where I half followed these steps: MagiskHide Props Config. I say half because the option "force BASIC key attestation" is no longer an available option. I went a different route. I selected the option Edit device fingerprint -> Pick a certified fingerprint and it is pretty self explanatory after that. Just make sure you pick your device model ad double check that the file and path are correct. (more info here)
This helped me pass the basic integrity check but this isn't enough!
{
"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 about 10 mins of googling and found this thread which lead me to the final fix. Instructions are in the screenshot below.
And that is all. check it out!
Happy modding xda fam!
P.S I am not in any way responsible for what happens to your device, your laptop, or the mods you decide to install afterwards. ​

Please let me know if there is any confusion that I can clear up.

How should I go about rooting my Galaxy a10e

So I got the first step, flashing TWRP. But, there's only a version of TWRP for the a10, would this work?

you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io

imalreadycrying said:
you don't really need twrp for root, just follow this guide
Installation
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
my phone doesn't show an oem bootloader unlock option

is it grayed out or do you just not see it

imalreadycrying said:
is it grayed out or do you just not see it
Click to expand...
Click to collapse
doesn't exist.

do you have dev options?

imalreadycrying said:
do you have dev options?
Click to expand...
Click to collapse
yes

send me a screen recording if you can, dev options should look 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 have previously tried Kingo/King Root which worked on my KitKat Nabi tablet, I tried that on my a10e it failed. Root checker says there is no root for andr 11 on the a10e

whatever you do, do NOT use kingoroot, it basically installs a outdated version of SuperSU (which isn't liked by the community anymore because the original developer sold it to some random company) and bloats ur system up.

Yep, no OEM bootloader unlock option in dev settings

it may be possibly locked to your carrier. again, you can send me a screen recording or get an unlocked phone

My phone appears to be unlocked already, there is no sign of Verizon still being on here. I have since upgraded phones and the SIM card isn't in anymore.

Do I have to factory reset to fully get rid of the OEM?

i found this youtube video with some quick searching. it's in hindi but you can get the gist of it.

I most certainly dont have to disable automatic time right?

i don't know, after you get the option maybe you can set it back

i followed and nothing happened

did you reboot your phone after the fact?

yep, nothing works