TWRP recovery για Mi 8 3.2.3.**** Official & Unofficial

Το force encryption disabler το περνάς μόνο αν βάλεις official rom.
Στην xtrv η την xiaomi.eu δεν χρειάζεται.
Σε άλλες custom room αν χρειάζεται θα το αναφέρουν οι δημιουργοί της room.

ανεβηκε το νεο recovery στην πρωτη σελιδα

Ο/H knight666 έγραψε:

Η διαφορά αυτών των δύο αρχείων zip ποια είναι;
Θέλω να πω κάνουν το ίδιο πράγμα αλλά είναι για διαφορετικές συσκευές ή κάνουν διαφορετικά πράγματα και ταιριάζουν σε όλες τις συσκευές;

ΥΓ. Ενημερωτικά πιο πολύ ρωτάω μπας και βοηθήσω και εγώ κάποιον με αυτά που θα μάθω.

Ουσιαστικα ειναι το ιδιο πραγμα.
το ενα ειναι universal
και το αλλο ειναι universal.
Αν θες διαβασε παρακατω τι ακριβως κανουν.

DM-VERITY AND FORCED ENCRYPTION

Implementing dm-verity | Android Open Source Project

What is dm-verity?

Android 4.4 and later supports verified boot through the optional device-mapper-verity (dm-verity) kernel feature, which provides transparent integrity checking of block devices. dm-verity helps prevent persistent rootkits that can hold onto root privileges and compromise devices. This experimental feature helps Android users be sure when booting a device it is in the same state as when it was last used.

Clever malware with root privileges can hide from detection programs and otherwise mask themselves. The rooting software can do this because it is often more privileged than the detectors, enabling the software to "lie" to the detection programs.

The dm-verity feature lets you look at a block device, the underlying storage layer of the file system, and determine if it matches its expected configuration. It does this using a cryptographic hash tree. For every block (typically 4k), there is a SHA256 hash.
Since the hash values are stored in a tree of pages, only the top-level "root" hash must be trusted to verify the rest of the tree. The ability to modify any of the blocks would be equivalent to breaking the cryptographic hash.

If dm-verity enabled on your device then simply you can't modify your system partition. If you do then you will face bootloop. On ramdisk's fstab.qcom there is a "verify" check along with system partition. So if you remove verify from ramdisk then you can bypass dm-verity. Here LazyFlasher script does the job. Its removes the "verify" check from ramdisk while you flash the script.

What is forced encryption?

Forced-encryption on Android is implemented through the kernel, which triggers the encryption process on your complete /data partition, on the first boot.

The idea of forced-encryption hooked up a lot of users, seeing this as a one-more-added step towards security. But when it came to the custom users, like you and me, who like to customize their device (A LOT!), it is not so much useful. In contrary, it creates a barricade, preventing any kind of modifications.

In order to successfully disable forced-encryption and decrypt your phone, you will first need a modified boot.img, that has dm-verity check disabled. By flashing this boot.img (kernel), you will ensure that your storage doesn’t get encrypted all-the-way, during the first boot. Also, it is a pretty high chance that you have your storage encrypted now, so flashing the modified boot alone won’t decrypt your device (Think logically, it just disables FE on first boot, either after you bought the device, or did a factory reset).
In order to decrypt, you will need to format the entire userdata partition on your phone, so that the encryption wears-off instantly.

Here also LazyFlasher script comes handy. It simply disables forced encryption. But still you can encrypt you device manually.

Δεν δημιουργειται προβλημα με κανενα απο τα δυο.
οπως τα ειπες ακριβως για το dm verity!
θα το βρεις και σαν opt dm verity
προσωπικα αυτο προτιμω.
να σαι καλα δεν κανει τπτ.οτι θες ρωτας και αν ξερω σου λεω.

νεο recovery φτιαγμενο απ την αρχη.

recovery-20181218-2012 by Germak mi8 (multilanguage)


changelog

1.cleaned twrp from chinese crap.
2.build from scratch.
3.based on official twrp {teamwin}.
4.proper decrypt data and back it up without trouble!
5.works on android pie and later releases.