Develop Bugs

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes

[ZE620KL/Android 9][TREBLE] COMPLETE GUIDE: Unlocking, Rooting & Flash GSI + Fixes
Unlocking bootloader to Flashing GSI (Asus Zenfone 5 [ZE620KL] / Android 9.0)
Code:
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
About :
The last guide could leads to soft brick, as the instructions were not clear nor the files not supported for Android 9.0.
Here is a complete guide with TWRP 3.3.0 for Android 9.0, clear instructions and multiple fixes for GSI.
It has been tested on stock version v16.0615.1903.92.​
Requirements :
- A stock version V16.0610.XXXX.XX or higher
- A phone on Android 9.0 (not 8.0!)
- A fully working USB cable
- Latest ADB / Fastboot drivers
- Bootloader unlocker (download latest from Asus website or from here)
- TWRP 3.3.0 image
- Android9EncryptionDisablerZE620KL.zip
- Magisk v19.3​
Instructions :
Unlocking Bootloader
1. Backup all your important data.
2. Install the bootloader unlocker APK, and follow the steps. You will loss your warranty here, and it will factory reset your data
3. If there is any issue here, go into your stock recovery (volume down + power button) and factory reset.​
Installing TWRP
4. Shutdown your device & boot in fastboot mode using volume up + power button.
5. Check that the connection between your device and your computer by typing this in your command line :
Code:
fastboot devices
6. Flash TWRP recovery using :
Code:
fastboot flash recovery <twrp_name>.img
7. Now reboot in recovery mode using :
Code:
fastboot oem reboot-recovery
8. In TWRP, select Wipe > Format Data > enter "yes" and confirm
9. Return to the main menu, select Reboot > Recovery
10. Do 8. & 9. and again
11. Using TWRP or ADB, install Android9EncryptionDisablerZE620KL.zip (on TWRP, go into Install > find Android9EncryptionDisablerZE620KL.zip > Install zip)
If everything has gone successfully, you now have a custom recovery.
As for some GSIs, a patched boot partition may cause bootloop, you should try installing Magisk after installing the GSI. If you want to keep your stock ROM, go directly to "Magisk Installation" section.​Installing a GSI
This step may vary depending on the different GSIs distribution. I assume you install Havoc OS v2.7 GSI which actually works on this device.
1. Backup all your important data using TWRP backup.
2. Select the arm64-aonly GSI image you want, and move it on your external SD.
3. Wipe Data, Dalvik, and Cache.
4. Go back in the main menu of TWRP, and reboot to recovery.
5. Remove Magisk if it was previously installed, by using its uninstaller script.
6. Flash the GSI to system partition.
7. Boot and perform a factory reset.​
Installing Magisk
1. Add the Magisk zip archive to your external storage.
2. Boot into TWRP recovery, and install the zip.
3. Enjoy!​
Bug fixes:
Insufficient storage in the system partition to flash GApps : Download your OpenGApps archive on your external SD, and use MagicGApps 2018.9.23 to install GApps.
Auto-Brightness doesn't work: Download framework-res__auto_generated_rro.apk from here.
Using a root explorer or command-line, push the APK to /vendor/overlay.
Then run the following command in a rooted terminal or ADB shell:
Code:
chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay;chcon u:object_r:vendor_overlay_file:s0 /vendor/overlay/framework-res__auto_generated_rro.apk
My camera doesn't work well (green tint on face camera) and/or the app doesn't boot: If Asus Camera doesn't launch on your GSI, you should probably edit your /system/build.prob file.
You need to edit ro.product.model, ro.product.brand, ro.product.name, ro.product.device, ro.product.manufacturer & ro.build.product properties to be:
Code:
ro.product.model=ASUS_X00QD
ro.product.brand=asus
ro.product.name=WW_Phone
ro.product.device=ASUS_X00QD
ro.product.manufacturer=asus
ro.build.product=ZE620KL
You can instead use Google Camera mod (port from Arnova8G2 & modded by 5Z community, thanks to them!), which works well (edit: there is a bug on HavocOS, we can't access settings).​Bonus:
- You can reinstall DTS Headphone:X here.
- For booting your kernel in Permissive mode, check here
Sources:
TWRP 3.3.0 : On GitHub
If you need help or if you want to help on ZE620KL development go here:
https://t.me/Zenfone5Dev
(We will continue to update & help here though.)
Many thanks to all of the Zenfone 5 community (particularly Emincan, Pandolfi and Lmajkej),
Phhusson & Erfan for their works on GSI, and Shakalaca for its work on TWRP 3.3.0!​

On HavocOS v2.8 GSI (13-08-2019):
It works:
- Almost anything
- Adaptive Brightness (after manual fix)
- Notch overlay
- DTS Headphone X (after manual installation)
- NFC
- Face unlock
- Stock camera (after manual fix)
- Magisk
- SDcard access
It doesn't works:
- VoLTE / VoWifi
- Google Camera settings
- External speaker amplifier (NXP amp)
- APT-X / APT-X HD bluetooth
- Low microphone in normal use
- No microphone in calls (only headphone microphone works)

GCam settings
But my google camera keep crashing when I want to go into camera settings

Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but everytime it asks permission it always say this

bentley0928 said:
But my google camera keep crashing when I want to go into camera settings
Click to expand...
Click to collapse
Same issue here. I will update the thread when I will find a more working GCam port (perhaps, this GCam port works well on ZenUI)
Jolo110 said:
Hi thanks for this tutorial, this is my first time rooting my phone. I'm encountering a problem with my sd card after installing havoc os, everytime i try to move, save or any write functionality i do to my sd card, it always says the android version isn't compatible. I could still see my files from my sd, but every time it asks permission it always say this
Click to expand...
Click to collapse
It's a known issue, the GSI maintainer @vince31fr is working on it. I don't have it, but I can advice you to use Solid File Manager, which works like a charm on my device.

"- No microphone in calls (only headphone microphone works)"
Funny... I'm on stock latest firmware and I have this issue, so I thought I try something new, and this has that issue. It can't be a coincidence. Something is ****ed up with this device.

Wonder if this will work for the Zenfone 5 Lite (or 5Q)? I wanna root my 5Q so bad haha

Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!

Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!

Hello do I need to flash Android9EncryptionDisablerZE620KL.zip if Im gonna flash a non-GSI custom ROM? Or its only for GSI Treble ROM?

[email protected] said:
Hi!! I thanks for these instructions you gave. I know this post is a bit older. But is the only one I think could help me.
I got an ZE620KL and I'm trying to root this device. I have some experience in unlocking bootloader and rooting devices. But this one... Is giving me a lot of work. Researching in a lot of forums and websites I tried a lot of things with no success. In theory, is just install the official apk provided by ASUS and run the application. But the app doesn't work for a long time as I researched (error accusing network problem). I tried unlock via fastboot commands but I always got stucked by "remote: permission denied" even with latest drivers and ADB Fastboot installed. And yes... I let my device with no one security feature enabled and didn't worked. I tried everything even after wiped data / cache and factory reset and no progress.
In my researches, I realized something about 'oem unlock'. It appears to be the key to solve this. And I guess the tool to work with this is the damn unlock tool from ASUS which don't work! Also, I've heard about workaround with Magisk by flashing a custom recovery to achieve the root. Magisk no longer supports zip files to flash. Only '.img' and '.tar' files. I'd like to find some light here... I don't know what to do. I appreciate any help!
Click to expand...
Click to collapse
Im not sure if you still have your phone or you have successfully unlocked bl. but I found an updated version of their tool which works.
*tried unlocking from android 10 not working, it says device model not supported*
Zenfone 5 Unlock BL

cf100clunk said:
Thanks for the great instructions! Steps 1 through 11 worked perfectly for me, then I installed LineageOS (lineage-17.0-20191231-UNOFFICIAL-treble_arm64_avN.img) and it works properly. Then when I go back to TWRP and install Magisk v20.1 it reboots into an endless Lineage bootup logo animation (not boot loop). I can get an adb shell, but now also the external SD card has become invisible. Any suggestions?
UPDATE: I switched over to the patched Magisk version from PHH (https://forum.xda-developers.com/zenfone-5/general/ze620kl-add-support-to-evey-android-9-t3966918) and everything works perfectly now!
Click to expand...
Click to collapse
Do you still have the patched Magisk zip file, the original link in the post seems not working

Realme X2 1993 development

I open this thread because in my opinion the development situation of the various versions of the device is very confusing. I seem to have understood that as regards the unlocking of the bootloader with a working fingerprint, the situation is evolving well only on the China and India version while on the European version nothing moves ... In my modest opinion, Realme deciding to treat those who buy its phones in Europe as users of its lower series devices compared to other areas of the world are wrong because little development leads to a few posts in the various forums and few voices in google searches that each of us does when deciding what to buy ... What do you think you realme device owners in Europe?

I have the 1993ex version and the FP is working fine after a16

hammerheading said:
I have the 1993ex version and the FP is working fine after a16
Click to expand...
Click to collapse
Thanks for the information ... What procedure did you use to unlock the bootloader?

I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device

Bolumstar said:
I have EU version and what you said is true about Realme but development aspect, most procedures on China version works on EU version but may partially work on Indian version.
I've tweeted Realme EU over 7 times they haven't replied yet.
MY advice for EU and rest of the world is not to buy from Realme if you want active development and OEM response. Otherwise, you can be patient by using Realme OS until there is bigger development for your device
Click to expand...
Click to collapse
So you too like me, although there is news of the working fingerprint on the EU, believe that it is still not worth unlocking.
I ask it because I repeat following the various treadhs on the forum it gets confused. It is sometimes indicated that the finger epint works and that for example magisk can work in normal mode and not core only ... This would already be a lot, to say yes it could use the viper4android.

surferbyter said:
Thanks for the information ... What procedure did you use to unlock the bootloader?
Click to expand...
Click to collapse
I used this guide, it works the same for X2.

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?

surferbyter said:
Excellent, and as regards the installation of the twrp, which vbmeta file did you use?
Click to expand...
Click to collapse
First time i flashed the twrp i folowed this but now i simply skip the vbmeta and flash twrp directly from bootloader and it works fine.

Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu

woocashewski said:
Just installed havos os 2.9 gsi, so, it's not that bad rmx1993ex eu
Click to expand...
Click to collapse
never installed a gsi, if I'm not mistaken it takes the image of the vendor ... if you can give me a link to a guide to get started? Thanks in advance...

Howto thread is on this forum...

woocashewski said:
Howto thread is on this forum...
Click to expand...
Click to collapse
I'm doing something wrong because i get bootloop everytime. i tryed to follow the guide with different gsi but no luck. Can you give a quick step how you did it ?

Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...

surferbyter said:
Until the twrp installation everything works perfectly, when I install magisk whether I try to do it from zip recovery or from boot image patched the verification of the integrity of the verity boot sends me to bootloop. You would need the vbmeta, but when I try to flash the vbmeta.img the command:
fastboot flash --disable-verification vbmeta vbmeta.img
On the fastboot cmd he replies that - - disabled verification is unknown ...
Click to expand...
Click to collapse
I've been there, i think the problem was the adb. I used the Minimal adb and it worked, give it a try

first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition

woocashewski said:
first - check everything with adb prior to installing anything - get most recent version - i'll get v41, check if there is adb connection - by adb devices, if no - troubleshoot as in many threads here on xda until everything works.
at this moment i've got Havoc OS v 3.0 installed, unfortunetely with same limitations as 2.9 - no FP, no lux metering, and weird battery behaviour (sometimes cpu isn't clocked down when screen off - it can be tuned by eg. Kernel adiutor after rooting with magisk flashed from twrp.)
simplified guide:
- unlock bootloader
- flash twrp from fastboot
- select to start recovery on phone's fastboot menu (volume keys+confirm by power)
- enter your password to decrypt data
- flash vbmeta.img from PC by adb command
- at this stage I made a restart to twrp from twrp menu
- there's shouldn't be any prompt about data encryption
- made a cpmplete backup of the phone - backup to SD card, or to internal and at this stage copy entire backup folder to PC
- wipe: dalvik/cache/system/data
- install system img from a file GSI
- reboot to recovery
- install gapps, if error 70 --> goto wipe, advanced, resize system partition, back to install, install gapps
- reboot
if bootloops - format data partition
Click to expand...
Click to collapse
So gsi roms also have fingerprint problems ... However, more than a custom rom, I was interested in coloros with root ...
I can't give up the fingerprint though because some applications of the company I work for use it for authentication ...

I managed to root, magisk 20.3 zip flash on twrp, on the European version a17 with this guide:
https://forum.xda-developers.com/showpost.php?p=81579961&postcount=44
To make the vbmeta flash command work I used the minimal adb version 1.43, with previous versions it doesn't work.
The fingerprint works very well and energy consumption has not changed compared to use with locked boot.
After carrying out all the procedure, the magisk manager indicates the certified safety net unlike the play store which is instead not certified. To have it certified, you need to download the Device ID app, copy the GSF code that gives you the result by opening it and insert it on the page of this link:
https://www.google.com/android/uncertified/?pli=1
After having it delete the data of google service framework and google play store, force the arrest of the second and reopen it ...

hammerheading said:
I used this guide, it works the same for X2.
Click to expand...
Click to collapse
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63

Sandalwood83 said:
Except the deeptesting apk in that guide isn't compatible with the x2 - at least not with the eu version. Funnily enough the apk for the realme 5 is compatible - see this post: https://forum.xda-developers.com/showpost.php?p=81014949&postcount=63
Click to expand...
Click to collapse
Ok my bad then, i follow more than one guide so im not sure were i got the apk from. anyway good job finding it for future unlocks!

ROM Stock EU Version
Here the ROM Stock EU https:// drive.google.com/file/d/1-GpV3YBMCCCrQPvCKqqK3cYRXmBMzTCy/view?usp=drivesdk
Just copy the link

GUIDE: Install GSI Treble Roms on Honor 8X Max ARE-AL00

Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?

hatemelectr said:
Hi,
Great job, very detailed.
I've faced a situation when trying to flash many GSI img's (Lineage 18, Pixel Exp+, AOSP). The recovery (stock then TWRP) returned "image is too large for the partition". I've ARE-AL00C (4/128) with unlocked BL. Is there any workaround ?
Click to expand...
Click to collapse
Some images simply do not work, so you will need to check for other images simply.

Just install this one : https://github.com/phhusson/treble_...nload/v222/system-quack-arm64-ab-gapps.img.xz
root&gapps&backlight working
of course you'll need Device+ID.apk and register ID with Google but that's easy and simple

Device: Huawei 8x Max AR00
The Quack version works but sadly it is Android 10. I have found many Android 12L GSI roms that I would like to use but the brightness is an issue on all of them. Anyone know how to copy the Quack backlight vendor display and patch it to the newer GSI roms? Tried buildprop GSI wont boot (Crdroid, Lineage 19) Tried Dirty flashing, obviously didn't work. Can't seem to find the file containing the slider brightness limitations. Phherson gives rom backlight options and tried several combinations, and yes rebooted everytime none of them work. Any ideas?

riadtaihi said:
Hello Team,
Well, I wish that there was a special special section for the Honor 8X MAX, as there was so many things we can add to it, but well, let's post in this section
Most devices that came with Android 8.1 are likely to be Treble GSI compatible, so, the thng is that you just gotta find what Partition it uses.
For this device, it was kinda tricky as it was supposed to be A partition but I found out that it on EMUI 8 neither or AB worked, so after several tests, I found out that using any EMUI 9, we gotta use AB and not A, so I tried LOS 17.1 and worked like a charm but as TWRP is not the best for this device and I did not want to bother decrypt it, then root and install GAPPS, I preferred to install AOSP 10 from phhusson now and it works like a charm. The pros of this rom are that it is already "Rooted" and "Gapped", so I would highly recommend it :good:
Requirements::
* Unlocked Bootloader (Not explained here, so you need to use HCU Unlock and purchase a credit for that);
* Your Recovery has to be stock, so if you have TWRP, I recommend to reflash the stock one;
* Choose an ARM64 AB GSI Rom from here;
BUGS:
1. The device might show as not certified, so you won't be able to use any Google services until you register your device. Guide from Androidsage to help doing that;
2. Brightness seems to be at 50% when set at a maximum. This issue might be due to the Vendor Overlays (not a 100% sure though), I am investigating this, but I am using the device as it is and it is fine for me, until we find a solution for it.
Quick Guide:
1. Turn off your phone and then start it with Power and VOL+, until you see the message of the unlocked phone;
2. Wait until you see the Stock recovery not eRecovery;
3. Wipe and reset, Type "YES" and wait for wiping;
4. Plug the USB Cable to PC, reboot the phone while pressing VOL - ;
5. You should see the Android Fastboot now;
6. On Windows download ADB tools and Linux or Mac they can be added using terminal (You can find it easily by doing a simple search);
7. To make sure the phone is correctly connected, type in the CMD Line or Terminal: fastboot devices ;
8. You should see a series of numbers, so now you can flash by typing: fastboot flash system WHATEVERGSIIMAGEYOUCHOOSE.IMG ;
9. Wait about 2-3 minutes and then when the flash is finished, type: fastboot reboot ;
10. That's it! Your phone should now boot to your preferred GSI ROM with more or less everyhing working
Click to expand...
Click to collapse
After trying many different gai variants and versions I found they all have an issue with browsers. Both chrome and edge freeze after scrolling a bit. I'm wondering if this because the GSI uses too much storage space and cannot buffer? Tried to port GSI onto other partitions such as cust, prod didn't work. Even Magisk flashes successfully but does not appear in the rom. The a and b is confusing like EMUI uses both and the TWRP does not decrypt and no Verity commands don't work either. The havoc rom seems to work the best with gapps pico flashed.
~ Android 12 backlight issues had to revert to android 10
~ All GSI have the common browsers freezing. Have to use VIA browser (basic)
~ Magisk won't install have to port to ramdisk, but isn't that the TWRP recovery?

Hello, which one is the Qualcomm driver to be installed for sdm660?

How To Guide guide unlock bootloader & enable root (magisk)

Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* 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 kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
GUIDE UNLOCKING BOOTLOADER & ROOTING Xperia 10 III (PDX213)​STEP 1 - UNLOCK YOUR BOOTLOADER
1- GUIDE UNLOCK BOOTLOADER XPERIA
2- WEB UNLOCK TOOLS BOOTLOADER XPERIA
STEP 2 - DOWNLOAD FIRMWARE STOCK USING XPERIFIRM
STEP 3 - extract boot_X-FLASH-ALL-8A63.sin using zip file manager ( 7zip, for ex here I used Ark zip manager from Fedora OS)
rename boot.000 to boot.img
STEP4 - install magisk manager in your phone from official github release
- open magisk patch your boot.img
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
ENJOY

Nice! Now maybe someone can look into fixing that green tint.

zpk787 said:
Nice! Now maybe someone can look into fixing that green tint.
Click to expand...
Click to collapse
idk what issue your referering ( maybe thread green tint in oled
? ) here I have totally normal screen color

So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?

pepijndevos said:
So I have my bootloader unlocked, developer mode on, USB debugging on, LineageOS 18 GSI installed, and reboot into fastboot with `adb reboot fastboot` but
Code:
$ fastboot boot Download/magisk_patched-23000_BOvMB.img
Sending 'boot.img' (98304 KB) OKAY [ 3.595s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
What?? I also tried to go into bootloader, but similar result. Did I mess up the boot.img?
Click to expand...
Click to collapse
For some reason bootloader no allow fastboot boot
Need : fastboot flash boot patchedboot.img

Yea it's just really scary to flash a patched firmware, what if you did it wrong and it bricks your phone. But well in the end I did it and everything worked out.
One really weird error I get from Magisk is that it says it's in an abnormal state because there is a "su" command that doesn't belong to Magisk. I have no idea where that came from. Should I be concerned? Everything seems to work as far as rooting is concerned, but mysterious su commands could be a security concern maybe. I hope it's not a sketchy GSI or something hehe.
Anyway thanks for your guide. I have MicroG and F-droid working now, as well as ACC. One thing I'd clarify about your guide is that "going into fastboot" is... actual fastboot and not bootloader or recovery which you also use with the fastboot tool. Just a thing that's obvious when you know, but uncertain when you're doing it for the first time.

Oh and another thing that was sliiiightly puzzling is that you actually have to copy the boot.img to your phone, patch it and then copy it back to your PC. Same thing, obvious when you know, kinda puzzling when it's your first time. For me it didn't show up in the file manager after patching so I had to copy it with adb, not sure what that was about.

Did anyone notice negative effects after rooting?
Is the camera working fine?
Is Bluetooth working, the microphone and calling?
Is safetynet check passing?
My main goal is to have Adaway working in root mode and have stable Wireguard VPN connection (without battery saving methods killing the process every few minutes), I will try custom ROMs after I get the rest to run.

Camera, bluetooth, microphone, calling, all working fine. No idea about safetynet haven't checked. As mentioned above, it does say I have an extra `su` that I don't know where it came from.

Did you do any backup of the TA partition (if that is even neccessary)?

I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.

pepijndevos said:
I did not. Not even sure what the TA partition is haha
Of course backups are always a good idea when possible. It just seems a lot of the stuff out there assumes you have TWRP.
Click to expand...
Click to collapse
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!

Raubsau said:
Check this: https://forum.xda-developers.com/t/does-rooting-sony-phone-still-lower-their-quality.4318171/
And more generally https://www.xda-developers.com/sony-xperia-android-pie-unlock-bootloader-drm-fix-camera/
I gather that the devices with Android 9 or above can safely be unlocked, but that does not necessarily mean everything works with root.
I just want to avoid rooting the device and realizing I need some DRM keys that I lost.
Please update us should any problems arise!
Click to expand...
Click to collapse
This is exactly the reason why I haven't rooted my device yet, too. If I understand it correctly, data in the TA partition is modified at the time the bootloader is unlocked, so if we were to create a backup, that would have to happen before unlocking.
The partition is only readable with root privileges, and rooting in general requires an unlocked bootloader. The only way forward is to wait until an exploit becomes available, allowing us to obtain a root shell with the bootloader still locked.
Hopefully it's possible to flash older firmware onto this phone, which would mean we can downgrade to an older Android security patch level if needed (i.e. the potential exploit gets patched by Google or a vendor) - does anyone here know if that's the case? When installing an OTA update, the UI says we won't be able to return to a previous version, but I suppose it's still possible to flash any of the official firmware packages at any point.

Thanks.

Is there any way to get OTA updates while rooted? That's what I loved about LOS. Maybe we'll get it on this device someday.

Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted

Unfortunately many users report a WLAN issue with 62.0.A.3.163.
62.0.A.3.131 cannot be downloaded anymore, except the french (FR?) localized versions. Also, I managed to install 62.0.A.3.131 on a 10 III, but denied the update to the latest version to avoid the WiFi troubles.
The boot.img from 62.0.A.3.131 (FR) and 62.0.A.3.163 (EE) differ. I wonder if anything could go wrong with the newer boot.img.
To my understanding, the boot.img contains the kernel... So, I'd like to test it with "fastboot boot boot.img" before I risk flashing, but: "remote: 'unknown command'".
Any suggestions on how to proceed from here?

You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/

ZenRebel said:
Thanks for this post. I have managed to unlock the bootloader which is great, but I am not sure how to -
STEP5 - go in fastboot and enter :
fastboot flash boot boot_patched.img
Update: I have not rooted
Click to expand...
Click to collapse
If you've managed to unlock your bootloader, that means you have already entered fastboot mode.

combinedfleet said:
You can find earlier firmware versions, including "XQ-BT52_Customized EEA_62.0.A.3.131", here: https://forum.xda-developers.com/t/stock-firmware-backups.4382229/
Click to expand...
Click to collapse
Man! Thank's a lot!
Any idea why the boot_X-FLASH-ALL-8A63.sin files differ slightly even if compared between markets (with the same version numbers)?

Question Rooting with Magisk failed (FAILED (status read failed (Too many links)))

Hello everyone,
I have a new Xiaomi 11T EEA device, tried rooting it with the following steps, but failed:
- Updated to the latest official MIUI version (13.0.9.0)
- Unlocked bootloader with MiUnlock (shows the unlocked padlock at boot, and also in developer options)
- Downloaded the latest ROM with the updater app in phone (also tried from c.mi.com, same files, checked checksums)
- Used payload dumper at PC to extract the boot.img from the ROM
- Installed latest Magisk Manager (25.2) to the phone
- Pached the boot.img with Magisk
- Installed latest adb and drivers to my PC (restarted it after the install)
And then I tried booting the phone to the patched boot.img (fastboot boot patched_boot.img), but failed (even tried with the stock boot.img, same result):
downloading 'boot.img'...
OKAY [ 3.188s]
booting...
FAILED (status read failed (Too many links))
finished. total time: 11.135s
I tried with my PC, with another notebook, 3 different USB A to C cable, 2 different USB C to C cable (different orientations too), all of the USB ports on the devices, but I got the exact same result.
So far I succeeded with these steps with 3 other Xiaomi phones (Redmi Note7, Mi 9T, Poco F3), but not with this one, and I have no idea what else I can do.
I suspected it has something to do with MediaTek SOC, that's the only meaningful difference I can think of.
Does anyone have any idea what else I can try, or maybe have a working patched boot.img?
Thanks for reading it, have a nice day!

Once the boot modify install with Fastboot, use fastboot reboot.

NOSS8 said:
Once the boot modify install with Fastboot, use fastboot reboot.
Click to expand...
Click to collapse
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.

s-zoli said:
Maybe I understand it wrong, but I didn't install the boot.img, and don't really want to install it until I am sure I don't soft brink the phone.
Click to expand...
Click to collapse
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?

s-zoli said:
It will be rooted until reboot, which is fine for a temporary root and testing things before making it permanent.
From my understanding it should be working either way, booting to it, or flashing right away. Previously I tested the patched boot.img just by booting into it, and worked every time. At the Redmi phone when I tried to flash the boot.img (that was used to boot into and worked), it didn't boot and got stuck to fastboot, and had to flash back the original boot.img.
I read the mentioned thread, it's the same steps I did, except the last booting vs flashing with fastboot.
Am I missing some key information how the booting mechanism works?
Click to expand...
Click to collapse
Newer devices have A/B partitions unlike old ones.

NOSS8 said:
Newer devices have A/B partitions unlike old ones.
Click to expand...
Click to collapse
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?

s-zoli said:
So you are saying that flashing the boot.img replaces both A and B partition and will most probably work, even if booting into it doesn't?
Click to expand...
Click to collapse
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?

NOSS8 said:
The .img boot never replaces the partitions, I was answering that you had already rooted other but old devices, that is to say without A/B partitions.
And why do you want to root this model with soc MTK(No or few development for Xiaomi with Mediatek processors)?
Click to expand...
Click to collapse
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?

s-zoli said:
The Poco F3 is a newer phone, and I just checked with Treble Check app, that it has seamless system update, therefore A/B system partitions (and so does the 11T).
The reason is the same as for every other phone... customization, automations, battery management... etc.
The things that should be available for power users, not just in fancy gaming phones.
It just happens to have MTK instead of QC (like the 11T Pro).
Do you have any information if this SOC difference can affect the booting and therefore rooting it?
Click to expand...
Click to collapse
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.

NOSS8 said:
MTK=MediaTek
QC=Qualcomm
Change nothing at the root level.
Everything you want to optimize is possible without rooting, moreover you will have to install modules which themselves consume battery.
Except for personalization.
Click to expand...
Click to collapse
Sure, you're right, but I already started the rooting process, the bootloader is unlocked, so I already lost a few things (Google Pay, Netflix... etc).
The only way out is re-lock the bootloader or find a way to install Magisk and modules for it.
We deviated a bit from the original question...
I haven't found any source of information what does "Too many links" error means?
Also I didn't find any information if I can easily get back to original state if flashing the supposedly good pached boot.img doesn't work. (bootloop, stuck at fastboot... etc)
My way of being somewhat sure it works was first booting to it, but that doeasn't work now, and it's suspicious for me that the flashing won't work either.

To have the play store certified, use Magisk + zygisk.
https://topjohnwu.github.io/Magisk/
https://www.droidwin.com/fix-status-read-failed-too-many-links/
Once the boot modify install with Fastboot, use fastboot reboot.

Long story short... I just went for it and flashed the patched boot.img, and it's working just fine.
I don't know why it didn't want to boot, but flashing worked and now I have root access.

NOSS8 said:
Obviously if you don't flash the modified boot.img, the phone won't be rooted.
See here (different device but same method).
https://forum.xda-developers.com/t/root-xiaomi-11t-pro-on-latest-miui-13-working.4450535/
Click to expand...
Click to collapse
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img

bluviper said:
thats snapdragon, and this is mediatek
will this work with mediatek? without specifying a/b partitions?
Code:
fastboot flash boot patched_boot.img
Click to expand...
Click to collapse
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.

NOSS8 said:
Check:
https://www.xda-developers.com/how-to-check-android-device-supports-seamless-updates/
getprop ro.build.ab_update
Then you will know which command to choose.
Click to expand...
Click to collapse
i have the a/b partition

bluviper said:
i have the a/b partition
Click to expand...
Click to collapse
So,use
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
or
fastboot flash boot_ab patched_boot.img
fastboot reboot

I just flashed without _a _b or _ab and it flashed still to both slots