Database Info

S7 edge - systemless root + xposed + android pay

(posted previously in the wrong section)
Anyone using systemless root + xposed and android pay?
I was able to use systemless root with magisk v3 + phh superuser + systemless xposed without any problem however flashfire was not working since I cannot also make chainfire supersSU to work in s7 edge...
( releases after v3 up to v6 are not supporting well samsung - I verified though with the android version G935FXXU1BPH6 which also might be causing issues).
However after updating this version G935FXXU1BPH6 it seems to cause issues with TWRP and only boots to the last (twrp-3.0.2-3-hero2lte.img) and now I cannot go systemless at all because magisk v3 is not working aswell, root simply is not recognized.
SO basically now I'm using stock phone as I wanted to use android pay.... any ideas or anyone with any sucess?

im using v6 without problems. BUT you have to root with cfautoroot and unroot with superSU one time. i think that superSU changes something in boot.img that magisk needs to work ...
after that you have to use phh superuser.
pogo work
Flashfire will not

ok

inteks said:
im using v6 without problems. BUT you have to root with cfautoroot and unroot with superSU one time. i think that superSU changes something in boot.img that magisk needs to work ...
after that you have to use phh superuser.
pogo work
Flashfire will not
Click to expand...
Click to collapse
This works fine as does systemless xposed etc. Did you pick the option to restore stock boot.img when you uninstalled SuperSU?
My banking apps can still detech phh's root. Wondering if the modified boot from SuperSU is the cause. Might just need to wait for Magisk V7 which shouldn't need this workaround.

Galactus said:
This works fine as does systemless xposed etc. Did you pick the option to restore stock boot.img when you uninstalled SuperSU?
My banking apps can still detech phh's root. Wondering if the modified boot from SuperSU is the cause. Might just need to wait for Magisk V7 which shouldn't need this workaround.
Click to expand...
Click to collapse
No. Restore stock boot.img doesn't work for me
Gesendet von meinem SM-G935F mit Tapatalk

Install xposed and KoalaCoak you don't need to be unrooted

That is only for ANZ and Westpac internet banking, not Android Pay? Is that correct? Have you got it working for Android Pay?
Cheers.

playingbball20 said:
Install xposed and KoalaCoak you don't need to be unrooted
Click to expand...
Click to collapse
What bank app are you using? And can you use Android pay?
Cheers in advance

Dear,
I am new to s7 edge
I have g935FU1BPI6 installed .
I would like to install systemless root/xposed/recovery,
Is it possible?
Please guide,
Thanks in adv

earth08 said:
Dear,
I am new to s7 edge
I have g935FU1BPI6 installed .
I would like to install systemless root/xposed/recovery,
Is it possible?
Please guide,
Thanks in adv
Click to expand...
Click to collapse
Read up on Magisk. Systemless Xposed is pointless as you can't bypass safetynet

If we get update and if we update.
Is it require to wipe data after flashing twrp?

[GUIDE] Lenovo P2 Marshmallow Root

EXPLANATION
Hello friends, I will tell you how to get a Root without bootlooping Lenovo P2 device. Looking at other methods, you can get root without any problem if it is a little longer.
FOOTNOTE
Remember to take a backup of your device in case of any problems.
My, OneTeam and XDA are not Responsible for Possible Problems.
Your device needs to be unlocked by OEM.
Your device must have TWRP installed.
ROOT LOADING INSTRUCTIONS
First of all download all the Files Needed from Below.
When the download is completed, all files are discarded.
Install Magisk Manager Application from the link below.
Install PhH's SuperUser Application when installation is finished.
Once the installation is done, start your device in TWRP mode.
Then load the zip files you downloaded from below.
Install Install / Magisk-v11.1_OneTeam.zip.
When the installation is complete, install the Install / SuperUser- R259_OneTeam.zip file.
Restart the device when installation is complete.
Your device will be root when your device is restarted.
DOWNLOAD LINK
Magisk Mana​​​​​​ger​​​​
phh's SuperUser
Magisk-v11.1_OneTeam.zip
superuser-r259_OneTeam.zip
Credit
@wzedlare
@kaankulahli
@DeftonesOT

There is already a guide to root with TWRP.
Would be great if you find way to root with exploit - without TWRP

pabgar said:
There is already a guide to root with TWRP.
Would be great if you find way to root with exploit - without TWRP
Click to expand...
Click to collapse
That guide causes bootloop on F2FS.This method also works on f2fs file system.

I have a problem with this guide though. When I install Magisk through TWRP, when it flashes boot, it gets stuck, screen goes black for a while, then the phone vibrates and shows blue notification LED.... Really don't know what that's about

ThomBwha said:
I have a problem with this guide though. When I install Magisk through TWRP, when it flashes boot, it gets stuck, screen goes black for a while, then the phone vibrates and shows blue notification LED.... Really don't know what that's about
Click to expand...
Click to collapse
Turn off the phone and try again. The black screen and blue led is QFIL mode

Does this method will break OTA updates feature? Sorry if i'm asking a newbie question. I want to root my P2 but at the same time want to get OTA update so this is why making me keep stock till now

kenji1996 said:
Does this method will break OTA updates feature? Sorry if i'm asking a newbie question. I want to root my P2 but at the same time want to get OTA update so this is why making me keep stock till now
Click to expand...
Click to collapse
I do not know, I did not try

Would this root work for the P2c72?

Laubscherc said:
Would this root work for the P2c72?
Click to expand...
Click to collapse
Worked P2a42 and P2c72

kenji1996 said:
Does this method will break OTA updates feature? Sorry if i'm asking a newbie question. I want to root my P2 but at the same time want to get OTA update so this is why making me keep stock till now
Click to expand...
Click to collapse
Shure it will

Is any of our (unfortunately only) few developers handling P2 working/trying to look for a method of rooting without unlocking bootloader?

spawnn617 said:
Is any of our (unfortunately only) few developers handling P2 working/trying to look for a method of rooting without unlocking bootloader?
Click to expand...
Click to collapse
Try Kingroot.

Do we need to unlock the bootloader and wait for 14 days to apply this root method ?
Please add it to this guide if so.
Thanks.
EDIT :
Your device needs to be unlocked by OEM.
Your device must have TWRP installed.
I didn't see it when I read the post for the first time. So we do have to wait 14 days before flashing TWRP.

ROOT LOADING INSTRUCTIONS
Click to expand...
Click to collapse
I simply flashed superuser-r259_OneTeam.zip, install phh's SuperUser and got root without Magisk.

@EypCnn
Sorry for reply on a months-old thread but, has anyone firgured out how to root and install custom roms without unlocking Bootloader? I got a Chinese unit and not having a Chinese number is huge roadblock for me. :/

Is it necessary to flash both supersu and magisk for rooting device?? Will the device get rooted if i flash only Supersu?

There is not a lot of Updates released by Lenovo for this model, so if it breaks the OTA, just download from here

bl00dsoaked said:
@EypCnn
Sorry for reply on a months-old thread but, has anyone firgured out how to root and install custom roms without unlocking Bootloader? I got a Chinese unit and not having a Chinese number is huge roadblock for me. :/
Click to expand...
Click to collapse
Without unlocking bootloader you cant do anything
Sent from my Lenovo P2 using XDA Labs

Will this method work with the S244 Nougat build?
I have a P2c72 model hardware which I bought from China, but it came loaded with P2a42 firmware which updated itself to Nougat S244 via OTA updates. I'm not sure how to root it and I'm currently in the 14 waiting period to unlock the bootloader!

EypCnn said:
EXPLANATION
Hello friends, I will tell you how to get a Root without bootlooping Lenovo P2 device. Looking at other methods, you can get root without any problem if it is a little longer.
FOOTNOTE
Remember to take a backup of your device in case of any problems.
My, OneTeam and XDA are not Responsible for Possible Problems.
Your device needs to be unlocked by OEM.
Your device must have TWRP installed.
ROOT LOADING INSTRUCTIONS
First of all download all the Files Needed from Below.
When the download is completed, all files are discarded.
Install Magisk Manager Application from the link below.
Install PhH's SuperUser Application when installation is finished.
Once the installation is done, start your device in TWRP mode.
Then load the zip files you downloaded from below.
Install Install / Magisk-v11.1_OneTeam.zip.
When the installation is complete, install the Install / SuperUser- R259_OneTeam.zip file.
Restart the device when installation is complete.
Your device will be root when your device is restarted.
DOWNLOAD LINK
Magisk Mana​​​​​​ger​​​​
phh's SuperUser
Magisk-v11.1_OneTeam.zip
superuser-r259_OneTeam.zip
Credit
@wzedlare
@kaankulahli
@DeftonesOT
Click to expand...
Click to collapse
Why upload zips with your name and not a link to the original developer.
View attachment 4312159
Sent from my Lenovo P2a42 using Tapatalk

Official Xposed for Nougat is out! Post your Xperiences...

Have you installed official Xposed for Nougat?
Does it work fine on your MotoZ?
Any performance issues/lags?
Please add details on your ROM version, root method and if you have Magisk installed too or not...
Thank you.

I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.

lilloscar said:
I have this rom
Android Nougat on Moto Z (All Unlocked Versions) and rooted in the way that post says.
Installed xposed OK via TWRP, modules are correctly checked and enabled but didn't work, for example greenify didn't recognize that xposed is installed so didn't show the option.
Now I have missed data connection so am going to reinstall the same rom on the dirty way to not lose data and reinstall everything.
Click to expand...
Click to collapse
Two things...
- Greenify needs to fix its compatibility with Nougat, it's a known bug
- It is *needed* to use new official Xposed apk v.3.1.2 to manage modules activation. I've seen that unofficial or old version aren't able to enable them properly...

Thanks I have just read that about greenify, the list of compatible modules with nougat is short at this time guess so
Sent from my XT1650 using Tapatalk

Mine doesn't boot with xposed installed.
Stock 7.1.1 with turboZ and magisk

I remember that installing magisk caused a bootloop on my stock 7.0

I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).

Hi my fried. How long time this reboot in minuts?
Thanks
Ano59 said:
I had forgotten what modifications I did to my 7.0 stock (retus), trying to flash Xposed on it prevented it from booting (probably because of verity-dm) so I restarted from scratch.
1) Downloaded 7.1.1 stock from here and flashed it. Downloaded and installed 2 OTAs from system updates then.
2) Flashed latest TWRP (3.1.1-0).
3) I've read various reports of latest Magisk not working on Moto Z. Gave it a try though. Flashed Magisk v14.0, everything went well and I got back root access.
4) Tried installing systemless Xposed, however install failed from Magisk Manager, flashing the zip succeeded in recovery but Xposed wasn't recognized after reboot.
5) So I flashed classic Xposed (arm64) following these instructions, everything went fine (after one very long reboot).
Click to expand...
Click to collapse

josenilsantana said:
Hi my fried. How long time this reboot in minuts?
Thanks
Click to expand...
Click to collapse
It took maybe 15-20 minutes for the first reboot.

For me systemless Xposed install e worked properly too.
Ano59 said:
It took maybe 15-20 minutes for the first reboot.
Click to expand...
Click to collapse

[Guide] Install Magisk for root & xposed framework and have working OTA updates

Most Nexus phones users use magisk in order to be able to have root and xposed and also be able to easily pass safetynet check tests in order to be able to get OTA updates.
Well now magisk 14.4 works on our device and OTA updates should work just fine according to this https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Of course when Android Oreo rom comes out we should wait before applying it just to be sure that magisk and twrp will work on that rom so that we wont be left without root after updating (or brick the device.
I wrote a guide for installing magisk 14.4 on our device having 2nd october OTA installed, i copy it here so that more people can see it.
DISCLAIMER - USE AT YOUR OWN RISK! Bellow steps worked for my device but they might brick yours, you might lose warranty etc.!!!!!!
I am not a developer, I am just a user that wants to have the new phone setup like the older phones in my possession before using it as the main everyday phone.
All below packages are here due to the hard work of the people who made them. If you use them, give them the appropriate credits. This is also the reason that I don't attach any files in this post, I only give links to download the packages on the the forum threads/ sites I also found them.
Here I just show a combination of packages/ programs that worked.
PREREQUISITES:
1) Read the whole guide before starting. Make sure you are familiar with all the terms used and you understand what you are doing in each step.
2) I advise you to firstly download all the needed packages and have them in a folder in your computer and also make a copy of them in your phone and then start with the steps of this guide.
3) In this guide I use a windows pc. Fastboot commands are written in cmd. If you use a pc with another operating system, just make sure you can use adb/ fastboot commands and that you can also use miflash or another tool to flash the rom to your phone.
4) Make sure you have correct adb drivers installed in your pc. For this guide I have used adb-setup-1.4.3.exe from this thread.
So this is the step by step procedure with links:
Flash official rom with miflash
rom image: Here is the latest rom. (tissot_images_7.10.14_20171014.0000.00_7.1_d791bf99f4.tgz is the image I used while writing this guide)
miflash: MiFlash2017-7-20-0.zip
Boot to freshly flashed rom,
Install second october OTA update (75mb),
Do reboot and wait a few minutes until the update is installed.
If you have not done any changes to your device (other root like supersu, old magisk verision etc) you can ignore above step.
From settings-->developer options:
Usb debuging on
OEM unlocking on
Just to be on the safe side for magisk manager app also go to Settings --> Security and enable Unknown sources.
Then shutdown phone, boot phone to fastboot with Vol- & power button,
send the command "fastboot oem unlock" in order to unlock bootloader.
Phone reboots by it self if I remember correctly.
Boot to rom, now being unlocked, and see the splash screen to see if it says "Unlocked" to be sure that it is unlocked.
Then shut down the phone.
Again boot phone to fastboot with Vol- & power button,
boot twrp (just boot, not flash) with command "fastboot boot recovery.img"
recovery-3.1.1-1
From twrp, install Magisk-v14.4-20171103-073038
It installs magisk 14.4 but magisk manager apk version installed with this is 14.0.
So, in order to have magisk 14.4, reboot to rom, uninstall magisk manager and then install Magisk Manager 5.4.0 (as suggested by matcho13579) MagiskManager-v5.0-20170513.apk
The problem now with this version of magisk manager is that it installs modules correctly and they work just fine, but the installed modules are not listed in magisk manager modules page (they work but they cannot be seen). That means that you cannot disable a single module, you have to enable magisk core mode to disable all of them or normal mode to have all modules enabled - I hope this will be fixed in a newer version. Magisk-v14.4-20171103-073038 zip file as I said installs magisk manager 14.0 which also appears to be working, but I did all tests on my device with MagiskManager-v5.0-20170513.apk installed.
Next, inside magisk manager downloads, search and install xposed framework sdk 25 systemless by topjohnwu.
After installation is completed reboot phone (phone boot takes some time at this step).
Then install this Xposed installer apk -material design XposedInstaller_by_dvdandroid_31_10_17.apk.
Now you have October 2nd update rom in your device, magisk 14.4 & xposed framework.
If you select magisk core only mode (which disables magisk modules), have enabled magisk hide and hide it form all apps except the ones you want to have root access, the device passes safetynet and theoretically you can install OTA updates (xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled), according to this link
Inside magisk manager you can also install this MiA1Plus_V1.01 module in order to enable camera2api & EIS, to be able to use google camera application.
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working, I have not tested it thoroughly though:
https://forum.xda-developers.com/showpost.php?p=73340439&postcount=2
https://forum.xda-developers.com/attachment.php?attachmentid=4317286&d=1509267532

After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk

How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.

Aman301582 said:
How do I flash stock recovery. I flashed twrp earlier and cannot find stock recovery. There is no recovery.img in the tissot system image.
Click to expand...
Click to collapse
Recovery is included in boot.img

tidschi said:
Recovery is included in boot.img
Click to expand...
Click to collapse
Which means I'll lose root after flashing ?

Aman301582 said:
Which means I'll lose root after flashing
Click to expand...
Click to collapse
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?

blackyz01 said:
After installing xposed... Safety net goes fail
Sent from my Mi A1 using Tapatalk
Click to expand...
Click to collapse
As I have written in the first post "xposed framework -systemless or not- does not pass safetynet, but being installed systemlessly through magisk, it can be disabled"
This means that if you enable magisk core mode which disables all modules or if you disable xposed framework module, it passes safetynet.

tidschi said:
Yes, but it takes 1min to boot to TWRP, flash TWRP and Magisk?
Click to expand...
Click to collapse
Okay, managed to get stock recovery back. But 2nd ota is not installing. Always fails

Why install old Magisk Manager? New one seems like it works, unless I am missing something..

ilpanos said:
Finally, i installed gravitybox using gravitybox non-fbe 7.0.4 - 29/10/2017 and it also appears to be working
Click to expand...
Click to collapse
Only one question about this: why did you choose NON-FBE version instead of the normal one?

Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?

matcho13579 said:
Only one question about this: why did you choose NON-FBE version instead of the normal one?
Click to expand...
Click to collapse
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.

suryaabadsar said:
Thank you :good::good::good:
this is worked for me
but i have a qu. how we will update next OTA?
Click to expand...
Click to collapse
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.

Will we lose root after an OTA update?

You have to do the procedure as described in the link I have provided in the first post. I am putting it again here:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

ilpanos said:
Just because unfortunately it seems that FBE is not currently supported on our device and it is using FDE.
Perhaps the normal version also works, but I didn't want to be in a situation where I find out in the future that something doesn't work correctly and I have to uninstall it.
Click to expand...
Click to collapse
I'm currently using the normal version and everything is working as intended.
That's why I ask, because it might not work the same way with Magisk (I used CF-Root + SuperSU + standard Xposed method)

ilpanos said:
First we have to make sure that magisk works correctly in the new OTA. Then and only then, enable magisk core mode to disable modules and pass safetynet and update according to the instructions in the link I have on the first post.
Click to expand...
Click to collapse
I HAVE UNROOT PHONE WITH THE SAME METHOD AND RE-LOCK BOOTLOADER WITH FASTBOOT COMMAND fastboot oem lock
NOW OTA WILL WORK PROPERLY ON MY PHONE.?

Thanks for the perfect guide.
One side note: official ROM on the provided link is already version .30, so no need to boot into the ROM and install the updates, the update is already merged in

@ilpanos hello mate! I just ordered my A1 from Trading Shenzhen. I have an clear conception what to do with my A1 when it has arrived. So therefore I am collecting some knowledge about flashing and modding (I am not a beginner, but not familiar with A/B partitions). Your thread is very useful here, many thanks.
I have still one question and maybe you can answer it: i would like to remove the google apps from the system, but I don't know if this works just like usual (to remove it from /system/app or priv-app). The reason is that I am using microG instead gapps.
Or will removing files and folders screw up something?
Thanks in advance!
Cheers!

Well, the thing is that by even mounting system partition as read-write ,and of course doing any change - even adding a line in build.prop - disables the ability to do OTA updates. You will have to reflash the new rom for each update. This is the purpose of this thread, to show that there is a way to mod root etc systemlessly without loosing the ability to update (of course under certain conditions).

[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