Database Develop

What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]

What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]
Hello,
I just reflashed OxygenOS from Paranoid android after a clean wipe of data, system, cache etc. After set up, I realised there is 12gb of data being occupied under the "other" storage. I proceeded to factory wipe as well and I still have this 12gb of data.
I can not seem to figure out what this 12gb of data is. It is not the oem_logs. I do not have nandroid back ups. I do have around 4gb of titanium backup that I can account for. That means there is still 7gb of data that I can not seem to find.
Any help with figuring this out?
The only thing I could think of now was to wipe internal memory and flash the rom all over. Is that possible? I heard that wiping internal memory is a no no.
I have included some screenshots. If anyone needs more information, please ask.
(The massive app data is because this morning I finally gave in and redownloaded my spotify playlists. Spent 2 days trying to figure out this damn 12gb other data...)
Edit: Forgot to mention, I am on the latest OxygenOS stable. Rooted with latest Magisk and using TWRP 3.1.1-2

An update
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.

Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.

Any apk files you've downloaded, logs you've recorded all in that category. Even large flashable zip files and other firmware files are also under that category.

EatDahPewPew said:
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Click to expand...
Click to collapse
Twrp backups

If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.

Mr.RooT said:
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Click to expand...
Click to collapse
Hey, Do you know what exactly I am looking for in there?

vighneshpillai90 said:
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Click to expand...
Click to collapse
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?

EatDahPewPew said:
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
Click to expand...
Click to collapse
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.

vighneshpillai90 said:
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
Click to expand...
Click to collapse
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.

EatDahPewPew said:
Hey, Do you know what exactly I am looking for in there?
Click to expand...
Click to collapse
Every folder except emulated directory. Firstly I thought that these other folders are links to their original location, but when I deleted that folders, original folders weren't affected. But delete it at your own risk! It could be coincidence, that these folders weren't linked to original ones.

EatDahPewPew said:
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
Click to expand...
Click to collapse
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:

vighneshpillai90 said:
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
Click to expand...
Click to collapse
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.

other than media files and unrecognized file extension
like .zip .apk .flac and etc

EatDahPewPew said:
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
Click to expand...
Click to collapse
Open the Blu-Spark thread, go to downloads, keep scrolling and you find the twrp among the kernels listed there (Latest is v8.52).

[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

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

[RECOVERY][UNOFFICIAL][OneUI3.1] TWRP 3.5.1_10.0 For Samsung M51

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

Question Root stock Android 13

I patched the boot.img file from the new Android 13 stock with Magisk 25.2. How do I relace the boot.img in the original AP tar file with the modified one? When I try to add it to AP I get an error saying there additional data at the end of the archive, which I assume is the md5 data.
edit: I installed TWRP and booted into it with no problem. But when I then booted system, powered off and boot back to recovery, it was gone.

lewmur said:
I patched the boot.img file from the new Android 13 stock with Magisk 25.2. How do I relace the boot.img in the original AP tar file with the modified one? When I try to add it to AP I get an error saying there additional data at the end of the archive, which I assume is the md5 data.
Click to expand...
Click to collapse
Is TWRP available for your device? If yes, use TWRP to flash the boot image to /boot.
Even better, just leave the boot image alone and flash Magisk in TWRP.
If TWRP is not available, try this as it should allow you to use fastboot command line to directly flash the boot image.

V0latyle said:
Is TWRP available for your device? If yes, use TWRP to flash the boot image to /boot.
Even better, just leave the boot image alone and flash Magisk in TWRP.
If TWRP is not available, try this as it should allow you to use fastboot command line to directly flash the boot image.
Click to expand...
Click to collapse
I edited my original post to say I flashed TWRP and booted into it but the patched file was in internal encrypted storage and TWRP couldn't access it. So I booted back to system and moved the patch to SD. But when I booted back to recovery, TWRP was gone. In desperation, I flashed TWRP again and then used it to flash the patched boot. IT WORKED!!! I now have root and it retained TWRP. Don't know why it was overwritten the first time as I made sure to boot to it before booting system.

lewmur said:
I edited my original post to say I flashed TWRP and booted into it but the patched file was in internal encrypted storage and TWRP couldn't access it. So I booted back to system and moved the patch to SD. But when I booted back to recovery, TWRP was gone. In desperation, I flashed TWRP again and then used it to flash the patched boot. IT WORKED!!! I now have root and it retained TWRP. Don't know why it was overwritten the first time as I made sure to boot to it before booting system.
Click to expand...
Click to collapse
Yeah, Vaultkeeper was the problem. Magisk dynamically disables this during boot; otherwise, after flashing TWRP, you should generally flash the Multidisabler and wipe data before continuing. Among other things, Vaultkeeper will automatically replace unsigned images with the stock images, even if the bootloader is unlocked.
Glad to know you got rooted, though!
If you're interested in running AOSP without any of the Samsung bloat, check out my guide here. I have a T290 (Tab A 8.0) and it's become painfully obvious that these midrange devices (Tab A series) don't have enough power to handle a lot of overhead.

V0latyle said:
Yeah, Vaultkeeper was the problem. Magisk dynamically disables this during boot; otherwise, after flashing TWRP, you should generally flash the Multidisabler and wipe data before continuing. Among other things, Vaultkeeper will automatically replace unsigned images with the stock images, even if the bootloader is unlocked.
Glad to know you got rooted, though!
If you're interested in running AOSP without any of the Samsung bloat, check out my guide here. I have a T290 (Tab A 8.0) and it's become painfully obvious that these midrange devices (Tab A series) don't have enough power to handle a lot of overhead.
Click to expand...
Click to collapse
What is +GSM?? Is that google services management?

lewmur said:
What is +GSM?? Is that google services management?
Click to expand...
Click to collapse
GMS. Google Mobile Services Basic Google apps (Chrome, Play Store, YouTube, GMail, etc) as well as the underlying framework and APIs required for Google Play Services dependent apps

V0latyle said:
GMS. Google Mobile Services Basic Google apps (Chrome, Play Store, YouTube, GMail, etc) as well as the underlying framework and APIs required for Google Play Services dependent apps
Click to expand...
Click to collapse
I'll give it a try a little later. Right now I'm bushed!! Thanks

lewmur said:
I'll give it a try a little later. Right now I'm bushed!! Thanks
Click to expand...
Click to collapse
Didn't work. Formatted data and flashed multi. But gsi gave error invalid file.

lewmur said:
Didn't work. Formatted data and flashed multi. But gsi gave error invalid file.
Click to expand...
Click to collapse
What file did you try to flash?
In most cases, you need to extract the system.img from the zip package. You can't flash the archive itself.