Database Develop

[RECOVERY][OFFICIAL][sagit] TWRP 3.2.2-0 for Xiaomi Mi 6

Team Win Recovery Project
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:
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
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
OR:
You can find more information and download links on our website.
FEATURES:
FBE Decryption support
MTP support
ADB root
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
CONTRIBUTIONS:
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
TWRP for Mi 6, Tool/Utility for the Xiaomi Mi 6
Contributors
TheStrix
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created 2017-06-10
Last Updated 2018-07-07

FAQ
FAQ:
HOW DO I GET LOGS SO WHEN I COMPLAIN I'M NOT COMPLETELY IGNORED OR SHAMED BY OTHER USERS?
To get logs while in TWRP, you should connect your device to your PC and use adb.
adb pull /tmp/recovery.log
adb exec-out dmesg > dmesg.log
This will create 2 files in the directory your shell is currently in, recovery.log and dmesg.log. You will need to upload these somewhere such as a pastebin or Google Drive. You can also attach it to your XDA post (recommended!)
If you are having an operating system boot issue, you should gather a ramoops log instead. Do this while in TWRP after the failed boot:
adb exec-out "tar c /sys/fs/pstore 2>/dev/null" > pstore.tar
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).

Reserved

Nice

Praying for good developers working on Mi6
Thx for TWRP

thanks

Thanks a lot for your work.

Any comparison to ValoXis / cofface version?

Thanks

Thanks a lot for your work!
Can I disable dm-verify with this revovery when using official MIUI rom?

Can not be backed up

.nice thank you !
Maybe lineage is next ? ?

Any reason why it asks me for a password?
Thanks!

Yeah, Parth its here
Now it's time to xiaomi to release kernel sources

Successfully re-flashed from ValoXis version via official TWRP app.
Thanks Strix!

Tried to restore from backup, This is the thing what I backed up :
1. Backup1 : boot, recovery, EFS
2. Backup2 : system, system image, data, cache
I tried to restore from backup2 first from failing the installation of China dev ROM. Wipe system, data, cache, dalvik, and do the backup.
It's booted okay (it uses the custom boot animation I picked), but at the end / near the end of the boot animation, there's low battery sound played, then the device is switched off.
Tried again to wipe everything, restore backup2, then backup1, I got the same "low battery" sound notification.
In the end I had to reflash Xiaomi.eu ROM and start fresh.
So what actually happened there?

Hello, after installing twrp this one does not stay, do you have a solution? thank you

Thanks a lot for your work!

I hope Sagit can get recovery by ZCX
Sent from my Xiaomi Mi 6 using XDA Labs

TWRP 3.1.1-1 release:
Fixes the nandroid backup/restore issue
(Notice: backups made using old recovery builds still won't restore fine)
Other updates
Also for some of you've have been wondering,
MY RECOVERY KEEP GETTING REPLACED WITH STOCK RECOVERY... WHAT KIND OF MAGIC IS THIS?
The file: /system/bin/install-recovery.sh present in stock system is responsible for that.
You can simply stop this from happening by deleting it or renaming it to install-recovery.sh.bak using any root explorer or via TWRP (Advanced -> File Manager).

[RECOVERY] [TREBLE] TWRP 3.3.1-0 with Tissot Manager

Thread template from CosmicDan's thread.
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing and other power-user tools with integrated TWRP-powered submenus that CosmicDan originally called Tissot Manager.
Few months ago, CosmicDan officially decided to leave Tissot development, and his twrp was stuck on 3.2.3. So I decided to update that to 3.3 and convert all the aroma stuff into TWRP-powered menus etc, in order to preserve better future compatibility.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan. It also has some general protips hidden within there, for example the seamless/slot system interactions and nuances, so it's worth reading for anyone who wants to be a master of the Android flashing domain
Features:
TWRP fully Treble-ready based on 3.3.1-0;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
Full USB-OTG support;
Full MTP support;
Optional TWRP Survival function, that works both in hotboot and real recovery;
Optional Active slot install method, selectable right before the zip flash;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Added a Tissot Manager list item under Advanced Menu, totally built-into TWRP itself that allows you to do:
Has the option to shrink Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
Treble-izing will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Adds a "Patches" section with the following current options:
Patch kernel from Enforcing to Permissive and vice versa
More features coming!
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Since this is an early version (still stable), some original features from 3.2.3 are still not available. I'll do my best to constantly add new functions when possible!
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-3.3-withTM-BOOT.zip
Code:
fastboot boot boot-recovery.img
Warning - do not EVER flash this img - hotboot it only.
Flash the TWRP Installer. Any slot, any ROM, any existing Recovery - it doesn't matter - it will be installed to both slot kernels.
Reboot Recovery
Optional - Use the "Advanced > Tissot Manager" option for repartition options and other advanced ROM patches, this time built-in TWRP itself for better compatibility with future versions.
About TWRP survival
Starting from 1.0, TWRP Survival will be able both in hotboot mode 'n real recovery mode. Just tick the checkbox 'n flash!
Download
All downloads (and source code) always at:
https://github.com/Giovix92/twrp_device_xiaomi_tissot/releases
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/Giovix92/android_system_update_engine
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! by CosmicDan for detailed instructions and learning on how to Treble like a pro.
FAQ
Q) After I flash TWRP, I get kicked into a Recovery loop when trying to boot the ROM!
A) This is probably because you have a kernel that does not disable dm-verity. To fix this, flash Magisk.
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes! In fact, this is the easiest way for using stock ROM on Treble repartition. May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM. This may occur while flashing in the active slot.
Q) What "Inject TWRP after install" option does?
A) It's TWRP Survival. If you check that checkbox, then after the installation of your zip file the TWRP will automatically reinstall TWRP into your slot.
Bugs Report
If any bug/problem may occur, feel free to report it here! Explain the problem and attach the recovery log. You can get it by going to Advanced - Copy Log and sliding. Kernel log isn't necessary.
If, for some strange reasons, you are unable to get into that menu', connect your phone to PC, open up CMD (aka command prompt) and type:
Code:
adb pull /tmp/recovery.log
Credits and Thanks
- @CosmicDan for tips, helps and his amazing work on TWRP 3.2.3, which I've taken many things from
- @nicknitewolf for his DT
- @chondoe for always being present in testing and reporting bugs/good news
- @flex1911 for DT stuff
- @mauronofrio for inject twrp function
XDA:DevDB Information
TWRP 3.3.1-0 with Tissot Manager, ROM for the Xiaomi Mi A1
Contributors
Giovix92
Source Code: [url]https://github.com/Giovix92/device_xiaomi_tissot[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-01
Created 2019-10-01
Last Updated 2019-10-01

Reserved
Changelog:
**10-11-2019**
- Fixed error 28 and 13, this led to some issues while doing a clean installation.
- Restored active slot install functionality, now it's fully working.
**18-10-2019**
Version: 2.0 (MAJOR UPDATE)
- Fixed all kind of problems while flashing:
- Error 51, 15, 31, 17, 35 (postinstall)
- Unability to make a clean flash
- Removed changelog section from Tissot Manager
- Added ADB God Mode
- Added missing binary, required in order to let selinux changer work properly
- Now the 2 new checkboxes won't stay checked anymore after any zip install
- Added system remount to r/w after zip flash in order to flash multiple zips in the same recovery session (like ROM + magisk + gapps and then reboot)
- Fixed linker problem that was causing some options in Tissot Manager to fail
- Smoother experience
Older changelogs:
**01-10-2019**
Version: 1.0
- Initial release with Tissot Manager, now powered by TWRP
- Optional TWRP Survival
- Ability to install into same slot
- Ability to repartititon to Treble and vice versa
- More features coming!

Reserved

Great work.
Sent from my Mi A1 using Tapatalk

Thanks ??

Nice. Bro you carried legacy ?

nice work waiting for shrp version of this ??

Noice :good:
Sent from my Mi A1 using XDA Labs

This is an update of TWRP Comic Dan?

manchirua said:
This is an update of TWRP Comic Dan?
Click to expand...
Click to collapse
Read op

Any way to flash it using cosmic dan's twrp? I don't have any pc now

Anikur Rahman said:
Any way to flash it using cosmic dan's twrp? I don't have any pc now
Click to expand...
Click to collapse
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.

Great job dude ?

Awesome work!
Thank you so much for this.

@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?

sdeft said:
@Giovix92
Great Job.
Is there a way to show the current slot status like in CosmicDan's ?
Click to expand...
Click to collapse
You can check current slot from reboot menú.

Where is the survival checkbox??

What is this "inject twrp" does ?

oskrprez said:
Where is the survival checkbox??
Click to expand...
Click to collapse
Anikur Rahman said:
What is this "inject twrp" does ?
Click to expand...
Click to collapse
That's the TWRP survival option

Unipo said:
That's the TWRP survival option
Click to expand...
Click to collapse
So, Isn't it automatically reinstalled like Comic Dan's version?

[TWRP] [RECOVERY] [SM-G530H] [UPDATED] [3.6.1_9-0] [LATEST] TWRP for Samsung Galaxy Grand Prime

[RECOVERY] TWRP 3.6.1_9-0 - TeamWin Recovery Project
For Samsung galaxy grand prime - sm-g530h
Full TeamWin credits are on the TWRP page on the TeamWin website: https://twrp.me/
Introduction:
Team Win Recovery Project or twrp3 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
How/Methods to install
TWRP Install (Requires TWRP 2.8.4 or higher already installed):
Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash.
Odin Install Method (No Root Required):
You will need to download and install Odin on your PC. Once you have Odin installed, download the proper .tar file for your device from the download link above. Power off your device. Turn on your device using the proper key combo to get into download mode and attach the device to your computer via a USB cable. Use the PDA tab or button to browse to and select the tar file that you downloaded and flash the device.
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
dd Install Method (Requires Root):
Download the latest image file (.img) from the download link above. Place it in the root of your /sdcard folder and rename it to twrp.img. Run the following commands via adb shell or a terminal emulator app:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p17
Download
https://twrp.me/samsung/samsunggalaxygrandprime.html
For Odin: Download twrp-3.6.1_9-0-fortuna3g.img.tar
Image file: Download twrp-3.6.1_9-0-fortuna3g.img
OR
Download from the attachments
Status:
Support Status: Current
Maintainer: Carlos Arriaga
Code Name: fortuna3g
Created 2022-03-23
Last Updated 2022-3-23

hello please don't post any bugs here since I am just an outsourcer for your convenience.

twrp-3.6.1_9-0-fortuna3g.img​md5 for twrp-3.6.1_9-0-fortuna3g.img
sha256 for twrp-3.6.1_9-0-fortuna3g.img
PGP Signature twrp-3.6.1_9-0-fortuna3g.img.asc
twrp-3.6.1_9-0-fortuna3g.img.tar​md5 for twrp-3.6.1_9-0-fortuna3g.img.tar
sha256 for twrp-3.6.1_9-0-fortuna3g.img.tar
PGP Signature twrp-3.6.1_9-0-fortuna3g.img.tar.asc

used this 1 img tar file in my fortuna3g, there is random glitch lines not working at all

[HOW TO][SM-G900X] crDroid 7.20+ or LineageOS 18.1+

As you know, you need to upgrade the modem and radio firmware from 6.0.1 Android version to make the latest LineageOS or other ROM to work.
You can't do this for this specific device, SM-G900X (Galaxy S5 Live Demo Unit), as the ODIN will fail to flash the files.
But you can modify the ROM to make it past boot-loop quite easy.
Here's what you need to do in order to make it work:
Install latest TWRP for TWRP for KLTE;
You can do this with both ODIN or direct upgrade using TWRP image inside TWRP;
Boot into the TWRP;
Load a ROM .zip on the device like crDroid;
You can upload to SDCard using USB while on TWRP;
Wipe everything (except Internal SD Card);
Install the ROM;
Check if it boot-loop;
Now you need to fix the ROM, which is quite easy:
Boot back into the TWRP recovery;
Go to: Mount -> System (check);
Go back;
Go to: Advanced -> File Manager;
Navigate to: /system/vendor/lib;
Delete or rename: libsec-ril.gsm.so, libsec-ril.usc.so, libsec-ril.vzw.so;
Reboot and enjoy .

what if those files are not present in vondor/lib folder and still is boot loop
G900X is on snapdragon or exynos?

[GUIDE][Install Treble][Only 9.0] Coolpad-LeEco Cool1

Code:
Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Instructions for installing Treble-firmware Android 9 based on the vendor from 11/12/2019 for EUI markup.​
1. Install Recovery specifying the vendor section.
1.1 Download: "TWRP_VENDOR1".
1.2 We go into our Recovery - Installation - Installing img - Select the downloaded file - Install as Recovery.
1.3 Reboot in Recovery.
2. Installing a patch that changes the markup and creates a Vendor section.
2.1 Downloading: "repart_vendor".
2.2 Install the patch through Recovery - Reboot in Recovery.
2.3 Go to Cleaning - Selective cleaning - everything is selected except Device memory and cleaning.
3. Restore Vendor and Boot.
3.1 Download the "boot_vendor".
3.2 In the archive from the folder BACKUPS\9ba6452 we take the Folder 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d and put it in TWRP\BACKUP\Folder with tricky code\
3.3 Recovery - Select backup 2019-11-12--03-11-24_aosp_c106-userdebug_9_PQ3A190705003_0fd956d - restore - Boot and Vendor must be checked.
4. Select the desired firmware (type ARM64 A (or A only)) in any available place Link Link2
4.1 If the downloaded firmware is in the archive, unpack it to img.
4.2 Installing img - select the downloaded file and install it as System image.
4.3 Reboot in Recovery (May write that the system is not installed, do not pay attention).
4.4 Install the patch "fix_gsi_r1".
4.5 Install Gapps if needed.
4.6 Reboot into the system.
4.7 If there is no sound - put a patch "sound+treble+final".
4.8 If there is no network, reboot into recovery and repeat step 4.4 again.
4.9 If you don't like the color saturation in Gcam - put a patch "video_play6".
• This manual is designed for installation using a PC, if you do not have a computer, download all the files in advance.
• Format data is not necessary, all data will be saved.
• Not all gsi are equally useful and bug-free.
• This instruction is not suitable for installing ported GSIs such as Miui, Flyme, ColorOS, etc.
Patch for rollback, for the 6th markup "restore_6"
The new kernel is based on 11 sources, in an attempt to run 10-11 gsi: "image-new"
10-11 gsi hang on a bootlogo, maybe someone can fix it.
You do everything at your own peril and risk. I am not responsible for bricks.
Source code
Discussion
Big Thanks:
Ampir-nn