Xiaomi 14 pro encrypted even after bootloader unlocked


So, im not sure what you're trying to say with the rest of the message. But the reason why the adb push fails is because you put the paths in wrong order. It should be the origin path on you PC as first argument and the destination on phone as second.
 
So, im not sure what you're trying to say with the rest of the message. But the reason why the adb push fails is because you put the paths in wrong order. It should be the origin path on you PC as first argument and the destination on phone as second.
Yes I noticed that. Sorry, I'm a bit rusty. (see my edited post)

And suddenly adb pull works... so I am gonna take a leap: and download ALL the stuff. I feel like I'm not getting ahead, every time I try something its another wall I hit. Even with you help. Again HIGHLY appreciated.

adb pull -a -p /sdcard seems to work now. Will take forever, but at least I can push (DCIM/Pictures/other folders) back after the new install/wipe.
 
For the problem with magisk. You can start sideload mode in twrp, connect the phone to PC and run "adb sideload magisk.apk" or the magisk.zip (the ending doesn't matter, apks are literally just zip files with different name)

Why do you need magisk tho, if you want to reflash anyways?
 
I tried to do that, but i cant get into the folder where I stored it, and the folders that are accessible in twrp, arent accesible in the file managers.
I'm feeling its about permissions. (I heavily edited this post, as I am trying to determine the issues.)

I have magisk manager installed, but now I have to patch it? With what? If I try the Magisk-v29.0.zip file it fails.

The reason I want adb pull to work is to backup my phone files to my mac, so i can restore them later. Or is there a better way?
to push something into internal storage do adb push sdcard
like adb push Magisk-v29.0.zip sdcard/Download
 
For the problem with magisk. You can start sideload mode in twrp, connect the phone to PC and run "adb sideload magisk.apk" or the magisk.zip (the ending doesn't matter, apks are literally just zip files with different name)

Why do you need magisk tho, if you want to reflash anyways?

Why do you need magisk tho, if you want to reflash anyways?
Good question, bc, SwiftBackup seems to require root, for the functions needed, and yes, I about to abort that 'being rooted' idea. BUUUTT i need backups, one way or the other.

!!) trying to backup/migrate Whatsapp with SwiftBackup: (the backup is created, can find it on storage, no issues there, its about the restoring on other device)
- Cloud: Can't use any cloud as it needs the Google account working.
– Local: I can make the back up (phone 1), adb pull/push it to phone 2 (in the right folders): SwiftBackup doesn't see the back up. I guess permission or encryption stuff.
 
Okay,

I have:
- whatsapp via Google Backup, its a month old backup, but better then nothing.
- a full sdcard pull on my Mac (more than I need, but at least I have the folders like DCIM and Pictures)

next step: complete reinstall (aargh).
My wishes:
- stop with the encryption crap
- block ads (I used root/Magisk/Adaway for that, but open for alternatives.)

My question:
How to proceed?? A kick to another topic is okay.
 
I still don't get what kind of encryption you are talking about. What exact problem are you facing at what exact point? I have never used (or even heard of) swiftbackup, I guess this is a huge knowledge gap for this discussion...
(PS.: if you want to adb push/pull from/to any path outside of /sdcard, you need to have the device rooted and allow root access for "shell")

For AdBlock I think AdAway is pretty much as good as it gets for normal users. I'm using it myself (though with ksu instead of magisk but shouldn't make a difference) and never had any serious problems.
 
I still don't get what kind of encryption you are talking about. What exact problem are you facing at what exact point? I have never used (or even heard of) swiftbackup, I guess this is a huge knowledge gap for this discussion...
(PS.: if you want to adb push/pull from/to any path outside of /sdcard, you need to have the device rooted and allow root access for "shell")

For AdBlock I think AdAway is pretty much as good as it gets for normal users. I'm using it myself (though with ksu instead of magisk but shouldn't make a difference) and never had any serious problems.
My 14 Pro, came with EU rom, and 2 partitions and encrypted as well. Major hassle when you want to backup/restore/update...

1) Encryption: when in twrp I can't make backups/restore. I can't acces folders, etc, bc, the system is encrypted. I don't know why Xiaomi decided on this, but it quite common for the 14 (and perhaps other devices.)
2) SwiftBackup was recommended to me by a forum member here, as I needed to be able to make backups, where is twrp was failing due to encryption issues.
3) adb pull/push work without the shell. So yay, I was able to back up images.
4) Ad blockers: I usually have with this addressed with Magisk, which I could not install, bc, .... yay encryption. For the browser, I switched to Vivaldi, which has in-build data/tracker/ad blockers.

My phone worked fine, until I decided to update, bc, ppl saying I should always update. Now I'm 3 weeks in (with a pause) to fix this s**t.
Main problem, I can't log in to my google and/or xiaomi account. Authenticator, text, mail, otp, none work. So without google account working, phone is pretty much, just a phone, no apps, mail, etc.
 
In case youre referring to userspace encryption: That has been a thing for years now on pretty much any android phone. The problem was that the "skkk" beta twrp builds for 14 Series (and some other phones shipped with A14) were not able to decrypt it. This has been fixed with the new release by kyuofox, which is completely stable and working. So you might want to download and flash that new version if you haven't already.

Once again, for magisk you can just adb sideload the app package. Either with PC connection and sideload feature or by selecting the package in twrp and "installing" it.

Also fyi, AdAway has a non-root mode where it utilizes the VPN feature of the phone to launch a local proxy-server where it filters the ad domains. Not as perfect as the root solution, but works 90% of the time.

And i know this question might be annoying but I have to ask again. After those problems with google came up, have you tried running the upgrade script in fastboot?
 
And i know this question might be annoying but I have to ask again. After those problems with google came up, did you try running the upgrade script in fastboot?

No problem! I really appreciate the help!
Actually the upgrade script is what seem to have caused it.

I was in complete bootloop, so I
- ran macos_install_upgrade.sh (via terminal) was recommended by a forum member (used xiaomi.eu_SHENNONG_OS2.0.206.0.VNBCNXM_15)
- then twrp installing (via sideload? not sure).
- securing twrp (to prevent loosing it after reboot)

- Then I have a working phone EXCEPT the ever needed google account, also my Xiaomi account doesnt log in.

Now I'm at the point of clean install/wipe. But now I wanna do it right.
 
new release by kyuofox, which is completely stable and working. So you might want to download and flash that new version

This is EXACTLY what I want.
(I've been stalling, to make sure I have my whatsapp, and my DCIM and Picture folders backupped.)
 
Why do you need magisk tho, if you want to reflash anyways?
Good question, bc, SwiftBackup seems to require root, for the functions needed, and yes, I about to abort that 'being rooted' idea. BUUUTT i need backups, one way or the other.

!!) trying to backup/migrate Whatsapp with SwiftBackup: (the backup is created, can find it on storage, no issues there, its about the restoring on other device)
- Cloud: Can't use any cloud as it needs the Google account working.
– Local: I can make the back up (phone 1), adb pull/push it to phone 2 (in the right folders): SwiftBackup doesn't see the back up. I guess permission or encryption stuff.
You probably need to login into the exact google account the backup was made in
 
Any updates on this? Did u already reflash?
No I was the weekend away, but thanks for asking!

I have 14 Pro (Shennong not Houji) So I guess this stable rom:

xiaomi.eu_SHENNONG_OS2.0.206.0.VNBCNXM_15.zip and
twrp-3.7.1_14_A15-shennong-Kyuofox.img


(My previues phones:
Xiaomi 1 Plus
Xiaomi 4W
Xiaomi 5S
Xiaomi 8
Xiaomi MIX
Xiaomi 10 Pro
Xiaomi 14 Pro)
 
I have 14 Pro (Shennong not Houji) So I guess this stable rom:

xiaomi.eu_SHENNONG_OS2.0.206.0.VNBCNXM_15.zip and
twrp-3.7.1_14_A15-shennong-Kyuofox.img
Exactly. That's also what I'm using right now without issues.
 
Interesting:
Could NOT wipe/format in TWRP, couldn't install rom zip, so I rebooted. And yay, I'm on HyperOs2 (I can't not remember flash/install it, so how is it there?). Also all my files there.

But now I can't use twrp? Bc I cant use: adb/fastboot, so how do I install TWRP now? AND get root access for SwiftBackup?

That phone has an attitude... managed to get into twrp. (ONLY button combo, not via Terminal)

Still can't format/wipe data in twrp ->"Failed to unmount /Data".... Tried that: doesn't work.

GOAL ::
1) HOW do get root access(/shizuku) for SwiftBackup restoring?
or) How do I wipe? Factory reset on the phone?
 
Last edited:
Once again I'm not sure if I'm understanding you correctly.

What did you try to wipe in twrp and why? I thought you wanted to clean flash?

For root, the easiest option is still the same as described before. Pull the magisk.apk file to PC, then enter sideload mode in TWRP, then use adb sideload magisk.zip command on PC. After completed, reboot and open magisk app - you will prob be greeted with an additional setup, just follow the "recommended" steps and reboot.
 
Because in step 1 of this topic it says wipe/format via twrp:


Installing with TWRP:
(TWRP must be installed with Fastboot mode and ZIP signature verification must be disabled)
  • Download Xiaomi.eu ROM zip file
  • Reboot to TWRP
  • If installing for the first time or downgrading: Wipe -> Format Data
  • Copy the ROM zip file to the internal storage
  • Install -> Select the ROM zip file
  • Reboot to system
  • Done!
 
Ah, I forgot that was a thing lol.
Usually when clean flashing, we use Fastboot for that in order to avoid exactly those kinds of problems you've been facing.

Anyways, because you said HyperOS 2.0 is working now (probably cached or something, not sure myself), is gapps working aswell or are there still the same flaws like before?
 
Gapps is working!
But in order to restore the SwiftBackups, I need root/Shizuku?

Waaait....

EDIT 1) I installed Magisk!, Seems te be working, (still without a format data...., still not sure about encryption, that will be my next check.)
I tried to make a twrp back up (only making it) Didn't give any errors, but in Settings > Security & Location > Encryption I can see it's still encrypted.
How will this effect my phone as the rest (see below) seems to be working?

EDIT 2) Restored apps with SwiftBackupp: works with the logins, only permissions need to be (re)set.

EDIT 3) I ran MIUI Backup, for homescreen and layout, that works too! (Only sad thing: the grid of 6 wide I used is not available on HyperOS2.)

EDIT 4) Bank apps, dont work as I expected, yet, next step I'm trying.
 
Last edited:
Sounds good

Your phone will always be encrypted, u can't disable that and it's good that way. What's important is that in TWRP, after entering your screen lock, it shows "user 0 decrypted successfully" in log.

The bank apps could be a bit bigger of a problem.
I'm not too sure what the situation looks like with magisk right now. You can try achieving BASIC_INTEGRITY and play certificate with magisk denylist + PlayIntegrityFix.
If that doesn't work, I think there was another thread on this forum where Integrity fix stuff was discussed - maybe you'll find a solution there.

With kernelsu, the solution is a bit simpler, but the installation is more complicated. If you want to look into that, we should either take the convo to dms or other platform.
 
Last edited:
I have one bank app working, in NL they scan your face for identification: One bank app works fine, the bank other doesn't. Same type of color flashing identification. But that 'color flashing identification - step' has always been a pita. There is an alternative method which I will try. (Identifying with a little device from the bank itself.) My main banking app is working. Most important to me.
"You can try achieving BASIC_INTEGRITY and play certificate with magisk denylist + PlayIntegrityFix."
I dont think I have PlayIntegrityFix installed yet.

(I did hide the banking apps in the deny list, after installing, and only after that, opening the app, but it seems to be stuck on that 'color flashing identification - step'.)
But the majority souns very hopeful to me. Perhaps after completing I can even get Google Wallet to work!

EDIT: I realize i don't have the simcard in my new phone yet, maybe that's a thing??

EDIT 2: What's important is that in TWRP, after entering your screen lock, it shows "user 0 decrypted successfully" in log. <- That shows.
 
Last edited:
  • Like
Reactions: ntlkr