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

[scorpionredblack]

Hi, I installed the recovery but I don't know why I installed it and it always came back to me in recovery.

 

[leso60]

Hi guys, i can't boot to system i got this message when trying to Flash stock vbmeta: "fastboot: unrecognised option `--disable-verity'

---------- Post added at 04:55 AM ---------- Previous post was at 04:27 AM ----------

Hi, I installed the recovery but I don't know why I installed it and it always came back to me in recovery.

Same thing to me :crying:

 

[krasCGQ]

Hi, I installed the recovery but I don't know why I installed it and it always came back to me in recovery.

You don't get unmodified system partition pop up during immediate recovery boot?

Hi guys, i can't boot to system i got this message when trying to Flash stock vbmeta: "fastboot: unrecognised option `--disable-verity'

Use latest ADB/fastboot tools from Google.
Package like Minimal ADB or such won't work.

Sent from my Mi 9 SE using XDA Labs

 

[nagyra]

Hi guys, i can't boot to system i got this message when trying to Flash stock vbmeta: "fastboot: unrecognised option `--disable-verity'

---------- Post added at 04:55 AM ---------- Previous post was at 04:27 AM ----------



Same thing to me :crying:

Just run it in normal command line, NOT in power shell! (that fixed to me)

 

[Chillipaste]

Regarding this instruction - how do we reflash stock vbmeta with disabled verity? I don't have a copy of the stock vbmeta

" however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!"

 

[krasCGQ]

Regarding this instruction - how do we reflash stock vbmeta with disabled verity? I don't have a copy of the stock vbmeta

" however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!"

There's a reason why I attached stock vbmeta on the same OP post...

Sent from my Mi 9 SE using XDA Labs

 

[Chillipaste]

Ah, I didn't realise the vbmeta file that was in the optional step was the same file to be used to reflash after installing twrp.

Thanks again.

 

[krasCGQ]

New build is up. Enjoy.

 

[denzel09]

[SIZE=+1]Changelogs[/SIZE]​

twrp-3.3.1-1-grus-20190603

• Updated prebuilt kernel and DTBO from MIUI China developer 9.5.30
• Corrected vendor image flashing
• Support for wiping /vendor
• Support for flashing and backup up (as part of boot) DTBO
• Defined TW_SCREEN_BLANK_ON_BOOT
• (Properly) excluded TWRP app
• Included private recovery configuration

twrp-3.3.1-0-grus-20190531

• Initial build.

Amazing work Dev. Works flawlessy. Will be possible that OTG support will be fixed soon? Thank you :good:

 

[Chillipaste]

There's a reason why I attached stock vbmeta on the same OP post...

Sent from my Mi 9 SE using XDA Labs

Just to be clear - if we need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!

Do we run the following code again? My mi9se is bootlooping to TWRP, despite running the below code. I am using global rom.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

 

[krasCGQ]

Amazing work Dev. Works flawlessy. Will be possible that OTG support will be fixed soon? Thank you :good:

I guess I need to buy a USB-C OTG soon ?

Just to be clear - if we need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!

Do we run the following code again? My mi9se is bootlooping to TWRP, despite running the below code. I am using global rom.
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

After updating MIUI, you need to reflash once again.

Sent from my Mi 9 SE using XDA Labs

 

[MrTheMake]

I have flashed the TWRP image as described and booted right into it. However, after I first exit TWRP, it is replaced with Mi Recovery. What can I do to prevent that?

 

[PeppeCNN]

New build is up. Enjoy.

I tested previous one n worked, but this one, work only flashing via twrp, via fastboot goes in bootloop n doesn't restart to system

 

[krasCGQ]

I have flashed the TWRP image as described and booted right into it. However, after I first exit TWRP, it is replaced with Mi Recovery. What can I do to prevent that?

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

I tested previous one n worked, but this one, work only flashing via twrp, via fastboot goes in bootloop n doesn't restart to system

I'm not sure who's at fault here, as I always test my images before publishing by flashing it with fastboot...

Sent from my Mi 9 SE using XDA Labs

 

[MrTheMake]

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

I get the "Swipe to allow modifications" notification and do so. Afterwards, I just reboot to system but TWRP is replaced the next time I enter recovery mode.

 

[PeppeCNN]

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


I'm not sure who's at fault here, as I always test my images before publishing by flashing it with fastboot...

Sent from my Mi 9 SE using XDA Labs

It surprised me too...i don't know if flashing over LR team recovery can cause this kind of bug...when is a LR recovery in the middle i expect everything:crying:

 

[putti71]

I guess I need to buy a USB-C OTG soon ?


After updating MIUI, you need to reflash once again.

Sent from my Mi 9 SE using XDA Labs

USB-OTG would be great!!

 

[qwek]

nahhh found you again bro, from max pro m1 and then mi 9 se? i think we have same choice.

 

[krasCGQ]

New build with fixed USB-OTG mount point has been pushed. Enjoy.
Thanks to PioFio on Telegram for testing!

 

[dzidexx]

New build with fixed USB-OTG mount point has been pushed. Enjoy.
Thanks to PioFio on Telegram for testing!

You're welcome
Thx,