Database Develop

[Q] 5.1 ZIP decrypt, no wipe

Is it possible that there will be no wipe update 5.1 ZIP with no encryption? Works like OTA.
I'd like to update from 5.0.1 (no force encryption) to 5.1 without loosing my data. The best for me is zip for TWRP

Well if backup everything in twrp to an external flash drive then it shouldn't be an issue. I know people have side loaded the OTA via ADB but it hasn't been working for everyone. You obviously can't take a normal OTA if you are rooted so you could try that. Alternatively I would download Parcel if you have root and backup all of your apps and data for each one that you don't want to lose then transfer it to an external drive so you don't lose it when flashing the updated images. From here you can install 5.1 and then simply restore all of your missing apps and data using Parcel. It works really well and much better than TiBu for restoring data in apps. I use both TiBu and Parcel for different things. The above is only if you can't find any alternative ways to get it loaded in TWRP

There's a stock based ROM in dev forum. Flash that followed immediately (without booting) a kernel with no force encryption such as elementalx and you'll be good.
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU

rootSU said:
Or just fastboot flash a system image followed by immediately boot into recovery, flash kernel and SuperSU
Click to expand...
Click to collapse
So what if we wanted to, coming from encrypted, decrypt without a wipe?

drinfernoo said:
So what if we wanted to, coming from encrypted, decrypt without a wipe?
Click to expand...
Click to collapse
nope. your internal storage meeds to be reformatted. save on a computer anything you would need.

Can not install anything custom anymore, dm-verity gets triggered

Hello,
I have always been on root but somehow something changed.
Since I tried to flash the newest stable stock (5.0.1), nothing works anymore.
No matter if I flash dm-verity disabler, supersu or magisk, dm-verity gets triggered everytime and my phone just says "decryption unsuccessfull" and won't boot.
I've tried everything to fix this, including: different versions of supersu/magisk, reflashing TWRP recovery, even going completely back to stock, locking the bootloader and everything.
Also I read somewhere that you can flash dm-verity disabler and wipe data to completely remove the encryption, but TWRP showed an error message, something like "failed to wipe, cannot mount /data".
In the end I got stuck with no ROM and I couldn't even access stock recovery anymore because it had the weird password bug, so I had to use the unbrick tool to get it working again.
Can someone tell me what I'm doing wrong?
I have always been on root since the early Nexus 5 days, but now I feel really stupid because I must be missing something obvious, so thank you in advance for any help.
Cheers

What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?

If by chance you are trying to flash OpenBeta 21, I have yet to avoid my data getting encrpyted when trying to flash. And personally, I must have been doing something incorrect ever since I got the phone, because almost every time I've flashed a stock OxygenOS ROM I have triggered encrpytion. In my situation it never seemed to matter if I flashed Magisk, SuperSU, a custom kernel, or even just a modified boot.img along with the disable encryption file... I don't know the steps you're taking, but what I do is this: once I get the "Encryption Unsuccessful" message when trying to boot, I just reboot to fastboot and type "fastboot format userdata". And since flashing stock OxygenOS usually overwrites TWRP with the stock recovery despite my best efforts to avoid it, I tend to go ahead and flash TWRP while I'm booted into fastboot. After, I boot into TWRP; at which point encryption has been removed, yet the total amount of storage available to me is less than 30GB (I have the 128GB model.) You have to go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data. That restores my device back to 111GB free of 113GB. I then transfer over and flash Magisk and whatever other mods I wanted. After that my device is no longer encrypted and works just how I want it to. Hope that helps with your issue.

What rom are you trying to install and what magisk version are you trying to flash over your preferred rom?
Click to expand...
Click to collapse
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
go to Wipe, then hit the button on the bottom-right, "Format." Type "yes" in the box and format data.
Click to expand...
Click to collapse
When I tried to do that, it just told me "cannot mount /data" and wipe failed...

kaeptn1 said:
The newest stock ROM, so this/.
Magisk is also just the newest version (15.3).
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're not using Blu Spark 8.61 TWRP, then I suggest you install it and try again.
If all else fails, do as @lordcheeto03 suggested and format userdata in fastboot - but note that this will completely wipe your data, including internal storage. Then install TWRP, then flash 5.0.1 and anything else you want.
Sent from my OnePlus3T using XDA Labs

kaeptn1 said:
When I tried to do that, it just told me "cannot mount /data" and wipe failed...
Click to expand...
Click to collapse
If you're getting the encryption unsuccessful error, I don't think you format data in that manner, you gotta use fastboot and fastboot format userdata to remove encryption THEN boot into TWRP to do that.

unable to flash twrp.

I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.

shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later

Sudhanshu030299 said:
fastboot erase recovery
fastboot flash recovery twrp.img
thank me later
Click to expand...
Click to collapse
Are you will it be successful L?

shree alwaz said:
I am have unlocked bootloader. I have recently changed to OB from RR 5.7. Now I am planning to flash rr Oreo. So i was trying to flash twrp since I am on stock recovery. I did fastbook flash recovery twrp. Img and I am getting msg date recovery flashed. But if I go to recovery still it's stock recovery. Can anybody let me know what's the problem.
Click to expand...
Click to collapse
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
If you flashed OOS (stock or OB), then it will always restore the stock recovery after a reboot.
If you want to have TWRP "stick", then you'll have to flash the modified boot image from here https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
The modified boot image turns off the flag that restores the stock recovery.
Click to expand...
Click to collapse
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?

shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Sent from my OnePlus3T using XDA Labs

shree alwaz said:
Do I need to flash modified boot image? Why? Earlier I could able flash twrp without any problem why am I getting that issue now?
Click to expand...
Click to collapse
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img

BillGoss said:
If you are running pure OOS, then the only way to have TWRP not get replaced by the stock recovery is to either use:
- a modified boot image
- a custom kernel
- or use Magisk
This is all tied up with dm-verity. Any of the three options I listed will remove the dm-verity flags that result in overriding TWRP.
Of course you can try just flashing TWRP and see what happens. If it sticks (but I think it won't), good. If it doesn't stick then you've learnt something and you know how too fix it.
Click to expand...
Click to collapse
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk? I am confused what to do?

redpoint73 said:
It depends on the exact sequence you are talking about:
1) If you flash TWRP, than immediately flash a custom ROM (without rebooting), it should then be patched to prevent TWRP being overwritten (with stock recovery). So maybe that is what you did last time. Alternately, immediately rooting (SuperSU or Magisk) or a flashing a patched boot image, will in either case prevent TWRP from being overwritten.
2) If you flash TWRP, then reboot (before flashing anything in TWRP) then in most cases you will find TWRP is overwritten.
However, if you flashed TWRP then immediately tried to boot TWRP but got stock recovery, then something else is going on (TWRP never flashed, and did not get overwritten - you need to reboot the phone for that to happen). Try erase cache and flash TRWP again. Of you can try boot TWRP without actually flashing it, as a workaround: fastboot boot TWRP.img
Click to expand...
Click to collapse
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.

shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
Temporarily boot into twrp with fastboot, copy zip files to memory using MTP (it will activate automatically, when TWRP boots successfully you can see the phone on your PC), flash them in TWRP, profit.
^ assuming you have already made a backup

Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
Or you can flash TWRP in fastboot, then boot directly into recovery (which will be TWRP) and the recover or flash ever ROM you want.
If you restart your phone with OOS installed and TWRP as your recovery, the stock recovery will replace TWRP.
Click to expand...
Click to collapse
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?

shree alwaz said:
Thanks for your prompt reply. I did that and now I could able to use twrp. It's a lesson learned for me.
Moreover, I have doubt that my phone is encrypted and I have not triggered DM-verity. Whenever I boot into my phone first it asks the password then only it will reboot the phone as well as twrp. What should I do to remove it? If I follow the instruction which sent me in your second reply, should I follow that?
Click to expand...
Click to collapse
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
No, keep the on boot password. It's a great security mechanism. It prevents anybody from getting access to your data via TWRP.
Click to expand...
Click to collapse
Boot password is nothing but forced encryption on?

You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Sent from my OnePlus3T using XDA Labs

shree alwaz said:
You got me. I am on open beta with unlocked bootloader. I used have rr nougat. But I flashed back to oos due to some preferences. Now I want flash to rr Oreo. So I am just trying flashing twrp using cmd. After flashing I am just rebooting phone and then I am going back to recovery. Surprise is that I am still having stock recovery. So I am not sure what to do.
Click to expand...
Click to collapse
As you've now figured out, your mistake is rebooting. As I already described, rebooting before flashing root (Magisk or SuperSU) or patched boot image (or custom ROM w. patched boot image) will by definition wipe TWRP. This is normal and expected.
Fastboot flash TWRP. Then in bootloader screen, select recovery, and it should go to TWRP. Then flash one of the above described files to make TWRP "stick".
---------- Post added at 09:25 AM ---------- Previous post was at 09:20 AM ----------
shree alwaz said:
If flash twrp and reboot the phone and then going back to recovery giving stock recovery only. Are you saying I need to flash custom kernel or magisk to get twrp?. My doubt is with out twrp can flash kernel or magisk?
Click to expand...
Click to collapse
No, that is not what he is saying. Yes, you need TWRP to flash a custom kernel or Magisk. Fastboot flash TWRP, then immediately select "recovery" from the bootloader menu and do not reboot the phone.
You don't need custom kernel/Magisk to flash TWRP (that would be a cart before the horse type situation, as you somewhat figured out). But doing so, makes TWRP "stick" and not get wiped (replaced with stock recovery).
---------- Post added at 09:27 AM ---------- Previous post was at 09:25 AM ----------
shree alwaz said:
Boot password is nothing but forced encryption on?
Click to expand...
Click to collapse
Encryption is not the same as forced encryption.
Forced encryption means that if your phone is decrypted, flashing an update will (I believe) "force" it back to being encrypted. For folks that want to stay decrypted, they will want to disable forced encryption. If your phone is encrypted, it doesn't matter if you have forced encryption or not. It will stay encrypyted in either case.

BillGoss said:
You can have encrypted storage with a default password in which case you're not asked for a password on boot or to read the data in TWRP. So then anybody could access the data using TWRP.
But if you have it encrypted and set an on boot password you will also need it to decrypt the data using TWRP.
Click to expand...
Click to collapse
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.

shree alwaz said:
Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
Encryption is always useful if paired with bootup password - in case of theft no one can read your data.
You will be asked for password, if you explicitly set it up in OS.
And what option do you mean?

shree alwaz said:
There used to option in settings menu to disable that. But now I cant able to see that option. Do you know where can I find it.
Click to expand...
Click to collapse
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
shree alwaz said:
And moreover I have little confusion between encrypted phone and setting up boot up password. I thought both are same. If both are not same. Where will be encrypted is useful. I mean when does phone will seek password to decrypt phone. It might be a dumb question but just wanna clarify my doubts.
Click to expand...
Click to collapse
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?

redpoint73 said:
If you change the security option (fingerprint, password or pattern), it will ask if you want to require a boot up password. But it will also wipe your present password, fingerprint, etc.
---------- Post added at 04:33 PM ---------- Previous post was at 04:21 PM ----------
It's a fair question, and I'm not sure I understand all the subtleties myself. But as I understand it (and others please correct me if anything below is wrong or incomplete):
1) Encryption means all your data is essentially "garbled" and cannot be read without the encryption key (for which you need password, fingerprint or pattern). So even if someone can pull some data off your phone (which I think would be hard) they can't read the data.
2) Even if the phone is encrypted, data is decrypted once you boot TWRP. You can literally plug the phone to a computer and read the data. Boot up password prevents this (phone will not boot to TWRP unless you enter the password).
Now a couple questions that still persist in my mind:
3) Is there any point in having a boot up password on a stock device (stock recovery)? If the phone is lost of stolen, it will prevent the person from rebooting the phone. But nothing until they do so. Is there some possible exploit that requires them to reboot?
4) Encryption, no boot up password, with TWRP is not very secure (and therefore not much of a point)? I guess you can rationalize that a thief would have to be pretty tech savvy to know that data can be accessed via TWRP. But certainly possible. If you have TWRP and care about security, is it basically advised to encrypt and have a boot up password?
Click to expand...
Click to collapse
Thanks you clarification. After reading your explanation even I got the same question 3 and 4.

Question How do i get Stock recovery to not replace TWRP when rebooting???

Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.

Helhound0 said:
Tried a bunch of things to make the TWRP installation persistent, but it just goes back to MIUI recovery when i reboot from the system.
I'm using TWRP 3.5.2 by Nebrassy.
USB debugging turned on
Correct drivers installed
fastboot devices work Using minimal ADB and fastboot
I have the file renamed as TWRP.img.
Steps i followed:
fastboot boot "TWRP.img" - Correctly boots into TWRP
install the TWRP image to the recovery partition - Happens with no errors
Reboot to system - No errors there as well
Reboot to recovery - Goes back to MIUI recovery.
Can someone please tell me what i should do?
PS: Tried with TWRP 3.6.0 as well just now. Same issue.
Click to expand...
Click to collapse
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu

Laptapper said:
Try again to flash TWRP dirty and if it's started don't boot with software. You have to boot TWRP again by pressing volume + and power button until you'll get vibration , afterwards you'll be in TWRP again, clear dalvik and cache and restart system via TWRP menu
Click to expand...
Click to collapse
Sorry mate that didn't work. Still going back to stock recovery...

Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?

Helhound0 said:
Sorry mate that didn't work. Still going back to stock recovery...
Click to expand...
Click to collapse
Then you've got to do a flash with stock ROM and miflash via pc

Laptapper said:
Then you've got to do a flash with stock ROM and miflash via pc
Click to expand...
Click to collapse
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?

I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.

romuser87 said:
I used the Disable-Dm-Verity-Zip directly in TWRP after installation. Worked without a problem.
Click to expand...
Click to collapse
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse

Helhound0 said:
I read that somewhere too but that didn't help me at all... Maybe i have a bad zip file..
Can you share the zip you flashed?
Also, any idea how i could get this fixed:
Click to expand...
Click to collapse
The attached file worked for me

Helhound0 said:
Would that re-lock the bootloader? And if so do i have to wait 7 more days for it to be unlocked?
Click to expand...
Click to collapse
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.

HiQual said:
1. With MiFlash there is an option at the bottom of the screen to lock bootloader. Just make sure it is NOT checked, and you will be safe to use MiFlash without relocking bootloader.
2. When installing TWRP for first time, it is essential that your first reboot is straight back to TWRP - then it becomes persistent, and future reboots to recovery will be to TWRP. If you do not do the first reboot back to TWRP, the stock MIUI ROM recovery reinstalls itself.
Click to expand...
Click to collapse
The first ever twrp install i did, i rebooted to system by mistake but i reflashed twrp and made sure to reboot to recovery.... That was the second try. I think i may have tried at least two dozen times since that but it just kept booting back to stock recovery...
I think I'll run with this until the end of Jan and then redo everything from scratch...

Helhound0 said:
Since i didn't find a solution to make the installation presistant, i went ahead and flashed Elixir with the temporarily booted TWRP. Then wiped cache and dalvik, flashed the TWRP image, formatted data and then rebooted. Now it works.
Edit: This method did something to my recovery. I can boot to system and recovery fine but TWRP isn't able to mount the data partition. So i'm not able to flash anything or root the device anymore.
I tried formatting data, no luck.
Then tried repairing the data partition. No luck.
Changed the file system to EX2 and then EX4... Nothing.
Anyone know a solution for this?
Click to expand...
Click to collapse
I'm stuck at this stage. Have you found any solution yet?

Question Device encrypted!

I am unable to decrypt storage in TWRP recovery, I used the device password, "default_password" no password and even tried my xiaomi account password! nothing works! removed all security from the device and tried again, still nothing. deleted everything, flashed again and i was able access phone storage from TWRP but as soon as i booted my phone and set it up it got encrypted again and wouldnt mount. I cannot flash or sideload anything using twrp, even from an external usb stick. I can flash roms that have fastboot script files but I cant even update a rom OTA since it reboots to the stock recovery and that doesnt have the option to update anymore.
how to do i go about and mount storage in twrp? or flash OTA updates? or even create fastboot script files for OTA update packages to be able to install them?
MiSuite also doesnt work since it requires me to update to the latest version.
Im flashing TWRP 3.7
Running MIUI 13.09 EU
thanks!

mokhabarat said:
I am unable to decrypt storage in TWRP recovery, I used the device password, "default_password" no password and even tried my xiaomi account password! nothing works! removed all security from the device and tried again, still nothing. deleted everything, flashed again and i was able access phone storage from TWRP but as soon as i booted my phone and set it up it got encrypted again and wouldnt mount. I cannot flash or sideload anything using twrp, even from an external usb stick. I can flash roms that have fastboot script files but I cant even update a rom OTA since it reboots to the stock recovery and that doesnt have the option to update anymore.
how to do i go about and mount storage in twrp? or flash OTA updates? or even create fastboot script files for OTA update packages to be able to install them?
MiSuite also doesnt work since it requires me to update to the latest version.
Im flashing TWRP 3.7
Running MIUI 13.09 EU
thanks!
Click to expand...
Click to collapse
Check that you are using the latest TWRP, A12 or A13 depending on the rom you want to install.
Normally by formatting the data you can install the rom with the TWRP.
Twrp/wipe format data type yes/reboot twrp/flash rom.
Try to install xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip then update via OTA.

NOSS8 said:
Check that you are using the latest TWRP, A12 or A13 depending on the rom you want to install.
Normally by formatting the data you can install the rom with the TWRP.
Twrp/wipe format data type yes/reboot twrp/flash rom.
Try to install xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip then update via OTA.
Click to expand...
Click to collapse
just check my twrp version its 3.7.0_11 eo im assuming its not the latest version...ill flash the new one and see. i'm trying to get away without a full wipe since ive done that twice already and always end up getting encrypted again right after i install a rom

NOSS8 said:
Check that you are using the latest TWRP, A12 or A13 depending on the rom you want to install.
Normally by formatting the data you can install the rom with the TWRP.
Twrp/wipe format data type yes/reboot twrp/flash rom.
Try to install xiaomi.eu_multi_MI11Pro_MI11Ultra_V13.0.12.0.SKACNXM_v13-12-fastboot.zip then update via OTA.
Click to expand...
Click to collapse
IT WORKED!!! I just booted to the TWRP version you pointed me to and used my device password and the data got decrypted immediately!
Thanks!