Database Develop

Device Encryption Question/Issue with Unlocking

I have had some issues with my phone since unlocking with sunshine. See separate thread http://forum.xda-developers.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.
I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.
So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.
My question is has anyone else experimented with device encryption and is this behavior expected?
Thanks.

Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.
As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.

I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.
At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.

This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.

Astrobrewer said:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
Click to expand...
Click to collapse
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.
Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.

Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.

Astrobrewer said:
Thanks for the info @TheSt33v, but I'm not sure that it's totally broken.
The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
Click to expand...
Click to collapse
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.

TheSt33v said:
Just FYI, our TWRP maintainer has fixed decryption...
Click to expand...
Click to collapse
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.

Astrobrewer said:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.
Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
Click to expand...
Click to collapse
Most people don't seem to think it's worth the impact that it has on performance.

I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app

Astrobrewer said:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
Sent from my DROID Turbo using XDA-Developers mobile app
Click to expand...
Click to collapse
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.

oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.

TheSt33v said:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562
If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
Click to expand...
Click to collapse
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?

oldidaho said:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
Click to expand...
Click to collapse
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.

TheSt33v said:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
Click to expand...
Click to collapse
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.

oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.

oldidaho said:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.
Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?
thanks for the help and information.
Click to expand...
Click to collapse
oldidaho said:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
Click to expand...
Click to collapse
oldidaho said:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RRI need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
Click to expand...
Click to collapse
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
But it's your phone, so you can run what you want.
I do commend you for having a recent backup on your PC.

ChazzMatt said:
Well, just as you used CM13 and RR just fine without encryption, not sure why you went to CF instead of RR just because encryption didn't work. But it's your phone.
Just not sure why you are implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.
I do commend you for having a recent backup on your PC.
Click to expand...
Click to collapse
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.

oldidaho said:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
Click to expand...
Click to collapse
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.

Mystery solved!
Astrobrewer said:
... At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.
Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
Click to expand...
Click to collapse
I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:
Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:
"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default!
But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???

Questions regarding dm-verity and OOS 4.0.x

Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?

mad-murdock said:
Hey there.
I got my 3t in the day, 4.0.0 was released. So I unlocked my bootloader after upgrading.
At the time, dm-verity was new to me and so I ignored it.
By now I read up on it and guess I get it. What doesn't fit to what I read is the fact, that I modified my system in many ways. By flashing TWRP, by modifying system with super su and things like ad blockers (hosts file) and pixel launcher.
Yet I never installed the verity fix. I also use encrypted data partition.
How can that be?
My only guess is, I never installed a custom kernel yet or another Rom. But then again verity should be triggered way earlier. Did 4.0 not fully implement it?
Click to expand...
Click to collapse
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...

ram4ufriends said:
They say (in twrp thread and in oneplus forums) if you flash supersu, you are fine...
Click to expand...
Click to collapse
When am I not fine? Protection only triggers if kernel is exchanged?
It's not that I don't want to flash it, but I am eager to know.

*bump* - trying a last time, to see if anyone knows details

The whole point of dm verity is to make sure phone is not rooted or modified in any way that could compromise app security, luckily it doesn't work quite 100% as we can still root without triggering it, even though it should.

I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone

I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!

mad-murdock said:
I guess, the answer to my question is, TWRP automatically applies the dm-verity patch on first install. I overlooked that feature to be honest, but it makes total sense to do so and protect custom recovery users from locking out of your phone
Click to expand...
Click to collapse
It's my understanding that SuperSU applies the dm-verity patch when it's installed.

napetost said:
I have this questions too. And I can't decrypt Data even if I input the right password. I can't use recovery anymore with TWRP or the stock rec.
Here is some details about the dm-verity. https://source.android.com/security/verifiedboot/verified-boot.html
I only know Android N will encrypt Data by using f2fs file system.........
If you have some effective methods, please tell me. Thanks a lot!
Click to expand...
Click to collapse
flash TWRP 3.0.3-1-beta1 and try again

I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.

napetost said:
I have found the right way!
First, you should flash back to OOS3.5 6.0, then set the pin password. And then copy OOS4.0 to /sdcard ,then using system update.Then you will update to OOS4.0 and you won't see any dm-verity problems.
Click to expand...
Click to collapse
That's one way. Using the TWRP beta is another. It's in the TWRP post, page 55, bottom. Post 550. Actually the last few pages of that post discuss this issue right now. Might be worth reading.

Mi8 force encryption with EU roms

HI guys! I have noticed that Xiaomi.eu ROMs dont have device encryption enabled by default. There is also no way to manually encrypt the phone as it would crash. While searching for the solutions I have found some solutions such as modification of "fstab.qcom" by changing "encryptable=ice" to "fileencryption=ice" but those do not work on MI8. I have found also a .zip file which would do the modification but also no success.
Any suggestions how encryption could be enabled on EU roms? With newest TWRP which does support it our unlocked devices could be much more secured.

you need to format userdata to remove encryption then flash zip remove encryption to work

richardyusan said:
you need to format userdata to remove encryption then flash zip remove encryption to work
Click to expand...
Click to collapse
By flash zip remove encryption do you mean dm verity zip?

landryna said:
By flash zip remove encryption do you mean dm verity zip?
Click to expand...
Click to collapse
I think he means you need to format userdata not wipe it, so that encryption is removed. After that you can flash the zip with the rom and it will work. That is at least how I had to do it to get EU roms to work. There is currently no way to have encrypted device with EU roms.

Superbia said:
I think he means you need to format userdata not wipe it, so that encryption is removed. After that you can flash the zip with the rom and it will work. That is at least how I had to do it to get EU roms to work. There is currently no way to have encrypted device with EU roms.
Click to expand...
Click to collapse
Well this is not the solution then - the pupose of this thread is to check how to have BOTH:
- Xiaomi.EU rom installed
- Encryption switched on and working on the device
Apparently as per your comment it is not possible. The only question is: why to install Eu rom and leave device completely unsecured to anybody who can google: 'remove twrp lock code' and why it does not concern people here..

have you tried with this guide?
https://xiaomi.eu/community/threads/howto-encryption-on-a-mi-6-with-xiaomi-eu-roms.43286/
if you try, let us know the results

gulp79 said:
have you tried with this guide?
https://xiaomi.eu/community/threads/howto-encryption-on-a-mi-6-with-xiaomi-eu-roms.43286/
if you try, let us know the results
Click to expand...
Click to collapse
Hi. Of course I have checked this in first instance. Partition is not encrypted so it doesn't work unfortunately.

landryna said:
Hi. Of course I have checked this in first instance. Partition is not encrypted so it doesn't work unfortunately.
Click to expand...
Click to collapse
HELLO
are you still digging on the subject?

[Q] Magisk data partition remain encrypted.

Hi, everyone
Is it possible after installing magisk and rooted,to keep the data partition remain encrypted without bootloop ?

I have yet to find a way, however there is a user claiming to have root with data & system encryption on the Oreo 8.1 ROM. I'm on 9.0 Global, and tried a million different ways. Encryption is different from 8.1 to 9.0 ROMs. I think the .eu multi-language ROM based on China disables the Data encryption (even though it reports Encrypted, the system is encrypted). There was a thread here that told about possibly enabling data encryption while keeping root on the .eu multi-roms, but i have not tried. I prefer the Global ROM.
If anyone can get root with the System partition AND the Data partition fully encrypted, please let us know!

Here in the forum there is a topic where one member helps another to get it done, and the encryption is done. I do not know if there's root in the middle of the tutorial.

on official global I think there is no way to run rooted and encrypted.
on xiaomi EU encryption is disabled by default, but you can enable it by editing fstab. qcom in /vendor/etc. I have already posted about how to do it, search xda

The newer versions break twrp encryption support I was running miui.eu with encryption up untill stable 10.0.0.2. in 10.0.0.3 their must have been some sequrity upgrade that changed the encryption because twrp would no longer decrypt the data partition

mikefallen said:
The newer versions break twrp encryption support I was running miui.eu with encryption up untill stable 10.0.0.2. in 10.0.0.3 their must have been some sequrity upgrade that changed the encryption because twrp would no longer decrypt the data partition
Click to expand...
Click to collapse
The new TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150 does decrypt 9.0 without issues. I use it, but still no way to have encrypted data with ROOT that i know of on Global ROM.

Is there any way to root/magisk global rom 10.0.3 ?, no need encrypted data.

Agimax said:
The new TWRP-3.2.3-0918-XIAOMI8-CN-wzsx150 does decrypt 9.0 without issues. I use it, but still no way to have encrypted data with ROOT that i know of on Global ROM.
Click to expand...
Click to collapse
Oh sweet ill have to check that out i hate not having encryption'
And yes you can run global with no encryption and root just flash no dm-crypt and wipe userdata, lots of guides

Question Internal Storage Encrypted

I need some help, I have Mi 11 Ultra CN version, I unlocked BL and install the Global Rom using fast boot, I enjoyed it, but battery seems to suck.
I installed MIUI EU 12.5.4 and now that I'm trying to update it to EU 12.5.7.0 within the phone, it tells me my internal memory is encrypted. How can i install the update or decrypt my internal memory. It does not allow me to install the update... any help will be appreciated it..

Mr_creeper_98 said:
I need some help, I have Mi 11 Ultra CN version, I unlocked BL and install the Global Rom using fast boot, I enjoyed it, but battery seems to suck.
I installed MIUI EU 12.5.4 and now that I'm trying to update it to EU 12.5.7.0 within the phone, it tells me my internal memory is encrypted. How can i install the update or decrypt my internal memory. It does not allow me to install the update... any help will be appreciated it..
Click to expand...
Click to collapse
Remove lock screen security

NOSS8 said:
Remove lock screen security
Click to expand...
Click to collapse
I don't have a password, or lock pattern for lock screen..

Mr_creeper_98 said:
I don't have a password, or lock pattern for lock screen..
Click to expand...
Click to collapse
You can try with Mi flash (dont relock bootloader)

MIUI EU 12.5.4 not EEA but CN version

Set a lock screen lock, then go to twrp and use it to unlock and decrypt the storage

i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all

Mr_creeper_98 said:
i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all
Click to expand...
Click to collapse
There is no downsize. You are only replacing stock recovery with a different version. It has no affect on your phone, it's and your own data. It just makes it easier to flash custom or even returning to stock if required as well as other tools offered in the TWRP package.

Mr_creeper_98 said:
i was able to install twrp and that did the trick, BTW what's the downsize of installing twrp as my boot recovery... it's been a while since I mess with a phone but now my google messages says network not ready when sending a picture message, but i can received them, if I use the stock message app, I don't have any issues at all
Click to expand...
Click to collapse
can you tell me how you did that?i have the same problem with my mi 11 ultra.CN version ,put the global version on it 12.5.4.0 and cant update to 12.5.7.0 because encrypted internal storage.
im not well known with TWRP.

Try what I wrote in post 3, https://forum.xda-developers.com/t/internal-storage-encrypted.4289325/post-85151561

I don't know what I do wrong but I installed twrp but it said that my phone is not rooted

sheephurther said:
I don't know what I do wrong but I installed twrp but it said that my phone is not rooted
Click to expand...
Click to collapse
Give me a couple of hours until I get home and I'll show you how I did it.. I did not root my phone BTW

@sheephurther I used this Xiaomi ADB/Fastboot to install TWRP
https://github.com/Szaki/XiaomiADBFastbootTools/releases/tag/7.0.3
Hope this will help you..
Make sure phone is in ADB Debugging mode.

Thanks.i gonna try later today.i let you know if it worked.

sheephurther said:
I don't know what I do wrong but I installed twrp but it said that my phone is not rooted
Click to expand...
Click to collapse
Installing twrp doesn't install root. It just replaces the system recovery. If you really want root, use Magisk but I've not found any reason to root my phone for ages.

I tried today but it doesn't work.
To bad!!I'll try it later on.

sheephurther said:
I tried today but it doesn't work.
To bad!!I'll try it later on.
Click to expand...
Click to collapse
Did you try setting a lock screen pin, pattern or pw and then using it to decrypt in TWRP? I'm using 3.5.1 twrp version fine.

sheephurther said:
can you tell me how you did that?i have the same problem with my mi 11 ultra.CN version ,put the global version on it 12.5.4.0 and cant update to 12.5.7.0 because encrypted internal storage.
im not well known with TWRP.
Click to expand...
Click to collapse
Change your password to 1234 and try it again
When your get asked to decrypt enter 1234 and press the ok bottom on the bottom right

Is there a film on YouTube that exactly tells how to install Twrp on mi 11 ultra?I tried several but it does not work.how difficult can it be??or maybe I am Tu stupid

I sold a phone yesterday to somebody, doing the full wipe before that. It was on the latest weekly Xiaomi.eu. Now it has this issue. Is it possible that it is the same thing?