[Recovery][Kenzo/Kate][Unofficial] TWRP-3.1.1 - Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re

[Recovery][Kenzo/Kate][Unofficial] TWRP-3.1.1 - Xiaomi Redmi Note 3 [Snapdragon] ROMs, Kernels, Re

Flashing Instructions:
To install recovery images use Flashify / Rashr / TWRP Manager from Play Store or flash in your current recovery:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
Changes in unofficial version:
MTP support
USB OTG storage support
Hardware Qualcomm-based full-disk encryption support (ext4 & f2fs)
f2fs file system support (read, write, format, backup & restore)
Covers more partitions for nandroid backup (fstab)
ADB root
Full SELinux support
compiled on omnirom-7.1 source
up-to-date with android-7.1 branch
up-to-date device trees
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
removed mouse cursor
There are 2 versions of my Unofficial TWRP available:
* twrp_3.0.3-0_kenzo_16-12-25.img - with precompiled kernel from official twrp kenzo device tree. For kenzo only
* twrp_3.0.3-6_kenzo-inline_17-02-24.img - with kernel compiled from source inline with recovery. For kenzo only
* twrp_3.0.3-7_inline_17-03-04.img - with kernel compiled from source inline with recovery. This recovery is currently the only one supported and suitable for both kenzo and kate variants
Download:
Attention: this recovery is no longer maintained by me and will have no more updates.
TWRP: Unofficial TWRP
fichl's theme pack: [THEME][TWRP] TWRP 3.0.2 dark stock theme pack w different colors v2 [07.03.2016]
Remember to do backup of your current recovery before installing.
XDA:DevDB Information
Unofficial TWRP-3.1.1 for Xiaomi Kenzo/Kate, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
dadi11
Source Code: https://github.com/dadi11/twrp_kenzo
Version Information
Status: No Longer Updated
Created 2016-08-24
Last Updated 2017-07-21

Source:
Device: https://github.com/dadi11/twrp_kenzo
Kernel: https://github.com/TeamHorizon/android_kernel_xiaomi_kenzo
Attention: this recovery is no longer maintained by me and will have no more updates.

That TWRP is better the cofface, the official or yours?

dadi11 said:
TeamWin's TWRP Touch Recovery for Xiaomi Redmi Note 3 Pro - Kenzo.
https://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Screenshots:

Flashing Instructions:
To install recovery images use Flashify / Rashr / TWRP Manager from Play Store or flash in your current recovery:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
Changes in unofficial version:
compiled on omnirom-5.1 source
always up-to-date
updated device tree
fixed AROMA installer
fixed screen brightness
extra languages + Polish by me
permissive selinux
enabled logd/logcat in recovery
enabled fuse exfat, ntfs-3g, jpeg
external storage as default storage
enabled usb-otg support
enabled backup of all partitions
enabled thermal control
crypto/f2fs may work or not..
red theme by @fichl
removed mouse cursor
decreased size by compiling kernel inline
There are 2 versions of my Unofficial TWRP available:
* (kenzo) - with precompiled kernel from official twrp kenzo device tree
* (kenzo-inline) - with kernel compiled inline with recovery. It decreases half of recovery image size, gives some modification options... and needs testing.
Download:
TWRP: Unofficial TWRP
Remember to do backup of your current recovery before installing.
XDA:DevDB Information
Unofficial TWRP-3.0.2-0 for Xiaomi Kenzo, Tool/Utility for the Xiaomi Redmi Note 3
Contributors
dadi11
Source Code: https://github.com/dadi11/twrp_recovery
Version Information
Status: Stable
Created 2016-08-24
Last Updated 2016-08-24
Click to expand...
Click to collapse
Great work mate!
Will it be possible for you to push the commits to the official TWRP, then we can have best of both worlds

Thanks a lot for your work, is it possible to have it in a more dark color?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

@dadi11, Since TWRP 3.0.2-0 is pl.xml already been uploaded so why is your merit? (Such curiosity)
Thanks for the alteration, I just had to run TWRP so by the way check

m4dbra1n said:
Thanks a lot for your work, is it possible to have it in a more dark color?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk
Click to expand...
Click to collapse
check out fichl's or any other twrp themes
Daviteusz said:
GOOGLETRANSLATE: @dadi11, Since TWRP 3.0.2-0 is pl.xml already been uploaded so why is your merit? (Such curiosity)
Thanks for the alteration, I just had to run TWRP so by the way check
Click to expand...
Click to collapse
https://gerrit.omnirom.org/#/c/16935/

No more horrible mouse cursor, thank you.

Could you pls add the option to patch the MIUI boot.img?
Thank you.

abhis3k said:
Great work mate!
Will it be possible for you to push the commits to the official TWRP, then we can have best of both worlds
Click to expand...
Click to collapse
Please refrain from quoting the whole OP thread! It's against the rules.

Great work. I have just the one query. Do we have to flash the boot.img patcher after flashing MIUI or will the recovery take care of that?
And, hearty thanks for your work.

I am on TWRP coffe 3.0.0, Should i upgrade it?
Sent from my Redmi Note 3 using Tapatalk

Is your kernel suppport display the battery for newer device variant?
Sent from my Redmi Note 3 using Tapatalk

qlm2009 said:
Could you pls add the option to patch the MIUI boot.img?
Thank you.
Click to expand...
Click to collapse
ayush3051 said:
Great work. I have just the one query. Do we have to flash the boot.img patcher after flashing MIUI or will the recovery take care of that?
And, hearty thanks for your work.
Click to expand...
Click to collapse
I will look at it later, but as for now it is more like official twrp than cofface one. Would be easier if he has any source or speak english
can you send me a link to this patcher? I am not familiar with miui, cofface twrp or patchers...
kakarotvn said:
I am on TWRP coffe 3.0.0, Should i upgrade it?
Click to expand...
Click to collapse
if you want
khangozzy said:
Is your kernel suppport display the battery for newer device variant?
Click to expand...
Click to collapse
it seems like it doesn't work with prebuilt kernel. try kenzo-inline version if you need battery level in recovery

I confirm that battery level works with inline version, on a kenzo with newer battery controller (the one that many kernels/ROMs have 50%/-2% problem with).
Thank you for this recovery.

cheeze.keyk said:
Please refrain from quoting the whole OP thread! It's against the rules.
Click to expand...
Click to collapse
Ah yes, sorry about that. I did that post in a hurry and didn't notice. Thanks for reminding

dadi11 said:
I will look at it later, but as for now it is more like official twrp than cofface one. Would be easier if he has any source or speak english
can you send me a link to this patcher? I am not familiar with miui, cofface twrp or patchers...
if you want
it seems like it doesn't work with prebuilt kernel. try kenzo-inline version if you need battery level in recovery
Click to expand...
Click to collapse
Thanks, flashed the inline version and battery correctly displays. Good job, bro!
Sent from my Redmi Note 3 using Tapatalk

used the non-inline variant...
mtp and adb doesn't work...

psndna88 said:
used the non-inline variant...
mtp and adb doesn't work...
Click to expand...
Click to collapse
will be fixed in next update. Thanks for reporting

Happy to see u psndna88 on redmi note 3 forum
Sent from my Redmi Note 3 using Tapatalk
---------- Post added at 06:12 PM ---------- Previous post was at 06:12 PM ----------
I have used agni kernel on Samsung Galaxy note 2
Sent from my Redmi Note 3 using Tapatalk

Related

[OFFICIAL]LineageOS 14.1 for ZTE Axon 7

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lineage OS
About Lineage OS:
Lin·e·age
/ˈlinēij/
noun
lineal descent from an ancestor; ancestry or pedigree.
a sequence of species each of which is considered to have evolved from its predecessor.
Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Warning:
This ROM will not work on devices that have not installed the N Bootloader and approriate Modem package below. You must have an unlocked
bootloader as well! Failure to do so could lead to an unrecoverable bricked device.
Instructions:
1. Install the Universal bootloader and your model specific modem.Failure to do so will not allow flashing the ROM!
2. Update recovery [Recommended -> Official TWRP for Axon7
3. Factory reset if coming from another ROM.
4. Install ROM
5. Install GApps (optionally) [Recommended -> Open GApps (arm64) (7.1) 2017-02-01 or Newer
What is CAF?
codeaurora.org
Code Aurora Forum, a Linux Foundation Collaborative Project, is a consortium of companies with projects serving the mobile wireless industry. The projects provide the tested code needed to bring innovative, performance optimized, open source based products to market and also serves as a staging area for code that is submitted to upstream projects such as the kernel and Android. Code Aurora Forum welcomes the participation of projects for multiple architectures. QuIC, as one of the members of Code Aurora Forum, provides support for Qualcomm hardware via the code it contributes to Code Aurora Forum. Code Aurora Forum also mirrors key upstream projects for use by the community.
Sources, Changes, & Wiki:
Source | Changes | Axon 7 Wiki | Lineage OS
Download:
Universal Bootloader and Modem packages for A2017, A2017G, and A2017U
Lineage Official Weekly Builds
Lineage Unofficial Builds
-----------------------------------------------------
XDA:DevDB Information
LineageOS 14.1 for ZTE Axon 7, ROM for the ZTE Axon 7
Contributors
Unjustified Dev, DrakenFX, tdm
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Nougat Bootloader+Modem
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 2017-02-01
Beta Release Date: 2017-02-01
Created 2017-01-27
Last Updated 2017-03-28

Questions and Answers
Q. I hate you and your unstable LineageOS. I want to go back to stock could I?
A. Sure, just make sure to use the full firmware zip from ZTE
Q. I have a Chinese model. Could I install this ROM?
A. No, we don't have access to the updated bootloader and modem. We have added checks to prevent installing on older firmware
A.Yes, ZTE has provided an up to date modem compatible with B15 firmware

Working:
Audio (Distorted on media playback)
GPS
Camera
RIL (Data+Calling+VoLTE)
WI-FI
Bluetooth
Double Tap to Wake
Video Playback
Fingerprint Sensor
Not Working:
Please let me know!

G model coming soon hold off guys until we get proper testing.

.
Q. Lineage comes pre-rooted?
A. NO, Lineage does NOT comes pre-rooted, if you want root privileges/access you need to flash the following SuperSU after flashing Lineage.
[STABLE][2016.12.15] SuperSU v2.79 or [BETA][2017.01.14] SuperSU v2.79 SR3
Or here Lineage Root Binary Flashable zip
Use su arm64 zip file.
----------------------------------------------------------------------------------------------------
Q. Daydream is not working what can I do?
A.
CandyFoxJ said:
I got a private message from a Mr. Fitzie that recommended switching the VR setting under display from reduce blur to reduce flicker and daydream works now.
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------------
Q. I'm receiving SMS or MMS what can I do?
A. This seems to be a current issue with T-Mobile at moment and Disabling VoLTE (Enhanced 4G LTE Mode) under SIM Settings is a temporary fix, till permanent is found.
----------------------------------------------------------------------------------------------------
Q. why can't I modify system?"
A. It seems, System Write Protection is enable, so let's get it fix
Using ADB :
Code:
adb shell reboot disemmcwp
Using your device Terminal :
Code:
su
reboot disemmcwp

What a surprise!!!!! Thanks!!!!!

thanks Guys , my Axon is in the road to me

Nice! Thanks for all the hard work everyone has put in to this!

Confirmed working on the G model. Working on the last few issues and I'll publish the ROM online for everyone.

Unjustified Dev said:
Questions and Answers
Q. I hate you and your unstable LineageOS. I want to go back to stock can I?
A. No, if you attempt to do so you'll be kissing your device goodbye!
Click to expand...
Click to collapse
Ok, so there is no way back. But, why we would be bricking the device if we try to do so? I thought EDL bootstrap would allow to flash the boot and recovery. And using TWRP we could flash the complete 2017U bootstack. Does this mean that LOS 14.1 is modifying the EDL mode? Just curious about this.

Double posty thingy...

Oki said:
Ok, so there is no way back. But, why we would be bricking the device if we try to do so? I thought EDL bootstrap would allow to flash the boot and recovery. And using TWRP we could flash the complete 2017U bootstack. Does this mean that LOS 14.1 is modifying the EDL mode? Just curious about this.
Click to expand...
Click to collapse
Flashing the bootstack from B29 is what will brick you. We are giving you all the updated N stack from N from ZTE. It changes the structure of booting and no zip on XDA and from ZTE will restore the changes it does. Just hold off until I can test downgrading my device.

Why do we need to update Twrp2?

GREAT!
I did not think this would be released until official N was out.
THANKS to all that made this possible.
I don't care if I can down grade If you need a guinea pig.

borijess said:
Why do we need to update Twrp2?
Click to expand...
Click to collapse
You don't have to, but that would be nice so we can make sure everyone is using the same setup to trace down issues.

Ok guys everything is ready. Please let me know if you have issues and make sure to follow the steps and read correctly. The links are up! and if you downloaded a bootstack earlier please delete it and download the new one's for your model. Enjoy!

Unjustified Dev said:
Flashing the bootstack from B29 is what will brick you. We are giving you all the updated N stack from N from ZTE. It changes the structure of booting and no zip on XDA and from ZTE will restore the changes it does. Just hold off until I can test downgrading my device.
Click to expand...
Click to collapse
I understand that your kernel requires that new bootstack in order to boot properly. The previous unofficial alpha version of LOS 14.1 was able to boot using the current B29 bootstack. However that old version had many non functional features.

Hey so wat if I have a TWRP backup of my stock Os.....Can I restore to that if this doesn't work out??
Sent from my ZTE A2017U using Tapatalk

Iancort said:
Hey so wat if I have a TWRP backup of my stock Os.....Can I restore to that if this doesn't work out??
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
No. Read the topic, it's only 2 pages.

xtermmin said:
No. Read the topic, it's only 2 pages.
Click to expand...
Click to collapse
Hmmmm no finger print scanner and no way to go back....It's a tricky situation but with the delay by ZTE leave me no choice... Anyways rooting is possible using TWRP?? Or is it pre rooted?
Sent from my ZTE A2017U using Tapatalk

[UB][RECOVERY] TWRP v3.2.2 for Xperia Tablet Z [POLLUX/POLLUX_WINDY]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING!
TWRP builds version 3.2.1-0 and higher are not compatible with Android Lollipop (5.0/5.1.1) due to SELinux rejection
OFFICIAL DOWNLOADS FOR POLLUX/POLLUX_WINDY :
https://dl.twrp.me/pollux/ ,
https://dl.twrp.me/pollux_windy/
twrp-3.x.x-x-pollux.img , twrp-3.x.x-x-pollux_windy.img : Official TWRP image
How to install : All informations available on TWRP.me
DEVELOPMENT DOWNLOADS FOR POLLUX/POLLUX_WINDY :
https://www.androidfilehost.com/?w=files&flid=202356
twrp-3.2.x-x-pollux.zip , twrp-3.2.x-x-pollux_windy.zip : Flashable TWRP 3 to FOTA installer
twrp-3.2.x-x-pollux.img , twrp-3.2.x-x-pollux_windy.img : Fastboot bootable TWRP 3 image
cleaner-fota.zip : Flashable FOTA formatter (optional)
HOW TO INSTALL EASILY TO FOTA :
* (Optional) : Download the TWRP bootimage and flash it to boot
fastboot flash boot twrpfilename.img
* Boot to recovery : Enter the Recovery as usual
* Flash to FOTA : Install the TWRP FOTA zip
* (Optional) : Flash the ROM you want
HOW TO INSTALL MANUALLY TO FOTA :
* Bootimage : Download the TWRP bootimage you want to flash
* File storage : Adapt the path and push the file to the device this way :
Code:
adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img
* Flash : Extract the TWRP image to the FOTA partition
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
* Reboot to recovery : adb reboot recovery
ADDITIONAL LINKS :
* Easy ADB and Fastboot for unexperienced users :
https://forum.xda-developers.com/showthread.php?p=48915118
Thanks to the TWRP Team
Current local manifest of the TWRP build
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/fusion3-common/twrp_development_sony -->

Oreo needs TWRP 3.2.x.x.
Does the appearance of this thread mean that there are ongoing work on Oreo for Tablet Z?

ze7zez said:
Oreo needs TWRP 3.2.x.x.
Does the appearance of this thread mean that there are ongoing work on Oreo for Tablet Z?
Click to expand...
Click to collapse
Yes, we are working on android 8.1.0 for all fusion3 devices

For me links are dead. Here i found it
https://androidfilehost.com/?fid=673791459329066468
Anyone installed 3.2.1.0 on windy ? Is it OK ?
Sent from my [device_name] using XDA-Developers Legacy app

phillipssat said:
For me links are dead. Here i found it
https://androidfilehost.com/?fid=673791459329066468
Anyone installed 3.2.1.0 on windy ? Is it OK ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
To me it works pretty well, don't see any difference. Running now the unofficial OREO LineageOS.

Does anyone know why original links are dead ? Any problems with the 3.2.1.0 at link from first post ?
Sent from my [device_name] using XDA-Developers Legacy app

Thank you Very much for your efforts for this device! Great!!!

phillipssat said:
Does anyone know why original links are dead ? Any problems with the 3.2.1.0 at link from first post ?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
All the download links work, I checked them.

@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support? I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature) from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.

ripee said:
@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support? I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature) from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.
Click to expand...
Click to collapse
Yes, I plan to do it this week. I think that our device trees are cleaner and more relevant for this -
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux_windy

CyberWalkMaN said:
Yes, I plan to do it this week. I think that our device trees are cleaner and more relevant for this -
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux
https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux_windy
Click to expand...
Click to collapse
Great! Hey, whatever works best is what's most important

Please test first official builds:
pollux - http://build.twrp.me/twrp-3.2.1-0-pollux.img
pollux_windy - http://build.twrp.me/twrp-3.2.1-0-pollux_windy.img

CyberWalkMaN said:
Please test first official builds:
Click to expand...
Click to collapse
What is a difference between unofficial and official builds?

ripee said:
@CyberWalkMaN, are you planning on eventually submitting your 3.2.1-0 builds for official support?
I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature)
from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.
Click to expand...
Click to collapse
Is already out of date?
I do not see any TWRPs for pollux*

Rootk1t said:
What is a difference between unofficial and official builds?
Click to expand...
Click to collapse
Before official builds come out, TeamWin runs official preview builds to make sure that the images their Jenkins builder churns out are actually functional and true to the code submitted by the developer, relative to the developer's own unofficial builds.
Once everything is confirmed to be working the same as unofficial builds, TeamWin runs the actual official builds, which get linked on their site and made available on the official TWRP app. Official support also ensures that future version of TWRP will be attempted to be built using existing repos without the need for the developer's further input unless and until the source repo become too outdated, at which point a new branch would need to be created with code that follows a more recent android API.

ze7zez said:
Is already out of date?
I do not see any TWRPs for pollux*
Click to expand...
Click to collapse
TWRP for pollux/pollux_windy is now officially maintained by me -
https://twrp.me/sony/sonyxperiatabletzlte.html (pollux),
https://twrp.me/sony/sonyxperiatabletzwifi.html (pollux_windy)

There must be something wrong with my pollux_windy. :crying:
Flashing v3.2.1.0 causes a TWRP boot looping.
The only way to boot LineageOS 14.1 was flashing again TWRP-3.1.1-pollux-FOTA-20170928.zip from CaHbKaUp.
Any idea what's going on?
BTW, thanks for updating TWRP! :good:
Edit:
Finally solved the problem.
Downloaded TWRP 3.2.1.0 from official page and I've followed the dd Install Method even though my tablet is not rooted (su command wasn't recognized -su: not found- but dd worked in TWRP Terminal).

Help-as written I cant flash this twrp on 5.1.1 right so i hve to downgrade it to 4.2.2 and then flash it
Can I flash it with Flashtool?
What is FOTA?? Can I flash it from Flashtool if yes then how

Hi,
any version for TWRP 3.2.2-0 ???
Thx

djibe89 said:
Hi,
any version for TWRP 3.2.2-0 ???
Thx
Click to expand...
Click to collapse
images are available on official site.

[RECOVERY][OFFICIAL][oxygen] TWRP 3.2.1-0 for Xiaomi Mi Max 2

Team Win Recovery Project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WHAT IS TWRP ?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD:
TWRP 3.2.1-0 for Mi Max 2
HOW TO INSTALL ?:
1) Be sure you have unlocked bootloader.
2) Download image file.
3) Reboot to fastboot.
4) Install using "fastboot flash recovery twrp-3.2.1-0-oxygen.img" command.
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Mi Max 2 Official TWRP Recovery, Tool/Utility for the Xiaomi Mi Max 2
Contributors
ataberkozen
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2018-04-23
Last Updated 2018-04-23

ah great i was actually waiting for an official thread from the maintainer himself adding this to the index as we speak

Wow! An official recovery! Thank you for the support!

Thank you so much:laugh:

Tested.
Flashed XENONHD ROM yesterday with gapps magisk etc...
Works great as TWRP usual

Thank you!

Im suprised .. my day is made.
Official twrp ..
Hope red wolf recovery also will get official support too

Wow starts 10 times faster now thank you looking forward to hiding them navigation buttons soon.

Finally official! :victory:

Does it have aroma support?

Tempete said:
Does it have aroma support?
Click to expand...
Click to collapse
Yes.

I really fcked up and installed updated version of TWRP (3.2.3.0 i think) on boot partition, and now phone boots only to TWRP.
Any help on this matter?

denis022 said:
I really fcked up and installed updated version of TWRP (3.2.3.0 i think) on boot partition, and now phone boots only to TWRP.
Any help on this matter?
Click to expand...
Click to collapse
tell us what rom u have installed, then extract boot image from that rom, transfer to phone in twrp via adb bridge and flash it to boot partition. or ask another user with same rom to provide boot image for you.
Sent from my Xiaomi Mi Max 2 (Oxygen) using Tapatalk

jbmc83 said:
tell us what rom u have installed, then extract boot image from that rom, transfer to phone in twrp via adb bridge and flash it to boot partition. or ask another user with same rom to provide boot image for you.
Click to expand...
Click to collapse
Now my tree is very stable but issue is ROM sources ..many times sources have soo many bugs and it's us who need to fix for these issue.
The night light, APN, FP..these were all ROM sources ISSUES which I have fixed in all rooms..by editing ROM sources..there is no symmetry in ROM sources which we sync..
So other devs whoever wants to build ROM will have tough time fixing those glitches..I know myself how I suffered lol and finally only in call volume ADJUSTMENT (PATHETIC OREO SOURCE) and led left.
ROM ORIGNAL SOURCES ARE NOT STABLE ENOUGH..AND THEY DO NOT SYNC UP WITH EACH OTHER.

Hard_Rock83 said:
Now my tree is very stable but issue is ROM sources ..many times sources have soo many bugs and it's us who need to fix for these issue.
The night light, APN, FP..these were all ROM sources ISSUES which I have fixed in all rooms..by editing ROM sources..there is no symmetry in ROM sources which we sync..
So other devs whoever wants to build ROM will have tough time fixing those glitches..I know myself how I suffered lol and finally only in call volume ADJUSTMENT (PATHETIC OREO SOURCE) and led left.
ROM ORIGNAL SOURCES ARE NOT STABLE ENOUGH..AND THEY DO NOT SYNC UP WITH EACH OTHER.
Click to expand...
Click to collapse
hey buddy, u sure uve quoted the correct post?

jbmc83 said:
hey buddy, u sure uve quoted the correct post?
Click to expand...
Click to collapse
Oops..i messed up..i was quoting inside lineage 14..as far as i remembered..but sorry for mess

Hard_Rock83 said:
Oops..i messed up..i was quoting inside lineage 14..as far as i remembered..but sorry for mess
Click to expand...
Click to collapse
haha no harm done. take it easy my man

jbmc83 said:
tell us what rom u have installed, then extract boot image from that rom, transfer to phone in twrp via adb bridge and flash it to boot partition. or ask another user with same rom to provide boot image for you.
Sent from my Xiaomi Mi Max 2 (Oxygen) using Tapatalk
Click to expand...
Click to collapse
Since I had rom img on internall storage, I just flashed rom again, and phone booted normally. I dont know is this proper solution for this kind of problem, but it worked for me :good:

Thanks Mac bro

Link Download OFF

[OFFICIAL][v.2.9.0] PitchBlack Recovery Project [lv517, MP260, TP260][32/64bit]

Pitchblack recovery project
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* We're 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.
*
*/
PitchBlack is a TWRP based on TWRP 3.2.3 developed by Reza Adi, maintained by Manjot Sidhu and Mohd Faraz and themed by FireWolf.
For devices (OFFICIAL) : https://sourceforge.net/projects/pitchblack-twrp/files/
Authors build : @Reza_adi, Mohd Faraz
Developers : @Reza_adi, Mohd Faraz
Thanks : @Reza_adi P - Indonesia (Owner / Lead Developer PBRP), George Pasakalis (G.M.L) - Greece (UI Developer), FirewolfXDA - Bangladesh (UI Developer), Manjot Sidhu - India (Source Maintained), Mohd Faraz - India (Co-Lead Developer, Source Maintained), Arbaz Khan - India (Source Maintained), PitchBlack Recovery, @ATG Droid & @dadi11 (Redwolf Developer) for MIUI OTA Support, @arra_quen for Helping and Uploading @faizhifzhan for layout to sourceforge, All Maintainer and User PBRP.
DOWNLOAD :
Recovery zip
BUGS:
When booted while charging, battery level shows 0%.
If you find any other bugs please let me know and i'll try to address them or update this section of the thread to let the bug be publicly known.
F2FS filesystem format is limited to 4GB for some reason so don't use it for /data ( I currently use /cache and /system as f2fs instead of EXT4 with no issues )
INSTALLATIONS :
Flash Zip file as if it were a ROM in TWRP, or you can flash the Recovery.img as you would TWRP (adb commands, apps such as flashify, kernel auditor/mtweaks, terminal dd commands, or using TWRP under Install > install image > recovery )
If using installing the Zip file through TWRP or other custom recovery, it will reboot automatically to recovery. If using the recovery.img method, reboot into recovery as you normally would.
Enjoy
XDA:DevDB Information
PitchBlack Recovery Project, Tool/Utility for the LG K20 Plus
Contributors
Travisholt92,
Deadman96385 (helped to provide bandwidth and the Q6 Stock Oreo kernel which my Oreo+ builds and this project utilize)
Source Code: [url]https://github.com/PitchBlack-Recovery[/URL]
Version Information
Status: Official
Current Version: 2.9.0
Release Date: 2019-02-05
Created 2019-02-03
Last Updated 2019-02-07

My to do list for tonight, update the Fstab to properly support F2FS filesystem format and address the filesystem error.
I should have a new official build up tonight.

I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.

kieffey said:
I must say this recovery is ? % awesome. I like the extra features that include the options to install/uninstall SuperSU and/or magisk and various more. I think twrp has met it's match.
Click to expand...
Click to collapse
And that's why I went for Official PBRP before official TWRP, to get people to at least give it a try. Its based on the latest TWRP so it has all of the features TWRP users love with quite a few extras.

will this work on stock rom

chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It should, I haven't tested. The only reason to stay on stock is VoLTE.

chacon16 said:
will this work on stock rom
Click to expand...
Click to collapse
It works fine in stock. It works with every flavor of ROM out for the K20 Plus.
Sent from my LG K20 Plus using XDA Labs

New build up today that addresses the issue with rebooting to recovery from within recovery.

Screenshots

ROMs?
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?

CrookedYoungHeretic said:
I read earlier that "every flavor of K20 Plus" will work with PB, so I just want to make sure I am 100% clear and sure I understand before I **** up (another) phone...
I am using a Rooted LG K20 Plus with the Resurrection Remix OS ROM and Pitch Black recovery. The only problem is that my phone has no audio function. Mic, and Speakers are nonfunctional. It won't play videos, make or receive calls, play music, or even the background sound on Games. It is my understanding that this is a common bug with Resurrection Remix ROM, so I'd like to just put a new OS. I just need to know if any OS will work as long as its compatible with the K8+ or if it has to be tailored/compatible for PB as well?
Click to expand...
Click to collapse
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device

Travisholt92 said:
This phone is not compatible with k8 at all. I released lineage 15.1 and it is currently the only stable Oreo rom for this device
Click to expand...
Click to collapse
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you

leave your /system partition formatted as ext4
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.

dode417 said:
Flashing this ROM uses block-based patching; instead of copying the necessary files to the filesystem, it copies blocks to the disk. These blocks are data representations of files as they were expressed on the filesystem they originate from, thus copying blocks from an ext4 filesystem to any other filesystem will corrupt it.
Since this is my first post I cannot post the pictures I took of PBRPs output after flashing the ROM to both f2fs and ext4 filesystems and then running e2fsck. On f2fs, the partition is recognized as ext4 after the flash, and e2fsck.f2fs fails as the partition is corrupt beyond repair. On ext4, e2fsck executes as expected. You can also search "block-based OTAs" to find the entry on the AOSP website for more information.
Click to expand...
Click to collapse
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.

CrookedYoungHeretic said:
Whoopee, where it says K8+ on my post is a typo, idk why but my boyfriend was under the impression initially that this K20+ was a K8, I still get confused and mixed up, especially since I also tinker with an LG K4 Rebel lol. But the phone I am using/inquiering about is indeed the LG K20+.
P. S do you have any input/suggestions/advice about the Resurrection ROM 8I can just 7 send 8tnti you
Click to expand...
Click to collapse
RR 8.1 was a total flop. I built it once and it had so many ROM source related bugs from no longer being supported by the RR team that i just gave up on it. More or a variety of ROMs will come after i get pie working.

Travisholt92 said:
Only /cache and /system will currently work with F2FS which needs to be formatted that way before install and only my Lineage 15.1 supports f2fs filesystem format. I have tested and confirmed it works at the time of implementation. Formatting /data as F2FS limits the partition to 4GB for some reason i have yet to figure out. I hope this bit of information helps.
Click to expand...
Click to collapse
I'm not saying it doesn't boot, only informing everyone that the f2fs partition is corrupted by the flashing process and cannot be repaired with fsck. I'm honestly not sure of the total effect of this, but those who are cautious may be thankful for this information.

I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1

SomeDooD123 said:
I can flash the recovery.img for PBRP after doing bootloader unlock via fastboot correct? I don't need to flash TWRP and do all the flashing steps under "How to Disable encryption and flash super su [Install Root]" in the TWRP v3 thread to get PBRP and Magisk on my device? Eventually plan on putting LOS 15.1
Click to expand...
Click to collapse
That is correct, you can use PBRP for those steps.

@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?

chugs said:
@Travisholt92 I am trying to flash PBRP and i can only find the .zips linked above. I have tried flashing the .zips in TWRP 3.2.1 . I am failed with "Invalid zip file format" . What am i doing wrong?
Click to expand...
Click to collapse
You have to unzip the file and fastboot flash recovery.IMG or install the image through twrp under install image

[CLOSED][UNOFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Samsung M21 | SM-M215F |

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1. Download twrp tar file
2. Boot in to download mode
3. Open Odin
4. Select Ap
5. Select twrp.tar file
6. Click on flash
7. Immediately press volume up and power button to boot in to twrp other wise it boots in to system or whenever you wanted to boot in to twrp just switch off and just press volume up and power button that's it
bugs
- All works but Decryption :cyclops:
Main features
- Super partition support
Special Credits
- TWRP team for source code
- Omni team for base sources
- A51 developers for the support
- @ianmacd for his amazing a51 source code as reference thanks mate :highfive::fingers-crossed::good:
- Samsung for kernel source code
- Google source for tools
Download Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for Samsung M21
Contributors
Raghu varma & ianmacd
Source Code: https://github.com/RaghuVarma331/android_device_samsung_m21-TWRP.git
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2020-11-03
Created 2020-11-03
Last Updated 2020-11-03

I request to xda moderators and forum admins to move my thread to Samsung galaxy M21 xda forum. Whenever it is available
Thank you
@TNSMANI
 @Logix
 @Macusercom
 @mrjuniork
 @apophis9283

Raghu varma said:
I request to xda moderators and forum admins to move my thread to Samsung galaxy M21 xda forum. Whenever it is available
Thank you
@TNSMANI
@Logix
@Macusercom
@mrjuniork
@apophis9283
Click to expand...
Click to collapse
Will do as and when the forum is created.

I really hope that the forum will be created quickly. And very many thanks for creating TWRP for M21. Hats off to you sir.

excellent work!!

Oh amazing, how's knox looking on M21? Does the Private Mode on Samsung Browser work after installing TWRP?

Good work dev. Anyone tried this recovery on their Galaxy M21 ?

Looks nice.
What about bootloadet unlock? And how to revert to stock recovery?

required key not available (Backup)
Hi,
when trying to backup my device thru twrp i get the "key not available" error.
E:failed to read default fstab
Updating ....
....
...
Can not create '/data/media/0/TWRP' folder (Required
key not available).
Failed to make backup folder
Any suggestions what to do?
many thanks

mudshark1309 said:
Hi,
when trying to backup my device thru twrp i get the "key not available" error.
E:failed to read default fstab
Updating ....
....
...
Can not create '/data/media/0/TWRP' folder (Required
key not available).
Failed to make backup folder
Any suggestions what to do?
many thanks
Click to expand...
Click to collapse
Did TWRP shows you a pattern to unlock your storage when you booted in it (that is the key to unlock storage)? if not then you are pretty much unable to do any operation that require reading or writing to your storage. It could be something else though.

Raghu varma said:
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
1. Download twrp tar file
2. Boot in to download mode
3. Open Odin
4. Select Ap
5. Select twrp.tar file
6. Click on flash
7. Immediately press volume up and power button to boot in to twrp other wise it boots in to system or whenever you wanted to boot in to twrp just switch off and just press volume up and power button that's it
bugs
- All works but Decryption :cyclops:
Main features
- Super partition support
Special Credits
- TWRP team for source code
- Omni team for base sources
- A51 developers for the support
- @ianmacd for his amazing a51 source code as reference thanks mate :highfive::fingers-crossed::good:
- Samsung for kernel source code
- Google source for tools
Download Twrp-3.4.0-0 From Here
XDA:DevDB Information
TWRP 3.4.0-0 , for Samsung M21
Contributors
Raghu varma & ianmacd
Source Code: https://github.com/RaghuVarma331/android_device_samsung_m21-TWRP.git
My build script https://github.com/RaghuVarma331/scripts
Version Information
Status: Stable
Current Stable Version: 3.x
Stable Release Date 2020-11-03
Created 2020-11-03
Last Updated 2020-11-03
Click to expand...
Click to collapse
thx for the effort
but there's no wipe 'system' partition and flash img in system partition,instead there's only boot,recovery and super(even vendor)but no system img.....help pls...............

Clutchmaster_OP said:
thx for the effort
but there's no wipe 'system' partition and flash img in system partition,instead there's only boot,recovery and super(even vendor)but no system img.....help pls...............
Click to expand...
Click to collapse
after android 10 dynamic partition introduced https://www.google.com/url?sa=t&sou...FjABegQIBRAS&usg=AOvVaw3d_ME4R5wSSov70bfn9wUt

Sagarking said:
after android 10 dynamic partition introduced https://www.google.com/url?sa=t&sou...FjABegQIBRAS&usg=AOvVaw3d_ME4R5wSSov70bfn9wUt
Click to expand...
Click to collapse
so what should i do bro??

Working fine...... thanks

Changelog Thu Feb 11 07:16:39 UTC 2021
==================================
* Initial android 11.0 Support
* Fixed MTP

Raghu varma said:
Changelog Thu Feb 11 07:16:39 UTC 2021
==================================
* Initial android 11.0 Support
* Fixed MTP
Click to expand...
Click to collapse
Hi mate,
what dies Initial Support mean?
Is it worth a try?
Same procedure was mentioned above?
Thanx,
Jürgen

Sir is it safe to flash with bugjaegar app in samsung m21
Pls somebody help me

Can u please mention, for which codename is it for? m21nsxx or m21nnxx??

ShadowMC74260 said:
Can u please mention, for which codename is it for? m21nsxx or m21nnxx??
Click to expand...
Click to collapse
Pls don't listen to OldNoobOne, hes wrong. Odin tarfile won't care as long as u use patcheD odin. So all nsxx should work on nnxx. Even if it doesn't boot you can just hard reboot and reflash working.

Thread closed on request of OP @Raghu varma

Database Develop

welcome