Database Develop

TWRP telling me device is encrypted on clean install with no lock screen

While trying to go from a custom ROM to the official global stable, I'm having issues. I used Mi Flash to install the rom with no issue, but when I boot into TWRP with fastboot, it tells me the data is encrypted. I have no lock screen on and I can't decrypt it because default_password didn't work. I'm going to try to explain to the best of my ability exactly what I was trying and what I did to get here.
Starting point: Epic Rom
I used mi flash tool to install official Nougat Global Stable ROM.
I accidentally lock my bootloader doing this, but no big deal, I unlock it again with the tool xiaomi provides.
I guess the official ROM has it's own recovery, since it overwrote TWRP.
I reflash TWRP, and use fastboot to boot into it.
I wanted to install magisk, so I boot the phone, download it, and boot back into TWRP from the command line.
Here's where I notice the data is encrypted and I can't access internal storage to install magisk.
I start over and reflash the global rom and twrp, this time not setting a lock screen at all.
Still encrypted.
Wipe userdata and repeat.
Still encrypted.
I'm lost at this point. I can't even flash a custom ROM because I again can't get into my internal storage in TWRP to install it. Does anyone have any ideas? I'm a bit desperate at this point

After a little bit more searching, it seems it automatically encrypts if supersu isn't installed. Is there a way around this for magisk?

I recently had the same issue with the global stable rom, twrp wouldn't show anything in my internal storage. How I fixed it was miflashing the latest global stable developer rom instead an then twrp , an that did it..... I was able to see internal storage. For some reason the global stable doesn't allow you to see the storage. Hope that helps

kjm2323 said:
I recently had the same issue with the global stable rom, twrp wouldn't show anything in my internal storage. How I fixed it was miflashing the latest global stable developer rom instead an then twrp , an that did it..... I was able to see internal storage. For some reason the global stable doesn't allow you to see the storage. Hope that helps
Click to expand...
Click to collapse
Brilliant, this worked! My issue now is that, as far as I can tell, developer ROM isn't on MIUI9? That seems strange, but I guess I may go back to a custom ROM in this case.

master565 said:
Brilliant, this worked! My issue now is that, as far as I can tell, developer ROM isn't on MIUI9? That seems strange, but I guess I may go back to a custom ROM in this case.
Click to expand...
Click to collapse
I know I'm on the latest an it is miui8, which I'm fine with... The device runs great an has everything I need. Just a heads up I didn't shut the updater off an left my phone on wifi. When I woke up in the morning it auto updated to the newest rom an I lost twrp, SU, xposed.... Had to re-do all that. Everything worked but just a pain. You don't get that auto update running a custom rom.

Twrp and encryption

Hello
Yesterday I unlock the bootloader to flash Xiaomi.eu Rom on a Chinese MI8 and I noticed that is not encrypted.
When I try to encrypt it, I get a brick. Seems that twrp-3.2.3.0.-dipper not support encryption partitions and I not able to see the sdcard partition and I had to flash in fastboot to revive the phone.
The second test was flashing the official chinese ROM since it’s encrypted from beginning with twrp-3.2.3.0 and recovery-TWRP-3.2.2-0711-XIAOMI8-CN-wzsx150. With the last, the phone hangs on boot, and with twrp-3.2.3.0 boots but the filesystem seems encrypted from TWRP.
I come from MI5s Plus and it ask me the encrypted password when it try to mount the filesystem.
anyone succeed the encryption?

Seaching for a solution as well. I had similar experience like you with global beta and global stable, bl unlocked, twrp.
I need magisk as well, so only solution for now is to run unencrypted, if I activate encryption I cannot boot anymore.

@grootooter , I can confirm you that the recovery TWRP 3.2.3-0918-XIAOMI8-CN can read the encrypted filesystem in the chinese rom.
It not boot only with "fastboot boot recovery.img", you need flashing it.
I don't know if you can use magisk with encryption because dm-verity.
That's the reason because I stay in the chinese ROM, that has native root.
Someone would have to try this TWRP with Xiaomi.EU, then encrypt the filesystem and post the results.

Complete delete of internal storage after switching to F2FS

I was switching to f2fs after new unlocking bootloader, because i wanted to instal Elite rom. I did not do a backup. (Yes, i am idiot...).
What to do now? I can get into bootloader, so i could flash boot.img? But where to find that? In Elite rom zip there was none boot.img.

Solved

(flashing / booting) Problems with all roms

Hi,
since many days I have a new Mi8.
The device is a chineese model, and because it was delivered with unlocked bootloader and a shop ROM, i want to use the latest Xiaomi.eu stable rom.
After flashing the TWRP, i cleared all (System, Data, Cache, internal storage) and installes the latest xiaomi.eu ROM.
Unfortunately the ROM was notstartet. Later i readed, that the xiaomi.eu ROM needs the system partition, so i tried to install some different ROMs.
All tested roms failed to install (device missmatch), so i tried to use different recoveries and at least i updated the vendor Image to MI8Global_V10.3.5.0.PEAMIXM.
After this, some Roms are able to install, mut the ROMs wont boot.
After a clean install of the xiomi global fastboot image, the phone is running, but i still have problems to install custom ROMs or the stable Xiaomi.eu ROM.
The fastboot ROM installation with mi flash tools ends with an error (Not catch checkpoint (\fastboot -s .*lock) Flash is not done (I choosed the option clean all, not the lock function)
cDroid Rom is working, but with this ROM i cant use google pay.
cDroid with update to xiaomi.eu weekly is also working, but also without google pay.
Xiaomi.eu stable - bootloops
Do you have any ideas why i cant use all ROMs?
Should i choose a chineesevendor image or something else?
I also heared, that it could be, that the device bricks, when i try to re-lock the bootloader, is this an option?
Which ROM should work fith functional google pay ?
Thanks in advance

The problem seems to be solved,
i have to flash "Disable_Dm-Verity_ForceEncrypt" after the flashing of every ROM, then I have no bootloops / boot Problems.
Now i only have the problem with google pay...

I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.

stevedat said:
I couldn't also get Miui Eu bootable on my mi8 last time. I didn't realize what you had mentioned Disable_Dm-Verity_ForceEncrypt. But I could manage to get MiRoom Miui workable and it seems ok for now.
Click to expand...
Click to collapse
DM verity zip removes the 'DM Verity' check that looks for modifications to the boot partitions (D-device M-mapper). You cannot boot with modifications (like root) without disabling the verity check. Also, if you are on a stock ROM, your custom recovery image file will be overwritten with stock upon reboot if you don't disable DM Verity. Hope this helps you understand more.
Found it on this topic.
I´m still looking for a ROM with google pay support, but iu think with unlocked bootloader and without root therre is no chance...

Bring light into the darkness of encryption

Hi togehter,
I had some problems with flashing new custom roms and ended up in a bootloop with not being able to boot to recovery. This could be solved by flashing the stock image with the xiaomi flash tool.
Before I will fu up again I would like to bring some light into the darkness.
When coming from Stock Rom:
1. Unlock Bootloader -> done successfully
2. Flashed TWRP Recovery -> done successfully but storage (data) was encrypted
3. Flashed Magisk via Recovery -> done successfully (storage still encrypted)
from here I was happy using the Stock Rom with Root.
Now I started messing things up:
Because there are a few things that bother me about the stock rom i wanted to use lineageOS/Pixel Experience. So I proceeded as following:
1. Backup my data (still have to enter key when starting twrp to decrypt the storage) -> done successfully
2. Flash LineageOS -> resulted in bootloop to TWRP
When entering twrp there was no query about the key and data where encrypted. Also the Backup was not accessible .
3. I used all in one tool to erase storage and decrypt data. -> successfully... Now i was able to place data on the internal storage again and start flashing a rom
4. Flashing LineageOS -> done successfully and able to boot into rom
Back to TWRP data was encrypted and I had to enter key.
5. Flashing remove force encryption script via twrp. -> done but now i was facing boot to black screen. TWRP was not working anymore.
Only way to get it work again, was flashing stock image.
Why is the data system always encrypted. This is rly annoying and backups don't work, because i can not encrypt them. Also, I can not put any files on the memory because it is encrypted.
I would rly like to try a custom rom, but I would also like to be able to go back to a backup. What have i done wrong?

You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.

SeppGoPro said:
Hi togehter,
.... What have i done wrong?
Click to expand...
Click to collapse
You need to format data (not just wipe data) in TWRP. Some people suggest before flashing a ROM and some say after, but I don't think it makes a great deal of difference either way.
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Then in TWRP wipe cache and dalvik, then format data.
Reboot into TWRP, or unmount and mount the data partition in TWRP so it correctly reads the data partition.
Copy across the ROM (and GApps if needed)
Them flash.
Boot into the ROM and you should be good.
After initial setup, if you want root, boot into TWRP and flash Magisk.
From here, if you've set a pin on the ROM, you'll be encrypted, but everything should still work normally. You should be able to access everything normally in TWRP and also perform backups. You should be able to got data across from/to a PC normally.
Turbine1991 said:
You have to flash no dm verify right after formatting data & flashing rom. Don't let it boot.
I would recommend using the stock firmware. Los/AOSP is rubbish for our device, it's too unstable, lacking features and has worse gestures.
Click to expand...
Click to collapse
Not true in many ways.
There is need to flash no dm verity. It's one way of solving the issue, but it's not the only way. You should only do this if you know what it's for and if you know you want this.
AOSP ROMs are not unstable. I've been using them on mine for over 4 months. None are perfect and they have a few minor issues/bugs, but they are far from being considered unstable. I've never had shutdowns, reboots or FC'S.

Thanks for the replies.
Robbo.5000 said:
Make sure you either flash the appropriate firmware and vendor recommended, or the fastboot ROM of that version.
Click to expand...
Click to collapse
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?

SeppGoPro said:
Thanks for the replies.
So for example with LineageOS 17 I can use the global vendor and firmware, but sometimes in the thread it is recommended to use chinese vendor and firmware. In this case I should flash another vendor and firmware then the global one.
What do you mean with a fastboot rom. How can I identify one of them?
Is the MiuiMix Rom a fastboot rom. This one changed my vendor and firmware. After flashing this rom, my bootlogo changed to redmi... Am i right with this suggestion?
Click to expand...
Click to collapse
Fastboot ROMs are official ROMs that are flashed through the Mi Flash Tool
, with the phone booted into fastboot mode and connected to the PC. They contains almost all partitions, including vendor and all firmware. They will be a .tgz file. They are mainly used as an almost failsafe way to recover the phone, should you mess things up. Flashing them will restore the phone to factory, so will lose TWRP, but you're guaranteed a clean starting point.
If, for example, you want to install Havoc 3, it is recommended to flash it on top of either China or India 10.4 vendor and firmware. So if you're phone is currently on global firmware, you would then need to flash, say, Chinese firmware and vendor flies, before flashing Havoc.
If you have been previously flashing other mods, such as 75Hz, screen refresh rate, for example, then you might choose to flash the official Chinese fastboot ROM, instead of just the firmware and vendor, to ensure that you've cleaned the phone of any mods, etc. In most cases you will be fine flashing firmware and vendor, though.
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.

Robbo.5000 said:
Miuimix is a custom ROM, which is based on the official China MIUI ROM. Because it's based on the China ROM this is why the logo changed to Redmi.
Click to expand...
Click to collapse
So in this case, i can just flash this rom and there is no need of flashing a diffrent vendor or firmware.
So final question: I'm happy with the stock rom plus root. I would like to try a custom rom but I'm not willing to go through the whole installtion procedure again. Is there a way of making a backup and keeping it?
When I backup the stock rom right now, the backup will ne encrypted again...When I formate the data, all my data will be gone again ?