Related
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Michael B.N. said:
I wanted to update my rooted Android Nougat to Oreo and also go from SuperSU to Magisk. During that process I discovered that TWRP recovery couldn't mount my internal storage.
I quickly saw on a lot of sites that it's a well-known issue, and I solved it by converting from ext4 to ext2 and back again. Now my phone is running perfect. All apps are installed, data and settings are restored with Titanium and root with Magisk is working fine. But then I remembered about the issue with TWRP and booted into recovery - just to discover the problem is back again. I can't mount my internal storage. So I can't flash zip files, I can't do a backup etc.
When I search xda or the web in general, I can't figure out why the problem has occured again. Also I can't find out how to fix it without losing all my data. Can anybody answer these two questions? Why is this happening again and how do I permanently fix it? And can it be with all my data on my phone - because I'm not able to do a backup.
Click to expand...
Click to collapse
The problem occurs when you use a ROM which encrypts the software or the ROM your flashing has an encrypted kernal. The only way out is to flash a ROM which doesn't encrypt. It is a known problem with TWRP and we have to wait for the TWRP team to update TWRP to handle quota allocation.
It seems the problem is solved for me. I flashed the TWRP version from this link: https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
First I tried from Odin but it didn't work. Then I installed the TWRP app from Google Play and flashed the other file, rebooted to recovery, and it seems to work. I can mount my internal storage, make a backup etc. So this is the solution for me.
I had also similar problem of internal storage 0mb and i was not be able to mount my data
so when i flash color recovery by nobody
It's gone because it's allready patch by him
I think it's issue of encrypt data so just flash this recovery from nobody post
https://forum.xda-developers.com/galaxy-s7/themes/recovery-twrps-colored-t3859323
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
i think you must try with different file mngr, that one have no ability or permission to read system files
noniboyba said:
i think you must try with different file mngr, that one have no ability or permission to read system files
Click to expand...
Click to collapse
I'll re flash later and try a different file manager. Otherwise I'll install treble or re flash stock and start over
isgakbrfc said:
Hey guys
wondering if somebody can assist me with my issue. I can mount the internal storage via twrp, and can copy files etc over to the internal storage on my pc. But when i go into file manager nothing appears. even though i indicate that it show me the internal storage. any ideas?
Click to expand...
Click to collapse
same problem, have you found solution ? please help me
TWRP sometimes can't mount the storage, the storage is encrypted, but don't worry. You can still flash your files and rewrite system partion. But in order to show the Storage, you have to use a different version of TWRP. Why am I saying this is mentioned following:
I installed the latest version of twrp, It didn't ask for any password patter to decrypt my storage. So , different XDA posts made me understand that , formatting everything, factory reset will decrypt my storage. And trust me, I have done it several time, several times my brother but it didn't decrypt my storage. I couldn't backup my ROM and without backing up my ROM, I didn't take the risk of flashing new ROM. I waited. This twrp couldn't even mount my system partion. So I seeked knowledge from different person. It took a lot of effort.
Then I learned that, I should change this version of TWRP. I changed to an older version and it didn't decrypt my internal storage after formatting, but it mounted my system partion. Since, it couldn't decrypt my internal storage, I couldn't take backup of my rom and save it to internal storage. so I inserted a pendrive in my phone, and saved the backup of my rom there.
Permanent Solution
Flashing DM Verity Force Encryption Disabler will decrypt your storage instantly. But in my case, it aroused another problem, None of the security measures of my phone worked afterwards. FOD, pin, password, pattern none of them worked. I don't know the reason but I don't suggest it with my little knowledge. but almost every rom flasher use them, so I thing I have to study about them to know how they work.
second and best option: start trying older version of TWRP, the good one will be the one to ask the password the recovery in the beginning. It will decrypt your internal storage.
I was brief here, if anyone doesn't understand these things, let me know, I will explain them step by step because I know the pain of being NEWB.
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
knives of ice said:
I upgraded to the latest Q4 beta. When doing this following instructions when flashing in TWRP it said to flash the file from USB otg since you couldn't flash from internal storage.
my question is, once you have Q installed as I do can you never flash files from internal storage? i assume this must be the case, or i have something very wrong with what i'm doing. I can't mount my internal storage at all in TWRP or see any of the files.
Click to expand...
Click to collapse
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
twinnfamous said:
Everything works but decryption.
We may have to wait until official q comes before decryption works.
You may find ways to run unencrypted using search function. I know it has been talked about in the forum.
Click to expand...
Click to collapse
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
knives of ice said:
Do you have any idea what could be wrong with my install or setup? I can't mount system. It can't even see my internal sd card it lists it as 0. Never had anything like this happen
Click to expand...
Click to collapse
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
twinnfamous said:
U can't see anything in SD card if decryption doesn't work.
What twrp and what where your steps to get where you are now?
Click to expand...
Click to collapse
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
knives of ice said:
yes, i know what you are saying with encryption when you can't decrypt it still shows everything with crazy decrypted numbers like 8784322qzzwerei, etc. Even if i turn off my security and boot into twrp (i'm running the latest version i believe 3.3.1-50 according to the twrp menu) it can't see anything on internal storage. when you go to select storage it shows 0mb under internal storage. if i plug in a usb otg it immediately shows and reads that.
if i want to select a file it says select file from internal storage (0 mb)
I have things installed to slot A. these slots i'm not used to using but maybe someone when it boots to twrp its not on the right slot or something? any ideas?
Click to expand...
Click to collapse
Has the rom booted yet? Did u wipe? Nevermind forgot on q it just shows 0mb
U can try switching slots but it might put u back to rom u had before.
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
miffymiffy said:
As was previously stated, TWRP cannot decrypt data on q. TWRP will have to be updated to address this. It will be the same for everyone.
Once you boot into rom, all your data will be accessible.
Maybe try fastboot boot twrp.img as that may allow decryption
Click to expand...
Click to collapse
even if i remove all encryption from my device the system still shows at 0mb. which means you can't flash anything in twrp from the sd card.
i'm trying to figure out why i can't get magisk vanced to work and i assume it is because the flashing in magisk isn't occurring correctly.
so does everyone show a system in twrp for q at 0mb? if what i have is normal and the norm, fine but that was the reason for this thread to list the differences/limitations of twrp in q.
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
docnok63 said:
I believe TWRP can't access the internal sdcard due to the change in Q called Scoped Storage:
https://developer.android.com/preview/privacy/scoped-storage
This is also why Magisk vanced isn't installing properly
Click to expand...
Click to collapse
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
knives of ice said:
i agree.
the problem is, some are reporting no problems with youtube vanced through magisk. others are claiming that they can see the data on their sd card. i have no idea, maybe some of these people don't even have the q beta installed.
Click to expand...
Click to collapse
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
docnok63 said:
I've been on DP2, 3, and now 4 and never been able to see internal in TWRP. All flashes have had to be done via OTG after the initial Q install.
Click to expand...
Click to collapse
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
I have YouTube Premium so I don't mess with vanced. Sorry...
knives of ice said:
ok awesome, thanks for confirming. have no idea what some are claiming in the ver 4 thread.
have you found a way to get youtube vanced working? even the non rooted version force closes for me. that is the one thing in my routine that is tough to live without.
Click to expand...
Click to collapse
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Namolas said:
Because if your run your device unecrypted you can access the data partitions in TWRP while running Q.
Click to expand...
Click to collapse
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
knives of ice said:
i remove all fingerprints/pins and have no security. i should be able to boot into TWRP and see data then correct?
it still shows 0mb for me and won't mount.
Click to expand...
Click to collapse
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Not sure if this is worth anything or not, but it's decryption related: https://gist.github.com/mauronofrio/af29bad34ad87a1a957d193794f0bf5f
Namolas said:
Currently decrypted state, and running the device unencrypted aren't the same. Even with your fingerprints pins removed if you look in Settings/Security you'll see your device still shows as encrypted.
OnePlus 7 forces encryption by default. To run your device unencrypted you have to format the internal storage (wipes everything pictures media etc) and make sure you flash a special disable force encrypt zip every time you flash anything system related in TWRP.
Its a lengthy process to get it running unencrypted and if you forget to flash the special script even one time OP7P will force encrypt on boot and you have to start over. Its not for everybody but I know a lot of people running this way, myself included.
This should all be fixed with and update to TWRP but who knows how long that will take.
Click to expand...
Click to collapse
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Gabrech said:
Thanks for your post.
So if I want to "dirty flash" a rom on android q, is it still possible with data encrypted or should I format internal storage anyway ? (and clean flash...)
Click to expand...
Click to collapse
On my Pixel (original) with TWRP 3.3.0-0 and Q, I am able to do everything normally, including decrypting, dirty flash, cutstom ROMs, factory, nandroids, etc .... However, /system and /vendor won't mount. But, it works anyway!
The scoped storage is still a pain in the butt.
I had MIUI 11 installed. I flashed the latest firmware 9.9.3, installed TWRP, and flashed the official Pixel Experience ROM 10 along with fcrypt disabler but it was stuck in the boot loop. So I flashed only the ROM file again and wiped dalvik&cache. The ROM is working perfectly.
But now I wanted to flash the magisk root and when I entered TWRP, it didn't ask me for a password even though I set a pin for my device. When I saw my storage, everything was encrypted.
So do I have to format my storage in order to get decrypted or did I miss any steps? Please advice.
The Blackholed Gamer said:
I had MIUI 11 installed. I flashed the latest firmware 9.9.3, installed TWRP, and flashed the official Pixel Experience ROM 10 along with fcrypt disabler but it was stuck in the boot loop. So I flashed only the ROM file again and wiped dalvik&cache. The ROM is working perfectly.
But now I wanted to flash the magisk root and when I entered TWRP, it didn't ask me for a password even though I set a pin for my device. When I saw my storage, everything was encrypted.
So do I have to format my storage in order to get decrypted or did I miss any steps? Please advice.
Click to expand...
Click to collapse
It's not your fault. There is a problem with pixel experience 10. Now you have one option. Use a external memory. And install what you want.
If you flas fcrypt disabler, then you have to format your internal storage. Which is disgusting.
Sourab debnath said:
It's not your fault. There is a problem with pixel experience 10. Now you have one option. Use a external memory. And install what you want.
If you flas fcrypt disabler, then you have to format your internal storage. Which is disgusting.
Click to expand...
Click to collapse
Will there be any issues if I connect external USB and install magisk because the whole storage is encrypted?
The Blackholed Gamer said:
Will there be any issues if I connect external USB and install magisk because the whole storage is encrypted?
Click to expand...
Click to collapse
I tried and it's showing me successfully installed. But i can not find any app on my device.
You can try
I need some explanation to make things clear..
1) First and most important. If you want to make a clean install, what you have to wipe? Should you format data also, and why? Format data affects system? Can you format data and still boot into rom? When you format/wipe all, is there something left in the phone? If no, then why still i can see in mount settings, that the folders still have Mb/Gb inside them? What are they? I guess you can';t delete everything from the phone? For example now i am stuck on custom animation bootloop. So there is still data left.
2) Format data make your encrypted or decrypted? Or just removes all encryption and if a) you install a rom you go automatically encrypted, b) you install a rom and flash no_verity you go decrypted?
3) If i go decrypted, the only way to go encypted is to install stock OS and why?
4) When is necessary to have the stock rom flashed in order to flash custom rom afterwards? If you want to install a different android version from the one that you have? Any other reason? Is it necessary to install the whole stock image, or just enough to install firmware + radio?
5) If you wipe/format all, the phone has some firmware,radio,vendor etc stored inside or it's empty 100%?
6) Is it 100% safe to install a TWRP through TWRP?
And now let's say the problem i had. But i think i know where was the problem.. I had installed android pie + xXx no_limits on my oneplus5 and i was decrypted. Some months later i decided to try something else, so i installed an AOSP android 10 version. I just wipe/format system,data,dalvik,cache then flashed rom, gapps, magisk. But i had some bugs on this version, lags and huge battery drain. Also whenever i was booting into TWRP it moved me on Mount --> Decrypt screen.. And i don't know why?
Now that i try to figure i know that the problem was i install a custom android 10 rom, without first installing the android 10 stock rom? In order to get the proper firmware etc? Or what? The instructions for installing the rom are the following, which i followed them 100% :
NOTE:
WE ARE ENCRYPTED (FILE BASED FORCED ENCRYPTION). So if you are unencrypted format data partition or use any no_verity solution you want. We don't support it.
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended). Bluspark twrp recovery recommended.
3. Wipe the System, Cache, and Data (you might need to format the data partition in some cases!).
4. Flash firmware. Actual one is 9.0.11. Download.
5. Flash the ROM Zipfile.
6. Reboot to TWRP recovery.
7. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (optional too if you want a root solution).
8. Reboot and set up your device.
Click to expand...
Click to collapse
The ROM should contain everything you need to enjoy Android Q. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
Click to expand...
Click to collapse
The only system app i restored was the Vanced youtube, but i don't this is the source of my problems.
Thanks in advance!
Guys i think i cleared some things on my mind..
When you install a rom you go encrypted. So you have to FORMAT data RIGHT AFTER installing the rom and then flashing no_verity? Am i right? When you format data do you lose Magisk also?
lazostat said:
I need some explanation to make things clear..
1) First and most important. If you want to make a clean install, what you have to wipe? Should you format data also, and why? Format data affects system? Can you format data and still boot into rom? When you format/wipe all, is there something left in the phone? If no, then why still i can see in mount settings, that the folders still have Mb/Gb inside them? What are they? I guess you can';t delete everything from the phone? For example now i am stuck on custom animation bootloop. So there is still data left.
2) Format data make your encrypted or decrypted? Or just removes all encryption and if a) you install a rom you go automatically encrypted, b) you install a rom and flash no_verity you go decrypted?
3) If i go decrypted, the only way to go encypted is to install stock OS and why?
4) When is necessary to have the stock rom flashed in order to flash custom rom afterwards? If you want to install a different android version from the one that you have? Any other reason? Is it necessary to install the whole stock image, or just enough to install firmware + radio?
5) If you wipe/format all, the phone has some firmware,radio,vendor etc stored inside or it's empty 100%?
6) Is it 100% safe to install a TWRP through TWRP?
And now let's say the problem i had. But i think i know where was the problem.. I had installed android pie + xXx no_limits on my oneplus5 and i was decrypted. Some months later i decided to try something else, so i installed an AOSP android 10 version. I just wipe/format system,data,dalvik,cache then flashed rom, gapps, magisk. But i had some bugs on this version, lags and huge battery drain. Also whenever i was booting into TWRP it moved me on Mount --> Decrypt screen.. And i don't know why?
Now that i try to figure i know that the problem was i install a custom android 10 rom, without first installing the android 10 stock rom? In order to get the proper firmware etc? Or what? The instructions for installing the rom are the following, which i followed them 100% :
The only system app i restored was the Vanced youtube, but i don't this is the source of my problems. Formatting data does not effect system in most cases.
Thanks in advance!
Click to expand...
Click to collapse
1) a clean install involves wiping system, data, cache and dalvik cache. All of these partitions must be wiped in order to remove data things that might conflict with the new software that you intend to flash. Yes, you can wipe data and still boot into your ROM. Yes, there are things still on the phone even after wiping the device, but, the things left behind are in partitions that are separate from what you can actually wipe, these other, separate partitions contain all the other stuff that is essential for your device to be able to function. These parts have nothing to do with the ROM that you are using and have nothing to do with what you have installed in your data partition. TWRP does not wipe /data/media partition(internal storage), /data/media is where your personal user data is stored, such as, photos, videos, downloaded files, data from apps such as games, etc. Basically, /data/media contains things that you have stored that are not apps. Your internal storage will still have all the files and folders that were there before you did the wipe. If you want to wipe internal storage, you have to specifically select your internal storage when you use TWRP to wipe the device, it will not wipe internal storage by default. If you still have a custom animation even after wiping the device, it is probably because the boot animation is in your system partition, that can only be removed by selecting the /system partition when using TWRP to wipe the device.
2) Formatting data "should" remove encryption. No, flashing a new ROM after removing encryption will not encrypt the device again unless you specifically choose to encrypt the device in its settings. Flashing no verity only eliminates issues involved with rooting a device and getting root to actually work without corrupting the device.
3)I'm not sure but I think you can encrypt a device without using stock.
4) It depends on which device you have, what your current firmware version is and what you are trying to flash. Some devices require a certain firmware to be installed before flashing certain custom ROMs but it is a case by case scenario. There is no specific answer to this, there is only the question of whether your specific device requires this or a question of whether the custom ROM that you are trying to flash requires this. This is best answered by reading the thread where the ROM is posted, if your device requires installing a certain stock firmware before flashing the custom ROM, it will tell you that somewhere in the thread for that ROM. Whether you need to install the entire firmware or just parts of the firmware also depends on which device you are using in some cases, you might only need the modem or only the bootloader or maybe both, or maybe none, or maybe the complete firmware.
5) As I stated above, there are partitions on the device that do not get wiped when using TWRP to wipe the device. If it wiped EVERYTHING, the device would no longer function at all, it wouldn't be able to power on, it wouldn't be able to boot into any of its modes and you wouldn't be able to flash anything at all on the device, not even it's original stock firmware. There are software elements that MUST remain on the device in order for it to continue to function.
6) It is perfectly safe to use your existing version of TWRP to flash another TWRP version, assuming the new TWRP is also built for your specific model number.
If you have installed a custom ROM and you are having issues, you need to go to the thread where you got the ROM and post your issues/questions there. The users there will know more about your device and what you actually need to do and the developer may also need to fix things in their ROM to solve the issues that you are experiencing.
Sent from my SM-S767VL using Tapatalk
I have ArrowOS 12 installed, with 11 the updates went well but now if I try to update i get the messages in the title. I tried to repair the filesystem, changed it from ext4 to ext2 and ext4 back again, wipe basically everything, can't restore anything, really have no idea of what I should do more.
TWRP is on 3.5.2_11.0, I have no personal files on the phone so anything is ok.
sherlockhs03 said:
I have ArrowOS 12 installed, with 11 the updates went well but now if I try to update i get the messages in the title. I tried to repair the filesystem, changed it from ext4 to ext2 and ext4 back again, wipe basically everything, can't restore anything, really have no idea of what I should do more.
TWRP is on 3.5.2_11.0, I have no personal files on the phone so anything is ok.
Click to expand...
Click to collapse
All custom recoveries (TWRP, OrangeFox) cannot decrypt Android 12 data in the meantime, so you will not see any internal storage and cannot mount.
If you want your data, you can try ArrowOS 11, restore data into ArrowOS 11, make sure data works in ArrowOS 11 system boot, then flash ArrowOS 12 without format data.
Some said you can do that, but there's chance it will fail, but since your phone has no personal files, you can try.
There is update of TWRP 3.6.0_11.0
pl1992aw said:
All custom recoveries (TWRP, OrangeFox) cannot decrypt Android 12 data in the meantime, so you will not see any internal storage and cannot mount.
If you want your data, you can try ArrowOS 11, restore data into ArrowOS 11, make sure data works in ArrowOS 11 system boot, then flash ArrowOS 12 without format data.
Some said you can do that, but there's chance it will fail, but since your phone has no personal files, you can try.
There is update of TWRP 3.6.0_11.0
Click to expand...
Click to collapse
Thanks man, does this mean there is no effective way to update the OS on android 12 in any way, no custom roms at least? In that case I'm very confused as to why the update button even is there
sherlockhs03 said:
Thanks man, does this mean there is no effective way to update the OS on android 12 in any way, no custom roms at least? In that case I'm very confused as to why the update button even is there
Click to expand...
Click to collapse
Custom recoveries cannot decrypt internal storage, but can read microSD cards and USB OTG. Remember Poco X3 Pro has microSD slot.
You can also use ADB sideload command in custom recoveries to flash zip files, so ROM updates can be installed this way.
Almost all function of custom recoveries are working, except decrypting internal storage.
pl1992aw said:
Custom recoveries cannot decrypt internal storage, but can read microSD cards and USB OTG. Remember Poco X3 Pro has microSD slot.
You can also use ADB sideload command in custom recoveries to flash zip files, so ROM updates can be installed this way.
Almost all function of custom recoveries are working, except decrypting internal storage.
Click to expand...
Click to collapse
alright, thanks a lot, have a good one