Database Users

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "

[Q] TWRP backup fails on data partition "E: Unable to stat /data/data/../cache/ .. "
Whenever I try a full nandroid backup in TWRP it always fails once it gets a few hundred files into the data partition. However, it does complete the backup when the data partition isn't selected.
When I first start the backup a bunch of different red error messages come up for various cache files in the data partition.
"E: Unable to stat '/data/data/[variousapp]/cache/[stuff]/[hashvalue?]' "
I've got a rooted T-Mobile Note 3 with Jedi Elite ROM and TWRP 2.8.1.0, however I'm not completely sure that my phone is legitimately rooted. If I try to open the SuperSU app it says "There is no SuperSU binary installed,...", and applications constantly achieve root access then get denied it moments later. Or sometimes the applications achieve root access with no further issues, it's quite random.
Does anyone have any idea what could be going on?
EDIT: It also should be noted that the files in the error messages can be found when using the TWRP file manager, but when using any file manager application with the OS booted the "/data" folder appears empty.

Anyone have any idea?
Thanks

Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck

CekMTL said:
Well.... from the top of my head I would try to do these things:
1) install one of those "check to see if I am rooted" apps and run it.
2) flash a kernel that has been prerooted, i.e.:that it installs the SU binary to the appropriate location.
3) flash one of those .zip packages in twrp that root your phone.
4) check to see if you can make twrp install root for you ( i think when it doesn't detect root binary it offers to do that).
5) reinstall rom only part as a last resort?
Once you restore proper root access you might need to restore proper SELinux labels to /cache /system /data.
Let me know if you get to this part and need specific instructions.
Best of luck
Click to expand...
Click to collapse
I flashed the latest SuperSU.zip and that ended up fixing root access. The Root Checker app verifies it as well as other applications being granted root access.
I tried flashing CF-Auto-Root in TWRP and it fails.
How do I restore the SELinux labels for those directories?

You caught me on my way to bed but here are the instructions:
From terminal or adb shell
su
ll -Z
(check for any "unlabeled" text for /data /cache /system)
restorecon -Rv /cache
restorecon -Rv /data
mount -o remount,rw /system
restorecon -Rv /system
mount -o remount,ro /system
ll -Z (you should not find any "unlabeled" /cache /data /system)
Let me know how it goes

I tried all those commands from the terminal and it still shows all of the same "Unable to stat" error messages when backing up
The "ll -Z" command, is that supposed to be double pipe or double L? I'd never seen a double L command before so I couldn't get it to work if that's what it is.

Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.

patstar5 said:
Sorry to budge in but I have the same problem too on my oneplus one. Everytime I do something in twrp it saids unable to stat /data/data/com.android.chrome/something I wiped /data and it still does that. I tried to install custom rom and when it starts it saids something is wrong with my system udi and com.android.phone keeps on crashing. So I don't know how I am suppose to fix this. If I format /data I will lose all my pictures,music,apps,etc. since it will wipe /data/media? Any help?
Edit: Upon reading the first post again, I also can't perform nandroid backup because it fails at /data. Which was why I wanted to try different rom and wipe /data to see if it would be fixed.
Click to expand...
Click to collapse
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
Click to expand...
Click to collapse
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.

bu_plus said:
Hi friend,
I have tried my best to locate the download link for the new ver. 5.00 ROM but with no success.
Kindly could you please provide me with the link. BTW, I'm using firefox browser.
Best regards,
bu_plus
Click to expand...
Click to collapse
Well you fixed it the easy way, I went to the thread on how to turn oneplus one back to stock.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
I unzipped the 44s Stock ROM and manually flashed each file via adb to it, that cleared up all my problems. I did lose some data, at least at had my apps, messages, and pictures backed up.
Sent from my Oneplus One using XDA Free mobile app.

utjock12 said:
pat, did you have any luck fixing this? i'm having the exact same issue with my oneplus
---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------
alright i said screw it and wiped internal storage and it fixed the issue. i had to push ROM onto the new storage through ADB but it seemed to fix the issue.
For anyone who is wondering you need to do a FULL wipe (ie in recovery wipe EVERYTHING including internal storage), then push or mount devices through recovery and put ROM back onto SD card.
Click to expand...
Click to collapse
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.

monkey29992 said:
I have this same problem with my OPO and I tried a full wipe including internal storage, but the "unable to stat..." problem still persists. Should I try using the "Format Data" option on TWRP instead of just the "Advanced Wipe"? I tried searching online for the difference but I can't really find any information.
Click to expand...
Click to collapse
So I had my issue on my OPO also, still never confirmed what the actual issue was but after some googling I saw this thread and maybe one more with the same error description.
From TWRP I went Wipe->Advanced Wipe->Clicked ALL boxes.
From what I could tell the issue is actually on the "internal storage" partition which is your emulated SD Card.
I'm not actually sure what the "Format Data" option does tbh I never had to go that far.
Word of warning, make sure you have ADB working and you know how to push files to your phone. You can in theory use the "mount" option from TWRP and connect to a PC as an extendable drive but this functionality is super flaky and is known to not work on occasion.

you don't have to!!!!!!!!!!!
actually i formated it and i was looking for a way to transfer my zip file to internal storage ........... but when i clicked on backup/restore it started to install and booted normally !!!!!!!!!!!!! (by temp boot file)

Sad I am also facing this problem too. At last I have to format everything to get my phone working again, wiping /data does not work, must wipe /data including media.

Internal Storage failure?
This happens to me all the time all of a sudden. I did not change anything at all, except for flashing a new CM version.
I also get a strange stat error, something with google.photo cache.
Yesterday, I have then flashed the new 2.8.6(7) and that gave my phone the rest. It might be because I flashed through TWRP itself into the recovery partition, but now additional to the backup error above when I want to erase dalvik cache, the recovery just hangs. I also can't restore a backup atm.
Now I have reflashed the real 2.8.6.0 recovery and it still hangs when I want to wipe dalvik... wtf is going on here?
And oh yea, my phone does not boot anymore either, it just loops at the flash screen...
UPDATE:
After I found some info on this thread about similar issues, I factory reset my phone with stock recovery (TWRP was not reliable anymore, even the 2.8.6.0 version that was running perfectly before) and then reflashed the latest CM on a wiped internal storage. Now I am up and running again with minimal loss of data due to my TB backups that are scheduled and save to the SD.
But this leaves a very weird feeling back, basically my phone was rendered useless out of nowhere (I was running the previous CM for 2 weeks already), making TWRP backups impossible and forcing me to wipe the internal storage with all media on it without giving me the chance to back it up (MTP in TWPR was also very flaky and died several times half in copy operations). Something is going very wrong with this phone, never ever had that on any of my 5 previous htc devices and the fact that the OnePlusOne users are among the main ones that reported similar issues, I have a feeling it is linked to cheap storage quality. Motorola is a Chinese company now after all... :-/

Hello,
I had the same issue with my Galaxy s4 GT-I9500, it said "E: Unable to stat /data/...", wiping didn't fix, but after I run "format data", it fixed the issue for me.

I have been going through the same issue. I can fix it for 'a while' (by wiping and formatting data) before it comes back again. Anyone knows how to get rid of this once and for all?

Safeguard yourself From Data format/NO O.S @ relocked boot loader

I did a real good number on my nexus 6
I wiped and formated data in twrp thinking you can format a ROM.This type of wipe was the type (YES) Under advanced wipe causing to have No O.S Installed after a reboot .This will happen on any phone if you type YES format data and reboot thinking you'll have a clean ROM . Its a instant brick Unless you have a ROM downloaded prior to flash or have external SD card slot to put a ROM onto.
Then when I went to flash firmware stock Images with Wugfresh tool kit in fastboot mode it failed ,afterwards I OEM relocked boot loader by mistake before i ever tried to reboot the Newly flashed firmware ....thinking the factory images flashed in which they didn't completely. The OEM relock wiped phone and
I was stuck with a No O.S System and no way to OEM unlock bootlader cause I had no O.S to boot into to check mark the OEM unlock box.
This is a highly unlikely scenario for the Inability to reflash firmware if you still remain oem unlocked but Possible if you format data within twrp because it wipes O.S meaning OEM unlock box is gone unchecked
Stay away from OEM relocking Unless you have rebooted safely into a ROM or stock ROM after flashing .
:screwy: DO NOT OEM RELOCK WITHOUT FOLLOWING THE METHOD TO DO SO.
Sent from my Nexus 6 using XDA Free mobile app

androidddaaron said:
I did a real good number on my nexus 6
I wiped and formated data in twrp thinking you can format a ROM.This type of wipe was the type (YES) Under advanced wipe causing to have No O.S Installed after a reboot .This will happen on any phone if you type YES format data and reboot thinking you'll have a clean ROM . Its a instant brick Unless you have a ROM downloaded prior to flash or have external SD card slot to put a ROM onto.
Then when I went to flash firmware stock Images with Wugfresh tool kit in fastboot mode it failed ,afterwards I OEM relocked boot loader by mistake before i ever tried to reboot the Newly flashed firmware ....thinking the factory images flashed in which they didn't completely. The OEM relock wiped phone and
I was stuck with a No O.S System and no way to OEM unlock bootlader cause I had no O.S to boot into to check mark the OEM unlock box.
This is a highly unlikely scenario for the Inability to reflash firmware if you still remain oem unlocked but Possible if you format data within twrp because it wipes O.S meaning OEM unlock box is gone unchecked
Stay away from OEM relocking Unless you have rebooted safely into a ROM or stock ROM after flashing .
:screwy: DO NOT OEM RELOCK WITHOUT FOLLOWING THE METHOD TO DO SO.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Just to note, when facing the "no OS installed" scenario, just download a ROM to your PC. Boot the phone to TWRP, and connect to PC. You can then drag and drop or copy and paste the ROM in your internal storage. Then flash the ROM with TWRP.

Evolution_Tech said:
Just to note, when facing the "no OS installed" scenario, just download a ROM to your PC. Boot the phone to TWRP, and connect to PC. You can then drag and drop or copy and paste the ROM in your internal storage. Then flash the ROM with TWRP.
Click to expand...
Click to collapse
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app

androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Removal of the Google account and a factory reset. Or removal of Google account and flashing a factory image.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:good:

Evolution_Tech said:
Removal of the Google account and a factory reset. Or removal of Google account and flashing a factory image.
Click to expand...
Click to collapse
Unfortunately I'm talking mainly about media data .. Photos files videos ... Unless you have eraser app installed i wanna say its all recoverable even after a reset
Anyone knows gt data recovery disk digger people use for there purpose of recovering lost photos but you never know if they use it on a used phone someone has sold
Sent from my Nexus 6 using XDA Free mobile app

androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
think about it, when you format something you cant have an os installed there any more, you yoursrlf formatted it. you can't format something and keep all the os there as well.

androidddaaron said:
Ya I should have done that .. My question is why even the option for formating data if it wipes O.S
Ive done this alot before selling a phone then flashing a rom after it says No O.S .Only thinking that's the real safe way to make sure all data is unrecoverable .
I have even seen no O.S pop up on many of my samsung phones when doing standard dalvic cache and including system wipe .
What I don't get about the nexus phones is what's the correct way to wipe it Ensuring all data is unrecoverable without having the no O.S issue ,obviously its not just the standard wipe option .It must be formating data ??
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
That's odd, formatting data in recovery has never formatted system for me. I've always formatted all partitions except for system to do a complete factory reset and never had an issue.
OS resides on the system partition so wiping dalvik and system will result in no os.
If you worry about data being recovered by a new owner perhaps you couod write junk data and then format the partitions several times? Not particularly versed on the characteristics of nand so you may want to look into that.

you5urf said:
That's odd, formatting data in recovery has never formatted system for me. I've always formatted all partitions except for system to do a complete factory reset and never had an issue.
OS resides on the system partition so wiping dalvik and system will result in no os.
If you worry about data being recovered by a new owner perhaps you couod write junk data and then format the partitions several times? Not particularly versed on the characteristics of nand so you may want to look into that.
Click to expand...
Click to collapse
he probably formatted everything instead of going by partition.

simms22 said:
he probably formatted everything instead of going by partition.
Click to expand...
Click to collapse
That's what I would think. I have formatted data several times on this device & it certainly doesn't wipe your system partition.

I just flash a factory image using fastboot. Fastboot itself will wipe each partition before flashing. Flashing userdata will wipe internal storage. Then reboot fully into the OS and ensure everything is working as expected. Only then is it safe to relock the bootloader.
Sent from my Nexus 6 using Tapatalk

[RECOVERY][ROOT]TWRP 3.1.0-1 - Galaxy J2 Grand prime plus SM-G532F/G/M

Unofficial release -TWRP recovery for the Samsung Galaxy J2 Grand prime plus SM-G532F/G/M/DS - Mediatek MT6737T
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
Current status: STABLE
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
NTFS support
F2FS support >> To be added
Twrp app support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Download:
twrp_3.1.0-1_sm-g532_5617b
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, my tester @ShaDisNX255
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Is the lineage 14.1 will come for this device or devs working on this?

I'm testing this out from the very beginning (it's not a huge sacrifice, this is my work's phone so I don't have many things stored on this phone)
Trying right now, will feedback after I'm finished.
---------- Post added at 11:11 AM ---------- Previous post was at 10:46 AM ----------
I assume that by wiping DATA is wiping my phone clean, the OS gets erased clean. Am I supposed to re-flash stock and re-root, re-flash recovery?
Edit: Never mind, fixed it.

ashyx said:
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
.
Click to expand...
Click to collapse
Ok so every time I boot in to TWRP, I am going to have to flash the "no-verity-no-encrypt_ashyx" file? Or is it every time the phone reboots, I am going to have to flash this file?
Because so far I've booted into recovery twice and both times I've had this message (the one that asks if I should keep read only or allow modifications to system)?
Also, backup was a success after the flashing of the no-verity file but I failed to make a successful restore
I'm uploading the recovery to mediafire since it's about 2 MB long and I didn't want you to miss any detail.
Recovery Log

ShaDisNX255 said:
Ok so every time I boot in to TWRP, I am going to have to flash the "no-verity-no-encrypt_ashyx" file? Or is it every time the phone reboots, I am going to have to flash this file?
Because so far I've booted into recovery twice and both times I've had this message (the one that asks if I should keep read only or allow modifications to system)?
Also, backup was a success after the flashing of the no-verity file but I failed to make a successful restore
I'm uploading the recovery to mediafire since it's about 2 MB long and I didn't want you to miss any detail.
Recovery Log
Click to expand...
Click to collapse
OK you need to flash the boot patcher to disable encryption. This is the only way you can make a data backup or restore.
You only need do this once unless you upgrade or replace the boot image.

ashyx said:
OK you need to flash the boot patcher to disable encryption. This is the only way you can make a data backup or restore.
You only need do this once unless you upgrade or replace the boot image.
Click to expand...
Click to collapse
Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback
---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------
ShaDisNX255 said:
Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback
Click to expand...
Click to collapse
Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.
---------- Post added at 01:31 PM ---------- Previous post was at 01:24 PM ----------
ShaDisNX255 said:
Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback
---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------
Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.
Click to expand...
Click to collapse
Unticking "nvram" and it gets a successful restore.
The phone works fine
:good:
I think TWRP is good to go for the G532

ShaDisNX255 said:
Got it. Yeah for some reason after 2 reboots in to TWRP I got the message twice so I flashed the no-verity file twice.
Anyway, I still couldn't do a "Full restore", it fails when it gets to something called vram?
Idk, I'm trying another backup and restore, but this time I'll wipe (factory reset) before restoring.
Be right back with feedback
---------- Post added at 01:24 PM ---------- Previous post was at 01:06 PM ----------
Yeah, it gets stuck on something called "nvram"
I am trying another "restore" with this particular box ticked off and see if everything else restores nicely
I really don't know what that is.
---------- Post added at 01:31 PM ---------- Previous post was at 01:24 PM ----------
Unticking "nvram" and it gets a successful restore.
The phone works fine
:good:
I think TWRP is good to go for the G532
Click to expand...
Click to collapse
I'll look at that partition, it may just be protected so not able to be backed up. If not I'll just remove it from backup.
Can you give me a screen shot of the on screen log?

ashyx said:
I'll look at that partition, it may just be protected so not able to be backed up. If not I'll just remove it from backup.
Can you give me a screen shot of the on screen log?
Click to expand...
Click to collapse
Here you go

ShaDisNX255 said:
Here you go
Click to expand...
Click to collapse
Ok I've found the issue with /nvram and will be uploading the fixed version shortly.
Just for info you can take screen shots directly in TWRP by holding POWER+VOL DOWN. Note where it saves the screenshot.
However there seems to be an issue with the EFS backup being empty, so I need to check if there are sub partitions I need to include.
Can you do the following in ADB or a terminal:
For ADB, enable USB debugging and do:
adb shell
su
ls -laR dev/block > sdcard/block.txt
For terminal do:
su
ls -laR dev/block > sdcard/block.txt
You can also use TWRP terminal:
ls -laR dev/block > sdcard/block.txt
Then find block.txt in /sdcard and post up.
.

ashyx said:
Ok I've found the issue with /nvram and will be uploading the fixed version shortly.
Just for info you can take screen shots directly in TWRP by holding POWER+VOL DOWN. Note where it saves the screenshot.
However there seems to be an issue with the EFS backup being empty, so I need to check if there are sub partitions I need to include.
Can you do the following in ADB or a terminal:
For ADB, enable USB debugging and do:
adb shell
su
ls -laR dev/block > sdcard/block.txt
For terminal do:
su
ls -laR dev/block > sdcard/block.txt
You can also use TWRP terminal:
ls -laR dev/block > sdcard/block.txt
Then find block.txt in /sdcard and post up.
.
Click to expand...
Click to collapse
Attaching requested file, also attaching screenshot of the message I got after typing the command

Good work, guys

ShaDisNX255 said:
Attaching requested file, also attaching screenshot of the message I got after typing the command
Click to expand...
Click to collapse
This should fix the nvram backup error. I have also reduced the amount of partitions available for backup. Some were just unecessary.
Can you post me the recovery log after installing this version and if possible after backup/restore please?
https://www.androidfilehost.com/?fid=961840155545571164
.

ashyx said:
This should fix the nvram backup error. I have also reduced the amount of partitions available for backup. Some were just unecessary.
Can you post me the recovery log after installing this version and if possible after backup/restore please?
https://www.androidfilehost.com/?fid=961840155545571164
.
Click to expand...
Click to collapse
Some weird red messages appeared during the back up
I am going to attach both logs of TWRP (the new version) being recently installed and the log of when I performed a backup.
I don't know if you want me to go ahead and try a Restore as is.
The log after the backup is uploaded to mediafire Check Link [Here} since it's about 2 MB big.
Pastebin doesn't let me host it there either.
The log after recently installing TWRP is attached.

ShaDisNX255 said:
Some weird red messages appeared during the back up
I am going to attach both logs of TWRP (the new version) being recently installed and the log of when I performed a backup.
I don't know if you want me to go ahead and try a Restore as is.
The log after the backup is uploaded to mediafire Check Link [Here} since it's about 2 MB big.
Pastebin doesn't let me host it there either.
The log after recently installing TWRP is attached.
Click to expand...
Click to collapse
Just needs a tweak to the fstab layout. Will update tomorrow.

ashyx said:
Just needs a tweak to the fstab layout. Will update tomorrow.
Click to expand...
Click to collapse
Yeah sounds good. Will test tomorrow

I'm trying to root my J2 Prime (SM-G532G/DS build G532GDXU1AQC1) but I want to do it through TWRP, will this method work? It's a new phone and I don't want to brick it within just 3 days of purchase.

ShaDisNX255 said:
Yeah sounds good. Will test tomorrow
Click to expand...
Click to collapse
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.

ashyx said:
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.
Click to expand...
Click to collapse
Similar red text to previous build
Uploaded recovery log to Mediafire

ShaDisNX255 said:
Similar red text to previous build
Uploaded recovery log to Mediafire
Click to expand...
Click to collapse
I'm assuming these are the errors you are referring to?:
Unable to locate '/proinfo' partition for backup calculations.
Unable to locate '/preload' partition for backup calculations.
Unable to locate '/secro' partition for backup calculations.
These aren't even included in the fstab or backup as I removed them, so no idea why TWRP is referencing these partitions.
Anyway hopefully this will resolve the issue: https://www.androidfilehost.com/?fid=817550096634775525
By the way, you don't need to back up /cache or /system_image. /cache is only temporary data and should always be empty after reboot. /system_image is the same as /system except it creates a raw backup of the system partition..
.

ashyx said:
Ok, this should fix all issues. :fingers-crossed:
Please note if you have made any previous backups then I suggest you delete these as they will no longer be relevant and will cause errors if you try to restore.
If you could try a backup then restore with this version and then post the recovery log so I can check it over?
I have added the update to the OP.
https://www.androidfilehost.com/?fid=673368273298960951
.
Click to expand...
Click to collapse
Link not working 404 error seemes like url not does not exist
Sent from my SM-G532F using Tapatalk

Stuck at Password Screen! Please Help

So I’ve tried many ROMs and am on the latest version of TWRP but I keep getting stuck at the password screen after rebooting. I have tried many factory resets and complete wipes and nothing has worked. I am also getting “encryption” errors and twrp errors about decrypting data...asking for a password and then telling me my password is incorrect. Is this the end of my 6P? Thanks for any help!

Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.

notstevek said:
Password is linked to user data partition, a full wipe with TWRP doesn't wipe this partition, so it won't remove it. So to remove your password and fix this issue, you need to wipe the user partition, which will remove anything on your phone.
Click to expand...
Click to collapse
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!

videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.

notstevek said:
Also, not to be rude, but you do know if you set a password, the twrp password is the password you're using for your lock screen? I don't mean to belittle you, just wanted to make sure you knew his. If you make your lockscreen password pin 1234, that's what you do in TWRP, if pattern, use that pattern, if regular password, type that.
What I mean by data is in TWRP you have the option to wipe phone (factory wipe) which does "data, cache, system", but that is not the data I am referring to. If you click advanced wipe, you have the option of formatting "internal storage" that is the user data I am referring to that holds the password. That's the portion you save stuff to like picture, the other data partition is where system apps get installed. If you can boot into the rom and use it normally, remove the password, does TWRP still ask you for a password? What about changing password, or changing from password to pin or pattern? If you've done all that I recommend manually downloading stock nexus 6p update, using fastboot, format each and every partition and flashing (including recovery) stock firmware. Nexus 6p is known for bootloop, this is something entirely different. Can you please verify that you can:
Boot into phone and use it(what rom?)
Remove password(if this doesn't work, see below)
Change password
Change to different type of password (go to pin if pattern, pattern if pin, password if pin/pattern)
Formated internal storage (which you need to backup and again is not the same as doing a "swipe to factory reset" in TWRP, you need to click advanced wipe and hit wipe internal storage.)
If none of that works, I again suggest trying to use fastboot, format each partition manually then flashing a full stock firmware including internal storage, and recovery, then install TWRP and rom, and see if that fixes it.
P.s. I don't want you to think I'm treating you as if you're clueless I am just trying get as much information and be 100% clear and on the same page regarding everything you try and make sure we're talking about the same stuff (i.e, regarding formatting Data) so we're on the same page, and so I can help you out to the best of my ability to.
Click to expand...
Click to collapse
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

videotape74 said:
I have formatted the data and wiped my phone fully. It will let me install a new ROM and I can boot into it, set it up but after a couple of restarts...I get stuck on the password screen again. Then if I reboot into twrp it asks me for a password there to decrypt data. I am so confused!
Click to expand...
Click to collapse
videotape74 said:
went back to stock fully after formatting partition, phone booted up fine, updated my apps and restarted my phone...now I'm getting a screen saying "Decryption Unsuccessful". i enter the correct password and it says I have to factory reset...i do, set up everything again and the same thing happens! pic below...thanks for any/all help.
Click to expand...
Click to collapse
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.

notstevek said:
Oh this explains it ok. You need to format the internal storage. I'm not sure what that button does in regards to resetting but I recommend you using fast boot to wipe everything to factory rom. Go here: https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 and follow #11 in the second post. Add the command "fastboot format userdata" to that set of instructions. This will wipe your phone to factory, as if you just bought it. Once this is done, setup the phone, make sure it boots and works. If it does, download TWRP again from https://dl.twrp.me/angler/twrp-3.2.3-0-angler.img.html use the command "fastboot flash recovery twrp-3 2.3-0angler.img" to reflash TWRP. Try rebooting into twrp a few times to see if you can get the same error, if you can't you fixed it. If you can, your phones flash memory is probably shot. Let me know if you need anymore help and how it goes.
Click to expand...
Click to collapse
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!

videotape74 said:
I followed your steps exactly and now I'm getting the below error...I guess my flash memory is done.
I appreciate all the help you've given me!
Click to expand...
Click to collapse
I'm sorry to hear that. So to confirm you completely reflashed to stock firmware, reflashed TWRP recovery, and it's still giving you the error? Maybe someone else has some idea of what's happening but only thing I can think of is flash memory is shot. Try maybe older version of twrp??

Something similar happened to me, I will explain my situation and how to solve it, I had the stock ROM 8.1.0 installed and out of curiosity I put a start block that starts with a password and all right up there, then install the twrp and I prepared to put a Custo ROM to be specific CRDroid and everything was installed correctly nothing unusual, the problem came to insert my SIM card and see that I had no signal review the imei and had disappeared was blank and had not made rest of the SAI so I turned pale, then started twrp and asked for the password I had put with the stock ROM and accept it I made an advanced deletion and still still without imei, I reinstalled the latest version of stock ROM home, I asked for the password ,I was. security and I removed all kinds of security, I returned. do the process of installing the Custon ROM and the imei turned MIA CONCLUSION by changing the ROM and better to disable absolutely all kinds of blocking tank can bring signal or encryption conflicts

Problematic Xiaomi MI 9T - can't flash due to encrypted partition

Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.

johan.drykke said:
Hi everyone, I just bought myself a MI 9T davinci global version. I wanted to make it so that it is nethunter, but It just doesn't work. I try everytime to flash recovery first then image, but when I try to copy images for flashing this **** comes up.
View attachment 5668491
I can't copy anything inside. I am looking for any image of a ROM but when I choose MIUI 11 for 9T, the official one, just so I can flash it somehow I can't do it, becuase Chinese little hands did something unexpected, I have to LOG IN to flash MY hardware with software I want.
What the f is going on? I can't flash dm-verify because I can't put it on the phone anywhere, I can't flash ****. What can I do? I have currently MIUI 12.4 I think.
Click to expand...
Click to collapse
Very simple. When you open TWRP, it should ask you for the PIN. You have to enter the same PIN/Pattern you use the same for unlocking the screen in Android
Use the latest official TWRP from TWRP.me
It's nothing specific to Mi 9T or Xiaomi, it's a very good protection enforced by Google couple of years ago with A10 - TWRP cannot decrypt your Internal memory data without your pin.
Just consider your phone gets lost and somebody boots to TWRP - would you like him to be able to see your photos, documents, etc

The thing is, I had pin, 1234, I flashed twrp official through fastboot, It didn't ask for it, partition is still encrypted. Whet next? I tried wiping **** out of sdcard putting image there and flashing it, PicselExp, bootloop willkomen. Nothing is working, I am glad I flashed recovery though.
Please stop moralizing, I bought this phone because I want to play with it, not to store DEFCON 2 documents on it.
EDIT1: Sorry for beeing harsh, just I think that this 'davinci' is different than other 'davinci' and for the love of God, I hate TiVoization.

johan.drykke said:
Please stop moralizing...
Click to expand...
Click to collapse
I'm not noraluzing, I wanted to help, now I don't care anymore. Google will be your friend, everything relevant can be found there
Good luck

use fastboot to flash stock ROM (fastboot ROM). then from stock removeall safety patterns, fingers, go to flashing twrp with fastboot, boot to twrp, format data, flash whatever you want
be polite or get the f...out of this forum

Hi!
I'm having a somewhat similar yet kind of different problem : long story short I was able to flash a ROM once last week, it bricked my device and the internal storage got encrypted just like that, I somehow managed to manually flash a stock ROM from ADB and now my device boots properly on a stock MIUI.
The issue is I have no lock pattern anymore and the internal storage is still encrypted so I still can't flash from recovery.
Am I doomed to rock MIUI until my device dies? At what point should TWRP ask me for a pattern?

can't you format data in recovery?
wipe everything in recovery, try to install desired ROM. Hope you have made a backup before encryption

I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.

Crikripex said:
I have not tried yet, does wiping data remove encryption and "read only" ?
I had not backed up before encryption but as long as I have fastboot I have a stock MIUI I could flash with adb, it's kind of tedious but better than nothing.
Click to expand...
Click to collapse
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc

yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM

zgfg said:
There are two things:
- Data and Internal memory are FBE encrypted:
File-Based Encryption | Android Open Source Project
source.android.com
- System As Root (SAR) = System, Vendor, Product are Read-only
Do not mix/mess-up one with another
---
Format Data does not remove one or another
FORMAT - not Wipe, there are two different buttons in TWRP.
And Format Data only (not System, etc)
After that, reboot to Android, setup your screen unlock pin
Then reboot to TWRP, it must ask you for pin - enter that same pin you did set in Android for screen unlocking
The TWRP (by the FBE mechanism) will be able to decrypt Data and Internal storage.
On a folder or file by file base - just like it works in Android (seemless for you)
Same way you have to enter your pin every time when you reboot to Android - samw you have to enter the pin every time you reboot to TWRP
Because FBE ancryption cannot decrypt without your pin
And that's a good feature (enforced by Google, since Android 10). I don't understand why people are 'afraid' or whatever of that. Thinking it's something strange, unwanted, whatever
If your phone is stolen and the thief reboots to TWRP, he will see scrambled files and folders. If he copies the files to PC - your photos and documents, etc will be scrambled and of no use for him
Without FBE, the thief reboots to TWRP (he cannot to Android since not knowing our pin) and he could copy your files to PC and open them
And things work seamlessly for you, hence no problem at all
---
Read only SAR is something totally different. System filesystems are read-onl and you cannot make any (hard) changes. Even not with Magisk/root
But Magisk privides Systemless mechanism - where every time while booting and initializing Magisk, Magisk mounts the changes asked by Magisk modules.
That way once you are booted, your System appears as it was changed (AdAway hosts file, debloating, Viper4Androud, etc).
Hence again, things work for you seamlessly.
But if you disable/uninstall Magisk module(s) or Magisk itself (or you just reboot with stock Boot img - without Magisk), then you have clean/not changed/not affected System - and since that you have no problem with OTA, etc
No Xiaomi 'features' but things enforced by Google and you will find them in all new phones with new Android versions
Actually, started with Android 10 or so, hence present already for 3 years out.
No more times of KitKat, Open Bootloaders, etc
Click to expand...
Click to collapse
yaro666 said:
yes, format data wipes encryption and all of your data.
Without decryption you won't be able to restore data.
Boot to miui, make a backup if that's possible and then boot to recovery, format data and do everything to i stall desired ROM
Click to expand...
Click to collapse
Thank you both so much for your time, help and explainations!
I finally understand what was happening, I had a hard time pinpointing exactly what made my partition encrypted but it does make a whole lot of sense.
I managed to successfully flash ArrowOS 12.1 using sideload after formating. I now know both that my system is naturally encrypted and that it is completely normal and not a result of a flashing error
Last time I flashed a ROM the newest and flashiest android was 9.0 so it's all new to me.
Thanks again!

There is a TWRP (TWRP 3.6.2+ - UNOFFICIAL | Android 12.) specially made to work with android 12 enryption. (The version from Adi is only needed for his supported roms. Otherwise always use the TWRP 3.6.2+ if not declared differently)
Could be useful if you want to OTA update your rom. Otherwise you could be forced to sideload over adb or even make a complete clean flash again.
Selfquote:
[RECOVERY][3.4.0-10][davinci]Official/Unofficial TWRP for Xiaomi Redmi K20 (Stable)
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...
forum.xda-developers.com