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

Search This thread

druckis3000

Member
Dec 15, 2017
17
0
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

Senior Member
Apr 14, 2017
237
106
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

Recognized Contributor
Apr 13, 2015
5,433
4,939
20
Kendari
kud.my.id
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

:rolleyes:

Sent from my MI 9 SE using XDA Labs
 

Bygepp

Senior Member
Apr 14, 2017
237
106
> no password asked, files remain encrypted
> need to flash stock because everything is wiped

:rolleyes:

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).
 
Last edited:

mocarela

Senior Member
Jul 16, 2012
57
13
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

Senior Member
Jul 16, 2012
57
13
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?
 

zepedroj

Member
Jul 8, 2018
19
2
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?
 

Lazer Bear

Senior Member
Dec 21, 2011
94
22
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

Senior Member
Nov 18, 2017
291
114
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.
 
Last edited:

Hobby-Student

Member
Oct 11, 2009
23
6
here and there
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=...)?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    https%3A%2F%2Fimg.xda-cdn.com%2FpSvihPyfhapF9LoHqaNVoQ9y7kw%3D%2Fhttp%253A%252F%252Flh3.googleusercontent.com%252F2HtVAF5zfNMlmKhF0QYqCSr1rsstB1btNfdKl7WvGTcZkOSKCYNxdXwsSizx9VhiPg%253Dw300


    This is basically a tl;dr thread.
    I don't want to make a thread that everyone will lazy to read.

    Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Disclaimer
    Code:
    /*
     * Your warranty might not be void (thanks Xiaomi). However...
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this RECOVERY
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    Requirements
    • Xiaomi Mi 9 SE (of course)
    • Unlocked bootloader
    • Some knowledge on how to deal with your device... and patience.

    Flashing Instructions
    I assume you've done (very) basic steps on preparing to flash your device.
    1. Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
    2. Optional: Flash stock vbmeta with the following command (attached if needed):
      Code:
      fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
    3. Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
      Code:
      fastboot flash recovery twrp-3.x.x-y-KudProject-grus.img
      Where x and y are version of TWRP you're going to flash.
    4. IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
    5. Swipe the option to allow modifications. This will prevent stock ROM from replacing recovery, however be aware that you might need to reflash stock vbmeta with disabled verity after that to be able to boot stock ROM!

    Downloads
    Webserver | MEGA
    Old releases only: OSDN | AndroidFileHost

    Known Issues
    • /dev/null

    Special Thanks
    • Dees_Troy and everyone behind TWRP
    • Everyone on Mi 9 SE community

    Device Sources
    13
    Changelogs
    twrp-3.4.0-0-KudProject-grus
    • Merged TWRP source changes up to 22 June 2020 (UTC+8)
    • Supports decryption of userdata on Android 10-based MIUI and custom ROMs using Android 10 crypto blobs (might not be backwards compatible)
    • Restored system and vendor (non-image) backup support
    • Added support for backing up persist (and the image)
    • Build some blobs from source
    • Updated remaining blobs from V11.0.2.0.QFBEUXM
    • Updated prebuilt kernel to latest Pie

    twrp-3.3.1-3-grus-20190802
    • Switched to source-built kernel
    • Updated blobs from MIUI China developer 9.7.4
    • Added support for F2FS in kernel (tell me if decryption breaks on this file system though)
    • Added persist into fstab
    • Added vendor-side touch firmware
    • Get CPU temperature from proper thermal zone
    • Disabled vbmeta checks
    • Only allow image backups for system and vendor
    • Symlinked /system to /system_root/system for backward compatibility
    • Misc stuffs
    • TWRP and f2fs-tools upstream changes

    twrp-3.3.1-2-grus-20190609
    • Fixed wrong USB-OTG mount point

    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.
    3
    Notes
    • Don't use fastboot boot to boot the recovery; it'll proceed to boot system instead using recovery's kernel. If this happens with your current kernel's boot image security patch being older than recovery one, you're basically busted as FBE keys are upgraded the time newer combination of system + vendor + boot image security patches are detected.
      If you're out of luck in this situation, the only way to resolve is to format data (just backup your data to somewhere safe before doing so).
    • If you flash disabled vbmeta, you can't flash stock MIUI zips until the original vbmeta is restored.
    3
    3.4.0-0 is now available. Changelog is on 2nd post and two latest links are no longer updated.

    Enjoy.
    3
    Thanks for the work! Great seeing you here after ZenFone 2 and Redmi Note 4. Hopefully a KudKernel will be in the works(if not already).
    Kinda off-topic, but well rebasing over CAF is a tough job...

    Sent from my Mi 9 SE using XDA Labs
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone