Code:
/*
* Your warranty is no longer valid, unless you lie.
*
* I am not responsible for bricked devices, strained relationships,
* 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 kernel
* 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.
*
*/
C.A.F 4.14 REBORN KERNEL
This Kernel is designed for, security witch general improvement as possible .What is features included in this Kernel ?driver stable from gram-q-oss debloated ( exept some drivers from mojito-r-oss... )latest CAF Kernel from LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0latest Techpack audio LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0compiled witch AOSP Clang r433403b (13.0.3).Merged latest google common android-4.14-stable ( 4.14.258)*fixed error dts in log*ttl support for bypass some operator restriction*schedutil governor debloated*using pelt instead walt for EAS*zram lz4 as default / lz4 - lzo updated*added exfat support from mainline*latest f2fs from jaegeuk/f2fs-stable*wireguard drivers added*enable LTO clang*security features enabled - CFI clang enforced - selinux enforced by default*vdso32*TCP BBR as default , westwood*Backport TCP cubic*fixed support to report HVDCP_3P5 adapterand probably more check sources for more information about features and change ...Compatible Systems with this KernelThis kernel is only compatible for Android 11 AOSP CUSTOM ROM.kernel version for GSI is only for phh GSI using stock vendorDOWNLOAD VERSION AOSP ROMDOWNLOAD VERSION TREBLEThis Kernel will receive updates with new CAF tags and new upstream & improvementGuide Install :Boot into recoveryFlash the Kernel ZIPwipe dalvik-cache & Reboot to System- enjoy!BUG : kernel tested from curtana EEA no bug found actually . -for report bug kernel only (issue rom, firmware issue ,mod flashed ex will be hardly ignored ) -give dmesg/logcat to me and descript issue .Thanks for :Xiaomi kernel sourcesCode Aurora forum for caf 4.14 releaseall other contributors no mentionned in sourcesXDAevDB InformationC.A.F REBORN Kernel 4.14 for MI POCO M2 Pro,Redmi Note 9 S/Pro,Redmi Note 9 Pro MaxContributors :@ada12Source CodeStatus: Stable
14/12/2021
*upstream 4.14.258
*LA.UM.9.1.1.r1-00700-RENNELL.QSSI12.0
*various fix kernel by kerneltoast
11/12/2021
rebased kernel to :
latest CAF Kernel from LA.UM.9.1.r1-11400-SMxxx0.0
latest qcacld,fw-api,qca-wifi-host-cmn LA.UM.9.1.r1-11400-SMxxx0.0
latest Techpack audio LA.UM.9.1.r1-11400-SMxxx0.0
latest techpack data LA.UM.9.1.r1-11400-SMxxx0.0
Merged latest google common android-4.14-stable ( 4.14.257)
*latest exfat backport of namjaejon
*USB f_fs fix
*usb: fix undefined behavior caused by zero-length array
and more change see sources.
Damages hardware,
{Mod edit}
@ada12 Thread closed. Please advise when the issue with the kernel has been fixed and the thread could be reopened.
Regards
Oswald Boelcke
Senior Moderator
P.S. Thread cleaned from outside-XDA items.
EDIT: @ada12 Thread has been reopened.
BladeRunnerA2C said:
Damages hardware,
{Mod edit}
Click to expand...
Click to collapse
I apologize for issue you have get . I have worked on it and fixed issue before post in xda do not be afraid . kernel is rebased.
regards
ada12 said:
I apologize for issue you have get . I have worked on it and fixed issue before post in xda do not be afraid . kernel is rebased.
regards
Click to expand...
Click to collapse
Well,
I can't risk my phone again on that, so I'll request you to drop the mess you did (which damaged the hardware), find a new way and walk around it,
BladeRunnerA2C said:
Well,
I can't risk my phone again on that, so I'll request you to drop the mess you did (which damaged the hardware), find a new way and walk around it,
Click to expand...
Click to collapse
As I write it's fixed in sources
*And it's software issue it's no damage hardware reflash all firmware in edl resolve error created in fw.
ada12 said:
As I write it's fixed in sources
*And it's software issue it's no damage hardware reflash all firmware in edl resolve error created in fw.
Click to expand...
Click to collapse
Can you send me instruction on how to flash in edl?
Roberto Nigel said:
Can you send me instruction on how to flash in edl?
Click to expand...
Click to collapse
guide for windows . ( solution for linux exist too but no tested in curtana )
You need drivers Qualcomm HS-USB QDLoader 9008 in your computer. { You can find easy by little search in internet }
For enter in edl mod easy method ( I assume for this method you have access to fastboot ) :
reboot to fastboot
* fastboot oem edl
Your device will then will go to black screen only. for verify Your computer reconize your phone now as QDloader 9008 in devices manager , you are in EDL mode.
*Open miflash tools
*Select your fastboot rom for curtana if you have this codename devices ... make sure
Flash it ... Wait ... Done reboot
in TG group reborn kernel has problems. It affects hardware hmmm.
ada12 said:
guide for windows . ( solution for linux exist too but no tested in curtana )
You need drivers Qualcomm HS-USB QDLoader 9008 in your computer. { You can find easy by little search in internet }
For enter in edl mod easy method ( I assume for this method you have access to fastboot ) :
reboot to fastboot
* fastboot oem edl
Your device will then will go to black screen only. for verify Your computer reconize your phone now as QDloader 9008 in devices manager , you are in EDL mode.
*Open miflash tools
*Select your fastboot rom for curtana if you have this codename devices ... make sure
Flash it ... Wait ... Done reboot
Click to expand...
Click to collapse
you cannot use edl mode without xiaomi edl authorized account
tusharind007 said:
you cannot use edl mode without xiaomi edl authorized account
Click to expand...
Click to collapse
Thanks to clarify that I have missed that .
I have 2018 account witch full authorization since it's worked here...
Flashing engeener firmware do a full clean flash too from fastboot .
About firehose patched it's always possible to generate it . Until now I have no worked on it
nice thankyou
I flashed this version of the kernel over your past 4.14.244 and after flashing a constant reboot and had to roll back to 4.14.244 why does this version 4.14.245 not work for me?
Nice
Information about Android 12
kernel have caf tag android 11 [LA.UM.9.1].
Actually caf have no released Android 12 [ LA.UM.10 ]
But Until now no issue is reported in custom rom android 12 using LA.UM.9.1 kernel,flash is safe.
Related
This Thread is deprecated!
Please use https://forum.xda-developers.com/sony-xperia-z1-compact/development/rom-lineageos-15-1-xperia-z1-compact-t3884247/
We'll provide Lineage 15.1 builds there as well. They come in two different flavours:
pure LineageOS
Security hardened microG LineageOS
Functionality is completely the same as provived by the builds from this thread - they are build from the same sources. Only difference: The new builds are signed to guarantee a maximum of security.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Status
List template by AdrianDC
Code:
- Boot : Ok
- GApps : OpenGApps Micro recommended
- Partitions (Data, Cache) : Ext4 and F2FS supported
- Bluetooth : Ok
- WiFi : Ok
- WiFi Hotspot : Ok
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- Touchscreen : Ok
- FM Radio : Ok
- ANT+ : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & music : Ok
- Bluetooth audio : Ok
- MHL: didn't test
- NFC : Ok
- Kernel : Ok
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- USB : Ok
- USB OTG : Ok
- Encryption : Ok, but installing updates only works with adb sideload!
- SEPolicies : Enforcing
Download
https://androidfilehost.com/?w=files&flid=269301
latest version: https://www.androidfilehost.com/?fid=11410963190603873784
Click to expand...
Click to collapse
FAQ
What about device encryption?
Device encryption is working. You only have to keep in mind that you need a PC with adb to install systemupdates.
Flashing via recovery isn't working until now, because there isn't a recovery capable of decrypting Oreo /data partitions at the moment. But an easy "adb sideload" should do the job. Or installing from the external SD card.
Click to expand...
Click to collapse
What about reboot to recovery?
Reboot to recovery is only working with magisk installed. Investigating this...
Reboot to recovery is working as it should now (and of course also without magisk).
Click to expand...
Click to collapse
What about GPS?
GPS apps like GPS Status&Toolbox or SatStat don't get location fixes. Nevertheless navigating with Osmand or googleMaps should work. Positionfinding is also slow. Got better
Click to expand...
Click to collapse
I found a bug. What should I do?
We need your feedback for optimization. But your feedback is only useful in connection with logs --> see section Bugreports
Click to expand...
Click to collapse
What about root access?
Root isn't included per default (except root over adb, but it's off by default).
If you want to gain root access to your apps use one of these (depending on your taste/needs):
Official Lineage Add-on https://download.lineageos.org/extras use su (arm) 15.1 here and flash via TWRP
Magisk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Bugreports
You'll find information about logging here.
Please also note how you got the error or how it can be reproduced.
Click to expand...
Click to collapse
Sources
Kernel: https://github.com/AICP/kernel_sony_msm8974
Manifest: https://github.com/115ek/manifest
Click to expand...
Click to collapse
Credits
SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
rcstar6696
SuperLamic
drakonizer
AdrianDC
munjeni: thanks for tips and tricks
nailyk: thanks for tips and tricks
All the other contributors on sony msm8974 platform
LineageOS team
Click to expand...
Click to collapse
XDA:DevDB Information
Lineage OS 15.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact
Contributors
115ek, SpiritCroc, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
Source Code: https://github.com/115ek/manifest
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Beta Release Date: 2018-09-10
Created 2018-09-10
Last Updated 2019-03-18
Changelog
13.12.2018
fixed wrong bluetooth MAC address (00:00:00:00:5a:ad on all devices), now displaying correct device specific one
12.12.2018
synced LineageOS sources (security patch level December 05, 2018)
11.11.2018
fix problem with Lineage SU addon by using 64-bit binder API (thanks @NyQuilXT)
synced LineageOS sources (security patch level November 05, 2018)
14.10.2018
fixed GPS 3D fix
08.10.2018
fixed MHL (thanks @koron393)
added callrecording
synced LineageOS sources (security patch level October 05, 2018)
23.09.2018
fixed reboot to recovery without magisk
minor improvements from AICP devices trees (thanks @SpiritCroc)
synced LineageOS sources
10.09.2018
initial release
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
Encryption : Ok but needs recovery capable of Oreo decryption for installing updates (AFAIK such a recovery doesn't exist until now for our device...)
Click to expand...
Click to collapse
I'm actually having some trouble finding a up-to-date recovery.
Jeroen1000 said:
Hi 115ek. Thanks for making this. I'm not new to flashing but I have a question nonetheless. What do you mean by
I'm actually having some trouble finding a up-to-date recovery.
Click to expand...
Click to collapse
You can use this https://androidfilehost.com/?fid=5862345805528046823 or that https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450.
For Lineage 15.x flashing you need TWRP>=3.2.x If the version is older you'll end up in a error 7.
Concerning decryption: Google introduced some new encryption stuff and so the decryption of /data from inside TWRP is broken. Some guys are working on it (@nailyk).
Encrypting the device should work fine, but I don't know what happens if you want to update the encrypted device. (I'm going to test that ).
Basically you need to store the update package outside of encrypted partitions... Maybe adb sideload works - but it's circumstantial.
Edit:
That's only interesting if you plan to encrypt your device. Otherways you can relax.
Edit2:
adb sideload should do the job. But you need a PC for updating. Installing an image directly via recovery isn't possible until now.
With sources for both kernel and system unlike the other port! Thanks, I'll definitely be using this!
Xperia J1 Compact
could this work on an Xperia J1 Compact?
it's basically the same phone with the same specs right?
The rom looks very stable and balance, but I've some problems with root procedure. I tried the lineage addon, the root seems active, but opening apps (es. Ad away) results unrooted, any ideas?
Update: Now Works. Flashed lastest Magisk
Amazing to see this old device on Oreo, just installed and it feels smooth and nice. Just a pity that I have broken the sim card connectors inside so I cant use it as a phone but I will fins use of it at home just for fun. Thank you for your work 115ek :good:
Great to see this rom realy! This rom have stock camera?
munjeni said:
Great to see this rom realy! This rom have stock camera?
Click to expand...
Click to collapse
What do you mean with stock camera?
There was a thing with kernel versions 3.4 and 3.10, wasn't it? We're using 3.4.
Concerning the camera: I'm not that expert, but it looks okay I would say.
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
115ek said:
Feel free to contribute: There's still the reboot-to-recovery problem and Pie is in the starting blocks.
Click to expand...
Click to collapse
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
raschad said:
my phone reboots to recovery.
Need to install Magisk
without it I also do not reboot to recovery
Click to expand...
Click to collapse
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
115ek said:
Thanks, but I already knew this
But I like to reboot to recovery without magisk. I think there are people around who don't like/need magisk (including me).
The fact that it works with magisk may locate the problem to the boot.img. I have init_sony in mind and will check that.
Any ideas welcome
Click to expand...
Click to collapse
I meant does this rom have stock camera blobs? Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
munjeni said:
Do you have property: ro.bootmode
and does /proc/cmdline shows diferent bootreason when you set reboot reason to recovery?
Click to expand...
Click to collapse
Good news: an easy import of your init_board_device.h did the trick. Maybe a timing problem?
Anyway: reboot to recovery is now working correctly, even without magisk
Is that okay for you: http://gerrit.aicp-rom.com/c/AICP/device_sony_msm8974-common/+/73688 ?
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
munjeni said:
I meant does this rom have stock camera blobs?
Click to expand...
Click to collapse
We're using them https://github.com/AICP/proprietary_vendor_sony/tree/o8.1/rhine-common/proprietary/vendor, so I guess yes.
You're more into topic, aren't you? How to distinguish between AOSP and stock blobs? There were some mysteries around DRM, camera quality and so on. I remember a separate thread you also participated in...
But I'm not really into this topic.
munjeni said:
I just found this https://github.com/LineageOS/androi...neage-15.1/init/init_sony/init_board_device.h its just prototype so seems you have missed init_sony/init_board_device.h in your device tree...
Click to expand...
Click to collapse
No, it's actually in here: https://github.com/AICP/device_sony_msm8974-common/blob/o8.1/include/init_sony/init_board_device.h
But It's different from yours. Yours performs another keycheck.
Seems rom have stock blobs. To distinguish between AOSP and stock blobs... depends on kernel you have using, aosp kernel can't be used with stock blobs since aosp camera kernel module is diferent, but I'm out of development for long, have no free time and to be honest I still didn't forgot treatment & injustice for my status on xda, that made me more inactive here. Recognised members have bad treatment here, seems senior members have much more priority than recognised members, and thats reason why everybody here need to care how many hours per day to waste here. I decided to stop wasting my time on xda since xda leaders do not respect anybody's hard work here. I recommend the same to everyone here.
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem ?
ULT][MO said:
I tried "reboot to recovery", after Sony logo the phone reboot again (also if you press recovery button), and to enter in recovery you've to push again the button at the second reboot.
It is like a normal reboot... But it's not a problem
Click to expand...
Click to collapse
What recovery are you using? I recommend this one: https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/lineageos-12-1-z1c-current-sec-patches-t3614936.
With mine from here https://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/recovery-twrp-3-2-1-t3759450 it still won't work. Maybe a timing thing.
But it's okay if we have at least one working TWRP.
And oreo /data decryption is still an issue we have to address.
This is basically a tl;dr thread.
I don't want to make a thread that everyone will lazy to read.
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a fully touch driven user interface; no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Disclaimer
Code:
/*
* Your warranty is... still valid?
*
* 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 RECOVERY
* 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.
*/
Requirements
ASUS ZenFone Max Pro (M1) ZB601/2KL (of course)
Unlocked bootloader, in either ways (official, unofficial)
Some knowledge on how to deal with your device... and patience.
Flashing InstructionsI assume you've done (very) basic steps on preparing to flash your device.
Reboot device to bootloader. If device is powered off, press and hold Power + Volume Up button until ASUS logo with "FASTBOOT MODE" message appears.
Under same directory as TWRP image and ADB/Fastboot executables (if ever required), type this command:
Code:
fastboot flash recovery twrp-3.x.x_9-<kernel>-y-KudProject-X00T.img
Where:
x and y are version of TWRP you're going to flash.
kernel: k4.4 - stock firmware or custom ROMs with FDE encryption; and k4.14 - FBE for custom ROMs with FBE encryption.
IMPORTANT: After flashing, immediately press and hold Power + Volume Down for about 10 seconds button to reboot to recovery.
Swipe the option to allow modifications. This way, you'll trip Android Verified Boot (AVB) and it's required to flash no verity zip in order to be able to boot stock ROM.
Downloads
Webserver | MEGA
Old releases only: OSDN | AndroidFileHost
Known Issues
k4.4: Due to QTI keymaster's behavior, only specific stock firmware as well as custom ROMs with same platform security patch level that can only be decrypted by TWRP. Applicable versions will be indicated explicitly in the changelog.
k4.14: Recovery may start with very low vibration level. You can adjust vibration intensity in settings later.
k4.14: Recovery can only decrypt userdata partition encrypted using AES-256-XTS algorithm. Only ROMs using Qualcomm's Inline Crypto Engine (ICE) with 4.14 kernel may also be decrypted by the recovery as well. This can be assumed an intended behavior since implementation of fscrypt_ice on msm-4.14 and msm-4.19 kernels are completely different. Tell ROM maintainers wanting to switch to FBE to use AES-256-XTS instead.
Special Thanks
Dees_Troy and everyone behind TWRP
shakalaca - base device tree used for older releases
Ankit Gourav - his work on whyred
Shivam Kumar Jha - person who kickstarted ZenFone Max Pro (M1) development
Everyone involved in testing numbers of test builds.
Sources
TWRP repository fork
Device tree
Kernel source: k4.4 - k4.14
Some stuffs...Another TWRP thread? Why?
I like to keep discussions about my builds separate. Moreover, the existing TWRP that already available on XDA before doesn't seem to be maintained anymore.
I flashed via fastboot but it always fails.
Check or change your cable, use other USB slot (especially 2.0 one if 3.0+ doesn't work), or if needed try to flash recovery with USB connected to a hub.
Changelogstwrp-3.5.2_9-1-KudProject-X00T
Merged TWRP source changes up to 25 April 2021 (UTC+8)
Builds are now splitted for devices running FDE (targetting stock, running 4.4 kernel) and FBE encryption (targetting custom ROMs, running 4.14 kernel, only works with ROMs using AES-256-XTS encryption)
FDE: Can decrypt 16.2017.2009.087 stock firmware and any custom ROM with 5 September 2020 security patch
Restored ability to backup system and vendor partition (images backup for these partitions are recommended)
Switched to build system libraries from source
Added persist partition backup support
Added support for NFC availability check in recovery
Added support for formatting asusfw partition in GUI
Updated set_version script to match up Android 10's system-as-root behavior
FBE: Updated crypto blobs from 17.2017.2012.438 stock firmware
twrp-3.4.0-0-KudProject-X00T
Merged TWRP source changes up to 11 June 2020 (UTC+8)
Can decrypt 16.2017.2005.082 stock firmware and any custom ROM with 5 May 2020 security patch
Switched f2fs-tools to latest AOSP master
Only allow user to backup system and vendor images
set_version script doesn't longer touch persist partition; script now has hardcoded SKU and version instead in case ASUS props can't be found
Updated prebuilt kernel based on S082 source drop
F2FS kernel driver updated to 5.3-rc1 with backports up to 5.7-rc1 from 4.9
Switched to arter97's fork of exFAT
Switched from NTFS kernel driver to FUSE ntfs-3g due to incomplete write support
twrp-3.3.1-0-X00T-20190526
Fixed stock ROM flashing due to missing prop
Fixed FDE decryption
twrp-3.3.1-0-X00T-20190525
Updated F2FS on kernel to 5.2-rc1
TWRP 3.3.1 + upstream changes
twrp-3.3.0-0-X00T-20190513
Updated base to android-9.0
Updated blobs from 16.2017.1903.050
Support for flashing unmodified stock firmware (please read notes!)
Rebased kernel to S050 source drop
Updated F2FS on kernel to 5.1-rc1
TWRP 3.3.0 + upstream changes
twrp-3.2.3-0-X00T-20190217
Now based on whyred official TWRP tree
Reverted kernel to stock-based as-released (S339) with F2FS upstream and sdFAT included
(this should fix USB-OTG support while retaining support with latest f2fs-tools)
TWRP upstream changes
twrp-3.2.3-0-X00T-20190118
Pick more patches from LineageTWRP project
Updated f2fs-tools to latest development branch
Slight cleanup
TWRP upstream changes
twrp-3.2.3-0-X00T-20190115
ADB sideload fixed for everyone
f2fs-tools v1.12.0
Disabled Synaptics' firmware update driver entirely
Removed qcacld-3.0 from kernel
TWRP upstream changes
twrp-3.2.3-0-X00T-20190108
Removed ntfs-3g from recovery
Included several extra recovery keys
Updated kernel to S338-based
Disabled Synaptics' startup firmware update
TWRP upstream changes
twrp-3.2.3-0-X00T-20181231
Updated platform security patch override to 2018-11-01 (matches 338 firmware)
twrp-3.2.3-0-X00T-20181226
Imported more proprietary blobs from stock 337 firmware
TWRP upstream changes
twrp-3.2.3-0-X00T-20181224
Allow wiping vendor partition
2nd CPU target set to Cortex-A73
Initial import of proprietary blobs from stock 337 firmware
Updated kernel to S337-based
TWRP upstream changes
twrp-3.2.3-0-X00T-20181215
Removed texfat and tntfs stock modules
Enabled DT2W
twrp-3.2.3-0-X00T-20181214
Rebased to shakalaca's tree
CPU target set to kryo
Updated platform security patch override to 2018-10-01 (matches 337 firmware)
Switched to my rebased kernel
TWRP upstream changes (android-9.0 branch)
twrp-3.2.3-0-X00TD-20181024
Initial build, based on ASUS-X00TD tree
Notes
"fastboot boot" command isn't supported by our bootloader. Don't ever try that. (blame ASUS/Huaqin)
I'll try to always keep this recovery updated especially when ASUS releases firmware update that also updates AOSP security patch. Security patch set in TWRP needs to match stock firmware used so TWRP can decrypt data partition. This isn't possible with current state as the bump is useless.
Unmodified Stock Firmware SupportWith introduction of unmodified stock firmware support, I need to clear up some confusions you've if any. Notes below are copy-pasta from my post elsewhere:
Code:
Starting this build, recovery supports flashing stock firmware without modifying the updater-script. In order for it to be possible, ro.product.device has to be set to ASUS_X00TD.
This, however, breaks flashing of custom ROMs that check for either X00TD or X00T.
Simply supporting it doesn't mean that you can flash stock firmware directly; you need to be at least on stock when you flash the recovery, so required properties can be exported to /persist which then will be set on every recovery boot up.
Still not sure though, as some ROMs check for ro.product.device and then fallback to ro.build.product for matching devices.
Flashing incremental OTAs are supported but not recommended, since you'll most likely flash verity disabler at the minimum and get the flashing failed upon patching boot.
In plain text:
The recovery has ro.product.device set to ASUS_X00TD that may break custom ROM flashing.
You need to be on stock before booting the recovery for the first time, then afterwards you can flash any stock firmware. 21 June 2020 UPDATE: Now not required, as it's now hardcoded in the script itself and since touching persist is never a good idea to begin with.
If you modify your system in any ways and don't have any system backup to restore, don't flash incremental OTAs. This also includes TWRP tampering system to prevent stock recovery from overwriting TWRP.
Verifying released buildsThis was originally posted on KudProject's Telegram channel and copy pasted here with minor edits for easier access.
Following TeamWin's stance about unofficial TWRP downloads here, all release builds from KudProject will start to be signed using my GPG key to ensure that you get a copy of legitimate builds directly from me.
You can download both of my currently active public keys here. Importing from PGP keyserver will be made available in the future.
To import on Linux:
Code:
gpg --import krascgq.gpg
To verify builds on Linux:
Code:
gpg --verify <build-name>.sig <build-name>
Windows users will need to search for compatible tools.
size is almost half from official recovery ?
I have been using official TWRP 3.2.3.0 since last 2-3 FW updates and haven't faced any problem. However, it's good to have a specific updated TWRP for 601KL.
theraaj said:
size is almost half from official recovery ?
Click to expand...
Click to collapse
And that almost half size comes from unwanted and unused SDM630, SDM636, and SDM660 DTBs concatenated inside kernel image used.
Sent from my ASUS_X00TD using XDA Labs
First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?
Ak-64 said:
First of all thank you for updating the twrp. Could you make something clear.
Is it synaptic only twrp if not can it be flashed over the older twrp?
Will it be supporting encryption?
Click to expand...
Click to collapse
1. It's not a Synaptics' exclusive version, and well you can override any installed TWRP versions.
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Sent from my ASUS_X00TD using XDA Labs
Thank you very much for your amazing work.... hope this TWRP will get the official tag soon??
Can this decrypt encrypted data partition yet?
Thank you for your excellent work, @krasCGQ
@krasCGQ Have you been able to fix the adb sideload function that doesn't work in the older twrp builds? Thanks. Otherwise, this is good as official. Thanks for your hardwork!
I couldn't able to touch anything after booting in to recovery
I need to press power button twice to use it
Any solution
krasCGQ said:
2. Not tested on my side since my data isn't encrypted, but I try to keep the platform patch inline with latest firmware so feel free to test.
Click to expand...
Click to collapse
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.
vladlp said:
Hi,
you have to overwrite init.recovery.vold_decrypt.keymaster-3-0.rc in /recovery/root/ (like in shakalaca version), because the name of ven_keymaster-3-0 service is [email protected] with "-qti" at the end. Than encrypted data will work. I already test it.
Click to expand...
Click to collapse
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Sent from my ASUS_X00TD using XDA Labs
krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
Any planning to official sir ?
Sorry if asking.
gusbalaa said:
Any planning to official sir ?
Sorry if asking.
Click to expand...
Click to collapse
Nope.
Sent from my ASUS_X00TD using XDA Labs
sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm
SlamDec said:
sorry for noob question, if i flash this new twrp it wipe my current OS or replacing twrp only? tyvm
Click to expand...
Click to collapse
The latter if you flash it on the right partition; if not... :silly:
Sent from my ASUS_X00TD using XDA Labs
krasCGQ said:
I pushed a test build on selected Telegram device testing groups with several init files replaced. I'll make it available for public today or tonight.
ADB sideload has been fixed on that build, BTW.
Click to expand...
Click to collapse
And... ~24 hours late from expectations, lol.
It's up for public now.
Sent from my ASUS_X00TD using XDA Labs
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime)
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
jerpelea said:
for a complete security patch you have to
1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
2. build and flash the ROM
* The security patch may affect or not the proprietary parts depending on HW and implementation
* After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release
Click to expand...
Click to collapse
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
@Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
@kgvarunkanth for the jenkins build server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 10
Created 2019-09-29
Last Updated 2020-10-23
Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, unless otherwise written.
GCAM Camera App:
Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.
Installation with a recovery:
fastboot flash oem_a oem_*.img
fastboot flash oem_b oem_*.img
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps
Dual Sim Patcher
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot -w (Wipes your internal storage and the userdata)
Continue with the normal installation
News
01.10.2020
i end of life this project now
android 10.0.0_r41 (august security patch level) was the latest by google before android 11 got released.
Click to expand...
Click to collapse
18.08.2020
now android 10.0.0_r41
august security patch level
and any other sodp open source change since my last build
Click to expand...
Click to collapse
14.07.2020
now android 10.0.0_r40
july security patch level
oemv9 support
and any other sodp open source change since my last build
Click to expand...
Click to collapse
20.06.2020
oemv8 support
and any other sodp open source change since my last build
Click to expand...
Click to collapse
06.06.2020
now android 10.0.0_r39
june security patch level
oemv7 support
charger, battery, sleep fixes
and any other sodp open source change since my last build
Click to expand...
Click to collapse
11.05.2020
now android 10.0.0_r34
may security patch level
oemv6 support
and any other sodp open source change since my last build
ps: Camera is work in progress.
Click to expand...
Click to collapse
14.04.2020
now android 10.0.0_r33
april security patch level
oemv5 support
and any other sodp open source change since my last build
switched to:
zip files to flash
dual sim patcher instead of dual sim rom files
ps: Camera is work in progress.
Click to expand...
Click to collapse
18.03.2020
now android 10.0.0_r30
march security patch level
and any other sodp open source change since my last build
ps: Camera is work in progress.
Click to expand...
Click to collapse
01.03.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
now android 10.0.0_r26
february security patch level
oemv4 -> camera & other improvements
and any other sodp open source change since my last build
ps: Camera is work in progress.
Click to expand...
Click to collapse
25.02.2020
need to take down the builds.
Oemv4 which comes tomorrow got some additional last minute changes today which needs a new rom compilation.
Click to expand...
Click to collapse
24.02.2020
oemv4 is needed or device won't boot.
Oemv4 is not backward compatible with older releases.
now android 10.0.0_r26
febraury security patch level
oemv4 -> camera & volte & other improvements
and an other sodp open source change since my last build
ps: Camera is work in progress.
Oemv4 maybe comes tomorrow.
Click to expand...
Click to collapse
18.01.2020
now android 10.0.0_r21
january security patch level
oemv3 -> initial volte/vowifi support and better camera
and an other sodp open source change since my last build
and i renamed the thread from alpha to beta and removed the unstable marking.
(it seems the rom was already stable since the last build in december)
thanks going to the entire sony open devices team containing volunteers and sony employees.
Everyone who want to help with coding can use the link in the first post on the first page)
ps: Camera is work in progress.
Click to expand...
Click to collapse
11.12.2019
rebuild after the new oem v2c release with the newest code changes and december security update.
Oem change -> "fixed incall sound"
i switched now back to self build kernels instead of using the prebuild ones to include the newest changes.
(since the oem releases in the beginning of development are faster than usual to test, report, debug the update interval of the prebuild kernels is too slow; of course this will change after we move back to monthly oem updates)
looks like with oemv3a we will move into the beta status.
(and i think then i will remove the unstable marker. It is stable, too at the moment, but i don't want to remove the marker too early)
thanks going to the entire sony open devices team containing volunteers and sony employees.
Everyone who want to help with coding can use the link in the first post on the first page)
ps: Camera is work in progress.
Click to expand...
Click to collapse
30.11.2019
rebuild after the new oem v2b release with the newest code changes.
Adsp update and keymaster update in the closed source binaries.
Now the work in progress camera driver is usable, also the encryption, decryption and the lockscreen usage.
The xz3 should now be bootable, too.
Instead of building the kernel myself, i use now the prebuild and tested kernels by sodp.
The current one is 5 days old and doesn't include the newest stabilization update for the smd845, which is under internal testing.
But it is already pretested. :d
ps: Camera is work in progress.
Click to expand...
Click to collapse
24.11.2019
rebuild after the new oem v2a release with the newest code changes and android 10.0.0_r10 (november security level).
Providing now single and dual sim builds
many stability updates
added camera, sound calibration, sensors. Also fixed keymaster and adreno.
And other fixes and optimizations.
Ps: Camera is work in progress. Now since it is compatible with kernel 4.14 the further updates/upgrades will be made here.
Aaaaaand we (will) support 120fps and hdr out of the box.
Click to expand...
Click to collapse
04.10.2019
rebuild after the new oem v1c release with the newest code changes.
Click to expand...
Click to collapse
03.10.2019
rebuild after the new oem v1b release with the newest code changes.
Boot to android is possible since oemv1b.
Click to expand...
Click to collapse
02.10.2019
with the new oem v1b blobs the tama devices are bootable to android.
Click to expand...
Click to collapse
29.09.2019
first alpha rom for the xz2, xz2 compact, xz3.
It will be stuck at sony logo and reveal a full adb shell.
It is single sim, since having a working mobile network is not a priority right now. (too unstable rom).
Click to expand...
Click to collapse
29.09.2019
first alpha rom for the xz2, xz2 compact, xz3.
It will be stuck at sony logo and reveal a full adb shell.
It is Single Sim, since having a working mobile network is not a priority right now. (Too unstable rom).
Click to expand...
Click to collapse
First woohoo!!!!
There has been an update of SW binaries today
UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436
UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.
ozamyatin said:
There has been an update of SW binaries today
UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436
UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.
Click to expand...
Click to collapse
But it least it boot once?
ozamyatin said:
There has been an update of SW binaries today
UPDATE1
Managed to boot android 10 with SW binaries ver. 1b from 1st October after flashing vbmeta from twrp section with command fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img. Device: Dualsim akatsuki 9436
UPDATE2
Still very unstable - after booting and turning the screen off to sleep, the phone goes into recovery and asks to wipe data / factory reset. So it is basically unusable at this point.
Click to expand...
Click to collapse
Thank you for your test!
What's the crash log in the/sys/fs/pstore/ folder right after boot after the crash happened?
(A second boot after the crash would delete the pstore logs)
02.10.2019
With the new OEM v1b blobs the tama devices are bootable to android.
Click to expand...
Click to collapse
03.10.2019
Rebuild after the new OEM v1b release with the newest code changes.
Boot to android is possible since OEMv1b.
Click to expand...
Click to collapse
04.10.2019
Rebuild after the new OEM v1c release with the newest code changes.
Click to expand...
Click to collapse
The same thing...
MartinX3 said:
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level and the OEM binary got fully implemented, if there is no need for a critical hotfix.
Bugtracker:
My Bugtracker
SODP Bugtracker
FAQ:
Switch the A/B slot for every monthly release to make sure you execute the same amount of write cycles on the entire flash storage. (Extends hardware lifetime) Bootloader issue needs to get fixed to make custom roms bootable on slot B.
[*]A bugreport needs logcat, dmesg and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
Switch SeLinux to permissive first, restart your device and look if that fixes the issue. (permissive.zip is in the TWRP bundle).
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
For a complete security patch you have to install the newest stock firmware and boot it once.
https://github.com/sonyxperiadev/bug_tracker/issues/258#issuecomment-445816826
TL;DR Flash the latest stockfirmware, boot it once, to update your baseband/mobile network drivers and then flash this ROM.
(I prefer and support only newflasher from XDA and xperifirm to download the firmware.)
Maybe this helps windows users:
https://developer.sony.com/posts/flash-tool-updated-with-new-feature/
Installation:
FASTBOOT
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash oem oem_*.img (Tama (latest) -> https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/
(Optional, but mandatory on first boot) fastboot flash userdata userdata.img -> will factory reset the device.
Reboot into SYSTEM
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
http://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with 7-zip or Linux.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea and the entire AOSP developers paid by and get inventory from the sony company and their volunteers coding this wonderful piece of software
@dhacke thank your for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: Alpha
Created 2019-09-29
Last Updated 2019-10-04
Click to expand...
Click to collapse
Was using your OmniROM version on my XZ2 (h8266) and had many problems, like the sound from dynamic or the speaker making a craking noise during the phone calls. Tried this ROM using the tama 10 img, and as you've said, the system booted as android but then stopped responding to any action, even after repeated restart. Basically it was working before going to sleep mode... btw camera wasn't booting at all. Hope you'll find the way to fix all of the bugs=)) Good luck to you!
Mazurik said:
Was using your OmniROM version on my XZ2 (h8266) and had many problems, like the sound from dynamic or the speaker making a craking noise during the phone calls. Tried this ROM using the tama 10 img, and as you've said, the system booted as android but then stopped responding to any action, even after repeated restart. Basically it was working before going to sleep mode... btw camera wasn't booting at all. Hope you'll find the way to fix all of the bugs=)) Good luck to you!
Click to expand...
Click to collapse
Camera will be added in OEMv2
Which problems you had aside from the work in progress camera and the cracking noise (which can be reduced by use the speakers limited at 70% max volume)?
The SODP team will fix them for sure
Thank you
We just need bug logs from random phone usage error with an instruction how to reproduce the bug.
This month was mainly to get the phone booted with Q and the new 4.14 kernel.
Forgot to mention...
MartinX3 said:
Camera will be added in OEMv2
Which problems you had aside from the work in progress camera and the cracking noise (which can be reduced by use the speakers limited at 70% max volume)?
The SODP team will fix them for sure
Thank you
We just need bug logs from random phone usage error with an instruction how to reproduce the bug.
This month was mainly to get the phone booted with Q and the new 4.14 kernel.
Click to expand...
Click to collapse
Btw, when checked the phone model - instead XZ2 (h8266) - it was XZ3=)))
My friend, I need your advice! From your perspective, which custom ROM would work without bugs for XZ2 h8266 while waiting for your stable versions? Tried Existenz yesterday v10 for .151 and honestly feel it as not my kind of stuff, and liked OmniRom better=))) What about Lineage? its the only one I haven't tried before=) What ROM is your favorite?!
Mazurik said:
Btw, when checked the phone model - instead XZ2 (h8266) - it was XZ3=)))
My friend, I need your advice! From your perspective, which custom ROM would work without bugs for XZ2 h8266 while waiting for your stable versions? Tried Existenz yesterday v10 for .151 and honestly feel it as not my kind of stuff, and liked OmniRom better=))) What about Lineage? its the only one I haven't tried before=) What ROM is your favorite?!
Click to expand...
Click to collapse
Aye I recommend OmniROM here
I use it as daily driver.
The SonyAOSP mostly gives you a plain AOSP experience
The LineageOS is outdated, but a newer SODP based one (by the SODP members) is om the todo list for the entire tama platform.
Be aware that the camera is not in a good state and the upcoming camera updates are only appearing on the upcoming OEMv2 (4.14 kernel) which is not stable enough for daily usage.
Thx 4 u response=)
MartinX3 said:
Aye I recommend OmniROM here
I use it as daily driver.
The SonyAOSP mostly gives you a plain AOSP experience
The LineageOS is outdated, but a newer SODP based one (by the SODP members) is om the todo list for the entire tama platform.
Be aware that the camera is not in a good state and the upcoming camera updates are only appearing on the upcoming OEMv2 (4.14 kernel) which is not stable enough for daily usage.
Click to expand...
Click to collapse
Thx a lot Bro I'll probably try to flash the OMNIrom again and hope that the bug with cracking sounds during the phone calls will disappear while keeping the dynamic around 70%. Before asking, I've checked your suggestions under OMNIrom not to rush for updating to 4.14 until its stabilisation=)
Thx a lot for your releases, hope you did well on your exams=)))
For those are curios the next update will come after OEMv2 (hardware drivers; which has no ETA).
https://developer.sony.com/develop/open-devices/latest-updates
OEMv2 got released
Added camera, sound calibration, sensors. Also fixed keymaster and Adreno.
The ROM also got stability updates and enhancements.
The next release I will publish will contain a better camera and fixes against the sound issues (compared to my android 9.0 builds with kernel 4.9).
The XZ2, XZ2c & XZ3 are on a good way thanks to the Sony Open Devices Developers (Volunteers and Sony Employees).
24.11.2019
Rebuild after the new OEM v2a release with the newest code changes and android 10.0.0_r10 (November security level).
Providing now Single and Dual Sim Builds
Many stability updates
Added camera, sound calibration, sensors. Also fixed keymaster and Adreno.
And other fixes and optimizations.
PS: Camera is work in progress. Now since it is compatible with kernel 4.14 the further updates/upgrades will be made here.
Aaaaaand we (will) support 120fps and HDR out of the box.
Click to expand...
Click to collapse
I think I bricked the phone with latest rom.
There was no problems after booting system, all worked fine.
Then some time later I noticed that can't wake up phone by pressing power button.
And now no one combination works for me (no effect, no led indication ): +/power, -/power, charging...
Sad :|
What is this kernel project ?
Xioami make daisy Q stock kernel brocken . , this project is designed for share kernel CAF Q for stability and safety kernel updated for your devices
What is features added in this Kernel caf daisy q 3.18 ?
Merged caf tag 'LA.UM.8.6.r1-04600-89xx.0
added caf tag prima wlan 'LA.UM.8.6.r1-04600-89xx.0 in source
@33bca CAF kernel rebased
*merged LA.UM.8.6.r1/fixes
*branch 'aosp/android-3.18' merged
*latest security patch google merged
*exfat driver
*upstream mismerge fix
*qcom mismerge
*touchscreen : updated driver fts from daisy-q-oss
*hqsysfs added
*tcp : set improvement to initial 64k
*preserve memory on restart
* Disabled dm-verity and Force vendor encryption
* Only build daisy dtb ( why build dtb for other device... )
And probably more change missed check source for more info
Compatible Systems with this Kernel
* this kernel is designed by xiaomi for daisy android 10 stock rom , so its mean this kernel work too in @phhusson gsi system
Guide Install :
1) Boot into TWRP recovery
2) decrypt your storage
3) Flash the Kernel ZIP file & re-flash magisk if installed
Reboot to System- enjoy!
DOWNLOAD
Thanks for :
C.A.F
@33bca
-and all other no mentionned in sources
XDAevDB Information
Kernel DAISY Q 3.18 for Mi A2 Lite (daisy)
Contributors :
@ada12 @33bca
Source Code: https://github.com/Aarqw12/kernel_xiaomi_daisy-1
Status: Stable
Current Stable Version: LA.UM.8.6.r1-04600-89xx.0
Stable Release Date: 2020-06-23
2020/04/13 update
*merged caf tag LA.UM.8.6.r1-04200-89xx.0 & prima caf tag LA.UM.8.6.r1-04200-89xx.0
Merge remote-tracking branch 'aosp/android-3.18' into LA.UM.8.6.r1
driver leds :
*aw2013&aw2023 driver update from daisy-q-oss
*Change leds-qpnp-flash from daisy-p-oss and enabled
*Enabled Serial Number Proc Interface
2020/04/23 update
merged prima caf tag LA.UM.8.6.r1-04600-89xx.0
It ran smoothly! Thank you!!
KERNEL reuploaded rebased in 100% caf project kernel for avoid all change damaged by xiaomi in daisy-q-oss
Run great, but only one problem for me... Not working Swipe with fingerprint for notification.
swipe fingerprint need support in system:crying: ...
Buddy_888 said:
Run great, but only one problem for me... Not working Swipe with fingerprint for notification.
Click to expand...
Click to collapse
Anyone already try with phhusson GSI ?
I use phhusson gsi ,no any problems ...
gusbalaa said:
Anyone already try with phhusson GSI ?
Click to expand...
Click to collapse
after another report, xiaomi have no delete support fp gestures its just fp goodix gestures is no good for system. I have updated link witch fix for goodix gestures ...
Buddy_888 said:
Run great, but only one problem for me... Not working Swipe with fingerprint for notification.
Click to expand...
Click to collapse
ada12 said:
What is this kernel project ?
Xioami have make daisy Q stock kernel brocken and can damage permanently your phone ... , this project is designed for share kernel c.a.f Q for stability and safety kernel 3.18 Q for your devices
What is features added in this Kernel stock caf daisy q 3.18 ?
Merged caf tag 'LA.UM.8.6.r1-04000-89xx.0
added caf tag prima wlan 'LA.UM.8.6.r1-04000-89xx.0 in source
@33bca CAF kernel rebased
*merged LA.UM.8.6.r1/fixes
*exfat driver
*adreno properly set GPU timeout
*upstream mismerge fix
*cpufreq governor improvements added
*qcom mismerge
*touchscreen : updated driver fts from olive-p-oss
*tas2557 codec sound added
*hqsysfs added
*TTL fix included
*tcp : set improvement to initial 64k
*preserve memory on restart
* Disabled dm-verity and Force vendor encryption
* Publish charger voltage to the usb psy :
-This brings back the "Charging slowly", "Charging" and "Charging
rapidly" texts on the lock screen.
Contributors :
@ada12 @shivamkumarJha
Click to expand...
Click to collapse
Will this kernel fix issues related to the bricking of daisy phones once updated to the Android 10 os v11?
Or is it for only d gsi & cfw for daisy?
Thanks
ada12 said:
I use phhusson gsi ,no any problems ...
Click to expand...
Click to collapse
Everything is fine right ?
1) this kernel fix issue for bricking in stock ROM v11
2) can be used too for gsi only after stock v11 ...
agbadino said:
Will this kernel fix issues related to the bricking of daisy phones once updated to the Android 10 os v11?
Or is it for only d gsi & cfw for daisy?
Thanks
Click to expand...
Click to collapse
I use since some day and in my device I no see any issue ...
I no need modify kernel actually ...
gusbalaa said:
Everything is fine right ?
Click to expand...
Click to collapse
ada12 said:
1) this kernel fix issue for bricking in stock ROM v11
2) can be used too for gsi only after stock v11 ...
Click to expand...
Click to collapse
Thanks so much for ur response.
But how do i use it in order to avoid bricking my device if i choose to update to Android 10 using miflash?
Thanks...
guide flash v11
1)go in stock recovery format data reboot to fastboot
2) flash in miflash Android 10 update( ./flash_all_except_storage ) and reboot immediatly to fastboot again!
3) enter : fastboot boot twrp.img (link ), in twrp mount vendor,system , flash force disable encryption( link ) and kernel.zip
4) you can safety reboot to system
ps : run always your device in fastboot unlocked its keep your device safe to brick if update fail you can always re-flash in fastboot or reboot to edl without pin edl
agbadino said:
Thanks so much for ur response.
But how do i use it in order to avoid bricking my device if i choose to update to Android 10 using miflash?
Thanks...
Click to expand...
Click to collapse
I appreciate u taking time to explain.
ada12 said:
1)
ps : run always your device in fastboot unlocked its keep your device safe to brick if update fail you can always re-flash in fastboot or reboot to edl without pin edl
Click to expand...
Click to collapse
I guess i understand wat u mean. Always keep d phone in fastboot mode.
However while i cant tell apart d different possible variants of "mi a2 lite" phone, i have observed that mine while using miflash, flashing any rom doesnt succeed unless i put it in "EDL" mode.
Also can i get a possible link for the stock Android 10 fastboot rom download? Thanks
- for flash rom you have no variant "mi a2 lite" ( all different part is included in rom )
link fastboot v11 ( link unofficial its v10.0.18 + ota recovery extracted and all img added inside )
agbadino said:
I appreciate u taking time to explain.
I guess i understand wat u mean. Always keep d phone in fastboot mode.
However while i cant tell apart d different possible variants of "mi a2 lite" phone, i have observed that mine while using miflash, flashing any rom doesnt succeed unless i put it in "EDL" mode.
Also can i get a possible link for the stock Android 10 fastboot rom download? Thanks
Click to expand...
Click to collapse
v11.0.4.0
bootloop
no magisk modules etc..
Wiped dalvick cache ?
remained said:
v11.0.4.0
bootloop
no magisk modules etc..
Click to expand...
Click to collapse
oops..?
Please include wiping in the instructions!
and thanks <3
Lineage 15.1 for Xperia X Performance [Stock based]
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 9.x (Pie),
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 has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM will never work with any versions of Google Camera (GCam)!
3. You need to flash Stock 41.3.A.2.149 before flashing this ROM.[
4. This ROM is suitable for dual and single model
5.VoLTE is supported, but you need to enable it on stock firmware at first./COLOR]
Downloads Links
LineageOS 15.1:
Unofficial: https://www.androidfilehost.com/?w=files&flid=307067
A special twrp recovery for this ROM:
https://www.androidfilehost.com/?fid=8889791610682924454
Google Applications (optional):
OpenGapps: http://opengapps.org/ (ARM64->Android 9.0->Pico, Nano or Micro)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
LineageOS addonsu for root access:
Download the addonsu for arm64: LineageOS Downloads / Extras
Flash the zip on a working Lineage installation (once)
Upon ROM updates, the addonsu is preserved
Reboot
About the builds:
Source: https://github.com/sony-msm8996
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:
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Chippa_a
Everyone involved in working and testing
Contributors
Sjll, Olivier
ROM OS Version: 8.1
ROM Kernel: Linux 3.18.x
Version Information
Status: Stable
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: No
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: No
- SEPolicies: Permissive
Result
I tested the project you didn't test and I can test it once. Now I know that GPs and microSD are working
And I hope you will continue to optimize lineages OS based on sodp
LeafNic said:
I tested the project you didn't test and I can test it once. Now I know that GPs and microSD are working
And I hope you will continue to optimize lineages OS based on sodp
Click to expand...
Click to collapse
Thanks for feedback.
New version uploaded, it is stable now.
will you make los 17.1 for it?. your build make my device cool not like treble, i can cook eggs on it
um....btw , he is the one who maintain project treble on dora
correct me if i'm wrong
Thestardr said:
will you make los 17.1 for it?. your build make my device cool not like treble, i can cook eggs on it
Click to expand...
Click to collapse
LOL
amnesia1408 said:
um....btw , he is the one who maintain project treble on dora
correct me if i'm wrong
Click to expand...
Click to collapse
Yup.
Is there a guide to isntall this? I got the bootloader unlocked using the key generet with the IMEI from the sony website, but when I tried "fastboot boot recovery.img", the phone just booted up normally.
I then tried flashing the recovery.img, this was reported as succesful, but the phone still booted normally whenever i did "adb reboot recovery".
Right now I got it back to stock, with bootlaoder locked and 41.3.A.2.149 NOBA installed.
try to boot to recovery manually
turn off your phone
hold power+volume down to turn on your phone
it take time to enter recovery mode so be patient
amnesia1408 said:
try to boot to recovery manually
turn off your phone
hold power+volume down to turn on your phone
it take time to enter recovery mode so be patient
Click to expand...
Click to collapse
I tried that now. I can see the "Sony" logo on the screen for around 5 seconds, but then a very brief red flash and the phone reboots. This behavior repeats itself while holding power and volume down.
If I release any of the two buttons during the "Sony" logo, the phone boots the system normally.
you can try out recovery at the project treble pie thread , i think the fstab file is still same with this recovery , well i dont think it worth to try , it consume your time to reinstall the stock if it fail when installing the rom
good luck if you want to try that
MartinFierce said:
Is there a guide to isntall this? I got the bootloader unlocked using the key generet with the IMEI from the sony website, but when I tried "fastboot boot recovery.img", the phone just booted up normally.
I then tried flashing the recovery.img, this was reported as succesful, but the phone still booted normally whenever i did "adb reboot recovery".
Right now I got it back to stock, with bootlaoder locked and 41.3.A.2.149 NOBA installed.
Click to expand...
Click to collapse
some version of twrp dont work with this phone so it will boot to system instead of twrp, it dont care how many times you have tried. try using sjii twrp-Q, its support many roms
Hi, thanks for the continued development!
Can I flash this rom over the one based on SODP?
leandrox said:
Hi, thanks for the continued development!
Can I flash this rom over the one based on SODP?
Click to expand...
Click to collapse
you should flash 41.3.a.2.149 first and then install for original performance
edit: but why. sodp support gcam and more hyper performance
can someone give me a link download firmware 41.3.a.2.149 pls
Thestardr said:
you should flash 41.3.a.2.149 first and then install for original performance
edit: but why. sodp support gcam and more hyper performance
Click to expand...
Click to collapse
Thanks, yes, I will stay on the SODP based ROM.
SikeClaus said:
can someone give me a link download firmware 41.3.a.2.149 pls
Click to expand...
Click to collapse
you can download it on xperiasite.pl here
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Thestardr said:
you can download it on xperiasite.pl here
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Click to expand...
Click to collapse
Xperifirm always worked fine for me
Thestardr said:
say no to xperifirm, xperifirm dont have imei after flash (aka imei error, this mean no sim card will work and *06# will crash. i face this)
Click to expand...
Click to collapse
Fine here , you should choose the correct region