Database Develop

[Q&A][ROM][6.0.1] CyanogenMod 13.0 for Xperia T, TX, V

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About this Q&A thread for CyanogenMod 13.0
Use this area to ask anything you want related to CM-13.0,
but try not to spam everyone, always search for an answer before.​
CyanogenMod 13.0 for Sony Xperia Blue
Xperia T (Mint) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3415827
Xperia TX (Hayabusa) : http://forum.xda-developers.com/xperia-t-v/orig-development/rom-t3418818
Xperia V (Tsubasa) : http://forum.xda-developers.com/xperia-t-v/v-development/rom-t3416938​
General Questions & Answers
Is root access included into CM ?
Yes. Go into Settings, About Phone. Tap "Build number" 7 times.
Go back, open Developer options. Change "Root access" option.
Do not use SuperSU unless you are sure, creates booting issues.
Read more about it : Here.​
Is the ROM suited for daily usage ? Google Apps compatible too ?
Yes completely. Nightlies and OpenGApps recommended.​
Can I flash CyanogenMod NIGHTLY and UNOFFICIAL without wipes ?
Yes you can.​
Should I flash SNAPSHOT builds when I'm on NIGHTLY ?
No, the Nightlies are already more up to date.
You can flash SNAPSHOT builds when you don't want to update often.​
Is the device encryption supported ?
State unknown. If you're coming from an older ROM
please read the details here : a07afb9660a86f702066003b8e81ab63789d1660​
When USB connected to a computer, I can't access the storage ?
The phone is in charge-only mode by default on Marshmallow,
due to a stronger security logic regarding unauthorized data access.
Swipe down the notifications and change the USB mode.​
I can't access the ROM's recovery with Volume-
You can either flash the boot.img from the newer Releases with "fastboot flash boot boot.img" or FlashTool,
or follow the instructions of the TWRP Recovery installation to update from TWRP.​
Due to an unknown issue in data, the partition still looks like a 2GB
Although very unlikely, it may be possible that your data had an error
that could not be fixed automatically by the time you did the UserData Unification.
Export the resize_userdata.zip from the CM-13 zip / install / unify_userdata,
and flash it from your recovery. If it works, problem solved.​
Against advices, I upgraded without GApps and now it crashes. Any way without factory reset ?
Yes there is, but nothing assures you'll manage to do it fully & preserve all your data...
Once booted, keep saying Ok to all "Unfortunately, ... has stopped",
pull-down the notifications panel, press the Settings icon,
go in Apps, menu, Show System, scroll to Setup Wizard (green Android logo),
Permissions, and activate Contacts + Telephone.
Later, some Play Store apps may need reinstalling.
If not ok, try this : CM Wiki
If still not, then I advise a clean factory-reset reinstallation...​

Current status of each device
Xperia T (Mint) : Fully working, stable, no known major issue remaining
Xperia TX (Hayabusa) : Fully working, stable, no known major issue remaining
Xperia V (Tsubasa) : Mostly working, RIL phone issues being worked upon

Just tried flashing cm-13.0-20160711-UNOFFICIAL-hayabusa.zip from basketbuild. Everything went fine, phone goes preparing applications, then it goes starting applications and it just waited the for a long time without proceeeding. Upon reboot phone is stuck on booting animation.
In previous builds from basketbuild:
* wifi/cell/gps/compass doesn't work;
* from the start sdcard wasn't available (fixed at 06 or 05);
* screen doesn't turn off and wasn't adjusting (until 08, now it turns off);
* when phone is off instead of charge level two text strings are displayed: "Charging", "??/100".
Apart from that everything went smoothly after updating from cm 12.1 - I haven't cleaned anything. Apps are working, youtube is playing video, ads are shown in games and I can install new apps. There was one reboot while GPlay was updating YouTube.
Ready for the new builds. If I have missed anything just name it.

How was the battery life in this rom.

too soon to comment for me.. just flashed it :laugh:

moly82 said:
too soon to comment for me.. just flashed it :laugh:
Click to expand...
Click to collapse
Will you leave comment later then...

Hayabusa released, details and links added.

Dn.Thanujaya91 said:
How was the battery life in this rom.
Click to expand...
Click to collapse
I can compare by going out for ingress. On previous build of 12.1 phone survived a hour and a quarter. Now it survives a hour and a half. This can be only my imagination though so I'll try to use it in the same pattern for a week or so.
On the other hand the phone overheats. This also may be my imagination as temperature here is near 38́°C (100°F) so everything overheats easily.

Hello, and that you for taking the time to tune your rom for this phone! One small question, is it possible to repartition the device to have only one single data partition, and build the rom accordingly(meaning emulated storage?) It is one big drawback on many sony devices of that time, and separate data and sdcard partitions.

anyone here have tried MultiROM for tsubasa? can you give me instruction for install or flashing it?

You can read about MultiROM inside my Huashan Xperia SP thread for it.
I'm not releasing it until it's finished, mostly touchscreen on Hayabusa & Mint being glitchy, so use hardware keys.

I accidently flashing SuperSU through TWRP, and now Im stuck in boot?
What should I do now? Clean Flash back the ROM?

EstherTakumi said:
I accidently flashing SuperSU through TWRP, and now Im stuck in boot?
What should I do now? Clean Flash back the ROM?
Click to expand...
Click to collapse
Just boot into recovery and flash the rom again. If you don't succeed, then wipe only system, and flash cm & gapps right after, and you should be fine ( your data will be untouched).

Klaus N. said:
Just boot into recovery and flash the rom again. If you don't succeed, then wipe only system, and flash cm & gapps right after, and you should be fine ( your data will be untouched).
Click to expand...
Click to collapse
Working great now! Thank

You suggested to move discussion about bricked phones due to WhiteNeos faulty TWRP image here in Q&A.
So it seems that I ran into this issue described here: http://forum.xda-developers.com/showpost.php?p=68100827&postcount=288
This should also explain why I am now unable to flash WhiteNeos Unofficial CM 12.1 builds (getting a missing crypto-footer issue) or a stock system image with Flashtool (just displays a FAILED message without further information even in debug log mode).
I was still able to flash all other .sin files in flashmode besides the failing system one though (amss_fsg, amss_fs_1, amss_fs_2, boot, cache, cust-reset.ta, fotakernel, kernel, partition and userdata).
Afterwards I rebooted into fastboot and flashed your TWRP 3.0.2 build as boot and it actually booted to it, however TWRP-3.0.2 was unable to mount most of the partitons, it succeded in flashing CM 13 after some playing around though.
It seems that some partitions or contents are still missing though as I am still unable to flash any other ROM besides your CM 13 version with the unified data partition.
My system is currently booting into CM 13 with the unified data partition but it's pretty useless for me as I'm getting constant black screen of deaths once the screen turns off for a few seconds.
Any suggestions, logs you want or maybe raw partition dumps I could try to flash?

I got a Xperia TX running Stock 4.3 (9.2.A.1.215) to install CM13 Only I need flash twrp-3.0.2-20160814-boot-hayabusa.img via flashtool or cmd and then the CM13.zip and OpenGapps? I've already unlocked the bootloader. I was using Windows Phone/Mobile for a year, So I'm quite lost.

DanielZRK said:
I got a Xperia TX running Stock 4.3 (9.2.A.1.215) to install CM13 Only I need flash twrp-3.0.2-20160814-boot-hayabusa.img via flashtool or cmd and then the CM13.zip and OpenGapps? I've already unlocked the bootloader. I was using Windows Phone/Mobile for a year, So I'm quite lost.
Click to expand...
Click to collapse
Yes, easiest way is to just flash the latest twrp img as boot (fastboot flash boot twrpimgfile),
then from there flash CM13, follow the instructions for the unification,
and finally flash CM13 and GApps, you're all set.

markus1540 said:
You suggested to move discussion about bricked phones due to WhiteNeos faulty TWRP image here in Q&A.
So it seems that I ran into this issue described here: http://forum.xda-developers.com/showpost.php?p=68100827&postcount=288
This should also explain why I am now unable to flash WhiteNeos Unofficial CM 12.1 builds (getting a missing crypto-footer issue) or a stock system image with Flashtool (just displays a FAILED message without further information even in debug log mode).
I was still able to flash all other .sin files in flashmode besides the failing system one though (amss_fsg, amss_fs_1, amss_fs_2, boot, cache, cust-reset.ta, fotakernel, kernel, partition and userdata).
Afterwards I rebooted into fastboot and flashed your TWRP 3.0.2 build as boot and it actually booted to it, however TWRP-3.0.2 was unable to mount most of the partitons, it succeded in flashing CM 13 after some playing around though.
It seems that some partitions or contents are still missing though as I am still unable to flash any other ROM besides your CM 13 version with the unified data partition.
My system is currently booting into CM 13 with the unified data partition but it's pretty useless for me as I'm getting constant black screen of deaths once the screen turns off for a few seconds.
Any suggestions, logs you want or maybe raw partition dumps I could try to flash?
Click to expand...
Click to collapse
When I flashed CM13 and CM14 I also had constant black screens and phone shut down randomly.
And because I wanted to prove to myself that these are not hardware faults I reverted to stock rom.
I flashed FTF image with Flashtool. I had to use older flashtool version as the latest couldn't finish the process and broke with errors.
Flashtool 0.9.18.6 did the job for me
Stock firmwares - http://forum.xda-developers.com/showthread.php?t=2648320
Initially it worked flawlessly but then, around 50% battery level, to my dissapointment random black screens of death happened again.
So it is either hardware fault, or something get messed while flashing the different ROM builds.

Hi there,
seems to me but 19 sept. update cm13 nightlies tree is not installing, crashing right after the recovery reports update started.
Anybody else?
Late edit.
Just realised somehow twrp was gone... reflashed it in fastboot mode, now everything is cool.
Thanks Adrian

It seems, that even the annoying behavior of the touchscreen in recovery will be fixed with the next nightly
@Adrian DC
You're really outstanding :good::good::good:

[OFFICIAL] TeamWin Recovery Project 3.3.1 For Zuk Z2 Pro

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer
Code:
/**
* What you do with your device is your choice.
* None of the developers of this software will be held accountable for any damages to your device or to third parties.
* You should know this by now.
**/
What's this?
This is TeamWin Recovery Project for ZUK Z2 Pro (z2_row).
This is an official recovery support thread.
Known Issues
MTP broken in 3.3.0 and newer builds because of a TWRP issue with 4.4 kernel (you can still use adb push and adb sideload)
Requirements
Unlocked bootloader
Common sense and a Z2 Pro
Downloads, changelogs, installation info
All of this info can be found at the official info page.
If you use fastboot to install TWRP, you may have to specify a vendor ID in the commandline, like so:
Code:
fastboot [B]-i 0x2b4c[/B] flash recovery twrp.img
fastboot [B]-i 0x2b4c[/B] reboot
Thanks
@varotone for the initial z2_plus TWRP device tree (and also for the thread template )
@kubersharma for some commits in the device tree
cosmedd for his work on the TWRP tree for z2_row
Frequently Asked Questions
Is this recovery compatible with both treble and non-treble ROMs?
Yes, this recovery is compatible with both non-treble and treble ROMs mounting /factory as vendor (the most updated ones are doing so), while it isn't compatible with the ROMs renaming /factory as /vendor. If the ROM you're using is still using /vendor instead of mounting /factory as vendor, report this to the maintainer and tell them to update.

gg

*Insert some random thx sentence*

I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?

robert_b said:
I'am using TWRP 3.2.3 since weeks without problems. Is this another version? Why should I use this one?
Click to expand...
Click to collapse
As first because this has the factory mounted as vendor support instead of factory renamed as vendor. If you're already using a build with this support and you downloaded it recently it means that the build is the exact same as this one. I created a thread so that things can get out of Telegram only and also because soon it'll become official (the old one is deprecated pretty much)

Thread updated with the official tag and a new official build on the TWRP.me website. Enjoy

Encryption with latest AEX is not working.

rower19 said:
Encryption with latest AEX is not working.
Click to expand...
Click to collapse
What do you mean with "is not working"? What happens when you try to encrypt?

DD3Boh said:
What do you mean with "is not working"? What happens when you try to encrypt?
Click to expand...
Click to collapse
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Hi, sorry for the late answer. Can you pm me on telegram so that we can discuss the issue and I can eventually send you some builds to test? t.me/DD3boh
Thank you!

rower19 said:
I have sucessfull encrypted my data partition with aex rom.
But twrp isn't able to decrypt it. Twrp asks for the password but after entering the right pass, i responds with password invalid.
Theres something that was changed in Android encryption (and twrp 3-2-3-1 should it fix for many other devices, here not).
Should not be a big thing.
Perhaps this helps:
review(dot)lineageos(dot)org/q/topic:%22bacon-twrp%22
Thanks for your work!
Click to expand...
Click to collapse
Checked with @DD3Boh and decryption for pie is working in a test build. He gonna push the new version after some more testing.
But be patient, we will be finally able to encrypt our device and decrypt it in twrp.
Thanks to him,
G0r3t3x

TWRP 3.3.0 just got released
Encryption was fixed, although mtp is broken because of 4.4 kernel (which is a must for encryption)
Instead of mtp you can just use adb push to push files to the internal memory, or either adb sideload <package path> to flash them directly without transferring to the internal storage (works only after having enabled adb sideload in the advanced TWRP tab)
Download link in the first post

Hi, thanks for your work.
I've tried to reinstall baseband but log says it's not installing nothing. Using twrp 3.3.0, i'm on ArrowOS.

A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery

DD3Boh said:
A new update has been released! TWRP-3.3.0-1 is present in the website
Changelog:
- Added edl reboot option (download mode)
- Don't wipe data if the command isn't sent by the user
- Sign the build with aosp keys
Go update your recovery
Click to expand...
Click to collapse
Perfectooo :good:
..btw: what about MTP? ..it works now?

satmaster said:
Perfectooo :good:
..btw: what about MTP? ..it works now?
Click to expand...
Click to collapse
It doesn't work on official builds for some reasons, so I had to disable it
I could though make a build locally where for some reasons it should work fine

I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.

lunloon said:
I need some help with the Zuk Z2 Pro. I've flashed TWRP 3.3.0.1 and it seemed to work.
However, I'm unable to get the phone detected on my pc in TWRP, or ADB sideload. The phone gets connected while rebooted in system in Zui. Using zuk2pro driver.
I've also not able to mount data.
So i followed some instructions and reformat the partitions, but i forgot the phone could not be detected in TWRP.
I'll like to know if ROMs can be flashed using OTG-USB.
Click to expand...
Click to collapse
I tried USB-OTG and it worked. Thankfully.
Can't make any sense out of the driver game.

Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.

Dolour said:
Sideload isnt working for me either, same as with the previous version, rendering TWRP essentially unusable when running a 4.4 kernel.
Resolve that first please, prior to adding more features. There arent THAT many kernels to choose from.
Click to expand...
Click to collapse
Probably you don't know why I even switched to 4.4 kernel, which is because 3.18 kernel in TWRP breaks decryption, which is quite an important thing.
Anyway I can build TWRP locally and send a build as that will somehow have mtp and USB in general working.

[DISCONTINUED][ROM][OFFICIAL][gta4xlwifi][10] LineageOS 17.1 for Galaxy Tab S6 Lite (Wi-Fi)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
Follow the instructions on the wiki https://wiki.lineageos.org/devices/gta4xlwifi
Note: You may use Odin instead of Heimdall, for this you will need to rename the recovery image to recovery.img and pack it into a tar archive.
Downloads:
Warning: 17.1 is now discontinued, use 18.1 instead
Builds: https://download.lineageos.org/gta4xlwifi
GApps: https://wiki.lineageos.org/gapps.html
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Support
Telegram group
Contributors
Linux4
Source Code: https://github.com/LineageOS

reserved

reserved

Congrats @Linux4 , you're "official" Lineage maintainer for GT4XLWIFI now.

any plans the lte edition, it really is sad people dont make anything for this version I don't actually care for the lte I just happened to have bought it second hand. EDIT: nevermind just saw the actual version

Works great for me!
For anyone interested: Netflix and Nanolx microG patcher do not work out-of-the-box.
Edit: Netflix does work after using MagiskHide Props and selecting the Galaxy Tab S5e Fingerprint, clearing the Playstore Cache and activating Magisk Hide for Netflix.

Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?

SvenHee said:
Well done, switching asap!
Edit: can this version be dirty flashed over the unofficial one?
Click to expand...
Click to collapse
No, I'm sorry, you can't dirty flash official over unofficial, there are two reasons for this:
1. It's signed with other keys (lineage ones)
2. It has FBE enabled like my unofficial 18.1 has, while unoffcial 17.1 had FBE disabled

Ok, thanks for the quick reply. Will clean flash

OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?

bose301s said:
OK, I have followed the directions on the LineagOS Wiki, got the bootloader unlocked, went into the system again, got onto the WiFi, verified that Allow OEM Unlock was greyed out in the on position. I then flashed the LineageOS Recovery in ODIN and booted into it, then did a Factory Reset/Wipe Data and then used adb sideload to install the latest nightly and ARM64 Stock OpenGAPPs and then reboot, I am then stuck on the boot screen for LineageOS. Any ideas on what I need to do?
Click to expand...
Click to collapse
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time

mu1989 said:
Have you taken the correct gapps version, for Android 10???
First lineage flashing, then rebooting and then gapps flashing, the first time
Click to expand...
Click to collapse
I tried the slightly smaller step down GAPPS and it worked fine, must be something with that package or something.

Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.

I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?

SvenHee said:
I tried installing the update 0601 yesterday and that went wrong, kept booting to twrp.
I did a factory reset an installed the same version again but it seems to be throwing all kinds of problems.
At first some but not all apps would not start.
I factory-reset again and installed agian.
Now apps do start but not all apps reinstalled from the google backup.
I now want to install autodesk sketchbook but I get a message to place an sd card, which in fact is present and can be read.
I just now looked at what is available in the internal storage but that seems litterally all to be mangled, even though the apps I could install all seem to work.
Not a single recognizable folder present.
Did I omit anything with wipe/factoryreset?
Click to expand...
Click to collapse
Please just stick to lineage recovery,
I'm almost sure all of these are being caused by TWRP.
Probably the reboot to twrp thing was even caused by TWRP messing with FBE again ... Did it show "Android Rescue Party Trigger" maybe ?

Linux4 said:
Please just stick to lineage recovery,
Click to expand...
Click to collapse
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.

SvenHee said:
Thanks for the quick reply!
Is this a general lineage twrp thing, or specific to the s6-L?
I had read the guide saying to install lineage recovery but not to only use it.
Will give it a go later today.
Click to expand...
Click to collapse
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too

Linux4 said:
It should be a general problem on every device running a ROM with FBE enabled but decryption not working in TWRP
Actually you can use twrp as long as you don't touch /data (wipe and such things) but looks like OTAs through twrp don't work too..
Or did your gapps addon.d maybe not run after the OTA? That would effectively have gapps uninstalled and might cause a reboot to recovery too
Click to expand...
Click to collapse
I had the same problem with an installation with Heimdall. After that I have installed the version 1230 without problem

dgo65 said:
Thank you Linux4. I love LineagOS.
I have an Installation generic Problem for this device.
SM-P610 flash --> Only official released binaries are allowed to be flashed(RECOVERY)
Hello, I cannot install TWRP either LineagOS on my new GALAXY TAB S6 Lite WIFI Here is my example with TWRP (same with LineagOS) Device Info : download mode: Product Name SM-P610 (SAMSUNG TAB S6 LITE) Current Binary : Samsung Official...
forum.xda-developers.com
I you have any Idea...Perhaps you already had this...
Thank you for your job.
Best Regards.
Click to expand...
Click to collapse
At the end I found the solution. After the "Preparing for installation" process I had to follow this procedure.
Fix Missing OEM Unlock Toggle on Samsung Galaxy Devices (Guide)
Are you facing the missing OEM unlock issue on your Samsung Galaxy device? That's because your phone has entered the Prenormal RMM/KG state. However, if you'd like to bypass it, then you can follow…
www.thecustomdroid.com
Before to follow with the installation.
Only if anybody as the same problem.

Any ideas how to enable MIDI over USB in this ROM?

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 1 II

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 18.1
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 10.x (Q),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM is for testing purposes only and may contain unexpected bugs
2. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
3. This ROM will never work with any versions of Google Camera (GCam)!
4. You need to flash Stock Android 10 before flashing this ROM.
5. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
6. If you came from SODP ROMs, you need to go back to official Android 10 firmware, and boot into launcher.
Downloads Links
AFH
Google Applications (optional):
NikGApps: https://nikgapps.com/
Information: Flash the GApps before first boot. If not, a clean flash is recommended
Flashing and updating
How to flash
Make sure you upgraded to Official Android 10.0 from Sony
Unlock bootloader is necessary
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
2. Put your device into fastboot by volume up key.
3. Enter fastbootd:
Code:
fastboot reboot fastboot
4. Flash LineageOS:
Code:
fastboot set_active a
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata
fastboot flash system system.img
fastboot flash product product.img
5. If you are first time to flash LineageOS, Wipe the old userdata:
Code:
fastboot erase userdata
GApps:
Flash the recovery.img in the zip file
Flash and boot into Recovery then choose Apply update - Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Root access:
Flash Magisk in recovery.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Shion Sjll
The LineageOS Team
The CyanogenMod Team
Source Code:
hellobbn/android_device_sony_pdx203
Contribute to hellobbn/android_device_sony_pdx203 development by creating an account on GitHub.
github.com
hellobbn/android_vendor_sony_pdx203
Contribute to hellobbn/android_vendor_sony_pdx203 development by creating an account on GitHub.
github.com
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2021-01-20
Last Updated 2020-01-20

Important note
1. This Lineage build is based on official Android 10, not Android 11 (since AT72 hasn't been updated yet)
2. This build is highly experimental and for testing purpose only
3. This ROM may not be able to pass SafetyNet check
What works:
- Boot
- Bluetooth (LDAC might have problems, I am not sure)
- WiFi
- WiFi Hotspot
- RIL - Phone - Data
- GPS
- Camera
- Lights
- Touchscreen
- Fingerprint
- Microphone
- Audio & music
- Bluetooth audio
- NFC
- Clock
- USB
- SEPolicies: Enforcing
What does not work:
Always On Display does not seem to work properly

Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.

james194zt said:
Just tried flashing this rom, followed instructions above but it just boot loops between the sony screen and the "bootloader unlocked" screen.
Click to expand...
Click to collapse
Are you on stock android 10 before flashing? Have you erased the userdata?
I tried to flash it again and it boots successfully.

Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).

james194zt said:
Yes I was originally stock android, followed the above and erased userdata, have even booted in to Lineage recovery and done erase data from there. Interesting thing though is that Lineage recovery cannot mount system? Have flashed it a few times no change, if I leave it after a few reboots it will eventually boot up on the "B" side and the stock OS starts to boot (to getting started wizard).
Click to expand...
Click to collapse
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?

I was on the built in fastbootd not Lineage OS, I used Lineageos recovery after to see what was going on, will try the above though

clfbbn said:
1. Can you post the model of your device? Are there any errors during flashing?
2. If you are on the LineageOS recovery (FastbootD) and trying to flash the ROM, you need to explicitly specify the slot, like `fastboot flash system_a system.img`
3. If it does not work, can you try flashing the stock 10 firmware using XperiFirm and newflasher and try flashing the ROM again?
Click to expand...
Click to collapse
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.

james194zt said:
have tried the above, it showed loading in to system a in the flash process when I did it but still boot looping device model is an AT51.
Click to expand...
Click to collapse
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....

clfbbn said:
Oh sorry, seems that I forgot something. When flashing, can you try flashing the dtbo.img? I forgot to add that command....
Click to expand...
Click to collapse
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change

james194zt said:
I had already seen that command on another ROM so tried it, also doing fastboot boot:raw boot.img, that just resulted in the phone showing a "this device is corupt", so I did fastboot boot boot.img and it returned back to the usual "bootloader is unlocked" message on startup, still just boot looping though.
I did notice I was on Android 11, so downgraded the phone to the last Android 10 rom with newflasher then ran the above commands again without any change
Click to expand...
Click to collapse
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?

clfbbn said:
OK, maybe the dual SIM version is not compatible with single SIM version? I will try uploading a testing version later this day and see what happens.
Another thing you can try is not flashing the boot.img and dtbo.img and see what happens.
Edit 1: and have you ever flashed the ROMs that are Android 10? Can you successfully boot them?
Click to expand...
Click to collapse
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!

james194zt said:
I have tried the above and no luck, boot.img and dtbo.img left alone and still boot loops!
No just got the phone yesterday want it to be Google free, I am coming from a OnePlus though so not a stranger to flashing ROMs I have tried a couple of lineage ROMs now and nothing works actually on this phone.
Very strange, I have bootloader unlocked it fine, it is fastbootd and does all the above commands with no errors but just boot loops, same with any ROM which makes no sense at all!
Click to expand...
Click to collapse
Interesting, did you booted at least once when you downgraded to Android 10 because that might be the problem too?
I am also assuming this problem to be related to the vendor partition. If that is the case, I need to pull the blobs from AT51 and rebuild the ROM.
Edit: Would you mind we talking using telegram? I have PMed you my username.

I have an AT51 if I can help somehow. I'm having a different issue, but maybe its related. https://forum.xda-developers.com/t/...os-17-1-for-xperia-1-ii.4199059/post-84512259

Hi! this is awsome!
I just tried it out and everything seems to be working!
I am wondering it it is possible to get the camera pro and cinema pro working like for xperia 5 II
[EXTRA] Stock Camera && Cinema Pro && Photo Pro For AOSP
You MUST satisfy following condition: * My Device Tree Based ROM (Not SODP) * A PDX206 (Xperia 5 II ) User Download Link: Stock Camera if (ANDROID_VERSION == 10 && STOCK_VENDOR == 10) Using 52_RHE Cinema Pro [52_RHE] Photo Pro [52_RHE] if...
forum.xda-developers.com
Does anyone know how to do it?

@clfbbn, any reason for not making this build official? I'm willing to support.

ShionKagurazaka said:
Not easy to do, I think Bbn and me both are students, we don't have many times.
And then, if we need something like Sony Camera, Sony Photo Pro and so on in ROMs, we can't be offical
So why not Unoffical ?
Click to expand...
Click to collapse
I would like to make it Official because I would like to be able to get OTA updates. But I think you're right about the camera. The alternative is to not provide them and just share them separately as you share them.
I just build mine but I am thinking that not everyone has the patience to do it.

I noticed that extFAT does work on this build. Do you know how to fix it? I formatted the sd card to fat32 but the file size is limited to 4GB...

XQ-AT52 device said cannot find "system" partition" when trying "fastboot flash system system.img" . Please advise.

ShionKagurazaka said:
fastboot reboot fastboot at first
Click to expand...
Click to collapse
tried but "fastboot: usage: unknown reboot target fastboot" message appears

[ROM]-[13]-[KIEV]-LineageOS-20-[OFFICIAL]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Motorola G 5G / Motorola One G 5G Ace​
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Introduction:
This is the Official Lineage OS 20 thread for the Motorola G 5G, codename kiev.​​Join our Motorola G 5g / Motorola One 5G Ace Development Telegram Group!​
LINKS:
ROM Files: LineageOS-20​Mind The GApps: Download​Magisk: Magisk​Factory Firmware: Stock Firmware Mirror​Copy Partitions: copypartitions.zip​
How to Install:
01. Use Install instructions @ LineageOS-wiki​
NOTES:
*Note-1: Slots, ROMS install to opposite (inactive) slot​If you FLASHED ROM from "Slot A", then ROM is installed to "Slot B", If you Flashed ROM from "Slot B", then ROM is installed to "Slot A"​​*Note-2: Updating "Dirty Flash"​01. Boot recovery​02. Flash ROM​03. Reboot -> Recovery​04. Install Gapps + Magisk​05. Reboot -> System​​*Note-3: SafteyNet:​Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status. (Magisk works fine with SafetyNet patcher modules, though is not supported.)​
XDAevDB Information
kiev-lineageos, ROM for the Motorole G 5G
Contributors
erfanoabdi, SyberHexen, Jleeblanch
Source Code: https://github.com/SyberHexen
ROM OS Version: Android 11
ROM Kernel: Linux 4.19
Based On: LineageOS
Version Information
Status: Stable
Created 2021-07-05
Last Updated 2023-02-15

Changelogs:
09/19/2021
Device changelog:
- Fixed Regression with DRM Apps​

Past Changelogs:
09/16/2021
Device changelog:
- Fixed Incoming call audio bug​ - Updated Brightness overlays​ - Updated Kernel Device Trees​ - Misc Improvements​​09/09/2021
Device changelog:
- Enforcing Selinux​ - Fixed Off-mode Charging​ - Switched to Racer Off-mode animation​ - Fixed Setting device model between Ace/5g variants​ - Fixed Media studder​​08/12/2021
Device changelog:
- carrierconfig: update from kievv tag 'RRV31.Q2-36-14-8'​ - carrierconfig: update from CAF tag 'LA.UM.9.12.r1-10800-SMxx50.0'​ - update defconfig from kievv tag 'RRV31.Q2-36-14-8'​ - Show Turbo Charging instead of charging rapidly​ - enable support for freeform windows and picture-in-picture​ - upgrade bootctrl hal to 1.1​ - increase audio for speaker(s) and microphone​ - Exfat driver included to kernel for LOS recovery support​​07/22/2021
Device changelog:
- Minor Fixes​- Updated Brightness overlays​
07/05/2021
Device changelog:
- Minor Fixes​ - Switch to Pixel Power Hal​
07/01/2021
Device changelog:
- Initial Build​

Excellent work, Andrew! I can't wait to try it. Been really busy lately.

I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?

@SyberHexen I may have the same exact XT2113-2 128 GB version of this phone as I just tried your recovery that has a working touchscreen. I was wondering which partitions should I backup?

I made this tutorial to help in flashing.

Murderburger said:
I am attempting this right now, So do we want the ROM to install Slot A or Slot B? I see you posted it installs to the opposite Slot
EDIT:
Had it on Slot A so it installed to Slot B and worked fine
Gapps has to be installed from https://wiki.lineageos.org/gapps.html the one you provided above does not work
For some reason on my MetroPCS phones Network its trying to connect directly to T-Mobile and not Metro by T-Mobile. Tried to Choose Network and nothing came up any ideas?
Click to expand...
Click to collapse
Use apn from your stock install or the metro website, or are options to edit apn greyed out?

SyberHexen said:
Use apn from your stock install or the metro website, or are options to edit apn greyed out?
Click to expand...
Click to collapse
I copied the exact apn settings from my GF's phone which is also a metro 5g ace and could not recieve texts, could text myself, could texts others, could call and get calls, just could not get texts back

@AviBharti35 thanks!!! I was also curious where the system, data, vendor, and boot partitions are when backing up? I see super and all these partitions. I'm used to seeing system image, vendor image, data, and boot from different devices so I want to make sure I backup and restore the correct partitions just in case I want to restore the stock os in TWRP along with the stock recovery after flashing TWRP?

Murderburger said:
I copied the exact apn settings from my GF's phone which is also a metro 5g ace and could not recieve texts, could text myself, could texts others, could call and get calls, just could not get texts back
Click to expand...
Click to collapse
This happens when debloating and deleting google framework. See my tutorial on debloating and go to step 3.

Just to clarify, this works on the Motorola one 5g ace?

bobbyp1086 said:
Just to clarify, this works on the Motorola one 5g ace?
Click to expand...
Click to collapse
Sure is. You can always boot into bootloader mode to compare codenames to be certain, in this case it's 'kiev'.

Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing
Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?
Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?
Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4

If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.

bobbyp1086 said:
Awesome, one more, is rw a reality since it's lineage or is that not working? I hate reinstalling everything but hey booting up to twrp will let me back it up so plus 1 to amazing
Click to expand...
Click to collapse
Can't say for sure, I want to build a custom kernel before moving to this myself (and I never touch the system partition anyway), but it should be formatted for R/W.
bobbyp1086 said:
Edit: looking over it a few questions, when fresh install, do we flash that one file if it's not updating firmware, going from stock rooted to lineage?
Click to expand...
Click to collapse
You only need to do an EFS backup and run Copy Partitions once when moving from Stock to Custom.
bobbyp1086 said:
Would it be easier, since I know this route, to boot twrp - back up - flash twrp - wipe and format (should remove encrypted state) - then install lineage, gapps and then magisk? Or is that not a good way anymore?
Click to expand...
Click to collapse
Follow the OP, reboot before installing GApps and Magisk.
bobbyp1086 said:
Lastly, before I go and flash it, can you explain the different boot colors, red, orange and green? If they are what I think I could prolly help in getting the phone to orange or green, if it's anything like my old note 4
Click to expand...
Click to collapse
Android Verified Boot state can never be changed on custom firmware without an exploit early in the boot chain or getting private signing keys. It does not matter, Magisk hides this so it has no effect. You can still pass safetynet as long as hardware attestation is not enforced. Your Note 4 does not have AVB.
atsalchenberg said:
If I already flashed TWRP, do I need to reflash the stock recovery and then go about the steps or can I do the clean flash from the TWRP recovery? I just don't want to break my device, my phone's my only source of Internet.
Click to expand...
Click to collapse
No, you can flash over it without effecting anything else. The OP never says to flash recovery and it's optional anyway. Just boot into bootloader mode and send it over with "fastboot boot twrp.img".

Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.
Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.

omgbathtub said:
Any way to get rid of the red border that flashes when changing apps at times? Would love to run this but that annoyed the hell out of me and I had to return to stock.
Also, seemed to have an issue wherein the SIM card had random disconnects? I live in a low service area but I've never seen what was happening on this happen on stock. It would kick me out of the SIM settings menu, drop connection, then come back a second later with a data connection. XT2113-2 factory unlocked.
Click to expand...
Click to collapse
First off much thanks to the o.p for a custom rom. No complaints here.
I had to research Lineage os since i haven't used that particular rom since oreo 8.1.1.
Havoc ,AICP and RR have been my go to roms...
Anyways, To use gapps it was recommended to use MindThegapps..ill send a link.
Ill tell ya this rom is tricky but good after proper installation. I saw the red rings of death too but after i re-flashed and put the rom on slot_a and flashed the Recommended gapps , no more Red Ring or nothing...
My problem was flashing gapps..Lineage only accepts gapps when flashed before first boot up. Also lineage flashes its own recovery and i couldn't boot to twrp or flash it.. Luckily, the lineage recovery has signature verification off so i was able to flash the gapps in Lineage recovery..
Hope this helps...
My install process requires an ext sd card and a cpu running windows 10..
Have copy of partitions zip lineage rom plus mindthegapps11 zip and optional magisk 23 zip on external sd card..
1. Flash stock firmware... mirror lolinet....moto kiev.. via fastboot..
2.Once new stock rom installed boot to welcome screen.
3.Now power off phone hold volume down have usb cord plugged in the phone then plug into cpu ..now ur in boot loader mode...
4.adb command fastboot boot recovery.img
in twrp now navigate to reboot and select reboot to slot_b
5.now flash copy partitions zip and lineage rom
6.Now select reboot to bootloader
7.Use volume keys to navigate to recovery and use power button to select "Recovery".
Now ull be in lineage recovery
8.use volume keys to navigate to install update use power button to select.
9.i placed all my zips in my download folder. look for the mindthegapps zip in the folder u put it in and hit install anyways when it says signature not verified.
10.now use volume keys to navigate to reboot to "bootloader"...Not System yet...
11. now in bootloader ...adb command
fastboot -w
now reboot system and profit...

Anyone who still plays ps3 and uses tether to connect ...this app "PS3 Proxy" is a life savor.. i only play socom confrontation since the servers was hacked and back online..
Also when tethering this app lets me know if im on a vpn or local host...local host 192.0.0.2 for some reason has no connectivity. but when its on lets say an address other than the local host then all devices have great tethered internet. just a jewel i found if any might wanna know.
P.S i can only tether h+ and lte only..
5G stays on local host 192.....xx.
The guy who made the boot img to override and modify the apn was only for stock..
if your reading this can you port the modified boot.img to lineage os 11..much thanks...