[RECOVERY][grus] KudProject's Unofficial TWRP 3.4.0-0 [28-06-2020]

[Deleted member 8681072]

Stocks rom works good but always when i install twrp i turn on wifi and it turns off by itself

 

[druckis3000]

Booting always into twrp recovery, flashing vbmeta does nothing. Flashing stock rom is the only way to fix this? Or is there any other solution to this problem?

 

[krasCGQ]

Booting always into twrp recovery, flashing vbmeta does nothing. Flashing stock rom is the only way to fix this? Or is there any other solution to this problem?

See the reason in the TWRP console. There might be something related to FBE-related failures.

Sent from my MI 9 SE using XDA Labs

 

[druckis3000]

See the reason in the TWRP console. There might be something related to FBE-related failures.

Sent from my MI 9 SE using XDA Labs

Console? You mean the one that appears after entering password?

Updating partition details
done
enablefilecrypto_failed
Data successfully decrypted
Updating partition details
done

 

[krasCGQ]

Console? You mean the one that appears after entering password?

Indeed.

You need to format data then.
Go and backup any valuable data before doing so.

Sent from my MI 9 SE using XDA Labs

 

[arzuakay]

EFS backup?

Only allow image backups for system and vendor

 

[krasCGQ]

EFS backup?

Not affected.

Sent from my MI 9 SE using XDA Labs

 

[druckis3000]

Indeed.

You need to format data then.
Go and backup any valuable data before doing so.

Sent from my MI 9 SE using XDA Labs

I just reflashed stock rom, but it was strange that without reflashing userdata partition it's still booting into recovery. In OP you are saying that 2 step is optional, thus I didn't do that, was that the reason I got stuck in recovery mode? Or it's something else?

 

[Bygepp]

Hello, I have a big problem, after flashing latest version 3.3.1.0, no password asked and so files remain encrypted. I need to flash a stock ROM because wiped everything, please help.

 

[krasCGQ]

I just reflashed stock rom, but it was strange that without reflashing userdata partition it's still booting into recovery. In OP you are saying that 2 step is optional, thus I didn't do that, was that the reason I got stuck in recovery mode? Or it's something else?

Maybe you accidentally boot image that has newer security patch than current one installed on system, so you ended with upgraded keys that only recovery can decrypt?

Hello, I have a big problem, after flashing latest version 3.3.1.0, no password asked and so files remain encrypted. I need to flash a stock ROM because wiped everything, please help.

> no password asked, files remain encrypted
> need to flash stock because everything is wiped



Sent from my MI 9 SE using XDA Labs

 

[Bygepp]

> no password asked, files remain encrypted
> need to flash stock because everything is wiped



Sent from my MI 9 SE using XDA Labs

Everything except user data, obviously.

Also tried to flash with OTG storage, but failed (error: failed to update vendor image), what happened so? Just wiped system, cache, dalvik and data (not user data).
In any case, solved with flashing fastboot ROM via MiFlash, lost all my data (but I have backup on Gdrive).

 

[mocarela]

ota/blockota update

ATM I'm on MIUI 10.2.2.0 Global with TWRP 3.3.1-2 (+ Magisk 19.3, EdXposed 4.5.1) - everything working perfectly in this respect - and got an update 10.3.3.0 (complete recovery and blockota variants).
I would kindly like to ask you what are my possibilities to perform the update? My main goal is to lose as less as possible of the current configuration.
JFTR... I have adapted /etc/mkshrc to suite my needs and changed /etc/hosts into the symbolic link pointing to /data/hosts. Is this problematic for the blockota way of update?

 

[mocarela]

ATM I'm on MIUI 10.2.2.0 Global with TWRP 3.3.1-2 (+ Magisk 19.3, EdXposed 4.5.1) - everything working perfectly in this respect - and got an update 10.3.3.0 (complete recovery and blockota variants).
I would kindly like to ask you what are my possibilities to perform the update? My main goal is to lose as less as possible of the current configuration.
JFTR... I have adapted /etc/mkshrc to suite my needs and changed /etc/hosts into the symbolic link pointing to /data/hosts. Is this problematic for the blockota way of update?

Nobody has updated after installing TWRP and other stuff? Can't believe it... I probably have asked a stupid question, right?
Searching on the net there are posts stating it's not possible to OTA update with TWRP, others saying only "compatibility.zip" file should be removed from the update package and then it should work.
Can someone at least point me to the right direction since I couldn't find any credible info on this topic, please?

 

[SkubiDoo]

Any idea why I'm having this?

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot: unknown option -- disable-verity

I'm on latest 1.4.3 adb...

EDIT:

Solved with https://forum.xda-developers.com/showpost.php?p=79971216&postcount=105

 

[zepedroj]

You don't get pop up regarding unmodified system partition?

Hello,
I'm not getting the pop up regarding unmodified system partition. I got it the very first time flashing the latest recovery (twrp-3.3.1-3-grus-20190802.img), and I swiped to allow modifications. Booted back to MIUI and TWRP got replaced with the stock recovery. Flashed the same version again, no pop up and got replaced with the stock recovery. Flashed a different, older version (twrp-3.3.1-2-grus-20190609.img) and got the pop up again. Once again, swiped to allow modifications, booted to the system and TWRP got once again replaced with the stock recovery. How can I solve the problem of getting TWRP replaced with the stock recovery?

 

[rcayret]

Hi guys. I installed the laster TWRP and xiaomi.eu rom and the cellphone was encrypted. Some solution to solve it? Thank you.

 

[Lazer Bear]

Hello guys, need a little help. I have a GRUS on stock MIUI EEA 10.3.4, the bootloader's unlocked (did it myself, coming from Chinese MIUI), everything's working fine. The only thing I want is root.

I'm a long time android user, but not so familiar with this whole verity thing, so bear with me. I understand that I cannot have Magisk without TWRP as the whole boot TWRP breaks encryption, so first of all I'm trying to install TWRP. What I've tried is:
-boot into fastboot mode
-flash recovery (I've tried both this version and the one in the other thread, I posted there as well) using Minimal ADB+fastboot 14.3
-reboot into recovery using power+volume up, recovery decrypts successfully (I don't get any prompt to swipe to allow modifications though)
-reboot to fastboot
-flash vbmeta with the disable verity commands

Up to here it works, I can boot into system normally, and if I reboot to recovery it boots into TWRP, provided I disable verity each time after I enter into TWRP.

Then I do this:
-boot into TWRP
-flash magisk
-(optionally, I've tried both doing and not doing this) reboot to fastboot, flash vbmeta
-reboot system

This results in bootloop to TWRP. I cannot boot into the ROM unless I wipe data, but that only fixes until next reboot, so I'm basically stuck.

What am I doing wrong? Should I be using lazyflasher or anything else? I've tried a few variations of the above process, not diasbling verity etc. and clean flashing with Miflasher between every attempt, but I always end up in bootloop to TWRP.

 

[elpaablo]

Same here. All you have to do is flash recovery in fastboot, go to recovery using power and vol up, flash magisk and reboot to system.

 

[krasCGQ]

Hi guys. I installed the laster TWRP and xiaomi.eu rom and the cellphone was encrypted. Some solution to solve it? Thank you.

Not related to TWRP.

Sent from my MI 9 SE using XDA Labs

 

[Hobby-Student]

I did google about this question, but could not get a final answer:

I'm using shelter (work profile) to add some privacy for some apps. Are there any plans that this will be supported by TWRP?
If not, What would I have to do to get a backup via adb (e.g. special mounts, which partitions, dd if=... of=...)?