Related
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
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.
I'M NOT RESPONSIBLE FOR ANY BRICKED DEVICES, DATA LOSS, OR THE WORLD WAR III...
FLASH THIS AT YOUR OWN RISK
ALWAYS READ THE INSTRUCTIONS BEFORE INSTALLING ANYTHING CAREFULLY.
IF YOU ARE NOT SURE, ASK IN THE COMMENTS BELOW OR IN THE TELEGRAM GROUP FOR HELP. OTHERWISE, DON'T BLAME ANYONE OTHER THAN YOURSELF
Bugs
-Userdata decryption is not working. You can flash multi disabler (check this before flashing) to disable encryption or use an external SD or USB OTG for putting ZIPs and IMGs on it in order to flash them
- Data backup is not working due to device encryption
How to Install
0. READ F.A.Q section first here
1. Unlock your bootloader
2. Boot to Odin mode
3. Check AP box and select TWRP tar file
4. Hit start
5. Reboot to TWRP and flash multi disabler if you want (check this before flashing it)
6. Have fun
Download
TWRP 3.5.1_10 - Beta 2
Multi Disabler
Sources
TWRP device tree
Kernel source
Change Log:
Beta 2 - 24th of March 2021
- Update to latest kernel 4.14.190
- Fix MTP on the latest kernel
- Clean up dynamic partitions
- Released kernel 4.14.190 source
Beta 1 - 20th of March 2021
- Initial Release
F.A.Q:
What is data encryption and why doesn't it work on TWRP?
Samsung M51 uses file-based encryption that encrypts the user data partition.
By default, TWRP can't decrypt user data partition, which makes it impossible for us to access the internal device storage from TWRP or recovery MTP, which means you can't put ROM files on your internal phone storage and flash them from there.
What is Multi disabler and how does it affect your phone?
- Multi disabler disables and removes the encryption on the data partition, which makes it possible for you to access your internal storage from TWRP or recovery MTP. thus, making it possible for you to flash files from internal storage.
- Removing the encryption on your device's internal storage makes it possible for you to access your files from recovery directly, which makes it possible for anyone to access your private files without your permission from recovery.
- All of the above means that your device will be less secure. So if you care about device encryption then don't flash the multi disabler and use a USB OTG or a sdcard to flash ROMs, which I recommend. Otherwise, flash the multi disabler at your own risk!!!
- FLASHINF MULTI DISABLER REQUIRES PERFORMING A FULL DATA WIPE WHICH MEANS YOU WILL LOSE YOUR DATA. SO BACKUP YOUR DATA BEFORE FLASHING IT.
My device keeps rebooting to recovery after flashing TWRP, why?
Most probably you will need to wipe your data partition and flash multidisabler
Data backup is not working even after flashing multidisabller, why?
Current multidisabler still can't fully disable FBE encryption, which means that TWRP can't read data partition at all, hence creating backups will always fail.
Reserved just in case
Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.
onurmemo77 said:
Thank you so much for your efforts,
Does backup, restore, work smoothly in this version of twrp? Does it fully restore after making a backup? Or are there still mistakes?
In Twrp 3.4.0 Data backup is not loading. Nonoperating. But the system is loading.
Oh, thank you, thank you.
Click to expand...
Click to collapse
Currently I have no working ROM so I can't test back and restore functionality. But backing data should be working.. don't take that for granted tho..
It would be great if you can test that and report if it's working or not, or wait until I or someone else test that.
thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!
ilya33 said:
thank you for your efforts. i installed this twrp and flashed mutlidisabler. also formatted data before reboot. Unfortunately twrp does not allow to create backups. Cannot unmount system partition etc...Your android 10 TWRP version is creating and restoring backups allright. So for now have to continue using android 10!
Click to expand...
Click to collapse
What error do you get? Can send me the recovery log?
LahKeda said:
What error do you get? Can send me the recovery log?
Click to expand...
Click to collapse
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:
ilya33 said:
i do not remember how to retrieve recovery log. this is a screenshot after I tried to do twrp backup:
Click to expand...
Click to collapse
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com
LahKeda said:
backups will not work because of device encryption. Even after flashing mutldisabler, the device will keep encrypting the data.
Click to expand...
Click to collapse
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks
ilya33 said:
Thanks.
Do you think that Magisk prerooting prior to TWRP flash might help here?
Or maybe we should just for full official Android 11 twrp release...
TeamWin updates TWRP to 3.5.1, Android 11 support coming soon
They're calling it a 'mini release' with a few notable feature improvements
www.androidpolice.com
Click to expand...
Click to collapse
prerooting won't solve encryption issues. Maybe when TWRP can be build using android 11, we can fix encryption issues or at least partially fix it.
ilya33 said:
Fyi -i have spare m51 device with android 11 installed. Ready to use it for any kind of twrp test builds. This is a good phone and we must have twrp for android 11 developed here. Thanks
Click to expand...
Click to collapse
Then go ahead and test this one. plus lineage 18.1 will drop here soon!
Backup failed
Error code: 255
saleem137 said:
Backup failed
Error code: 255
Click to expand...
Click to collapse
Did you even read the FAQ section?
anyways, backups will fail because of data encryption
Does this TWRP require to format data after installing without Multi disabler?
smallKING81 said:
Does this TWRP require to format data after installing without Multi disabler?
Click to expand...
Click to collapse
Nope, but you may need to install multidisabler to prevent the phone from reverting back to stock recovery. Don't formate the data after flashing Multidisabler and see if the phone boots or not
LahKeda said:
Then go ahead and test this one. plus lineage 18.1 will drop here soon!
Click to expand...
Click to collapse
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?
ilya33 said:
well i already tested that twrp build and it does not allow to create backup (which is the main reason i need twrp to start with). i will test your lineage roms no problem. Do you think that twrp will work properly with lineage 18?
Click to expand...
Click to collapse
Data backup doesn't work because of data encryption.
Yes! it's working without any problems with lineage 18
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.
I daily drive a Redmi Note 10 Pro (great phone for anyone having a 250 euro budget if you can get the 8GB version) and decided to swap roms after getting fed up with MIUI's bull****, I ended up installing Pixel OS via ADB Sideload. After a while, I decided to root my phone (mainly to install some mods for the OS such as Dolby Atmos support etc.) and installed TWRP. However TWRP won't mount storage posting "Failed to mount storage" and pressing "Reboot to system" leads to a message saying "No OS detected", before booting back into Pixel OS just fine. Some people are saying that doing a Dalvik Cache and Cache wipe is supposed to fix this issue, however I can't do that if I cant even mount the storage. Another solution people are throwing around is reinstalling your basic recovery, doing a complete factory reset then installing TWRP and your custom OS. All of these solutions are a huge pain in the butt and I would like to avoid resetting my whole phone for the 4th time in 2 months. Has anyone experienced this and can suggest a fix, or is it something I can attribute to Android 12 not being supported by TWRP yet?
imho you have done it in the wrong sequence, because installing a rom, means encrypting storage.
It could be that you have installed the wrong version of Twrp that doesn't support A12 or that encryption is the reason Twrp can't mount storage anymore.
CvGR said:
I daily drive a Redmi Note 10 Pro (great phone for anyone having a 250 euro budget if you can get the 8GB version) and decided to swap roms after getting fed up with MIUI's bull****, I ended up installing Pixel OS via ADB Sideload. After a while, I decided to root my phone (mainly to install some mods for the OS such as Dolby Atmos support etc.) and installed TWRP. However TWRP won't mount storage posting "Failed to mount storage" and pressing "Reboot to system" leads to a message saying "No OS detected", before booting back into Pixel OS just fine. Some people are saying that doing a Dalvik Cache and Cache wipe is supposed to fix this issue, however I can't do that if I cant even mount the storage. Another solution people are throwing around is reinstalling your basic recovery, doing a complete factory reset then installing TWRP and your custom OS. All of these solutions are a huge pain in the butt and I would like to avoid resetting my whole phone for the 4th time in 2 months. Has anyone experienced this and can suggest a fix, or is it something I can attribute to Android 12 not being supported by TWRP yet?
Click to expand...
Click to collapse
Check here and then you'll revise your opinion
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
TWRP is really unclear about wether it supports Android 12 on it's latest release. I've seen many YouTube videos of people daily driving this particular phone, with Pixel OS and TWRP installed so I don't think it has anything to do with the encryption. It may have something to do with me installing my OS via ADB Sideload and installing a custom recovery afterwards
Elinx said:
imho you have done it in the wrong sequence, because installing a rom, means encrypting storage.
It could be that you have installed the wrong version of Twrp that doesn't support A12 or that encryption is the reason Twrp can't mount storage anymore.
Click to expand...
Click to collapse
Laptapper said:
Check here and then you'll revise your opinion
👍[SHARED] orange fox recovery with decryption for Android 12,13
Update post 9 with android 13 decryption support Here I'm sharing the nearly perfect recovery orange fox with implemented decryption for android 12 ( I've tested only pin protection) The main advantage comparing TWRP is the "beautiful" UI and...
forum.xda-developers.com
Click to expand...
Click to collapse
Will check it out as soon as I'm back on my PC you're a lifesaver!