Question PROBLEM INSTALLING ARROWOS - Xiaomi Poco X3 Pro

Hi
I installed ArrowOS and when I try to go back to TWRP, there isn´t any password even tho I have one on my device.
The thing is that when I enter it shows that there isn't any storage in the phone (0mb - imposible) so I can't wipe all data nor install other ROMS because it isn't reading the internal storage.
Does anyone know how to solve this problem? It doesn't matter if I have to factory reset or delete all data, or install another ROM, but knowing that it is not a cable problem, I would like to know if I should use other TWRP version (and how to do it) because I can't even seem to do that.
The tutorial I installed the ROM was this, but instead of ArrowOS11, the 12 in my POCO X3 PRO:

Most likely using incorrect / old TWRP. Use https://twrp.me/xiaomi/xiaomipocox3pro.html
Edit: Android 12 ROM's cannot be decrypted yet.

So should I just wait? Thanks for the fast reply!

No recovery can decrypt android 12 data yet.
You can still format the said data though and if twrp doesn't allow you to do so, try using orangefox instead.
You also can install or update rom and other stuffs (that doesn't access data) via sideload.
If you want to install magisk then you need to do the boot.img and related thingy.

Is there a recovery to decrypt android 12 data yet? I've been trying decrypting since 2 months ago and didn't find any answer.

Did you try Orangefox?

Toflamo said:
Is there a recovery to decrypt android 12 data yet?
Click to expand...
Click to collapse
No

borisku said:
Did you try Orangefox?
Click to expand...
Click to collapse
Wouldn't make a difference, it's a limitation faced by all custom recoveries and OrangeFox is based on TWRP.
@Toflamo You can try flashing a ROM from the SD Card or ADB sideload, but the SD card flash would less of a hassle. None of the recoveries as of now support decryption, might take a while to overcome that limitation.

Ngl I don't know how to ADB sideload and don't have any SDs rn to flashing it, so it seems I would have to wait until some recoveries can do it. From now on I'm staying with ArrowOS12 on my PocoX3Pro, even tho battery performance isn't as good as I expected.
Thanks so much everyone, you've been very helpful!
I will come back in some months to check if there is any tool to overcome the decryption problem of Android 12.

Related

A/B slot questions

I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..

Oneplus 7 Pro Bootloop after overlay install, still booting into recovery

Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Bxperiaz3 said:
Hi guys. Really need your help. Oneplus 7pro ,european version running 10.0.4 software, latest magisk 20.4 i think? and twrp. Everything was running fine until earlier when I installed a system ui overlay (one i've used before) and now my phone is in a boot loop. I can access TWRP, I've run the substratum overlay uninstaller zip and removed all magisk modules but still i'm in a bootloop. I've never had a proper bootloop before and i'm very frustrated. I've googled for the past few hours and removed everything I can think of that could be causing issues. Does anyone have some advice that doesn't end with me losing all my data? I have a backup but its from a month ago. I've never had this issue before so i'm a little stuck. Thanks
Edit. Phone is fully accessible through my laptop I can see all my files and connect to it. I just cannot get it to boot,surely its a simple fix?
Click to expand...
Click to collapse
Can you boot in TWRP? if can try changing slot and boot from it
Mervingio said:
Can you boot in TWRP? if can try changing slot and boot from it
Click to expand...
Click to collapse
Hi,yes I can. Its loading the logo now so i'll wait and see what happens. If that works then what should be the next thing I do?
Edit: Slot B seems to be bootlooping on the logo unless its meant to take a few minutes
Is there a way to recover without wiping my data?
So slot A sits on the caution device rooted screen then defaults to the fastboot rescue mode which allows me to select reboot to recovery which is twrp. From there I have full access to the phone but still not booting to system. Slot B passes the fastboot screen and hangs on the one plus logo just circling around. This is my first rooted phone and I haven't had any problems until now so I'm hoping its something simple because I didnt do anything big to cause it. Hopefully someone has some insight.
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Bxperiaz3 said:
Can I just sideload the current version of OOS i'm running using TWRP and not lose my data?
Click to expand...
Click to collapse
Yes
MrSteelX said:
Yes
Click to expand...
Click to collapse
Will I lost root or relock the bootloader? I'm trying to find the least destructive way to get back to what I had which was oos 10 with twrp and magisk.
Uninstalled magisk and was able to reboot. However reflashing it as i want to retain root makes it bootloop again. Any possible fix for this that isn't a factory reset and reroot?
I can't get substratum or substratum themes to work on any rom or stock, nothing happens after reboots.....or everything turns this weird orange theme. Then one time it corrupted the whole OS and I had to wipe.
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
i6rb said:
try to Dirty flash the same Oxygen version
it will not Wipe your Data or internal storage
Click to expand...
Click to collapse
Thanks, i'll try this. Will I need to install TWRP again once I do this or is it unaffected?
Tried to dirty flash the same stock rom from TWRP but I don't think it did it properly. Can I dirty flash stock rom, flash magisk then try reboot to system?
Any help greatly appreciated.

Question slot trouble

Hello
I have a problem tying to install any custom ROM in TWRP slot error appears and it says rebooting to recovery will change the SLOT, I have tried everything I know WIPING DATA , reinstalling the TWRP and many other things w/out success, is there anybody able to assist me on this matter, I was running CR DROID then changed to PIXEL and since the problem started I had to reinstall original MUI 12.5 which I don' like at all..
Advanced thanks
CHEERS
This phone doesn't even have A/B partitioning, are you sure you have correct TWRP and flashing correct ROM for this device?
TWRP: https://androidfilehost.com/?w=files&flid=324966
k3lcior said:
This phone doesn't even have A/B partitioning, are you sure you have correct TWRP and flashing correct ROM for this device?
TWRP: https://androidfilehost.com/?w=files&flid=324966
Click to expand...
Click to collapse
yes I read that in another FORUM but gives me that error I've flashed 1000000 roms bricked unbrick and never faced this problem
P.S ıam USİNG the same TWRP NEBRASSY

Question How to update Custom Roms using OTA?

I'm using a Custom Rom but when there-'s an update I download the new Rom, using OTA process. It enters in the recovery but I can't update it. What is wrong? If i Try making a dirty flash inside the recovery my Smartphone gets encripted. Can someone help me?
For many custom ROMs, the so-called OTA is just using recovery to dirty flash what OTA downloaded and everything should be Okay. I never found my data gets encrypted after the update. Maybe u could check the log if there's some update that needs a clean flash.
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
As the first reply said, at least in the Roms I use, it just downloads the zip, reboots in twrp and flashes it. It worked pretty good in Havoc-Os
TioCareca said:
You had you rom flashed with DFE?
If yes you need to flash DFE zip after rom before booting.
Anyway it's supposed a rom encrypt data, but if recovery can't decrypt data you going for a bad time, last twrp has working decryption ...
Or you talking about something else?
Please provide more details....
Click to expand...
Click to collapse
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Fmeyen said:
I'l try to explain in details what my problem is.
I was on Havoc 4.8 and the 4.9 came out. I entered config, selected System and Update. It showed me the new Rom to download. That's what I did. It was downloaded perfectly and then asked me to continue. Só I pressed the button and it entered TWRP (35.2 Nebrasy) and there I was. Stopped in recovery and no other process was going on. Should I have chosen Install, the rom (probably in download folder)?
I was thinking it should have done the whole process autmaticaly, as it always did using Miui Rom.
So, that's my problem. Thanks for your help.
Click to expand...
Click to collapse
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
DarthJabba9 said:
If your phone is not encrypted, then I don't think that the automatic OTA update (which uses an openrecovery script) will run. You will need to install the update manually, and your device will probably be encrypted when the ROM boots (unless you disable forced encryption).
Click to expand...
Click to collapse
When I install the new custom rom i usually flash DFE. So, by your words, it is not encrypted. If so, I'll run it manually as I prefer not to have an encrypted rom. Thanks for your support.
Could you please explain the correct steps to make a proper dirty flash in X3P? Asking this 'cause this smartphone needs a format data.

Samsung Galaxy A7 (2018) - Storage still encrypted on next reboot after wiping internal storage

I flashed TWRP recovery on my Samsung Galaxy A7 (2018). I wiped internal storage, and it worked fine; the storage was decrypted. Later on, I flashed Magisk 21.4 (I can't flash newer versions, or else the phone bootloops) and rebooted into system. Everything went perfectly while setting up the phone. But when I proceeded to go into recovery mode again, the storage was encrypted (0 MB). Which meant I would need to wipe my phone again. I tried a lot of stuff already, such as:
flashing DFE; now It's deprecated, so that didn't do anything
rebooting to recovery after wiping the storage
changing my custom recovery (I chose OrangeFox Custom Recovery, but it also didn't work)
Too bad there are NO official custom roms designed specifically for this model. None. Not even recoveries. Only GSI images. So I'm using an unofficial TWRP version 3.2.3-1.
TL;DR: Storage is still encrypted after wiping it on the next reboot.
Is it somehow possible to permanently decrypt the storage or is my phone a lost cause?
I followed this guide and haven't encountered any problems so far. I highly recommend to follow all steps (Step 1 - 27) to avoid any issues. I think the solution you need is to Format Data and then flashing Magisk + DFE, this got rid of Enforced Encryption for me. Hope this helps, have a nice day.
Futazaki said:
I followed this guide and haven't encountered any problems so far. I highly recommend to follow all steps (Step 1 - 27) to avoid any issues. I think the solution you need is to Format Data and then flashing Magisk + DFE, this got rid of Enforced Encryption for me. Hope this helps, have a nice day.
Click to expand...
Click to collapse
I will try when I get home, thanks.
Dude, you deserve a coffee, beer, whatever you fancy! Thank you soooooo much!!! It appears I flashed wrong DFE. Anyways, it works now. Thanks a bunch!

Categories

Resources