Question How to Downgrade from Android 12 to 11? (ArrowOs) - Xiaomi Poco X3 Pro

I am on ArrowOS 12, and I would like to return to ArrowOS 11, because after a while with Android 12, I was not completely convinced, and especially that I had some features in ArrowOS 11 that I do not have in ArrowOS 12.
I really don't know the exact steps to do it safely and I can't find any tutorials about it.
Previously I was on ArrowOS 11, and I did a dirty flash of ArrowOS 12, to upgrade.

chavaa said:
I am on ArrowOS 12, and I would like to return to ArrowOS 11, because after a while with Android 12, I was not completely convinced, and especially that I had some features in ArrowOS 11 that I do not have in ArrowOS 12.
I really don't know the exact steps to do it safely and I can't find any tutorials about it.
Previously I was on ArrowOS 11, and I did a dirty flash of ArrowOS 12, to upgrade.
Click to expand...
Click to collapse
A12 data is lot differant from A11 data, so if you dirty flash you will have a boot loop
you have to clean flash the rom

Related

From OOS 10.0.1 trying to install LOS 16.0 as a beginner and failing completely

I'm trying to install LOS 16.0 but it just won't work. I've tried using the TWRP 3.3.1-16 Q Unofficial by mauronofrio and it works that I can get into TWRP and can flash the rom and GApps, but then after that process once I try to boot into the OS it is just forever stuck in either fastboot or stuck on the bootloader unlocked warning screen. I did realize that I had to use fastboot flash boot twrp*.img because they disabled fastboot boot twrp*.img in the Android 10 update, but then am I supposed to reflash something on that boot partition now? The whole process is very confusing and the instructions from the LineageOS seem to not work at all. Is there anything I can do right now or is it just not possible to install this until TWRP, or OOS, or something I'm not knowledgeable enough to know about updates?
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
TheSproker said:
It's because you are using OOS 10.1 as a base (android 10) and you are trying to install Lineage OS 16 (android 9), so it's quite obvious why it isn't working. Try lineage OS 17 instead.
Click to expand...
Click to collapse
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
remewer said:
Lineage OS 17 won't work either. The developer intentionally used OOS 9 as base since fastboot boot command doesn't work yet on OOS 10. OP needs to downgrade to OOS 9 first, whichever of the two Lineage OS versions they wish to use.
Click to expand...
Click to collapse
I tried this. I downgraded to 9.0.9 and still the fastboot boot command is not working. Apparently this has something to do with the bootloader image itself not being downgraded?
I give up now, my temp phone I was using for holding backups for chat data just randomly wiped itself on havocOS and I've just lost years of chats and stuff and it's got me really down right now. They did fix the fastboot boot issue with today's 10.3.0 update but still nothing is working from any tutorial to get this thing to work on lineage, it just won't boot to it and twrp keeps having errors during flashing. This used to be so much easier on my older phones and I've installed this OS on about 5 phones now but OnePlus 6 just doesn't seem to work no matter what. I'm just going to go back to OOS and hope LineageOS 17.0 will get these issues ironed out by the time it releases. Severely disappointing and a waste of 3 days now but oh well
In my opinion, this is the easiest way to downgrade everything to OOS 9, including bootloader https://forum.xda-developers.com/oneplus-6/how-to/op6-collection-unbrick-tools-t3914109
After that, just unlock the bootloader again like usual and follow the LOS16/17 page's install instructions and you should be good to go.
I tried to install Havoc 3.5 while i was on 10 Ob2, unlocked bootloader and installed patched twrp, then rom. Got stuck in fastboot mode. **** hell i messed everything, later i found fastboot recovery rom from xda, flashed it, thank god it saved me. For me, msm tool was not getting connected, got an error like sahara xyz something... Then after refering to multiple xda threads came to know that most of the present 10 custom roms are based on oos android 9. Then again i used downgrade package from community, reverted back to ob 25 oos (pie), then as usual installation process. So if you are interested in custom roms, downgrade to pie. And again i wanted to go back to complete stock from havoc but unfortunately msm was not responding and fastboot roms wont support upgradation (im not sure), i went to twrp and installed stable 9.0.9 to both partitions + twrp installer. Then 10 oos stable to both partitions + twrp. Then booted up and installed Ob2 again from system updater, lost twrp on that process, then locked bootloader, so mow completely stock ? lot of work for nothing ? oos is better for me.. infact i got used to that. maybe i should purchase another phone to continue the momentum of getting latest updates. crazy oos influence ?

Install LineageOS on an Android 12 device?

My Pixel 4a is currently running the Android 12 beta. I understand that if I install LineageOS, it would go back to being based on A11, as there is no A12 LineageOS yet. However, am I able to go straight from A12 to Lineage, or do I need to flash stock A11 and from there install Lineage?
The safest choice is probably flashing back to stock A11 before installing lineage.

Cannot Install Lineage OS 18.1 (Nightly Jan 11th 2022) using the official installation method from Lineage WIki

I'm on Stock OOS 11 with all the latest firmware installed and no more updates from oneplus.
So I tried to flash lineage os 18.1 on my Oneplus 6 (enchilada).
I followed every step, unlock bootloader, flash lineage recovery to boot and use lineage recovery to copy partitions and install lineage os
and open gapps.
But when I reboot finally I get stuck in the Lineage OS boot animation. Can't get past that even after 2+ hours. Tried to reflash many times
with the same procedure.
Finally I gave up and used MSM Download Tool to get back to stock OOS 10 and then updated again to the latest version of OOS from oneplus.
Now what should I do different, to install Lineage OS 18.1 in my oneplus 6(enchilada)?
SOLVED:
The latest nightly has a major bug hopefully the future release may fix it. Until then use 220104 nightly and don't update through OTA.
Wait until next build comes with the reverted commit.
Revert "adbconnection: don't spin if adbd isn't running." Breaks boot for many devices.

Question How do I install a custom rom coming from xiaomi eu?

I am using my poco x3 pro with mi eu as my daily driver; however, duplicate apps still reign supreme and the default mi music app doesn't get recognized in Android Auto.
I have dabbled in custom roms before, a couple times but most of them have stopped me from completely using the phone normally, namely broken camera support with drive doesn't recognizing the camera (even with gcam, don't @ me), slow document viewer and so on. As such, I generally refrained from using them, until I saw Crdroid 8 with MIUI cam, which seems like the best of both world for me.
The guides on the thread are too vague? And Im not sure about updating (the rom required a custom recovery image, however, my recovery is too old and i don't want to risk my phone getting bricked)
Can someone help? Thanks a lot!
bump
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
AmmarHaseeb said:
Boot to twrp
Format data
Wipe data, dalvik, cache
Install latest firmware - https://xiaomifirmwareupdater.com/firmware/vayu/
Install ROM
Flash Gapps
Format data
Click to expand...
Click to collapse
Does this erase the internal storage? I don't have an SD card and a usb otg
BreadGyarados said:
Does this erase the internal storage? I don't have an SD card and a usb otg
Click to expand...
Click to collapse
I already got that figured out
BreadGyarados said:
I already got that fig
Click to expand...
Click to collapse
BreadGyarados said:
I already got that figured out
Click to expand...
Click to collapse
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
irmas5 said:
Flash latest twrp, or orangefox recovery. On A11 android you can put rom zip to internal storage and flash from there, on a12 you need sideload rom, because recovery still not support encrypting storage.
Click to expand...
Click to collapse
I see!
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
BreadGyarados said:
does twrp support cross android versions? Like can I dirty flash one of the update (a12)? The crdroid og thread mentioned sth about a12 custom recovery
Click to expand...
Click to collapse
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
pl1992aw said:
All custom recoveries cannot decrypt Android 12 yet.
So you cannot see internal storage in any Android 12 ROM if your phone is encrypted. This will cause difficulties in dirty flash Android 12 systems.
What do you mean cross Android versions? MIUI to CrDroid 12 ? CrDroid 11 to CrDroid 12? CrDroid 12 to CrDroid 12?
It is better to do clean flash than to only dirty flash when you are crossing different OS and different Android version to prevent bugs.
Click to expand...
Click to collapse
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
BreadGyarados said:
What I meant cross android versions is that miui eu running android 11 to crdroid running android 12, as the device has no official android 12 support.
I know that I need to clean flash the roms as a first time installation, but current twrp supports android 11 (check it on mifirm).
Click to expand...
Click to collapse
The deciding matter is the Android system currently installed in the phone.
Your example is MIUI.eu with Android 11, in custom recoveries should be able to see internal storage.
[Phone is now Android 11]
After you install CrDroid Android 12 and boot, then custom recoveries cannot see internal storage if it's encrypted.
[Phone is now Android 12]
If you revert from CrDroid Android 12 to MIUI.eu Android 11 and boot, then custom recoveries should be able to see internal storage again.
[Phone is now Android 11]
If your phone is now Android 12, when you want to install something or flash/update a ROM in custom recoveries, it will be a bit complicated as mentioned earlier. You have to sideload with commands.
If you have microSD cards in the phone or USB OTG, then custom recoveries should be able to read them even under when phone is Android 12.
Whether ROMs can dirty flash or not, you have to read the ROM thread and replies (or Telegram if there is no XDA thread), especially replies by the developer.
Some version cannot be dirty flashed, even if it's by the same developer.

Go back to EMUI in Huawei devices

I have Huawei Y9 2019 with unlocked bootloader running Pixel Experince Plus 12.1 and I want to go back to EMUI 9.1 because I saw in some threads that I need to have EMUI 9.1 Firmware installed and kernel 4.9.148 to run Android 13 GSIs but I am worried because I heard that flashing EMUI will lead to relock bootloader (Whatever the method, official or unofficial). Is this true? if so, how can I go back to EMUI without relock bootloader?
Check wether phone is Project Treble ready - what is required to flash GSIs. BTW: Android 13 GSIs ( experimental ) are available since February 1, 2023.
jwoegerbauer said:
Check wether phone is Project Treble ready - what is required to flash GSIs. BTW: Android 13 GSIs ( experimental ) are available since February 1, 2023.
Click to expand...
Click to collapse
My phone is already supports Project Treble, I just want to go back to EMUI 9.1 (Last time was EMUI 9.0 before bootloader unlock). They say EMUI 9.1 with kernel 4.9.148 required to run Android 13 GSIs, Android 12 GSIs and below work well without any issues on my phone.

Categories

Resources