Develop Bugs

[Guide] How to install custom ROM (Tested with Pixel Experience and Lineage OS)

I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!

thanks so much for this! Been flashing since andriod 1.6 but couldnt wrap my dumb head around these dual partitions.

And is the same for miui.eu ?

raphae34 said:
And is the same for miui.eu ?
Click to expand...
Click to collapse
No. Follow the instructions in the OP there. They work.

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?

Snjeky said:
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Click to expand...
Click to collapse
the "no os installed" is normal, dont worries.
The installation method for pixel experience worked when I installed the old version, it was updated multiple times so probably the process changed, I will update the thread later

This dual slot fuking my mind up.
TWRP asking for password to decrypt data. while first boot in recovery.
also *unable to decrypt FBE device* error while formating data.
"couldnt able to flash Any ROM "unable to partition path/cache" error.
ps. flashed in slot a.

When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same

ManuMan99 said:
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
Click to expand...
Click to collapse
downgrade to android 9. apparently android 10 got some issues.

pradie said:
downgrade to android 9. apparently android 10 got some issues.
Click to expand...
Click to collapse
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it's booted correctly.
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it booted correctly.

Sapper Morton said:
Indeed, it's not as straight forward, but it's possible without losing Widevine L1 security level; read my experience here, I explained the steps I took ; so far, I came back to v11.0.8.0 QFQMIXM from v10.3.17.0 PFQEUXM after the downgrade, with no issues whatsoever (no format/wipe data); my DRM Keys and sensors remains intact.
Click to expand...
Click to collapse
Thank you I wouldn't have guessed that would work it seems too easy to be a fix but that's good news.
Thanks for that info

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.

vjrx88 said:
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
Click to expand...
Click to collapse
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!

garylawwd said:
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
Click to expand...
Click to collapse
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.

garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
No problem in downgrade ,, i Already downgraded. No bugs facing!
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
vjrx88 said:
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
Click to expand...
Click to collapse
Lol i came back to 9 ,, untill stable comes or i will use pixel rom ?

Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.

spring_roll said:
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
Click to expand...
Click to collapse
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version

garylawwd said:
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
Click to expand...
Click to collapse
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?

spring_roll said:
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
Click to expand...
Click to collapse
For you I don't think twrp is installed now. Some ROMs have twrp built in but if not then you have to manually flash twrp every time you flash a ROM or it gets overwritten with stock recovery.
When you flash the twrp.img and boot twrp it isn't actually installed, you are running it in ram and when you reboot it goes out of ram and your left with an un-bootable slot due to your boot slot being messed up from flashing the twrp.img and twrp won't stay installed.
For it to be installed properly you need to flash twrp.zip which will patch your boot.img with twrp and install it.
But as I said everytime you flash a ROM this will overwrite twrp and it will be gone unless the twrp.zip is flashed in twrp before rebooting.
Not as easy as it used to be by just installing twrp once and it is there forever. The new era of Android

[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN 🤓 (Redmi Note 9 / Redmi 10X 4G)

DISCLAIMERS:​
This help is specific for MERLIN devices only !
(Xiaomi Redmi Note 9 and Xiaomi Redmi 10X 4G)​
Keep atention. This is an UNOFFICIAL thread.​
This thread was based on the thread by Agent_fabulous. Thank you very much !​
DON'T ask by PM. If you have any question, reply to this thread.​
Keep in mind, nothing is 100% perfect, so you need to read careful
and keep trying before to ask an already answered question.​
Keep your backup files safe and secure ! If you can, encrypt them.​
If you try to flash in "firmware upgrade" mode, bootloader will be LOCKED again !​
Never try to flash in "format all" mode ! Otherwise, you will LOSE all secure and identifying infos for your device. Like IMEI and MAC.​
Never try to share your backups or your security and privacy will be compromised.
USE AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.​
Sorry for my bad english.​
GOOD LUCK

1. Where can I find official and untouched STOCK FIRMWARES ROMS?​Here, you can find latest releases: https://xiaomifirmwareupdater.com/miui/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/miui/merlin/​
2. Where can I find some useful tools?​Xiaomitool: https://www.xiaomitool.com/V2/​Miflashpro: https://miflashpro.com/​Miflashtool: https://xiaomiflashtool.com/​Sp Flash Tool: https://spflashtools.com/category/windows​Mi PC Suite: http://pcsuite.mi.com/​
3. There are useful tools for LINUX or Mac OS?​Xiaomitool (Linux & MacOS): https://www.xiaomitool.com/V2/​Sp Flash Tool (Linux): https://spflashtools.com/category/linux​
4. My pc can't detect my phone. What to do?​Probably, you need to install appropriate usb drivers.​Try this: https://androidmtk.com/download-mtk-usb-all-drivers​
5. Where can I find custom ROMs?​Here, you can find the collection of custom ROMs for MERLIN: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/​
6. How can I root?​First and obviously, you need to unlock your bootloader. Once you unlock your bootloader, you can root your device flashing magisk patched boot.img.​Here, you can find magisk patched boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
7. Where can I find TWRP & PBRP?​There is only ONE recovery project with open source for MERLIN.​But, there are other twrp and pbrp with closed source.​If you use it, you can cause damages to your device, use at your own risk and DON'T ask about it.​KEEP ATENTION: you need to IGNORE misc partition, if you flash the misc partition, your phone can be stucked in boot loop.​Here, you can find recovery projects images: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
8. How can I restore the state of UNLOCKED BOOTLOADER?​You need to restore your backup of SECCFG partition.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/​
9. How to make TWRP V11.0.4.0 work on MIUI V12.0.5.0 or higher?​If you are using MIUI V12.0.5.0 or higher, TWRP V11.0.4.0 will not work.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/​You will need to flash an older LK partition.​Here, you can find lk images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/​
10. How can I disable TWRP?​You will need to flash original stock recovery.img.​Here, you can find original stock recovery images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​
11. How to flash using SP FLASH TOOL without EDL and authentication?​If you want to use flash tool on MIUI V12.0.5.0 or higher, it will requires EDL and authentication.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/​
12. I am on MIUI V12.0.5.0 or higher, how can I flash using SP FLASH TOOL without EDL and authentication?​You will need to flash an older PRELOADER binary.​Here, you can find preloader binaries: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/​
13. I am on MIUI V12.0.4.0 or lower, how can I flash using SP FLASH TOOL without EDL and authentication?​You will need the specific DA (download-agent) file for it without authentication (#NoAuth #NoAuthentication #No-Auth #No-Authentication).​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/​
14. How can I downgrade MIUI version?​For downgrading your miui, you need unlocked bootloader.​After unlocked bootloader, you can flash older firmware rom using fastboot or sp flash tool.​
15. My phone is booting to a black screen after flashed misc partition together twrp. What to do?​If your phone is booting to a black screen, you need to erase MISC partition.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/​
16. My phone got bootlop after installed a Magisk module or Xposed module. How can I disable it?​You will need to uninstall the module. You have two methods for this.​For first method, you can disable Magisk (read question 17).​For second method, you need to boot in emergency mode (rescue mode).​For booting in emergency mode, you need to press Vol+ (volume up) after boot starts. (YES, I mean AFTER you see boot logo.)​And then, you can uninstall the module.​
17. My phone got bootlop after flashed Magisk. How can I disable it?​You will need to flash original stock boot.img.​Here, you can find original stock boot images: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/​
18. My phone got bootloop, I am on MIUI V12.0.4.0 or lower and I can't enter in fastboot mode or recovery mode. What to do?​You need to flash stock rom using sp flash tool.​Please, read question 13.​
19. My phone got bootloop, I am on MIUI V12.0.5.0 or higher and I can't enter in fastboot mode or recovery mode. What to do?​For this, you will need to bypass authentication and flash in EDL mode with NO auth for FREE.​Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/​For this, you will need an authorized account for flashing in EDL mode.​You need to go the service centre for professional assistance.​Please, read this: https://www.xda-developers.com/xiaomi-edl-unbrick-authorized-mi-accounts/​
20. There is any other way for flashing or unbricking?​Yes. You can try any useful tool (read question 2 and 3).​But, this help is not for how use them.​You can find a huge amount of videos in youtube about it.​
21. I want to keep with original stock boot.img together TWRP, but TWRP is removed at every reboot. What to do?​You will need to flash patched boot image without overwrite of recovery.​Please, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/​KEEP ATENTION: you need to disable verification for vbmeta too.​Here, you can find patched vbmeta with disabled verification: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/​
22. Where can I find scatter files to flash using flash tool?​Here, you can find scatter files: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/​
23. Where can I find readback file to backup using flash tool?​Here, you can find read back file: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/​
24. How can I know what is working on my phone before installing?​If you want to know what is working for MERLIN, read this: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/​
25. How can I disable preinstalled apps without uninstalling them?​You need to perform this in command line:​pm disable-user --user 0 com.android.chrome​(Change com.android.chrome to desired package name to disable.)​
26. Where can I find source code of the kernel?​Here, you can find the OFFICIAL source code of the kernel: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/merlin-r-oss and https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/lancelot-q-oss​Here, you can find the OFFICIAL source code of the kernel modules: https://github.com/MiCode/MTK_kernel_modules/tree/merlin-r-oss and https://github.com/MiCode/MTK_kernel_modules/tree/lancelot-q-oss​
27. Where can I find device tree and other sources codes of MT6768?​-> https://github.com/Jebaitedneko/omni_device_xiaomi_merlin​-> https://github.com/Redmi-MT6768/android_device_xiaomi_merlin​-> https://github.com/Redmi-MT6768/android_kernel_xiaomi_mt6768​-> https://github.com/Redmi-MT6768/android_vendor_xiaomi_merlin​-> https://github.com/AndroidBlobs/device_xiaomi_merlin​-> https://github.com/AndroidBlobs/vendor_xiaomi_merlin​-> https://github.com/SparXFusion/android_device_xiaomi_merlin​-> https://github.com/SparXFusion/android_kernel_redmi_mt6768​-> https://github.com/JamieHoSzeYui/android_device_xiaomi_merlin​-> https://github.com/surblazer/android_device_xiaomi_merlin​-> https://github.com/surblazer/android_kernel_xiaomi_mt6768​-> https://github.com/ZyCromerZ/android_kernel_xiaomi_mt6768​-> https://github.com/Box-boi/android_kernel_xiaomi_mt6768​-> https://github.com/Box-boi/omni_device_xiaomi_merlin​-> https://github.com/Box-boi/android_device_xiaomi_merlin​-> https://github.com/Box-boi/android_vendor_xiaomi_merlin​-> https://sourceforge.net/projects/zyc-kernels/files/Merlin​
28. How to pass SafetyNet?​You will need to have Xposed installed. After it, everything you need to do is install HiddenCore-Module, active it on Xposed Manager and reboot.​Here, you can find the HiddenCore-Module: https://repo.xposed.info/module/com.cofface.ivader​KEEP ATENTION: it is making android to keep on activity forever and never suspends screen.​You can use the patched apk by Evengard: https://forum.xda-developers.com/t/hiddencore-module-what-was-it-doing.3903984/post-81982121.​
29. How to disable ads (advertising)?​You will need to have Xposed installed. After it, everything you need to do is install AdBlocker-Reborn, active it on Xposed Manager and reboot.​Here, you can find the AdBlocker-Reborn: https://repo.xposed.info/module/com.aviraxp.adblocker.continued​KEEP ATENTION: some people said it can get troubles to google apps.​
30. How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED?​KEEP ATENTION: never try to restore partitions from a different device, or you can brick and cause damages to your device.​Here, you can find the guide: https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/​
31. How to disable ads (advertising) without xposed?​For unrooted devices, you need to perform this in command line:​pm disable-user --user 0 com.miui.msa.global​For rooted devices, you need to debloat your system and then remove the "MSA" app.​
32. What should I backup before trying to customize my device?​Here, you can find the list of what partitions you need to backup for avoiding mistakes without risking all of your device's identification details, like IMEI, WiFi MAC, Bluetooth MAC, calibration data, NVDATA, NVRAM, RADIO/MODEM/BASEBAND and others: https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/​
33. How to bypass authentication and flash in EDL with NO auth for FREE?​Here, you can find the guide for bypassing EDL authenticated mode for FREE: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/​
34. How to install XPOSED?​1. You need to unlock your bootloader.​2. You need to root using Magisk.​3. You need to install magisk manager.​4. You need to install the magisk module: RIRU. (Only Riru in the name).​5. You need to choose between EDXPOSED or LSPOSED and then install the magisk module: "Riru Edxposed" or "Riru Lsposed".​6. You need to install the properly manager: "Edxposed Manager" or "Lsposed Manager".​7. Reboot.​Done. Enjoy !​
35. How to remove and clear GOOGLE ACC and Mi ACC / MiCloud?​Here, you can find the guide for removing google account and xiaomi account: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/​
36. How can I flash a CUSTOM ROM?​Here, you can find the guide for flashing custom roms by c.whoopee: https://forum.xda-developers.com/t/...rom-on-a-redmi-note-9-global-variant.4234151/​(Thanks to c.whoopee)​Here, you can find the guide for installing a Lineage 17.1 ROM by ma259: https://forum.xda-developers.com/t/...eage-17-1-rom-in-redmi-note-9-merlin.4235003/​(Thanks to ma259)​
37. How to properly use the SP Flash Tool?​Here, you can find the guide how to configure correctly the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/​Here, you can find common errors of the SPFlashTool: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
38. How to solve "LIB DA not match" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
39. How to solve "PMT changed for the ROM" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
40. How to solve "STATUS_BROM_CMD_STARTCMD_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
41. How to solve "STATUS_SEC_AUTH_FILE_NEEDED" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
42. How to solve "STATUS_BROM_CMD_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​
43. How to solve "STATUS_BROM_CMD_SEND_DA_FAIL" error?​Please, follow the guide "How to properly solve the errors of the SP FLASH TOOL": https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/​​44. Where can I find official ENGINEERING ROMs?​Here, you can find ENGINEERING ROM V1: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/​Here, you can find ENGINEERING ROM V2: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/​
45. Where can I find extracted FIRMWARES?​Here, you can find the thread of the EXTRACTED FIRMWARE by yshalsager: https://forum.xda-developers.com/t/...-4g-redmi-note-9-merlin-auto-updated.4250261/​Here, you can find latest releases: https://xiaomifirmwareupdater.com/firmware/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/firmware/merlin/​
46. Where can I find extracted VENDORS?​Here, you can find latest releases: https://xiaomifirmwareupdater.com/vendor/merlin/​Here, you can find archive of releases: https://xiaomifirmwareupdater.com/archive/vendor/merlin/​
47. How can I mount system RW (read-write) ?​Here, you can find the guide and the script by lebigmac for mounting system as read-write (RW): https://forum.xda-developers.com/t/...unt-system-read-write-super-no_super.4247311/​
48. How to write and recover the IMEI for SLOT 1 and SLOT 2?​Here, we are discussing about the possibilities of how to recover the IMEI for SLOT1 and SLOT2: https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/​Here, you can find md1img images of the baseband/modem/radio: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/​​49. Where can I find custom KERNEL?​-> https://sourceforge.net/projects/zyc-kernels/files/Merlin/​-> https://github.com/JamieHoSzeYui/dream/releases​-> MOD EDIT: Link Removed​​50. How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE?​Here, you can find the guide: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/​

Full List of My Own Threads:
[V12.5.2.0][Android 11.0] New Update: Download Files for Merlin V12.5.2.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4357045/
[V12.5.1.0][Android 11.0] New Update: Download Files for Merlin V12.5.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4321093/
[V12.0.1.0][Android 11.0] New Update: Download Files for Merlin V12.0.1.0.RJOMIXM
https://forum.xda-developers.com/t/...-0-rjomixm-redmi-note-9-redmi-10x-4g.4295435/
[V12.0.8.0] New Update: Download Files for Merlin V12.0.8.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4285863/
[V12.0.7.0] New Update: Download Files for Merlin V12.0.7.0.QJOMIXM
https://forum.xda-developers.com/t/...-0-qjomixm-redmi-note-9-redmi-10x-4g.4245351/
[BOOT][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209263/
[DA][FLASH] DA files for flashing to MERLIN using FLASH TOOL
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209765/
[V1][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227933/
[V2][ENGINEERING][ROM] OFFICIAL Egineering Firmware for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4246891/
[FAQ][GUIDE][HELP] Assistance Solution Centre for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4225163/
[DISCUSSION][ROM][CUSTOM] What is the BEST CUSTOM ROM for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4291423/
[GUIDE] How to bypass authentication and flash in EDL with NO auth for FREE
https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/
[GUIDE]How to properly solve the errors of the SP FLASH TOOL for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4238161/
[GUIDE] How to properly use the SP FLASH TOOL for MERLIN ?
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4229937/
[GUIDE] How to remove and clear GOOGLE ACC and Mi ACC / MiCloud for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4233977/
[GUIDE] How to restore IMEI, Baseband, MAC, fix NVRAM WARNING and fix NVDATA CORRUPTED on MERLIN ?
https://forum.xda-developers.com/t/...-on-merlin-redmi-note-9-redmi-10x-4g.4230423/
[GUIDE] What should I backup before trying to customize my MERLIN device ?
https://forum.xda-developers.com/t/...lin-device-redmi-note-9-redmi-10x-4g.4229629/
[GUIDE][FLASH] How to keep flashing without AUTH or EDL on V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223089/
[GUIDE][TWRP] How to keep TWRP V11.0.4.0 working on MIUI V12.0.5.0 or higher MIUI versions in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223077/
[DISCUSSION] How to write and recover the IMEI for SLOT 1 and SLOT 2 in MERLIN ?
https://forum.xda-developers.com/t/...-in-merlin-redmi-note-9-redmi-10x-4g.4258779/
[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
[GUIDE][UNLOCK] How to restore the state of UNLOCKED BOOTLOADER in MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4220013/
[LK][STOCK] LK Image Partition for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
[BASEBAND][STOCK][MD1IMG] MODEM Image Partition for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4258919/
[MAGISK][XPOSED] What is working for Magisk and Xposed in MERLIN ?
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
[PRELOADER][STOCK] PRELOADER Partition Binary for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218929/
[READBACK][FLASH] Read Back file for backuping using flash tool from MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223109/
[SCATTER][FLASH] Scatter file for flashing using flash tool to MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4223097/
[STOCK][PATCHED] Boot, Vbmeta and Recovery: Images Partitions for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
[RECOVERY PROJECT] Collection of TWRP & PBRP & SHRP & ORANGEFOX for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/
[VBMETA][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN
https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218909/
[GUIDE] How to skip & avoid EDL auth bypass and FLASH in DOWNLOAD MODE for MERLIN
https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4322631/

TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.

Communos said:
TWRP does work above 12.0.5, I have tested.
New build: https://tdrive.elytra8.workers.dev/image-new.img
Flash like you flash any other custom recovery.
For ADS in MIUI, using debloat tool and removing MSA does the job.
Click to expand...
Click to collapse
Thank you very much.
Both were added on FAQ & GUIDE.
Here, you can find unofficial recovery project with closed source: https://forum.xda-developers.com/t/...for-merlin-redmi-note-9-redmi-10x-4g.4227751/

Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.

MyBrainIsAStrainer said:
Uhm... hello, newbie here and hopefully in the right thread.
I have a Redmi Note 9 and wanted to install LineageOS. What I have done so far:
Jumped through all the hoops to unlock the bootloader.
Since that erases all user data, I did not bother setting a password in the setup. Just went through it as quickly as possible.
Installed TWRP 12.0.6
Used that to install lineage-17.1-20210209-UNOFFICIAL-merlin.zip from here.
Result: The new system does not boot. I always end up in TWRP again. Even if I specifically go to Reboot -> System, it'll boot into recovery. I think the first boot fails and then it goes into recovery (if I power the device off and on again, it vibrates, the logo comes on, the screen goes black, it vibrates again, the logo shows again, and then I'm in TWRP).
What I have tried unsuccessfully:
Flashing the vbmeta from here.
Erasing the misc partition.
Flashing the old lk from here.
Closing the AVB2.0 after flash (with and without closing DM verity).
Wiping cache, dalvik, data, internal storage, and cache before reinstalling LOS.
Replacing TWRP with PBRP and trying again.
Probably some other things I don't remember. I've been chasing red herrings through this rabbit hole all day.
I also tried to install the ArrowOS build (from here), just to have one more datapoint. After that, the device boot-loops into the bootloader, and I have to manually go into recovery via VolUp+Power. This leads me to believe that it's not the LOS build at fault. It seems more likely that I am a moron and am doing something wrong. I just can't figure out what it is.
Any help would be appreciated.
Click to expand...
Click to collapse
Hey, Custom roms for Redmi Note 9 need MIUI 12.0.1 Indonesia, or MIUI 12.0.3 global vendor.
Downgrade your phone to the specific MIUI vendor, and then try flashing custom rom.
Here's the link for global 12.0.3
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
And before you downgrade your miui version, please erase system and vendor to bypass anti roll back.
Use these commands after connecting device in fastboot mode:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
fastboot reboot bootloader
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
If after fastboot reboot fastboot it shows waiting for device, install this driver. https://drive.google.com/file/d/1JFYCZ3mu_Y_xpnS7QrmtwqOeFnWg6DO2/view?usp=sharing
Please note that you need to be on stock recovery for fastboot reboot fastboot to work.
Happy flashing

Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Communos said:
fastboot reboot fastboot
fastboot erase system
fastboot erase vendor
Click to expand...
Click to collapse
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Then flash the 12.0.3 global/12.0.1 Indonesia miui version through MiFlash.
Or
You could give flashing 12.0.1 Indonesia vendor in TWRP, and then flashing rom.
Click to expand...
Click to collapse
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!

MyBrainIsAStrainer said:
Thank you very much! With that info, I think I finally have it working!
I case it's helpful for future users, here are some issues I encountered along the way:
Code:
$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
$ fastboot erase system
erasing 'system'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.013s
$ fastboot erase vendor
erasing 'vendor'...
FAILED (remote: Partition table doesn't exist)
finished. total time: 0.012s
Is that normal? I do have a partition named 'super' that I can see in the TWRP backup module. Judging from its size, that could be the system partition. I think there's also a vbmeta_system and vbmeta_vendor, did you mean those?
Ok, so I downloaded the full ROM for 12.0.3 global. I'm using Linux, so MiFlash won't work. But the ROM archive I downloaded contained a bunch of partition images and a shell script that would flash them using the fastboot command. I just ran that script. Windows users probably could have run the .bat file that was also included. There were no errors. And after a reboot, MIUI started to boot and presented me with the setup procedure.
I did not complete the setup (I suspect it would have just auto-updated MIUI to something that would have caused problems again) and used the power button to go into the bootloader.
From there, I flashed TWRP again (since it got overwritten by the script mentioned above), went into recovery mode, and tried to install LOS again. First, flashing seemed to hang. The last messages in the log were:
Code:
Installing file '/external_sd/Download/lineage-17.1-20210209-UNOFFICIAL-merlin.zip'
Checking for Digest file...
Target: Redmi/merlin_eea/merlin:10/QP1A.190711.020/V11.0.2.0.QJOEUXM:user/release-leys
And that was it. The border around the progress bar was doing it's busy animation thing and after waiting for 10 minutes, I used the power button to reset the device.
The second attempt went through fine, and now I have LineageOS running on the device. I still need to play around with it some more to see if there are any issues, but the flashing itself seems to have worked.
Again, thank you for your help!
Click to expand...
Click to collapse
Oh you're using Linux, for Linux the commands is
/.fastboot reboot fastboot
Great to know you were able to flash successfuly. Note that first boot in all roms is a bootloop, you just have to force reboot after a minute of bootlogo showing up or so.

hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out

Kain105 said:
hi i flashed a wrong twrp and now the phone keeps bootlooping, cannot enter recovery or fastboot by power + vol (+ or -)
adb from computer doesn't detect
sp flash tool doesn't move when i hit "download" button
bootloader unlocked, root yes
pc notificates a device connection by sound
phone redmi note 9
thank you for the help really cannot figure it out
Click to expand...
Click to collapse
Apparentely, you need to flash in EDL mode.
So, you need to bypass the authentication in EDL mode first.
Read this: https://forum.xda-developers.com/t/...d-flash-in-edl-with-no-auth-for-free.4229683/

Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.

E77en12 said:
Newbie Android user here, hopefully i’m on the correct thread...i have a Redmi Note 9 with MIUI Global version 11.0.5 and Magisk version 20.4.
I tried updating Magisk to the latest version using the direct install option but I keep getting an error. I was told I need manually patch the boot.img and flash it but I need to create a magisk_patch.img first from the boot.img.
I read some of the guides on this thread but I’m not sure which one to follow. Also the steps to create the magisk_patch.image shows I need to click the Install button on Magisk then Select and Patch a file. I only have the Update button on Magisk, can I use that instead?
Or if you have other suggestion how to fix my issue. I attached the error I’m getting when I’m updating Magisk.
Thank you in advance for the assistance.
Click to expand...
Click to collapse
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).

VD171 said:
You can't install the magisk using the direct option.
You need to the patch the boot.img file and then flash the magisk_patched.img using fastboot (or spflashtool).
Click to expand...
Click to collapse
Thank you, it worked. Now my magisk is updated

E77en12 said:
Thank you, it worked. Now my magisk is updated
Click to expand...
Click to collapse
Good work, my friend.
You are welcome

HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?

George528 said:
HELP PLS
i first flashed the patched_magisk.img then i got in a twrp boot loop. When i try to reboot into the system i get back to twrp menu.
Then i panicked and went to WIPE and factory reseted,
but it got stuck again. Then i powered it off.
How do i get out of this? I wanted to flash the stock boot.img but the storage folders has strange names
View attachment 5289089
EDIT:
i figured it out what i have done. The data was ecrypted so i formated the data. But now i have another problem:
I installed linageOS from here, but when want to reboot back to system it says
No OS Installed! Are you sure you wish to reboot? i don't undertand why the custom rom didn't install.
I just copied the .zip file with the custom rom in the phone and hit install in TWRP. What did i do wrong?
Click to expand...
Click to collapse
Did you flash the patched vbmeta too?

VD171 said:
Did you flash the patched vbmeta too?
Click to expand...
Click to collapse
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything

George528 said:
do you have a full step-by-step guide for this? i am feeling lost rn. I only have your FAQ but it doesnt cover everything
Click to expand...
Click to collapse
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com

VD171 said:
Steps for flashing vbmeta are same for every device.
You may try to use the search.
Here, you can find patched vbmeta for MERLIN:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
Click to expand...
Click to collapse
no, i mean a full guide for rooting from the beggining to end, for redmi note 9. For example i missed the vbmeta and this resulted in an error. Now i have to flash the stock firmware and wait for another 7 days for it to unlock. For newbies like me, this looks like a mess. If you don't have one, can you please create one? Do it for us, newcomers. Thanks

Dirty flash Realme UI V 2.0

I successfully dirty flashed Realme UI V 2.0 over stock android 10 without losing anything and now on Android 11.
Links available in telegram channel for Rm5p.
Anybody can do it...just dont forget to flash vbmeta with disable verity......

SShots

Do you have steps how to do it? I didnt actually get the steps in the telegram.

Kristopher28 said:
Do you have steps how to do it? I didnt actually get the steps in the telegram.
Click to expand...
Click to collapse
Yes, I will post now

Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.

jijojamie said:
Dirty flash Realme UI V 2.0. (Zero risk of losing any data if things are done as mentioned)
Things you will need.
1. A PC to use fastboot command.
Will definitely need adb and fastboot drivers installed. (folder C:/ADB)
2. You need to be on stock firmware V c.14, the latest one.
3. Custom recovery. Orangefox recovery R .11 stable version. (any other recovery latest version might work, just find the keywords mentioned)
Note: You will lose any custom recovery installed after Android 11 installation. (use system recovery and recovery ROM provided in telegram to revert back to A10 )
I am going to use Orangefox recovery as base here.
Download from telegram:
Realme UI 2.0 ozip and vbmeta.img, recovery.img (if you want-I have not installed any recovery as of now)
Download and place the vbmeta.img in your ADB folder.
Reboot phone to recovery and DO NOT WIPE anything.
Inside recovery find the entry called TERMINAL (under MENU), open it and type this first:
--------------------------------------------------------------------------------------------
setprop ro.separate.soft 19691
--------------------------------------------------------------------------------------------
xxxxxx [do not type this line]- just for your infoxxxxxxxxxxxxxxxxxxxxxxxxx
-[setprop(space)ro(dot)separate(dot)soft(space)19691]-----[do not type this line]
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Press enter
Back to ROM installation under FILES browse to UI V2 ozip.
Flash Realme UI 2.0 ozip (4fab98b6-6964-4c1d-9c5c-dcd92064ae14.ozip)
CAUTION - do not press reboot but instead just go back to MENU find option REBOOT and select reboot to BOOTLOADER or fastboot mode.
Now in your PC, press SHIFT + right mouse button on ADB folder and select OPEN COMMAND WINDOW HERE
In the command window type or paste this command
(copy below command from here and in the command window mouse-right-click and select paste) then press enter:
--------------------------------------------------------------------------------------------
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
--------------------------------------------------------------------------------------------
You should see SUCCESS message in your PC command window.
Then reboot your phone by selecting START in orangefox recovery.
I really love UI 2. Everyone should try this----safely.
Ensure your fastboot command works. I had a slight issue with fastboot on windows 7 x64 bit. I had win 7 x86 abd installation folder. Copy pasted the files from there to X64 and problem solved.
I was rooted while in A10 and magisk installed, didnt uninstall it, still had no issues. Just in case if any issue arise, I suggest you uninstall Magisk in A10 and proceed with A11 installation.
Click to expand...
Click to collapse
Is your phone rooted?

I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now

Kristopher28 said:
I have actually found a bug in the rui 2.0 where phone storage can't be read i thought my phone is bricked for good, but instead i installed their rui recovery then i format my phone and it's okay now
Click to expand...
Click to collapse
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.

jijojamie said:
If it was a bug, I would have encountered the same, but no. Except the windows version I used caused fastboot command error once and that too solved within minutes, I had zero errors. I was rooted on A10, but not on A11.
Please elaborate what you encountered. Maybe you did something wrong or else tips that might be helpful for others.
Click to expand...
Click to collapse
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.

Kristopher28 said:
Well in my case i did a clean wipe to avoid issues flashing the official rom , as you can see in the telegram post I did everything it shows there 1st is wiping in twrp (dalvik, data,system,cache, and vendor) then i installed the c.14 then terminal and so forth but i think there's a wrong part I've done where i dont use the commands in fastboot properly, flashing vbmeta where the disable verification is in. In my case i just flash the vbmeta with "fastboot flash vbmeta vbmeta.img" but after i understand that you have to use a specific commands for the vbmeta i flash it again with the proper codes. Then after that i reboot the phone and it works, but the problem where i dont have a storage is there.View attachment 5347851
Click to expand...
Click to collapse
After i saw the problem i wipe the data by using the rui 2.0 stock recovery then the problem is gone but there's another bug where a specific files cant read by the phone. I dont know if its a bug or i just flashed wrong but it cannot read it. So i decided to go back to the rui 1.0 c.14 patch. And after i got back my files is okay and ready to be use.

I dont know but the early access of 2.0 seems a little bit buggy for me

Kristopher28 said:
" but there's another bug where a specific files cant read by the phone."
Click to expand...
Click to collapse
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Or else did you mean you got into bootloop.
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.

Flashing the vbmeta wrongly or wrong command usage May cause trouble. You may get boot destroyed msg but that can be solved by getting back to FB and installing properly the vbmeta.

jijojamie said:
After custom rom installation we have to do a data format to actually boot into it.
Try doing a factory reset or wipe data.
By the way i am using rm5p Indian variant.
Click to expand...
Click to collapse
Oh i think that's it. Because after i flash the rom and made a mistake in flashing vb meta verification. i didnt wipe the data i just reboot the system and I thought that it worked but as i discovered there's no storage. So after i saw that i flash the rui 2.0 stock recovery then wipe the data.

jijojamie said:
This is what i didn't understand. You mean to say, after rom installation you got into Ui 2.0 Android 11 and you cannot access your storage inside file manager.
Click to expand...
Click to collapse
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.

Kristopher28 said:
Yeah after the rom and then the vbmeta error it got worked but as soon as i open the storage there was none. After that i installed the rui 2.0 stock recovery and then wipe the data and then restart. After that the storage seems fine, but a specific files i want to see in my sd card is nowhere to be found. The "android data" specifically.
Click to expand...
Click to collapse
Now, this is precise. I just tried to access the data folder through es file explorer. Then system asked to grant permission and then system file manager came up. I just granted permission in that and the data folder is listed and visible.

Please be more specific which ROM did you dirty flash?

Its ok I managed to find the telegram group and files. I will try this out on monday after i have made a backup of my phone.

Point number 2. Stock firmware latest.

Cant find the files . Which telegram channel.
Link plz

Flashed TWRP, but no OS is working

Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.

asaeles said:
Redmi Note 8, I've successfully installed TWRP, then without taking backup attempted to wipe everything (including vendor & system).
Wiping of data failed.
Tried installing Pixel OS (non Plus version using ADB side loading), the OS started with the Google logo then it rebooted to TWRP.
Then I formatted data using Ext2 then using Ext4 then tried to wipe everything again and it worked (wiping everything system, data and vendor).
Tried installing Pixel OS again, but this time not even the Google logo appeared, just Redmi and then it reboots to TWRP.
I tried installing Pixel OS Plus, same.
I tried installing stock Mi ROM Global, this time it is stuck on the MIUI logo without doing anything, I have to reboot into recovery manually.
Tried Potato OS, same, stuck on startup potato logo.
crDroid, same, stuck on startup logo.
Now the only thing working on this piece of metal is TWRP, what to do?
Here are the logs from TWRP (compressed in 7z format): https://drive.google.com/file/d/1sfgYId00k-VRpzQ5VVC2mpP0rBRP1StB/view?usp=sharing
Oh, and one more thing, even though now TWRP doesn't show red error lines and writes successful after OS installation, there is only one line that bothers me on the screen saying: init_user0_failed, but it's not in red.
Click to expand...
Click to collapse
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)

loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Ok, I've downloaded an unofficial PixelOS for Samsung Galaxy A10, but inside the ZIP file I can't find something called vbmeta, where can I find it? Also if you have a specific A10 ROM in mind, please indicate.

loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Also why A10 specifically? I mean this is a Xiaomi device after all, so is this vbmeta thing generic? Same across all devices?

loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
It worked

loopypalm said:
flash vbmeta :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
you can find vbmeta in any A10 rom
reboot to recovery and flash latest stable OrangeFox as a normal zip
it will reboot to recovery
do a clean flash with your prefered rom
(you can find DFE here)
Click to expand...
Click to collapse
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working

asaeles said:
Now Pixel Experience is working, but up till now I have two major issues:
1) SIM card is not working (it's saying network disconnected)
2) This mobile is for my kid and Google Family Link for children was working fine and now it is saying "Can't set up supervision on this device", so the issue is not with my son's google account it's now with the device itself.
Does Google sense rooting? Is Pixel OS rooted out of the box?
I mean my daughter has the same model and I unlocked OEM installation and flashed TWRP and Google Family link is working
Click to expand...
Click to collapse
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...

Connectivity problems lead me to suspect it could be a firmware issue: either start from the beginning by going back to stock with MiFlash or try changing the firmware (see https://xiaomifirmwareupdater.com/firmware/ginkgo/).

loopypalm said:
try another rom (the rom i suggest is RRos)
and see if the sim network is connected (if not, it might be a sensor problem)
about google things = i don't know, i hate google ...
Click to expand...
Click to collapse
Thanks, here's a gift ;-) https://i.pinimg.com/originals/74/c0/e5/74c0e55d1fe725793e18758dcef11f72.png

How To Guide [GUIDE] Magisk on LineageOS

I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!

I just flashed Lineage, rebooted, set up the phone, rebooted into recovery and then flashed Magisk.apk after renaming it to Magisk.zip. After a reboot I opened the Magisk app (which was automatically installed when flashing Magisk) for the first time and it prompted me to do some additional operations. It survived an OTA update so it should keep working in the future.

The firts mentioned method does not seem to work with the new Magisk 24.1
Does anyone have a solution to this?
(Never mind ..you need to uninstall the earlier version,then it will work)

sburry said:
I found the steps to install magisk when using a custom recovery a bit confusing (I extracted boot.img from the stock image and then bootlooped my device after I flashed the patched boot.img...), so I thought I'd write this after having recently done it myself to help anyone else running into trouble. I did this on a Poco F3 global version with 12.5.4 firmware.
Prerequisites:
- LineageOS recovery + LOS already installed (so you can use Magisk app to patch recovery.img)
- working adb, fastboot, and so on
- download Magisk-v23.0.apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0
- download lineage-18.1-*-recovery-alioth.img from https://download.lineageos.org/alioth
Basing steps on https://topjohnwu.github.io/Magisk/install.html
1. Copy recovery-alioth.img to phone; I used 'adb push lineage-18.1-20211127-recovery-alioth.img /sdcard/Download/alioth.img' to do this
2. Open Magisk app and select Install for Magisk near the top
3. Use 'Select and Patch a File' method, finding and selecting the alioth.img file
4. Click LET'S GO and let it finish.
5. Retrieve the image from the phone; I used 'adb pull /sdcard/Download/magisk_patched-[random-strings].img ~/patchedboot.img'
6. Reboot phone to bootloader by running 'adb reboot bootloader'
7. Flash patched image via 'fastboot flash boot ~/patchedboot.img'
8. Reboot into system via 'fastboot reboot'
9. Proceed to installing modules.
I was able to install Magisk hide and props config and set device fingerprint to OnePlus 6T on Android 11, hiding root from almost all apps, and then pass safetynet. Any questions or input is appreciated, I hope this helps someone!
Click to expand...
Click to collapse
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!

ldm21 said:
Has anyone had issues with this? Some days ago this worked fine, but now Magisk does not let me access the "Modules" tab and Zygisk is not in the options in Settings anymore. I have a POCO F3 on Android 12, set the Fingerprint to a Redmi Note 10 to pass the CTS test (which worked and still works)
Any help would be much appreciated!
Click to expand...
Click to collapse
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed

Rstment ^m^ said:
You had update yesterday I think. Your magisk is no longer there - boot image is overwritten after ota update.
Open magisk and check, it'll likely say not installed
Click to expand...
Click to collapse
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!

ldm21 said:
Thanks for your reply. I'm quite new at this so I'm not sure what's going on: the latest Magisk release is still v25.2 and after following again these instructions but for v25.2, I still have the same issue. What should I do to fix this?
EDIT: you're right that it does say that it's not installed, but I followed the procedure from some days ago and it doesn't seem to fix it.
Many thanks again!
Click to expand...
Click to collapse
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
I think this is the equivalent of flashing the apk as zip in custom recovery, which is deprecated.
I compared the official one with the first post and I think the following is missing in the first post:
(Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
From:
Installation
The Magic Mask for Android
topjohnwu.github.io
Poco has a vbmeta but i never executed this step. The instructions say that it is optional but they don't specify it.
I used the first post since LOS18.1 and no problems. Since LOS19.1 updates give me bootloops so after some repair tries (and failed twrp restore) I did a fresh install and did not take the updates anymore. No idea if it has something to do with magisk or patching vbmeta. Soon gonna try to update LOS with magisk disabled.

Rstment ^m^ said:
Simplest option is to reboot phone to recovery , select adb update , connect to pc and do "adb sideload magisk.apk"
It will patch image for you, don't rename it to .zip or anything
Click to expand...
Click to collapse
Does this still apply to LOS20 and Magisk 25.2? After doing this, do I still need to extract the patched image?

Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful

[deleted]

johnr64 said:
Hi,
I run the Amazing Evo-X 7.4, that comes with it`s own built in Recovery, it`s OK but i prefer Orangefox or TWRP, as these have more features than Evo-X STOCK.
I use a program called "Temporary Recovery" and is installed using FASTBOOT and a PC, it doesn`t overwrite the original Recovery, in case you need stock for OTA Updates.
Once in Temporary Recovery i can install all my goodies, including Magisk v25.2 as you would with normal recovery,
once your finished installing your programs you have the option to make either OrangeFox or TWRP (temporary recovery) permanent.
Example below:
I install Evo-X and it overwrites my permanent recovery ,
i Re-boot my F3 into Fastboot mode and connect it to my PC,
I run "RUN_TWRP-Orange Fox FIXED.bat", i then have a choice of either TWRP or OrangeFox, once installed my F3 reboots into Temporary recovery, i then make Recovery permanent, Re-install "Magisk-v25.2.apk" from with-in recovery and carry on where i left off.
If your interested and would like to try it out, you can find
"Temporary Recovery" on the Evo-X thread page 1, post 20,
I hope you find this useful
Click to expand...
Click to collapse
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.

dangerousnerdrays said:
Not sure this is going to fit my particular needs. I'm looking to use LineageOS' recovery and stock, along with Magisk.
I had previously tried patching LineageOS' recovery with Magisk, pulling the patched .img to my desktop, then tried to fastboot flash boot <Magisk-patched>, but when I went to reboot to the system, it looped back to recovery, so I ended up going back a few steps to redo LOS recovery and LOS properly flashed.
At this point, I have a working LineageOS and recovery. I booted to the system, installed Magisk-v25.2, opened it, and did a direct install -which, if I remember correctly- is the temporary root I need in order to get root in whatever the next step is.
I just don't know what to do next.
Click to expand...
Click to collapse
lol... flashing patched image is all you need to do
Either via adb sideloading magisk.apk or manually flashing image both will suffice.
Just look at magisk app, if it doesn't say not installed then it is working