Database Info

[ROM][7.1][LineageOS(CM)14.1 and CM13 ][UnOfficial] (Nougat) [tate]

CM13.0 (Marshmallow) unofficial builds for the TATE
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
download:
new: https://www.mediafire.com/folder/u7sb7p10ik7v0/tate
old:https://www.mediafire.com/folder/5a97vbv93k24n/tate
old:https://www.mediafire.com/folder/w9nh7oyabwvww/tate
backup before flash, gapps need for upgrade, don`t flash SuperSU
deep sleep fixed
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
bluetooth lte-version fix: https://forum.xda-developers.com/ki...elp/kindle-fire-hd-8-9-bluetooth-rom-t3315904

Great, now it's time to bring TWRP 3.0.0.0 for better results.

alexander_32 said:
Great, now it's time to bring TWRP 3.0.0.0 for better results.
Click to expand...
Click to collapse
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.

build 20160215 (backup before flash, gaaps need for upgrade): http://www.mediafire.com/download/pj2994j9p358tit/cm-13.0-20160214-UNOFFICIAL-tate.zip

xWolf13 said:
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
Click to expand...
Click to collapse
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).

alexander_32 said:
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
Click to expand...
Click to collapse
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs

monster1612 said:
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you very much :good::good::good:

@transi1 Great rom! Very fluid. Only issue is the lack of deepsleep. Do you have an idea what might be causing it?
Also I flashed the ROM with Twerp 2.7.x.x so Twerp 3.0 is not required (but if you guys build it,i'll still take it )

Thanks for bringing CM13!

hope this rom to be official

build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed

Screenshots please??

transi1 said:
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Click to expand...
Click to collapse
My battery thanks you. From what I can tell, everything that was working in cm12.1 also works in cm13. Along with very aggressive memory killer recommended from OP, I'm also using max cpu freq 1500MHz with performance governor and deadline scheduler with 512kB read-ahead in kernel adiutor and the performance is good. In cm12 I remember several crashes with the same cpu oc but for now it seems stable.

How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk

Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
LOL! Definitely don't flash supersu! Just got my kindle back up from soft bricking it that way.

Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Click to expand...
Click to collapse
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).

r3t3ch said:
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
Click to expand...
Click to collapse
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Sent from my Amazon Tate using Tapatalk

Jrhoop said:
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Click to expand...
Click to collapse
If you can enter fastboot you have nothing to fear. TWRP is the only recovery that is consistently updated and is highly recommended over philz/cwm. Download TWRP 2.8.7.0 and extract the img from the zip.
I've never been a fan of flashing tools from within android. It's much simpler to just go into fastboot and use:
Code:
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img

You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting

Maromi said:
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Click to expand...
Click to collapse
Hey what rom are you running on the KFHD?

[ROM][Official][Nightly] LineageOS 16.0 for OnePlus 3/3T

LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 16.0 builds for OnePlus 3/3T. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Tips:
You need at least OxygenOS 9.0.2 firmware, otherwise you'll get error 7 when installing the zip. Latest firmware is recommended.
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Official TWRP 3.3 or higher is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
......
Download:
Official: https://download.lineageos.org/oneplus3
Last unofficial: https://androidfilehost.com/?fid=1395089523397903569
XDA:DevDB Information
LineageOS, ROM for the OnePlus 3
Contributors
dianlujitao
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2018-11-13
Last Updated 2019-08-12

Reserved
Changelog:
2018.11.13:
Initial release
2018.11.17:
Sync latest source
Fixed directly reboot to recovery when attempting to enter power on password when secure boot enabled
Downgraded kernel to LA.UM.7.5.r1-02500-8x96.0 due to CAF stability regression, but there's still a race condition which could cause random kernel panic, especially when attempting to wake up the device, I'm still debugging on this.
Improved GPS performance
Minor bug fixes
2018.11.29:
Sync latest source
Kernel baseline updated to LA.UM.7.6.r1-03600-89xx.0
Thanks to a clue provided by @markakash , the "random kernel panic on wake up" issue seems to be fixed now. The ROM is probably stable enough for daily use, so I call it "beta" instead of "alpha" now. Please report if you still have the issue.
Minor bug fixes
2018.12.02:
Sync latest source
IMS experiments, VoLTE is confirmed working, VoWiFi is untested
Battery life optimization
Fix fingerprint sensor not respond on first boot and after user switched
Minor bug fixes
2018.12.05:
Sync latest source
SELinux enforcing for now, let me know if there're any regressions
Minor bug fixes
2018.12.15:
Sync latest source
Fix some suspend issue
Kernel baseline updated to LA.UM.7.5.r1-03700-8x96.0
Minor bug fixes
2018.12.22:
Sync latest source
Slider key fix by @nvertigo67
App launch boost & touch boost, hope it helps reduce lagging
2018.12.30:
Sync latest source
Kernel baseline updated to LA.UM.7.5.r1-04000-8x96.0
WiFi display support
Bug fixes & improvements
2019.1.1:
Sync latest source
Various bugs in the last build have been addressed
Working unofficial SU addon: https://androidfilehost.com/?fid=11410963190603887268
Happy New Year & Enjoy!
2019.1.12:
Sync latest source
Add support for always-on-display
Minor bug fixes
2019.1.24:
Sync latest source
Fix touchscreen when gesture disabled
Fix whatsapp and CamScanner camera issue? Not sure, need feedback
Minor bug fixes
2019.2.10:
Sync latest source
Update kernel to LA.UM.7.5.r1-04100-8x96.0
Livedisplay & touchscreen gestures internal API migration
Allow disabling new USB gadgets when the device is locked
Minor bug fixes
2019.3.1:
Sync latest source
Fix weird color after boot? Need your confirmation
Performance optimizations
New offmode charging animation
Minor bug fixes
Note that some features/bugfixes will NOT be included in the upcoming official builds, be aware before switching from unofficial to official.
Future:
https://download.lineageos.org/oneplus3/changes/

Your opinion on migrating to official Pie firmware
dianlujitao said:
As you're aware, OnePlus started Pie closed beta days ago, and there're already leaked builds. I made a new Lineage build with blobs from one OOS9.0 leak, installed and updated firmware. On first boot after fw update, when boot animation was done, unexpectedly, I didn't see my launcher desktop as usual, but an "Decryption unsuccessful" warning telling me that my data was corrupted. Undoubtedly, after rebooting to TWRP it failed to mount /data thus I lost everything on my internal storage.
After several experiments I finally figured out the cause:
If your data is encrypted and bootloader is unlocked, after upgrading to Pie modem firmware, there's 100% chance of your data to become corrupted, and probably no way to restore them. The cause is on firmware side, probably something wrong with key migration, so there's no way for 3rd party developers to fix it. Note that which ROM was in use pre-upgrade doesn't matter at all, i.e., if bootloader was unlocked and you were upgrading from OOS 5.0.8(enforce encryption by default) to OOS 9.0, you'll lose all personal data after reboot from recovery installation. Interestingly, everything works as expected if bootloader was locked.
I couldn't comprehend why do they apply diverse low-level strategies to locked and unlocked bootloader. Arguably this is a bug and should be fixed when they started rolling OTA updates to the public, but it's also possible that this is by design and aims to restrict "unsafe" operations. Regardless, always be careful and backup your data before upgrading firmware in the near future.
Click to expand...
Click to collapse
Unfortunately they still didn't fix the issue in the OxygenOS 9.0 Community Beta released hours ago, in contract their PR claimed "SW team is aware of this issue" during the early closed beta stage. Given the fact the issue persists in both public H2OS and OOS build, I highly doubt if they're actively working on fixing the issue or they'd even gaf. Ofc it's still possible but very unlikely for them to fix it in future builds.
Now I'd like to know your opinion on migrating to Pie firmware. Device owners with encrypted data and unlocked bootloader MUST either backup data or relock bootloader before installing new firmware, others are not affected. Please vote.

Nice
Is it possible to update with a wipe system only ?

good

whats the difference in this build and does this uses 4.4 kernel ?

Playa82 said:
Finally
Is it possible to update with a wipe system only ?
Click to expand...
Click to collapse
Why this question is asked each time ?
You have TWRP right ? So backup your current install, flash without wiping, if it goes wrong, you know you have to clean flash, simple.
Plus, from the O.P of this thread:
O.P said:
Installation:
First time flashing LineageOS 16.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery (Latest official TWRP is highly recommended: https://twrp.me/oneplus/oneplusthree.html)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package
Reboot
Click to expand...
Click to collapse

lol, right when I clean flashed 15.1 and reinstalled everything from too many dirty flashes

karkiankit said:
does this uses 4.4 kernel ?
Click to expand...
Click to collapse
Why don't you check yourself? OP clearly states which kernel is in use:
https://github.com/dianlujitao/android_kernel_oneplus_msm8996/blob/lineage-16.0/Makefile#L1-L3

Nice!.. op3 community love u
Thank you

Weeew the legend is back. Awesome job

hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly

ele95 said:
hi guys, what about these builds https://nyyu.tk/builds i also get ota update nightly
Click to expand...
Click to collapse
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.

Screenshots pls... Anyone??

Encryption still not working
Reboots to recovery right after "enter PIN" shows up

Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
IIRC, we need OnePlus sources from Android Pie for encryption to work correctly.

pjgowtham said:
Tried 9/11/18 build from jenkins. It wouldn't boot. You are welcome to try his latest one though and check if it boots.
Click to expand...
Click to collapse
dirty flash works and bootup fine for me but there is no sim signal so i revert to old one

Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
The same happened to me also. I'm encrypted on f2fs coming from OOS with a clean install.
@dianlujitao could you please add in the OP that it needs to be installed on an unencrypted phone - assuming that the reboot to recovery is caused by booting on an encrypted device.
Sent from my OnePlus3T using XDA Labs

Sometimes when I try to unlock using the fingerprint reader the screen stays black, while the buttons light up. The phone freezes and I need to reboot it. Someone else experienced the same issue?

Racc145 said:
Encryption still not working
Reboots to recovery right after "enter PIN" shows up
Click to expand...
Click to collapse
you knew that going in this, so why write and be supprised?

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Introduction
This is an unofficial build of TWRP for Redmi Note 7 Pro (violet). Differences with the official one include:
- Supports CAF-based wrappedkey encryption (decryption) properly (tested with MIUI 10.3.5.0)
- Supports decrypting devices that have screen lock set up after Android 9 May update, which introduced a new key derivation function.
- Mounts the system partition at /system_root as per AOSP standards. This makes the auto-backup scripts (e.g. GApps / Magisk survival script) work properly during updates, and you no longer need any 'patch' to flash GApps / Magisk properly. However, this may break some existing ROMs. See below FAQ section for details.
- Appended DTBO to the recovery image so it doesn't depend on the dtbo partition. No standalone DTBO image required.
Flashing instructions
- Download and extract the img file
- Reboot to fastboot mode
- fastboot flash recovery whatever_img_file_you_extracted.img
- Reboot and press Volume + to enter recovery
- DO NOT try to run 'fastboot boot recovery.img', it won't work.
- DO NOT flash the fcrypt disabler if you use my recovery. There is no need to do so, and it is possible to mess stuff up if you don't know what you are doing.
- You have to format the data partition if and ONLY IF:
1) You were not encrypted, now going to an encrypted state, or vice-versa OR
2) You were on a ROM other than MIUI that does not support "wrappedkey" (ROMs would often state it supports wrappedkey if it does), now going to a ROM that supports it
Limitations
DO NOT boot this recovery with empty system and vendor partitions. It will fail to decrypt any data partition with empty /system and /vendor. DO NOT wipe system and vendor partitions without installing a new one before rebooting. I am working to remove this limitation.
Now works even with empty system and vendor partitions after 3.3.1-5. No need to worry about formatting system and vendor breaking TWRP any more.
The restore zip created by the Migrate app is NOT compatible with this recovery. It's a problem of the Migrate app, not this recovery. Please DO NOT try to flash the restore zip created by Migrate.
FAQ
- Q: Do I need any specific DTBO image to make this recovery working?
- A: Nope. It is appended to the recovery image so it will work with any DTBO.
- Q: What is wrappedkey?
- A: It's a different mode of FBE implemented in CAF, the Qualcomm branch of AOSP.
- Q: This cannot install ROM X, why?
- A: Because it mounts the system partition at /system_root, which is AOSP standard behavior for A-only system_as_root devices, but is broken in some custom ROMs currently (MIUI should work though). To make any ROM work again, they will need to include this commit from LineageOS Gerrit https://review.lineageos.org/c/LineageOS/android_build/+/247066
- Q: Decryption doesn't work with ROM X, why?
- A: Decryption should work for most ROMs based on the CAF branch (not AOSP). CAF ROMs (including official MIUI) use a different scheme for key storage, which is why TWRP hasn't supported it till now. I have ported the CAF encryption changes (wrappedkey) to TWRP, but unfortunately this will break ROMs that do not support the CAF wrappedkey mode of encryption. Here is a list of patches non-CAF ROMs need to support CAF-encrypted /data partitions https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged). If you confirm your ROM is CAF-based but the decryption still does not work, please open an issue on my GitHub repository which you could find below. (XDA threads are no good for issue tracking, sorry)
- Q: Why not contribute to the official TWRP?
- A: All the patches to the TWRP code base have been submitted to the official gerrit code review, though not merged yet, which you can see below.
Downloads
3.3.1-6: https://mega.nz/#!3QIRQYhK!Jq5QrGfJw5VCYZ8sq_BO1qNZecrFqlM9IB1IdSwogvI
changes: updated kernel to support pstore instead of /proc/last_kmsg. If you don't know what this is, it's probably not relevant to you.
Here you can find an unofficial LOS build with wrappedkey encryption and also proper system_as_root support for those survival scripts https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-lineageos-16-caf-encryption-t3933532. In addition, all official MIUI builds should flash just fine.
History versions:
3.3.1-5: https://mega.nz/#!nMowHKiL!zRvoTM0iIZKArmUDnZzaEFtXQv0_q7hIHUCmTHTOmOM
changes: 1) Now works even with empty /system and /vendor partition 2) Fixed brightness problem; 3) Enabled EDL Reboot
3.3.1-3: https://mega.nz/#!yAYXxAzZ!FNMYLzLphnSmJ-DbBx-OZUgxxYiftgn8e4Jn3kxiQik
Patches and sources
Patches for TWRP are available here:
https://gerrit.omnirom.org/#/c/34091/
https://gerrit.omnirom.org/#/c/34093/
https://gerrit.omnirom.org/#/c/34092/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34096/
Patches for ROMs to support wrapped key have been given in the above sections.
Source of the current device tree for TWRP: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp
Kernel source: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150, note that the device tree uses a prebuilt kernel image.
Contributors
PeterCxy, Dyneteve, merothh
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp

Now fixed and tested with MIUI.

PeterCxy said:
Now fixed and tested with MIUI.
Click to expand...
Click to collapse
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.

I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?

Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?

Can confirm this successfully decrypts storage, running xiaomi.eu on my phone. Thanks for your work.

Dwughjsd said:
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.
Click to expand...
Click to collapse
It did not decrypt MIUI 10.3.5.0 successfully due to magic (I missed some commits from qcom). It was fixed by pulling more commits in.

Jpwner said:
I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?
Click to expand...
Click to collapse
You won't need to erase userdata or flash fcrypt disabler anymore, if all the ROMs will update to support the wrappedkey encryption

Naveenthemi said:
Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?
Click to expand...
Click to collapse
just fastboot flash recovery whatever_you_downloaded_and_extracted.img

PeterCxy said:
just fastboot flash recovery whatever_you_downloaded_and_extracted.img
Click to expand...
Click to collapse
So it's possible for me to flash OTA Updates without encountering a bootloop and such?

Can someone please provide an alternate download link? The Mega link doesn't seem to work for me.
EDIT: Worked on a different device. Thanks.

Naveenthemi said:
So it's possible for me to flash OTA Updates without encountering a bootloop and such?
Click to expand...
Click to collapse
+1
Please answer

Good job! ?
I want you to know that your patch has been merged with the official one. I was away for a while so I hope you understand the little unfortunate delay.

In latest update can we flash any custom roms without any issue?

Yogendra Kher said:
In latest update can we flash any custom roms without any issue?
Click to expand...
Click to collapse
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in

PeterCxy said:
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in
Click to expand...
Click to collapse
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)

Naveenthemi said:
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)
Click to expand...
Click to collapse
Should work fine with MIUI. At least from what I have tested.

kushal.purkar said:
+1
Please answer
Click to expand...
Click to collapse
PeterCxy said it would as far as his testing had been done.

Gapps aroma not installing in this one as well. error 255

Can I flash Magisk and root my phone with this build.?
Do you have any Magisk zip file that will work.?
Thank you for your work

[RECOVERY][grus] KudProject's Unofficial TWRP 3.5.2_9-1 [16-05-2021]

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.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
Optional: Flash stock vbmeta with the following command (attached if needed):
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
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.
IMPORTANT: After flashing, immediately press and hold Power + Volume Up for about 10 seconds to reboot to recovery.
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​
TWRP repository fork
Device tree
Kernel source

Changelogs​twrp-3.5.2_9-1-KudProject-grus
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated kernel to MoeSyndrome kernel based on Android 10
Mount firmware partition as read-only
Added support for formatting Cust partition in GUI
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.

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.

Wrapped key support is added into recovery just for anticipation, although not defined by default in fstab.
I can't test it since EEA device so far is on March ASB as of V10.2.5.0 stable.
Otherwise, basic functionalities including decryption should work.
Edit: grus doesn't have anti rollback enabled at this moment, but Xiaomi may enable it in the future...

it is save changed from wzsx150 twrp ? or must on fastboot ?

bonbibonkers said:
it is save changed from wzsx150 twrp ? or must on fastboot ?
Click to expand...
Click to collapse
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.

ok, gonna test it out , many thanks great work ??

Thanks! working so far so good

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
Working fine when flashing from wzsx150 twrp version.

krasCGQ said:
If already on any version of TWRP, just flash it using Flash Image option to recovery partition.
Click to expand...
Click to collapse
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol

rzki03 said:
i already flash it, worked good. but the CPU Temps is little misreading, i think.... it can go up to 80° C lol
Click to expand...
Click to collapse
Just ignore it. That same CPU temperature glitch also happens on sirius.

Wow, finally an *actual* twrp
Sent from my Mi 9 SE using Tapatalk

krasCGQ said:
Just ignore it. That same CPU temperature glitch also happens on sirius.
Click to expand...
Click to collapse
okay then. thank you!

@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks

denzel09 said:
@krasCGQ
Hey, in next release can you add the option to backup and recover dtbo partion/image like with this recovery https://forum.xda-developers.com/mi-9-se/how-to/recovery-twrp-lr-team-wzsx150-v3-3-0-t3926219 ?
Thanks
Click to expand...
Click to collapse
So this release doesn't have Backup/Restore working?

luisbelmont said:
So this release doesn't have Backup/Restore working?
Click to expand...
Click to collapse
Yes, it has. My request was a bit different.

denzel09 said:
Yes, it has. My request was a bit different.
Click to expand...
Click to collapse
Oh, perfect! Thank you. What advantages does your request have?

luisbelmont said:
Oh, perfect! Thank you. What advantages does your request have?
Click to expand...
Click to collapse
To backup and recover dtbo image before and after flashed this custom kernel: https://forum.xda-developers.com/mi...nel-okitakernel-v1-0-mi-9-se-27-2019-t3934029

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).

puppetminds said:
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).
Click to expand...
Click to collapse
Kinda off-topic, but well rebasing over CAF is a tough job...
Sent from my Mi 9 SE using XDA Labs

[RECOVERY][mido][k4.9] KudProject's Unofficial TWRP 3.5.2_9-1 [21-05-2021]

Notice: This is a dedicated thread for unofficial TWRP builds with msm-4.9 kernel. If you don't know why you're here, you probably want to just stick with whatever recovery you're using right now.
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​
Redmi Note 4(X) (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.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Down button until tinkering Mi Bunny with "FASTBOOT" text appears.
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-mido.img
Where x and y are version of TWRP you're going to flash.
(???) You know the rest.
Downloads
Webserver | MEGA
Known Issues​
You tell me?
Special Thanks​
Dees_Troy and everyone behind TWRP
Acknowledgements for msm-4.9 kernel port: https://kudnet.id/~raw/mido-4.9
Everyone on Redmi Note 4(X) community
Device Sources​
TWRP repository fork
Device tree
Kernel source

Changelogs​twrp-3.5.2_9-1-KudProject-mido
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Updated MoeSyndrome kernel in recovery
Added back Cust partition entry in fstab (umounting it also umounts Vendor partition)
twrp-3.3.1-3-KudProject-mido
Synced with TeamWin's changes up to 25 May 2020 (UTC+8)
Switched f2fs-tools to latest AOSP master
Updated prebuilt kernel to include all fixes and workarounds done in kernel
twrp-3.3.1-2-KudProject-mido
Initial TWRP build with msm-4.9 kernel in preparation for custom ROMs that ship 4.9 kernel
All other builds older than 3.3.1-2 are with msm-3.18 kernel instead.

Notes​
This specific TWRP build is mandatory for flashing ROMs that ship msm-4.9 kernel and target FCM level 3. Any other recoveries (official and a number of TWRP forks) aren't supported nor will be guaranteed a successful flash.
Technical advice (although unrelated to TWRP): Never flash 3.18 kernel on 4.9 ROM or vice versa and hope everything will work. Just... don't.
Verifying released builds​This was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.

And... I'm officially back!

We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??

ShreyYy said:
We can even flash it from TWRP it self ryt?
I really dk if i hv a KudProjects twrp or normal Twrp
But ik that we can just install the recovery from twrp itsepf ryt???
---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------
N btw m on PE plus rom which isnt rooted ...so do i need to root my phn again for flashing the img??
Click to expand...
Click to collapse
You can flash TWRP from TWRP itself just fine, just target right partition. And, you probably want to use 3.3.1-1 instead if you don't plan to flash any 4.9 ROM.
[Spot the device version]
Sent from my MI 9 SE using XDA Labs

It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.

Yes, look at los 16 official from Aryan Kedare, post 1167 with links.

Official TWRP 3.4.0 got released for mido.
Can we use that? Or you have to do your magic first?

speter2 said:
It might be a stupid question but bear with me. Is there any kernels or roms for our phone that use the msm-4.9? Because i been looking but couldn't find any.
Click to expand...
Click to collapse
Evolution x support 4.9

Hi community,
Please, correct me if i'm wrong. If i already have installed a custom recovery, i just have to flash this and reboot to recovery and thats all? Regards.

Any update on 3.4?

lintah_darat said:
Any update on 3.4?
Click to expand...
Click to collapse
Under testing for all 3 devices so far
PS: You'll probably need updated ROMs more than recovery.
Sent from my Redmi Note 4 using XDA Labs

Hello guys, first post here I have installed the last Pixel Experience 11 Stable with the official lastest TWRP 3.4, but in the PE11 official page, they have a link to use this TWRP Custom version.
What should I do now ? Flash the custom and reinstall the PE11 ? Sorry if its a newbie question, but Im still learning about rooting and Custom ROMS. Cheers

Version 3.5.2_9-1 is now available. Release is currently available only via download server due to storage constraints on MEGA mirror. Enjoy!

does it need lazy flasher?

So no one has bothered to point out kudnet.id isn't working and the latest build is not posted on Mega.nz ?
Is this project abandoned?