yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
HMMMM......HELP!!

I flashed twrp.img in userdata, then afterwards, my phone began to enter boot loop however times I flash a whole official firmware I had been using!! What the hell is going on!!:crying::crying:

EDIT: Finally it's fixed!!!! Just after posting this one!!!:good::good::good:
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
I failed the first method, and now I am trying the second one. boot.sin was in H8266*.ftf file which is in zip format, but converting boot.sin to boot.img is tough. boot.sin is actually just a tar file containing boot.cms and boot.000, but if I tried to extract it to elf file with flashtool, flashtool says "unknown format"!!!! JUST a tar file!!! It doesn't know tar.

$ tar tvf boot.sin
-rwxr-xr-x 0/0 1328 2009-01-01 08:00 boot.cms
-rwxr-xr-x 0/0 67108864 2009-01-01 08:00 boot.000

Then, how can I make boot.img from boot.sin or boot.tar?:confused:
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
I use xperifirm to download the firmware

And Unsin.exe to convert the .sin file

Both are on XDA

But I heard that the magisk manager app can open boot.sin files directly.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Now I tried to patch boot.sin directly, only to find magisk recognizes it as a tar file and says boot.sin has no booting function.....
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
Oh, then use the UnSin.exe from XDA first

It works on windows and Unix/Linux (mono)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] shoey63:
Or flash new firmware, fastboot boot twrp and backup boot. Rename boot.emmc.win to boot.img and use Magisk to patch it.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Thank you.... I tried to root my XZ2, but it doesn't work. I don't know magisk really patched correctly....or I did something wrong.

My procedure is as follows (a bit long, but this is my adversaria):

Retrieve boot.sin from .ftf file which is actually a zip file on PC (in my case, Linux.) My ftf is H8266_52.0.A.8.131_1313-4500_R5B.ftf.

Convert boot.sin to boot.img using UnSIN.exe (see this thread.. ) In short, "UnSIN boot.sin".

put MagiskManager-v7.3.2.apk in a directory in SD card in xperia xz2.

flash xperia xz2 firmware (clean install)

install MagiskManager.

boot and enable developer mode without registering anything.

"adb devices" to confirm adb is available, then "adb reboot bootloader" to enter flash mode.

as usual, "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"

as usual, "fastboot boot twrp.img"

In twrp, advanced wipe data, internal storage, and dalvik.

boot to system.

Put boot.img in SD card. Now I have a phone only with magisk manager.

Apply patch to boot.img using Magisk Manager. magisk_patched.img is put in Download directory in the phone, so copy to my pc.

"adb devices" to confirm adb works, and enter flash mode with "adb reboot bootloader"

"fastboot flash boot magisk_patched.img"....this should work to root.

"fastboot reboot"

I got boot loop... :angel:

Somehow patched boot.img is much smaller than original boot.img. I checked these files, and found something.

Investigate boot.img

$ file boot.img
boot.img: Android bootimg, kernel (0x8000), ramdisk (0x1000000), page size: 4096, cmdline (androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000 )

Then, patched boot image (magisk_patched.img)

$ file magisk_patched.img
magisk_patched.img: Android bootimg, kernel (0x8000), ramdisk (0x1000000), page size: 4096, cmdline (androidboot.hardware=qcom androidboot.console=ttyMSM0 video=vfb:640x400,bpp=32,memsize=3072000 )

Console has changed. And their sizes are

$ ls -l boot.img magisk_patched.img
-rw-rw-r-- 1 tetsuji tetsuji 67108864 Jan 1 2009 boot.img
-rw------- 1 tetsuji tetsuji 25374720 Aug 10 06:01 magisk_patched.img

Patched image is less than half of the original!!

Anyway, it failed......I'll try again. Now take a nap!! I'm sleepy. That may be the reason for the failure.

Cheers!!
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
Do you know if it patched magisk 18.1 in it or the newer ones which make bootloops?

Is there maybe a canary magisk manager version which patches a canary magisk in your boot.img?

Magisk 19.4 will have a fix for Sony xperias to avoid the bootloop.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
[/COLOR]

AHHHHH I'm using the one MagiskManager downloads. I guess it's version 19.3. Then, where can I download 19.4?

Now I'm trying to not only advanced wipe data, internal storage, dalvik, but also format them.

regards,

-Tetsuji

EDIT: The reason to format data areas is on my Linux, encryption is decided when formatting a partition.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] moyu4096:
You search Magisk on XDA and there is a thread [DEV] Magisk Canary Channel - Bleeding Edge Builds

---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------

It is normal to have a patched img which is smaller than the original img.

At least mine is ok to flash.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] L1e":
Hello sir，I am a new user of XDA.Just saw a GFAN user: iovf, Released TWRP for XZ2 52.0.A.8.107, according to what he said can be forced to unlock the DATA partition also contains Magisk 19.3 and selinux patch, although I do not know if this can help you
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
Hello sir :)

Thanks, I know him, but that doesn't help

He just bundled my twrp, with magisk, the bootimage and selinux permissive (security killer).

Just wait for magisk 19.4 and you're fine :)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Thank you for the heads-up! I'm now trying Magisk Canary. It looks like version 19.4.

EDIT: Sorry. It downloads magisk v19.4, and the manager is version 7.3.3. The manager looks buggy. Although Magisk isn't installed, it says "Magisk is up to date Installed: (-1)"
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] L1e":
Ok,Thanks sir I am using Magisk Canary 19.4, but I can't edit the root directory (for example I want to delete the folder under System / app or the file RE file manager will prompt the deletion to fail)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
I tried to modify kernel with magiskmanager-v7.3.2 (sorry, abandoned canary), and found it was not rooted.

Very complicated.....the results are different whether the patched boot.img is flashed with fastboot or it is flashed by twrp.

I'll try some more.

edit: I'll try magisk canary again!
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] Klaus N.:
It seems like dm-verity is active on your device. Please check this by tapping on Advanced Settings of Magisk Manager (is the checkbox of "Preserve AVB 2.0/dm-verity checked?). If dm-verity is active, this will help you ;)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
I thought the partition is just mounted as read only
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] shoey63:
And I thought Tama dm-verity resides in vbmeta, which Magisk doesn't touch.

Converted boot.sin patched by Magisk canary and fastbooted worked flawless for me on 131 update btw.

No problems writing to /system or /vendor.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Finally root it!!

Using TWRP and magisk-canary, modifying kernel, I finally rooted my H8266!!

Procedure was relatively simple.

After flashing the firmware, boot the phone, without wifi or any settings. But put the package in 2019-08-08_10-17-29_twrp_stock_xz2_52.0.A.8.131.tar.gz in SD card of your phone. But you won't use all. As a matter of course, enable developer option and debugging option. Connect your phone to pc, launch "adb reboot bootloader" and "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", then launch twrp as "fastboot boot twrp.img". But here, you just advance wipe data, internal storage, dalvik.

And backup boot partition in TWRP and put it in SD card. The file name is boot.emmc.win, so rename or copy it to something like boot-orig.img.

Reboot your phone and login with your google account, install MagiskManager canary version (you can download in this link. I downloaded from the top link in this page.

Open MagiskManager and hit Magisk "Install" and hit "patch...blah blah", choose your original boot image (in my case boot-orig.img), then Magisk is downloaded and patch it to root your phone. The patched file is stored in /storage/emulated/0/Download/magisk_patched.img. You can leave it there or copy it somewhere.

Now put patched boot image into the boot partition.

Then boot twrp like I mentioned above, install the patched boot image and permissive.zip in 2019-08-08_10-17-29_twrp_stock_xz2_52.0.A.8.131.tar.gz. Installing permissive.zip gave me warnings, but it seems to work.

That's all.

Now I rooted my h8266. Then, what shall I do with twrp.....?

Rooted images;

[IMG="rootchecker"]https://i.ibb.co/D4fhy2g/root-checker-h8266.jpg[/IMG]

[IMG="MagiskManager"]https://i.ibb.co/sKSx55R/magiskmanager.jpg[/IMG]

After these mess, I found xperia series were very nice and foolproof. Thank TWRP team. Please polish it. When I backup all of my apps/settings, I will challenge twrp recovery.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
Nice that it works now

For .131 twrp we need to wait for the twrp team to adapt the august security updates.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] dhacke:
Let's hope they will be fast:)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Oh, nice to hear that!!

But I'm afraid Sony might release a new update before that! :D

In that case, I may stay at .131.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] turnout96:
Hello sir，iovf just released the TWRP for XZ2 52.0.A.8.131, but I don't know if it works.:confused:
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
But....what the heck! If I install twrp.img in recovery ramdisk, my phone tries to boot to twrp and stops at twrp logo.....

EDIT: This was fixed by reflashing the whole firmware and booting, entering twrp with adb and fastboot to put the patched kernel. It took just a moment, but twrp doesn't seem to like to sit in recovery partition. I'm wondering twrp is eligible for release....
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
Then you did flash twrp on your boot.

According to the instructions and to the TWRP standards a twrp needs to get started by "fastboot boot twrp.img" and installed by "Advanced -> Install Ramdisk -> Choose the same twrp.img again".

This doesn't replace your kernel and can't force you to recovery again.

Another issue maybe, that you lead your device bootlooping too often by damage your firmware, then the "/misc partition" gets a flag to restart into recovery.

The first post in the first page describes how to fix that.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
I build a new TWRP at the moment.

Either they released an update or I did reset something in the source code on my computer, but the twrp decrypts now my phone.

But I reset the source code before every build and sync it with the official sources, so I assume the released a fix today.

We'll see it today.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
I'm just wondering. Speaking of encrypting a partition on linux, cryptsetup command is used. It is often called "luks encryption." It's used just after a partition is created on a disk(s), and before formatting. It requires a key; either typing a password or specifying a key file is ok. But in android encryption, it sounds quite different. How is a partition encrypted in android? Actually advanced wiping disables encryption. On linux, it's incredible. What is "advanced wipe"?

Just a thought.....because I like both Linux and android, and I'm relatively new to android.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
It's different here

The one I know are FBE and FDE

And they can contain encryption footer

And somewehere in the past there was an own partition for the encryption key.

On tama, if you want a full wipe, you need to wipe /data and the internal storage, or the internal storage is left encrypted with a now vanished encryption key in the footer (last 16k kb or bytes) of the data partition.

And

FDE = Full Disk Encryption

FBE = File Based Encryption
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Then, if you look at the last 16kb or so, you can decrypt the storage. But I wonder in android world, data and internal storage are different. In Linux, data is data, whether it's internal or external. So I often wonder the nomenclature of android. For example, "download" means transferring data into a phone. At first (2 years ago) I saw "download" in the flashtool log on the computer and thought the computer was downloading data from my phone!

As for encryption, linux encryption is very flexible. Of course full disk encryption is possible, and multi-volume encryption (make a partition over multiple hdd/ssd's) is possible. My computers also use encryption, so upon boot, I need to enter password. Once the main disk is decrypted with my password, it contains a 4kb other drives' key file and cryptsetup automatically decrypts the other drives using that key. If computers are down, nobody knows the contents of disks. So encryption/decryption is up to kernel. Now the latest stable kernel is 5.2.7, but I'm using 5.3-rc3 which is vigorously developed by Linus Torvalds and his group (it's really fast. A new version is released every 4 or 5 days.) android seems to use kernel 4.x. Anyway linux is interesting.

So I thought android also used that, but as far as I read your messages, it looks like not true.

Thank you for the fun!!

Cheers!
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
10.08.2019
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
It's earlier than twrp for xz1, isn't it?
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
I don't know, I don't maintain the xz1 twrp :)

But as far as I know the tama xperias are the first with the google rollback protection requiring monthly twrp releases :)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
I see.. Every one has his/her own wheelhouse.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
And mousewheel. :silly:
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
oh, your running machine is a mousewheel!! ;)
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] Pandemic:
This one works without issues bro [MENTION=6031898]MartinX3[/MENTION] also on fw 131 :D ?
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] sve1313:
I can confirm that TWRP is working fine now.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Belated nice job!! :good::good:

Now I restored patched kernel. And installed new twrp. The patched kernel lasted only one day :p

But I needed the latest magisk.....so called magisk canary. Version is 19.4. Its manager can be downloaded from the 1st link of this thread. magisk-release.zip is also in the 4th link, but I used Magisk-v19.4-736729f5(19307).zip downloaded by magisk canary manager v19.4 on xperia.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] Hồ Ly Tiên Sinh:
Help Me

i can't flash my xz2 with firmware 52.0. A.8.84 . Flashtool show error "No flash script found. Flash script is mandatory". In .flashtool/devices/H82XX only has 51.1.fsc, nothing in .flashtool/mydevice. Help me please
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] dhacke:
Simple answer:

Use Newflasher.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] apaxtc:
10/048/2019 23:48:13 - INFO - Selected Bundle for Sony Xperia XZ2(H8216). FW release : 52.0.A.8.107. Customization : Orange MCV FR/ES/PL/SK/RO

10/048/2019 23:48:13 - INFO - Preparing files for flashing

10/049/2019 23:49:27 - INFO - Please connect your device into flashmode.

10/049/2019 23:49:58 - INFO - Using Gordon gate drivers version 3.1.0.0 R/W

10/052/2019 23:52:47 - INFO - Write-TA status : OKAY

10/052/2019 23:52:47 - INFO - Writing TA unit 000009A9 to partition 2

10/052/2019 23:52:47 - INFO - download:00000001

10/052/2019 23:52:47 - INFO - download status : OKAY

10/052/2019 23:52:47 - INFO - Write-TA:2:2473

10/052/2019 23:52:47 - INFO - Write-TA status : OKAY

10/052/2019 23:52:47 - INFO - Writing TA unit 000009B6 to partition 2

10/052/2019 23:52:47 - INFO - download:00000000

10/052/2019 23:52:47 - INFO - download status : OKAY

10/052/2019 23:52:47 - INFO - Write-TA:2:2486

10/052/2019 23:52:47 - INFO - Write-TA status : OKAY

10/052/2019 23:52:47 - WARN - TA Unit 2553 is excluded from bundle

10/052/2019 23:52:47 - INFO - processing elabel.sin

10/052/2019 23:52:48 - INFO - signature:0000055B

10/052/2019 23:52:48 - INFO - signature status : OKAY

10/052/2019 23:52:48 - INFO - erase:LTALabel

10/052/2019 23:52:48 - INFO - erase status : OKAY

10/052/2019 23:52:48 - INFO - sending LTALabel.000

10/052/2019 23:52:48 - INFO - download:01000000

10/052/2019 23:52:49 - INFO - download status : OKAY

10/052/2019 23:52:49 - INFO - flash:LTALabel

10/052/2019 23:52:49 - INFO - flash status : OKAY

10/052/2019 23:52:49 - INFO - Sending set_active:a

10/052/2019 23:52:49 - INFO - set_active status : OKAY

10/052/2019 23:52:49 - INFO - Writing TA unit 00002725 to partition 2

10/052/2019 23:52:49 - INFO - download:00000014

10/052/2019 23:52:49 - INFO - download status : OKAY

10/052/2019 23:52:49 - INFO - Write-TA:2:10021

10/052/2019 23:52:49 - INFO - Write-TA status : OKAY

10/052/2019 23:52:49 - INFO - Writing TA unit 00002774 to partition 2

10/052/2019 23:52:49 - INFO - download:00000001

10/052/2019 23:52:49 - INFO - download status : OKAY

10/052/2019 23:52:49 - INFO - Write-TA:2:10100

10/052/2019 23:52:49 - INFO - Write-TA status : OKAY

10/052/2019 23:52:49 - INFO - Sending Sync

10/053/2019 23:53:49 - INFO - Sync status : OKAY

10/053/2019 23:53:49 - INFO - Sending powerdown

10/053/2019 23:53:49 - INFO - powerdown status : OKAY

10/053/2019 23:53:53 - INFO - Device disconnected

10/053/2019 23:53:54 - INFO - Device connected in flash mode

-----------------------------today I flashed .107 stock rom with flastools (Flashtool Version 0.9.25.0) 64bit using windows 7 64bit
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
I recommend Xperifirm (rom download) and newflasher (flash tool)

And the newest firmware ends with .131.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] Hồ Ly Tiên Sinh:
i failed from this step, please help me

c:\adb>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]

Writing 'vbmeta_a' FAILED (remote: 'Command not authenticated')

fastboot: error: Command failed
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] Klaus N.:
Yes, I can confirm that it works flawlessly. Updated 2 hrs ago...
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
try

c:\adb>fastboot --version

if the output is 27 or lower, please upgrade your google plattform tools.

Your installed ones seem to not support A/B devices.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
I rooted H8266 some days ago as I wrote in this thread, but today I got bootloop suddenly, and couldn't enter system. Does this mean root wasn't good enough?

So I had to install firmware and get root again,. But during this process, when I rebooted after flashing twrp.img in recovery (I mean "Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img" part) and install Magisk-19.3(xxx).zip and tried to reboot system, somehow I entered twrp instead of system. I powered off and started, but entered system. If I entered recovery by "adb reboot bootloader" and "fastboot boot twrp.img" and in twrp, reboot into recovery, somehow I reached "real" recovery mode....I mean, several selection are listed "wipe user data" "reboot" "power off" blah, blah.... Is it normal?

So I finally decided to wipe userdata and power off, and install firmware.....I mean I started from scratch. This time, after installing twrp.img in recovery ramdisk, rebooting into recovery (twrp), installing Magisk.zip, trying to boot into system, I got twrp once, but after another trial, I booted system, rooted......by writing this, I found it sounds very complicated, but I just want to say after installing twrp.img in recovery, trying to boot into system brought me to twrp once. Next time reboot into system succeeds. Why?

To tell the truth, when a few days ago I rooted Chinese cubot x15 I had bought cheaply, after instsalling Magisk.zip, I somehow entered recovery once instead of system. Next time I could enter system and I could get root. Why does it happen?
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] apaxtc:
I know what the root advantages of magisk , but if you are still experimenting after installing twrp try to flash with supersu :cyclops: does he work ???
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
18.1 is good, 19.4 well be good

Don't use magisk versions between please
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
oh. sure.

EDIT: just a moment....I use magisk 19.4-736729f5 on xz2 and got this problem. I used it again....
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
If it was to newest magisk and nothing else please report a bug report to the magisk developer

(Dmesg & logcat)

https://github.com/topjohnwu/Magisk/issues

He explains in his magisk thread how to report a bug report.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Thanks, but I am afraid I lost old dmesg and logcat....check and if I found it, I'll report. And I'm afraid it'll happen again. Then I'll report it. Thanks.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
Trying several root check apps, I found Safetynet failed error with Root Checker 3.2 by App Hippie. How can I fix it? I tried several safetynet cleaning tools, but haven't fixed so far. An app "SafetyNet Test" says SafetyNet Status "Passed."

[IMG="Failed status"]https://i.ibb.co/tDFfydL/h8266-failed-safetynet.png[/IMG]
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] MartinX3:
If you on one of my custom roms.

Use the magiskapp to check the status.

One of both tests will succeed.

For the other one there is a magisk module with a similiar name like the name of the failed safetynet part.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] maverick6664:
ok. Then I don't mind it.
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] holychelsea:
I'm get message "E:Error getting bootctrl module." when "install recovery ram disk". TWRP installed on my phone but i can't flash any zip file ( show success but no app installed on phone). and my camera show black screen in photo mode and hdr video mode.

My error:

https:// imgur.co m/a/QD5qz9w

(I can't post link because i'm new member)

Please help me. Thanks
[Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other] voilsb:
I finally unlocked my bootloader and, using xperifirm and newflasher, flashed my xz2c to the UK Customized 8.131 firmware. I booted and set it up, and played a little on wifi and mobile data, before following your instructions to `adb reboot bootloader` to get into fastboot, and followed your TWRP install instructions. I got the bootctrl error that started after the Aug security release, so I skipped it and went to install your OmniROM port. I'll play with it more during the week, and I'll do what I can to provide you with whatever information you need.