Database Info

[GUIDE][20-MAY-2019]HOW TO FLASH Z010D ROMs on Z010DD (8.1 and 9.0 ROMs).

This guide is specifically aimed for Z010DD users who want to flash custom ROMs:​If you want to stay on stock and only wanna flash TWRP and root the Stock ROM, please skip this thread and refer to @jide1 's guide here instead: https://forum.xda-developers.com/as...ot-asus-zenfone-max-zc550kl-qualcomm-t3652518​
Things to be noted beforehand:
1. Make sure you are on the latest/final stock rom/firmware
2. Need Unlocked bootloader (Linked below, install the apk and follow the steps)
3. Take backup of all of your data from the internal storage. (To avoid depression if accidentally wiped your precious data)
4. Minimal ADB and Fastboot (Thread Linked below, Download from there and follow on-screen steps).
Steps:
A. To flash TWRP:
1. Once you have unlocked the bootloader, download 'minimal adb and fastboot zip' and PBRP zip(extract img from it).
2. Boot into fastboot by switching off the device, then POWER + VOLUME 'UP'. (You'll enter CSC ode screen, which is fastboot so don't worry)
3. Place the recovery image into the fastboot folder and open a command window there.
4. Connect your device, then type 'fastboot devices' and Enter, just to verify if your device is shown.
5. type: fastboot flash recovery recoveryname.img
THE NEXT STEP IS IMPORTANT, Pay Attention.
6. Now REBOOT Directly to twrp by holding POWER + VOLUME 'DOWN'. Don't boot into system else stock recovery will get restored.
B. Preparing for Flashing ROMs:
Once you have booted to twrp successfully, you will need to 'format' all the partitions, which includes:
System, Data, Cache, Dalvik/ART Cache, & Internal Storage.
HERE YOU WILL LOSE ALL OF YOUR DATA, YOU HAVE BEEN WARNED ALREADY SO, yeah.
Click to expand...
Click to collapse
1. In TWRP, go to WIPE -> ADVANCED WIPE;
2. Select the above listed partitions and then SWIPE TO WIPE.
Note: You will notice a partition called 'ASDF' ,wipe/skip, doesn't matter.
3. Come back to home, go to REBOOT -> RECOVERY
C. Flashing ROMs:
1. Download the ROM, Patch, and Kernel zip (Linked Below).
2. Flash them in the mentioned order.
3. Flash Opengapps (if needed) (Nano Gapps recomended).
4. Reboot.
(NOTE: FOR MAGISK, FLASH IT 'AFTER FIRST BOOT ONLY', AND IF FLASHING ZIP NOT WORKING, THEN see POST #3)
Bugs and Notes:
1. Notification LED doesn't BLINK when a notification arrives, it stays on (colors are correct though).
2. VoLTE is broken on pie roms (ignore the volte logo), stick to Oreo if you want VoLTE. (LTE data works fine).
3. Reboot Sometimes get stuck in black screen, its RANDOM, LONG Press the power button for 15 secs instead if that happens.
4. If any ROM contains 'Always On' functionality, disable it as the feature doesn't work properly. (Ambient display has no issues)
Links: Refer POST #2 .
Credits:
@SakilMondal for roms.
@YaAlex for kernel and patch for Z010DD.
Myself for testing.
Created 2019-04-22
Last Updated 2019-05-20

Links:
ROMs: https://sourceforge.net/projects/zenfone-max-updates/files/Z010D/ (Please flash the latest ones only, don't use old ones)
Patch (link updated): https://anonymousfiles.io/3WLplRtD/
Kernel (link updated + new kernel update): https://anonymousfiles.io/m4oKP6wL/
TWRP Recovery (Image file, Flash via fastboot): https://drive.google.com/file/d/1txHT0vRNo0gTMkD0Sb5kpuQQT0dAiphH/view
ASUS Official Bootloader Unlock Tool for 8939 Devices: http://dlcdnet.asus.com/pub/ASUS/Ze...513.74708998.1502054577-2083321676.1502054577
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790

Troubleshooting:
Instructions for Magisk:
1. Extract boot image from the rom zip
2. Go to Magisk Manager app
3. Tap 'Install' next to 'Magisk is not installed' line.
4. Tap 'Select and patch a file'
5. Navigate to the extracted boot image. It will now create a new boot image and save it in mentioned location.
6. Reboot to recovery, Flash the Boot image + KERNEL zip.
7. Reboot to system.
To fix CTS Mismatch in Magisk:
Open /system/build.prop, replace the line 'ro.build.fingerprint=' with:
Code:
ro.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys
Open /system/vendor/build.prop , replace the line 'ro.vendor.build.fingerprint=' with:
Code:
ro.vendor.build.fingerprint=asus/WW_Phone/ASUS_Z010_2:6.0.1/MMB29P/13.8.26.80-20161230:user/release-keys

Patch is required for sd410 devices??

koushik99 said:
Patch is required for sd410 devices??
Click to expand...
Click to collapse
Nope, patch is only for DD.

Guide has been updated. Please check.

unable to flash GAPPS
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl

I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?

PRASAD.ASRS said:
Hai , i got a problem , phone shutdowns after flashing GAPPS (opengapps) , i tried Many RAMS(DOT OS, lineage-16.0-20190514-Z010D, BootleggersROM-Pie4Z010D.4.1-Stable-Unshishufied-20190421-170442 ,RR-P-v7.0.2-20190505-Z010D-Unofficial ) , without GAPPS Flashing it is , ROM working good , please let us know how to fl
Click to expand...
Click to collapse
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.

ihatebarrels said:
I cant turn off the phone with pie,
i need to go in recovery first to power off otherwise after a while it turns back on
is it a known bug?
Click to expand...
Click to collapse
In both oreo and pie, for both z010d and dd, reboot and shutdown is an issue
It doesn't happen everytime, its random, and no fix is found yet.

Is it working on asus zenfone max 2016 sd 615?

Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files

james_imch said:
Can anyone give me the updated link for the dd-fix-r5.zip and GUNMetal-R3.zip files
Click to expand...
Click to collapse
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).

Kaustav365 said:
Is it working on asus zenfone max 2016 sd 615?
Click to expand...
Click to collapse
Hope you have read the OP properly
This thread is only for sd615/Z010DD/MSM8939, and its clearly mentioned.

TechNova said:
I just saw that the link was no longer working (would have been better if you pointed out that first instead)
Anyways,
Link is updated, check again (kernel is updated,patch remains the same).
Click to expand...
Click to collapse
PBRP Recovery (flashable zip) link is also not working. Please update it.

james_imch said:
PBRP Recovery (flashable zip) link is also not working. Please update it.
Click to expand...
Click to collapse
Done,
Removed pbrp and now Twrp link posted.

TechNova said:
Looks like you're using aroma gapps..
Use micro gapps or below. Here everything works fine.
Click to expand...
Click to collapse
Hey! I am also facing the same issue. I tried the nano version of Gapps on my Asus Zenfone Max Z010D and my phone is still crashing it keeps restarting and then automatically turns off. Is there any issue to fix this?

unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939

Eric0000 said:
unable to flash roms it shows up no digest found or invalid zip or update error 7
please help how do i find correct rom for sd615 8939
Click to expand...
Click to collapse
I too facing same problem

Unlocking the apk no longer works

[GUIDE][OP7][9.0/10.0/11.0] Unlock Bootloader | TWRP | Root with Magisk | Update

Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
This thread is dedicated to newbies and rooting, so if you're familiar with the whole procedure, you're done
Just ask questions about every step and you'll receive help!
Downloads
TWRP Installer ZIP and TWRP IMG for Android 9/10: https://forum.xda-developers.com/oneplus-7/development/recovery-unofficial-twrp-recovery-t3932943
TWRP for Android 11(including instructions, thank's to @Nebrassy ): https://forum.xda-developers.com/t/recovery-11-unofficial-teamwin-recovery-project.4289455/
TWRP Installer ZIP = For example twrp-3.4.0-10-guacamole-unified-installer-mauronofrio.zip
TWRP IMG = For example twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
Check for Pie or Q TWRP IMG! If you have Android Pie, choose Pie TWRP IMG, if you have Android Q, choose Q TWRP IMG.
The TWRP Installer ZIP works on Android Pie(9)/Q(10)
Magisk ZIP: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Hints
If you need to update TWRP or Magisk, always keep older versions of both in hand(Magisk canary or beta may have issues)
Remove your lockscreen protection which also removes encryption to prebvent mounting issues within TWRP
Before proceeding
Your Windows PC should already recognized your device with the USB cable
Use an USB cable provided with the phone
Make sure your Windows Explorer is set up to have file extensions enabled to avoid file name issues
This process will FORMAT/WIPE/DELETE your internal storage and every file of your phone, so please back it off your device at first!
Also keep a boot.img from your current system in place if anything went wrong so you can flash it via fastboot, see "Rooting without TWRP" for how to get it.
Rooting with TWRP (Android 9/10)​
Steps for unlocked bootloader with TWRP AND Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP installer ZIP" and "Magisk ZIP" to the phones internal storage.
5. Copy the "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP installer ZIP" from your phones storage from step 4.
13. Hit "install" and navigate to the "TWRP installer ZIP" file and select it for installation(dont boot the system now!).
14. Go back and flash "Magisk ZIP" the same way as for TWRP Zip otherwise your device will not boot!
15. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP and Magisk:highfive:
Steps for unlocked bootloader with TWRP WITHOUT Root(Magisk)
1. Follow this guide to unlock your Oneplus 7 bootloader(wipes everything on your device, works for OP7 pro and OP7): https://forum.xda-developers.com/showpost.php?p=79741564&postcount=2.
2. Your phones bootloader is now unlocked, leave the phone plugged to your PC
3. Make sure you have enabled USB-Debugging and Advanced Reboot under developer options(see step 1 how to enable it all) again after the first boot of the wiped device, since this gets reset
4. Copy the latest "TWRP IMG" to the phones internal storage.
5. Copy the latest "TWRP IMG" to the "platform-tools" folder from step 1.
6. Open command window or PowerShell window again if you did not closed it before within the "platform-tools" folder from step 1
7. Type
Code:
adb devices
to see if your device is connected and recognized sucessfully by your PC.
8. Type
Code:
adb reboot bootloader
to reboot to fastboot mode.
9. Type
Code:
fastboot boot recoveryimgfilename.img
to temporary boot TWRP, where recoveryimgfilename.img is the name of your downloaded TWRP *.img file, so watch your file name!.
10. Enter your screen lock PIN within TWRP if you have set it up before.
11. Allow modifications.
12. Now you have temporary booted twrp recovery. To make it stick permanently you need to flash the "TWRP IMG" from your phones storage from step 4
13. Navigate to advanced menu within TWRP, click on "Install Recovery Ramdisk" and select the "TWRP IMG". This will patch the boot image which does Magisk otherwise.
14. Thats all, you can unplug the USB cable and boot the device to your system. Your device is now bootloader unlocked with TWRP:highfive:
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Rooting without TWRP (Android 9/10/11)​
Also useful to get stock recovery and kernel --> Recovery is within boot.img on A/B devices like OP7
Refer here for unlocking the bootloader.
1. Download the payload dumper tool to your PC from here and extract it
2. Download the FULL OxygenOS Rom zip(The version your phone is running) and extract the payload.bin
3. Put payload.bin to "payload_input" folder o the extracted tool
4. Run payload_dumper.exe from the tool's folder
5. Extracted img files are in "payload_output" folder
6. Now you have your own boot.img for your Rom
7. Copy it to your phone
8. Patch the boot.img with Magisk directly on your device: Magisk Manager App -> hit install after your Magisk version -> hit "Select and Patch a file"
9. Copy the patched boot.img (it should be in the Download folder of your device named something like "magisk_patched-22100_bjjRn.img") back to your PC
10. Reboot your device to fastboot
11. Flash the patched magisk_patched-22100_bjjRn.img
Code:
fastboot flash boot_a magisk_patched-22100_bjjRn.img
fastboot flash boot_b magisk_patched-22100_bjjRn.img
12. Reboot your device. Now you have your phone rooted without the need of TWRP (Check with Magisk Manager App)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update your rooted OxygenOS (Android 9/10)​Steps for UPDATE OxygenOS via OTA and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
3. Go to Android settings -> system -> system update and hit "Download & Install Now", don't reboot yet!
4. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
5. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version -> hit "install to inactive slot"
6. Reboot your device
7. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via OTA and you keep TWRP and Root:highfive:
Steps for UPDATE OxygenOS via local upgrade and keep unlocked bootloader, TWRP, Root(Magisk)
1. [OPTIONAL, but highly recommended]Backup everything in case of issues!
2. Download the full rom zip file and place it into the root folder of your storage(/storage/emulated/0)
3. Go to Magisk Manager App and uninstall all modules
2.1 [Optional]: For some modules(read those instructions) you should do an reboot now, then proceed
4. Go to Android settings -> system -> system update and hit gear icon top right -> local upgrade, don't reboot yet!
5. (not for Android 11)Flash "TWRP ZIP" within Magisk Manager App like a Module: Magisk Manager App -> Menu -> Modules "+". This installs TWRP to both a/b partitions.
6. Install Magisk via Magisk Manager App again: Magisk Manager App -> hit install after your Magisk version ->hit "install to inactive slot"
7. Reboot your device
8. Reinstall your Magisk Modules(maybe a reboot is necessary)
Your device is now updated via local upgrade and you keep TWRP and Root:highfive:
If you have any issues, just feel free to ask!

@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.

Kollachi said:
@strongst you should maybe write in your guide that magisk flash is a must! Without phone won't boot if it's stock.
There are a lot of people who wanna flash TWRP without magisk. I don't know why they do that it makes no sense for me.
Click to expand...
Click to collapse
I made it a little bit more clear, thanks, that's an common issue across several devices and requested often enough

Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel

AxelM said:
Thank you for the quick tutorial. For me it looks very similar to the procedure with the OnePlus 5, am I right?
Does this indicate, that an EFS Backup is also to create the same way? https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877
BR
Axel
Click to expand...
Click to collapse
There's something different after unlocking the bootloader(which is the same). Twrp and magisk installation is different due to treble.
For EFS you can backup with twrp or local terminal
dd if=/dev/block/sdf2 of=/sdcard/modemst1.bin bs=512

Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?

Camack said:
Thanks for the guide, my OnePlus 7 came with 9.5.5 and I want to clean flash to the latest 9.5.8. I have already unlocked the bootloader, boot into TWRP and installed TWRP, are these the correct steps to flash 9.5.8 as I'm confused with the A/B partition?
1. Wipe data, cache, system
2. Flash 9.5.8 signed flashable zip
3. Flash kernel and Magisk or the other way round?
Click to expand...
Click to collapse
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard

strongst said:
1. Wipe data, cache, system and internal storage
2. Flash 9.5.8 signed flashable zip with current twrp
3. Flash twrp installer zip with current twrp
4. Flash magisk zip with current twrp
5. Reboot
Make sure not to FORMAT internal data, otherwise you wipe the files you want to flash as it formats sdcard
Click to expand...
Click to collapse
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?

Camack said:
Thanks, so I boot into TWRP first and then do step 1 and 2? Also, which step should I flash custom kernel?
Click to expand...
Click to collapse
You need to do all steps. I recommend to flash the custom kernel when you've sucessfully booted the device at first.

Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well

murti52 said:
Hi, a new OP7 User here. I wanted to know how can i keep my data decrypted? i have installed TWRP but i want to decrypt my data and also keep it the same after updated newer updates. Is it possible? I was able to do it on my OP3T, so wanted to know if its possible on OP7 as well
Click to expand...
Click to collapse
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

strongst said:
This should work https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.

murti52 said:
I think i messed up real bad, now when iam booting the phone, a message comes, your device is corrupt. It can't be trusted and will not boot.
Click to expand...
Click to collapse
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.

strongst said:
That message is the bootloader unlocked warning and comes every time as soon as you unlocked the bootloader.
Flashing DM verity patch can only be done when you format internal storage which wipes everything of your internal storage. You can't "decrypt" your existing data permanently with this.
Click to expand...
Click to collapse
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.

murti52 said:
No, this is not the same, i can't even go to fastboot or anything, it's hardbricked.
Click to expand...
Click to collapse
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325

strongst said:
If you have really bricked it: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
Click to expand...
Click to collapse
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?

murti52 said:
Sadly it didn't worked, as phone doesn't gets detected on pc, keeps on rebooting. Gave it to service center and they are also not able to solve it ??. So a replacement for me ?
Edit : i think the force decryption was the culprit. When i rebooted, system was crashing. Op3t had its specific force decrypt file, not a general one, So i think as the development moves forward, op7 will also get it's own. Hoping the best ?
Click to expand...
Click to collapse
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.

strongst said:
This file also works on OP7 pro, so it should also work on normal op7. I think the issue comes from something other.
Click to expand...
Click to collapse
Then there must be some issue with my flashing sequence. Btw, The service centre repaired the issue and i have rooted it and using bluespark with stock rom. I'll give the zip another try later on when a new update comes. Thanks for the help

I believe the default file system is ext4, is there any benefits changing it to f2fs?

Jacckz said:
I believe the default file system is ext4, is there any benefits changing it to f2fs?
Click to expand...
Click to collapse
A good and quick overview and comparison with oneplus 7 pro https://sparrowsnews.com/2019/08/13/difference-between-f2fs-and-ext4-file-system/

[Request] Please make a guide/ tutorial on how install GSI ROM on the latest firmware.

The phones keeps getting updates and the procedure to install GSI ROM might change. There are a bunch of guides in here but none of them worked for me.
If you managed to run GSI ROM on the latest Samsung firmware please share how you did it. Or is it even possible now?

this method was tested on my SM-A750F with lineageOS 17&18 (android 10&11).
1. download the AB VNDKLITE variant (should be called something with arm64-ab-vndklite.img or arm64_b??-vndklite.img)
2. if the image is in a .xz format, extract it using xz or 7zip/winzip
3. download the zip file i attached to this post
4. copy the zip and the extracted image into a SDCARD, then move the SDCARD into the phone.
5. install a custom recovery (for SM-A750FN, use TWRP by ashyx; for SM-A750F or SM-A750GN/DS, use PBRP)
6. boot into the custom recovery by holding the power button + volume up while restarting.
7. swipe to allow modifications
8. click install
9. on TWRP, you will need to click Install Image
10. navigate to your SDCARD folder
11. click on the .img file
12. it should ask you where do you want to install this image. click system
13. wait for it to flash.
14. click install again, then select the zip file you downloaded from your SDCARD.
15. click flash
16. after you finished flashing it, click install, navigate to /data/tmp and install Magisk.zip (you can delete this file after flashing it).
17. Click wipe > format data, then format data
18. After formatting data, click reboot>reboot system. you should now boot into your new OS!

Thank you for the guide!!!
It booted to Lineage OS 18 but after rebooting it's stuck at the lock screen: Screen Lock, Fingerprint and Camera are not working. Is this to be expected for Lineage OS 18?

did you make sure to wipe data before you installed the new OS?
what do you mean by screen lock? password?
What model do you have? (e.g. SM-A750FN, SM-A750F, etc)
can you send me the logs when the camera crashes/when setting password? (to get logs, run adb logcat -f logcat.txt, then upload logcat.txt)

What model do you have? (e.g. SM-A750FN, SM-A750F, etc)
Click to expand...
Click to collapse
Device: SM-A750GN
Tried: GSI - Lineage OS 18 [arm64-ab-vndklite]
did you make sure to wipe data before you installed the new OS?
Click to expand...
Click to collapse
Yes I made I sure I followed your instructions. Question: Is it enough if I format the data partition once? If first attempt failed and I want to flash another ROM will I have to format data partition again? I am doing this everything just to be sure for now.
what do you mean by screen lock? password?
Click to expand...
Click to collapse
During the initial setup if I try to set a PIN or Fingerprint it bootloops or the setup crashes.
Outcome of each ROM:
Lineage OS 17: Bootloop = The logo keeps moving.
Lineage OS 18:Camera, GPS not working. Error when setting PIN for lockscreen.
Please check attachments for logcats and screenshots.

Can you send me a logcat of the boot proccess? (start logcat when powering up the phone, close it after camera crashed/pin setting crashes)

itmr said:
Can you send me a logcat of the boot proccess? (start logcat when powering up the phone, close it after camera crashed/pin setting crashes)
Click to expand...
Click to collapse
I have tried for days and given up. Sorry. Maybe I will try later.

u need to downgrade to the oldest same sw bit firmware, no other options works

I did install treeui 0.95 gsi on my a750f device,how can i install other android 11 gsi on my phone?

Question LineageOS: "Can't load Android System" on first boot.

My new Xiaomi Poco X3 Pro is showing an error screen after some time, like in this post:
https://forum.xda-developers.com/t/cant-load-android-system-lineageos.4314035/
It reads "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device"
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
After the first error screen
- I tapped Try again,
- When the error occurred again, I tapped "Factory data reset," but the error still occurred. The phone is new, no user data is on the phone.
- I booted into recovery and reset all the data I could. When I tap "Format system partition" it throws an error "E: Failed to open /dev/block/dm-0: No such file or directory. System wipe failed."
- Then I repeated the adb sideload. The error occurs again.
- I removed the SIM card, as someone in the forum suggested this could be a problem source. The error still occurs.
What can I do now?
----
Update [2021-12-05 Sun 20:09]
It seems to be a Problem with the GApps Version.
What I did Try so far is:
- Install 03-12-LOS and latest GApps via LOS recovery (didn't work)
- Install 03-12-LOS and latest GApps via TWRP recovery (didn't work)
- install LOS Build from 26-11-2021 without GApps (works)
- Install LOS Build from 26-11-2021 with latest GApps (didn't work)
- Install LOS Build form 26-11-2021 with GApps from 25-11-2021 (works)

Just use TWRP, flash ROM and AFTER flashing ROM Format Data where you have to type "yes". (Format, not Wipe)
Xiaomi Poco X3 Pro
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me

Thanks for the Idea. At the moment it has not solved the problem.
This is what I did:
- Flash TWRP
Code:
fastboot flash recovery TWRP-3.5.2-vayu-Nebrassy-2.img
- copy lineage-18.1-20211203-nightly-vayu-signed.zip and "open_gapps-arm64-11.0-nano-20211204.zip" to the Poco device
- install via "install" option, wipe cache at the end of installation
- Format files (via "Wipe" -> "Format Data" -> type "yes")
- Reboot
After some time of the animated Lineage OS logo, the phone reboots into TWRP.
To me this seems very similar to the Lineage recovery before.
Any ideas what could be wrong?

You probably wiped System or Vendor partition or something, you are not supposed to do that.
Most likely you have to reflash MIUI now first. Make sure it's atleast version 12.5.X.X.
Flashing instructions are really simple, this apply to all ROM's.
FIRST INSTALL?:
Remove any fingerprint, PIN, or password in MIUI
Unlock the bootloader
Transfer ROM to internal storage
Install any suitable recovery
Flash ROM zip file
Do a data wipe in recovery (format data)
Reboot to the system, wait and enjoy
FLASHING UPDATES?:
Download via OTA Updater and let it automatically install; OR
Download an update, transfer to internal/external storage (always check file sha256)
Flash ROM zip and reboot.
Do not wipe anything else or add any additional steps. (maybe except Gapps if ROM doesn't have them included)
ps.
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
This happened so far:
I just unlocked the boot loader of my new phone after week of waiting.
I followed the official lineage instructions to install the OS: https://wiki.lineageos.org/devices/vayu/install
Everything worked including the sideloading via db.
I downloaded those two files for the LineageOS-Site:
- Recovery via fastboot: lineage-18.1-20211203-recovery-vayu.img (recovery works, I can still boot into recovery)
- System via adb: lineage-18.1-20211203-nightly-vayu-signed.zip
I also added Gapps via adb: "open_gapps-arm64-11.0-nano-20211204.zip"
Both adb transfers exited successfully.
Click to expand...
Click to collapse

k3lcior said:
In first post there is no mention if you did Format Data or not and when you did it. Like i said before - you have to Formata DATA AFTER flashing ROM . Not before.
Click to expand...
Click to collapse
I followed the LOS Install Guide: https://wiki.lineageos.org/devices/vayu/install But this procedure does not seem to bee the cause (see below).
Download the LineageOS installation package that you would like to install or build the package yourself.
Optionally, download an application package add-on such as Google Apps (use the arm64 architecture).
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Up + Power. When Xiaomi/POCO/Redmi splash appears, release Power and keep pressed Volume Up until recovery appears.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
Click to expand...
Click to collapse
Okay so this is what I did (the part that works):
- I downloaded the latest possible stock ROM from https://www.xda-developers.com/down...ut-several-xiaomi-redmi-mi-poco-devices/#vayu The fastboot ROM is more than 5GB.
- Extract the file "vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea_05cc38de43.tgz"
- then connect the phone via USB cable in fastboot mode and:
Bash:
cd ~/Downloads/vayu_eea_global_images_V12.5.3.0.RJUEUXM_20211015.0000.00_11.0_eea
/bin/bash ./flash_all.sh
- The default MIUI starts flawless, as it dit the first time I turned on the phone. So far so good.
What didn't work:
1. I installed the LOS Recovery again and flashed the OS and Gapps. Only after that I did step 3 - formating. The result ist the same bootloop as in the beginning.
2. I flashed the stock MIUI ROM again (which woks fine). Then I flashed TWRP, transfered the OS and GApps file and installed. I did not wipe anything, just used "format data" like above.
In both cases the OS does not start. After a while displaying the LOS-logo the phone reboots to recovery.
What did work:
I downloaded lineage-18.1-20211126-nightly-vayu-signed.zip, one version before the latest verion and the corresponding recovery lineage-18.1-20211126-recovery-vayu.img
I flashed only the OS, and no GApps -- and it launched successfully. Installing with the latest GApps failed again.

Install older gapp, not all gapp is compatible

Magisk & Lineage = No wifi

Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?

Ork_77 said:
Goodmorning everyone. I have a problem with magisk and lineageos 18.1
I have a xiaomi mi mix 2 unlocked
Premise: I've never had any problems with magisk and lineage until now.
I installed magisk scrupulously following the official instructions and using both the boot.img patch system and the direct installation via recovery (adb sideload & lineage recovery)
In both cases magisk appears as not installed when looking from magisk manager and the wifi stops working (the phone connects to the various networks I have tried but reveals them as without internet.)
clearing cache does nothing
resetting network connections does nothing
Updating to the latest version of the radio firmware does nothing
restore boot.img OR reinstall lineage corrects the problem
In all cases I don't get root ...
Honestly, everything is beyond my understanding .. can you help me?
Click to expand...
Click to collapse
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?

Droidriven said:
It seems to me like you aren't properly flashing the patched boot.img. What method are you using to flash the patched boot.img?
Click to expand...
Click to collapse
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.

Ork_77 said:
I used both the method I'm aware of
1) I install magisk manager, extract the boot.img from lineage zip, upload it to the phone, patch it with magisk manager (operation ends fine), pass the modified version back to the pc reboot the phone in recovery and install the new boot with adb (installation ends correctly).
2) I rename the magisk app as .zip and then I install it through recovery
The result is the same.
In the past (with lineage 17) i always used the second method and I lived happy and with root for years.
Click to expand...
Click to collapse
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com

...

Droidriven said:
Since you have TWRP, you don't need the patched boot.img.
The Magisk Manager app has the root binaries built in now, all you should need to do is a Magisk Manager flashable zip.
Read this:
The Magisk Manager APK can now be flashed from within TWRP
Magisk is now distributed as part of the Manager APK, meaning you no longer need to flash a separate ZIP file from a custom recovery.
www.xda-developers.com
Click to expand...
Click to collapse
Yes...this is exatcly what I did.
Method 2.

Ork_77 said:
Yes...this is exatcly what I did.
Method 2.
Click to expand...
Click to collapse
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.

Droidriven said:
You said that you converted the apk into a flashable zip. I think you should be able to find a MagiskManager.zip that is prepackaged for you to download and flash.
Also, if you use the patched boot.img method, you should rename the patched boot.img to "boot.img", then place the boot.img in your fastboot folder on PC. Then right click inside the fastboot folder and choose the option to open a cmd terminal, then boot your device into fastboot mode, connect your device to PC, type the following command:
fastboot devices(press enter)
If it returns a serial number, you are connected. Next, type the following command:
fastboot flash boot boot.img(press enter)
This should flash the patched boot.img correctly. Then reboot the device to system and try installing the Magisk Manager apk file from your internal storage instead of flashing it as a zip in recovery. If that doesn't work, try flashing the apk as a zip in recovery, wipe cache and dalvik cache after flashing the zip(DO NOT FACTORY RESET OR FORMAT ANYTHING), then reboot to system and see if it works correctly.
Click to expand...
Click to collapse
Hi Droidriven, thank you for your answers. Perhaps, synthesizing my steps too much, I gave the impression of not being particularly capable in computer science (you even tell me to press "enter" after commands ...). Well, let's say it's not my case.
All steps are performed correctly.
all steps end without errors.
No matter what I do, in the end Magisk appears as n / a, I don't have root, and the data connection doesn't work. Small addition about the latter aspect: when rebooting the wifi connection works for a variable time between 10 and 20 seconds, after which the network appears as without internet (or intranet) but the phone remains connected.
At the reboot, history repeats itself
Restoring the original boot everything returns to normal.