Intro:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* 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.
*
*/
About CyanogenMod:
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Not working:
- Using device microphone instead of headset mic in calls
You need the newest version of TWRP to flash this rom!
Downloads:
20160826
Google Apps (not required)
Installing guide (thanks to @Amish):
Download the rom and copy it to sd card
Boot into bootloader and flash this recovery
Boot into recovery
Wipe data/factory reset
Wipe cache partition
Select install zip from sd card.
Install the rom-zip.
Extract boot.img inside the roms zip-file.
Boot into bootloader and flash the kernel:
Code:
fastboot flash boot boot.img
Reboot your device, it will take about 10 to 20 min to boot.
Russian installing guide (thanks to @VFox777):
XDA:DevDB Information
CyanogenMod 11, ROM for the HTC One V
Contributors
jonas2790, rastomanchik
Source Code: https://github.com/AndroidPrimou/android_device_htc_primou/tree/cm-11.0
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Stable Release Date: 2016-08-26
Created 2015-03-15
Last Updated 2016-08-26
Changelog:
20160826:
- Security fixes
- Reverted some wifi changes
20160702:
- Fixes of the may and june android security bulletin
- Kernel security fixes
- Increased wifi voltage and other wifi changes
20160413:
- Fixes of the april android security bulletin
- Kernel security fixes
- Added a workaround to use handset microphone when calling with headset
- Fixed some audio bugs
20160312:
- Fixes of the March android security bulletin
- Added vdd sysfs interface for voltage control
20160207:
- Fixes of the February android security bulletin
20160108:
- Important security fixes from the android security bulletins
20150916:
- Set the default scheduler to FIOPS
- Added some NAND tweaks
- Minor kernel security fix
20150826:
- Security fixes for new Mediaserver vulnerability
- OTA server optimizations
20150816:
- Fixed the stagefright vulnerability
- Increased available ram
20150712:
- Based on final cm11 snapshot
- Enabled standalone power collapse for battery saving
- Increased earpiece volume
20150620:
- Wifi disconnecting bug fixed
- Music force-close bug fixed
- Wifi-direct support added
- Fixed screen flickering bug
- Panel initialization time improved
- Flashlight now also works when screen is off
- Disabled low-ram ui
20150527:
- Internal storage support (Micro-sd still is the default storage)
- Added DeviceSettings control for doubletap2wake tapping-height
- OTA-Updating support
- Enabled app switching button
- Reduced wifi scanning interval to 15s
- New bcmdhd kernel driver with updated firmware
- Fixed wifi and bluetooth bugs
- Decreased zram size to 128mb
- Fixed noise cancellation for speakerphone
- Improved earpiece sound quality
- Much smaller changes
20150502:
- Using better memory allocation
- Camera bugs and crashes fixed
- Performance improvements
- Changed default governor (Intelliactive)
- Has some wifi bugs again...
20150425:
- Wifi bugs fixed
- Bad earpiece sound fixed
- Added flashlight toggle for quicksettings
- Enabled sd card swapping without reboot
20150421:
- Much more available ram (363mb)
- Device specific settings app added
- Added sweep2wake and doubletap2wake
20150414:
- Video recording bug fixed
- Bass bug fixed
- New kernel with much changes
- Increased zRam size (256mb)
- Much other changes
20150321:
- Headset button issue fixed
- Signal-strength fixed
- ro.config.low_ram enabled (everything should be faster and smoother now)
- Set permissions for /dev/diag
- Enabled zRAM
20150319:
- Earpiece bug fixed
20150318:
- No Gapps workaround needed
- ADB security turned on again
- Disabled KSM
- Updated CM sources
- Some minor changes
- Bug: Earpiece doesn't work
20150315:
- First release
- ADB auth turned off
What are the differences between this and Rastomanchiks file?
Neff_V said:
What are the differences between this and Rastomanchiks file?
Click to expand...
Click to collapse
Not really much differences, I disabled the low_ram prop to get some nice kk effects and I enabled ksm, which may improve performance.
CM file manager works and I didn't include OpenCamera.
By the way: I wrote 1ceb0x, who also had this problem with shpongle and he used precompiled binaries. If we can get those binaries to run on kitkat, bass will work.
Its like dream come true i will flash it asap
gapps and some screenies please.
Thanks.
Installation failed
Amish. said:
Installation failed
Click to expand...
Click to collapse
Short answer: Use my latest twrp.
Long answer: You need a selinux enabled kernel in your recovery. The function set_metadata_recursive which sets selinux-contexts and permissions doesn't work without a selinux supporting kernel.
jonas2790 said:
Short answer: Use my latest twrp.
Long answer: You need a selinux enabled kernel in your recovery. The function set_metadata_recursive which sets selinux-contexts and permissions doesn't work without a selinux supporting kernel.
Click to expand...
Click to collapse
yes i did that..and installation was successfull but now my phone is bricked or what idk...htc logo came once and then black screen past 1-2hrs...cant get into bootloader..no adb..no response to any button..
Amish. said:
yes i did that..and installation was successfull but now my phone is bricked or what idk...htc logo came once and then black screen past 1-2hrs...cant get into bootloader..no adb..no response to any button..
Click to expand...
Click to collapse
Did you flash the kernel (boot.img in archive)?
Hold the power button for about 15 seconds and it should reboot into recovery.
jonas2790 said:
Did you flash the kernel (boot.img in archive)?
Hold the power button for about 15 seconds and it should reboot into recovery.
Click to expand...
Click to collapse
i did a full wipe and flashed the cm11.zip..i tried all those things..holding power button and all nothing..on using adb commands now its saying device is offline.
Thanks for screenies.
Amish. said:
i did a full wipe and flashed the cm11.zip..i tried all those things..holding power button and all nothing..on using adb commands now its saying device is offline.
Thanks for screenies.
Click to expand...
Click to collapse
You can't brick your device by flashing a rom.
Is your phone S-Off or S-On?
Try plugging it into a charger, maybe it has run out of battery.
jonas2790 said:
You can't brick your device by flashing a rom.
Is your phone S-Off or S-On?
Try plugging it into a charger, maybe it has run out of battery.
Click to expand...
Click to collapse
s-on is root right? s-on as per my memory.
Amish. said:
s-on is root right? s-on as per my memory.
Click to expand...
Click to collapse
No, S-On is the HTC restriction for rewriting some partitions, like the kernel partition if you're in recovery mode.
If your phone is S-On (it is by default, even with root and unlocked bootloader), you have to flash a kernel by rebooting into fastboot mode.
So if you didn't flash the kernel, you know the problem now. Did you already get it working again?
jonas2790 said:
No, S-On is the HTC restriction for rewriting some partitions, like the kernel partition if you're in recovery mode.
If your phone is S-On (it is by default, even with root and unlocked bootloader), you have to flash a kernel by rebooting into fastboot mode.
So if you didn't flash the kernel, you know the problem now. Did you already get it working again?
Click to expand...
Click to collapse
I used to directly flash the roms.zip file..never flashed kernel separately..nope its not working..htc one v is the only phone i have..:*
Amish. said:
I used to directly flash the roms.zip file..never flashed kernel separately..nope its not working..htc one v is the only phone i have..:*
Click to expand...
Click to collapse
Can you open a thread in the help forum for this please? What exactly is happening with the phone?
jonas2790 said:
Can you open a thread in the help forum for this please? What exactly is happening with the phone?
Click to expand...
Click to collapse
i guesss it was battery drain or what...it started now...i flashed the kernel using fastboot and adb commands..i guess i will fall in love within few minutes...does boot take long time?
Amish. said:
i guesss it was battery drain or what...it started now...i flashed the kernel using fastboot and adb commands..i guess i will fall in love within few minutes...does boot take long time?
Click to expand...
Click to collapse
Just finished uploading my new build
Yes, first boot does take a really long time.
jonas2790 said:
Just finished uploading my new build
Yes, first boot does take a really long time.
Click to expand...
Click to collapse
Put installation section also..now what should i do...update? i had flashed pico PA-gapps
Amish. said:
Put installation section also..now what should i do...update? i had flashed pico PA-gapps
Click to expand...
Click to collapse
You can do it without a wipe, but I wouldn't, I always do a full wipe.
jonas2790 said:
You can do it without a wipe, but I wouldn't, I always do a full wipe.
Click to expand...
Click to collapse
can we start dreaming about cm12?
Related
Welcome to the EternityProject!
What do we have here?
CM10.2-EPRJ --- Or... EternityProject's CyanogenMod 10.2 build for HTC One X!
Yeah, it's a long time I wanted to make something like that and... I'm proud of this now.
What's the point in using CM10.2-EPRJ?
It contains various optimizations made at compilation time. Moreover, it isn't being compiled with the default Android toolchain, but with a custom one that handles and optimizes the code better.
Is there anything not working?
....Watch at the bugs voice.
Everything is working well, until someone proves that something isn't!
Recommendations:
For achieving the BEST performance on CM10.2-EPRJ, make sure to use our EternityProject Kernel 3.4.37 for HTC One X: I'm developing that ROM always on our kernel and I'll also make this ROM to use the unique features that only our kernel is bringing at the time of writing this (04/08/2012).
Can I use a non-EternityProject Kernel on CM10.2-EPRJ?
For now, it's possible. Absolutely.
Features:
- All the standard CM10.2 Features are enabled
- New, custom toolchain for improved code optimization and better performance
- More to come
EPRJ-SleepLock (LP Lock)
Start by firing up a terminal (Terminal emulator or ADB), then.. here's how to use it:
Activate LP lock: echo "1" /sys/eprjmanager/power_lock
Deactivate LP lock: echo "0" /sys/eprjmanager/power_lock
Changelog:
Code:
20131008:
- CM repos synced
- New EternityProjectOS performance optimizations
- Built with GCC 4.8.x
v0.15
- CM repos synced (29/10/2012, 1.00PM GMT+1)
- OpenGL performance improvements
- libc performance improvements
- skia performance improvements
v0.08
- CM repos synced (31/08/2012, 5.00PM GMT+1)
- libcore performance enhancements
v0.07
- CM repos synced (24/08/2012, 11.00PM GMT+1)
- Call recording is now possible
- WiFi problems gone (along with new kernel)
v0.06
- CM repos synced (18/08/2012, 12.00AM GMT+1)
- Launcher settings now customizable
- USB Mass Storage transfer speedup!
- Camera: solve FC when switching to camcorder mode
- Other speed tweaks
- Some battery tweaks
v0.05
- Proprietary binaries updated to hTC 2.17.401.2
- Introduce experimental USB pendrive automount (for USBHost)
- Solve the crash in Settings -> Storage (remember to flash the latest kernel)
- Solve the inverted-axis problem that was happening in some apps (like camcorder)
- A little faster
v0.04
- CM repos synced (10/08/2012, 11.00AM GMT+1)
- WiFi Wakelock (de)activable!
- Included EternityProject SleepLock (no widget at the moment)
- Performance enhancements
v0.03:
- CM repos synced (06/08/2012, 8:40PM GMT+1)
- User customizable HW buttons!
- User customizable brightness settings (light sensor)
v0.02:
- CM repos synced (05/08/2012, 11:40PM GMT+1)
- skia enhancements (should give less overhead on 2DHW)
v0.01:
- First release.
Screenshots can be found following the download link.
How-To:
1. Copy the CM10.2-EPRJ and GApps packages on your internal memory
2. Flash CM10.2-EPRJ, then flash GApps
3. Make a complete wipe (erase cache and userdata)
4. Flash the kernel package
5. Reboot
6. Enjoy!
If you have WiFi problems, make sure you've flashed the latest EternityProject Kernel for CM10-EPRJ prior complaining!
Do I have to make a full wipe if coming from a previous version of this ROM?
Usually, you only have to wipe your CACHE, unless specified.... but I can't assure you at 100% that you won't have any problem. You shouldn't, but we're living in a world where the only sure thing is that sooner or later we will d.. ehm... understood?
Various:
- Have you got any problem? That's probably because you didn't do a SUPER-UBER-WIPE when coming from CM10/10.1 or Sense.
So, what to download?
You'll find everything here: EternityProject Website
Important: Flash our kernel AFTER flashing the ROM!
Hey, and what about GPL?
Search on my GIT: HERE
Or on our new self-hosted GIT: http://pubgit.eternityproject.eu
Thanks to:
The CyanogenMod Team for the CM base sources!
That said, enjoy!
The EternityProject Team Manager & Main Developer,
--kholk
Awesome, Thanks!
awesome！！！！！！！:good:
Cheers for this, downloading as I type (download seems rather slow though, 40min remaining bu I guess your server may be getting hammered at the moment?)
I'll report back.. thanks again
first page!! Congrats on new rom
No bugs sounds good to me! Right onto it! No need to flash boot.img???
@StomUK
Yeah, it is... and also, the downloadserver isn't that much fast. You should anyway be able to download at 400KB/s with normal load usually....
@KLUVJ
Thanks!
@sottyc
If you've flashed one of the EternityProject Kernels listed on the download page... no, you don't need to flash the boot.img found in the CM ZIP!
sottyc said:
No bugs sounds good to me! Right onto it! No need to flash boot.img???
Click to expand...
Click to collapse
kholk said:
Recommendations:
For achieving the BEST performance on CM10-EPRJ, make sure to use our EternityProject Kernel 3.4 for HTC One X: I'm developing it always using our kernel and I'll also make this ROM to use the unique features (like ION) that only our kernel is bringing at the time of writing this (04/08/2012)
The EternityProject Team Manager & Main Developer,
--kholk
Click to expand...
Click to collapse
If you are already running his latest kernel then I am assuming that you won't need to flash the new boot image, otherwise yes, you will need to do that also (personally I just reflash boot images and roms each time anyway to make sure that they are running as the developer has created them for finding bugs (or hopefully not finding bugs!))
No bugs !No freezes !That to on 3.4 kernel!!Brilliant !This might overshadow the new HTC release!!!
I am alone with no Wifi ?
-JFK- said:
I am alone with no Wifi ?
Click to expand...
Click to collapse
Did u do a superwipe before flashing?
can anyone help me how to flash the kernel in mac?
i typed sh flash_osx.sh in the terminal but it doesn't flash even tho' i get a series of text saying its complete.. but full of errors..
thnx in advance.
I believe if you put some cool screenshots you will have more downloads
and also a feature list is mandatory
sounds nice; unfortunately the additional fixes, which are necessary for being able to build this, aren't given in your sources. device, vendor and kernel tree aren't sufficient for compiling. you can make a list with these fixes pls? *g*
So, if you say there a no bugs...you've fixed all the stuff which is not working on the other CM10 roms?
- Occasional soft-reboots with GPS On + Facebook ( http://forum.xda-developers.com/show...postcount=2184 )
- WiFi direct doesnt work
- MHL output is rotated incorrectly to portrait in horizontal mode (but workaround added since alpha 8 for hw decoded videos/youtube. Use bsplayer from playstore, almost all videos play with it in correct rotation in hwoverlay)
- No FM radio app in ROM. But Spirit FM works from market (it's commercial!)
- USB storage copies slower than normal
- Some paid apps loses settings/acconts due to this android jellybean problem: http://code.google.com/p/android/issues/detail?id=34880 Solution is to backup with Titanium Backup and restore to internal memory, not to sd
- You tell
Click to expand...
Click to collapse
i wonder is multitouch in games that cm10 suffers from fixed
nish77 said:
Did u do a superwipe before flashing?
Click to expand...
Click to collapse
+1 no wifi.Did full wipe before flash...
no wifi too.
yeah~~~a feature list? thank you for the works!
nteeb said:
+1 no wifi.Did full wipe before flash...
Click to expand...
Click to collapse
Probably a Drivers problem, we just have to wait he's working on
CyanogenMod (pronounced /saɪ.'æn.oʊ.dʒɛn.mɒd/) is an enhanced open source firmware distribution for smartphones and tablet computers based on the Android mobile operating system. It offers features and options not found in the official firmware distributed by vendors of these devices.
http://wiki.cyanogenmod.org/w/About
Code:
#include
/*
* 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.
*
*/
Instructions
1. Download the zip(s) - firmware and Google Apps additional package (optional)
2. Download and flash a compatible recovery
3. Boot into recovery
4. First Flash: Wipe data, system & cache partitions and flash firmware --Afterwards you can dirty flash.
5. Flash Chainfire's SuperSu (required to have root)
6. Optional: install the Google Apps additional package
7. Reboot and profit
Known Issues:
NFC doesn't work.
You tell me.
NOTE!!! THIS WILL FORCE ENCRYPTION ON THE PHONE!!!
This ROM will encrypt your storage. I am only following CM's guidelines. If you don't want encryption, please flash with the ROM a different kernel that allows for encryption.
Once you have booted up on this ROM, if you want to go back to KitKat, you will first have to transfer the contents of your internal storage and SD Card to a PC or you will lose everything you have there.
2014-01-04
cm-12-20150104-UNOFFICIAL-hlte.zip --> DOWNLOAD
MD5: 03336a6af71afafb4024a5922ab0cb32
2014-01-05
cm-12-20150105-UNOFFICIAL-hlte.zip --> DOWNLOAD
MD5: 076d86556717117f471327a5f563e831
NEEDED PACKAGES
TWRP: http://forum.xda-developers.com/showthread.php?t=2467001
All TWRP recoveries for HLTE are here
This ROM works with any bootloader. It's the recovery, TWRP, that has to match the bootloader version in order for the device to correctly boot up.
GAPPS: https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053 ---> Direct Download Link: http://download.chainfire.eu/641/SuperSU/UPDATE-SuperSU-v2.40.zip
All current and previous builds, kernels and fixes can be found HERE
Thanks to CyanogenMod team and Google
CHANGE LOG:
This list is not exhaustive. For a complete list of all merged changes please go here
2014-01-03: First build
- mtp fixes
- SElinux fixes
- Superuser: Don't set root access as a default fallback option.
- Buttons: set HOME wake key default as disabled
- ActivityManager fixes
- Fix null pointer exception - should fix most of the FC problems
- Lots of framework fixes
- QuickSettings: Add long click support
- Sepolicy fixes
- root disabled by default
2014-01-04
- Translations
- New terminal app
- Replace app-based superuser with the PG version
- Remove Superuser app
- SEpolicy fixes for new superuser
- su: Remove the superuser app
- su: Add Root access app-ops control
- su: Add an indicator when a 'su' session is active
- appops: Add support for SU
2014-01-05
- Many fixes. Too long to list here.
First?! Upload faster plz
waywardfrantz said:
First?! Upload faster plz
Click to expand...
Click to collapse
Ready!
Any special mods to this ROM?
Sent from my SM-N9005 using XDA Free mobile app
bigstunta101 said:
Any special mods to this ROM?
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
This is pure CyanogemMod 12 Android Lollipop. Any mods that work for CM 12 will work on this ROM.
Does NFC work on this rom?
troc240 said:
Does NFC work on this rom?
Click to expand...
Click to collapse
NFC doesn't work yet on any CyanogenMod ROM for the T-Mobile Note 3.
I just flashed this and it booted right away O____O
WOW. Thank you. Will await other user feedback, but definitely subscribed to this thread! Cheers and happy new year!
iynfynity said:
I just flashed this and it booted right away O____O
Click to expand...
Click to collapse
Does WIFI work?
10507 said:
Does WIFI work?
Click to expand...
Click to collapse
Yes, it works fine. Bluetooth too. Only NFC is not working.
Also the temperature and humidity sensors work OK.
T-Mobile Wifi Calling work on this ROM?
escavi said:
T-Mobile Wifi Calling work on this ROM?
Click to expand...
Click to collapse
I'm not sure if I just can't see it or there's no wifi calling for this ROM. I haven't tried that before.
Anyway, so far I haven't experienced any major issues with the ROM after using it for hours. Wifi works perfectly for me compared to the other Lollipop ROMS out there.
One minor issue, that may bother other people including me, is that the syncing of the Android browser bookmarks isn't working for this ROM. I only use the Android browser because of the Pie controls so I'm a little sad about this issue. Hope this gets fixed in the future. Thank you!
iynfynity said:
I'm not sure if I just can't see it or there's no wifi calling for this ROM. I haven't tried that before.
Anyway, so far I haven't experienced any major issues with the ROM after using it for hours. Wifi works perfectly for me compared to the other Lollipop ROMS out there.
One minor issue, that may bother other people including me, is that the syncing of the Android browser bookmarks isn't working for this ROM. I only use the Android browser because of the Pie controls so I'm a little sad about this issue. Hope this gets fixed in the future. Thank you!
Click to expand...
Click to collapse
Camera and video recording working for you as well?
10507 said:
Camera and video recording working for you as well?
Click to expand...
Click to collapse
Yes, both of them works. Front face camera works too.
An other LP ROM is coming, I am going to try, thanks.
Sent from my SM-N900T using XDA Free mobile app
New rom 2014-01-04
New ROM 2014-01-04 posted on the OP.
Enjoy!
miscom said:
CHANGE LOG:
This list is not exhaustive. For a complete list of all merged changes please go here
2014-01-03: First build
- mtp fixes
- SElinux fixes
- Superuser: Don't set root access as a default fallback option.
- Buttons: set HOME wake key default as disabled
- ActivityManager fixes
- Fix null pointer exception - should fix most of the FC problems
- Lots of framework fixes
- QuickSettings: Add long click support
- Sepolicy fixes
- root disabled by default
2014-01-04.
- Translations
- New terminal app
- Replace app-based superuser with the PG version
- Remove Superuser app
- SEpolicy fixes for new superuser
- su: Remove the superuser app
- su: Add Root access app-ops control
- su: Add an indicator when a 'su' session is active
- appops: Add support for SU
Click to expand...
Click to collapse
Do we still need to flash the SU if we are starting with 1/4 build? Also the only recovery I found via the link shows "4.4" at the end. Is that the right one? From Sept 29th?
Edit: the mirror for recovery is 12/22. Still shows 4.4
bobbyphoenix said:
Do we still need to flash the SU if we are starting with 1/4 build? Also the only recovery I found via the link shows "4.4" at the end. Is that the right one? From Sept 29th?
Edit: the mirror for recovery is 12/22. Still shows 4.4
Click to expand...
Click to collapse
Yes, as far as I know you'll have to flash SU to get root because root is not completely written as it was in CM11. I use Cyadelta to flash custom ROMs because it allows me also flash other zip files. It simplifies flashing. Then once CM nightlies are available it will will download the deltas for every new build and not the entire ROM.
In regards to 4.4 it depends. If you already have the latest bootloader from Samsung, i.e. you flashed any Samsung factory ROM version 4.4.2 then you need a 4.4 TWRP recovery to match the bootloader.
This ROM works with any bootloader. It's the recovery, TWRP, that has to match the bootloader version in order for the device to correctly boot up.
CyanogenMod 13 For F320
Please NEVER upload this rom to other forum or file share service.
Please contact me before modifying this rom.
Originally Posted by cyanogen
Code:
#include
/*
* 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.
*/
Click to expand...
Click to collapse
Recommend Recovery : TWRP 2.8.7.X or above
Working on CM13
- Cellular(Call&Data)
- Wi-Fi
- GPS
- Sensors
- seLinux
- SD Card(w/ exFat FS)
- and all features except below
Not Working on CM13
- VoLTE
Known Bugs
- Not reported
Change Log
- Sep 4
* Merge latest kernel and device sources from cyanogenmod
- June 12
* Merge latest kernel and device source
* Fix battery icon width
- May 15
* Kernel Timer changed(100hz to 300hz). it increases performance without more power costs.
* TCP buffer define location changed(init -> overlay)
- Apr 10
* Fix Lockscreen's shortcut starts apps(camera, googlenow, etc...) while touch other area.
- Apr 3
* increase speak volume from F320K Stock Lollipop's mixser_path.xml
* merge d802 kernel, g2-common source.
- 14 feb
* fix media playback error when seek.
* change default governor to ondemand and customize for msm8974 ap.
* change iosched on init.g2.rc ( bfq -> fiops: for more battery)
* fix invalid number.
- 27 Jan
* sync latest cyanogenmod repos. system is more stable.
- 10 Jan
* Update init.g2.rc
> android 6.0 has changed storage mount like externalSD or USB OTG.
I change storage mount(fstab and etc...). Now can Boot!
* Change Default Governor: SmartassH3
* Change Default IO Sched: fiops
* update power_profile for f320*
- 8 Jan
* rebase all source
- 25 Dec
* Add IOSCHED, CPU GOV, ExtSD, EXFAT
Installing Guide
Precondition :
KK Bootloader and LP BootStack are required in order to install this ROM.
You may also need new Modem for working radio
1. Flashing LP BootStack (If upgrade old version, this is not needed)
1-1. Wipe factory reset, Wipe /system (IMPORTANT, Never Dirty Flash from CM-12.1 or others.)
2. Flashing Modem(If you first install)
3. Flashing CM13
4. Flash Gapps
5. Reboot
Source Code
Github : https://github.com/whdgmawkd
android_device_lge_f320, android_device_lge_g2kr-common,android_kernel_lge_msm8974_kr
Special Thanks to
CyanogenMod (Rom Source)
TheMuppets (CM vendor)
lg-devs (LP BootStack)
mpeople (KitKat Bootload for each F320S/K/L)
Download Link
I'm not fluent in English. Sorry for my poor English.
Modem : https://www.androidfilehost.com/?w=files&flid=46208
It was included KitKat Bootloader and LP Modem and etc.
Stable ROM : https://www.androidfilehost.com/?w=files&flid=46198
Download "cm-13.0-20160903-UNOFFICIAL-f320.zip"
Customized ROM by @pipyakas : https://www.androidfilehost.com/?fid=24591023225176446
* Changelog
- Compiled with UBERTC 5.3 for the rom and Architoolchain 4.9 for the kernel
- -O3 optimization flag, I'm working on further optimizations like graphite or full archidroid optimizations
- 3.4.112 linux kernel, I added 2.65ghz CPU OC and 650mhz OC, for the kernel I'm trying to implement zram and fastcharge, also I'm looking to modify ondemand governor for better balanced between performance and battery
This is my experimental build with some changes I like, everyone feel free to test it and give me feedbacks, also any advice would be awesome as I only have a month of experience in android building
Gapps : Use anything support 6.0.X. Recommend OpenGapps.
Merry Christmas.
Thank you for your work.
I shall test it. if it has the same bug i have with another marshmallow rom, i will re use the report i did on the prev rom. wish me luck
It won't boot on my F320L. It gets stuck at LG logo. My steps: Wipe data, cache, system, dalvik. Install F320L_KK_bootloader_plus_LP_bootstack.zip. Reboot to recovery. Install ROM. Is it supposed to boot on F320L?
wont boot on f320k. tried from Vanir 6.0.1 (f320 also) and didn't work. there is no reason for me to flash a bootloader/stack because I am on marshmallow. Please help
Added to index
[INDEX][LG G2] ROMs, Kernels, Guides and more
adriannxda said:
It won't boot on my F320L. It gets stuck at LG logo. My steps: Wipe data, cache, system, dalvik. Install F320L_KK_bootloader_plus_LP_bootstack.zip. Reboot to recovery. Install ROM. Is it supposed to boot on F320L?
Click to expand...
Click to collapse
For F320S/K
somboons said:
For F320S/K
Click to expand...
Click to collapse
Previous versions cm12.1 booted and worked fine. It should work on F320L outside Korea.
did anyone manage to boot on this rom? mine won't go past the LG logo
f320s .The same as yous.can't boot with LG LOGO .
liusi522 said:
f320s .The same as yous.can't boot with LG LOGO .
Click to expand...
Click to collapse
I'm Hoping @parkjh0821 Senpai can fix this
planning on fixing the fact it won't go past the LG logo ? don't worry, take your time its usually like this on all first builds XD
I'm sorry for late.
I found It cant boot because rom has critical problem. but I dont know why it cant boot.
boot image is OK. maybe overlay(ExtSD Patch) make this problem.
but I dont have enough time to build new cm13.
it will take long time to release new build.
parkjh0821 said:
I'm sorry for late.
I found It cant boot because rom has critical problem. but I dont know why it cant boot.
boot image is OK. maybe overlay(ExtSD Patch) make this problem.
but I dont have enough time to build new cm13.
it will take long time to release new build.
Click to expand...
Click to collapse
It's not your fault. It's just your job no return.Just Do your own thing.
When you have a new building in your free time, I'll test.Thanks
its ok. take ur time. aslong as in the end, we will have a booting cm13
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
parkjh0821 said:
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
Click to expand...
Click to collapse
Continue trying, good luck!
parkjh0821 said:
new version released.
but still cant booting.
need more tester and feedback.
my device cant boot this rom with KK bootloader.
stuck at bootanimation and /data partition has no files, only folders
Click to expand...
Click to collapse
Thank you for your work.I will test tomorrow .
tested
wont go through the cyanogen mod boot animation
DISCLAIMER
Code:
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.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Steps to install:
(0. Install any 6.0 rom)
1. Factory reset
2. Make sure you format /system and /data to ext4 for the install
2. Install ROM zip, you will get a warning about partition size change of system if its the first time you flash, just flash it a second time to confirm the change, this will erase your data partition!
3. Please do NOT install Gapps (you can still do it, but at your risks)
4. Reboot
5. Wait for a long time
Known Bugs:
- First boot is slow
- RIL sudden crash (?)
- Webkit render issues with the latest cm14.1. It will be fixed in the next build.
- CM's FileManager is bugged
Features:
- Stock Cyanogenmod 14.0
- Dirty CoW patched kernel (anyone cares ?)
- kernel built with GCC 6.2.1 with -03
- F2fs support on /data but not on /system
- Bigmem enabled (no cma for now)
- sdcardfs support to come someday
- Zram enabled
Please note that this rom is not ready for daily usage yet, it's an alpha.
Downloads:
Android 7.0:
http://www.mediafire.com/file/5d1fdr0f75rywml/cm-14.0-20161120-UNOFFICIAL-galaxysmtd.zip
Android 7.1.1:
http://www.mediafire.com/file/xfcjvn1y1vjwwpu/cm-14.1-20161223-UNOFFICIAL-galaxysmtd.zip
I will provide mirrors later if needed.
Please check the MD5 !
094fa2133073f22cea28e80d18a628e5
HUGE thanks to @xc-racer99 for his AMAZING work on his variant, without him, this woudn't have been possible at all.
XDA:DevDB Information
CyanogenMod 14.0, ROM for the Samsung Galaxy S I9000
Contributors
Coldwindofnowhere, xc-racer99, sooti
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Alpha
Created 2016-10-28
Last Updated 2016-12-23
Reserved
Changelog:
23/12/2016
Android 7.1.1 r6
No more crashes due to the graphic driver
Working ril (except data on the first boot apparently ?)
Fixed internal storage issues
Updated kernel
Latest TWRP (without their new app, tell me if you want me to add it back)
20/11/2016
Latest CM 14.0
As people wanted, cmc is back
Tweaked art settings (lag should be gone)
Fixed video recording
Fixed MTP crash
Fixed adb authkey issue
Disabled SDcardFS
More stable RIL (but there are still issues with 3g)
28/10/2016
Initial release
Reserved
FAQ & tips :
Where is SuperSU ?
You don't need to flash SuperSU, just enable it under the Developer options.
How to change Bigmem modes ?
You can change it in advanced parameters>Bigmem
What are the best schedulers/governors/...
That's up to you, personaly, I like the combinaison of smartassV2 and bfq.
But ... how to change them ???
You can use Kernel Adiutor or any other app like that.
When will you release the next build ?
Don't ask for ETA ..... and wait.
Something isn't working, please fix it, please PLEASE
Logcat. No logcat == no fix.
If you don't know how to logcat properly, read this.
My phone is bootlooping ,what can I do ?
Pull battery and restart. Also don't forget to do a factory reset before flashing this rom.
Can you add X feature on your rom ?
No. I wont add additional features, this is stock cm. The only thing I might add is signature spoofing support.
Here are a few additional tips to get the most of this rom :
Format /data in f2fs in TWRP
OC your cpu if it can handle it
Use Bigmem
Don't install unnecessary apps
Remove apps from startup
(Wait for the next build)
Wow!!! It is impossibly! Big thanks!!!
+1
:good:
Link is up, make sure to check the md5sum and tell me if you experience issues.
Logcats appreciated !
Ok, just tested it. Was compared with AOSP 7 from x-racer99.
Seems CM14 more laggy in games. Not so smooth like an AOSP. But problem probably is not in the kernel. Cause i was also use x-racer99 kernel on your CM14 rom. Look at this videos with Mega Jump game:
https://youtu.be/ueyjuPu3BgA AOSP rom by x-racer99
https://youtu.be/FWbCNKZdAdE Cyanogenmod 14 rom with x-racer99 kernel.
Second video is not so smooth with a lot of jerks. May be problem in low memory killer settings, or GFX drivers, or V-Sync, or build.prop tweaks, i do not know.
Also i prefer CMC instead Voodoo Color. Because VoodooColor have two bugs since android 2.x.x. It is yellowish tint of all screen (CMC have more right white balance) and green bug on low backlight with high gamma settings, look at this video:
https://youtu.be/gkP7VgWbTlY
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
About CMC, you can tweak voodoo by yourself, but yeah if many people want me to switch to CMC, I will do it.
Coldwindofnowhere said:
Thanks for the feedback, I guess that's related to various properties in build.prop. I will experiement a bit to see if I can improve this.
Click to expand...
Click to collapse
You can just download Subway Surfer from market or another place and try to make run this game more smoother. Some times Subway Surfer have bad responce on touch and can hung up after long play. Also can try this on Mega Jump or other dynamic game.
Thank you!
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
P.S. Issue with MXplayer was resolved by itself after reboot phone.
M1n3cr4f7.G4m35.2015 said:
Ok, one question. I know it takes forever on the first boot, but, how long does it take? I've been waiting almost 45 minutes for it...
Click to expand...
Click to collapse
Um pull off the battery, start the phone again. Got this issue once but no idea why.
jupiter5700 said:
First boot was around 15 - 20 minutes for me.
Bugreport:
-not all apps correctly work with sd-card. I cant scan cards by MXPlayer for example.
- camera can't save videos.
What are the libs used in the rom? Pathed for bigmem or regular?
Click to expand...
Click to collapse
Bigmem patched, I haven't tested 720p videos tbh.
This rom can run on samsung wave?
thinhx2 said:
This rom can run on samsung wave?
Click to expand...
Click to collapse
I haven't tried but as it's really similar to the i9000, you should give it a try.
Coldwindofnowhere said:
I haven't tried but as it's really similar to the i9000, you should give it a try.
Click to expand...
Click to collapse
Screen is different. You think driver display of i9000 can work on wave?
thinhx2 said:
Screen is different. You think driver display of i9000 can work on wave?
Click to expand...
Click to collapse
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Coldwindofnowhere said:
Um having a quick look at https://github.com/Badadroid/android_kernel_samsung_aries, looks like it wont be possible, additional kernel drivers are needed.
Click to expand...
Click to collapse
You can public your kernel for aosp 7 of ss s1?
thinhx2 said:
You can public your kernel for aosp 7 of ss s1?
Click to expand...
Click to collapse
https://github.com/Coldwindofnowhere/android_kernel_samsung_aries/commits/staging
No way man, nice work
Android 7 N for s1
Ejgjskfkcisvjj hahah
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.