Develop Bugs

[Kernel][7.1.1] SunKernel Pedigree Z5 for LineageOS [sumire]

A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30

Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse

Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)

Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I

Thanks, I hope you don't forget dsds variant.

It is a pleasure to have SunKernel in LineageOS.

Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.

Flashing lineage and kernel, looking forward to try it
Thanks for upload

s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload

Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.

Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update

zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.

stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)

In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install

zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.

actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?

@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.

L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks

zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse

L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse

[TWRP][3.2.1-0][Nougat & Oreo] Teamwin Recovery for Nokia 3

*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:

i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1

Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.

Also please can someone flash/test this twrp so i can see does it work for others.

System and Data can be backed up and restored on oreo with this twrp?

Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It

ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you

Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.

Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.

Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !

Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.

Can this work on Nokia 1 with Android Oreo 8.1?

abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.

SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928

Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:

Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad

Can i use for Nokia 3 locked bootloader???

How to install ?

please Post Nokia 3 TA1032 Android 8.1 Custom recovery

Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?

[RECOVERY][Android 10][Stock/Custom ROM][XZ2/C/P/3] TWRP [UNofficial]

Central project page
https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305

11.06.2020
Switch to TWRP 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.A.2.1
Now both twrp should work without a ROM being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse

13.06.2020
Thanks to the fixes in 3.4.0 we got now a TWRP with the following enhancements for STOCK and SODP:
- This TWRP will work with future 10.0 ROMs, you don't need a new build matching the security patch level of your ROM.
- You can install this TWRP again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
Please test and report back if you got any touch / decryption problems.

14.06.2020
Reuploaded the stock TWRP with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse

15.06.2020
Reuploaded the STOCK TWRP for the XZ2 Premium with a completely fixed touch.
Click to expand...
Click to collapse

Hello i need some help. Can somebody help me out
Sony xz2 premium model H8166.
Im unlock the boot loader. But twrp Don t want to install.

您的ROM是否基于AOSP？系统是否附带简体中文，因为我是中文用户
----------
MOD EDIT: English Translation Below
Is your ROM based on AOSP? Does the system come with Simplified Chinese, because I am a Chinese user

N920T said:
Is your ROM based on AOSP? Does the system come with Simplified Chinese, because I am a Chinese user
Click to expand...
Click to collapse
It is a recovery, not a ROM.
But I used the OmniROM 9.0 buildsystem to compile it.
It should contain the chinese language

Need I unlock the bootloader first?

[CLOSED][SHARE] Lineage 18, Android 11 for Pixel 4a Sunfish

This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system

Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.

liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.

This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.

ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.

Does this support signature spoofing?

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS

ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom

EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No

TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.

ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G

ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available

New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.

TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?

Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.

Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.

TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources

Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?

Development [TWRP Recovery] TWRP recovery for SM-F926B based on CVCA

Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)

So just push it as the recovery to the active slot via adb?

Breaks dex? If Not its kompatible with latest one ui?

It doesn't break dex, you can backup your recovery partition, it should be compatible with latest Android, since recovery is contained

Mikowitsch said:
So just push it as the recovery to the active slot via adb?
Click to expand...
Click to collapse
Yes, the usual way works fine

is the link down.. i cant download it

miman04 said:
is the link down.. i cant download it
Click to expand...
Click to collapse
Fixed !

Azkali said:
Fixed !
Click to expand...
Click to collapse
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?

miman04 said:
Tq sir .. can i get a simple guide on how to get the TWRP works on my fold 3. im currently on a rooted fold 3 Android 13.
Should i use odin and put in AP then flash rite away or i use fastboot?
Click to expand...
Click to collapse
Yes in Odin putting recovery.tar in AP will work fine ^^

i cant download recovery and vbmeta

Azkali said:
Hi folks
Since some of you asked me to make another thread for my TWRP build, here you go, the kernel is based on EWB5 (A13) but is compatible with all currenlty released Android versions.
WARNING/DISCLAIMER: Since the outer display isn't shut down this build can cause irreversible screen burns if used extensively. As such I take no responsabilities if you damage your device while using my TWRP build (and/or) other projects that may suffer from the same issues.
Edit: after some time the "screen burn" disappeared, so it seems that it's just a remanent image. In doubt stick to the warning.
TWRP Image
Sources:
Kernel
Device Tree (Forked from @shadow-of-leaf Z Flip 3 DT)
Click to expand...
Click to collapse
404 page on TWRP and VBMETA

Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon

ROM-PacMe said:
Using the DT from Azkali to build a new Release of TWRP, i'll make a new Thread for that
Thanks so much @Azkali for your Device Tree, i hope to help you soon
Click to expand...
Click to collapse
I have a newer TWRP, maybe instead of a new build we could figure something out together
Join the discord and ping me there, I'll be available later

Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!

ROM-PacMe said:
Release q2q-5337227142 · bm0x/twrp-actions-compiler
Recovery for q2q
github.com
based on minimal-twrp branch 12.1
and uses the DT from @Azkali
enjoy!
Click to expand...
Click to collapse
is it compatible with SM-926B?
q2q is SM-926B?
google didnt know anything about "q2q samsung"

Can you try, If not working, only re install the recovery stock and vbmeta too

The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
the revision is a random number gived from Github Actions, nothing more my friend

thewayofwright said:
The other thread cites CVCA as a basis, but all I can find in the TWRP revision q2q-5337227142 in each. Is there an older build out that works better w/ BL 1, not 3?
Click to expand...
Click to collapse
only use the vbmeta and recovery tar of my own github releases, let me any update, ok?
i see soon any bug to help to fix