Database Info

[GUIDE] Install Any ROM, GApps, Magisk, TWRP, DolbyAtmos and more for Mi A1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello, I've seen a lot of community members struggling to install custom ROMs, GApps, Magisk or DolbyAtmos, so I've created a guide. So did I, this took me around 15 tries without bootlooping or breaking my OS. Yes, I was really new at this. Some guides had broken English that I couldn't understand, others were too complicated.
However, now I am presenting you a fully working, detailed (and easy) guide. Hopefully, it'll help at least someone to avoid potential mistakes when flashing or using root. Good luck!
(If you don't install TWRP, the GApps version will mismatch!)
(Probably not anymore, needs a confirmation.)
All-in-One installation .7z package: (NOW ONLY INCLUDES MAGISK, ADB DRIVERS, RECOVERY AND GCAM MOD. CHOOSE THE ROM YOURSELF.)
GDrive: https://drive.google.com/open?id=1tkkVyuGfv2UYvehsV7cmGi9BQ2msodKY
Mediafire: http://www.mediafire.com/file/y146i4satahiper/updatedFiles-Magisk-Recovery-GCam-ADB.7z
Mega: https://mega.nz/#!B34XmbLD!GzZuJthLWrJbsHqRd_r-wxMKOwvi3fQdGOmWmW0Mtlo
(Extract with 7zip or WinRar before using)
Enabled developer options with ADB debugging enabled (Settings->System->About Phone->Tap 7 times on Build Number, go back, Developer Options, scroll a bit down, Android Debugging - Enabled)
Backup any photos or videos, if needed.
Unlocked bootloader (Open a cmd in the folder->adb reboot bootloader->press Yes if your phone asks for a confirmation->fastboot oem unlock)
1. Open a command prompt in the provided folder
2. Use the command adb reboot bootloader
3. Use the command fastboot boot recovery-3.2.1-2-oreo.img
(Press Keep Read Only)
4. Go to Wipe->Advanced Wipe->Select: Dalvik / ART Cache, System, Data, Internal Storage and wipe by swiping right
5. Copy all files to your SD card/Internal Storage: Twrp-recoveryInstaller-3.2.1-2-oreo.zip, Google_Cam_Fix_for_LineageOS_v1.0.zip (not needed for other ROMs other than LineageOS, or at all), lineage-15.1-20180313-UNOFFICIAL-tissot.zip (or any other ROM file), Magisk-v16.4(1642).zip, open_gapps-arm64-8.1-micro-20180526.zip (Download the newest one at https://opengapps.org, ARM64, Android 8.1, micro)
6. Go to Install->and select lineage-15.1-20180313-UNOFFICIAL-tissot.zip (or any other ROM file) and install the zip file by selecting the file and swiping right
7. Reboot->Switch to the other slot (A->B or B->A) (Not needed on the latest ROMs)
8. DO NOT REBOOT (Just press the Back button)
9. Install Twrp-recoveryInstaller-3.2.1-2-oreo.zip by selecting the file and swiping right
10. Go to Reboot->Recovery and swipe
11. Install->Flash open_gapps-arm64-8.1-micro-20180526.zip by selecting the file and swiping right
12. Reboot or continue to the Magisk installation procedure below to get root access
12.5 IMPORTANT! Press Do Not Install
Your device can take a few minutes to boot
1. Reboot to recovery
1. Install->Flash Magisk-v16.4(1642).zip by selecting the file and swiping right
2. Reboot->System
3. Go to Magisk Manager->Modules->Add->Top right corner, three dots, Show internal storage and find the Google_Cam_Fix_for_LineageOS_v1.0.zip and flash it by clicking on it, reboot your device. (Not needed for other ROMs other than LineageOS, or at all)
(If you can't see your SD card because it is formatted as an adoptable storage, copy the file to the Internal Storage again)​
NOTE: MAY NOT WORK ON MOST ROMS ANYMORE, I USE VIPERFX FROM MAGISK REPOSITORY OR DIRECTLY FROM XDALABS HERE INSTEAD.
1. Copy DolbyAtmos_for_Oreo_20180218.zip and magisk-permissive-script_v1.2.zip to your SD card/Internal Storage (Currently only downloadable from the link below, please check the note just above the step 1)
(Please note that if you have your SD card formatted as an adoptable SD card, you'll have to copy your files to the Internal storage, nowhere else.)
2. Go to Magisk Manager, update it (you might need to install the latest apk by clicking on the INSTALL button, let it update before doing anything else)->Modules->Press the + button, top right corner, three dots, Show internal storage and find the magisk-permissive-script_v1.2.zip, tap on it.
3. Reboot
4. Reboot to recovery (Go to Settings->System->About Phone->Tap 7 times on Build Number, go back, Developer Options, Enable Advanced restart. Now you can simply hold the power button, press restart, tap on Recovery.)
5. Install->Flash DolbyAtmos_for_Oreo_20180218.zip by selecting the file and swiping right
(IF IT ENDS UP WITH AN ERROR->Back, go to Mount and check System) Then try flashing it again.
6. Reboot->System
(OPTIONAL STEPS, USE ONLY IF YOU DON'T SEE DOLBYATMOS AFTER REBOOT)
(In recovery)
7. Reboot->Select the other partition (A->B or B->A)
8. Back->Reboot->Recovery (Swipe to Reboot)
9. Install->Flash DolbyAtmos_for_Oreo_20180218.zip by selecting the file and swiping right
10. Reboot->Select the other partition (A->B or B->A)
11. Reboot System
1. Open Magisk Manager->Downloads->Search for GCam Mi A1 Fix->Tap, install, reboot (Please note that this is already enabled in most ROMs out here)
2. Copy the GoogleCamera-Pixel2Mod-Arnova8G2-V7beta-test-9.apk (from the Bonus folder) to your internal storage
3. Use any third-party file manager, (I recommend total commander) and install the .apk
4. Use the recommended settings:
Open the camera app->Settings->Advanced:
Config Camera HDR+: Nexus 6 Auto (This setting might not be neccesary in the provided GCam version anymore)
HDR+ parameters: Super High
Enable Zero Shutter Lag (ZSL): Enabled
Improve in low light: Enabled
5. Restart the app
1. Open Magisk Manager->Downloads->Modded Pixel2 Launcher->Tap, install, reboot (Optionally, you can install other Pixel launchers. I personally prefer Ruthless Pixel Launcher)
2. Tap on Pixel 2 Launcher
3. Press the home button
4. Always
(This sets the Pixel 2 Launcher as your default launcher.)
At this point - MAKE A BACKUP in TWRP (Boot into Recovery, select Backup, Select all partitions (except storage), Backup)
1. Download the OREO_MAGISK_Xiaomi_mi_A1_DualSpeaker.zip file from the attachment section
2. Open Magisk Manager->Modules->The + button->Find the OREO_MAGISK_Xiaomi_mi_A1_DualSpeaker.zip file->Flash it
3. Reboot
1. Download and install XposedInstaller_3.1.5.apk from the attachment section
2. Open it and click on the Xposed version 90-beta3 (or a newer version) in the INSTALL/UPDATE section
3. Install
4. You'll get an error saying that the device is busy
5. Restart to TWRP recovery
6. Install->Find the Xposed_Framework_(SDK_27)-90.1-beta3_(Systemless).zip (or a newer version) in the MagiskManager folder in the root of your internal storage (/storage/emulated/0/MagiskManager)->Flash the .zip file by swiping right
7. Reboot to system
@abhishek987 - the guide has been inspired by his guide
@mohancm - used his recovery
@talk2indrajit - used his Google Cam fix, used some steps from his guide
@Rajeev - for providing link to the latest LineageOS
@Arnova8G2 - his camera mod has been used in this guide
@sad96 - his fps fix has been used in this guide
@guitardedhero - his DolbyAtmos port has been used in this guide
@lelozerien - for letting me know about the DualSpeaker mod
@ydd0ras - for guiding me through the installation of Xposed
@coda00 - for letting me know about the version mismatch when not installing TWRP
@ravinder0003
OpenGApps taken from: http://opengapps.org
LineageOS taken from: https://forum.xda-developers.com/mi-a1/development/rom-lineageos-15-1-t3757938
GCamMod taken from: https://www.celsoazevedo.com/files/android/google-camera/dev-arnova8G2/
TWRP taken from: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472
DolbyAtmos taken from: https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508 (I've used an older version in this guide. If you are confident enough, you can try the latest one.)
Xposed taken from: https://forum.xda-developers.com/showthread.php?t=3034811
I was writing these steps while actually installing the ROM, so it should work for sure.
I might add guides for installation of other ROMs too.
If you have any issues or questions, feel free to reply to this post.
A newbie tip: If you can't see your internal storage, swipe down the notification bar and change USB Charging to Transfer Files.
Coming from stock Android 8.0? Coming from Android Nougat, 7.1.2? Do you need to reflash your TWRP?
Take a look​
If is anyone interested about the design:
HTML:
https://cooltext.com
Changelog:
HTML:
27/05/18 - Updated the guide and separated the main installation procedure.

Great work!
Thank you for your effort!

@SmallTarzan
Very nice guide. Appreciate it...
I want to ask something.. I am not a LOS fan. I won't flash too. Asking this question for some of my whatsapp friends... My question is...
They have already permanent TWRP installed. So do they need to install twrp installer again? With that A/B slot trick?

Rajeev said:
@SmallTarzan
Very nice guide. Appreciate it...
I want to ask something.. I am not a LOS fan. I won't flash too. Asking this question for some of my whatsapp friends... My question is...
They have already permanent TWRP installed. So do they need to install twrp installer again? With that A/B slot trick?
Click to expand...
Click to collapse
I'm not a developer but I'll try to answer your question as well as I can. By logical thinking and my personal experience, I've came to this conclusion: (Don't take me by word, I might not be totally right!)
If you are coming from stock, Android 8.0, you shouldn't need to flash TWRP again.
If you are coming from Nougat, 7.1.2, you'll need to reflash TWRP again.
If you are coming from other custom ROMs, you shouldn't need to flash TWRP again.
With that said,
I've always reflashed my TWRP with the latest one provided for the ROM I was installing at the moment, just in case.
About that A/B trick, when I was flashing the first LineageOS version, I needed to use the A/B partition trick.
However, in the latest one released on 13/03, I needn't. (I didn't try the version released on 8th March.)

wiping internal storage is necessary?

surajsun22 said:
wiping internal storage is necessary?
Click to expand...
Click to collapse
That depends. First, check if is your internal storage encrypted. If it is, you'll need to wipe it.
There might be workarounds on the forum, but I, personally, haven't tried those, yet.

Thanks for the guide

Sorry, what is bonus folder? And where i can find it?

arjiyunandar said:
Sorry, what is bonus folder? And where i can find it?
Click to expand...
Click to collapse
It's inside the All-in-One package. You can find the download link in the requirements section.

SmallTarzan said:
It's inside the All-in-One package. You can find the download link in the requirements section.
Click to expand...
Click to collapse
Can i download what i need? Without download the whole package? Because the size so big, ?

arjiyunandar said:
Can i download what i need? Without download the whole package? Because the size so big, ?
Click to expand...
Click to collapse
What do you need?

SmallTarzan said:
It's inside the All-in-One package. You can find the download link in the requirements section.
Click to expand...
Click to collapse
SmallTarzan said:
What do you need?
Click to expand...
Click to collapse
Google_Cam_Fix_for_LineageOS_v1.0.zip
fixed_30_60_120fps module_v2.zip
Just that,

arjiyunandar said:
Google_Cam_Fix_for_LineageOS_v1.0.zip
fixed_30_60_120fps module_v2.zip
Just that,
Click to expand...
Click to collapse
Have fun.

SmallTarzan said:
Have fun.
Click to expand...
Click to collapse
Thanks so much ?

Not sure if permissive script is needed for dolby atmos, dolby works well on my MiA1 without this script because this rom is already with permissive sellinux... Thank you for your help, it will sure be helpfull. You should try Dual Speaker mod if you haven't got it on your phone.

Is it alright to flash LOS15.1 from stock Nougat or is it a prerequisite to upgrade to stock Oreo before flashing LOS15.1?
Thanks.

lelozerien said:
Not sure if permissive script is needed for dolby atmos, dolby works well on my MiA1 without this script because this rom is already with permissive sellinux... Thank you for your help, it will sure be helpfull. You should try Dual Speaker mod if you haven't got it on your phone.
Click to expand...
Click to collapse
The magisk's permissive script isn't needed, since LOS 15.1 is already in the permissive state. However, if you'd accidentally/purposely change your SELinux status, the DolbyAtmos would break and you'd possibly face audio issues.
TheMadRuffian said:
Is it alright to flash LOS15.1 from stock Nougat or is it a prerequisite to upgrade to stock Oreo before flashing LOS15.1?
Thanks.
Click to expand...
Click to collapse
There's no need to upgrade to Android 8.0 Oreo first, you delete all files in /system anyway. You can directly flash to 8.1. Don't forget to reflash your TWRP!

I m on LOS 13-03-18 how to install Dolby Atmos separately. Can u please guide me

Rzts said:
I m on LOS 13-03-18 how to install Dolby Atmos separately. Can u please guide me
Click to expand...
Click to collapse
Follow the steps in the DOLBY ATMOS section. Copy required files to your device and start from step 4.
Download the Dolby Atmos and magisk's permissive script here: https://drive.google.com/open?id=1NL_Sq2q05L6RyZQSGsPam3HrGoEoOesY

Be carefull with dualspeaker mod if you use it with dolby atmos.
You must change the volume value manually to 80 maxi (default is 84) in the file...
Read carefully thze original post: https://forum.xda-developers.com/mi-a1/themes/mod-xiaomi-mi-a1-soundmod-dualspeaker-t3741675
You should mention it in order to prevent problems...

[root] ulefone armor 2 - easy rooting procedure [SUPERSU]

Hello mates! What a heck of a problem rooting this fancy brick, right? Not anymore ! The guides available in here are very confusing and lack of simple information. I'm just trying to help.
Special thanks goes to sumec100 who made me into the first steps of this process.
Rooting the Brick
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
- SuperSU: https://mega.nz/#!t2wGDbhL!H07JxlbmLH2tFQD7Frx2BKlJp0AyDthXkbEj6sw4z08 (this one worked out) (Leave it in your SD Card before start the process)
- TWRP ported by Jemmini from 4pda and translated to English by TuksOID. : https://drive.google.com/open?id=1Uwkl_2vqHfXkbLGmF-gKbs63UxVKmw_T
- ADB Driver Installer: http://adbdriver.com/downloads/
- ARMOR 2 Latest Drivers: https://drive.google.com/folderview?id=0B8NC4kBpjQhYdDNhdzdUdTRsRFE&usp=sharing
0) Go into your Ulefone Armor 2.
Settings >About phone > Tap ''build number'' 8 times until you see ''now you are a developer''.
Developer options> OEM unlocking (yes) >USB Debugging (Yes)
After all drivers are installed in Driver_Auto_Installer you downloaded from ulefone.com keep ADB Driver Installer open and plug in your phone on your PC. It will auto detects your MediaTek device. Just click ''Install'' wait until it finishes and close it. Now you are properly connected to your phone.
1) Open ''cmd.exe'' as an administrator.
Type: cd (path you unziped plataform-tools inside SDK tools folder) kind of looking like this: ''X:YOUR PATH\tools\platform-tools''
Put the recovery image you downloaded (I suggest you to rename it as ''recovery'') in ''plataform-tools''
2) Back to the cmd in the way you leaved it do it:
adb reboot bootloader Press Enter. The phone will reboot in fastboot mode. (I suppose you did not shut it down, please don't)
fastboot flashing unlock Press Enter. The phone will prompt you. Read the content of the text if you want. To keep going press ''Volume Up'' DO NOT INTERRUPT THIS PROCESS
fastboot flash recovery recovery.img Press Enter. Now the TWRP will be flashed. Note that I used ''recovery'' as file name.
After the successful flash:
fastboot boot recovery.img Press Enter. TWRP will now start.
3) Unplug your phone.
Your TWRP will show a ''Enter Code'' prompt since your device stills encrypted. Press ''Cancel''
Drag the bar to allow modifications;
Press ''Wipe'' in the main menu;
Drag the bar to do a Factory Reset (THIS IS NOT OPTIONAL);
Press ''Install'';
Select the SuperSU file you downloaded in the above. (I hope you copied it in your SDCard. If you did not, You can plug your phone in your PC, mount your Storage via TWRP, copy the zip file and keep going);
Drag the bar to flash SuperSU zip file (DO NOT select any parameters)
Press ''Wipe Dalvik/Cache''
Press ''Reboot System''
Wait for it.
If you had a successful boot, now your device is rooted. Cheers !
Did your device don't boot in 15 minutes? I'm quite sure you messed up but keep calm, don't panic!
Unbricking the brick
*What will you need:
SPFlashtool: https://spflashtools.com/windows/sp-flash-tool-v5-1728
Latest Ulefone Armor 2 ROM: https://drive.google.com/open?id=0B8NC4kBpjQhYdEJTdTdpazVGQjg
The software is quite of auto-explained. Please, Do not use the Ulefone's SPFlashtool, use the one I provided. (I DID NOT CREATE IT)
Shut off your phone
In SPFlashtool set the ''scatter-loading file'' inside the ROM zip, Click ''choose'' and locate it.
Keep it ''Download Only''
Click ''Download'', SPFlashtool will be waiting for your device. (REMEMBER YOU NEED THE DRIVERS I QUOTED ABOVE FOR ALL PROCESSES)
Plug your phone.
Wait until SPFlashtool say it is finished.
[*]After that your phone is brand new. If you want to try again just go up and follow all steps again (Correcting mistakes, of course)
Known Issues
-Latest Magisk is not working with our Stock ROM. It bootloops.
-Latest Nougat Xposed Module Bootloops our phone too.
Any doubts or corrections please, say it !

TheReal V said:
*What will you need in a first moment:
- SDK MANAGER AND PLATAFORM TOOLS ONLY
Click to expand...
Click to collapse
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO

Have you tried the new ROM that came out last month on needrom?

TheReal V;76285584[FONT="Arial Black" said:
*What will you need in a first moment:[/FONT]
- SDK MANAGER AND PLATAFORM TOOLS ONLY https://developer.android.com/studio/index.html#downloads *end of the page, 132mb archive* (Plataform-tools is attached in case you can't find it)
Click to expand...
Click to collapse
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you

enzovic said:
Have you tried the new ROM that came out last month on needrom?
Click to expand...
Click to collapse
No, I did not. I'm not messing with this system anymore (not enough time ) since I made my last format and root I decided to not try anything else since he is my daily driver and I need it workin 24/7

kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
That's right ! Inside this zip and inside sdk tools folder it should be a plataform-tools folder. If not, tell me !

Daugl said:
The download doesn't contain the platform tools anymore. They have been moved into an extra download:
developer.android.com/studio/releases/platform-tools
Funny thing: I can't quote links because of new account oO
Click to expand...
Click to collapse
You can go ahead and download it. I guess my attach was erased

kaibird said:
Hi,
Thank you for your work
but I could not find the platform tools 132mb archive in the link you provided.
The only download link close to 132mb is the 149mb I found.
Is this the file you were referring to?
View attachment 4550585
Thank you
Click to expand...
Click to collapse
Quick Remember ! Plataform-tools is a tiny folder (15~30mb) The huge one is the sdk tools !!

Hey, everybody ! Plataform-tools is attached again ! You guys can download it again !

hey guys... sorry to comment in the old thread but I followed the guide and... my phone is booting always in the recovery I really don't know what I have to do now lol

Hi,
I have flashed successful the latest Ulefone Armor 2 Firmware from their site h**p://ulefone.com/download/armor2.html
Then I did all the necessary steps to root the phone. But when I first time start the SuperSU app, get a popup message "SuperSU needs to update"
and hit "OK". After a while get this failure:
"SU Update unsuccessful"
Regards...

After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?

rafaelsenna said:
After install SuperSu and press "Reboot System", my phone keeps booting into TWRP.
Can someone help me?
Click to expand...
Click to collapse
Fixed. I restored my original ROM using this this tutorial: https://forum.xda-developers.com/showpost.php?p=74294320&postcount=31
Now, Super SU is installed but is asking for update.

Hi all,
I managed to root my Armor 2 but after that I cannot install Netflix from Play Store. It says that device is not compatible.
Does anyone know if the app is restricted to rooted devices?
Thanks in advance

flashed the wrong recovery now stuck ( I used "one click" program )
phone constantly restarts and gives the following error
"
orange
state your device has been unlocked and can't be trusted your device
will boot in 5 seconds
"
the following video is someone else who has the same problem as me
( I didn't have a camera, so I used another video)
I can't do "fastboot and recovery" in any way. Always gives me this error
https://www.youtube.com/watch?v=LJRqMPtKKX4

The best way to root armor 2
1) copy boot-verified.img from firmware folder to internal
2) install magisk
3) download any update in magisk
4) press install and select "select and patch a file"
5)select boot-verified. Img
6)after operation comlate copy magisk-patch. Img file in download folder to pc
7)flash it with sp flash tool

Bricked after Downgrade to Pie, adb not working, pls help

[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any thoughts please?

I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.

akhilarora666 said:
type "Oneplus 7 Downgrade Firmware".
Click to expand...
Click to collapse
Thank you for your encouraging message.
That article you mentioned says this:
copy the Rollback package to the phone’s internal storage.
Go to device Settings > System > System Updates > Tap on top right icon > Local upgrade > Select the installation zip package > upgrade > System upgrade completed to 100%.
Click to expand...
Click to collapse
But as my screenshot shows, I am not able to boot, so how is that supposed to work?

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
akhilarora666 said:
I have been there. Dont worry I have the solution. You'll have to reset the phone though.
First install the latest Android Q firmware. and start your device.
Im new here, dont know if we can paste external links. But go to google and type "Oneplus 7 Downgrade Firmware". In the results, you will see a link from "getdroidtips.com" Just follow the steps from there and it will give you your android Pie back.
One thing. following those steps, you are installing stock OS that is not from a verified source. Myself being a paranoid, I installed this unverified OS, but once you install Pie back, you can reinstall any Pie OS you want. including the stock from oneplus website, which is what i did.
Good luck! let me know if you are still stuck.
Click to expand...
Click to collapse
That's not possible when you have no os anymore...
who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
Just stay on xda-developers, no need for suspicious off site downloads.
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Or the unbrick tools: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

who ah way said:
Thank you for your encouraging message.
That article you mentioned says this:
But as my screenshot shows, I am not able to boot, so how is that supposed to work?
Click to expand...
Click to collapse
In my case, I was stuck too. So i did "fastboot boot recovery.img" tried both android Q and android pie revocery. (version 70 and 65) (editied versions by mauronofrio) one of them worked. I got into the recovery. then installed the android Q stock firmware zip file. Thing is, i dont know why, but once you are on android Q, your phone stops supporting android PIE. Since you were on android Q once, you have to go back there. only then follow the external website i linked.
Like the other guy said, you can stick to XDA and try the unbrick tools. but for me they didnt work. So i followed that website. then everything was fine. Ofcourse its fishy. but once you are back on pie, you can reinstall any pie rom you want.

strongst said:
You can use fastboot roms: https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
Click to expand...
Click to collapse
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)

who ah way said:
@strongst the fastboot ROMs are only if you're able to see the fastboot screen, not the screen on my screenshot, right? With adb devices not seeing my device, will that work?
(Otherwise I'll look at the MSM download, seems like some Qualcomm drivers must be installed.)
Click to expand...
Click to collapse
Your screenshot is the fastboot screen. Stated with: fastboot
If your device is not recognized, maybe you should check your adb drivers etc.

TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.

who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
Same situation happened to me but due to wipe in twrp vendor image

who ah way said:
[cross-posted on OP7 Pro forum]
- Downgraded to Pie (from Android 10) using TWRP backup
- Boot stuck on screen below
- Selecting "Start", "Recovery mode" or "Restart bootloader" brings up the same screen
- When selecting "Start", Fastboot screen briefly flashes but the screen below immediately appears
- Selecting Power Off does work when unplugged
- Volume Up + Down + Power brings up the same screen
- adb does not see the device
Any thoughts please?
Click to expand...
Click to collapse
You used a nandroid backup which is what resulted in the brick. Nandroid backups do not backup firmware
Anyway try
fastboot --set-active=a
Then reboot and see if it boots
Or try
fastboot --set-active=b
If that doesn't work download twrp and flash it to the boot partition
fastboot flash boot whatever
Reboot and you should have twrp
Which twrp to flash? The one for Q firmware. It's obvious
---------- Post added at 22:31 ---------- Previous post was at 22:25 ----------
who ah way said:
TL;DR OMG. It took all day but I have my phone back (fingers crossed):
- last version of Pie
- system and apps like I had them a month ago (thanks to old backup)
- lost all local files that were stored on the device (photos etc)
Thank you @strongst and everyone who made the tools.
Mmm hey, if you ever see someone like me on the forum who asks if it's safe to downgrade from 10 to 9 using TWRP please rush to jump in and tell them no no no.
Before I completely forget and in case someone else has the same problem, here are the useful steps (I think) of this really long day. Not including all the intermediate steps of failed installs and reboots.
- the phone was no longer showing on the computer's attached devices so had to install some drivers. Drivers were found on mega via Step 1 / 1 of this xda post.
- installing the drivers was a bit of a journey, they're unsigned so you have to enable something in Windows, I used Step 2 of this article which was linked in the above post. After rebooting into that special mode you have to go into device manager, right-click the device which had a strange name, select the cab file, then MS will want to upgrade the driver
- no luck seeing the device using the MSM method (option 2 of strongst's post) so I focused on his option 1, the fastboot tools:
https://forum.xda-developers.com/one...lus-7-t3937478
- downloaded the 9.5.8-GM57BA
- it doesn't work out of the box after unzipping, you have to unzip the zips within the zip and copy the bat and img files to the main folder of the tools
- tried several of the batch files then tried the "if you are badly bricked i recommend to use flash-all-partitions.bat"
- still wouldn't boot, got the Chinese recovery mode screen (vol up down power), from there followed the advice to do English -> Wipe data and cache -> Erase everything
- soon after that I think, the phone booted
- went back to study the original rooting guide
https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
- in particular, enable dev options, then enable usb debugging, advanced boot
- followed steps 8—15 of that guide, for twrp I used the original one I had used
fastboot boot twrp-3.3.1-52-guacamole-unified.img
then flashed versions that I knew were safe
twrp-3.3.1-52-guacamole-unified-installer.zip
Magisk-v19.3.zip
- boot, initial setup, didn't bother filling the google account yet
- boot to recovery, twrp didn't open (stock recovery), adb fastboot twrp again then re-flash twrp and magisk
- still had the latest OOS Pie update, copied to phone storage
OnePlus7Oxygen_14.E.14_OTA_014_all_1907280716_7e28877dd39949e3.zip
- reboot phone, system update, local upgrade
- after reboot, boot to recovery (long press power then select), run twrp, restored old twrp backup from usb
- at that stage my system from a month ago was restored, except files, photos and probably a few other bits and pieces
That's all I have for today, hope no one else needs to follow these steps!
Thank you again to strongst and those you made the tools.
Click to expand...
Click to collapse
I do not know how you formatted cache on a device that doesn't have a cache partition

CN Open Beta Android 10

It haves antirollback active.
CN Thread with info.
Direct Download Drive Mirror MEGA Mirror

Can someone make a tutorial post on how to install it?

souma_rox said:
Can someone make a tutorial post on how to install it?
Click to expand...
Click to collapse
It can be installed by original cn recovery, but i didn't try cause of anti-rollback

I hope they make global one to because its already 6 months with no updates...

is it global or chinese version?

Questafa said:
is it global or chinese version?
Click to expand...
Click to collapse
Chinese version.

Has anyone try whether gapps and twrp work on this rom?

I installed this ROM it has almost all languages, very good ROM only the gyroscope that didn't work
Enviado de meu Pixel 2 XL usando o Tapatalk

The installation's process and some details [TWRP, ROOT, GAPPS]
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
Code:
fastboot oem nubia_unlock NUBIA_NX629J
Code:
fastboot flash recovery [URL="https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482"]twrp.img[/URL]
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Perseo99 said:
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
Click to expand...
Click to collapse
Can I install this on red magic 3s?

does anyone know gyro solution for this ROM just missing that so you can use as daily ROM
Enviado de meu Pixel 2 XL usando o Tapatalk

Hi. I just installed the rom without formatting the phone and the code of the screen lock that was previously 6 figures has become 4 and they are not the first 4 of the previous one.
Does anyone know what it can be or am I going to have to format it?

Questafa said:
Hi. I just installed the rom without formatting the phone and the code of the screen lock that was previously 6 figures has become 4 and they are not the first 4 of the previous one.
Does anyone know what it can be or am I going to have to format it?
Click to expand...
Click to collapse
I don't see another option for your situation
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
akashc3303 said:
Can I install this on red magic 3s?
Click to expand...
Click to collapse
No. it's for RM3... I don't know if there is an android 10 beta for 3S

akashc3303 said:
Can I install this on red magic 3s?
Click to expand...
Click to collapse
For red magic 3s is that ROM https://bbs.nubia.com/thread-2578208-1-2.html
http://romdownload.nubia.com/红魔3S/V3.01/NX629J-update.zip
Enviado desde mi NX629J mediante Tapatalk

Thank you for your useful post. After reading it, I tried the ROM myself, with about the same results. Then I used the unbrick tool to reverse to Android 9.
Things that didn't work for me in the beta:
- Bluetooth kept restarting every 10 seconds, I couldn't use my Bluetooth headset
- Some incompatibility between the ROM and GAPPS, Google Play working only on occasions; after installing some stuff some apps refused to start ( Phone, Settings, Outlook etc).
It was an interesting experience, but it can't be used as the daily driver, at least not for me.

Detection 10 error

hoichemgio9x said:
Detection 10 error
Click to expand...
Click to collapse
What does it mean?

Nightpwish said:
What does it mean?
Click to expand...
Click to collapse
Button touch in YouTube, time screen , etc

Try V3.25
Perseo99 said:
Hey!
I finally install and run the beta on my device. The process is very simple and easy to follow:
1. Get the stock rom on your device without root. You will have to do a full wipe of your data and cache from the Recovery. If you have installed a GSI (as me) you can simply use the Unbrick Tool shared on XDA. After that, just flash from a OTG device in the stock recovery the rom. It should install normally (I did it about three times). Let the device restart normally and configure it.
2. At this point, you will have your device working with the android 10 beta without Google Services and root. To get them, follow the next steps. In the developer's settings enable the usb depuration and reboot into the bootloader menu (if you are here, you don't need a guide to do this).
Once in the bootloader, you will have to type the next commands from a PC:
Code:
fastboot oem nubia_unlock NUBIA_NX629J
Code:
fastboot flash recovery [URL="https://forum.xda-developers.com/red-magic-3/development/recovery-unofficial-twrp-nubia-red-t3962482"]twrp.img[/URL]
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
You can extract the vbmeta.img from the package of the beta.
You should can boot the custom recovery without problems. There is an importante failure at this point. I can't acces to the data of the sdcard of my device. It could be a problem if you flash a wrong module in magisk and you can't delete it from the recovery.
To get the gapps working and root in the device, flash the "pico" package from the open gapps project page and flash the last version of magisk (maybe this could be the cause of the encrypted data in the twrp, I will be experimenting other options (the most evident thing is that the recovery is not the correct ones for this rom).
3. Just reboot the device and enjoy the new android 10 experience on Red Magic 3. You shold be able to proceed to finish the setup and install all the apps you want. The are some things that didn't work for me: some syncs with the google account (Google Keep, Calendar, etc.), auto-rotation (gyroscope), the music notification panel, various notifications, etc. You can't recover your apps and data from a past backup, the rom doesn't give the storage permission to the Google Play Services, so that's the problem. Just install them from the playstore. You will have to reboot one time before use the play store normally.
I hope the developers of Nubia could make a fully working global rom for this great device. Until then, we have this new option to get the best experience of RM3.
Important: If you just don't like the rom and you would like to downgrade to android 9, you will have to use the unbrick tool in order to avoid a softbrick caused by the anti-rollback system. I tried and it works, but after the program finished the unbrick process the phone started to boot into a black screen, only lighting up the led in a green colour. It was strange and I believed that my phone was bricked without possibility to recover it. After a few tries to reboot the device pressing the power button, I was able to boot without problems into the 2.07 global rom europe version.
View attachment 5030877
View attachment 5030879
View attachment 5030881
View attachment 5030883
View attachment 5030885
View attachment 5030887
Click to expand...
Click to collapse
Hey Buddy,
You are on V3.22, Why don't you try V3.25 the latest one and share us your experiences.
I like your review. Thumbs up brother.

V3.25
jlorf7 said:
It haves antirollback active.
CN Thread with info.
Direct Download Drive Mirror MEGA Mirror
Click to expand...
Click to collapse
Could you provide us the latest update v3.25 link?
Thank you.

Development [RECOVERY][UNOFFICIAL][EXPERIMENTAL][ALPHA] TWRP for Galaxy A22 5G SM-A226B

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It took me sometime, but I can now share with you a TWRP with basic functionality. You of course flash at your own risk. I am not responsible for lost warranty, lost data or any other damage to your device.
This Build of TWRP is based on:​
Firmware: A226BXXU4AVB1(Android 11) and A226BXXU4BVF7(Android 12)
TWRP-11 minimal manifest or TWRP-12.1 minimal manifest
Device Tree
Kernel source
Working:​
flash of zips
fastbootd
flashing of GSI images (via fastbootd)
MTP
Not working:​
Probably a lot of stuff ...
What you need:​
Unlocked bootloader.
Odin3 v3.13.1
android platform-tools and device driver.
adb and fastboot
Magisk or GSI depending on what you want to do.
Patience, the device can be very tricky to get to download mode.
How to flash:​Be advised that this build is a work in progress and is not ready as a daily driver. Only flash if you know what you are doing.
Spoiler
First read all points below, without doing anything. Warning, you will lose all your data!
If you are on Android 11 firmware download v1.01.2-alpha if you are on Android 12 firmware download the recovery.tar from here.
You start off in Odin, put recovery.tar in AP slot and the vbmeta_disabled_R.tar in the USERDATA slot, uncheck auto-reboot.
After the flash is completed hold down power + volume down, instantly after device goes Black screen press and hold power + vol up to boot to TWRP
if you didn't get to TWRP, you have to flash again.
In TWRP, go to Advanced → terminal.
Type multidisabler two times.
Now go to Wipe → Format Data (not wipe) → and type yes.
You can boot to system now.
Hot to install Magisk:​
Spoiler
Method 1, Micro-SDCard​
Download Magisk from here, rename the file from .apk to .zip
Save the file to a Mico-SDCard
Reboot the phone to TWRP.
Go to Install → Select Storage → Micro-SDCard. In the file system, choose Magisk-vXX.X.zip and swipe to confirm flash.
You can now Reboot to System
Method 2, sideload​
Download Magisk onto your PC from here, rename the file from .apk to .zip.
Reboot the Phone into TWRP. Go to Advanced → ADB Sideload → Swipe to start Sideload.
On your PC, type in a Terminal adb sideload Magisk-v24.3.zip
You can now Reboot to System. adb reboot system
How to install GSI:​
Spoiler
Go to Wipe → Format Data (not wipe) → and type yes.
Now reboot to fastboot.
Connect the phone to your pc and startup a terminal of your choice.
In the terminal type fastboot flash system name-of-your-gsi-iamge.img (it has to be a .img file, extract .img.xz files do not just rename them).
You should now be good to go and can reboot to system.
Thanks and credits to:
cheese-ass
akhil99
TeamWin

How to get TWRP log files:​recovery.log
adb pull /tmp/recovery.log
OR
Advanced -> Copy Log -> Swipe to copy log to default storage
dmesg
adb shell dmesg > dmesg.log
OR
Advanced -> Copy Log -> check "Include kernel log" -> Swipe to copy log to default storage
logcat
adb logcat -d > logcat.txt
OR
Advanced -> Copy Log -> check "Include Logcat" -> Swipe to copy log to default storage

Changelog​v2.00.1-alpha​
bump firmware and touchscreen drivers to A226BXXU4BVF7 and TWRP to TWRP-12.1
v1.02.2-alpha​
added drivers for himax touch screens.
v1.02.1-alpha​
added drivers for novatek touch screens.
v1.01.2-alpha​
added patch with improved multidisabler
v1.01.1-alpha​
update multidisabler
v1.01.0-alpha​
fix permission for mkbootimg
v1.00.0-alpha​
Initial Release

This has been tested, right? If it does work, I'll probably try it out when I have free time, which might be in a few days.

Yes, it runs on my A22 5G.

Could-Chaplain said:
Yes, it runs on my A22 5G.
Click to expand...
Click to collapse
It worked. But I didn't read your post carefully and now I have to format data :/
Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.

Edit: Ran multidisabler twice. On the second time, it said that /system was an invalid argument
Click to expand...
Click to collapse
It's the same for me, but no issues so far.
Edit2: Trying to mount partitions don't work, like trying to make a backup or using the file manager. Speaking of backups, I didn't format data because I really don't want to, and it rebooted safely (Thank god), so now I'm making a backup of apps I should have made a week ago.
Click to expand...
Click to collapse
That will be because you didn't format data. If I find sometime, I will try to reproduce that. Thank you, for testing.
Edit: Backups should work fine if you uncheck data?

Is the A226BZH3AUL1 suitable？

a0963655966 said:
Is the A226BZH3AUL1 suitable？
Click to expand...
Click to collapse
If your device is a SM-A226B you should be fine. But as always, flash at your own risk.

Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?

Thank you! Going to test asap.

lebigmac said:
Works great! Thanks! Keep up the good work!
Any idea why adb shell doesn't work? For the same reason why /data isn't mountable?
Click to expand...
Click to collapse
/data is most likely not mountable because you didn't run multidisabler twice and formatted data? ADB shell works fine for me, check in device manager that it shows up as ADB Interface.

Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?

koosman911 said:
Tested working, but haven't succeeded flashing a gsi yet, phone reboots and then goes to blank black screen, and ideas?
Click to expand...
Click to collapse
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.

Could-Chaplain said:
Honestly, it could be everything. Just go over How to flash again. But this time without vbemta and multidisabler. Then continue as described in How to flash GSI. Please let me know if that works for you.
I recommend Pixel Experience.
Click to expand...
Click to collapse
Are you using pixel experience on your device currently?

koosman911 said:
Are you using pixel experience on your device currently?
Click to expand...
Click to collapse
Yes and no, currently I am working on TWRP and there for flash the stock Rom quite frequently. But I do plan to use Pixel Experience. The only thing that does not work is NFC. But that seems to be the case with all the GSI I could find, as they are all based on phh.

Hey Guys, I did some work on the TWRP recovery. It's now more reliable, I highly recommend the update. You will find the download link and updated instructions at the top.

Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.

koosman911 said:
Thank you sir, updated recovery works perfectly on two separate phones so far, I've flashed a few gsi's and they work as far as they are able to obviously each gsi might have its own issues, the two phones I have don't have Nfc so I can't help to test that sadly. We appreciate the hard work.
Click to expand...
Click to collapse
Thank you. What other phones despite the A22 5G are you using the recovery with?
Edit: Ahhh, you mean, you have nothing to test NFC with?

The model of a22 5G available in my country does not have nfc.