[GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares

[suntanfrodo]

I followed the guide step by step and my phone is now stuck in a bootloop.

I have a XQ-AS52 with firmware 58.1.A.1.178 (Customized EEA). Here is what I did:
- I already had USB debugging and OEM unlock enabled
- I followed the OP's guide to a T (with Magisk beta channel and all that)
- I flashed the magisk_patched.img to both partitions a an b in fastboot
- At this point, I had not used the Newflasher tool at all
- When I finished flashing the images, I got "Your device can't be checked for corruption. Please lock your bootloader"
- That repeated a few times and then it showed "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
- To get out of that bootloop, I used the firmware boot_XXX.img file (that i got from the XperiFirm and Unsin tools) and flashed it in fastboot mode. However, I did not specify any partition, and just wrote "fastboot flash boot_XXX.img" and it showed that it was flashing that to partition b.
- The phone did boot up afterwards but still showed the "Your device can't be checked for corruption. Please lock your bootloader" message
- I allowed the USB debugging again (but could not find the OEM unlock in the Developer options because I guess the bootloader was already unlocked)
- I pasted the Newflasher files in the folder of the firmware downloaded by the XperiFirm tool
- I turned off the phone and put it in flash mode
- I ran the newflasher.exe file as admin and did "f, n, n, y" (fastboot, no, no, yes)
- But now my device is in bootloop again with the same messages as above and won't power up.
- Even if I redo the step of flashing the boot_XX.img file in fastboot mode, it still shows the same error.

I have Android 11 by the way (if that helps) and a previous user said to use another method than magisk as it is not currently working with Android 11 (which I, unfortunately, did not do).

Can anyone please help?

EDIT: I managed to get my phone out of the bootloop and it is working now. But it still unrooted and I guess I won't try rooting it again until we have experience trying to root Android 11, especially with Xperia 5 ii.

This is what I did to get my phone out of the bootloop:
- I installed the Sony Companion app and chose to repair the phone
- I do not know how much battery I had but I guess it was enough for the Sony Companion app to work
- The app would not work with an unlocked bootloader. So you have to boot into fastboot mode and lock the bootloader again.
- The app would guide you for the next steps. Basically, it would ask you to turn off the phone, disconnect it from the computer, choose repair in the app, boot into flash mode by pressing the volume down button while plugging in the cable
- if everything is fine (it was in my case), the companion app would reflash the phone with the original firmware and it should boot up normally again.

So my phone is back to operational right now, albeit with bootloader locked and unrooted

 

[doggydog2]

Negative guy is right, rooting was easy back in the day.. i have my 10y old files here for such phones as S Plus, Note 2 (didn't root earlier decade of HTC phones) and it was as easy as flashing one file
Last 3-4 years it got difficult unless you have OnePlus or Google device. For these phones, there's just few UI clicks to upgrade, and no tracking of IMEI.
But I will root til i die, so many benefits.. I switch between ~4 flagships a year, and I have hundreds of apps in the exact state on each phone. And the Magisk, Xposed plugins are so necessary..
Having said that, is Xperia5ii ok to upgrade to new firmwares? The OP says data is lost on each update, but some guys encourage otherwise.

 

[Bellitsch89]

I followed the guide step by step and my phone is now stuck in a bootloop.

I have a XQ-AS52 with firmware 58.1.A.1.178 (Customized EEA). Here is what I did:
- I already had USB debugging and OEM unlock enabled
- I followed the OP's guide to a T (with Magisk beta channel and all that)
- I flashed the magisk_patched.img to both partitions a an b in fastboot
- At this point, I had not used the Newflasher tool at all
- When I finished flashing the images, I got "Your device can't be checked for corruption. Please lock your bootloader"
- That repeated a few times and then it showed "Your device is corrupt. It can't be trusted and will not boot. Your device will be powered off in 5 seconds"
- To get out of that bootloop, I used the firmware boot_XXX.img file (that i got from the XperiFirm and Unsin tools) and flashed it in fastboot mode. However, I did not specify any partition, and just wrote "fastboot flash boot_XXX.img" and it showed that it was flashing that to partition b.
- The phone did boot up afterwards but still showed the "Your device can't be checked for corruption. Please lock your bootloader" message
- I allowed the USB debugging again (but could not find the OEM unlock in the Developer options because I guess the bootloader was already unlocked)
- I pasted the Newflasher files in the folder of the firmware downloaded by the XperiFirm tool
- I turned off the phone and put it in flash mode
- I ran the newflasher.exe file as admin and did "f, n, n, y" (fastboot, no, no, yes)
- But now my device is in bootloop again with the same messages as above and won't power up.
- Even if I redo the step of flashing the boot_XX.img file in fastboot mode, it still shows the same error.

I have Android 11 by the way (if that helps) and a previous user said to use another method than magisk as it is not currently working with Android 11 (which I, unfortunately, did not do).

Can anyone please help?

I had the same Problem with Android 11.
I have tried very often with Android 11 but IT doesnt works. With Android 10 IT works but I cant change any System files, like delete System Apps or change "normal" Apps like nova launcher to a System-App.

 

[suntanfrodo]

I had the same Problem with Android 11.
I have tried very often with Android 11 but IT doesnt works. With Android 10 IT works but I cant change any System files, like delete System Apps or change "normal" Apps like nova launcher to a System-App.

How did you recover your phone when you encountered that problem?

I cannot get my phone out of that bootloop

 

[Bellitsch89]

I have locked the bootloader, then I have flashed android 10 and then I have made a repair with xperia companion. You can load the battery with the original Sony Power Adapter. IT will bootloop every time but IT will load.
You must at the right Moment press the volume down or up and connect to PC then you can Flash and lock the bootloader.

I hope you unterstand me because my Englisch is Not the yellow from the egg

Edit: in this thread

Phone bricked , stuck in bootloop

forum.xda-developers.com

I have found the solution. The last 3 or 4 replies has help me.

 

[suntanfrodo]

I have locked the bootloader, then I have flashed android 10 and then I have made a repair with xperia companion. You can load the battery with the original Sony Power Adapter. IT will bootloop every time but IT will load.
You must at the right Moment press the volume down or up and connect to PC then you can Flash and lock the bootloader.

I hope you unterstand me because my Englisch is Not the yellow from the egg

Edit: in this thread

Phone bricked , stuck in bootloop

forum.xda-developers.com

I have found the solution. The last 3 or 4 replies has help me.

It worked! Danke dir

 

[Bellitsch89]

It worked! Danke dir

Kein Problem

 

[BlackSalami]

I ****ed up somewhere and had to use the Xperia companion app to repair the phone after being stuck. But now my device is on Android 11 and I'm unsure if this tutorial will work or even serve a purpose now that I've learned Magisk is not working properly on android versions past 10. I'm too scared of bricking my device so I guess I'll give up on fully owning this one

 

[Thelemic]

So I searched far and wide but there's no option to backup the DRM keys for the 5 II yet, correct? I'll probably have no use for it but still.

 

[NoroXX]

Hi - step 27 tells me that the .img is too big to download .... what about that?

 

[NoroXX]

Otherwise, the tutorial is great, thanks for that

 

[reclaimerog]

I'm having the absolute worst time trying to root my sony xperia 5 ii.
I have the USA variant XQ-AS62 build number 58.0.A.28.51
I do NOT want to move to android 11, im still stuck nearly at the begining of the entire process
when i look at xperiafirm its only offering me the a11 update which i dont want to do. if anyone is kind enough to please help me out via voice or chat ill gladly compensate you with 125 bucks when we are finished. I'm not completely illiterate when it comes to things like this but its been a long while. my email is [email protected] message me there then we can figure out discord or phone call. thank you guys.

 

[AgashU]

EDIT: Realised this has been posted in the rom section by fengmubai here:

[KERNEL] Stock Kernel Patched with Magisk on Android 11

The boot image patched with magisk for Xperia 5II (AS72, Customized HK). Download it form Google Drive. If you patch stock boot image without fixing on Android 11, Xperia 5II will be bootloop. Here is the solution to fix it. I have only patched...

forum.xda-developers.com

If anyone has the XQ-AS72 (Hong Kong) Xperia 5 II on software version 58.1.A.3.87, I have uploaded the fixed boot image patched with magisk as there are problems when flashing magisk on Android 11.
Link:

44.69 MB file on MEGA

mega.nz

Works well on my device, but please make sure you have the correct variant and software version before flashing.

 

[NoroXX]

Hello. Has anyone managed to root the Xperia 5 ii XQ-AS52? I tested the procedure repeatedly /with build 58.1.A.5.55 and 58.1.A.3.87/ The result is always the same - bootlop The new .img is not loading ... Can't anyone advise what to do with it?

 

[b0r000]

@Miustone Have you tried that on Android 11?
Soft version 58.1.A.5.55 to be specific. I've tried that yesterday and it was epic fail. Not sure what went wrong.
Phone ended up in bootloop but luckily Xperia Companion was able to revive it to "factory" state.
I've looked around how's the state of rooting Android 11 looks now (I'm quite outdated when it comes to modding phones) but it seems it was taken care in Magisk 21.0. So I'm really lost what could go wrong?

 

[Miustone]

The Problem is explained here :

Bootloop after installing the patched boot image on Android 11 on Sony Xperia 5 II · Issue #3752 · topjohnwu/Magisk

ISSUE DESCRIPTION After trying to install Magisk with the patched magisk_boot.img from the latest Canary (and Beta) version of the Manager, the device is unable to boot and goes into the bootloop. ...

github.com

Let's hope for a fix asap...

 

[robi101012981]

Hello, I just got my 5 II and I would like to root it, but I do have some questions.. Right now I'm on Android 11 and I would like to if rooting it's possible, because, as I've read here, rooting it's more difficult on android 11 than on 10. If I'm rooting, can I still receive OTA updates or I'm stuck on that certain version?

 

[rayman2k1]

Thank you for the guide!!

Got my AS72 shipped from HK this week and did both the OTA updates to bring me to Android 11.

Followed the guide (boy has it been long since I've done a bootloader/recovery/rom replacement) but ended up with a bootloop. It seems that Magisk cannot patch the 58.1.A.3.87 properly.

I was able to resolve the bootloop by getting into the bootloader (Vol+, plug in USB) and just doing

fastboot flash boot_a <unpatched boot.img from XperiFirm+UNSIN>
fastboot flash boot_b <unpatched boot.img from XperiFirm+UNSIN>

So, now this puppy is sitting with the latest firmware, but with an unmodded bootloader (essentially where it was after the fastboot oem unlock step).

Will do some more digging to see if there are any updates to the Magisk/Android 11 situation. If anyone has cracked this nut, I'd appreciate any and all help!

EDIT: Wow, I can't read. Looks like @AgashU has posted a patched bootloader. I will try this now!
EDIT2: Thanks to @AgashU for pointing me to this thread where I downloaded the patched Magisk-patched partition.

 

[robi101012981]

Thank you for the guide!!

Got my AS72 shipped from HK this week and did both the OTA updates to bring me to Android 11.

Followed the guide (boy has it been long since I've done a bootloader/recovery/rom replacement) but ended up with a bootloop. It seems that Magisk cannot patch the 58.1.A.3.87 properly.

I was able to resolve the bootloop by getting into the bootloader (Vol+, plug in USB) and just doing

fastboot flash boot_a <unpatched boot.img from XperiFirm+UNSIN>
fastboot flash boot_b <unpatched boot.img from XperiFirm+UNSIN>

So, now this puppy is sitting with the latest firmware, but with an unmodded bootloader (essentially where it was after the fastboot oem unlock step).

Will do some more digging to see if there are any updates to the Magisk/Android 11 situation. If anyone has cracked this nut, I'd appreciate any and all help!

EDIT: Wow, I can't read. Looks like @AgashU has posted a patched bootloader. I will try this now!
EDIT2: Thanks to @AgashU for pointing me to this thread where I downloaded the patched Magisk-patched partition.

What about AS52?

 

[rayman2k1]

What about AS52?

I'm not really sure what you mean, exactly, but I imagine that the procedure would be the exact same, except for the part where you download the firmware, you'd need to grab the one that is right for your phone...