Database Develop

[ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off

Changelog:
V5.23 Fix for Android 6 (Freeze on boot logo)
Installation of kcal kernel module for supported kernels. Get the app from https://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
V5.22 Bug in the vendor overlay creation. Existing directories (like /vendor/bin) have not been replicated correctly
V5.21 Fix issue when running on Linux (some CR/LF)
Patch libsepol in bootimg for backwards compatibility with Android 6
V5.20 Support for superuser as an alternative to SuperSU (https://github.com/phhusson/Superuser)
Fix for the missing internal storage link in TWRP
V5.11 Support for Android 7.0
Fix in the overlay layout which could prevent some libraries from loading and cause battery drain
V5.1 Support for Android 7.0
Updated bootimg to deal with Android 7.0 policies
New tool inside bootimg for adding new contexts to binary file contexts
New system overlay layout due to a more restrictive linker in Android 7
V5.0 New system overlay method using the /vendor directory. As this directory is also in the library search path even libraries can be easily replaced without modifying the system partition
System-less SuperSU integration improved (Version 2.76 or higher recommended)
System-less xposed integration (using the standard distribution)
Support for 32.A.0.253
V4.51 Fix for awk script for Linux kernel version detection when running on Linux
V4.5 Fixed adb and mtp file access in TWRP for 32.2.A.0.224
V4.42 Added support for Z2 (Sirius) and TWRP fstab fix for leo and aries (thanks to waleedsq81)
V4.41 Fixed issue with Y/N choice on non-english Windows. Added support for Z3 (leo)
V4.4 Support for Z3+/Z4, Tablet Z2, Tablet Z3 and Tablet Z4 added (Z4 still has an issue with TWRP, but DRM fix works)
SuperSU integration reworked in order to need less SELinux exceptions and to be more secure
All tasks can now be individually selected. Therefore there is no separate DRM only script required
V4.31 Renabled Z5P (satsuki) and Z5C (suzuran) for TWRP and drmfix
V4.3 Support for older Lollipop added
Script execution for Linux fixed
V4.24 Fix for for a bug in SuperSU integration in V4.23
V4.23 Fix for repacking 3rd party kernel (Some permissions were on custom directories were lost)
V4.22 Bugfix for readta (flash_dk reported unit not)
V4.21 Fix for the Linux binary of bootimg
V4.2 Updated TWRP to 3.0.2
V4.1
Fix for WideWine (if you have your device key) Thanks a lot to goofnorf101 for testing
unpackinitfs and makeinitfs in my bootimg tool now maintain date/time of files correctly
Automatic SuperSU installation
V4.0
Fix for older kernels (Lollipop)
Binary for Linux (The older version had the ARM version packaged)
Device is not stored in the kernel image anymore
TWRP updated to version 3.0.1
FAQ - Please read
Is is possible to have root with locked bootloader?
Short answer: no
Long answer: The locked bootloader only boots unmodified kernel packages signed by Sony. The stock kernel only mounts unmodified /system partitions (dm-veritiy) -> No modification without unlocking
So any change to the kernel (like this script) or system partition requires unlocked bootloader
What is dm-verity?
A hash checksum on all blocks of a filesystem in order to verify the integrity
What is Sony RIC?
A protection to avoid mounting the root filesystem or system read/write
What happens if I unlock my bootloader
The device key (TA unit 0x1046b) will be wiped, which deactives everything DRM related. In addition a full wipe of your phone will be perfomed.
So extract your TA partition before with this great tool http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597 from zxz0O0
If you already unlocked the bootloader before, then at least the credentials will be restored, which will reactivate stuff like x-reality and camera de-noise
Why do I need to flash my device key?
Without your device only some functions can be reactivated, like x-reality. Other functions like widevine do not work with out your device key.
How do I enter TWRP recovery?
Restart your phone and press the volume key up as soon as the LED switches to yellow
I want to use a custom kernel with the DRM fix
Just say "N" to all other options. Nevertheless be prepared for problems if the custom kernel does not match your Android version.
What should I do if there is an update to this script?
First check if you really need to run this update by checking the changelog. E.g. if it says binary for Linux fixed and you are using Windows then probably you don't care. If you did not change your Android version then all you have to do is to update the kernel package with fastboot flash boot. If you do not use the automatic SuperSU integration then you have to reinstall SuperSU in TWRP.
This tool repacks an existing kernel package (usually the stock kernel) in order to make it rootable and adds TWRP recovery as well. Version 4 has been succesfully tested with LP and MM.
In particular it adresses the following issues:
DM-Verity: Android is now using dm-verity to verfy the integrity of the system partition. Until you switch it off your phone won't boot after modifying /system
SONY RIC: RIC is blocking the write access to the system partition
DRM Keys: After unlocking the bootloader your device key is wiped, which deactivates some functionaliy. E.g. x-reality, denoise in camera aso.
Recompiling the kernel is not required as only the init ramdisk needs to be modified. You can run these scripts either in Windows or Linux.
Thanks to the excellent work of zxz0O0 you can now backup the TA partition before unlocking the bootloader with this tool http://forum.xda-developers.com/crossdevice-dev/sony/iovyroot-temp-root-tool-t3349597
If you managed to backup your TA partition before you unlocked the bootloader then this version will fully reactivate your keys as well. (many thanks to addicted1900 for helping me with the testing)
As there has been some confusion I would like to point out one more time that you cannot run any kernel package which is not signed by Sony without unlocking the bootloader. So this works only with unlocked bootloader.
As it seems that it is not clear to everyone I also want to mention that <...> is a placeholder. E.g. <extracted kernel> means that you should replace it with then name of your extracted kernel, which could be kernel.elf
There was a report that having SuperSU in the system partition installed may lead to a bootloop. Therfore you shoud first install the bootimage created by this script and then install SuperSU afterwards, as it will then use the system-less strategy.
In order to use these scripts you need the kernel boot image of your current version. There two different ways to obtain it:
Method1:
If you have a .ftf image then open it with zip application (7Zip, WinZip, Windows Compressed Folder) and extract kernel.sin. Afterwards use Flashtool -> Tools -> SIN Editor to extract the kernel. You should end up with the boot image with extension .elf.
Method2:
Run your favourite recovery and connect via
Code:
adb -d shell
Now run
Code:
find /dev -name boot
dd if=<output of the find command before> of=/sdcard/kernel.img
Once you have the kernel image you are ready to use the script.
The newest version support superuser as an alternative to SuperSU. This is available open source and can be verified. In order to integrated you need the current superuser.zip from http://superuser.phh.me/superuser.zip and to be install the app afterwards from Google Play (look for superuser phh) or build it yourself from github.
To integrate the kernel part just place superuser.zip in the rootkernel directory.
You can also still use SuperSU, although it is causing a huge battery draining on my Z5 with Android 7.0 If you place SuperSU in the same directory (SuperSU*.zip, case sensitive) then it will be also installed automatically . It did all the tests with 2.76, but newer versions should work as well. Please be aware that you can not update SuperSU within the application. For a newer SuperSU version you need to rerun the script.
If you want to integrate xposed as well just place the distribution for you device and Android version in the same directory. (e.g. xposed-v86-sdk23-arm64.zip). Only support with Android 6.0 (sdk 23) and higher.
xPosed for Android 7.0+ is still not available.
Code:
rootkernel <extracted kernel> boot.img
You are prompted for several choices:
Sony RIC is enabled. Disable?
I prefer not to disable it in order to keep my phone more secure. Unfortunately there are a lot of bad guys in this world and SELinux and RIC still can save us if someone discovers a new kernel exploit.
Sony RIC basically prevents mounting the /system partition for write. You can still modify it in recovery of of course, but if you require write access to /system without entering recovery then you need to disable it.
Install TWRP recovery? Here you should say yes unless you are trying to patch a non-stock kernel, which comes already with a recovery
Install busybox? For security reasons I prefer not to install. In recovery you have it anyway. This choice is only available if you chose install TWRP
Found SuperSU-v....zip. Install? Integrates SuperSU. For this option to show up you have to place the SuperSU package into the same directory with the name SuperSU*.zip (case sensitive)
Found superuser.zip. Install? Integrates superuser. For this option to show up you have to place superuser.zip into the same directory (case sensitive)
# Make su permissive (Permits any action as su)? This only appears if you install superuser. Permissive means you can anything as root, without it is restricted mainly to file operations (sufficient for e.g. Titanium Backup)
Found xposed-v....zip. Install? Integrates xposed system-less. For this option to show up you have to place the xposed for your device and Android version into the same directory. (e.g. xposed-v86-sdk23-arm64.zip)
Install DRM fix? Installs the DRM fix. First it tries to use the device key which you flashed with flash_dk. If it does not exist it uses an alternative method which cannot fix everything (e.g. Widevine will not work, but X-reality, Camera denoise etc. will work)
Now put your phone into fastboot mode (Volume Up + connect USB) and then run:
To test it without actually flashing it:
Code:
fastboot boot boot.img
For flashing it:
Code:
fastboot flash boot boot.img
If you managed to backup for TA partition before then you can reactivate your original device key as follows:
Code:
flash_dk <ta backup image> DK.ftf
Flashing this file with flashtool will write your device key to an alternative unit, from where the drmfix library will pick it up.
This is a one-time task. It will survive a complete reset of the phone or Android system upgrade. The device key has a length of just 16 bytes, so it is correct that the resulting DK.ftf has a size of only aprox. 500 bytes.
If you like my work you can buy me a coffee
Some background information:
There are two main tools involved (for both Android and Windows)
- busybox
Probably everyone knows it
- bootimg
A multicall binary with several tools for unpacking and packing the boot image as well as adapting the SELinux policy. Part of the code is written by me from scratch, some other parts are cherry picked from other projects. I will also provide the source for it. As Windows doesn't have softlinks I modified the tools for unpacking and packing the init ramdisk to write text files with __lnk__ at the end instead.

Would be great if someone shared E6653 stock .200 kernel boot.img or flashable zip so we can try this out

Funkmasterchilla said:
Would be great if someone shared E6653 stock .200 kernel boot.img or flashable zip so we can try this out
Click to expand...
Click to collapse
Do you want the kernel.sin of stock . 200?

lordriguez said:
Do you want the kernel.sin of stock . 200?
Click to expand...
Click to collapse
I am downloading the whole firmware again from xperifirm. Thank you mate !
Edit: Working great! I'll stick to stock kernel now since Androplus' consumes more battery while asleep !
Edit2: I successfully flashed recoveries in command window from my PC but can't access TWRP at boot though, no LED flashing.
Edit3: Ok that's cuz there's no recovery boot script obviously, my bad. That's above my pay grade, if somebody is kind enough to create a stock. 200 with recoveries it'd be much appreciated PM me if so
Edit!: I flashed monx new stock based kernel
Thank you Tobias !

tobias.waldvogel said:
Hi everyone,
as most of you know, even after unlocking the bootloader there are a few more requirements before you can modify the system partition, i.e. install SuperSU, xposed etc.
- Android is now using dm-verity to verfy the integrity of the system partition. Until you switch it off your phone won't boot after modifying /system
- SONY RIC is blocking the write access to the system partition
The good news is, that it is not required to recompile the kernel. It is sufficent to modify the init scripts inside the init ram disk. So you can just stick to the stock kernel.
I created a package which precisely does this job for you. Just run it from TRWP after installing a new Android version
With this you don't have to wait anymore until someone creates the right kernel package for your phone
PS: It leaves a copy of the new boot image in the internal sdcard if you want to save it somewhere. (boot.img) It can be flashed with fastboot if required.
Click to expand...
Click to collapse
Hmm... I don't understand what this zip file do with phone.... Can you explain more primitive for me?!
Is that for recover stock kernel with stock drm keys?! I understand correct?!

zavpasha said:
Hmm... I don't understand what this zip file do with phone.... Can you explain more primitive for me?!
Is that for recover stock kernel with stock drm keys?! I understand correct?!
Click to expand...
Click to collapse
Before you can start to install thing like SuperSU and xposed you have to change the kernel, otherwise your phone won't boot anymore. In the past you had to wait for someone to come up with a compatible kernel for your phone, now this package just converts your existing kernel.
Regarding the DRM please install the package from the DRM restore thread.

Funkmasterchilla said:
I am downloading the whole firmware again from xperifirm. Thank you mate !
Edit: Working great! I'll stick to stock kernel now since Androplus' consumes more battery while asleep !
Edit2: I successfully flashed recoveries in command window from my PC but can't access TWRP at boot though, no LED flashing.
Edit3: Ok that's cuz there's no recovery boot script obviously, my bad. That's above my pay grade, if somebody is kind enough to create a stock. 200 with recoveries it'd be much appreciated PM me if so
Edit!: I flashed monx new stock based kernel
Thank you Tobias !
Click to expand...
Click to collapse
Thanks for the feedback. Future versions of this package will add TRWP as well. I am currently working on it.

tobias.waldvogel said:
Thanks for the feedback. Future versions of this package will add TRWP as well. I am currently working on it.
Click to expand...
Click to collapse
As promised the new package with TWRP is out

tobias.waldvogel said:
As promised the new package with TWRP is out
Click to expand...
Click to collapse
Great work thanks ,
How would I go about disabling the vibration for recovery?
Sent from my E6653 using Tapatalk

Well, the script which checks if recovery should be started is bin/init inside the zip. If you don't like the vibrate then just remove the line and run the package again
Gesendet von meinem E6683 mit Tapatalk

huh, so it is possible to have 2 recoveries at the same time? (and why would anyone want 2 recoveries? )

Three Recoveries are als possible
CWM, Phils Touch & TWRP
Sent from my E6653 @ XDA Portal

Sorry for being noob.
I miss my Oneplus one where things were so easy.
After unlocking BL what do i do with this zip.
Is it going to Root my phone and Install TWRP?
Thanks for help.

I flash the v2 and i got bootloop. 4 time red LED and the phone reboot and all over again. What's the problem?

Hi Tobias,
can you please build a v2 for the z5 compact too?
thx
stiffmeister

FakeSmile said:
I flash the v2 and i got bootloop. 4 time red LED and the phone reboot and all over again. What's the problem?
Click to expand...
Click to collapse
On which model did you use it and with which firmware version?
If you used flashtool before then you can just flash the kernel one more time (i.e. deselect everything else).

stiffmeister75 said:
Hi Tobias,
can you please build a v2 for the z5 compact too?
thx
stiffmeister
Click to expand...
Click to collapse
This should work on Z5 compact with stock kernel as well, without any change.
In case of any issues you can flash the kernel again via flashtool
If it did not work you can pass me the generated boot.img from your interal sdcard for further analysis

hi tobias,
i didn't try the v2, because i thought, that the twrp recovery wouldn't be compatible.
but when you say it's ok, than i'll try it
br
stiffmeister

stiffmeister75 said:
hi tobias,
i didn't try the v2, because i thought, that the twrp recovery wouldn't be compatible.
but when you say it's ok, than i'll try it
br
stiffmeister
Click to expand...
Click to collapse
I flashed zombie kernel without making backup of stock kernel, can you share it with me so I can try this method (I doubt it will work on zombie)
ps : I have .200 fw

tobias.waldvogel said:
On which model did you use it and with which firmware version?
If you used flashtool before then you can just flash the kernel one more time (i.e. deselect everything else).
Click to expand...
Click to collapse
E6653 on .200 firmware

[Root][Stock][P2a42_S244][Fastboot]

You can flash this boot.img with fastboot on the latest stock ROM (S244) with an unlocked bootloader (no custom recovery needed).
The included Magisk is v13.6 (beta) and the Manager is v5.2.0.
From what I gather the modules won't install (or using something like Flashify won't work) because there are still f2fs bugs present (not only on this device, most android kernels have them). But I didn't fully test this so YMMV.
I did it this way because I only need root for some apps (like: Amaze, Termux, Wirebug, WiFiKeyShare, KISS launcher, ...) and didn't want to change too much after unlocking.
Don't ask about passing the SafetyNet check. I don't use Google Play Services so really can't answer this.
You can also do this yourself by following the instructions in the main Magisk thread. But I uploaded it as it's maybe of any use to somebody else that only needs a fast/simple (systemless) root solution.
DL-link:
https://www.androidfilehost.com/?fid=817550096634797229
Instructions:
Rename the downloaded image to boot.img and run the following commands from the same folder.
$ adb reboot bootloader
$ fastboot flash boot boot.img
$ fastboot reboot

Flash kernel to disable the selinux on EMUI9.0

If selinux is useless for you or you don't konw what is selinux, maybe you don't have to read the thread.
This is a kernel but I don't have have enough permissions to send it to the kernel section.
This kernel allows users to use "setenforce 0" or "setenforce 1" to change the status of selinux.
======FBI Warning======
It was only tested on my phone...
The phone is COR-AL10 and the system is offcial AEX of View 10.
I don't know whether it could work on L29 or official EMUI9.0.
I know it will not work on EMUI8 or other 8 systems.
I don't konw whether it could cause hardware damage to your phone.
=====================
Introducions:
1. Maybe we can backup the kernel first.
I used the mt manager 2.0 (free editon) to copy the /dev/block/by-name/kernel_a to somewhere interesting.
Then we reboot the phone and hold the vol- to enter the bootloader mode.
2. We can use this command to flash the kernel.
Code:
fastboot flash kernel xxx.img
3. We can use this command to reboot.
Code:
fastboot reboot
4. If there are any problems after flashing this kernel, you could flash the official kernel or your backup kernel.
ps. Flashing kernel could not cause losing data. But I suggest you do a backup.
pps. Why we flash the kernel to change the selinux status? Because the official kernel don't allow user use the command "setenforce" to change the status. It means that the status must be "enforcing".
Kernels & Imageslanzouyun...)
https://www.lanzous.com/i553l4d
Good luck and enjoy the kernel.

Maybe I have a new version
and I will upload it

Here is my new post and new version of kernel.
https://forum.xda-developers.com/ho...el-kernel-emui9-0-roms-based-emui9-0-t3972873

[KERNEL][Dispossible]A kernel for EMUI8.2 or ROMs based on EMUI8.2

I just made few changes on the official open source kernel of 8.
Some features:
This kernel is based on the official open source kernel.
This kernel allows users to use "setenforce 0" or "setenforce 1" to change the status of selinux.
======FBI Warning======
It was only tested on my phone...
The phone is COR-AL10 and the system is offcial EMUI8.2 151.
I know it will not work on EMUI9 or other 9 systems.
I don't konw whether it could cause hardware damage to your phone.
=====================
Introducions:
1. Maybe we can backup the kernel first.(If you are brave, you can skip this step.)
I used the mt manager 2.0 (free editon) to copy the /dev/block/by-name/kernel_a to somewhere interesting.
Then we reboot the phone and hold the vol- to enter the bootloader mode.
2. We can use this command to flash the kernel.
Code:
fastboot flash kernel xxx.img
3. We can use this command to reboot.
Code:
fastboot reboot
4. If there are any problems after flashing this kernel, you could flash the official kernel or your backup kernel.
ps. Flashing kernel could not cause losing data. But I suggest you do a backup.
pps. Why we flash the kernel to change the selinux status? Because the official kernel don't allow user use the command "setenforce" to change the status. It means that the status must be "enforcing". Now you can use the command "setenforce 0" to make the SELinux interesting.
Source code:
https://github.com/kindle4jerry/honor-play-kernel-8.1-kindle4jerry
Download: maybe you can download it from my github
https://github.com/kindle4jerry/honor-play-kernel-8.1-kindle4jerry/releases/tag/0.2

[ROM][UNOFFICIAL][12][S]LineageOS 19.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 19.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-11
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
New: Camera fully working! (with the restriction to 8 MP)
Enforced SELinux support
Fingerprint (sometimes crashes)
FM-Radio (maybe it needs a few restarts before it's working)
GApps
German App AusweisApp2
GPS
Headset
LiveDisplay
Location services
Network Traffic Monitoring
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

Which GApps would you suggest?

I've tested NikGApps, but they are not working stable. Other GApps aren't available for Android 12 as far as I know. So, I suggest none.

Update: NikGApps works after its self-updated service bibliothek and a manual restart of the device flawlessly.
It's a little bit choppy, but I can live with that.

I've set the state of the development to BETA due to quite good overall performance.

After installing this TWRP was changed to the one from Lineage. It no longer picks up my mounts. Must I use ADB to recover from this? How do I revert to TWRP? I can no longer use fastboot.

I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:

Berni-0815 said:
I can't believe that fastboot is no longer working.
Please take a look at my 1st post:
Important informations:
Required for installation:
Click to expand...
Click to collapse
Thanks. I got fastboot working and installed TWRP again. How did the Lineage loader install though? I did not see any prompts for it.

I performed a cache/dalvik/system and data wipe and installed the latest 19.1 release but it never boots up past the swirling animation. It does not reboot either. I added a zip containing pmsg-ramoops-0

I'll take a look into it asap. Please be patient.

I can't find any reason for the crash; I'm sorry.

New version out; see 1st post.
New values for vibration strengths set.
Fixed Fingerprint location hint animation while enrolling.
Screen density reduced because all of the UI elements of Android 12L (Lineage 19.1) are too large for our little screen.

New version out; see 1st post.
Updated from android-12.1.0_r1 to android-12.1.0_r2

Berni-0815 said:
I'll take a look into it asap. Please be patient.
Click to expand...
Click to collapse
Thanks for looking. I flashed with the currently build and my device is working again.

New version out; see 1st post.
Updated from android-12.1.0_r2 to android-12.1.0_r4
Android security patch level: 5 April 2022

Hey friends,
New z5c, had sony stock on it.
I installed TWRP latest using adb/fastboot on ubuntu 20.04
All good
I flashed Lineage 19
On reboot I just get a boot loop, going between Sony logo and swirly android animation
adb recgnises the device but says "offline"
No commands work
I have tried every button combo I could find suggested everywhere, including above
But the phone will not boot into TWRP
Any suggestions, please?

kaivalyam said:
z5c, had sony stock on it
Click to expand...
Click to collapse
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
kaivalyam said:
I installed TWRP latest using adb/fastboot on ubuntu 20.04
Click to expand...
Click to collapse
How have you flashed TWRP?

Berni-0815 said:
Which version? You have to come from the latest stock ROM (32.4.A.1.54)! Otherwise you can't flash LineageOS successfully!
Click to expand...
Click to collapse
Ok, that's probably why it wont boot then, I didnt know that, and didnt check

Berni-0815 said:
How have you flashed TWRP
Click to expand...
Click to collapse
Downloaded latest and used fastboot
fastboot flash recovery twrp.img
If I can just get TWRP to load, I can flash a different ROM and all will be good ..

Ok. Which version of TWRP have you flashed? My own?
You can flash the latest stock ROM with the flashtool. If you're installing this tool at windows, you can use the integrated XPeriFirm tool to download the latest stock ROM.
Or you install this XPeriFirm version.
If you're not in a hurry: In a few minutes my upload of my latest LineageOS 19.1 boot and system image will be completed.