[EOL][RECOVERY][Android 8 / 9][Stock/SODP][XZ2/C/P/3] TWRP 3.3.1-0 [UNofficial] - Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other

[EOL][RECOVERY][Android 8 / 9][Stock/SODP][XZ2/C/P/3] TWRP 3.3.1-0 [UNofficial] - Sony Xperia XZ2 ROMs, Kernels, Recoveries, & Other

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
FAQ:
If your stock camera preview is black, please follow this issue ticket.
https://github.com/sonyxperiadev/bug_tracker/issues/261
https://github.com/MartinX3-AndroidDevelopment/bug_tracker/issues/7
Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
You need to open advanced wiping and check the entries data and internal storage.
Of course clear the dalvik, too.
If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Weird problems not easily to reproduce by other users require that you make sure, that you
Use the newest platform tools (adb & fastboot)
Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
Newflasher from XDA
Xperifirm from XDA
Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
In TWRP:
Code:
cat /dev/block/bootdevice/by-name/misc
shows you the reason.
Please replace it with an empty string.
Known Bugs:
The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
Bugtracker:
TWRP Bugtracker -> If you think the problem is in TWRP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
The TWRP should be still usable if you just "fastboot boot twrp.img" it.
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@dees_troy and his team of volunteers for the TWRP code
@M-ROM for his hint activating the touch in TWRP
@osm0sis
@nreuge
@FartyParty
@pandemic
@nasko_spasko
@VeixES
@Klaus N.
@old.splatterhand
@yanke928
@michele2
@niaboc79
@j4nn for hacking the kernel to make "fastboot boot twrp.img" possible
@shoey63 for testing @j4nn 's hack
@oshmoun for a better "fastboot boot twrp.img" solution
@dhacke thank your for providing a download server
Shame on me if I forgot someone after searching through the thread and my PM's!
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
XDA:DevDB Information
TWRP, ROM for the Xperia XZ2
Contributors
MartinX3, oshmoun, Marijn, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Matching to firmware in twrp name
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-08-10
Created 2018-07-26
Last Updated 2020-10-23

Download & Installation
Download:
https://androidfilehost.com/?w=devices&uid=11410963190603893035
https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
Unzip the *.gz files with https://7-zip.org/ or Linux.
Installation Android 9.0:
Update to newest stock firmware before unlocking!!!
Enter fastboot via software, not hardware buttons. See "Known Bugs".
(Optional; If you modify the system or need the camerafix.zip)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot boot twrp.img
Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
Reboot into installed TWRP
Want Root? -> Magisk
(Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
In case of touch issues on the XZ2 compact:
Download (try the v10 zip first, if it doesn't work try v9 or v8)
Do the same steps, but with the TWRP test release.
Installation Android 8.0:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta-xz2(?).img
fastboot flash boot twrp.img
Install stockkernel-xz2(?)-installer.zip
Install twrp-3.2.3-0-xz2-xz2c-xz2p-installer-xz?-installer.zip
Install Magisk-v17.1.zip
(Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)

News
30.01.2020
i put this twrp officially into the endoflife status.
Due to twrp 10.0 being work in progress, i am unable to compile it in a 10.0 build environment.
So the 10.0 release will take its time.
(and sony didn't release the source code for the stock kernel until now).
I will try to experiment with a 9.0 twrp and a 4.14 kernel, so look if it is usable in the new 10.0 4.14 custom roms as a temporally workaround, when i have free time.
If that works, i will experiement with the stock kernel source, after it got released.
But for now i have no clue for any eta. (the curse of doing it as a volunteer :d)
Click to expand...
Click to collapse
17.11.2019
stock twrp 52.0.a.11.32 doesn't decrypt userdata.
Waiting that the needed patches get submit in twrp/omnirom.
Then i rebuild a new twrp for 52.0.a.11.32.
Please only "fastboot boot" it, don't flash it to the phone or the twrp will be just stuck at twrp logo.
Click to expand...
Click to collapse
16.11.2019
stock twrp 52.0.a.11.32
Click to expand...
Click to collapse
16.10.2019
stock twrp 52.0.a.11.3
Click to expand...
Click to collapse
13.10.2019
september security patch level:
Stock twrp 52.0.a.10.6
smaller download size:
Removed bundled magisk, since the newest one doesn't make bootloops anymore.
Removed touch drivers from twrp, now a script greps them dynamically from the vendor partition.
Click to expand...
Click to collapse
08.09.2019
a testbuild for the apollo/xz2c users with the not working tcm touch hardware.
Together with the testbuild for omnirom and sonyaosp every apollo user should be able now to use the touchscreen.
apollo_twrp_v8.zip
Click to expand...
Click to collapse
26.08.2019
september no new release
reason -> vacation + university exams
Click to expand...
Click to collapse
10.08.2019
august security patch level:
Stock twrp 52.0.a.8.131
sodp twrp
Click to expand...
Click to collapse
09.08.2019
removed the august stock twrp.
The new aosp pie august security patch level introduced new updates to the de/encryption, which needs to get adapted by twrp first.
Click to expand...
Click to collapse
08.08.2019
august security patch level:
Stock twrp 52.0.a.8.131
Click to expand...
Click to collapse
30.07.2019
stock twrp:
Upgraded the touch drivers to the 52.0.a.8.107 version.
Should fix all possible happening touch issues in twrp.
Click to expand...
Click to collapse
13.07.2019
fixed stock twrp touch
(culprit was the activation of the logcat support; working fine in the sodp twrp, but kills the touch workaround of the stock twrp)
Click to expand...
Click to collapse
12.07.2019
fixed stock twrp touch
(accidentially delivered with sodp kernel leading into not working touch)
Click to expand...
Click to collapse
12.07.2019
july security patch level:
Stock twrp 52.0.a.8.107
sodp twrp
Click to expand...
Click to collapse
11.06.2019
stock twrp 3.3.1 firmware 52.0.a.8.83 (june security patch level)
Click to expand...
Click to collapse
10.06.2019
custom rom twrp with june 2019 security patch level.
For the upcoming sonyaosp / omnirom june 2019 security patch level release.
Click to expand...
Click to collapse
01.06.2019
reuploaded custom rom twrp with hotfix to decrypt devices fullwiped on may 2019 or newer.
Click to expand...
Click to collapse
31.05.2019
custom rom twrp 3.3.1 with may 2019 security patch level.
Also i'll only push files to the single sim device section.
The dual sim device section will get a file with a hint to look into the single sim section.
That'll save bandwith and server storage.
Click to expand...
Click to collapse
18.05.2019
reworked the thread page
Click to expand...
Click to collapse
14.05.2019
http://www.dhsfileserver.de/ftp/martinx3/ thank you @dhacke for the second download server
Click to expand...
Click to collapse
13.05.2019
stock twrp firmware 52.0.a.8.50 (may security patch level)
Click to expand...
Click to collapse
24.04.2019
reuploaded aosp/stock twrp.
Accidentially uploaded (build environment bug) the akari xz2 twrp for every device. It boots & installs magisk, but it can't mount the other partitions.
Sorry!
Click to expand...
Click to collapse
22.04.2019
aosp twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!
Click to expand...
Click to collapse
17.04.2019
stock twrp
hello "fastboot boot twrp.img"!
Bye bye twrp installer zip file! (see installation instructions.)
reduced the download size!
Click to expand...
Click to collapse
09.04.2019
stock twrp firmware 52.0.a.8.25 (april security patch level)
fixed touch problems some people have.
Twrp is now at version 3.3.0-0.
Click to expand...
Click to collapse
07.04.2019
bug & feature tracker
https://github.com/martinx3sandroiddevelopment/bug_tracker
Click to expand...
Click to collapse
06.04.2019
reuploaded april security patch level aosp twrp with a newer kernel and more upstream merged changes from sony aosp.
I hope now the wifi problem is gone.
Twrp is now at version 3.3.0-0.
Click to expand...
Click to collapse
02.04.2019
reuploaded april security patch level aosp twrp.
Reverted https://gerrit.omnirom.org/#/c/andro...overy/+/33783/
now zips are installable again without the "digest" error.
Omnirom still has the bug. Just install it on top of omnirom or replace its boot.img by the twrp.img.
Click to expand...
Click to collapse
02.04.2019
aosp twrp released for aosp / custom roms with april 2019 security patchlevel.
Click to expand...
Click to collapse
01.04.2019
aosp twrp released for aosp / custom roms with march 2019 security patchlevel.
May contain the stock twrp mtp bug.
A zip installer is not needed anymore.
Just flash the boot.img, the dtbo.img and the vbmeta.img with the parameters.
Click to expand...
Click to collapse
31.03.2019
reuploading twrp.
Removed the old build, which stopped at twrp logo.
Now the mtp and touchscreen problems should mostly be fixed.
Click to expand...
Click to collapse
30.03.2019
reuploading twrp.
Removed the old build.
Now the mtp and touchscreen problems should be fixed.
I tried to automate the upload with my new android file host access.
It is unstable.
Sadly android file host is the only hoster with unlimited quota.
Click to expand...
Click to collapse
25.03.2019
stock twrp released for stock firmware 52.0.a.8.14.
Many new fixes and features and sadly a new bug:
Wait until the password entry appears, before you connect the phone with your computer or the touch won't work.
But i hope that the touch bug on the xz3 is now fixed.
Click to expand...
Click to collapse
14.03.2019
dear people, sadly no new twrp for the new stock march firmware with shiny new twrp bugfixes and so on until i finished my next exam (of many) at the 20.03.2019.
But after that i'll release a new release.
Maybe with working "fastboot boot twrp.img"
i hope
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/33287/
will got merged then, too, so i can hopefully remove the twrp installer zip file.
Ps:
The good thing is, if you rely on the twrp and won't update the firmware before i release it, you can see others complaining about march firmware bugs without having them on your phone. [emoji14]
Click to expand...
Click to collapse
19.02.2019
bundling now .202 touch drivers.
The difference to the first version is, that i don't try to get them from the vendor partition.
Instead i bundled them into my ramdisk file.
I hope the touch problems are now fixed for everyone, which i sadly can't reproduce.
Click to expand...
Click to collapse
17.02.2019
since some users still get no working touch, i switched back from .202 touch drivers to .163 touch drivers.
Click to expand...
Click to collapse
16.02.2019
hotfix for stock xz2 twrp. I introduced a bug with the last update.
Click to expand...
Click to collapse
16.02.2019
hopefully fixed touch bugs some where having (even with the exact same hardware/firmware combination like me)
Click to expand...
Click to collapse
13.02.2019
twrp firmware 2019 february 52.0.a.3.202
including a camera fix, which is compatible with the latest twrp release. (fixes only the black preview)
reduced the twrp download size by around 6mb. If the touch doesn't work, pelase report it asap.
Click to expand...
Click to collapse
10.02.2019
in combination with my sonyaosp _r31 release i uploaded the twrp for custom rom's / aosp (february patch level)
it is importand to use the same twrp security patch level as the rom or avb 2.0 will lead into bootloops in twrp and the system.
Click to expand...
Click to collapse
08.02.2019
i found the broken twrp solution together with the sony developers.
It's the cause of the omni 9.0.0_r31 ramdisk (february security level)
i need to wait for the february security patch stock update.
The rollback security is preventing me to use an january kernel with the february firmware, resulting in a blinking bootlooping black/logo/black/logo twrp animation.
Will release the next working twrp with twrp camerafix & magisk camerafix included and maybe my touch driver approch will work then, ( now i know it should work, it was only the cause of this security behaviour)
Click to expand...
Click to collapse
07.02.2019
i̶n̶c̶l̶u̶d̶i̶n̶g̶ ̶a̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶c̶a̶m̶e̶r̶a̶ ̶f̶i̶x̶ ̶c̶o̶m̶p̶a̶t̶i̶b̶l̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶l̶a̶t̶e̶s̶t̶ ̶t̶w̶r̶p̶ ̶u̶p̶d̶a̶t̶e̶.̶ ̶(̶o̶n̶l̶y̶ ̶f̶i̶x̶e̶s̶ ̶b̶l̶a̶c̶k̶ ̶c̶a̶m̶e̶r̶a̶ ̶p̶r̶e̶v̶i̶e̶w̶.̶)̶
Click to expand...
Click to collapse
06.02.2019
r̶e̶d̶u̶c̶e̶d̶ ̶t̶h̶e̶ ̶t̶w̶r̶p̶ ̶d̶o̶w̶n̶l̶o̶a̶d̶ ̶s̶i̶z̶e̶ ̶b̶y̶ ̶a̶r̶o̶u̶n̶d̶ ̶6̶m̶b̶.̶ ̶i̶f̶ ̶t̶h̶e̶ ̶t̶o̶u̶c̶h̶ ̶d̶o̶e̶s̶n̶'̶t̶ ̶w̶o̶r̶k̶,̶ ̶p̶l̶e̶a̶s̶e̶ ̶p̶r̶o̶v̶i̶d̶e̶ ̶m̶e̶ ̶t̶h̶e̶ ̶i̶n̶f̶o̶r̶m̶a̶t̶i̶o̶n̶s̶ ̶l̶i̶n̶k̶e̶d̶ ̶i̶n̶ ̶t̶h̶e̶ ̶f̶a̶q̶.̶
Click to expand...
Click to collapse
03.02.2019
a mysterious bugfix for the stock twrp appeared. It is super effective for stock decryption.
Click to expand...
Click to collapse
01.02.2019
added the aosp/customrom support. I tested it on my xz2 with omnirom, aosp and resurrection remix.
Click to expand...
Click to collapse
19.01.2019
updated to stock firmware 52.0.a.3.163 (jan 2019)
Click to expand...
Click to collapse
19.01.2019
created buildenvironment for twrp.
Twrp is now based on tama omnirom builds.
That means we now get the latest twrp code commits.
This are the twrp code changes:
https://github.com/omnirom/android_...8=✓&q=committer-date:>2018-12-10&type=commits
Click to expand...
Click to collapse
15.01.2019
hopefully activated the xz3 twrp touch.
Click to expand...
Click to collapse
10.12.2018
twrp android 9.0 pie december update.
Synced my stuff with the 52.0.a.3.126 stock firmware (drivers, kernel, etc.).
Added the xz3.
uploaded the last pie firmware with a working camera on unlocked devices.
Click to expand...
Click to collapse
16.11.2018
the xz2p has a different kernel.
I fixed the xz2p twrp by splitting it in its own twrp boot.img file.
Click to expand...
Click to collapse
16.11.2018
twrp android 9.0 pie november update.
Synced my stuff with the 52.0.a.3.84 stock firmware (drivers, kernel, etc.)
Click to expand...
Click to collapse
13.10.2018
android 9.0 pie update.
Cleaned unused stuff.
Fixed mtp.
Only for xz2 and xz2c as universal installer.
Encryption still not supported, but my device config files are now usable to compile your own twrp.
Of course, the configsettings still are not fully optimal for this device.
Click to expand...
Click to collapse
13.10.2018
android 9.0 pie twrp for xz2 and xz2c got released!
Xz2p will follow, after it gets the same update.
Mtp is still deactivated.
Encrpytion of the userdata doesn't work (password always wrong), because of the new android 9.0 pie encryption.
I think the next release will fix this.
Btw. In the first post is now a know bugs section.
And thanks to @m-rom, @michele2 and @niaboc79, who tried to helped me in this emergency situtation that pie got released and needed a new twrp while i was at work. :silly:
Click to expand...
Click to collapse
11.10.2018
i seperated the twrp builds again, because of touch bugs in the xz2c.
The xz2, xz2c and the xz2p got seperated twrp.img files and stock kernel installer for twrp.
Click to expand...
Click to collapse
10.10.2018
i seperated the xz2_xz2c build from the xz2_premium build.
It seems that i made a mistake.
The xz2 and xz2c are sharing the same kernel, but the xz2premium kernel has little differents.
I also optimized the folder structure behind the downloadlink.
Click to expand...
Click to collapse
10.10.2018
working together with @storm// to achieve a working xperifix drmfix.
After we got success, i will highly recommend removing the old drmfix and installing his one.
The old one may brick the device forever during a longer time period. (2 weeks or longer)
old drmfix uninstall routine:
Flash with newflasher (v13+) only the file:
Vendor_x-flash-all-b6b5.sin
but remember to flash both slots.
Not only a or b.
twrp is your friend.
Or
fastboot set_active other
Click to expand...
Click to collapse
10.10.2018
i am happy to announce the twrp for the xz2, xz2c and xz2p!
I need test results for the xz2c and the xz2p which i don't own.
Installation instructions got updated.
The last file got uploaded a few minutes ago.
Click to expand...
Click to collapse
08.10.2018
fixed sdcard
in the 2018-10-08_01:36+2:00 folder.
Code:
1 fastboot format userdata
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Reboot into recovery
4. Twrp flash stock kernel xz2_51boot.zip
5. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
6. Install drmfix by storm// [b]or[/b] m-rom
7. Twrp flash magisk-v17.1.zip
8. Twrp flash permissive.zip
9. Reboot into system
Click to expand...
Click to collapse
06.10.2018
new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-06_14:53+2:00 folder.
Code:
1. Clean flash
[b]or[/b]
1.1 fastboot format cache
1.2 fastboot format userdata
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Twrp flash stock kernel xz2_51boot.zip
6. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
7. Install drmfix by storm// [b]or[/b] m-rom
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system
Click to expand...
Click to collapse
05.10.2018
new try, thanks to everyone who helps me, tests for me and are a part of this nice little project.
in the 2018-10-05_16:10+2:00 folder.
Code:
1. Clean flash
2. Fastboot flash twrp-xz2-2c-fixed-fstab-fixed-security.img
3. Fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
4. Reboot into recovery
5. Install drmfix by storm
6. Twrp flash stock kernel xz2_51boot.zip
7. Twrp flash twrp-installer-xz2-2c-3.2.3.zip
8. Twrp flash magisk-v17.1.zip
9. Twrp flash permissive.zip
10. Reboot into system
Click to expand...
Click to collapse
05.10.2018
modified the twrp recovery hack by @m-rom again.
Now i fixed the security settings for adb.
Twrp-xz2-2c-fixed-fstab-fixed-security.img
in the 2018-10-05_10:22+2:00 folder.
Click to expand...
Click to collapse
04.10.2018
modified the twrp recovery hack by @m-rom again.
Now unpacked and repacked by android image kitchen.
Twrp-xz2-2c-fixed-fstab.img
in the 2018-10-04_21:00+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.
Click to expand...
Click to collapse
04.10.2018
modified the twrp recovery hack by @m-rom.
Twrp-xz2-2c.img
in the 2018-10-04_11:30+2:00 folder.
I exchanged the twrp.fstab and the recovery.fstab. I hope this fixed the shell problem.
Click to expand...
Click to collapse
02.10.2018
a new build.
Twrp__more_oem_drivers__oem_firmware__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added the entire firmware, bin, and radio folder and some more lib64 drivers from the aosp oem 8.1.6.3_r1_v15 binaries, so we can test, if the touch works now.
Click to expand...
Click to collapse
28.09.2018
a new build.
Twrp__more_oem_drivers__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
in the 2018-09-27_22:20+2:00 folder.
I added every lib64 driver, so we can test, if the touch works now.
Click to expand...
Click to collapse
27.09.2018
a new build.
Twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img
i tweaked some configs.
Switched back to oem 8.1 v15 drivers.
I did not upgrade the kernel, because the current code could damage the display.
Kernel bugs are listed in my aosp rom thread.
Click to expand...
Click to collapse
20.09.2018
new builds.
Feel free to test.
boot__omni_8.0__stock_8.0_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__stock_51.1.a.11.51_libs.img.gz
boot__omni_8.0__stock_8.0_kernel__oem_8.1_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__oem_8.1_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__oem_8.1_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__oem_8.1_libs.img.gz
boot__omni_8.0__stock_8.0_kernel__oem_9.0_libs.img.gz
boot__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img.gz
twrp__omni_8.0__aosp_8.1_kernel__oem_9.0_libs.img.gz
boot__omni_8.1__stock_8.0_kernel__oem_9.0_libs.img.gz
boot__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img.gz
twrp__omni_8.1__aosp_8.1_kernel__oem_9.0_libs.img.gz
Click to expand...
Click to collapse
18.09.2018
a new build.
Twrp_8.0_oldconfig.img.gz
twrp_8.0_newconfig.img.gz
now i used the source code of the stock kernel to create a prebuild kernel image.
And i updated the device config.
And it looks like, that i can't put the stock source into the kernel folder of omni build environment.
It stops with the error, that it can't find a rule to make the zimage.
It is much more easier to build the aosp kernel, than the stock kernel.
Click to expand...
Click to collapse
17.09.2018
i downloaded the 51.1.a.11.51 firmware and extracted all the needed stuff, including the new kernel to update the twrp device sources. Hehe.
One is got built with omni 8.0 and the other one with omni 8.1.
Feel free to test them.
Click to expand...
Click to collapse
16.09.2018
split the aosp rom part into its own project.
https://forum.xda-developers.com/xperia-xz2/development/aosp-aosp-8-1-h8266-t3843269
Click to expand...
Click to collapse
15.09.2018
i uploaded the aosp rom.
Feel free to test it.
Its kernel will be the one with my twrp build.
So i need to know if the kernel work or has bugs and broken functions.
If the kernel and the aosp image is fine, i will update the twrp build.
Click to expand...
Click to collapse
14.09.2018
the bootloader v60 got released with the september patch.
i will now build aosp with the latest sources and if it will boot and work, i will use its kernel and the updated device sources to build twrp.
Click to expand...
Click to collapse
27.08.2018
don't use this twrp builds.
We need to wait for the bootloader update from sony.
The device will be announced as part of the sony open devices project at the same time and the following issue will be closed:
https://github.com/sonyxperiadev/bug_tracker/issues/149.
The leading developer jerpelea told us, that it would be released with the september stock update.
Click to expand...
Click to collapse
18.08.2018
i compiled the xperia aosp 8.1 image for the xz2 (h8266).
Feel free to test it.
I don't know, if we need the bootloader patch to run it.
Please follow the installing instructions in the third post.
https://drive.google.com/open?id=1-p7sknnber8pc9ya7ojpkvcltuwlgnri
Click to expand...
Click to collapse
04.08.2018 #3
i compiled the sony 51.1.a.4.265 stock kernel.
I compiled the normal bootimage with the sony stock kernel and the sony aosp build sources, to test if it is bootable.
I did the same with the omni 8.0 sources and the sony stock kernel.
I uploaded them with the file ending "-with-stockkernel.img"
i don't know, if the stock kernel is compatible with the sony aosp or the omni sources.
Click to expand...
Click to collapse
04.08.2018 #2
i compiled the normal bootimage with the sony aosp kernel and the sony aosp build sources, to test if it is bootable.
sony-aosp-8.1-04-08-2018-bootimage.img
Click to expand...
Click to collapse
04.08.2018
i recompiled the sony aosp 4.9 after its change to 'beta'.
I recompiled omni 8.0 twrp bootimage and recoveryimage with it.
Please test it and provide a feedback.
Ps: Omni 8.0 because since the last 'repo sync' i am not able to compile 8.1 anymore because of missing framework lib dependencies.
Click to expand...
Click to collapse
01.08.2018
i was able to compile the standard recovery with the sony 4.9 aosp kernel for the xz2.
I also compiled a bootimage and a recoveryimage with twrp with the sony 4.9 kernel and the omni sources.
Please test it and provide a feedback.
Click to expand...
Click to collapse
30.07.2018
the build is not working.
It seems, that we need to wait for sony to stable their asop kernel on github (e.g. To announce, that the xz2 is now a part of the open source project.)
Click to expand...
Click to collapse

Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it

mitpio said:
Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it
Click to expand...
Click to collapse
Could you tell me, which error message you get?
Or does nothing happen?
Did you unlock your bootloader?
Do the command
"fastboot devices"
(Without "")
Will it ahow your device with a number?
_______________________________________
Or if you need to get into the Fastboot Mode
Connect your device to your PC and write
"adb devices"
This should show you your device and a number.
Then you can do
adb reboot bootloader
And choose the fastboot mode.

entering fastboot mode xperia xz2
mitpio said:
Unfortunately, trying to run but the command does not enter you can write exactly step by step how to do it
Click to expand...
Click to collapse
Switch off the phone. Press and hold the Volume Up button
Connect to your PC using a USB Cable while holding down the Volume Up button on your Xperia XZ2
Before plugging in the USB cable on your Xperia XZ2 make sure that the other end of USB cable is already connected to the PC.
Wait till the LED turns into blue (the volume up button has to be pressed all the time till you see the blue led). Blue LED -> no more need to press the volume up button. Now you are in fastboot mode.
Using Linux do the following: open a terminal, type 'sudo fastboot devices' (without the quotes) (make sure before that you have fastboot installed on your linux box).
The output should be something like: QV7016A31E fastboot
The procedure should be very similar using windows (without using the sudo command), but I never tried it.

Ok, thanks, I'll try
Wysłane z mojego H8266 przy użyciu Tapatalka

mitpio said:
Ok, thanks, I'll try
Wysłane z mojego H8266 przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you using linux or windows?

windows

mitpio said:
windows
Click to expand...
Click to collapse
https://lifehacker.com/google-finally-lets-you-download-adb-and-fastboot-as-st-1790840830
https://www.desinerd.co.in/how-to-adb-and-fastboot-windows-mac-linux/
https://thedroidarena.com/best-adb-fastboot-commands-list-android/
https://wiki.lineageos.org/adb_fastboot_guide.html

Unfortunately this build seems not working, it did something out of an ordinary boot though.
Here's what exactly what I did:
1. The phone is unlocked, model H8266.
2. Shut down and get into fastboot mode, with blue LED on.
3."fastboot boot xz2_twrp.img" and get it booting.
and this is what I observed:
1. Screen turns on with Blue LED on, diaplaying "Your device software cannot... Blablablah".
2. After 5 seconds the screen turns off, but the blue LED is still on.
3. After around 20 seconds the screen turns on again with "SONY" logo, blue LED is still on.
4.About 5 seconds later, Blue LED turns off.
5.Again about 10 seconds later, screen turns off.
6.The red LED blinked a few times, with two times of vibration.
7.Screen turns on with "SONY" logo, then it's totally an ordinary boot into Android.
Hope the feedback will help.

yanke928 said:
Unfortunately this build seems not working, it did something out of an ordinary boot though.
Here's what exactly what I did:
1. The phone is unlocked, model H8266.
2. Shut down and get into fastboot mode, with blue LED on.
3."fastboot boot xz2_twrp.img" and get it booting.
and this is what I observed:
1. Screen turns on with Blue LED on, diaplaying "Your device software cannot... Blablablah".
2. After 5 seconds the screen turns off, but the blue LED is still on.
3. After around 20 seconds the screen turns on again with "SONY" logo, blue LED is still on.
4.About 5 seconds later, Blue LED turns off.
5.Again about 10 seconds later, screen turns off.
6.The red LED blinked a few times, with two times of vibration.
7.Screen turns on with "SONY" logo, then it's totally an ordinary boot into Android.
Hope the feedback will help.
Click to expand...
Click to collapse
Can you give use the entire Message of "Your device software cannot.."?

MartinX3 said:
Can you give use the entire Message of "Your device software cannot.."?
Click to expand...
Click to collapse
Well, it's just the same warning as the bootloader is unlocked, "Your device software cant' be checked for corruption, please lock the bootloader", quite common after a bootloader unlock.

I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/

MartinX3 said:
I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/
Click to expand...
Click to collapse
Tried to get log during the recovery booting but failed.
By issuing "adb logcat > logcat.txt" at the second terminal while booting the device from fastboot to the TWRP, it doesn't output anything when it's trying to boot the TWRP, but after the failure boot of TWRP, it does catch logs of an ordinary boot. Which means the adb works fine, while the TWRP doesn't give out any logs.
---------- Post added at 03:01 PM ---------- Previous post was at 02:27 PM ----------
MartinX3 said:
I should compile the Android 8.0 kernel with the Omni 8.0 sources, instead of 8.1 I think.
I also can't use the Sony Kernel 4.9.116 on Github, because it is not finish and stick with the delivered Kernel 4.9.65 from the July update.
(It is hard to test without an unlocked phone, hehe)
@yanke928
Can you use a second terminal to use
adb -d logcat &> log.txt
OR
ddms (in the android sdk)
while entering the fastboot boot cmd
to look, if it will give us any logs?
There is also a xda guide
https://www.xda-developers.com/guide-on-using-adb-logcat-and-ddms/
Click to expand...
Click to collapse
I've found that I did a stupid thing, model confused.
Seemed you've compile it for H8266 for Chinese Mainland market, while I have H8296, HK version, but I don't think this will matter somehow since the phone of HK version and Chinese version can be flashed with each other's firmware. Also, if you're Chinese, you can communicate with me directly without English

yanke928 said:
Tried to get log during the recovery booting but failed.
By issuing "adb logcat > logcat.txt" at the second terminal while booting the device from fastboot to the TWRP, it doesn't output anything when it's trying to boot the TWRP, but after the failure boot of TWRP, it does catch logs of an ordinary boot. Which means the adb works fine, while the TWRP doesn't give out any logs.
---------- Post added at 03:01 PM ---------- Previous post was at 02:27 PM ----------
I've found that I did a stupid thing, model confused.
Seemed you've compile it for H8266 for Chinese Mainland market, while I have H8296, HK version, but I don't think this will matter somehow since the phone of HK version and Chinese version can be flashed with each other's firmware. Also, if you're Chinese, you can communicate with me directly without English
Click to expand...
Click to collapse
I am also using the H8296 HongKong device, because of the 6GB ram, but I installed the H8266 German firmware on it.
@spirit-eh got the same error, but I don't know his device.
PS:
I am still downloading the minimal platform_manifest_twrp_omni on 8.0 branch, before I can compile it again.
Many stuff to download and I got only 5Mbit internet on my vacation. :silly:
Edit:
A notable difference between the XZ2 image and the XA2 image is the kernel size
XZ2 kernel 15.3 MB
XA2 kernel 46 MB
Maybe he compiled the AOSP one from github.
Edit2:
I assume hardly, that I need to wait for the XZ2 to be added to the Sony open source programm.
So I can use the AOSP 8.1 kernel, instead of this hacked thing delivered in the Sony open source downloads in their site.
The XA2 twrp maintainer did the same.

An older version of twrp does not work on xz2 (H8216) ? @MartinX3

Pandemic said:
An older version of twrp does not work on xz2 (H8216) ? @MartinX3
Click to expand...
Click to collapse
TWRP 3.1 introduced support for A/B-Devices.
TWRP 3.2.0 introduced the Android 8.x compatibility and 3.2.1 and 3.2.2 included important fixes.
I wouldn't try an older version.
I also need to compile TWRP from source with my collected config files to work with the XZ2.
(TWRP need to compiled for every device on its own).
Now I try to compile it with OMNI 8.0 instead of 8.1, because it is a hacky 8.0 kernel, which I need to use.
(Sony's Android 8.1 AOSP 4.9 kernel is not finished.)

01.08.2018
I was able to compile the standard recovery with the Sony 4.9 AOSP kernel for the XZ2.
Click to expand...
Click to collapse

MartinX3 said:
01.08.2018
Click to expand...
Click to collapse
Also for H8216 bro ?
Btw see pm

Related

Flashable TWRP v2.8.7.0 for Sony Z3+ E6553 Ivy_Kitakami

Introduction
Disclaimer: While this TWRP has been tested by myself on my own device to flash, wipe and backup, I make no warranties as to it's performance. Use at your own risk.
WARNING: flashable version contains a kernel boot image which will be flashed to your device along with the recovery image.
Click to expand...
Click to collapse
Installation instructions
This recovery image is for the E6553 single SIM Z3+. Do not use it on another model.
This recovery 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.
DO NOT enable MyXperia functionality if you've unlocked your bootloader. You will brick your device.
This first download of this recovery image CANNOT be flashed to your phone and must be used in fastboot mode only
The second download is a flashable recovery
Use the first version to flash the second dual-boot.zip version
Unzip the recovery.zip file to extract the recovery.img file to use in fastboot mode
Code:
C:\>adb reboot bootloader
C:\>fastboot boot recovery.img
C:\>adb push dual-boot.zip /sdcard/dual-boot.zip
C:\>adb push dual-boot.zip.md5 /sdcard/dual-boot.zip.md5
Click to expand...
Click to collapse
Now use the TWRP install feature to install dual-boot.zip. Follow the prompts of the Aroma graphical installer.
CAVEAT: this extends the boot time by about 5 - 10 seconds as ramdisk images need to be unpacked and there's a wait on a keypress to determine whether to enter recovery mode. In order to boot into recovery, press power on. When you see the yellow LED come on then press the down volume button once or twice. You will then boot into TWRP.
NOTE: the dual-boot.zip installs a new 28.0.A.8.251 kernel. If you're using the autoroot kernel from Devries you will need to flash SuperSU to re-root your device
This dual boot/recovery works by flashing the recovery image to the FOTAkernel partition. A custom ramdisk image contains the normal boot image. If the down volume keypress is detected, then the recovery ramdisk is automatically extracted from the FOTAKernel partition and flow of control switches to recovery. If no keypress is detected then the normal ramdisk is extracted and normal android boot ensues.
Those of you who installed version 1.0 please download and install this version 1.1 to fix the error with the startup of the trim area daemon
Download
Binary
Fastboot TWRP Recovery Image v2.8.7.0-e6553-1.0 for Z3+ E6553
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 (MD5: 52d4b7d406308dbd457e8b94210b7c87)
Flashable TWRP Recovery Image v2.8.7.0-e6553-1.1 for Z3+ E6553 - MD5
Sources @ github
device_sony_kitakami
device_sony_ivy
Click to expand...
Click to collapse
Changelog
Code:
Current changelog: -- 29 September 2015
[new] v1.1 fix up problem in combined ramdisk preventing trim area daemon from starting correctly
[new] Flashable recovery - 28 September 2015
[new] Fixed various sys/class issues so that CPU temperature and LED / backlight control work correctly
[new] Updated to use 28.0.A.8.251 kernel (as opposed to the AOSP kernel)
[old] Initial release - 10 September 2015
Click to expand...
Click to collapse
Thanks To
The regular contributors to the Z3+ forum, among others @[NUT], @ChrisJ951, @DHGE, @Devries, @zxz0O0, @Venkat Kamesh, @AndroPlus, @Sacktreter who pass on knowledge and who make the forum a lively and cooperative place
Click to expand...
Click to collapse

People who installed version 1.0 of the Flashable TWRP must please update to version 1.1 to correct a bug.

Awesome work.
Glad you were able to get the screen working for it! Boots up fine w/o issue for me

This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+

AMoosa said:
This is fantastic. Is there any way of getting this to work with a locked bootloader?
Sent from my Xperia Z3+
Click to expand...
Click to collapse
I'd venture to suggest that it's highly unlikely that locked bootloader recovery could work. The DM_VERITY is almost a guarantor of that. Just search for CONFIG_DM_VERITY or Verity in the Z3+ forums for more info.
Even if an exploit works, the second it modifies the system partition, the kernel panics and refuses to boot. The only way of preventing that is to flash a new kernel or edit the ramdisk to remove the verity key. And the only way to flash a new kernel / edit the ramdisk is to unlock the bootloader.

Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
This is correct behaviour. You're not actually flashing the recovery image, just temporarily booting a recovery kernel and associated ramdisk. Sony Xperia devices don't have a recovery partition, or more accurately, they don't have a bootloader than can check and load a boot image from a recovery partition.
Technically it's possible to make the boot image check for a ramdisk on another partition and use this instead of the normal ramdisk, but this is step two. Sony should be releasing an open recovery bootloader fairly soon for the Z3+ which will allow this recovery image to be flashed. It's already been released for other devices.
Until Sony releases open recovery for Z3+ or I spend the time trying to implement a feature that probably only has days or weeks of utility (until Sony releases the open recovery for Z3+) , you're stuck with a TWRP that you need to launch every time in fastboot mode.

On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot

elladroid said:
Thank you first for development... maazing!
I have unlocked the bootloader via Sony and then used an boot.img from Devries to root as root was my primary goal. I have flashbooted as per instructions the TWRP recovery.img that is provided here by the awesome dl12345 .
However the issue is that I am unable to boot to recovery after rebooting from TWRP. In other words the flashboot works and I am able to make a backup and use TWRP well but it doesn't seem to stick.
Am I doing something wrong. Should I have flashed a ROM first from xperfirm, Flashtools, and/or can I flash a kernel without it effecting the recovery. My knowledge is sketchy but I am totally up for testing if I can help.
Click to expand...
Click to collapse
New version now flashable so that you can boot into recovery...read top post carefully before using.

serrin85 said:
On the first screen immediately after the TWRP logo comes up, the battery is always being reported at being 50%. Sometimes the correct number is displayed when in the flashing screen. Otherwise works great!
Also, link to Sony Z3+ windows drivers
How to install unsigned drivers in Windows 8.1/10 with secure boot
Click to expand...
Click to collapse
Fixed in latest version

http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..

deecept said:
http://www.kz3.eu:18998/dual-boot.zip link gives 404 ..
Click to expand...
Click to collapse
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.

dl12345 said:
Yes, I've temporarily disabled the link while I resolve a problem relating to the trim area daemon not starting up due to some peculiarity of the dual boot ramdisk. I'll reinstate it as soon as I fix the problem.
Click to expand...
Click to collapse
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!

deecept said:
Oh, ok, sweet! Looking to flash this to my Z3+. More than happy to test if needed =) Great work on these!!
Click to expand...
Click to collapse
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks

dl12345 said:
Download back online and problem fixed
Those who downloaded the 1.0 please download this 1.1 version and install to correct the problem with trim area daemon startup. Thanks
Click to expand...
Click to collapse
HI dl12345,
this recovery support Dual model? E6533

hi.question...i get remote: dtb not found error when trying to boot the recovery..any ideas?

didnt get a thing... how do i install?

please, release TWRP for 6533 too
we need custom recovery so bad

Dathrex said:
please, release TWRP for 6533 too
we need custom recovery so bad
Click to expand...
Click to collapse
Pleaseee ????

Brother, please, help us with twrp to E6533, please.
Enviado de meu E6533 usando Tapatalk

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?

[FLASHABLE] Latest Vendor + Firmware for Laurel_Sprout [V11.0.7.0]

Latest flashable Vendor + Firmware combos for Laurel_Sprout
While this shouldn't cause any harm to your device, if anything happens - that's on you. I'm not responsible for any harm to your device.
Those packages are made for custom ROMs only! They may break MIUI ROMs. They don't include boot/system/product/dtbo so you don't need to reflash anything!
To install just flash in recovery and reboot.
(If you used no-fde patch before you might need to reflash that)
Why should you update your firmware and vendor? To get latest security and stability patches from Qualcomm.
V11.0.7.0 - February 2020 Security Patch - Android 10:
Download: https://drive.google.com/open?id=1DOGUZqrgkJvU4hto-OOcofYcKCutHVeH
Mirror: https://mega.nz/file/pgl22Qha#llyjbpdDMrfdYN-K1ly4sv4B8mPVkv_PLQ6Zz78Dik8
First Android 10 Vendor for Mi A3. Pretty much everything is improved.
ONLY FLASH THIS IF ROM YOU'RE USING SAYS THAT IT REQUIRES ANDROID 10/Q VENDOR!
V10.3.13.0 - January 2020 Security Patch:
Download: Google Drive
Users on telegram reported improved battery life, fingerprint scanner improvements and multiple other improvements.
(On first boot your phone might stay on splash screen for a little longer than usual. No idea why this is happening)
V10.3.12.0 - December 2019 Security Patch:
Download: Google Drive

Can I flash this in Rooted TWRP stock rom?

m.h.mahadi said:
Can I flash this in Rooted TWRP stock rom?
Click to expand...
Click to collapse
Why would you when you can just install latest stock?

Thank you so much for sharing, I have a small question, this will safe to flash over havoc Os?

What about root on this one ? Can't manage to do it...

Kaissner said:
Thank you so much for sharing, I have a small question, this will safe to flash over havoc Os?
Click to expand...
Click to collapse
Yes
JohnKoffee said:
What about root on this one ? Can't manage to do it...
Click to expand...
Click to collapse
What do you mean? This just flashes latest vendor.img, it doesn't touch your existing root or system in general. You can just flash Magisk for root if you weren't rooted before

nullbytepl said:
Yes
What do you mean? This just flashes latest vendor.img, it doesn't touch your existing root or system in general. You can just flash Magisk for root if you weren't rooted before
Click to expand...
Click to collapse
Because I can't manage to root it nor install Magisk. Constant failure ( no such partition if I recall correctly). I try by using XiaomiTool.
EDIT: I found a way. I was using the wrong commands in Minimal ADB/Fastboot. Now I have root and Magisk.

Maybe you can help me to solve the same problem?
JohnKoffee said:
Because I can't manage to root it nor install Magisk. Constant failure ( no such partition if I recall correctly). I try by using XiaomiTool.
EDIT: I found a way. I was using the wrong commands in Minimal ADB/Fastboot. Now I have root and Magisk.
Click to expand...
Click to collapse
Could you kindly submit the commands that helped you get root and Magisk working? Cheers + thank you

Is this a stock ROM that can be flashed through TWRP recovery?

Barbiox Dogg said:
Is this a stock ROM that can be flashed through TWRP recovery?
Click to expand...
Click to collapse
Yes he says it in the op just to flash in recovery

Barbiox Dogg said:
Is this a stock ROM that can be flashed through TWRP recovery?
Click to expand...
Click to collapse
It doesnt flash everything, only vendor

V10.3.13.0.PFQMIXM - January 2020 Security Patch released:
Users on telegram reported improved battery life, fingerprint scanner improvements and multiple other improvements.
(On first boot your phone might stay on splash screen for a little longer than usual. No idea why this is happening)
Downloads are in the first post!

nullbytepl said:
V10.3.13.0.PFQMIXM - January 2020 Security Patch released:
Users on telegram reported improved battery life, fingerprint scanner improvements and multiple other improvements.
(On first boot your phone might stay on splash screen for a little longer than usual. No idea why this is happening)
Downloads are in the first post!
Click to expand...
Click to collapse
Was using ExtendedUI ROM before flashing. Now stuck on OrangFox Recovery. Tried flashing fastboot firmware. Now stuck on stock recovery.

krimstix01 said:
Was using ExtendedUI ROM before flashing. Now stuck on OrangFox Recovery. Tried flashing fastboot firmware. Now stuck on stock recovery.
Click to expand...
Click to collapse
1. Install twrp via fastboot
2. Install firmware, rom, twrp installer (in this order). Wipe dalvik
3. Reboot and wait
4. If it didn't boot hold power until phone reboots. Wait again. It should boot

nullbytepl said:
1. Install twrp via fastboot
2. Install firmware, rom, twrp installer (in this order). Wipe dalvik
3. Reboot and wait
4. If it didn't boot hold power until phone reboots. Wait again. It should boot
Click to expand...
Click to collapse
Can I ask md5 of the firmware+vendor file just in case?

krimstix01 said:
Can I ask md5 of the file just in case?
Click to expand...
Click to collapse
It probably wouldn't install if it was corrupted, but whatever:
8d197b1727716de7d49df9d2d281175e

nullbytepl said:
1. Install twrp via fastboot
2. Install firmware, rom, twrp installer (in this order). Wipe dalvik
3. Reboot and wait
4. If it didn't boot hold power until phone reboots. Wait again. It should boot
Click to expand...
Click to collapse
Tried this, stuck in rebooting into TWRP. I am sweating like crazy right now I wish I could fix this.
---------- Post added at 10:54 AM ---------- Previous post was at 10:23 AM ----------
krimstix01 said:
Tried this, stuck in rebooting into TWRP. I am sweating like crazy right now I wish I could fix this.
Click to expand...
Click to collapse
Ok so after chatting in Telegram I got it to work. I flashed the vendor+firmware, then the no_fde (not the no_fde10, just the no_fde), then rebooted. It worked hahaha.
Credits to pheno1992 of telegram

nullbytepl said:
Latest flashable Vendor + Firmware combos for Laurel_Sprout
While this shouldn't cause any harm to your device, if anything happens - that's on you. I'm not responsible for any harm to your device.
Those packages are made for custom ROMs only! They may break MIUI ROMs. They don't include boot/system/product/dtbo so you don't need to reflash anything!
To install just flash in recovery and reboot.
Why should you update your firmware and vendor? To get latest security and stability patches from Qualcomm.
V10.3.13.0.PFQMIXM - January 2020 Security Patch:
Download: Google Drive
Users on telegram reported improved battery life, fingerprint scanner improvements and multiple other improvements.
(On first boot your phone might stay on splash screen for a little longer than usual. No idea why this is happening)
V10.3.12.0 - December 2019 Security Patch:
Download: Google Drive
Click to expand...
Click to collapse
Can I flash it over EU rom?

addidas_85 said:
Can I flash it over EU rom?
Click to expand...
Click to collapse
No, just flash full rom recovery package

krimstix01 said:
Tried this, stuck in rebooting into TWRP. I am sweating like crazy right now I wish I could fix this.
---------- Post added at 10:54 AM ---------- Previous post was at 10:23 AM ----------
Ok so after chatting in Telegram I got it to work. I flashed the vendor+firmware, then the no_fde (not the no_fde10, just the no_fde), then rebooted. It worked hahaha.
Credits to pheno1992 of telegram
Click to expand...
Click to collapse
Which were exactly the steps? vendor&firmware+no_fde+rom+twrp installer?
Edit: Nvm, I just found how boot

[ROM][Alpha-3][UNOFFICIAL] LineageOS-16.0 For dragon (6/19/2020) 4.9 kernel.

[UNOFFICIAL] LineageOS-16.0 For Dragon 4.9 kernel.
The system is built on the basis of the 4.9 kernel and drivers from Nvidia Shield TV.
Of the pluses I noticed, Play 2 / 4k video on YouTube and from files.
To install this firmware you need your own version of TWRP. You can download TWRP here.
Android 9.
Known issues:
- There is no LP0 sleep (standby) mode.
- There is no Camera.
- SELinux - permissive !
Works:
- Wi-Fi and BT
- Sound speakers, headphones, via BT.
system-as-root (SAR)
Fresh Installation / Upgrade from any other ROM:
1. Boot into TWRP
2. Wipe SYSTEM and DATA partitions ! (If you are encrypted, pls format DATA partition !)
3. Install ROM.zip
4. install gapps (arm64)
5. Wipe CACHE and DAVLIK
6. Reboot into system
Download ROM Alpha1
Download TWRP
LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM Alpha3
- The ROM does contain it's own vendor.img !
Links to the sources
kernel 4.9
platform/dtb
Kernel 4.9 drivers
Kernel 4.9 nvgpu
Vendor
Device nvidia dragon
Thanks @webgeek1234 and CM-Shield team, for the source.
Thanks @michie for testing rom.
If someone wants to help finish the sound support in the kernel and the system, write, I will help you how to start the assembly yourself.

Thank you very much.
This is really an important refresh for the software base.
I think that this new kernel can do wonders on our device.

LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM

if sound is working can you make it work on linux with 4.9?

mi_guel said:
if sound is working can you make it work on linux with 4.9?
Click to expand...
Click to collapse
If you mean the mainline kernel, then the answer is no.
If you are about Linux for Tegra at 4.9 then this is possible.

Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Good work
Gesendet von meinem Pixel 2 XL mit Tapatalk

Vartom said:
LOS-16 based on kernel 4.9 nvidia Alpha 2.
Changes
-Added sound through speakers, microphone.
-Blocked sleep mode in the kernel. Now the tablet does not freeze after turning off the screen.
Installing images from the archive via fastboot or twrp.
Download ROM
Click to expand...
Click to collapse
Glad to see most function works!good job!

The recovery here doesn't seem to work.

almightysiman said:
The recovery here doesn't seem to work.
Click to expand...
Click to collapse
What exactly does not work?
Encryption does not work. I checked the firmware installation.

Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.

almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.

michie said:
Try downloading the recovery again, sounds like it's corrupt. It should work both ways.
Click to expand...
Click to collapse
Tried so many time,still no luck,maybe I should keep trying.

Vartom said:
What exactly does not work?
Encryption does not work. I checked the firmware installation.
Click to expand...
Click to collapse
Finally get alpha2 working,one question,Can I flash magisk to root It?

almightysiman said:
Finally get alpha2 working,one question,Can I flash magisk to root It?
Click to expand...
Click to collapse
You can, but magisk will not work. This is a real SaR.

Vartom said:
You can, but magisk will not work. This is a real SaR.
Click to expand...
Click to collapse
So root is not possible at the moment?

almightysiman said:
So root is not possible at the moment?
Click to expand...
Click to collapse
Yes. To be able to get root, I have to make a special version of the firmware.

Vartom said:
Yes. To be able to get root, I have to make a special version of the firmware.
Click to expand...
Click to collapse
Thanks for making such effort!It's truly a good kernel,I already feel much smooth than other rom.

almightysiman said:
I try fastboot Flash recovery and can't boot into recovery,I am not sure what I did wrong.
Edit:I also tried to flash recovery in 3.3.1.2 recovery,then when I tried boot into your recovery,It get black screen and go back to bootloader.
Click to expand...
Click to collapse
i used it with fastboot boot command, not flash, worked fine, and the rom it's quite snappy

LOS-16 based on kernel 4.9 nvidia Alpha 3.
Changes
-Added sound through headphones.
Installing images from the archive via fastboot or twrp.
Download ROM

Hello friends, can you please take notice of the following thread for the future of development of our device?
https://forum.xda-developers.com/pix...xel-c-t4123463
Thank you in advance!

Question twrp

Hello, tell me please, is there a working TWRP for the realme s21 device?

leon2299 said:
Hello, tell me please, is there a working TWRP for the realme s21 device?
Click to expand...
Click to collapse
Yes, and here is the source.
It is not fully tested, but i have installed RealmeUI2 .ozip firmware with it (and i externally needed to flash rui2 recovery in order to boot), i currently use rui2 and my phone is rooted.
The twrp is for android 10 only, afaik there is no one for android 11 yet.

MrMiyamo said:
Yes, and here is the source.
It is not fully tested, but i have installed RealmeUI2 .ozip firmware with it (and i externally needed to flash rui2 recovery in order to boot), i currently use rui2 and my phone is rooted.
The twrp is for android 10 only, afaik there is no one for android 11 yet.
Click to expand...
Click to collapse
thanks, is it possible to somehow collect it into a recovery file

leon2299 said:
thanks, is it possible to somehow collect it into a recovery file
Click to expand...
Click to collapse
I am poor at building recovery from source, so you can get in touch* with him.
*(check his github overview)

ok, I'll think of something

hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check

leon2299 said:
hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check
Click to expand...
Click to collapse
You can use
dd if=/path/to/TWRP.img of=/dev/block/platform/bootdevice/by-name/recovery
Than run "reboot recovery" to check, if it boots congrats, else you can just reboot device by holding 3 key for 10 seconds, the recovery will become stock after reboot, to keep recovery there is a magisk module.
Note that, there is 2 branch in this recovery, android 10 one works, but 11 is not working

MrMiyamo said:
You can use
dd if=/path/to/TWRP.img of=/dev/block/platform/bootdevice/by-name/recovery
Than run "reboot recovery" to check, if it boots congrats, else you can just reboot device by holding 3 key for 10 seconds, the recovery will become stock after reboot, to keep recovery there is a magisk module.
Note that, there is 2 branch in this recovery, android 10 one works, but 11 is not working
Click to expand...
Click to collapse
the fastboot worked, it was necessary to flash Android 10 of the latest version 53, went into the fastboot by holding the power button and the minus adjustment button, tried to flash the samples, as a result, the TWRP splash screen hangs and nothing, the phone does not respond to the buttons, to the tapas too, but already at least something, there is a twrp screensaver
these three created recovery, the twrp screensaver hangs, they need to be brought to mind

can I flash these through MTK clint?
leon2299 said:
hello, there are tvrp samples, I need to check, fastboot stopped working for me, and twrp needs to be checked, there is a result, I need to check
Click to expand...
Click to collapse
and which one should I flash

Zartazor said:
can I flash these through MTK clint?
and which one should I flash
Click to expand...
Click to collapse
Yes, twrp 10 I found worked for Android 10
I am working on the fastboot issue for 11, as I did the same trick on my android 10 USB serial error, just trying to remember exact line of code I used lol
But basically it involves using magisk, magisk, module magisk props config, and having that insert the serial number where it's needed without actually inserting to build.prop.
I'm back home tonight where I will be able to work in it more

I have flashed the TWRP from android 10 and updated it to android 11 GSI
TWRP is working just fine

But is fastboot still working that is the question

smiley.raver said:
But is fastboot still working that is the question
Click to expand...
Click to collapse
Yes it does

Develop Bugs

welcome