Database Develop

Unofficial TWRP for sagit [F2FS+EXT4][Unofficial]

Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM

Thank you for your great work . keep it up

Thanks,I'm following the topic

Sorry for my ignorance....but can somebody tell me the difference between these two?

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/

DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward

fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course

New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?

Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0

Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?

perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1

I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...

Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?

Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )

This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444

New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.

Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!

I assume this twrp version use for flashing gsi. Am I correct?

[RECOVERY][TREBLE] TWRP Recovery for Zenfone 3

This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
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;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
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
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
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).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
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.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
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.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12

@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.

dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now

iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol

dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.

makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?

dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )

makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.

Great work guys!! Waiting for vendor partition, for some tests!

Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.

Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.

Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?

[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.

fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.

I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.

Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition

can i flash android q gsi images using treble recovery.

Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?

Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.

Can i flash android Q gsi image using this recovery on ze520kl

[CLOSED]TWRP 3.3.1-1 for Pixel 3A XL [OFFICIAL]

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its 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.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is not void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* 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.
*
*/[/I]
Note: Please be aware that you cannot install this without a kernel with LZMA compression support, I believe most ROMs have included my commit for this so you should be good for all custom ROMs and kernels. If not please file a request to the maintainer.
In addition, please be aware that TWRP is currently not compatible with Android 10. If you would like to use TWRP you will need to go back to Android 9. If you would like more information you can read at the link here.
Not a huge problem, stock users can just temporarily boot TWRP if you have access to a PC.
Not compatible with Android Q.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. Use ADB or MTP to transfer the zip onto your device.
Go to install and browse to the zip and install the zip. The zip will install TWRP to both boot slots. Installing TWRP at this time will remove root if you are currently rooted.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Changelog:
[BETA]
3.3.1-0: Initial release for Pixel 3A XL devices
3.3.1-1: Fixed having to manually change slots before rebooting.
3.3.1-2: Updated to July blobs!
3.3.1-3: Can now install TWRP to boot image. ADB, MTP, LOGD, Repack Tools and Logcat have all been removed to save the necessary space for this to work. You can grab stuff while in the OS, then flash it in TWRP (Keep in mind I have only tested this on stock as of now, feel free to test it on whatever ROM you use. It should work, but let me know if it doesn't).
3.3.1-4: Changed back to LZMA compression, also added back all the features besides ADB/Logcat. As long as your kernel supports LZMA you will be able to take advantage of installing it permanently without having to worry about space restrictions.
3.3.1-5:
Add persist entry to fstab
* To allow TWRP to store a backup settings file on /persist
and also to be used as QCOM time fix source during early boot.
Revert "Don't include logcat."
Revert "Don't include repack tools."
3.3.1-6:
Revert "Revert "Don't include repack tools.""
Add haptics firmware.
* This obviously on it's own isn't enough to get haptics working for the 3A in TWRP, but its a start.
Don't include a precompiled update_engine_sideload
* This should fix the issue of flashing officials for StatiXOS
[STABLE]
3.3.1-0: Initial official release!
Download:
https://twrp.me/google/googlepixel3axl.html
XDA:DevDB Information
TWRP, Tool/Utility for the Google Pixel 3a XL
Contributors
ZVNexus, janjan
Source Code: https://github.com/TeamWin/android_device_google_bonito
Version Information
Status: Stable
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-07-17
Current Beta Version: 3.3.1-6
Beta Release Date: 2019-06-27
Created 2019-06-27
Last Updated 2019-11-15

Reserved

Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?

DriveEuro said:
Awesome! Thank you so much!
So as of this moment, there is only the ability to boot to twrp via fastboot?
Click to expand...
Click to collapse
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.

So does anyone know if TWRP + Magisk work on Android Q for root?

ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
I don't mind, I haven't flashed TWRP to a device since Treble came out, but it's easy enough to boot an image, so at least for my usage case, this is all I need

otg mounting problem
ZVNexus said:
Yeah, having some issues actually installing it to the boot image. Should be fixed rather soon, just decided to post. Maybe I shoulda waited a bit longer, idk.
Click to expand...
Click to collapse
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?

I'm on Q DP4. Anyone having luck flashing Magisk (canary)? In B slot it fails to mount system and vendor. I change to A slot. It completes. I reboot on A slot, I get stuck at Google starting logo and the phone never boots. If I attempt to boot B slot afterwards, it boots up fine, but I obviously don't have Magisk installed, verified with the Magisk APP.
Anyone have a clue?

Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!

My TWRP is NOT prompting for pin/pattern. That has to be part of this...
Wiped data via google recovery. The phone booted to Pie (i had previously did the OTA from Pie to Q beta 4). So now I'm back on Pie somehow (without reflashing). I booted to TWRP, installed Magisk successfully.
So overall, I'm not sure if this was related to Q beta 4 OTA occupying B slot while Pie still was on A slot.
Thanks to all for their work with TWRP!

Antonyo13 said:
Just to provide feedback.
Fastboot booted the image, it prompted for my pin, mounted system, and was able to backup properly, moved backup to computer.
Wiped the phone, reboot and went through setup, everything was working.
Back to twrp, adb pushed the backup to the phone, restored the backup and everything was functioning.
Also tested and was able to sideload flash Magisk.
So everything seems to be working as intended.
Thank you so much for your hard work!
Click to expand...
Click to collapse
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?

artiemon said:
On previous devices I have run into TWRP restore issues if I had a security PIN set on the device when I backed up. During your test did you have a PIN setup on the phone?
Click to expand...
Click to collapse
I had a pattern, not sure if it makes a difference between pattern and pin.
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.

Antonyo13 said:
I will say the only thing weird i noticed was when i wiped the phone (the default wipe from twrp, not a full format of data from twrp), when i booted I was prompted for my pattern on first unlock before the device setup. Even though it was wiped.
But restoring was perfectly fine.
Click to expand...
Click to collapse
That is normal on pixels. If you factory reset in TWRP your password still stays

spaceman860 said:
That is normal on pixels. If you factory reset in TWRP your password still stays
Click to expand...
Click to collapse
Thank then everything is working great. No issues at all with TWRP

So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?

jcrompton said:
So just confirming - I am , I assume encrypted , as I have a PIN and a pattern with DU ROM. Can i safely backup the existing ROM and flash another and then be able to restore if need be using this version of TWRP?
Click to expand...
Click to collapse
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.

DriveEuro said:
Yes. This is how it has worked in the past. Don't see why it wouldn't work like this currently. If you flash a different vendor image or system image, you'll want to revert back before you restore your old ROM backup.
Click to expand...
Click to collapse
Revert back to what? Sorry I don't understand?

Flash back the original vendor and system images.

GQJ said:
Revert back to what? Sorry I don't understand?
Click to expand...
Click to collapse
He was answering my question about hypothetical referring back to a prior rom from a backup

neshipda said:
no you shouldn't have waited!! thanks a lot specially from all of us checking if twrp came out every day!
hey maybe you can give me a tip since i have a problem mounting otg:
when i boot twrp image if i go to backup/select storage i find a storage/usb partition (0MB)
when i connect otg (and go to mount) it becomes storage/usbotg 1 (12000MB)
but the problem is that if i click it doesn’t remain selected, and the log reports “Unable to find partition for the path ‘/storage’ ”
if i go to mount or backup/select storage and click usbotg 1 storage it doesn’t remain selected and the log reports “E: unable to locate partition for ‘/storage/usbotg-1’ ”
(i’ve tried also with different keys but i don't think it's the point anyway the 1st was an 256GB usb/SD and the 2nd a 16GB usbkey but logs reports same error)
any tip?
Click to expand...
Click to collapse
I didn't test OTG before I uploaded, didn't have an OTG cable, but now that I know its a problem I'll look into it.

[GUIDE] ROM flashing the easy way

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

twrp-3.6.1_11-1_gta4xlwifi para galaxy tab s6 lite ONEUI ONLY

twrp-3.6.1_11-1_gta4xlwifi
Descarga
twrp-3.6.1_11-1_gta4xlwifi.img | by Tickbaby for Galaxy Tab S6 Lite
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
en tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

Someone tested?

Yes and works

ARIES4RR said:
Yes and works
Click to expand...
Click to collapse
How did you install it? I tried zipping it to a tar file with 7-zip and flashing it from AP with Odin but that didn't work.
Never mind. Got it with fastboot. But backup fails and that's my reason for wanting TWRP.

Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin

ARIES4RR said:
Change the name TWRP-3.6.1_11-1_GTA4XLWIFI.IMG by
recovery.img
and create.
recovery.tar
and pass it with Odin
Click to expand...
Click to collapse
I didn't rename it, so that's why it didn't work with Odin. But as I said, I managed to flash it with fastboot anyway. But it still won't backup, probably because data is encrypted.

hi

here it is in tar
twrp-3.6.1_11-1_gta4xlwifi
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
pass with odin

Why use TWRP when you have Lineage Recovery? Lineage Recovery is better.

Backup option work?

Plzz make for LTE variant

Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.

Stelios333 said:
Just made a version for the LTE variant (modified prop.default).
Issues I've found:
Encrypted data partition can't be mounted.
LineageOS fails to install ota updates, because update zip is stored in data partition.
Backup option is not working correctly unless data are decrypted.
Mind the gapps installer fails because it can't mount system_ext partition.
Tested on my SM-P615.
Click to expand...
Click to collapse
#3 I would much prefer to have backup than encrypted data, if that were an option. Is there a way to keep LOS from re-encrypting data? I know that in earlier versions, once you formatted the data partition, it didn't get encrypted again unless you flashed a stock ROM. Or is this a GSI thing?

To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!

Stelios333 said:
To prevent lineageos from re-encrypt data open /vendor/etc/fstab.exynos9611 in an text editor, find a line which starts with "/dev/block/platform/13520000.ufs/by-name/userdata" and remove
fileencryption=aes-256-xts parameter (don't forget to remove also the comma!).
WARNING: That should be done after wiping. The instructions are device specific!
Click to expand...
Click to collapse
Let me see if I have the steps right. I already have LOS up and running. I flash TWRP and boot to it. Then format the data partition to get rid of encryption. Then edit as per the above and reboot. Is that right?

This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de

SamDungUser said:
This is why Linux4 abandoned TWRP for the platform. TWRP seems so problematic! Everyone should switch back to Lineage Recovery. Data is encrypted for good reason on the devices. You don't need a backup option in recovery plus why use TWRP when you can use an official looking recovery? OTA updates on LOS Recovery aren't hideous with logs and it looks official and fits with Lineage! Use Lineage Recovery, NOT this crap excuse of a recovery. Lineage Recovery can be found on the official lineage website for the official version of 19.1 and the unofficial version for unofficial 19.1 can be found at lineage.linux4.de
Click to expand...
Click to collapse
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.

lewmur said:
You do it your way and I'll do it mine. I DON'T LIKE LOS RECOVERY!! And I DO NEED the backup option, thank you very much.
Click to expand...
Click to collapse
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.

SamDungUser said:
TWRP is unsuitable for the device because /data is encrypted therefore backup won't work and decrypting data is unsafe.
Click to expand...
Click to collapse
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)

lewmur said:
I guess you neglected to read the post that tells you how to keep LOS from re-encrypting the data partition. I DON'T WANT IT ENCRYPTED!! I have been using Android devices for close to a decade without encryption and have NEVER had a problem. I have a belt. I don't need suspenders too. (And LOS when it was Cyanogenmod.)
Click to expand...
Click to collapse
Due to the issues with TWRP, Linux4 might block your recovery from being able to install LOS.