....I hope the phone dialer will be fixed too.Thread Updates coming soon including Android 12 GSI flashing + Magisk
lolI was dead for a number of years, and was resurrected by a sith lord.
Excuse my newbnessness, Respectfully...
Is there any particular reason we're not using TWRP? or is it just an option? or is it to do with this A/B Treble stuff? or just because it can be done without?
lol
Older Xperia like 2019 and back are using the Kernel for the Recovery. Means we always need a new Boot Image once we get Updates. We don't get updates anymore and newer Xperias have an extra partition for the Recovery. So if someone is willed to build TWRP that works with the latest Stock Firmwares it would be nice. But we don't have one yet so the only way is this Guide... Sadly
You just need to flash vbmeta if You have Issues booting Up an specific GSI. Google provides just Images for that, that we can also use on Xperias. Otherwise just flash the OEM AOSP Binaries from Sony If You want to use GSIs. They May Help on some functionality here and there...Hi Miustone... Just a question to clarify regarding ''vbmeta'.
Do I use Google's vbmeta only if it is needed? otherwise ignore it, and use stock?
^what a horrible question...
Thanks so much!!! On Android 12 now and it's perfect... At the moment on PE, trying others now too...You just need to flash vbmeta if You have Issues booting Up an specific GSI. Google provides just Images for that, that we can also use on Xperias. Otherwise just flash the OEM AOSP Binaries from Sony If You want to use GSIs. They May Help on some functionality here and there...
You encountered a Bug of older Magisk releases. Just use the recent one. @Robot76 just managed it one Post before yours. "Your Temp Fix" was known for Long and isnt needed anymore on Magisk 23/24+DO NOT FOLLOW THIS GUIDE if your system build is Android 11
I have carefully followed it for five times in the past and every time it led to brick.
Not because of A/B partition or flashing a different image or reasons like that, it was just simply because Sony added 「system_ext」code in android 11 so directly flash magisk_patched.img will 100% brick the phone.
Use Android Image Kitchen to unpack the img and delete the code in ramdisk file and repack it, then it can be flashed.
I'm lucky that I have been doing this a long time in the past, that my experience showed me this this was the easiest flash of my life, it was over in maybe 1-2 minutes tops, making this the easiest flash yet (my device was locked and was Android 11 stock, and I was on Linux, making preparations a little complicated).DO NOT FOLLOW THIS GUIDE if your system build is Android 11
I have carefully followed it for five times in the past and every time it led to brick.
Not because of A/B partition or flashing a different image or reasons like that, it was just simply because Sony added 「system_ext」code in android 11 so directly flash magisk_patched.img will 100% brick the phone.
Use Android Image Kitchen to unpack the img and delete the code in ramdisk file and repack it, then it can be flashed.
Solved this shortly afterwards. The ubuntu repository (kubuntu) for platform tools was incomplete, once I downloaded Google's platform tools and 'copied' (cheated) the missing files into "/usr/lib/android-sdk/platform-tools/", 'mke2fs' in particular (the commands were unable to utilize ubuntu's own using e2fsprogs), once doing "fastboot -w" , everything behaved as it was supposed to.I was on PE 12 GSI and life was beautiful... ....I then decided to experiment with LOS, and so I erased Userdata...
Then I failed to install it stuck on LOS logo...
Whenever I use ' fastboot -w ' I get this ouutput:
Erasing 'userdata' OKAY [ 73.324s]
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
Have I missed something? is it because I f'd myself, and I need to flash stock, re-lock, and repair, and start again?
4. Bootloader Unlocking and Magisk Root:
Note: Since You are going to unlock Your Bootloader, You may surely want to get Root. So let's start with Magisk or it will take more Time afterwards...
Note: Unlocking Your Bootloader erases Your unique Device Key FOREVER. That will flag Your Device as "it was unlocked". This can be checked by SONY and (maybe) everyone else who has Your Device in his Hands...
- Download UnSin from XDA and extract it somewhere
- Download the "Platform Tools" (Fastboot/ADB) from Google and extract it to the root of Your Windows Drive
- Download and install the Magisk Manager on Your Xperia Device
- Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)
- You will get a .img File which You can patch now with the Magisk Manager on Your Xperia
- Open the Magisk Manager and go into the Settings. Tap on the Update Channel and Select the Beta Channel
- Go back to the Main Page of Magisk and install Magisk by selecting the Image File You just got from UnSin
- Copy the magisk_patched.img in /download from Your Device to the Platform Tools Folder
- Grab Your Device again, go to "About Phone" in the Settings and tap several Times on the build Version
- Go now to the Developer Settings under "System" and enable "OEM-Unlock" and "USB-Debugging"
- Use now the Platform Tools with this Commands:
- Type now (Step by Step):
Note: To use the Platform Tools Folder as environment for Fastboot and ADB. Or hold Shift and Make a right Click in the Platform Tools Folder to open the Command prompt there...Code:cd\ cd platform-tools
- Type now:
You will get a prompt on Your Xperia Device. Your Device will Reboot afterwards...Code:adb reboot bootloader
- Now Your Bootloader Unlock Code:
Code:fastboot oem unlock 0xYOURKEY
- Wait for it... And type now:
Code:fastboot reboot
- Wait for Your Device to Wipe and Start. Once in the Android System, turn Your Device off without USB Connected
- Press and hold now the Volume UP Button while connecting to USB to enable the fastboot Mode
- Continue with flashing the Images for Root (Step by Step):
Code:fastboot flash boot_a magisk_patched.img fastboot flash boot_b magisk_patched.img
- Wipe and Reboot:
Code:fastboot -w fastboot reboot
(SONY knows it anyways since You have to order a Key with Your IMEI).
Hey! Which OS so far suits the best? Can you suggest pls?Thanks so much!!! On Android 12 now and it's perfect... At the moment on PE, trying others now too...
![]()
cd\
cd platform-tools
adb reboot bootloader
fastboot oem unlock 0xYOURKEY
fastboot reboot
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot -w
fastboot reboot
fastboot flash system_a system.img
fastboot flash system_b system.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
[Optional] fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
fastboot -w (This does Format Your Device and is needed everytime You change the GSI!)
fastboot reboot
fastboot oem lock
lolI was dead for a number of years, and was resurrected by a sith lord.
Excuse my newbnessness, Respectfully...
Is there any particular reason we're not using TWRP? or is it just an option? or is it to do with this A/B Treble stuff? or just because it can be done without?
Thanks so much!!! On Android 12 now and it's perfect... At the moment on PE, trying others now too...You just need to flash vbmeta if You have Issues booting Up an specific GSI. Google provides just Images for that, that we can also use on Xperias. Otherwise just flash the OEM AOSP Binaries from Sony If You want to use GSIs. They May Help on some functionality here and there...