Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 8T
Installation:
# To temporarily boot it
fastboot boot <twrp_file_name>.img
# Since 8T/9R has a separate recovery partition, you can flash the recovery with
fastboot flash recovery <twrp_file_name>.img
Updating to a newer build:
Simply flash the latest TWRP installer zip from TWRP
OR
Flash the img from TWRP/fastboot
FAQ/Know Bugs are given in post #2
Send me a beer, if you think I deserve it: PayPal
Huge thanks to:
@bigbiff (For everything )
@Lossyx
@osm0sis
@Nebrassy
@Qnorsten
for helping in making this recovery. Without these people, TWRP for this device would not have been possible.
Special mention to a friend @apophis9283
Trees:
Device: https://github.com/theincognito-inc/android_device_oneplus_kebab
Kernel: https://github.com/AOSPA/android_kernel_oneplus_sm8250
Download:
OnePlus 8T (kebab)
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
If you need a black themed TWRP (same TWRP as the above, but themed black), you can go to this thread:
[RECOVERY] TeamWin Recovery Project black Themed [OP8T] [2022-03-11]
TeamWin Recovery Project (TWRP) with full black Theme I build a full black themed TWRP for the Oneplus 8t. This is based on the latest TWRP done by @theincognito This nice black Theme was originally created by @Morphine1 and @acuicultor for...
forum.xda-developers.com
FAQ and Known bugs of TWRP:
If you are planning to switch to a custom ROM, and are currently on OOS/H2OS, format /data, switch slot, reboot to TWRP and then sideload/flash the ROM + installer.
It's better to flash ROM + TWRP installer, if you want to keep your TWRP after flashing a ROM.
Don't format /data, after a flashing a ROM, before the first reboot.
It takes around 50s to actually boot into TWRP.
Ideal way to flash:
For OOS to Custom ROM - Format /data, switch slot, reboot to TWRP, sideload/flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
For Custom to Custom ROM - Format /data. Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system.
For updating a custom ROM - Flash ROM + installer, reboot to TWRP, flash Magisk/Gapps. Reboot to system
For custom ROM to OOS - Format /data. Flash ROM + installer, reboot to TWRP, flash Magisk. Reboot to system.
PS: After formatting /data, until the first time the device is booted to system, the files you send to phone via MTP (USB) will be at /data/media, not at /sdcard
PS2: If, for some reason, you cannot send files to phone after formatting /data and rebooting to TWRP, press vol +, vol - and power button simultaneously.
PS3: Factory reset WILL NOT wipe internal storage.
Steps for backing up and restoring data in TWRP (Huge thanks to @BillGoss )
TL;DR for data backup on custom ROMs:
Backup /data (copy the backup folder to PC if you will format /data).
Flash the ROM and boot it once to system.
Restore /data (copy the backup folder back from PC if you formatted in step 1) and boot into system.
If you find any issues like missing navigation bar or blank screen or something, just do a normal reboot again to system.
System Backup and Restore
The "system" partitions on the OnePlus 8T are:
Boot
DTBO
Super which contains the logical system, system_ext, odm, product, and vendor partitions
Just backup and restore these partitions.
Do NOT backup/restore any of the logical partitions individually.
Data Backup
Make sure USB debugging is enabled
You do NOT need to remove your password
In TWRP
Backup: Select only the Data partition.
Reboot System
Restore
Remove the current password before starting the restore process by Settings>Security & Lock Screen>Screen lock: Select Swipe (if prompted tap on "Yes, remove")
If you don't do this, the system will not reboot properly after restoring.
This will also remove your fingerprint data and your lockscreen (encryption) password (you won't be prompted for a password in TWRP or when you restart the system)
In TWRP
Wipe>Factory Reset
Reboot System (this will rebuild the data partition)
Back in TWRP
Restore: Select the backup you want to restore
Remove the SIM card. If you don't do this the system won't boot properly.
Reboot system, making sure the phone is not connected to a PC
Notes:
At this point the phone will take longer than usual to boot - that's normal
You will be presented with a blank screen
Connect the phone to a PC. You should be able to see the phone using adb devices
Disconnect the phone from the PC
Hold the Power button down and select Restart
In System
Settings>Security & Lock Screen>Screen lock: set your password
Insert the SIM card
Note: Your fingerprints will have been restored because the backup was taken with the password set.
besss
Works flash in fkm?
This is great!
liver20 said:
Works flash in fkm?
Click to expand...
Click to collapse
fastboot only
Thanks for it!
Gonna try it!
Amazing! My OnePlus 8T is arriving tomorrow. Perfect timing for TWRP, thanks a lot for the detailed instructions as I am going to need it.
I was flashing this twrp with the previous test_kebab twrp as flash .img. Choosing recovery partition and was thicking "install to both slots".
So far works good.
Bro, I'm happy for you. Great job.
@theincognito Though I am a fastboot flash guy at this point (honestly forgot how to even use TWRP after all this time), I appreciate all the work and time you (and apop) put in for this project. It's definitely going to make this device appeal to more Android enthusiasts as most are used to and prefer TWRP for flashing I've noticed. And that will lead to more development (hopefully) for the device. That seems to have been the case with previous devices I've owned that had TWRP available, but also had the fastboot method available.
Anyway, I have been up for like 32 hours, so if what I've said doesn't make much sense, sorry.
Thanks @theincognito for all your work and time, and I hope this brings more to the 8t community. Good job!
He has this. Again, great job. Glad folks now have a thread to come to for proper support
liver20 said:
Works flash in fkm?
Click to expand...
Click to collapse
Yep, works fine.
You can also flash the zip in the Magisk app, manually from the modules page.
Booted on 9R but unable to decrypt data, after switching to 9R compatible kernel everything is working fine.
Nice job bro.
YumeMichi said:
Booted on 9R but unable to decrypt data, after switching to 9R compatible kernel everything is working fine.
Nice job bro.
Click to expand...
Click to collapse
Is there a unified kernel tree you know of?
osm0sis said:
Is there a unified kernel tree you know of?
Click to expand...
Click to collapse
I'm using kernel source from aospa.
GitHub - AOSPA/android_kernel_oneplus_sm8250
Contribute to AOSPA/android_kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Unified prebuilt kernel · YumeMichi/[email protected]
This should be working fine on both OP8 serials and 9R Signed-off-by: YumeMichi <[email protected]>
github.com
@YumeMichi Thanks a lot for this. I shall make a build with the AOSPA kernel and test on 8T. Should I release it here then, or do you wanna release for 9R?
theincognito said:
@YumeMichi Thanks a lot for this. I shall make a build with the AOSPA kernel and test on 8T. Should I release it here then, or do you wanna release for 9R?
Click to expand...
Click to collapse
It would be great if you can do that.
YumeMichi said:
It would be great if you can do that.
Click to expand...
Click to collapse
I will PM you the build once it's done Then let me know whether it works for 9R too
EDIT: Posting it here
Related
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).
RETIRED! No longer supported or being developed. @Giovix92 is now the lead dev, please use his TWRP for full compatibility with modern kernels/ROM's - https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-3-1-0-tissot-manager-t3976117
Old thread below:
-----------------------------------
About
This is a TWRP Installer ZIP and bootable IMG with extra capability such as Treble-izing, Dual boot repartitioning and other power-user tools with integrated Aroma Installer-powered GUI screens that I call Tissot Manager.
HIGHLY recommended reading and guide for everyone new to Treble - [TREBLE][GUIDE] From Stock to Treble - everything you need to know!. 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 with dual-boot ROM patcher;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Option to install a payload ROM in the current slot, rather than the inactive one;
Option to ignore Payload<>Recovery certificate failures (fix for newer LOS-based ROMs);
Adds a "Tissot Manager" Aroma GUI to TWRP Advanced Menu (bottom-right button), which is the tool used to repartition the device for Treble and Dual boot, as well as some other nifty stuff:
Has the option to shrink System OR Userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink System, you will keep max size Userdata - however it will be incompatible with non-Treble ROM's (they will crash on installing with Error 28 due to System being too small). It will Erase system, requiring you to reinstall a ROM or restore a ROM backup.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Dual boot requires Userdata shrink and works by splitting into userdata_a and userdata_b. The partition split size is customizable during the repartition process.
Adds a "Patches" section with the following current options:
Patch the current Vendor for dual-boot capability (only required if automatic patching wasn't possible). See the 'About Dual-boot' section below for more information.
Enable an insecure ADBD on boot for the current slot (i.e. enable debugging and remove authentication requirement). Useful for ROM hackers/porters.
Patch the current slot to enable/disable forced userdata encryption
All of this info is detailed inside the Tissot Manager GUI.
See screenshots in post 2.
Instructions
Optionally boot the boot-recovery.img to get a temporary TWRP if you don't have it installed, unzipped from TWRP-boot.img-3.2.1-with-Tissot-Manager-x.x.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 (Aroma Installer powered GUI - a fully guided and interactive process).
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack. Reminder - check out my full guide for learning and instructions on all things Treble.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
About Dual-boot
Dual-boot on this device is relatively simple. As you know we have Slots - boot_a and _b, system_a and _b and vendor_a and _b (for Treble). This repartition splits userdata into userdata_a and _b too. You can simply change your Slot in TWRP reboot menu to change which ROM to boot.
This is designed for developers and testers - NOT for daily use. There are some significant issues with dual boot systems:
Any kind of security lock (PIN, fingerprint, etc.) set on one ROM will cause the other ROM to believe it has security too, but constantly fail with unlocking. This is reportedly because security info is stored on persist, which is shared between each slot (and not compatible with differing ROM's).
Because Userdata is split, so is Internal Storage. In TWRP, when changing slots, the MTP will remain mounted to the old slot - it must be manually disabled and renabled (Mounts menu) to update to the new slot.
I will not fix these issues - dual-boot is not designed to be for general/daily use and there may be more minor issues that I don't know about. It's intended for developers only.
In order for a ROM to be dual-boot compatible, the fstab file (information given to Android about partitions to mount) needs a small modification. This TWRP can try to do this patching automatically when you install a ROM, or it can be done manually in Tissot Manager's Patches menu (as well as single-boot patch to e.g. revert a ROM backup from a dual-boot state).
You will see in the install log if a dual-boot patch attempt is successful in the flash text output.
Automatic dual-boot patch occurs only if necessary when:
Flashing an AIO Treble ROM ZIP with TWRP
Flashing a vendor.img in TWRP "Install Image" mode
Automatic dual-boot patch does NOT work when:
Flashing a vendor.img via fastboot
Restoring vendor in a TWRP backup
Any other way of flashing a vendor
In any of these cases, you can manually patch Vendor for Dual Boot in Tissot Manager's Patches menu. You can also remove dualboot support the same way. It will detect the dualboot state of the current Vendor slot and present the available option. If you find that it doesn't actually change after patching, the Vendor is incompatible (please report it to me). RR AIO Vendor is tested OK.
Download
All downloads (and source code) always at:
https://github.com/CosmicDan-Android/android_device_xiaomi_tissot/releases
...or via DevBB Downloads section.
Additional sources not able to be listed in DevBB:
Modified update_engine: https://github.com/CosmicDan-Android/android_system_update_engine_tissotmanager-mod
What's next?
See [TREBLE][GUIDE] From Stock to Treble - everything you need to know! 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. The void kernel included in RR AIO does not have this problem and can therefore be safely used without Magisk (for e.g. GSI compatibility).
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) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
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. It will definitely not work if you have shrunk system.
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 (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (see Questions above regarding fastboot kick and recovery loop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ROM ZIPs with a shrunk System (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
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.
Credits and Thanks
- @mohancm for the original TWRP port, I used some flags from his DT
- @ghpranav and @mountaserhalak for the RR device tree that this is built with (and random help)
XDA:DevDB Information
TWRP with Tissot Manager (Treble & Dual boot support), Tool/Utility for the Xiaomi Mi A1
Contributors
CosmicDan
Source Code: https://github.com/CosmicDan-Android/android_device_xiaomi_tissot
Version Information
Status: Stable
Created 2018-05-29
Last Updated 2019-11-24
Reserved
Screenshots (click for slightly larger non-cropped version)
Screenshot of new TWRP button:
_______________
Main menu (stock partition map detected):
_______________
Repartition choice type when coming from stock:
_______________
Repartition wipe warning/disclaimer if chosing to shrink Userdata for Treble:
_______________
Main menu (Shrunk Userdata type Treble partition map detected):
_______________
Repartition wipe warning/disclaimer if chosing to restore Stock from Shrunk Userdata Treble mode:
_______________
Example of Repartition processing screen:
Good job! :good:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Omg, you are the best man. @mohancm also huge thanks to u man, great devs in our XDA.
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Chikoow1 said:
Nice work!
Did you tested treble roms with this? Aex now have treble support
Click to expand...
Click to collapse
This is just the repartition part, one step of Treble. You still need a Vendor pack. But yes, this enables Treble ROMs and the ROMs require repartition.
ddaggebi said:
I have never seen this kind of detailed, kind guide in XDA. You guys are awesome! Thanks for all this work!
One question : If I choose to shrink /userdata instead of /system,
1. Will I be able to flash stock rom by using MiFlash?
2. If I can, will I be able to get OTA and install them w/o issues?
3. Can I restore a TWRP backup that was made before repartitioning?(because of data on /data)
I think lots of people will be wondering about #3. If you think so too, then please add it in OP!
Thanks to all of you devs again!
Click to expand...
Click to collapse
1. If you do, it will wipe partition map back to stock. So you will need to repartition with Treble Manager TWRP again. But you can make a backup of stock ROM in TWRP and just restore it after the repartition. It should work.
2. Don't know. Needs testing.
3. Yes! I forgot to add this to the FAQ.
Has this tpwr f2fs support and working?
Since Los support It i would like ti have
@CosmicDan
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Filip013;76586434 [user=1844875 said:
@CosmicDan[/user]
Thank you so much for your effort. I'm currently on stock and want to retain stock compatibility, so I'm going to wait until this becomes more polished before trying. I understand that Treble is not meant to be compatible with stock, so I realize my question might be out of place. Still, my question is:
Will you also release the .img file for Treble TWRP for those of us who don't want a permanent custom recovery?
Click to expand...
Click to collapse
It's indeed not intended to be compatible with stock ROM, but your mileage may vary, and as @CosmicDan said, it might work good enough or it won't. You can only try to see the results yourself.
This whole Treble thing is meant mainly for custom ROMS, since stock will never be Treble compatible (still, anything could happen)
I've just updated the TWRP with Treble Manager to 1.1 which fixed a semi-important bug.
Also, I've released a guide for those who find the Treble conversion/install process confusing - check it out. If you can, keep TWRP and Treble Manager specific questions in this thread, but ask your general questions and help over there - I will update the guide as I get feedback
CosmicDan said:
FAQ
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) Untested. Please report your results. But Treble is really not about Stock, you will likely encounter more problems down the line or it may turn out to be completely incompatible.
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/only way for...
...using stock ROM on Treble repartition (requires Userdata shrink ONLY). May also require a custom kernel with dm-verity disabled (untested - if you get bootloop when using stock, it means you do) or Magisk (also untested, may still get bootloop).
...using a non-treble ROM if you shrunk System instead of Userdata since you cannot install non-Treble ZIP's on ROM's with a shrunk Userdata (see next Q)
Q) I get some Error 28 when trying to install a ROM when repartitioned
A) You have shrunk System and are trying to install a non-Treble ROM. This is not possible AT ALL because the ROM ZIP expects a stock-size System. Use Userdata shrink mode instead if you want to be able to use non-Treble ROM's easily.
Q) I see "Unable to mount '/vendor' (Invalid argument)" red error in this TWRP
A) You can safely ignore it. It just means you have not repartitioned your device for Treble yet, so it can't mount the /vendor image.
Click to expand...
Click to collapse
Ay!
Have just finished testing about OTA on stock after Treblizing!
Result?!?
OTA works perfectly on stock after shrinking data to Treblize! Hurrah! ???
Process I followed:
1) Treblize by shrinking data
2) This is important: flash stock ROM in fastboot using MiFlash! When flashing for the first time, select "clean all and lock"! No other standard options working! I couldn't even boot stock using other options!
I've tested by fastboot flashing April build and then updating it to May OTA!
*** On a note: clean all will erase everything on your phone including your personal data!
If you use "save user data" then stock can't even boot! This may caused by the encryption!
BTW, after everything I just restored my non-Treble RR backup and everything works perfect! Just Treble Check app can't check that it's Treblized!
But don't worry! Treble partition table still remains! Fastboot flash can't touch that and can't recognize that it actually exists! Which to me is a good thing!
@CosmicDan, give me a thanks buddy! I deserve this!
SomratMJX said:
-snip-
Click to expand...
Click to collapse
Don't quote the whole OP and please use a smaller font size.
Change slot doesn't work... Others are okay as far as i have seen
dback31 said:
Don't quote the whole OP and please use a smaller font size.
Click to expand...
Click to collapse
Just thought it's too important to highlight! Nothing else!
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Reboot to fastboot and change the slots with
fastboot set_active b
Rakibboss said:
Change slot doesn't work... Others are okay as far as i have seen
Click to expand...
Click to collapse
Use the latest TWRP 1.1! Works fine for me!
SomratMJX said:
Just thought it's too important to highlight! Nothing else!
Click to expand...
Click to collapse
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
dback31 said:
Then please atleast remove the OP quote. It's a pain for mobile users to scroll through this
Click to expand...
Click to collapse
Ha ha ha! It's related to OP buddy!
Anyways, I am too lazy to quote a certain part of the OP!
We all know flashing ROMs got a lot more complicated with the advent of A/B partitions.
This is not my work, the aim here is only to highlight a process which simplifies the task.
Original post on the OnePlus 6 forum can be found here:
https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
It makes use of a script which copies the flashed firmware to both slots without having to reboot recovery and do it a second time. Also by not having to reboot recovery you avoid the issue where internal storage becomes unreadable.
Credit for this goes to:
LineageOS @erfanoabdi @filipepferraz @Prakyy @drpradsms
Download by prakky (hit the thanks button on his post below):
https://androidfilehost.com/?fid=8889791610682890605
The following posts detail it's usage which you follow at your own risk.
Clean Flashing a new ROM
Disable lockscreen security
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Format data; type 'yes' (backup as this wipes phone)
6) Boot System
Reboot recovery to flash additional zips.
Updating OOS base whilst on a custom ROM
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash ROM
3) Flash TWRP installer
4) Flash Finalize.zip
5) Boot System
Reboot recovery to flash additional zips.
Updating a custom ROM (nothing fancy here)
Boot TWRP 3.4+
1) Flash ROM
2) Flash TWRP installer
3) Boot System
Reboot recovery to flash additional zips.
Reverting to OOS
WARNING I've yet to test this!
Boot TWRP 3.4+
1) Flash latest OOS
2) Flash Finalize.zip
3) Format data; type 'yes' (backup as this wipes phone)
4) Boot System
Note: this will revert you to stock recovery as well.
Tip:
Chain install the zips by selecting 'Add more Zips' after selecting the first zip.
Only 'Swipe to confirm Flash' once all zips have been queued.
I recommend numbering the zips in the order they need flashed.
Note: this issue is now resolved as of 09/08/20 as per https://forum.xda-developers.com/oneplus-6t/how-to/guide-rom-flashing-easy-t4143701/post83241857
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Deleted. Think maybe I'm getting altimeters. ?
Prakyy said:
Nice post! Don't mean to be rude but is kinda redundant as my thread already existed: https://forum.xda-developers.com/oneplus-6/how-to/script-copy-oxygenos-base-partitions-to-t4097979
Click to expand...
Click to collapse
Edited first post to make it clearer this is your work.
mitchst2 said:
Didn't know your post existed. Only learnt about the method on Pixen OS thread which uses it and gives you credit as did I. A lot of people only look in their own phone forum. If you don't mind I'll leave this thread open. However if you aren't happy I'll ask a mod to close it.
Click to expand...
Click to collapse
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Prakyy said:
You can keep it open ofc I don't mind.
However, yes, many people only see in their device's forums but since this script will work w/ any A/B device, is there a forum I could post in so that all device owners can see it??
Click to expand...
Click to collapse
Good question.
Is 'Android Development and Hacking / General' the right place? There are some all device guides with a lot of views in there.
https://forum.xda-developers.com/android/general
mitchst2 said:
As a side note and given that I show an OmniROM zip in the previous screenshots here's a fix required for flashing OmniROM.
I use Mixplorer to do the following.
1) Open the OmniROM weekly zip
2) Navigate to folder shown
3) Open metadata
4) Edit oneplus6t to OnePlus6T
5) Save metadata
OmniROM will now flash successfully in TWRP.
Click to expand...
Click to collapse
As of 09/08/20 build and this commit all is well with OMNI and TWRP again. No need to edit the ROM zip anymore.
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
brajesh.sharma87 said:
Is there a proper way to switch from one custom rom to another without formatting the data? Encryption and A/B made the custom rom game so crazy and time taking now. Or maybe I lost track of things. I could always take a backup of storage on laptop but the backups are very huge, mostly 80gb+ and takes forever while backing up whatsapp databases with images thumbnails and all.
Click to expand...
Click to collapse
No when switching ROM formatting data will be necessary. Not used it myself but others recommend Migrate to restore apps and data.
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
brajesh.sharma87 said:
I was looking for a way to backup current rom using twrp, test a rom and then be back on the original rom with a twrp restore. If anyone finds a way to do this without format data, pls let me know.
Click to expand...
Click to collapse
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
flash713 said:
I just restored PiXeN from AOSPA on 6t device and had no issues and I did NOT format my data or do anything but let TWRP do it's restore then rebooted system.. Just backup your system, data and boot partitions and restore them then reboot system. I didn't encrypt my backup using a pw in recovery. I also use magisk canary latest and the themed TWRP recovery 3.4.0-v1 from EvoX rom that acuicultor compiles and morphine1 themes. I've not restored yet using any other TWRP so not sure what works and what doesn't as far as that goes but the themed recovery works for me.
**Formatting data is unavoidable when installing an AOSP custom rom coming from stock OOS rom.
Edit
Click to expand...
Click to collapse
I had to mandatory format data when I wanted to move from evolution x to aospa.
brajesh.sharma87 said:
I had to mandatory format data when I wanted to move from evolution x to aospa.
Click to expand...
Click to collapse
And I've also had to format data before as well but not lately. Could it be because I format both slots coming from OOS or because I use Canary Magisk or the recovery I use.. No idea but next time you are on EvoX backup system, data and boot and try and restore it using that recovery that comes with EvoX and see what happens. These last few weeks I've stayed on AOSiP and PixeN and I flashed Omni once I think but restoring from AOSPA to Pixen was flawless for me and also restoring Pixen to Pixen was also fine, which I do because I always mess around with sound mods.... I'm on AOSiP now and soon as I get more charge on my phone I'm going to try and restore to something I have a backup already made on one of my USB drives and I'll edit this post and report what the outcome is...
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/xiaomi/xiaomimi11.html
Android 12 compatible?
pogi.paul0119 said:
Android 12 compatible?
Click to expand...
Click to collapse
Only with no pin/password
Niice thanks for the recovery bro
Nebrassy said:
Only with no pin/password
Click to expand...
Click to collapse
So answer is "no"
great thank you for the recovery, I hope that the rom quotes will finally be able to get us plenty of custom
Nebrassy said:
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
first test build here, test and report what works/doesn't:
https://build.twrp.me/twrp-3.6.0_11-0-venus.img
Click to expand...
Click to collapse
thank you very much. I installed it for a12. twrp worked. but I couldn't install magisk. How can I install magisk?
Can i update from unofficial 3.5.1 twrp.
But advance not have menu install recovey
Antyhaker said:
So answer is "no"
Click to expand...
Click to collapse
Hummm no it's your selfish answer. It's already good to hear A12 is compatible without security PIN/Password instead of nothing. Congrat dev for his work and for be now the official maintainer
agabey_42 said:
thank you very much. I installed it for a12. twrp worked. but I couldn't install magisk. How can I install magisk?
Click to expand...
Click to collapse
ROM ? MIUI or AOSP ?
You can flash magisk (canary recommanded) directly from TWRP after first setup / boot (so after complete first ROM configuration settings) reboot to TWRP and flash magisk
If from TWRP magisk is not installed, you must using the boot.img patched method.
nunggg said:
Can i update from unofficial 3.5.1 twrp.
But advance not have menu install recovey
Click to expand...
Click to collapse
From TWRP > Install > click button on bottom for change "Install Zip" to ""Install Image" > select new TWRP 3.6 img > Flash
After successfully flashed TWRP, Reboot > Recovery
You can also update from adb (on bootloader/fastboot mode) with this simple line :
Code:
.\fastboot boot twrp-3.6.0_11-0-venus.img
And after flashing, go to recovery mode, it's updated
I'm on Rom 21.12.8, I installed twrp successfully but it can't read the data, I removed all the passwords
Hi
When i try do do this,
"From TWRP > Install > click button on bottom for change "Install Zip" to ""Install Image" > select new TWRP 3.6 img > Flash
After successfully flashed TWRP, Reboot > Recover"
I have one more screen to choose.
I have to select partition.
The options are:
Boot
Dtbo
Persist
Super(system,product,odm, system_ext, vendor)
What should i choose?
Nice job!!! Hope there will be more roms for our phone.
Hello,
I need help, I just intall the new TWRP with the latest Xiaomi.eu stable.
I have a patern and TWRP doesn't let me make my patern to decrypt data.
Can I flash my previous TWRP even if I can't access data ?
Thank you very much !
Edit : I did it, and everything is OK !
After update recovery fastboot loop after reboot every time
please recommend
Nebrassy said:
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Mi 11
USB OTG will not work
Decrypting Android 12 will only work if you remove pin/password
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
thanks to : @erfanoabdi @Cozzmy13
Send me a beer: Crypto (Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_xiaomi_venus
https://github.com/TeamWin/android_device_xiaomi_sm8350-common
Telegram group: https://t.me/NSSFB
first test build here, test and report what works/doesn't:
https://build.twrp.me/twrp-3.6.0_11-0-venus.img
Click to expand...
Click to collapse
Could the install command be wrong? I think typing flash was forgotten in the command.
will this be true? fastboot flash boot twrp.img
agabey_42 said:
Could the install command be wrong? I think typing flash was forgotten in the command.
will this be true? fastboot flash boot twrp.img
Click to expand...
Click to collapse
Simply read a little some reply... There litteraly the command
its NOT working (no files/directories on install zip section)
21.12.8 at A12 (no pins/password)
thanks very much for your efforts mate!
I remove pin or password and install twrp but TWRP can't access data (internal data)
Santoshlove20 said:
I remove pin or password and install twrp but TWRP can't access data (internal data)
Click to expand...
Click to collapse
Same with me. I do everything but not access data.
Solve problem
-Back to Global firmware for me is back to "venus_global_images_V12.0.4.0.RKBMIXM_20210306.0000.00"
After finish need to install TWRP
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3.Reboot TWRP
4.Send the ROM to your phone
5.Install Rom ( EU or Custom rom )
6.Do not reboot after installation complete. Go back in main TWRP menu
7.Go in Wipe menu > Format Data button > Type ' yes ' to confirm > OK
8.Rebot system and Enjoy.
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
http://twrp.me
Old Info
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
ghostcrew said:
Thanks for the build. Tested on Android 11, latest Scorpion rom. Touch does not appear to be working.
Click to expand...
Click to collapse
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Thanks for TWRP for Pixel 3XL!
Thanks bro!. Dont use my pixel for much anymore but great to see someone still developing for it
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
bigbiff said:
Scorpion is not using a stock DTBO. You will have to use the fastbooted twrp adb shell session to install this flashable zip:
https://build.twrp.me/test/crosshatch/twrp-installer-3.6.0_11-0-crosshatch.zip
Push it to /sdcard with adb, and do twrp install twrp-installer-3.6.0_11-0-crosshatch.zip inside the adb shell
Then use adb to reboot to TWRP that is now installed as recovery in boot.
Click to expand...
Click to collapse
I followed your instructions and now I have twrp on my phone and touch is working. Thank you for the instructions and thank you for TWRP on Pixel 3xl!
bigbiff said:
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP 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
Easy selection of internal/external storage
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. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of official builds.
Device Config: https://github.com/bigbiff/android_device_google_crosshatch
Hello, this is a test build for crosshatch users.
If others thing don't work, please report the issue and let me know.
I am opening this thread to replace @Dees_Troy's thread with his blessing.
Download here:
Test1: https://build.twrp.me/test/crosshatch/twrp-3.6.0-0-test1-crosshatch.img
- fix backup and restore
- fix decryption thanks to @Captain_Throwback and his twrp-common tree which fixes the order of proprietary services starting: https://github.com/TeamWin/android_device_qcom_twrp-common
- supports 12 decryption with no pin set
- fully supports 11 decryption with keymaster
http://twrp.me
Click to expand...
Click to collapse
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
sliding_billy said:
Hey, Biff. Thanks, of course. Just wondering if you are releasing it for Pixel 3... I am on P3XL, but my wife is on P3.
Click to expand...
Click to collapse
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
delete...
Zero_Shadow said:
Was able to install TWRP on my Crosshatch however whenever I tried to use the ADB Sideload function to install a rom I would get this error:
serving: 'C:\Users\Zero\Downloads\Pixel 3 XL Project\EvolutionX\evolution_crosshatch-ota-sq1d.211205.016.a1-12251000-unofficial-unsigned.zip' (~0%) adb: failed to read command: No error
Logs attached. *XDA wont let me upload the files see below.
Logs
Click to expand...
Click to collapse
I was able to sideload lineage-18.1. Does adb devices show sideload?
bigbiff said:
We are supposed to have someone lined up. Has anyone posted in the blueline forums?
Click to expand...
Click to collapse
Unfortunately, no.
bigbiff said:
I was able to sideload lineage-18.1. Does adb devices show sideload?
Click to expand...
Click to collapse
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Zero_Shadow said:
Yes I am able to use adb devices in my command prompt and see the device while adb sideload is active in twrp. Heres what happens.
I open up TWRP > Wipe (Factory Reset) then Advanced > ADB Sideload > Swipe to Start Sideload
I see Starting ADB Sideload feature
I go back to my computer and type adb devices (to confirm it see it) > adb sideload filename.zip (being the file of course).
Soon I hit enter I get a crash within TWRP and it goes back to the Main startup page for twrp.
When I go back to ADB Sideload I see this message:
E: fialed to mount /tmp/com.android.apex.cts.shim.
apex to loop device /dev/block/loop0. Reason: Device
or resource busy
E: Unable to create loop devices to mount apex files
E: Unable to load apex images frin /system_root/
system/apex
I did install TWRP to recovery using Advanced > Flash Current TWRP
If I use one of the recoveries for PE or Lineage I am able to flash using adb sideload.
*Edit 1: Now I did download the version from Telegram so let me try the one link above.
*Edit 2: Just tried with the one linked above same thing.
*Edit 3: Logs for review. https://drive.google.com/drive/folders/1PqKN_QzdGnFJTu4Ov-2iUzyzv85ZaD9D?usp=sharing
I could be doing something wrong so any help would be appreciated.
Click to expand...
Click to collapse
What zip are you installing?
Tried the A12 builds for PE, EvoX and PixelDust same issue across the board.
Thanks a lot for this build!!! My Pixel3 XL keeps getting corrupt due to handing/wifi dropping, now finally I can have a Nandroid backup!
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
brandonabandon said:
Need help installing pls. Tried many times with stock to no avail. Now trying with evolution Rom to no avail. My cmd is fastboot flash boot TWRP.img, which works with stock, but I'm unable to install or sideload and have to reflash the stock kernel to reboot the Rom. Same with evolution besides with stock I can attempt to reboot (after flashing twrp) which reboots to twrp, but won't reboot at all with evolution (until reflashing the kernel) I've been at this for a few hours now, any advice much appreciated.
Click to expand...
Click to collapse
You don't flash boot.img with this device. You temporarily boot it with fastboot boot img, then push it to sdcard and use twrp's install recovery ramdisk function.
nithin suresh said:
Thank you for TWRP! Lifesaver. Tried this on my Pixel 3XL running on Evolution X, A11 .... Works great!
Click to expand...
Click to collapse
Is there any possible way you could put instructions or how to install list for me I would greatly appreciate it. I have the pixel 3xl and have been having the hardest time getting twrp install as well as other items.