Develop Bugs

Custom kernel Z3+ E6553 - Nuke Verity / Sony RIC and allow SELinux permissive

Introduction
The stock Sony kernels use SONY RIC, SELinux and CONFIG_DM_VERITY that together make it exceptionally hard to root. With the stock kernel, it's impossible to run a modified ROM of any form (incorporating changes to the system partition). Attempting to boot with the stock kernel off a modified system partition results in a kernel stop or panic, manifested either by getting stuck on the Sony screen or a bootloop.
This kernel removes the Sony RIC and CONFIG_DM_VERITY and sets boot and runtime parameters that allow SELinux to be disabled or to be set into permissive mode. Once this kernel is flashed, you can download SuperSU flashable zip and flash it to your phone using the TWRP recovery image I posted in this forum in order to get root on your stock ROM.
This kernel contains no source patches. It's a completely stock kernel from the Sony github repository.
Click to expand...
Click to collapse
Features
SELinux configurable at boot and runtime
Sony RIC disabled
CONFIG_DM_VERITY disabled
Click to expand...
Click to collapse
Installation instructions
This boot image requires an unlocked bootloader. You will lose some functionality on your phone if you unlock your bootloader
Do your research and make sure you're using the latest version of the relevant tools if you do decide to unlock.
Unzip the boot.zip file to extract the boot.img file
Code:
C:\>adb reboot bootloader
C:\>fastboot flash boot boot.img
C:\>fastboot boot recovery.img
C:\>adb push UPDATE-SuperSU-v2.46.zip /sdcard/supersu.zip
Then switch to the TWRP interface, go to the Install menu and flash /sdcard/supersu.zip. Reboot and you're rooted. You can then modify your system partition as you please.
Click to expand...
Click to collapse
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
Binary
28.0.A.8.251 custom kernel for Z3+ E6553
TWRP Recovery Image V0.1 for Z3+ E6553
Sources @ github
Kernel config
Sony kernel-copyleft repository
Click to expand...
Click to collapse
Changelog
Code:
[B]Changelog[/B]
[new] 12 September 2015- Update to 28.0.A.8.251
[old] 10 September 2015 - Initial release
Thanks To
Code:
[url="http://forum.xda-developers.com/member.php?u=631273"]@Chainfire[/url]. What would we do without SuperSU.....
Click to expand...
Click to collapse

Awesome work, works without any issues.

I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!

elladroid said:
I must be being really stupid....
Unable to boot into recovery without reflashing recovery.img. I must be missing something!
Otherwise no other issues to speak of. Amazing Thanks!
Click to expand...
Click to collapse
"Until Sony releases an open bootloader you need to use this image via fastboot boot mode."

really 28.0.A.8.251?
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy

DHGE said:
@dl12345
searching for 28.0.A on GitHub gave me:
28.0.A.7.xxx Updated 2 months ago by jerpelea
28.0.A.6.xxx Updated 3 months ago by jerpelea
28.0.A.4.xxx Updated 4 months ago by jerpelea
Did you try the source posted on SONY Developer?
http://developer.sonymobile.com/dow...rchives/open-source-archive-for-28-0-a-8-251/
Does your boot.img work as a replacement for the boot.img flashed with 28.0.A.8.251 FTF?
I ask because I failed booting a boot image compiled from the SONY Developer source and an older kernel from 28.0A.7.24/31 as replacement for the image in the latest 8.251 FTF for my SGP712/karin_windy
Click to expand...
Click to collapse
Correct. The sources on github are old. I dowloaded the archive from the Sony website and compiled it. Yes the boot.img I compiled works perfectly as a replacement. I'm currently running it on my phone.

How to modify system partition
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.

yawo76 said:
Hi all,
Nob question but need help urgently. After installing the kernel I'm now getting storage space almost full and error 504 due I think to some modifications to the kernel to get root. I'm aware OP did say to modify system partition but don't have a clue how to do so in order to get storage space back and also install apps. Urgent help needed pls.
Cheers and thanks for your assistance.
Click to expand...
Click to collapse
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.

dl12345 said:
The kernel makes no modifications to the system partition and is unrooted. You need to flash SuperSU to get root.
This error you're getting is caused by the Xposed framework. You've installed the Xposed framework but you forgot to do a wipe dalvik and cache after installing. This is exactly what happens when you forget to wipe cache after installing xposed.
You can try to use the xposed uninstaller which may fix it. If not, you need to do a full wipe and reflash a ROM.
Click to expand...
Click to collapse
Thanks very much. It's true I installed Xposed Framework and didn't wipe cache. I have already reinstalled the Rom so will remember this time not to repeat the same mistake.

dl12345 said:
Introduction
NOTE: if you install Xposed you MUST wipe cache/dalvik after installation otherwise you will get an error message telling you that you are running out of storage space and any apps you install with Play store will fail the installation with a 504 error. This is NOT related to the kernel, but is caused by failing to wipe cache after installing Xposed.
Download
[B
Click to expand...
Click to collapse
I'm on .251 (modified system partition) without XPOSED installed. Using the kernel just causes boot loops (Sony Logo then 3 red flashes from the LED) the same way the stock kernel does. Is there something special I need to get SONY RIC / Verity to not run at boot?

This looks like a bad flash. Can you fastboot this kernel?

dl12345 said:
This looks like a bad flash. Can you fastboot this kernel?
Click to expand...
Click to collapse
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it

ChrisJ951 said:
No luck doing fastboot boot, or fastboot flash boot (both have the same issue of red led 3x then rebooting)
I re-downloaded it and the md5sum matched between the downloads:
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img
768eac3ba2ebcbdaf67e12d8bd11450b /home/chris/Downloads/boot-251.img (2)
EDIT:
Also just in case it matters, the exact build I'm on is
28.0.A.8.251
Edit2: Went back to complete stock from FTF flash and the kernel boots. Need to modify system partition and recheck
Edit3: Flashes SuperSU.zip and it is booting with SU installed. Unsure why my old rom was incompatible with it
Click to expand...
Click to collapse
Me neither - this bootimage has very few modifications: only CONFIG_DM_VERITY and RIC removed, some options for runtime control of SELinux added and the verity keys removed from the ramdisk. It boots fine on a stock 251 ROM for me. The kernel source is .251 source too...
I have noticed that I occasionally get bad flashes and odd behaviour when flashing ROMs (with everything from fastboot to flashtool to TWRP). I think the platform itself isn't totally stable and bug free. Usually I fix it by just wiping and reflashing

Hi @dl12345, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
EDIT - removed full OP quoted by mistake.

ondrejvaroscak said:
Hi, can you make the same kernel for Z3 (D6603) or at least point me in direction to know what I need to change by compiling own kernel from sources? Or modifying the original ramdisk..
The issue is that the new Concept M firmware from Sony uses the same security features. Guys (@Gustavo RD78) made successfully kernel for previous Concept L (5.1.1) based firmware, however the same approach seems to fail in case of Marshmallow. Your help will be very appreciated.
Click to expand...
Click to collapse
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
[UPDATE]
AOSP and copyleft source are different things. You need kernel source for concept rom's kernel, and it won't be published so it's impossible to build custom kernel for concept rom.

AndroPlus said:
You need kernel source (Sony won't upload it since it's closed beta test).
Also do not quote full OP.
Click to expand...
Click to collapse
Do I get it right, that I can't justo compile kernel for use with this firmware from AOSP / Sony Copy-left sources?

Another TWRP 2.8.7 for Fota Partition with working brightness

TWRP updated to 2.8.7.2 including latest commits. Download at the bottom (see Dec25 file). Selinux permissive is set, so, should work on all roms. Remember, unzip and flash in fastboot.
$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
I know there is a bunch of different TWRP recoveries for our Z1, including the official one. Well. This one is for Fota. It was compiled in Z1 build environment with all the appropriate flags. And brightness is working fine. Why brightness is important? Because at maximum brightness your phone will overheat to over 65 degrees during flashing. And thanks to previously wrong value, the brightness level in other TWRPs is 15 times the maximum one.
You can flash this one in fastboot like this: fastboot flash recovery recovery.img. Just make sure that your kernel does not have inbuilt TWRP, because 2 identical recoveries will conflict with each other. Unzip first...
For those who would like to know what's new, look here: https://gerrit.omnirom.org/#/q/project:android_bootable_recovery
In this build, I have also reduced default vibration to 28/28/28, but you can set in Settings to whatever you want.

can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !

hawkeyexp said:
can you publish your settings to get brightness working ? would be nice to complete official sources from twrp !
Click to expand...
Click to collapse
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe

ok will try it out if it works with my tree

Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk

Gawis said:
Thanks for posting.
I guess since this is FOTA it will not work with roms with recovery in boot like Jaguar?
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
That's right, but I am planning to update Jaguar's kernel. So, when it is done, I will
post it without recovery, so this one can work.
But it really makes no difference...

optimumpro said:
My commit was merged about 2 months ago by Slimroms. See their /device/sony/rhine-common. There is a flag for brightness that should be 255 instead of 4095. So, the changes are not in TWRP sources, but in the rhine tree...
Edit: Here is the commit: https://github.com/SlimRoms/device_sony_rhine-common/commit/7d64159d87d948926ebd40485deb18f9c292abbe
Click to expand...
Click to collapse
Is working fine - thx !

Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk

swa100 said:
Does this one work with the aosp android 6.0 rom that's around here?
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
Try, but there is a separate branch for TWRP for M. And anyway, M is not usable yet and won't be for a long time...

Thanks for this one!
I do however seem to experience an issue when trying another ROM like CM.
With your ROM I can reboot into this recovery but with CM I get a black screen. When using another older TWRP recovery I used when rooting both ROMS boot fine into recovery.
Sent from my Z1 using Tapatalk

@optimumpro is there any chance to make a flashable zip with it? Thanks

matcho13579 said:
@optimumpro is there any chance to make a flashable zip with it? Thanks
Click to expand...
Click to collapse
Use Rashr app to install this...

Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<

Snowblond said:
Hey there~
For some reason this recovery is not working for me at all. It won't start after flashing it, just a black screen.
The original twrp 2.8.7.0 from twrp.me is working, though. But I'd rather get your version to work because of the brightness control.
Could you help me please? >.<
Click to expand...
Click to collapse
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.

optimumpro said:
Are you sure you are doing everything right? Does your kernel have a builtin recovery? If that's the case, you will have problems. Have you updated your bootloader with Emma? Before flashing (in fastboot), do this: fastboot erase recovery; and then fastboot flash recovery recovery.img. Make sure you are not mistyping: the command means fastboot has to flash recovery.img to recovery partition. If you have FOTA, then there is a chance flash recovery may not work.
Click to expand...
Click to collapse
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
I don't know why it is not working for you. If you post your boot.img, I can put recovery in it..

Snowblond said:
Thanks for your answer. I tried flashing it exactly like you suggested, but the result was the same - black screen. My kernel does not have an inbuilt recovery and no, I didn't update my bootloader with Emma. That means I can only use FOTA, right? But I thought this recovery IS indeed for FOTA?
It's strange that the original TWRP is working, but yours doesn't.. even though they're both for FOTA..
Click to expand...
Click to collapse
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.

drakonizer said:
Happened to me once.
Try wiping FOTAKernel partition first, with:
Code:
fastboot erase FOTAKernel
and then flash the recovery with
Code:
fastboot flash FOTAKernel recovery.img
where recovery.img is your recovery.
Click to expand...
Click to collapse
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-

Snowblond said:
Thank you, but it's still a black screen when I try to boot in recovery. :/ I just don't understand why this version won't work with my device but the one from twrp.me without brightness control does .. -.-
Click to expand...
Click to collapse
Did you try with another kernel? If it worked then, you can trace the problem to the kernel itself, and not the device or your flashing methodology.

Recovery updated to 2.8.7.2. See OP for download...

TWRP RECOVERY in to FOTA PARTITION GUIDE (XPERIA S)

Flash TWRP to FOTA Partition(SONY XPERIA S).(Terminal Command Method)I will not responsible if you do something wrong to yor device
You can flash TWRP into fota partition if your kernel supports to flash it.(Ask the developer if support is available or not,To know more about Fota Partition Read here.).if yes then follow procedure.
1. You must have to root your ROM first.
2. Download TWRP.img (is the recovery file) from TWRP website.Place the downloaded twrp.img in sdcard. (Don’t place it under any folder.just copy to sdcard.if the downloaded file name is something else then rename it to twrp.img).
3. Now goto playstore and install terminal emulator app to your phone.
4. Now open terminal emulator app and type
su (and press enter key.it will ask for root permission.GRANT it) then type
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p11
(and press enter keyr.be careful while you writing the above commands.)
Finished.Now you have successfully flashed twrp recovery into fotapartition.Reboot your phone and when you see pink led just tap Volume UP key to enter to recovery.
Rom Flash Procedure
METHOD 2:
First extract boot.img and recovery.img from rom.zip and copy both to SD card root folder
1. Flash twrp recovery image like you flash kernel/boot.img(by flash tool or by fastboot method).
2. Enter to recovery.
Then follow the image by the numbers written in the image.Swipe to flash.
Then do the same for boot.img but choose boot. Img from SD card and boot(partition) in image 4. Swipe to flash and done.

Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !

C0D3FR34K said:
Sir, Could you please help me.
I have CWM recovery installed on Xperia SL and is running Layers ROM Cm11 based.
But I am thinking of switching to a new rom as the earlier one was very laggy. ([ROM][XS][5.1.1][LMY48P] OneOfaKind 22/09/2015 | UberTC 4.9 | Layers | Aroma Addon)
Could you tell me what shall I do with regards to:
1. Making the build.script change to make it compatible with Xperia SL
2. Do I need a TWRP recovery ? How will it go alongwith the CWM recovery which I already have installed and running pretty well ?
Thanks !
Click to expand...
Click to collapse
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t

C0D3FR34K said:
Problem is I am not able to find support for Xperia SL
The difference between Xperia S and SL is just 1.5GHz and 1.7GHz CPU respectively.. but support for the latter is sh!t
Click to expand...
Click to collapse
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.

Mirhawk said:
As said by You, the difference is just in frequency, and none in hardware. So what ever applies to XS will apply to XSL.
Click to expand...
Click to collapse
Thanks ! I have installed TWRP latest build using fastboot !

nageswarswain said:
First thing I am not sir..I am also like you...I have just shares my experience to which will help new comers in simple words.
As of your point 1 you have to make change to support on SL...
And about recovery.try to flash with cwm first if not succeed then flash twrp 2.8.4.1 or above and flash the rom.
Click to expand...
Click to collapse
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
/sdcard #
Click to expand...
Click to collapse
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058

C0D3FR34K said:
This is tantamount to spam but plz plz help me !!!
I was resizing the my 2GB partition but I am stuck now in the middle !!
I got stuck in step 10
Followed the instructions on this thread :
http://forum.xda-developers.com/xperia-s/s-development/tutorial-increase-data-partition-t2821058
Click to expand...
Click to collapse
I saw now that you have solved your problem. And this time also @mirhl is present there to help..good guy mirhl.

Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?

Torroan said:
Hello, i am using DooMKernel which comes with a preinstalled TWRP v2.5.0.0 now i am trying to update it to the latest version via Terminal or Fastboot but it doesn't work version stays the same. Does anyone know what could be the problem?
Click to expand...
Click to collapse
Here is a link which will give you mickybart's recovery and kernel of nAOSO b26.but before flashing this first copy the rom to your phone because u can't boot the device after flashing it.so flash this and reboot to recovery and flash the rom you want.
Link.
https://mega.nz/#!SZ9DXZgZ!tzugmlsOMum3cZYXyTh69lDDlhGfGjV-Fw2VKvaYdK8

Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?

Torroan said:
Thanks, in case i want to keep my current stock ROM there is no problem whatsoever is there? I mean i can just install the Kernel and i'll be good to go?
Click to expand...
Click to collapse
Take backup of the current rom before flashing the other file.then do as I said

TWRP... thanks!

Thanks
Thanks for the guide really appreciate !!

BTW - only mine recovery dont show temperature? my soft is oneofakind and newest twrp recovery in FOTA via dd command.

I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.

guruAhtasham said:
I installed twrp 2.8.7 using this and my phone got stuck in a boot loop
I am on uCyan b04.
Click to expand...
Click to collapse
Flash ucyan b04 kernel only on fastboot and try to reboot...

nageswarswain said:
Flash ucyan b04 kernel only on fastboot and try to reboot...
Click to expand...
Click to collapse
Thanks for the reply but it didn't work
have to do a clean flash again to make it boot.

[kernel][E6533][Z3+ dual][32.2.A.0.224](RIC disable, TWRP, root,dm-verity)

Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe 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!:silly:

Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!

youngcube said:
Hello，i've already flashed your boot.img. then i try to flash SuperSu2.6.5.zip. Everything is just fine.
But when i enter SuperSu , the app said that i am in system-less mode.
another app can't detected root mode also.
is there anything wrong with me?
it's dual Z3+
Thanks a lot!
Click to expand...
Click to collapse
no need to flash superSU i think, it's already included in the kernel.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.

bruno$0 said:
Sorry guys, i have the same problem here. After a few minutes i discorvery that i used an 'update' (pretty old) superSu zip.
So, i went to the recovery and flash the supersu2.66.zip. After this all programs detected root nomally.
Sorry for inconvenience.
Click to expand...
Click to collapse
Working wonderful with SuperSU 2.68 I have a doubt do you have a DRM Restore that works with this Android Version?

Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks

[/COLOR]
creepyvillager said:
Hello, sorry for this noob question. If I flash this to my already rooted Z3+ dual, would it delete all my files and stuff here? Thanks
Click to expand...
Click to collapse
No flashing a kernel doesn't wipe anything, if you're having a dilemma then take a backup of everything like apps, contacts etc using titanium backup, copy the backup folder to your external memory or computer then flash.
Hope it helps.
P. S ONLY INSTALLING A RECOVERY WIPES EVERYTHING.
---------- Post added at 09:41 AM ---------- Previous post was at 09:25 AM ----------
bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe 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!:silly:
Click to expand...
Click to collapse
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?

njaya95 said:
Can you tell me how long it took for the first boot?
Cause mine is stuck at 'Starting Applications' for about 8 minutes.
Edit : Couldn't wait it took almost 20mins with no progress so shut it down using power + volume up key and went into recovery wiped dalvik/cache and installed supersu 2.66 and again wiped then rebooted. Now it's showing optimising apps. The only problem is it's not charging. Usually at this stage when i connect my charger the charger led starts glowing but now nothing. Any ideas?
Click to expand...
Click to collapse
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.

creepyvillager said:
Yeah, this also happens to my device when I flashed the kernel.
Edit: It just stuck at the boot screen with blinking red LED notification.
Click to expand...
Click to collapse
I just found out to use this kernel i should have .244 firmware i bet you're at .185 so update it to .244 then try this kernel. I'm just downloading the firmware now using Xperifirm(https://www.google.com/url?sa=t&rct...9Q4Ht-00R24lisYcw&sig2=ac8ImW1ZY7AvFSZpG9I9mA) and i'll post what i did to the phone after the update.

zemetal said:
no need to flash superSU i think, it's already included in the kernel.
Click to expand...
Click to collapse
It's not, need to flash SuperSU I flashed 2.66 Beta

bruno$0 said:
Hello guys.
Today i will post a kernel that i (just run the wizard to) created for Z3+ dual variant version 32.2.A.0.224. My simple contribution!
This kernel contents:
-RIC disable
-TWRP
-root
-dm-verity
How to install it:
Run this command at command prompt,
fastboot flash boot boot.img
Or.....
Use the Flashtools in a fastboot mode, then choose the Flash option by DoomLord.
Please, Don't thanks me. All the hard work was performed by Mr. Tobias Waldvogel in this thread:
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
So, if you like this kernel, please pay a coffe 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!:silly:
Click to expand...
Click to collapse
Hey can you help me, how to make this kernel SELinux status permissive.

njaya95 said:
Hey can you help me, how to make this kernel SELinux status permissive.
Click to expand...
Click to collapse
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.

bruno$0 said:
I don't know. I just run the script to create the image. Sorry. in a near future when Sony release the MM for M4 dual and share the source code i will try to create a custom kernel from benning for my other device.
Click to expand...
Click to collapse
Okay ?

Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?

SugnaB said:
Running Lollipop 5.0.1 and when i flash the kernel i get not orange/yelllow LED. How do i go into recovery?
Also got no super su app.
I meant to flash it with "fastboot flash recovery boot.img" from Android/android-sdk/platform-tools. Correct?
Click to expand...
Click to collapse
It's for 6.0.1 so don't flash it for 5.0.1, update the firmware then flash it cause Sony would have updated somethings in the kernel which won't work with old firmwares. The reason for boot working is maybe because of the phone rebooting from fastboot mode.
Hope it helped. [emoji4]
Sent from my E6533 using XDA-Developers mobile app

Did it need a Unlocked Boot-loader device?

sani007 said:
Did it need a Unlocked Boot-loader device?
Click to expand...
Click to collapse
offcourse.

Sorry for the noob question but I need to know the prerequisites,
Can I flash the Kernel right after flashing stock file OR....
Do I need to first unlock my bootloader
Do I need to have backed up my TA partition

hi there, i wanna update form .185 to .224. is it possible to update without wipe the data? and if it can, if i wanna root it, i just flash this kernel after fw upgrade, then flash supersu via twrp, am i right? thanks

If Xperia Z3+ Dual can't be bootloader unlocked, what's the point in this kernel?!

[RECOVERY][Hollyss][Hollyds][TRXteam] TWRP 3.1.1-0 touch recovery [2017-09-10]

Team Win Recovery Project for Xperia M5
NOTE : This recovery for only bootloader unlocked M5s! Doesn't work with locked bootloader.
Installation :
for Lollipop users :
1- Root your device with this https://goo.gl/F512NR or this https://goo.gl/NADp3S)
for Marshmallow users :
1- Install this kernel (optional) (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users.
2- Go to the /system and delete recovery-from-boot.p with any file manager that has a root privilege.
3- Enable USB debugging and connect the phone to PC.
4- Open cmd and enter these codes:
Hollyss(SingleSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyss.img
fastboot reboot
Hollyds(DualSim)
Code:
adb reboot bootloader
fastboot flash fotakernel twrp-3.1.1-0-hollyds.img
fastboot reboot
Bugs :
- USB-OTG not working
- Cache partition has some troubles, it is not wipeable
Workaround for cache:
-In TWRP click settings and enable "Use rm -rf instead of formatting"
Download :
Hollyss-20170910-SingleSim
https://www.androidfilehost.com/?fid=673368273298984560
Hollyds-20170910-DualSim
https://www.androidfilehost.com/?fid=889764386195928556
TRXteam Members :
- @ByBlaCk
- @krkshalill
- @TheShadow35

Changelog :
Code:
2016-12-9 :
-Fix the device name and codename
-Fix Otg(Needs test)
2016-09-22:
- Added M5 Dual support.
2016-09-15:
- MTP issues fixed
- Minor bug fixes
2016-09-14:
- Updated to TWRP 3.0.2-2
- SD Card now working
2016-09-13:
- Initial release

I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.

Limi96 said:
I can't flash it, 30.1.A.1.55 is not supported.
Although i have it rooted & unlocked the bootloader.
Nvm foundnew firmware; flashing now.
Click to expand...
Click to collapse
@Limi96
Sorry bro, I forgot adding installation for Lollipop Now I'm adding :good:

TRXteam said:
you must flash marsmallow rom and try again
Click to expand...
Click to collapse
Will post results when i come back home, i just flashed 30.2.A.0.100 going out now.

Added installation for Lollipop users.

http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!

i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?

Limi96 said:
http:\\i.imgur . com\8x0L2Zd.png
I now have a working TWRP thx!
Downloaded new firmware using xPirifirm flashtool 30.2.A.0.100 single sim, cda was 1300-3365.
Flashed new firmware using flashtool; E5603_30.2.A.0.100_1300-3365_R2B.
Booted up device, hard reset it because it looped then it loaded apps and i did the tutorial.
Flashed kernel using flashtool; boot_m5_ss_30.2.A.0.100_nodmv_su_drmfix.
Flashed twrp-3.0.2-2-holly using flashtool.
So far no complaints if i find any bugs i will inform!
Click to expand...
Click to collapse
Thanks you reply:good:

ataraxist said:
i was looking for otg-usb issue for M5 and i stumble upon this page...big thanks to TRXteam for providing the recovery!!
By the way why is the otg not working...?
Click to expand...
Click to collapse
My Team look it and cant fix otg,but work ıt.Thanks you reply:good:

When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.

ginowoo said:
When I write the commands do I need to put my M5 in fastboot mode? Or plug the device in normal mode?
Thanks.
Click to expand...
Click to collapse
ıf your M5 in normal mode write this command
adb devices
adb reboot bootloader
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot
ıf your M5 in fastboot mode write this command
fastboot flash fotakernel twrp-3.0.2-2-holly-20160915.img
fastboot reboot

how to boot into recovery after that?

warboss said:
how to boot into recovery after that?
Click to expand...
Click to collapse
Hold volume down when powering device up.

i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?

ataraxist said:
i realised that after using this recovery, the phone was recognised as Redmi_Note_2 in TWRP and windows pc? the recovery was modified from Redmi?
Click to expand...
Click to collapse
Yes,same sources from redmi

TRXteam said:
Yes,same sources from redmi
Click to expand...
Click to collapse
your english is ok!
So it cannot be modified to "Xperia_T2Ultra"?

I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root. (https://goo.gl/nBWatu)
After the first step, continuous steps same for all users."

ataraxist said:
I am on MM stock rom. If i do not need root, do it need to flash the kernel? Can i straight away flash this fotakernel for recovery?
"for Marshmallow users :
1- You're install this kernel first for root.
After the first step, continuous steps same for all users."
Click to expand...
Click to collapse
You need to unlock your bootloader

Yup.. Already unlocked bl.
Sent from my E5653 using XDA-Developers mobile app