Database Info

SAFE rooting to HUAWEI MATE 9

hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all

one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting

Thx to reply. Like the others i wanna root to have root apps in my phone ,

Thx . Wanna have apps requires root in my phone . That simple

You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+

super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action

nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.

ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!

I failed install su however still waiting for any updates

nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?

ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!

FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.

Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk

FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD

ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310

nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.

mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
 @st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.

mr. ante0 ..... u r the man , thank you so much

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

[TESTING] Flash Patched boot.img to achieve Systemless Root

WARNING:
Please do every preparation that could fix your phone to original state before doing this trick.
DOING THIS MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
I managed to unpack the official firmware of Nokia 7 and 8, and patched their boot.img with SuperSU Systemless Root.
But I don't know if it works on them.
Patched boot.img can be downloaded at:
https://mega.nz/#F!igsBmarT!3rIjD4ZaZN8ueOTVmciGwg
Here's the method you need to do:
1. Install OST LA and patch it, and OPEN IT FROM INSTALLATION DIRECTORY DIRECTLY.
2. Flash required firmware before proceed. If you don't do that, you won't be able to access Wi-Fi after the boot.img flashed.
For Nokia 7, you need to use the firmware "C1N-0430-0-00CN-B05" which I haven't released to public for some reason.
For Nokia 8, you need to use the firmware "NB1-435J-0-00WW-B01" which released in this topic: https://forum.xda-developers.com/showthread.php?t=3678487
If you've already flashed required firmware before proceed, you can skip this part.
Click to expand...
Click to collapse
3. Use the Service Purposed Bootloader trick I've mentioned in the Nokia 6 Root Guide: https://forum.xda-developers.com/showthread.php?t=3702354
4. Type these commands:
Code:
fastboot-android flash boot_a E:\NB1-435J-Boot-Patched.img
fastboot-android flash boot_b E:\NB1-435J-Boot-Patched.img
fastboot-android reboot
For Nokia 7, use C1N-0430-Boot-Patched.img instead. I've attached the Firehose, rawprogram0 and patch0 for Nokia 7 in case you want to use EDL Mode on Nokia 7.
Click to expand...
Click to collapse
5. If it's accepted by the system, the phone will reboot twice, and you'll see SuperSU appeared.
However, if "Verification Failed" appeared on your phone, then the trick failed. You have to flash original firmware to restore your phone to factory state.
If anyone know how to fix that in boot.img, that's a breakthrough of Nokia Android Devices.
You may want to use Flashfire to flash Xposed Framework or something else, but DO NOT RECEIVE ANY OTA UPDATES after your phone rooted.
I'm looking forward to a boot.img manual patcher on PC or Phone available, which could patch boot.img to achieve Systemless Root either SuperSU or Magisk and bypass Verification Boot.

This looks exciting. I have to look deeper into recovery options before I dare this kind of experiment...

Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.

ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Click to expand...
Click to collapse
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?

hikari_calyx said:
Thanks for feedback.
I'll check if anything wrong.
Can you check if you can install SuperSU manually from Google Play?
After you installed it, is root available?
Click to expand...
Click to collapse
Nope. SuperSU said "Root not available"

Many thanks for your efforts on this patch, I would love to be able to root my Nokia 8.
Having an unlocked bootloader I am not really worried about, but having root access is a big feature for me.
Any chance this patch will become available to firmware version 00WW_4_390 which is the current latest? (And what my phone is currently running)
Not sure if I can downgrade it to NB1-435J-0-00WW-B01 or not, but I can try that if it is not able to be patched to the latest firmware image.

Thnx hikari_calyx for your hard work!
ansonscleung said:
Tried on a retail Nokia 8 TA-1052 running 00WW_4_35J_SP01
Boot passed but unfortunately no root
End up having to upgrade to 4390 using 4G
Update: Can't install 4390 even when I download the update multiple times. Flashed 435J using OST and tried flashing the kernel again but still no root.
Click to expand...
Click to collapse
Did anyone else but ansoncleung tried this meanwhile?

@hikari_calyx I have a self prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8

2WildFirE said:
@hikari_calyx I have a prepatched boot. IMG for TA1012, flashed via fastboot now I have root with Magisk, but WLAN won't work.
Powered by Nokia 8
Click to expand...
Click to collapse
Log

Op please pm me i am developer too we can do this together.

TheKsM said:
Op please pm me i am developer too we can do this together.
Click to expand...
Click to collapse
Hey we need developers here on Nokia!
And what we need to is a dev who build twrp for Nokia8. The recovery is inside the boot. IMG.
If you want build a one for the community. Thanks
Powered by Nokia 8

Question About the Beta P Program on Verizon

So I have a few questions about the android P beta program. I was wondering if anyone could answer before I opt into it
1) if I opt into I get ota updates which won't be Verizon variants so would I be able to jump back to Oreo?
2)would this allow me to unlock my bootloader possibly?

1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.

dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Thanks so much for this information I'm gonna opt in for the hell of it

dbrohrer said:
1) You should be able to go back to oreo by opting out of the beta and taking the subsequent ota from Google. Or you can manually flash a newer ota you downloaded from your computer. Must be a newer build than the the one you are on.
2) Almost certainly not. Unless there is some error, your bootloader will not be unlockable. You are not currently receiving "Verizon" builds. No such thing. Your device info is on a server side whitelist / blacklist. It has nothing to do with the build you have installed. That is my understanding.
Click to expand...
Click to collapse
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!

daede86 said:
Im not sure i understood this properly, I've already unlocked the bootloader of my Verizon pixel 2 on 8.1, if I update to P, will the bootloader be locked back? Or I can update and still enjoy the unlocked bootloader?
Thanks!
Click to expand...
Click to collapse
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.

dbrohrer said:
If you unlocked the bootloader already, it will stay unlocked until you lock it via fastboot from your computer. Flashing firmware will not relock it. Don't worry, updating to Android p won't mess with that.
I'm really enjoying this beta so far. The new navigation gestures are cool. Nothing so far that makes me want to go back to 8.1.
Click to expand...
Click to collapse
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!

daede86 said:
thanks so much! i've installed android p but i'm not able to root the phone.. i've installed magisk but it fails while patching boot.img.. any idea?
thanks again!
Click to expand...
Click to collapse
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.

dbrohrer said:
What version of magisk are you flashing? You should be using the beta magisk. Looks like people are having some success rooting with version 16.4.
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Hope this helps.
Click to expand...
Click to collapse
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!

daede86 said:
thanks so much!!
i'm trying to flash magisk using this tutorial https://forum.xda-developers.com/pixel-2-xl/how-to/guide-how-to-install-google-software-t3760535 but as soon as i launch fastboot boot [twrp image filename].img, it loads up twrp (i see the splash screen) but right after it crashed and reboot.. so i'm not able to flash magisk beta
is there a way to install magisk manager (beta) and being able to patch the boot.img without passing through twrp?
thanks again and sorry for all my questions!
Click to expand...
Click to collapse
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?

dbrohrer said:
Do you have the Pixel 2 or 2 XL? Are you booting with twrp 3.2.1-2 img?
Click to expand...
Click to collapse
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!

daede86 said:
i have a pixel 2 verizon with bootloader unlocked trying to boot twrp-3.2.1-2-walleye.img. am i doing something wrong?
thanks again!
Click to expand...
Click to collapse
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.

dbrohrer said:
That's correct. Just checking. You need to boot to twrp to flash magisk. There isn't another way that I know of. Maybe download twrp img again? I doubt its a corrupt download since you get the twrp splash screen, but its worth a try.
Click to expand...
Click to collapse
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?

daede86 said:
no luck
should i try to flash again the factory image?
or maybe opt out from androind p beta, install back oreo, root and flash android p without deleting my data?
Click to expand...
Click to collapse
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.

dbrohrer said:
You can boot into the OS right? Are you're platform tools the latest version?
Reverting back to oreo, rooting, and updating to p beta will either fail or wipe out root. You won't end up with p beta and root. Don't do that.
Click to expand...
Click to collapse
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup

daede86 said:
ok thanks again, really appreciated.
yes, at least i can boot and use my pixel with no problem, i'd only like to root it and restore my backup
Click to expand...
Click to collapse
I understand that. I am not sure whats going on then. Sorry.

i've solved the problem!! just to share, i had installed handbrake in my mac to share files via usb and i guess it caused some incompatibility issue.. i've just uninstalled it and i've managed to flash it properly!

Rooting on Android 10

Hi, Im new in this forum, just got my OP 7 Pro. I've been away from anything root related for a long time, since my previous devices couldnt be rooted.
I remember using magisk when it was a new thing, and everyone was using greenify to extend battery life.
I just updated to Android 10 Beta, can I root my device?
If it is possible, what do I lose if I root besides widevine?
The only thing I'm really looking forward is gcam port and the use of aux cams, since a lot of things have to be updated to Android 10, I don't think there's a lot to do right now besides that.

I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing

vuoshino said:
I think you have to come back to the android p stable, root, install the twrp and after you will able to update with the root. Now im on the beta with root and twrp throw a dirty installing
Click to expand...
Click to collapse
Hi! Thanks. If you don't mind, can you give point me to a guide or something to downgrade? I'm a total noob with everything OnePlus related.

You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345

There's also another way which avoids to downgrade.
Flash the magisk patched img you'll find in this forum.
After following instructions from there, you'll be rooted but without TWRP.
If you need that also... flash the TWRP installer zip as a magisk module, reinstall magisk (direct install), reboot and you're done.
Inviato dal mio GM1913 utilizzando Tapatalk

tidschi said:
You don't have to downgrade to Pie.
Do it like this:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
You just need stock boot.img:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Click to expand...
Click to collapse
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?

donelwero said:
Wow, thanks!! that seems stupidly easy, even for me. Two questions:
Do I need a PC to do the extraction?
Will this wipe any data?
And as for my initial question, is there anything besides widevine lost when rooting?
Click to expand...
Click to collapse
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.

tidschi said:
You can download Magisk patched boot.img from second link above.
Flashing boot.img will not wipe any data.
If I remember right, Widevine will get L3 with unlocked bootloader.
Click to expand...
Click to collapse
Awesome!! Thank you very much, thought I had to unlock the bootloader by myself using a PC.
Edit: I'm so dumb, just realized I still have to flash the boot.img using fastboot

I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?

littlejonny17 said:
I have a question, in order to root and flash twrp coming with android 10 (no root) I must unlock the bootloader, right?
Click to expand...
Click to collapse
Yes bootloader must be unlocked to flash TWRP or Root the device also when you unlock the bootloader it will factory reset the device so make sure you backup any personal data you need before unlocking.

Thank you

[CLOSED] Deleted

Here was a Guide. Someone said people don't care about Me or My Work so...​

Thank you

Hello,
I'm going into boot loop when I'm trying this :
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot continue
I have downloaded your img for Xperia 1
Can you help please ?

After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.

kelly669 said:
After multiple tentative your image was woking
But when I install your module in Magisk and restart, I get Pixel Launcher Stopped message (with rest pixel laucher or go to info) and I can do nothting : the message appears every time I click somewhere.
Thanks
Click to expand...
Click to collapse
Thats due to the Gesture Navigation. Please enable 3 Button Navigation To fix it... :angel:
daphix said:
when you say "module" what you reffer? pixel launcher or boot image? it's seems that the author posted here only boot image.
Is bettwer to build your own image instead to use one build by others;
The pixel launcher problem may be from not installing proper magisk module; check download section in magisk for necessary modules and also search on forums for pixel launcher prerequisites.
Click to expand...
Click to collapse
It was about My Work. There are No other Modules for the Pixel Launcher...
Since My Threads got moved from the Development Section am i No longer contributing Images Myself. Thanks to XDA and the Moderators!

Guide overhauled like promised to some <3 Let Me know if i missed something

Updated the Guide

Updated the Thread again with more exactly Instructions and a typo fix

Attempting to flash the vbmeta.img I have this problem:
unknown option fastboot --disable-verity
Any idea why fastboot can't figure this command? adb version 30.0.5
Also, what exactly is the reason to flash the vbmeta.img? Is this to allow the phone to boot with the patched image..?
I was still able to boot into android but I can't confirm if the devices is rooted or not.. all programs just hang with no confirmation if root access is granted or denied...

Will this work with android 11?

I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Miustone said:
Updated the Thread again with more exactly Instructions and a typo fix
Click to expand...
Click to collapse

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases

jt23738 said:
I get a boot loop when trying to flash magisk img on android 11 with magisk 20.3
Click to expand...
Click to collapse
Sorry I meant 22.1 magisk

Miustone said:
20.3 is totally outdated: https://github.com/topjohnwu/Magisk/releases
Click to expand...
Click to collapse
Any news on this ? I used the latest Magisk 23.0

My Xperia 5 is dead so i can't Test anymore... Sorry

Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Miustone said:
If You want to relock Your Bootloader...
-Just go into fastboot mode any type in the command prompt (like before in this Guide):
Code:
cd\
cd platform-tools
fastboot oem lock
-Wait for Your Device and disconnect it from USB
-Download and Install the "Xperia Companion" from SONY
-Open the Xperia Companion and select Software Repair
-Select that Your Device can't get recognized (or is a Smartwatch 3 lol)
-Go to the next Page and select the Xperia Smartphone Option
-Continue and wait for the Initialization
-Press and hold Volume DOWN while connecting to USB (You will see the Green Flashmode LED again)
-Continue once Your Device gets recognized and let the Xperia Companion do his work...
Done. Your Bootloader is locked again and most of Your DRMs are restored. But please Note, that 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 everyone else who has this Device in his Hands... (SONY knows it anyways).
Click to expand...
Click to collapse
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?

OutOfSync said:
Thank you @Miustone, your post has been a helpful reference. Some things change over time so it's good to have this guide that is current.
In your guide, I have been looking at the Flashing Firmwares and re-locking the Bootloader... section.
Please can you advise, confirm that while rooted with Magisk (v23.0), I can relock the bootloader so as to be able to get Sony OTA updates for my Xperia 1?
I had to download firmware with XperiFirm anyway, to get the boot img for Magisk to patch. And because it is newer firmware I just went and flashed it - also because I needed to fix the broken camera/torch caused by rooting with Magisk. So now everything is working again.
So I lose root but I can just root again with Magisk. At that point can I relock the bootloader so that I can receive OTAs, and still be rooted?
Click to expand...
Click to collapse
You need to choose.
Unlocked = Magisk/Root, Freedom, Control
Locked = No Magisk/Root, Freedom, Control
I do also recommend to wait for Pixel Experience. It will come soon with Mainline Kernels for many Xperias... Including OTAs

Hi guys, I cannot watch Netflix after unlock bootloader my J9110, it shows error 5.8. Tried many workarounds but none of them work.
I'm on Android 12 beta 5. Please help!

Thread Updates coming soon including Android 12 GSI flashing + Magisk