yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Compact Android Development] tomascus:
You must be on stock kernel to use locked bootloader. This is why they say custom kernels only works on unlocked bootloaders...

Why bother with restoring DRM keys when this kernel apparently has a DRM fix included ?
[Xperia Z3 Compact Android Development] ShadowElite:
Well for me it works fine, maybe I can add it on other version but for now It isn't on my ToDo list, also my personal experience with intelliplug is bad.
[Xperia Z3 Compact Android Development] Cirra92:
Yea, I understand that, that's the reason why I asked, different devices, different setup, it would be nice to have that included as well, you won't remove the ThunderPlug anyway, just add this. Thanks in advance :)
[Xperia Z3 Compact Android Development] fandan:
I am in the same situation....can I ask you how did you solve?

Thanks
[Xperia Z3 Compact Android Development] Strmy:
My bootloader isnt unlockable, can still unlock it and flash this kernel?
[Xperia Z3 Compact Android Development] panzerox123:
No you can't
[Xperia Z3 Compact Android Development] Robot76:
So if you get "Bootloader Unlock Allowed = No"

Then you could try going to the 'Sony Service Centre' and ask them if they can do it for you... If they are kind enough to do it for you, then they will explain this will indeed terminate your warranty, and charge a fee for the service...

**But if you're unsure still of your phones status, go here:

https://xdaforums.com/showthread.php?p=68532096

A.R.I.S.E Z3C Phh.superuser Magisk Substratum
[Xperia Z3 Compact Android Development] fandan:
Hello, I am currently using EliteV3 and AOXP 1.5.2, and I am completely satisfied of general the behavior and battery life of the phone, but the camera quality seem quite worsened.

I am now trying to find out if it is a matter of DRM keys, lens/hardware, my eyes, Cyberian (as a matter of fact camera performs poorly also with good light, and I firstly noticed it after flashing the rom, and before unlocking the bootloader).

I have a couple of questions about the fixing of DRM keys:

Checking the DRM status in the service menu I find:

Marlin unknown error active

Ckb unknown error active

Widevine unknown error active

All the other keys are ok and active

Does this mean that the DRM keys have not been fixed?

In case, to fix them keeping this kernel I understand I should:

Flash stock kernel

Flash corresponding stock rom (is a pre-rooted one OK?)

Full wipe

Re-flash elite kernel

Is this correct?

….well, this is the first time I am trying to mod my phone. All the guides and the the info I could find here are really remarkable, thank you
[Xperia Z3 Compact Android Development] panzerox123:
Is this Kernel gonna have a new update? Or is V3 the last? Just a question... you dont have to answer it :)
[Xperia Z3 Compact Android Development] Robot76:
It's frustrating isn't it, because of the awesomeness of the ShadowElite's cool Kernel!

Want moar awesomeness from HRH ShadowElite...

[emoji7]

A New Hope...

I'm on custom Nougat now, and miss the v3 very much...

A.R.I.S.E Z3C Phh.superuser Magisk Substratum
[Xperia Z3 Compact Android Development] panzerox123:
I know. Carbon isn't stable yet. Will shift as soon as it's stable. :)
[Xperia Z3 Compact Android Development] FernandoFaria:
Hi,

I'm using AOXP 1.5.7D by [MENTION=6948461]panzerox123[/MENTION] and I would like to flash this Kernel.

Since I'm new about rooting and flashing I have some questions:

1. To apply this kernel I just have to download the zip (V3) and flash it using TWRP?

2. Do I need to use that profile zip from Robot76? If so, how can I flash it and use it?
[Xperia Z3 Compact Android Development] x_one:
This kernel is for stock FW..
[Xperia Z3 Compact Android Development] fluffi444:
Aoxp is stock... ?
[Xperia Z3 Compact Android Development] panzerox123:
Oh wow, I never saw your post. Yes, DRM is lost after you unlock bootloader. EliteKernel doesnt restore DRM keys. It only fixes DRM functions so you can use it in low light.

Also, for cyberian, It is a camera being developed singlehandedly. Give it some time :) mkdmc is testing the latest Cyberian right now with LP... He will be porting it to MM asap :)
[Xperia Z3 Compact Android Development] fandan:
Yes thank you, only after reading the post by Team EXR and Team THS I started to figure out this could work similarly to their mod.

I understand and appreciate; now for daily use I moved to the latest concept (rooted, drm fix), but I kept a full BU of the AOXP/Elite Kernel :) and I am ready to jump back and update in case of new releases of the camera.
[Xperia Z3 Compact Android Development] panzerox123:
I would love to make a ROM on concept, but unfortunately it doesn't work on my device itslef :eek: only with D5803
[Xperia Z3 Compact Android Development] reellamer:
Are this still the best/latest settings?

I can not load the .json in newest Kernel Adiutor from Playstore by putting it in /internal storage/android/data/(kernel adiutor folder)/profiles. These are the exported settings only. Couldnt find the file with search for filename. Think they want money for this...;)
[Xperia Z3 Compact Android Development] baudbox:
I don't know from when the post is, but here are the one used and still up to date from what I saw with users under AOXP

https://xdaforums.com/showpost.php?p=70369173&postcount=439
[Xperia Z3 Compact Android Development] reellamer:
Thanks for your answer, I will try them.
[Xperia Z3 Compact Android Development] ThePhoenixBird:
[MENTION=5900960]ShadowElite[/MENTION] could you check Magisk 11.1, it seems that it nows uses a different method ot inject selinux policies and it causes bootloops on this kernel
[Xperia Z3 Compact Android Development] ShadowElite:
I'm working on it, and more things, I successfully added magisk support, also I passed Safety Net, just be patient
[Xperia Z3 Compact Android Development] ThePhoenixBird:
This is amazing!:)
[Xperia Z3 Compact Android Development] Robot76:
[MENTION=6164641]baudbox[/MENTION] [MENTION=5894989]reellamer[/MENTION]

I'm glad you guys enjoyed the ideas about possible configurations for Kernel Auditor.

https://xdaforums.com/showthread.php?p=70369173

I have been using an Interactive Governor profile for myself using GlassFish1.2** by SoniCron.

http://xdaforums.com/showthread.php?p=64279886

(CPU Governor Tunables)

above_hispeed_delay 0

align_windows 1

boost 0

boostpulse_duration 0

go_hispeed_load 91

hispeed_freq 960000

Io_is_busy 1

max_freq_hysteresis 0

min_sample_time 0

target_loads 80 460800:70 652000:99 960000:90 1440000:99

timer_rate 40000

timer_slack 480000

use_migration_notif 1

use_sched_load 0

(CPU Boost)

Input Interval 1920

Core1, Core2 and Core3, all at 652000.

And Core4 leave disabled.

(I/O Schedulers)

I/O Schedulers at Zen (or Noop if Zen is not available)

Read-ahead 1024, RQ Affinity default 1 (2 is a possibility)

I/O Stat's off.

(Virtual Memory)

Swappiness 40

(Misc)

TCP Congestion Algorithm Westwood

Now if you have some better advice, please share your thoughts...

Now if you like this, please give a like on SoniCrons link above...

***The main reason for the above conservative settings, is because I am using this on a custom Nougat rom.

**almost identical, just a few tiny alterations, as our device is a bit different, and I am in no way an expert, just thought I'd share my settings

[emoji7]
[Xperia Z3 Compact Android Development] wmg.architect:
When I use this kernel, there is important app couldn't open, how to fix it? Actually it is banking local app here in Turkey. Can i fix this? Or it must be done by the app developers?
[Xperia Z3 Compact Android Development] panzerox123:
It's not the kernel. Bank apps usually don't work when there is root access detected. You can install magisk , it'll be supported by the kernel in v4
[Xperia Z3 Compact Android Development] wmg.architect:
Thanks for fast reply, The app was working good with every Rom I tested (with root and without it).

What is magisk? And what can i use it for?
[Xperia Z3 Compact Android Development] kuntiiiL:
[MENTION=4470081]topjohnwu[/MENTION] Could you please apply your offer in this thread?

With respect to OP who still working for the next version :oWho knows man this could be a, rare, chance for Z3C

-------------------------------------

EDIT

NOT necessary

, sorry for the trouble.

REASON: Elite Kernel v3 repacked very well by Magisk ZIP during flashing, so it's good to go which simply mean: Compatible.

CLUE: Perhaps DEV was trying to provide some sort of clue or something to that thread. Maybe boot.img that were repacked using "tobias script" will fail when Magisk ZIP repacks them back. Just a guess, I don’t really know.

https://xdaforums.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605/page224
[Xperia Z3 Compact Android Development] fluffi444:
[MENTION=5900960]ShadowElite[/MENTION]

Hey KernelMaster - What do you think to add this commit to next version?

https://github.com/DooMLoRD/android...mmit/48e7a70f3af70dfe26420a587a4e30fc20c7a9cf

It's for showing modified BootLogo (logo.rle) which we can change in ramdisk. Looks like otherwise changed logo.rle (in ramdisk) is not loaded.

Sure - not critical but nice to play with bootlogo - maybe we can make an custom one for EliteKernel

Thanks for you work! :good:

EDIT

Just for a little motivation i made short draft how it could look like... For sure also possible without Z3C branding - Maybe only XPERIA
[Xperia Z3 Compact Android Development] panzerox123:
+1 Looks pretty :victory:
[Xperia Z3 Compact Android Development] ShadowElite:
Good Idea thank you, I think Sony added this patch on code because I tried with Z3 logo on Z2 and it seems to work, anyway I like the logo that you send so talk with me on telegram
[MENTION=5900960]ShadowElite[/MENTION]22
[Xperia Z3 Compact Android Development] fluffi444:
I don't use telegram but I can support nevertheless.

Attached is the rle file acording to my img. Just rename it to logo.rle and put it to ramdisk (overwriting the existing)

I tried this already but it never showed up. That made me to do some reserach and found this commit finally...
[Xperia Z3 Compact Android Development] ShadowElite:
Ok I will take a look later, as you can see on my git I'm working on next version...
[Xperia Z3 Compact Android Development] fluffi444:
OK - take your time. Can do them also for Z2 and Z3 because EliteKernel is released for those models as well.
[Xperia Z3 Compact Android Development] snaky90:
Which version of magisk works with v3 ???
[Xperia Z3 Compact Android Development] panzerox123:
10.2 I guess... I'm not sure though
[Xperia Z3 Compact Android Development] FlintStoned-:
I'm using 10.2. The 11.1 version keeps crashing and rebooting the system on everything I do. I don't know if it's related to elitekernel.

You could try and let me know if it works for you.
[Xperia Z3 Compact Android Development] TASL:
I'm running Panzer's AOXP (1.58 on D5833) with Magisk 11.1 and Elite Kernel V3. I ran into the reboot problem and narrowed it down to enabling Magisk Hide and/or Systemless hosts (under Settings > Magisk).

Leaving those options unchecked I haven't had a single reboot, also have official Xposed installed.
[Xperia Z3 Compact Android Development] FlintStoned-:
Hi TASL, thanks, I will definitely try this. I have indeed Magisk Hide running. Thanks for the tip!

Edit: so far so good ;)
[Xperia Z3 Compact Android Development] Kocane:
Can anything at all be done with wlan_rx_wake wakelock? I know the old f*cker's been around always but over a course of 14hr it can keep a total of 1hr wakelock... and I've no idea why? I that time my longest partial wakelock is like 60s and caused by Nlp
[Xperia Z3 Compact Android Development] ted!:
I know, i know... ETAs are annoying but can you give a hint shadow?

Greets ted!

(ps if u still need testers... I'm on call!) ;)
[Xperia Z3 Compact Android Development] fluffi444:
[MENTION=5900960]ShadowElite[/MENTION]

Maybe you can take a look into this issue (or strange behaviour) regarding CPU hotplug.

Afrer fresh reboot all cores (except of course core 1) are shutting themself down, so that only 1 core in online.

But after first "screen off" a second core (here core 4) is online all the this as well. Deosn't matter if this was done by power button or automatic standby via system settings.

This is reproducible.

Tried it with 30 screen on time after reboot. All good. Hotplug keeps only one core online.

But with normal (1 min) screen on time hotplug keeps 2 cores (1 and 4) online all the time.

I mentioned this quite early in the thread already but I though as you are in the middle of new version its time to mentioned it again.

I use standard MPDes. hotplug and interactive gov.

Thunderplug reacts even more strange. Afaik thunderolug is designed for phones with two seperate CPUs - typically one little and one big.

Don't know if thunderplug is even usefull for our device...
[Xperia Z3 Compact Android Development] ShadowElite:
Thank you for your feedback, I will to take a look on it
[Xperia Z3 Compact Android Development] baudbox:
[MENTION=5900960]ShadowElite[/MENTION] I've read that you were working on Magick integration. It seems that a new version came this morning 2017.3.20 Magisk v11.5. I hope what you've done for compatibility will not be broken.

Keep going my friend! :fingers-crossed:
[Xperia Z3 Compact Android Development] lovermed:
Is there a way to tune screen sensitivity I have many ghost touches thank you
[Xperia Z3 Compact Android Development] panzerox123:
Isn't magisk 12 out? I don't know much about magisk... But I'm running it right now on aicp and it says V12
[Xperia Z3 Compact Android Development] jacfry:
I've managed to use Magisk 12 and pass SafetyNet check with v2 version of this kernel. I guess the improvements implemented in v3 are the reason for SafetyNet check failure. Is it possible to have a kernel with such modifications passing SafetyNet check? If yes, is passing SafetyNet planned for future developement?

EDIT: Tests made with debloated stock 23.5.A.1.291 as AOXP and Existenz didn't pass safetyNet check even with V2. I didn't check the Xperience rom.
[Xperia Z3 Compact Android Development] KUN1:
I'm runnig Magisk 12 with Elitekernel v3 and Xperience Rom and pass Safetynet test.
[Xperia Z3 Compact Android Development] fluffi444:
I really guess thats V3 is not the reason. Maybe it was just the fresh kernel flash of V2 what helped... Did you now tried to flash V3 again followed by Magisk?
[Xperia Z3 Compact Android Development] jacfry:
I'm pretty certain that it's the difference between V2 and V3. I can switch between kernels (flashing a kernel followed by Magisk) and pass safetynet with V2 and fail with V3. I'm not doing any wipes thou.

EDIT: Just to be sure wiping cache and dalvic doesn't change anything. Still can swith kernels back and forth passing safetynet check only with V2
[Xperia Z3 Compact Android Development] fluffi444:
Then it should be clear.

Best would be to wait until [MENTION=5900960]ShadowElite[/MENTION] comes with an update. As far as I know he's aware of magisk and stuff.
[Xperia Z3 Compact Android Development] jacfry:
Could you double check it? I've installed latest Xperience Rom and didn't pass SafetyNet test with v3 and v2. CTS profile missmatch just like with any other customized stock rom.
[Xperia Z3 Compact Android Development] KUN1:
Have you installed Xposed?

For passing Safetynet you have to disable the Xposed Magisk module...
[Xperia Z3 Compact Android Development] fluffi444:
Maybe you guys can install "Root Validator" and check (with each Kernel) the results....
[Xperia Z3 Compact Android Development] jacfry:
I didn't install Xposed and didn't uninstall/disable anything either
[Xperia Z3 Compact Android Development] ShadowElite:
Yeah, I fixed magisk support but I can't work on Kernel because the windows 10 partition was damaged and I should format my pc, now I have again my windows 10 partition working but I can't restore my backup of Linux with clonezilla idk why, so development is stopped right now...
[Xperia Z3 Compact Android Development] jacfry:
That seams to be the right approach:

I've found those differences:

Superuser binary detected in /vendor/bin/su with v3

Busybox detected in /vendor/bin/busybox with v3

Deleting those files solved the problem with SafetyNet check fail with EliteKernel v3
[Xperia Z3 Compact Android Development] fluffi444:
Exactly! That was my though as well. I guess that /vendor/bin/su is enough to delete... Even if su is not in ramdisk of EliteKernel it happend to me as well that su come up in /vendor/bin/su! If I remember correctly this is done by an (former) SuperSU installation (to SYSTEM)... But actually I don't know it....

Busybox (/vendor/bin/busybox) is part of Ramdisk and will be back after reboot! It's needed for integrated installation routine for TWRP (check in Ramdisk file "init")

But as I said. SU is the problem...

If you are interested in Kernel/ramdisk exploring - check wonderfull AIK from master [MENTION=4544860]osm0sis[/MENTION]

https://xdaforums.com/showthread.php?t=2073775

Well done!

---------- Post added at 06:59 PM ---------- Previous post was at 06:51 PM ----------

Sorry to her that. I guess most of us know that as well...HD crash or completly fu**ed up system... :eek:

We will wait in patience! Take your time... :good:
[Xperia Z3 Compact Android Development] jacfry:
Yes, /vendor/bin/su is the only reason for safetynet check failure but unfortunately it is restored during booting. Any hints how to disable it?
[Xperia Z3 Compact Android Development] fluffi444:
As I started with unmodified EliteKernel I used an simple init.d script to remove su automatcly during boot.

Now I use modified EliteKernel with removed TWRP, busybox, drm fix and suff... Better to say I use stock Ramdisk with EliteKernels zImage and modified this with PoC Tool to get full DRM back... TWRP is now only on FOTA Partition....

Actually I don't know exactly were this su comes from... But I can remember that it disappers when I used an updated busybox in Kernel... Is su in that specific busybox?

For test you can de-pack boot_z3c.img and delete busybox. But be warned that intergrated TWRP will not work anymore. So be on FOTA TWRP first...

What do you have in /vender/bin folder after reboot? besides of busybox and su?

EDIT

I de-packed EK again and there is init.vendor_ovl.sh. Looks like this has something to do with this all...

As faar as I know EKs ramdisk was modified with rootkernel tool from tobias waldvogel. Don't know but ramdisk looks like this.
[Xperia Z3 Compact Android Development] kuntiiiL:
Kernel features that better to be excluded, regarding 2017 cool developments, are at least these three below. Reason is that they are more related (somebody slap me if I'm wrong) to Operating System features and not pure governor stuff that directs hardware behavior.

1) TWRP: when placed in FOTA Partition it becomes user-side updateable also withstand ROM flashing

2) DRM fix: TA-PoC patch enable us to use original hardware keys on unlocked environment

3) Busybox: Magisk have built-in applets and switchable systemless

Maybe more. . . dm-verity, Sony RIC, init.d, kernel root. My only success with Android Image Kitchen (AIK) is debloating TWRP since the obvious file name. The rest just don’t have idea which is which; way beter if [MENTION=5900960]ShadowElite[/MENTION] share some guidance here:D Now for some fun stuff,

32-bit Performance

[PERF] results...

SliMM 3.8 ROM -vs- Concept 3657 ROM

ROM treatments: debloat & modified to balance features & deep sleep times

Kernel treatments: AIK, TA-PoC, Magisk 12

SliMM Kernel | EliteKernel | EliteKernel [PERF] -vs- Kernel12C [PERF]

Basemark II 2.0 : . . 1320 | 1220 | 1490 -vs- 1430

Basemark X : . . . . 13800 | 12100 | 14180 -vs- (fc)

Antutu 6.3.3 : . . . . 62500 | 60000 | 68800 -vs- 62900
[Xperia Z3 Compact Android Development] espaciosalter20:
could you provide your EK modified version?
[Xperia Z3 Compact Android Development] fluffi444:
Indeed buddy!

No problem... actually...

But because my kernel (in particular) is patched with PoC (TA included) its useless for any other Z3C. This works only on my phone because of my TA.img.

There are now two ways:

1) Send me your TA (this is save - I can do nothing with it as its only for your phone) and I patch it for you. But I will do this only for two of you. It's understandable that maybe others are asking and I have not the time to patch the whole day... understandable I think... ;)

2) And prefered: I make only stock Ramdisk (from original kernel.elf 291) with EliteKernel zImage (and two other needed small files) and the rest ist stock:

no RIC deactivation, no DRM fix, no BB, no TWRP, no kernel root, etc.... But init.d is possible if you want.... or even not... I still like init.d and use it...

With this boot.img you will go to PoC Tool and patch it for yourself with your TA.img and disable RIC - this is easy:

In PoC Tool say YES to "disable RIC" and say NO to "add TWRP" (if this question comes up - only if you have "recovery.img" in same folder)
[Xperia Z3 Compact Android Development] jacfry:
Based on hints by [MENTION=4962787]fluffi444[/MENTION] I've unpacked both kernels and repacked stock 291 with boot_Z3c.img-zImage from EliteKernel v3 using AIK. I've injected DRM keys form my TA backup with TA_POC and everything seems to work OK but the method below described by [MENTION=4962787]fluffi444[/MENTION] is easier and there is "more" EliteKernel in it
[Xperia Z3 Compact Android Development] fluffi444:
As this is still wonderfull EliteKernel I stay in this thread. [MENTION=5900960]ShadowElite[/MENTION]: if you want me to delete this or move this out of here... just call...

OK guys. Then I try to sum up the needed steps:

Just to remember: This procedure with TA PoC Tool makes only sense if you have an working TA.img backup!

This all can be done also with other kernel de-re-pack tools. But I will only refer to TA PoC Tool here.

Files/tool to have:

boot_z3c.img (stock EliteKernel), kernel.elf (stock Kernel 291), working TA.img, TA PoC Tool (https://xdaforums.com/crossdevice-dev/sony/poc-real-trim-instead-drm-fix-t3552893)

1) use PoC with boot_z3c.img and save following files from OUT folder to main PoC folder: boot.img-cmdline, boot.img-dt, boot.img-zImage.

Finish this PoC session. Don't mind about resulting kernel. It's not needed at this point.

2) use new session of PoC with kernel.elf and your (working) TA.img: Say YES to Disable RIC, say NO to TWRP (if it comes up) - DON'T PRESS KEY to FINISH at this point.. Keep this PoC session open.

3) Go to PoC folder and copy previously saved 3 files to OUT folder: boot.img-cmdline, boot.img-dt, boot.img-zImage - This is were you merge EliteKernel with stock ramdisk.

4) Back to CMD window and now PRESS KEY to repack kernel and finish PoC session...

5) Resulting Kernel is EliteKernel with (almost) stock ramdisk, RIC disabled, SELinux: permissive (as stock EK) , TA included and therefore FULL DRM support (as original!)

I left out init.d support here...

Reports are welcome :)
[Xperia Z3 Compact Android Development] jacfry:
Worked like a charm with no need to use AIK. Thanks
[Xperia Z3 Compact Android Development] espaciosalter20:
i get an error (failed remote:size too large) when i try to flash the new_boot.img created with ta_poc tool...
[Xperia Z3 Compact Android Development] fluffi444:
Did you add twrp via PoC? Some combinations are to big. They are bigger than max size of 20 MB. Otherwise ask in PoC thread.
[Xperia Z3 Compact Android Development] espaciosalter20:
ok, i finally made it using DOUBLECLICKME option on ta_poc tool... don't know why the option with ta_poc.bat didn't work for me (always get a over 20mb file)... anyways, now everything is working as it should with my security keys active! Thanks!
[Xperia Z3 Compact Android Development] fluffi444:
Yes - DOUBLECLICKME is now the best (and most simple) way to use TA PoC Tool.

But you can still use commandline if you want... As an exapmle with kernel.elf:

ta_poc kernel.elf TA.img ramdisk