Question TWRP Unable to mount /data/media/TWRP/.twrps + 0 Mb storage - Xiaomi Poco X3 Pro

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

Related

Get rid of Stock ROM's encryption

Hey guys just want to know if there's a way to avoid samsung encrypting the internal storage. I know there's the no-verity-opt-encrypt but I read even if I flash that and proceed to root with magisk the internal storage will be encrypted anyways. I'd like to have it encryption free with magisk without having to go for a custom rom. Is that possible?
soarespt said:
Hey guys just want to know if there's a way to avoid samsung encrypting the internal storage. I know there's the no-verity-opt-encrypt but I read even if I flash that and proceed to root with magisk the internal storage will be encrypted anyways. I'd like to have it encryption free with magisk without having to go for a custom rom. Is that possible?
Click to expand...
Click to collapse
You cannot i'm afraid it's part of the stock image, the applicable files are weaved throughout the stock firmware, no one has been able to break Samsungs encryption on a stock image or turn it off.
Wiping internal storage is the only way to get rid of it, Hence the TWRP method of wiping internal storage then flashing a custom Rom.
Yeah last time I formated data, got magisk installed right away. But of course months later I want to install some module and get the can't mount data error. So that means i'd have to "format data" on twrp and get magisk and the module installed before the first boot, right?
soarespt said:
Yeah last time I formated data, got magisk installed right away. But of course months later I want to install some module and get the can't mount data error. So that means i'd have to "format data" on twrp and get magisk and the module installed before the first boot, right?
Click to expand...
Click to collapse
Possibly but if i remember correctly there's a modified version of TWRP which can handle the encrypted internal storage they way you want.
https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
cooltt said:
Possibly but if i remember correctly there's a modified version of TWRP which can handle the encrypted internal storage they way you want.
https://forum.xda-developers.com/showpost.php?p=77296102&postcount=1243
Click to expand...
Click to collapse
Tried to install that one but yeah still can't mount data. Edit: Well not sure if it was the twrp change or so but now managed to be able to install the module but from magisk itself. Thanks!

TWRP differences/limitations in Android Q

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.

TWRP 3.3.1 encrypted storage after installing Pixel Experience ROM

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

Question Poco x3 pro after update to miui 13 (android 12)

Hello! I have this problem after updating to miui 13. Orange fox recovery started bugging. when I want to enter the sd card, there is nothing empty there. Even all root folders became empty, I tried flashing recovery but nothing worked. I think there are people among you who have experienced these.
Zhanbo554 said:
Hello! I have this problem after updating to miui 13. Orange fox recovery started bugging. when I want to enter the sd card, there is nothing empty there. Even all root folders became empty, I tried flashing recovery but nothing worked. I think there are people among you who have experienced these.
Click to expand...
Click to collapse
Custom recoveries (TWRP, OrangeFox) cannot decrypt Android 12 internal storage at the mean time.
You will need MicroSD card or USB OTG.
pl1992aw said:
Custom recoveries (TWRP, OrangeFox) cannot decrypt Android 12 internal storage at the mean time.
You will need MicroSD card or USB OTG.
Click to expand...
Click to collapse
Thanks for answering

Question TWRP Doesn't Show Internal Storage

Getting tired of the buggy MIUi 13 so I'm trying to install a custom rom on my phone. But when I'm in TWRP to flash rom, it doesnt show my internal storage and it shows what I suspect are root android folders. Any way to fix this? Thanks!
in Android 12 the data partition in TWRP can not be decryptet, if you search, you will find the infos yourself. You can format the data partition, but all stored data will be lost then...
borisku said:
in Android 12 the data partition in TWRP can not be decryptet, if you search, you will find the infos yourself. You can format the data partition, but all stored data will be lost then...
Click to expand...
Click to collapse
I tried doing that, but It still cant detect my internal storage. Also tried using a USB OTG but TWRP still don't detect it. Is there any way to flash rom using pc? If there's none I'll just give up lol
dnleet said:
I tried doing that, but It still cant detect my internal storage. Also tried using a USB OTG but TWRP still don't detect it. Is there any way to flash rom using pc? If there's none I'll just give up lol
Click to expand...
Click to collapse
You can just adb sideload rom.
irmas5 said:
You can just adb sideload rom.
Click to expand...
Click to collapse
Thanks for the reply bro! But from what I learned from @borisku that android 12 has strict storage encryption. So what i did was downgrade to an older version of miui that runs android 11, and after that flash the rom i was changing to.
dnleet said:
Thanks for the reply bro! But from what I learned from @borisku that android 12 has strict storage encryption. So what i did was downgrade to an older version of miui that runs android 11, and after that flash the rom i was changing to.
Click to expand...
Click to collapse
You don't need to have a recovery that can decrypt android 12 internal storage to use adb sideload. Hence, even if you are using MIUI 13 and TWRP, you can just adb sideload the custom rom directly without the need to downgrad to android 11.
JSGuangco said:
You don't need to have a recovery that can decrypt android 12 internal storage to use adb sideload.
Click to expand...
Click to collapse
I'm not familiar with ADB sideload so I didn't use the method, but thanks for the info! I'm running Pixel Experience on my phone right now so my problem is basically solved.

Categories

Resources