[kernel][Z3+ dual][32.4.A.1.54](TWRP, dm-verity,DRM Keys)

[bruno$0]

Hello guys.

Today i will post a kernel that i (just run the wizard to) created for Z3+ DUAL variant version 32.4.A.1.54. My simple contribution! I'm no responsable for bricks or 3º global war if this kernel make something bad. I sold my device so i created this kernel by historical method.

PLUS: Old Kernel version - 32.3.A.2.33 / 32.2.A.0.253 / 32.2.A.0.305 / 32.2.A.5.11 / 32.3.A.0.372 / 32.3.A.0.376.

This kernel contents (newest one):

-TWRP
-dm-verity disabled
-fake DRM key
-Ric Disabled
Maybe works :
-SafetyNet
-Pokemon Go / Android Pay support

If you install the Magisk, maybe you can have the root and use Android Pay / POGO.

Update 8

Based on the new firmware 54. Same features like previous version. In this version i disabled the RIC, so pay attention to don't something stupid. LOL

Update 7

7.23.1
I made a test and in the previous version we cannot bypass safetynet. So i remove the busybox from this image. Using Magisk + MagiskSu i was able to bypass Safetynet.

7.23.0
Based on the new firmware 33. Same features like previous version.

Update 6.22

6.22 update: From root kernel thread: "Bug in the vendor overlay creation. Existing directories (like /vendor/bin) have not been replicated correctly".

6.00 update: Same features from update 5 but using the new firmware 376 as base. Expect a better battery life and sound issues fix.

Update 5

If you have a backup from your TA partition you can use it to get a better compatibility with sony features. At this time this kernel support superuser as an alternative to SuperSU and fix in the overlay layout which could prevent some libraries from loading and cause battery drain.

Update 4

At this moment we don't have a workaround for SafetyNet that keeps our root alive. The only method that i use if i need chage something is using the recovery terminal. :'( . I f someone found a way please send me a email to test it on this kernel.

This version appears content only November Security Path, but seems that tooks almost 200 Megas and i think that Sony perform some changes that he can't tell for us.

All process to flash it is bellow on update '3' or '1'.

Update 3

I create a new kernel for newest Sony Firmware 32.2.A.0.305. In order to keep Pogo running use the same method above, but use the last suhide version instead ( currently 0.54 ).

Ps. Seems that POGO UID has changed to 10245

Update 2

Last Saturday reading the news from ChainFire, i found a intersting method to hide su for specific apps. Think on it i imagine that this could bring back the Pokemon/Android Pay support. Since Magisk keep telling that his last version isn't compatible with Sony. Even so i give a try but this method don't work for me.

I perform alot of test to create a full operational kernel with all features that we like:
DRM key, TWRP, root, Xposed AND... Pokemon Go / Android Pay Support!

I still keep still enable RIC protection. So you still use the bellow commands to give write acess to System.

Please, follow this sequence:
Flash Kernel v3
Flash SuperSu 2.78 SR1 - need to be this ( other version could be not work )
- Deprecated Flash SuHide 0.52 - user the last version instead
Flash Xposed 86.2 from @DVDandroid Modded by me to leave it install on a SuperSu SR1 version.
Uninstall the Orignal Xposed Installer and install the Material Xposed Installer from same OP of Xposed.

After that we need to put the apps that we can avoid to obtain root access in the SuHide blacklist. Please, refer the SuHide OP to learn how to do that.
Ps: Pokemon Go UID: 10238

Links:

SuperSu 2.78 SR1 OP Thread:
http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133

SuHide Op Thread:
http://xdaforums.com/apps/supersu/suhide-t3450396

Material Xposed mod for SuperSu 2.78 SR1:
https://mega.nz/#!hYoiwCTL - Key: !GYCbKxwFuCs9z3LFWSgnsWaT0sJN2DuUoe4MgRCREy8

So sorry to modify you work Mr. @DVDandroid, but your check avoid to install the Xposed with this version of SuperSu. :'(

So..... After all have fun catching some Carterpies. Lol

Update 1

Reading the Tobias OP i understood that for update the Su Binary we must reflash a new Kernel with new version of SuperSu. This makes the process not so convenience to perform, since we need to compile a new kernel for a not always a new Kernel Version. So i decide to create a new version of thsi Kernel without root, because this way we can flash SuperSu over a zip file and Keeps our device always up-to-date. Another reason to perform this change is about the 'Magisk" OP that brings (not for us YET ) the Android Pay functionality in a ULB with root. I this setup we must use a most like 'Stock' kernel that we can because Magisk will try to put a mod version of SuperSu/PHH root. By this way it's better we not include root in our kernel.

Another changes was a remove DRM function on Kernel to give a opportunity to you choose best method for your. Please, search of DRM function restore on Xda and flash the proper zip file.

I don't disable RIC function this time, because Tobias belive that device get more security with RIC running. If you needs to write something on System folder you can use TWRP recovery or.... just go to the /sys/kernel/security/sony_ric edit the enable file, put a '0' without quotes, save it, the go to a terminal command app and type this using su: pkill /sbin/ric | mount -o remount, rw /system . this will make the system writetable until next restart. I think its better we deal with this.

I create a shell script to make to system partition temporarily writeable:
https://mega.nz/#!ZRQHyKqJ - Key: !55mhkn9A-2tfaNOFW5ipgTBK7xk_1WNb9-4Puipcd8Y
Please, change his permission with chmod on twrp file manager and copy it to data folder. Run it in a terminal program with ./gravasys.sh
Now you should be able to write on system folder until next restart. -- useless with new kernel

How to install it:
Run this command at command prompt -> fastboot flash boot boot.img

Where to download it:

54 Firmware Version

https://mega.nz/#!QVQzUbyb V1.00 - Key: !WgpKxjpVctoEcJ6qKuES_CgPvbD_8ExKWpNwwbUmg7s

33 Firmware Version

https://mega.nz/#!4c4m0ZKL V2.23- Key: !dC-zVyHUTruPGd2pa_PigI88CmMueD9uITZUg7TEmrs
https://mega.nz/#!MZoGUaJY V1.23 - Key: !nxnjQYVUWFpvxJkZtqI29dwXn2qyxzN6tyapf7JklcA

376 Firmware Version

https://mega.nz/#!0ZpwAAzD V1.22 - Key: !w_oin39T9BaFy49JD88Sr-W2RuR0gMEhSptbv3jkptA
https://mega.nz/#!sI5BHDYD V1 - key: !vd8rdAy-obpKbx6kTH1a2A-xnt1eNOqHhiBpQCTevsw

372 Firmware Version
https://mega.nz/#!BZJERYQR V2 - Key: !cyPTAgGuhGk_AHyrX05BKkVQ4W90XP1JfLzW5XsW3cw

11 Firmware Version
https://mega.nz/#!ZYIlwL7K V1 - key: !dEIYxesFpGPgrmQlpfhUUzDnl0mpiYXdVzBS9-qH9gE

305 Firmware Version
https://mega.nz/#!YFJBhBqD V1 - key: !VdmfhUuAiBM4wlBPik0QFvop607GXGoXbHmdYhAHvds

253 Firmware Version
https://mega.nz/#!JQoViBxB V3 - key: !Yt2zBL4ZLawyUyMsrYHb9hoUoOd1qgaCuHzoJECHt8o
https://mega.nz/#!cERT2bKA V2 - key: !WSPehajEAaHziOQbfCnBEePx5D3NHXg1c79XD9PGdP4
https://mega.nz/#!BNoR3KAb V1 - key: wR4F2bUGC2OUoMnD1FlY48nHD1UlD-AXc0WRsB_UdKY

Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.

Or... If you already have any other version kernel, you can flash another kernel by Twrp in install function by 'flash image' option.

Or....If you wanna update you firmware, download the proper kernel version and flash it on twrp. After this, go to 'REBOOT' and SHUTDOWN your phone. Now go to the flashtools and flash the original firmware but MARK the option to EXCLUDE the Kernel or you will need flash my kernel through PC again- I think that process sucks...

Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://xdaforums.com/xper...el-dm-t3301605

And another guys mention above.

So, if you like this kernel, please pay a coffee for these guys!

Sorry about my english.....

Warning
DON'T use this kernel on single model. I don't know whats happens!

Deprecated for V2/V3
Ps3: The most important part -> The tool that i used to make this kernel isn't ready to create it with a proper Twrp Recovery, so i made a 'workaround' to the tool understood that new rom version is compatible. Maybe could be happen something wrong while using Twrp altrohugh i already used it to install xposed again.

Bonus! Single Sim Version:

Fw 33: https://mega.nz/#!tRA0RA5B V2.23 - Key: !yPOImsO3ltXWDzy5GLxhFwyhAy92L3QLCMLuolY6kkc
Fw 376: https://mega.nz/#!ZR4nSKgYV1 - Key: !2NnhQChLiMS3exgsr51GjocM-ubB-0BCP-QHEsnI0zo

 

[r.ifat381]

Where u found the whole ftf file? Could u plz me the link?

Sent from my E6533 using XDA-Developers mobile app

 

[futiless]

Yes please.. Just let us know the ftf and we can start the celebration ????

So, if you like this kernel, please pay a coffee for this guy!

Ps. I already tested on my Z3+ and everything it's okay, so i will not responsable about any brinks or damage in use this kernel!

Ps2: DON'T use this kernel on single model. I don't know whats happens!

Ps3: The most important part -> The tool that i used to make this kernel isn't ready to create it with a proper Twrp Recovery, so i made a 'workaround' to the tool understood that new rom version is compatible. Maybe could be happen something wrong while using Twrp altrohugh i already used it to install xposed again.[/QUOTE]

Ok make that 2 things 1) your encryption key and 2) hint toward which ftf

 

[bruno$0]

The Ftf could be donwloaded on xperifirm and created by flashtools. you can choose any origin. I made this kernel by Russian version.

 

[futiless]

The Ftf could be donwloaded on xperifirm and created by flashtools. you can choose any origin. I made this kernel by Russian version.

OK but why the password I would thank you anyways ... do you know your download is encrypted with your password ?

 

[bruno$0]

Sorry. I.don't have noticed this. I always use Google drive and it's don't ask for a key.

Please, try this and let me kwon if it's works.

wR4F2bUGC2OUoMnD1FlY48nHD1UlD-AXc0WRsB_UdKY


Sent from my E6533 using XDA-Developers mobile app

 

[amirh8466]

Bootloader must be unlock or no?

Sent from my E6533 using Tapatalk

 

[futiless]

Thanks Bruno you made this easy...

 

[futiless]

FO - sending 'boot' (23188 KB)...
16/008/2016 03:08:49 - INFO - OKAY [ 0.772s]
16/008/2016 03:08:49 - INFO - writing 'boot'...
16/008/2016 03:08:49 - INFO - FAILED (remote: Command not allowed)
16/008/2016 03:08:49 - INFO - finished. total time: 0.791s
16/008/2016 03:08:49 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (23188 KB)...
OKAY [ 0.772s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.791s

Still PE Permissive problem : How did you do it Bruno.. I am on an unlocked bootloader btw.. :crying:

UPDATE !! : Simply Settings>Security>Xperia protect (like find my iphone)

 

[bruno$0]

FO - sending 'boot' (23188 KB)...
16/008/2016 03:08:49 - INFO - OKAY [ 0.772s]
16/008/2016 03:08:49 - INFO - writing 'boot'...
16/008/2016 03:08:49 - INFO - FAILED (remote: Command not allowed)
16/008/2016 03:08:49 - INFO - finished. total time: 0.791s
16/008/2016 03:08:49 - INFO - FASTBOOT Output:
target reported max download size of 536870912 bytes
sending 'boot' (23188 KB)...
OKAY [ 0.772s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.791s

Still PE Permissive problem : How did you do it Bruno.. I am on an unlocked bootloader btw.. :crying:

UPDATE !! : Simply Settings>Security>Xperia protect (like find my iphone)

Still have problem trying to flash this kernel?

Did you try to use Flashtools in the Fastboot mode?

Bootloader must be unlock or no?

Sent from my E6533 using Tapatalk

Yes. U need to open your bootloader to flash custom kernels, but if you really need do this my advice is make a downgrade to 5.0.2 - final rom # 266 - and make a backup from your DRM key before proceed the unlock method.

 

[creepyvillager]

Thanks bruno$0 for this kernel. It worked and it's great!

 

[PauljhonyZ3plus]

nice, job man

great , I'll do the test today , I'm currently using the kernel for 32.2.A.0.224 and this funciondando all ok with the root and Xposed TWRP . I can not wait to test the latest released version ...:good: enviado de meu E6533

 

[Alekim91]

Befors that I install this, I mush do other operation? as unlock bootloader or others?
thanks u

 

[lisboapcs]

Befors that I install this, I mush do other operation? as unlock bootloader or others?
thanks u

Yes! You must have an unlocked bootloader.

 

[Marko2424]

I am using your kernel with .224. How can I upgrade to 253? OTA & Xperia Companion are failing.
Many Thanks

Sent from my E6533 using XDA-Developers mobile app

 

[feizhel_vandrago]

i'm currently in .224, and i want to update to .253. after flashing .253 via flashtool, what should i do? unlock bootloader then flash this? i've ever do this before without losing anydata, but i forgot the step ._.

edit : i have unlocked bootloader before. so, i just flash it, and the bootloader unlocked again (because in .224, its already "locked" again after flash this kernel (the .224 version), and because the bootloader unlocked, i flash this kernel again (.253 version ofc) and voila, its back like it was before and dont forget, to access twrp, you need to hold vol. up button at yellow light when booting at sony's logo.

 

[challtsham]

This kernel work with android 6.0?

*Updated*
I was flash E6533 RU Rom and flash kernel , Finally work !! Thanks

 

[SultanRaad]

I Love you Bro!!!!!

for days I was banging my head on the wall. I dont own a computer. I borrowed my friend's laptop on a condition that I would install windows 10 on it as I'm a computer engineer. I installed Android Studio, flashtool, ADB thingee, google drivers, .net framework, JAVA, and lot of things with a 1Mb internet speed. now you can understand my pain......:crying:
I luckily found this today when I was in toilet as all the great ideas comes in toilet. lol
I just had flashed the latest HK version from xperifirm in flashtools last night and
then today I flashed your kernal.
so all I did.....
STEP 1: flashed firmware from flashtool's flashmode. had android up an running
STEP 2: flashed your Kernal from flashtool's fastboot mode via DoomLord option
its done up and running. now testing.....:good:

now what are DRM keys and things I dont know. would it effect my camera?

 

[bruno$0]

for days I was banging my head on the wall. I dont own a computer. I borrowed my friend's laptop on a condition that I would install windows 10 on it as I'm a computer engineer. I installed Android Studio, flashtool, ADB thingee, google drivers, .net framework, JAVA, and lot of things with a 1Mb internet speed. now you can understand my pain......:crying:
I luckily found this today when I was in toilet as all the great ideas comes in toilet. lol
I just had flashed the latest HK version from xperifirm in flashtools last night and
then today I flashed your kernal.
so all I did.....
STEP 1: flashed firmware from flashtool's flashmode. had android up an running
STEP 2: flashed your Kernal from flashtool's fastboot mode via DoomLord option
its done up and running. now testing.....:good:

now what are DRM keys and things I dont know. would it effect my camera?

It's for sure... Dou you still need a help to flash the drm fake keys?

 

[SultanRaad]

Yes please

It's for sure... Dou you still need a help to flash the drm fake keys?

Yes bro I havent done anything to DRM and how to flash?
I ant to flash from TWRP recovery. I dont uave a computer
SuperSU keep saying cant update binaries. Restart and try again and lucky patcher did not recognised the bussy box and kept saying install. But now it stopped asking. Itried many but right now jRummy 5.5.1.0
Please tell me why do I need DRMs? Where to get? And how to flash via TWRP recovery.
Thankyou