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.

Can't Flash Any ROM with TWRP

Hi guys.
I had been on RR Oreo for quite a while and as I wasn't happy with battery endurance, I decided to go back to RR Nougat.
Initially, I just downloaded the zip and flashed it on the latest official TWRP 3.2.1.
The phone just bricked.
I then proceeded to flash Stock ZUI Nougat 3.1 with QFIL, flashed TWRP again and tried to flash RR Nougat. No way. Apparently /system was not properly mounting and I just got stuck on "flashing system" steps.
I tried to format data and system partitions, change them to ext2, ext3, f2fs and back on ext4, repaired the filesystem, wiped all /system, /data, /cache and /dalvik and nothing happened.
Actually, after rebooting to recovery, I noticed that I always got the "swipe for modifications menu" and /system could not be mounted. I could only apparently mount system after changing the partition type back and forth. However, it didn't seem to be really mounted in fact as everytime I tried to flash a ROM (being it RR, AEX or even custom-made stock ones), they got stuck and sometimes even bricked my phone again.
I also tried to flash Stock Marshmallow by QFIL to no avail...
This is a very strange issue...
After more than 10 years of flashing custom firmware, this absolutely never happened to me.
Can you be so kind and share some ideas on how to solve this?
Many thanks

Update: my phone is got now hard bricked while using stock marshmallow rom.
Please, can you still help me with the issue I shared above?
I will try to revive my device in the meanwhile.

Update 2: Phone is back on stock after I did a homemade deep flash cable and flashed stock nougat with qfil. Still looking for a way to flash custom roms

Patoilo said:
Update 2: Phone is back on stock after I did a homemade deep flash cable and flashed stock nougat with qfil. Still looking for a way to flash custom roms
Click to expand...
Click to collapse
Try with twrp 3.2.1-0 . Go to twrp /wipe /format dataand type "yes" . It will erase all your data and internal memory . If still get brick you should install zui 1.9.104 by qfil and start all from beginning .

mar.ur said:
Try with twrp 3.2.1-0 . Go to twrp /wipe /format dataand type "yes" . It will erase all your data and internal memory . If still get brick you should install zui 1.9.104 by qfil and start all from beginning .
Click to expand...
Click to collapse
Thanks a lot for the tip, my friend.
I did the formatting of data that you refer, no luck.
Anyway, I would like to try to flash zui 1.9 as I tried so far with 2.1, 2.3, 3.1 and 3.5.
However, all the links I found so far to download the 1.9 are down. Can you let me know where I can download 1.9?
Many thanks

Check here
https://zukfans.eu/community/forums/official-z2pro-zui-rom-releases.13/
Watch out -Zui 1.9.104 will relock bootloader . After that install Zui 3.1.194 bu qfil , then unlock bootloader , install twrp 3.1.1-0 and install non-treble custom rom ( RR 5.8.4 for example )

mar.ur said:
Check here
https://zukfans.eu/community/forums/official-z2pro-zui-rom-releases.13/
Watch out -Zui 1.9.104 will relock bootloader . After that install Zui 3.1.194 bu qfil , then unlock bootloader , install twrp 3.1.1-0 and install non-treble custom rom ( RR 5.8.4 for example )
Click to expand...
Click to collapse
Solved! Dziekuje

Flashing chinese Mi9 issues and getting stuck in bootloop

Hi all,
So over the last day I have decided to install twrp and flash a new rom on my Chinese Mi9. Previously I have locked the bootdoader and installed the global rom. I have adb set up correctly and all relevant PC drivers.
So this is what I did and the problems I encountered. Hoping I can get some feedback as to what may have happened.
1 - Installed TWRP (mauronofrio) then it would get stuck on splash screen. Was told to install TWRP (LR.Team/wzsx150) which I did and it worked. I formatted and wiped my drive to get rid of encryption.
2 - I flashed EU rom (after editing script) using TWRP (wzsx150) then after install it would get stuck in bootloop.
3 - I installed TWRP (mauro) then installed EU rom and success, everything worked well. But I found with this EU rom, most of my apps would not install from play store or my Mi restore would not work, there were apps everywhere. Also EU rom was very buggy flashed it again and still the same issues so decided to go back to global rom. Too many apps would crash for no reason and even clearing cahce/data in app settings would not fix it.
4 - I flashed global rom on TWRP (mauro) and installed fine. But when restarted phone it got stuck in bootloop and couldn't get out of there. Had to use Miflash to flash the rom and start from scratch. I now lost TWRP and got Mi recovery back because of this.
5 - I flashed TWRP (mauro) again and tried global rom once again, flashed magisk etc and once installed rom, the thing got stuck in bootloop again.
6 - I now have flashed TWRP (wzsc150) and have installed global rom and it is installing and restoring fine. Once global rom has installed I have lost TWRP. I am also stuck in bootloop and can't get out.
So basically no TWRP works on my phone.
I have managed to flash phone back to original condition with the global rom. On a positive it still works and the storage is unencrypted.
Does anyone have any ideas or suggestions why my Chinese Mi9 doesn't like TWRP (mauro) and it always gets stuck in bootloop. I just want root access on my phone and google pay to work with unlocked bootloader.
Thank you

This seems to be the theme with 8GB version? I have this version too and makes me worried. I still have about 5 days till unlock insha Allah

These TWRP for Mi 9 are quite beta (no working decryption, no proper backup and restore for example).
If you want to have it, you must use custom rom like EU one.
Stock rom auto re-flashs Mi recovery, period.
BTW, I don't find any unbearable bug the EU rom (most of guys here also have no problem with it), just reinstall the app, backup program such as Titanium backup may introduce a lot of errors...
Sent from my MI 9 using Tapatalk

The apps were fresh installation from Google restore. Even when I deleted them and installed again they still crashed. Gmail, Waze and even checking software version in settings all made it crashed.
So now if I were to install twrp and euro rom again, it shouldn't delete my user data as I no longer need to unencrypt my storage right? Will euro rom just overwrite global rom and keep all my data

ted presley said:
These TWRP for Mi 9 are quite beta (no working decryption, no proper backup and restore for example).
If you want to have it, you must use custom rom like EU one.
Stock rom auto re-flashs Mi recovery, period.
BTW, I don't find any unbearable bug the EU rom (most of guys here also have no problem with it), just reinstall the app, backup program such as Titanium backup may introduce a lot of errors...
Click to expand...
Click to collapse
Do you think when I installed this rom I never did a wipe and all my apps were there on start up. Do you think this might be a cause of certain apps crashing?

Rommco05 said:
...for example I have EEA variant and lastly using Global Dev rom. I still geting regulary updates even when I have TWRP (mauronofrio) and root. Only before every update I need flash stock boot and recovery. Then update phone and then flash back TWRP and Magisk. All the time working my old Magisk + Xposed (Ed) modules working without reinstalling them. Little out of topic here but just wanted to say
Click to expand...
Click to collapse
So with a custom rom like EU rom, everytime there is an update do you have to flash back twrp etc? Do the updates work OTA?

Rommco05 said:
I was talking about official Global Developer rom. To answer your questions. With EU you always need reflash Magisk for sure, if also twrp I don't remember. Yes EU have OTA updates but only full packages and need be flashed over twrp so all bloadware is back.
Click to expand...
Click to collapse
But when you flash back, you don't wipe the cache/data and lose all your stuff do you?

Ok, managed to flash to EU rom with no problems. Works great. Will updating with the updater delete my stuff?

perryano said:
Ok, managed to flash to EU rom with no problems. Works great. Will updating with the updater delete my stuff?
Click to expand...
Click to collapse
It won't.
Sent from my MI 9 using Tapatalk

ted presley said:
It won't.
Sent from my MI 9 using Tapatalk
Click to expand...
Click to collapse
Thank you for all your help with this Ted. It has helped a lot.
So I did the OTA update this morning successfully, but noticed before doing the flash in TWRP, there was a message saying it had to do it that way due to my device been encrypted. That's funny because I have formatted then wiped the drive before installing the rom. Is this a true message?

Always do a full wipe when flashing to a different variant of miui since current twrp has issues on decryption. I also had tons of problems from just resetting only without wiping data. For example flashing to eu from china stable everything worked from just doing factory reset. But google play cannot download any app that has an obb attached for some reason. Most likely problems with file encryption so i did a full wipe now everything works properly.

I'm not able to make TWRP work, its successfully install on terminal and when I reboot and hot volume Up key it bringing me to FASTBOOT mode, and if I do restart system, it and then hold Volume Up key, its again the stock Recovery.
My device is Chinese 8GiB 128GiB. any help will be appreciated. I want to install Xiaomi.eu rom as my current stock Chinese rom with google app giving me horrible battery life, standby battery drain is too bad.

QuakeString said:
I'm not able to make TWRP work, its successfully install on terminal and when I reboot and hot volume Up key it bringing me to FASTBOOT mode, and if I do restart system, it and then hold Volume Up key, its again the stock Recovery.
My device is Chinese 8GiB 128GiB. any help will be appreciated. I want to install Xiaomi.eu rom as my current stock Chinese rom with google app giving me horrible battery life, standby battery drain is too bad.
Click to expand...
Click to collapse
You need to do it quickly.
After successfully installed TWRP in fastboot, hold power button to power off (it will restart instead of completely off), when the screen gone black, very quickly hold the volume up button, hold it until you see the twrp screen.
If you are not quick enough, the phone will boot up and stock recovery will be automatically intstall back, you have to start over: install twrp again.
Sent from my MI 9 using Tapatalk

Error 7 issue after android Q

hello
It's been a while since I wrote anything on XDA, so please be gentle
Let's get the ball rolling.
I have been using MI9 since launch. I bought mine directly at the store in Shanghai, and brought it with me to Europe. After 2 weeks i unlocked the bootloader, and was able to flash TWRP + xiaomi.eu ROM (current beta at that time).
For a couple of months I received OTA updates (all firty flashes), up until introduction of beta android Q (miui 11).
I downloaded the ROM, and flashed, everything worked fine. after some time I had an issue with google pay, so thought of reverting to android Q. I checked, and dirty flash was not recommended option, so I prepared Android P ROM (not sure if exact version is relevant), booted to TWRP (3.3.1.42), wiped the data and tried to flash the ROM (from USB OTG).
Sadly - received error 7, some info about system partition.
I tried reflashing android Q - only to receive the same error.
Stuck at TWRP or fastboot, I used miflash and returned to a global stable.
then I reflashed twrp hoping to remove the error, but had the same error while flashing. Tried to flash from both internal memory, and usb OTG.
returned with miflash to stable, to use the phone..
bootloader is still unlocked, I can flash twrp again, but it will be wiped once I restart the system (as global roms "reflash" recoveries when they boot up).
I looked on some guides how to deal with error 7, but most of them aren't applicable (removing asses lines from config files, as there is no assess line in the ROMs).
Perhaps I am missing some files that I should flash, such as "vendor" files, or something ?
I thought that miflash restores fully to factory state, so TWRP shouldn'[t give any more errors.

There might be something wrong about either the rom, or the twrp.
> Since error 7 is the updater script checking for the phone model, it's either a bad script, or you missed an asserts file when flashing with MiFlash, as even the "factory" roms might not contain all partitions.
> Some partitions can't be seen by Mauronofrio's TWRP, but that shouldn't be a problem tho...
- Try using TWRP 3.3.1-1001 by a chinese team
- Try using the latest 10.10.2019 MIUI11 Rom from xiaomi.eu, I'm using in on an EEA phone and quite satisfied with it

Flashing problem on Chinese version K20 Pro (raphael)

Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks

therightperson_630 said:
Hello there,
I'm using the Xiaomi.eu latest Beta rom ATM. I'm trying to flash other roms (like lineage OS 17.1 for example) but it seems to reboot to fastboot everytime. I've tried doing a clean flash, formatting data, dirty flashing. Nothing seems to help it boot into the new rom.
Clearly I'm doing something wrong. If I try flashing the recommended Chinese vendor firmware (stable version), I get an error 7..but my TWRP is up to date as recommended.
If anyone has any idea where I'm going wrong, that would help a lot.
Thanks
Click to expand...
Click to collapse
Don't know what your doing wrong, but this is my failsafe method should nothing else work.
Flash the latest Chinese 11.0.5 fastboot ROM. Make sure you don't lock the bootloader if using the Mi Flash Tool.
Boot into MIUI once to allow it to finalise the install, you don't need to do the initial phone setup once it boots into MIUI.
Boot into fastboot and install TWRP. I recommend the latest from mauronofrio which should be 3.1.1-32
Boot immediately into TWRP. I use the volume up button while powering up the phone.
Perform a factory reset in TWRP (using the swipe button), then format data (need to type 'yes' to confirm).
Reboot into TWRP using the TWRP boot menu, this ensures the newly formatted data partition is correctly mounted.
Copy over the ROM you want and GApps if needed, then flash.
Boot into your new ROM, everything should be OK. Then boot back into TWRP to install Magisk if you want root.

Yep that seems to have done the trick. At first I was getting frustrated because I thought I was downloading the right Chinese ROM, turns out I was downloading the recovery version instead of the fastboot one.
I think it wasn't working because I was on the beta channel. Switching over to the stable channel meant I had to go through a fastboot flash apparently. I've seen this before on my OP3.
Got lineage OS loaded, thanks for your help!