I will be posting my kernel builds here for convenience.
Pre-requisite
Unlocked bootloader with TWRP Recovery installed.
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works
Features
- Stock based kernel with DT2W enabled.
- Forced encryption disabled.
- Passes Safetynet out of the box.
- Fully working camera (Pie kernel-no DRM fix needed for camera).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Flash zip in recovery (don't just extract boot.img as zip has system files to enable DT2W)
Kernel Sources
https://developer.sony.com/develop/open-devices/downloads/open-source-archives
Note. Kernel is compiled as per stock. DT2W is enabled in the DTB, the same parameters as used by the Loire platform.
Downloads
G8141_DT2W-41-kernel.zip
G8142_DT2W-41-kernel.zip
Kernel Requests.
Post the kernel.sin and I will patch it and add it to the OP.
Kernel Requests: View attachment kernel-G8142-205.zip thx !
oneheart said:
Kernel Requests: View attachment 4522264 thx !
Click to expand...
Click to collapse
Added, thanks. Please test and report back (I only own G8141).
shoey63 said:
Added, thanks. Please test and report back (I only own G8141).
Click to expand...
Click to collapse
if i need flash the drmpatch.zip ？
oneheart said:
if i need flash the drmpatch.zip ？
Click to expand...
Click to collapse
Yes, it's required.
it work on G8412 ， thx ！
How can I update to 205 without losing my data?
SilverGamer_YT said:
How can I update to 205 without losing my data?
Click to expand...
Click to collapse
Flash only system.sin - nothing else. Then boot to recovery and flash drmpatch.zip, kernel.zip and then Magisk if you need it.
Reboot and you are done.
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
karrouma said:
@shoey63
dual sim kernel have a problem with wifi.
wifi is off didn't turn on
Click to expand...
Click to collapse
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
shoey63 said:
Kernel itself is unmodified, and ramdisk changes don't touch wifi settings at all. Seems to be a hardware or software problem with Sony sd835 as per various complaints here https://talk.sonymobile.com/t5/Xperia-XZ1-Compact/Wifi-connection-problem/td-p/1315030
Adding to the confusion is that the issue is sporadic, intermittent and apparently device specific. Some users suffer badly, whereas others have no problems.
At any rate, there is nothing I can do about it.
Click to expand...
Click to collapse
Thank you for you work.
One guy tell me to flash CE1 firmware
I will trt
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Castiglionais said:
Hi, thank you for time to do this kernel @shoey63 nice work
Just a little beginner's question ... what is the best kernel for my rom stock (yours ot androplus kernel),
from what I read your kernel is not changed at all ?
Click to expand...
Click to collapse
For tweaking and double tap to wake - Androplus. For the stability of stock - mine.
shoey63 said:
I will be posting my kernel repacks here for convenience.
Pre-requisite
DRM fix must be in place before rebooting to avoid a soft brick.
This DRM patch which was available in sToRm//'s free Xperifix version still works.
Features
- Pure stock kernel with only ramdisk changes to enable DRM fix plus solve SafetNet and Magisk issues.
- Passes Safetynet out of the box.
- Fully working camera (No green Pic's).
- Flashable zip with no need to extract boot.img
- Compatible with any version of Magisk.
Installation
Flash drmpatch.zip then kernel.zip.
You can then flash Magisk if you require it.
Camera doesn't depend on it though.
Downloads
drmpatch.zip
G8141-205
G8142-205dual
Click to expand...
Click to collapse
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
YasuHamed said:
sir what extra this forbidden xperifix does?
i mean if i have maple kernel and those 3 files from system.sin, and using @serajr 's modified script of TOBIAS , I create one boot.img file and flash it and flash the drmpatch.zip (given) here by you via twrp...
WILL it work?
i don't have xzp
if okay, plz reply
Click to expand...
Click to collapse
Not quite OK. You also need to patch init.environ.rc as per this post https://forum.xda-developers.com/showpost.php?p=74310718&postcount=43
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You could try this one. It is from M-ROM v1.5, a Chinese rom.
I would flash the kernel.zip again, then the SuperSU.zip then the drmpatch.zip and wipe cache and dalvik and see how you go.
jianlin3062 said:
I tried flashing SuperSU 2.79 and 2.82 onto my G8142 which runs oreo but it always results in the phone getting stuck at the Sony logo right after the bootloader unlock warning.
Does the kernel not need to be patched for SU to work?
Click to expand...
Click to collapse
You must try this version this is created for xperia phones:https://forum.xda-developers.com/attachment.php?attachmentid=4164510&d=1496008012
help
I can not understand the order in which I have to do things
Should I unlock the bootloader and then?
I must install the recovery by adb or first the kernel
I come from samsung and the difficulty here is greater and there is much less information, if someone could help me I would appreciate it. I have the latest version of oreo the .205
Related
Note: I have only tested this on Mate 10 Pro, so I don't know if it works on Mate 10. Title will stay until tested
Kernel downloads: https://github.com/Ante0/BKL_OREO_EMUI8/tree/master/releases
Source used: https://github.com/Ante0/BKL_OREO_EMUI8
Currently upstreamed to: 4.4.130
4.4.60 and above contains Blu_Active governor
Windows: https://mega.nz/#!NTgEFKiZ!4nB6QuznpI-Q4R8mtJENZ34KV4YNr6aUIlMTyTYOQcQ
Download Kernel_Pack_tool_windows.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_windows folder, open a command prompt in the extracted folder and run "pack_kernel.bat 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
Linux: https://mega.nz/#!Ne5mXATT!FXjWsnY61VewihTWagrJ09G6jv15_y4BlS_R0HDQ5UM
Download Kernel_Pack_tool_linux.zip, extract.
Download desired Image_4.4.*.gz, put in the Kernel_Pack_tool_linux folder, open a terminal in the extracted folder and run "./pack_kernel.sh 2018-08".
This will create an image for patch level 2018-08, change to your current patch level (Settings->About->Android Security patch).
Flash image using fastboot. Example: fastboot flash kernel Kernel_4.4.53.img
If you get permission errors you may have to chmod +x pack_kernel.sh and mkbootimg
UPDATE: I have changed sources to use Honor View 10 instead as camera works here (and everything else) and I'm also upstreaming it. Currently at 4.4.52: https://github.com/Ante0/BKL_OREO_EMUI8.0
Downloads will come soon. I will make a new script to change patch level instead of changing each image (from 2017-12 to 2018-09) as it takes time and space on my mega.
This does not set selinux to permissive all the time, you have to use 'setenforce 0' to enable permissive, this is to only enable it when you need it.
All this does is let us use 'setenforce' again, since Huawei decided to disable it in Oreo.
Could be useful for V4A and other sound mods, since they usually require permissive. Or anything else that could need permissive.
V4A still doesnt work with permissive, something else needs fixing
Note: This is for Security Patch level 2018-01. If yours is 2017-12 or 2018-02 you will bootloop.
This is because --os_patch_level must match ro.build.version.security_patch in /vendor/build.prop
If so you need to repack kernel and change --os_patch_level to match your version.
I will keep my github updated with security patches from Google, but if Huawei changes something in their own source it won't be in this kernel.
Mate 10/Mate 10 Pro downloads: https://mega.nz/#F!FbBBCaIS!YYH94l12su3HcsbwIqDygg
(Check Settings -> About - "Android security patch:" to get the correct patch level.
If it says 1 January 2018, download and flash 201801 kernel. 1 February 2018: 201802 and so on.)
Flash using: Fastboot flash kernel kernel.img
Mate 10 Kernel source: https://github.com/Ante0/ALP_OREO_EMUI8
Mate 10 Pro Kernel source: https://github.com/Ante0/BLA_OREO_EMUI8.0
Update 10/2: Added Wireguard support, for those who like to use VPNs.
Added some simple build scripts
Please note that portrait mode in camera has been broken with custom kernel since BLA-L29C432B137
Not working on BLA-L09, error mode boot image load failed.
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
smariob said:
Will try on ALP and report later
Edit: Failed flash due partition lenght get error
Click to expand...
Click to collapse
Bordo_Bereli51 said:
Not working on BLA-L09, error mode boot image load failed.
Click to expand...
Click to collapse
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
ante0 said:
Fastboot flash kernel kernel.img
Its kernel, not boot image or ramdisk.
Click to expand...
Click to collapse
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
@ante0
Thank you for the new kernel!!!
Keep up the good work dev :good::good::good:
smariob said:
Ok will try again. As I'm writing this now I have a new concern.
My initial thought is remove magisk root, then flash kernel and then flash magisk again. Am I right?
Click to expand...
Click to collapse
No. Kernel is separate. Magisk goes in ramdisk.
Before oreo ramdisk and kernel was merged in the boot partition, but now they're split into ramdisk and kernel partitions.
So you only need to flash kernel to kernel.
Congrats for the first Mate 10 kernel, mate![emoji482]
noob question here: setenforce 0 is written in terminal or adb? how to?
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Bordo_Bereli51 said:
Ok worked. Thanks ante0. Guys if you have magisk, search for permissive script for magisk. It sets at every boot to permissive
P.S Now I have bootloop, phone started at first boot, but at the second boot its now in bootloop, always restarting.
Click to expand...
Click to collapse
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Saadkhalid786 said:
noob question here: setenforce 0 is written in terminal or adb? how to?
Click to expand...
Click to collapse
terminal.
Or use the Magisk Module as Bordo_Bereli51 suggested.
Though if you don't have any app or something that needs permissive it's no use in running it at all times.
ante0 said:
flash back stock kernel, and see if it helps. If not, it might be the Magisk module if you installed it.
You can "disable" magisk by flashing back stock ramdisk.
Please note that this is built from Huaweis sources, so we don't know how many bugs there are yet xD (Mate 9 kernel source broke camera for example)
Click to expand...
Click to collapse
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Bordo_Bereli51 said:
Disabled magisk by flashing stock ramdisk but did not help. Do you have any stock kernel for BLA-L09?
Click to expand...
Click to collapse
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
I am already doing that but wanted to know if he had stock but I am almost finished getting stock kernel
Pretoriano80 said:
@ante0 : I was looking at the source code and spotted this - > https://github.com/Ante0/BLA_OREO_E...rnel/drivers/huawei_platform/vibrator/drv2605 <- do you think it's possible to expose the vibrator controls, so we can increase vibration strength, which is awful on this device?
P. S. : Huawei says the kernel source code is based on 21/01/2018 software build, so i guess is more recent than the one from B129 build, which is compiled on 28/12/2017.
---------- Post added at 11:47 ---------- Previous post was at 11:25 ----------
Download a FullOTA for your BLA-L09 device using Firmware Finder for PC.
Than use Huawei Extractor to unpack the update.app file, you will find the stock kernel image in there.
Click to expand...
Click to collapse
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
ante0 said:
According to Kconfig, it's not used. So there must be a vibrator elsewhere.
Click to expand...
Click to collapse
Yes, looks like that driver is disabled, but i still didn't found another vibrator/motor.
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Bordo_Bereli51 said:
lol When you guys download the HWOTA8 tools from this thread there is a image BLA_Kernel_Permissive. I flashed this as a kernel and it works now. Selinux is permissive. This kernel was already there since the upload. No one tried it to flash this file I think.
Click to expand...
Click to collapse
It's set to always permissive.
Edit: And for me it bootloops for some reason.
ante0 said:
It's set to always permissive.
Click to expand...
Click to collapse
Which is why I want it in order to get V4A working
I am on kangvip rom.
Bordo_Bereli51 said:
Which is why I want it in order to get V4A working
Click to expand...
Click to collapse
I've tried with permissive, doesn't work with the Magisk Modules...
You might have luck with installing to /system and /vendor manually.
Kangvip might be why the kernel is not working for you, they usually incorporate their own hacks.
*Only tested on TA-1032 but it should work on other models too*
Downloads:
Build 1:
https://mega.nz/#!qIhFkKia!AkUMvQJ0PGVnSePabTvOgO-oUAMZahlCNaZfy2gE4vE
This TWRP now supports removing data encryption on Oreo.
General Changelog for TWRP version:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Changelog:
Build 1:
- Initial release
What works:
- Touch
- OTG
- Backup (system.img backup doesn't work but don't worry, you can backup System and you'll be fine)
- Restore
- Flashing IMGs and ZIPs
What doesn't work:
- Battery percentage is incorrect (it's possible to fix but need some time)
- MTP (it's possible to fix but need some time)
- you tell me
For full backup you need to remove encryption so you can backup /data too.
If you're wondering why protect_f, protect_s, para and uboot partitions have 0MB it's because these partitions have less then 1MB.
Comment if link need to be updated.
Credits:
@mohancm for Lenovo K4 Note TWRP
Screenshots:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Riadh300 said:
i can't install it with sp flashtools ... now i bricked my phone and i downgrated it to 7.1
Click to expand...
Click to collapse
i installed it without problems, tell me your device model and how you installed it.
Worst thing that could happen is that recovery got bricked, to recover simply flash new recovery. it worked for me, with twrp flash img, with flashify and with SP Flash Tool. Maybe you flashed it in wrong way.
Also please can someone flash/test this twrp so i can see does it work for others.
System and Data can be backed up and restored on oreo with this twrp?
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
ChalapathiRevanth said:
Hey! Why Ported One? I did upload the Twrp Recovery Source! https://github.com/ChalapathiRevanth/twrp_device_nokia_heart
You are Free to Compile It
Click to expand...
Click to collapse
Top.
Thank you
Reygal21 said:
System and Data can be backed up and restored on oreo with this twrp?
Click to expand...
Click to collapse
data can be backed up only after removing encryption, system can be backed up without problems.
As for restore, it works on Nougat (i restored whole rom when i tried substratum theme)
but i didn't tested for Oreo.
I think that will work on Oreo too because there is no change in partition mount points between Nougat and Oreo.
Update:
I found out that incorrect battery percentage and MTP are not kernel issue so it is possible to fix it.
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Nikola Jovanovic said:
Is it still ported, or you used twrp kernel source in new version ?
What is the diff between this and mediafire007 ver ? This second one can't find the thread about it.
Thank you Skabo !
Click to expand...
Click to collapse
it's ported from Lenovo K4 Note TWRP which have MT6753 CPU
Though i noticed that medifire007 is smother, especially when changing storage. This TWRP have latest TWRP version and touch works smoothly while on mediafire007 TWRP you need to wait in beginning to work.
Can this work on Nokia 1 with Android Oreo 8.1?
abdul_manan said:
Can this work on Nokia 1 with Android Oreo 8.1?
Click to expand...
Click to collapse
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
SkaboXD said:
no, but i can try to port it, i just need testers.
Edit: Bro you already have twrp for Nokia 1, just search xda Nokia 1 forum.
Click to expand...
Click to collapse
Thanks Bro! It worked! But there is a new problem Now. Here it is..
https://forum.xda-developers.com/nokia-1/help/stock-recovery-error-nokia-1-black-t3798928
Tested and working on TA-1028 variant with Android nougat. Installed SuperSU and everything seems okay. Thx dev:victory:
Is there any custom Rom and kernel for Nokia 3 .
Stock Nokia 3 Rom and kernel is really bad
Can i use for Nokia 3 locked bootloader???
How to install ?
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Umairali321 said:
please Post Nokia 3 TA1032 Android 8.1 Custom recovery
Click to expand...
Click to collapse
Doesn't work on 8.1? Did you tried it?
Kang kernel
By Sjll
Notice: Beware of bricking device!
This a new kernel for stock 10. It's aim to optimize the kernel and provide better user experience.
I had cherry-picked some commits from other SDM845 devices like M i8 and Oneplus 6T. So it's a fusion kernel, though I don't know whether these commits could improve our performance.
I share the source codes, so you could tweak the kernel by yourself. Ok, don't forget to share your work with us.
Download: Github
Note:
1. For XZ2, boot.img already included Magisk.
2 Internal problem is normal, ignore it.
CAF Version: LA.UM.8.3.r1-07600-sdm845.0.
Linux Version:4.9.206-r25-rel
Recommand to use EX kernel Manager
Feature:
1. GPU OC to 835 Mhz.
2. Thanks: Hide unlocked state from @j4nn
3. Qcacld wlan driver.
4. Remove useless drivers.
5. zram to lz4.
6. Increase priority of RT thread.
7. AVB flag removed.
8. WireGuard support.
9. Disabled some logs in kernel.
10. Newer CAF buff and Linux version.
11. Cpufreq and drm drivers optimization.
12. Schedutil optimization.
13. Energy model improved.
14. New I/O governor (Maple & Zen)
15. Blu_schedutil CPU governor( More Powersave ) Need to enable manually
16. IOsched optimization.
17. DTS eagle driver.
18. KLAPSE Color manager. Need EX kernel Manager
19. boeffla_wl_blocker supported.
20. adrenoboost supported, disable it by default.
21. etc..
How to flash:
HTML:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot boot.img
Vbmeta.img see Attach Files
If there is a dtbo.img, then:
HTML:
fastboot flash dtbo dtbo.img
I provide a new thermal configuration, see Attach Files, download it and replacing the same file in vendor/etc. You will get the full performance of SDM845.
Source code: Github
ROM OS Version: 10.0
ROM Kernel: Linux 4.9
Contributors
Sjll
Created 2020-02-26
FIRST! Muahahaha
Thank you like always.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Is it possible to port it on aosp10/los17 with osmosis anykernel?
thanks! can I flash on xz2 compact h8314?
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
It's the stock kernel
Completely incompatible with the SODP project
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
MartinX3 said:
FIRST! Muahahaha
Thank you like always.
Click to expand...
Click to collapse
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
nos1609 said:
Is it possible to port it on aosp10/los17 with osmosis anykernel?
Click to expand...
Click to collapse
No, this kernel is only for stock, not SODP.
nikkdib said:
thanks! can I flash on xz2 compact h8314?
Click to expand...
Click to collapse
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Faruk.ErdaL said:
Thank you for this! I got a slight increase in Antutu benchmark score, especially in GPU and UX tests. Hide unlock status is also working, Sony started to send me updates for system apps. Been using for an hour and it's smooth af. will update this comment if I encounter any issues or other improvements in longer term.
Click to expand...
Click to collapse
Thanks, if there is any bugs, feedback to me please. I will try to solve it.
Sjll said:
Thank you ,too, Martin!
I build a new twrp for 10. But I stucked at TWRP logo.
ADB seems works, but no authorized.
Here is the tree.
https://github.com/sjllls/android_device_sony_akari/tree/twrp-10
Click to expand...
Click to collapse
Yay
Nice, I wanted to look into TWRP at weekend
You could try to set
ro.debuggable=1
ro.adb.secure=0
Or build an -eng TWRP.
Sjll said:
No, you can't, but I will provide a version for xz2c after source code is updated to latest.
You could upload the boot.img of xz2c. I need it. Because I don't want to download the whole FTF firmware of XZ2c. It's too large.
Click to expand...
Click to collapse
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
nikkdib said:
thanks! this is the boot image of xz2c from stock italian firmware .532 (android 10)
https://drive.google.com/open?id=1aKZiVIa6T3k7ZJ7mGWw_hWPCHkkxzRAj
Click to expand...
Click to collapse
Done, try it and feedback, thanks.
Sjll said:
Done, try it and feedback, thanks.
Click to expand...
Click to collapse
i need to patch with magisk manager first if i want root yes?
nikkdib said:
i need to patch with magisk manager first if i want root yes?
Click to expand...
Click to collapse
Yes, you can. It should work fine with Magisk.
Sjll said:
Yes, you can. It should work fine with Magisk.
Click to expand...
Click to collapse
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
nikkdib said:
ok i patch with magisk and flash. for now all is fine. I will test. in next release you add more features? like more governor for cpu or undervolt?
Click to expand...
Click to collapse
Done, try V1.5 please.
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
After first crash files in /sys/fs/pstore giving you the crash reason
MartinX3 said:
After first crash files in /sys/fs/pstore giving you the crash reason
Click to expand...
Click to collapse
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Faruk.ErdaL said:
yes but it crashes when it says phone is starting... so I can't really get into my files and have to leave for university in 10 minutes, I'll give it another try in the evening and provide logs if possible
Click to expand...
Click to collapse
After crash go into Fastboot mode and flash the working kernel back (with magisk)
Then the device boots and you get the files
Just don't boot one time too much or the pstore will be wiped.
Faruk.ErdaL said:
Does the kernel already include magisk?
Edit: V1.7 crashed device after boot, gives the warning there's an internal problem with your device then reboots.
Click to expand...
Click to collapse
For XZ2, it already included Magisk. Internal problem is normal, just ignore it. All works fine for me.
Provide your phone type please.
Central project page
https://forum.xda-developers.com/xperia-xz2/development/recovery-twrp-3-3-1-0-t4074305
11.06.2020
Switch to TWRP 3.4.0
sodp twrp 2020-06 security patch level
stock twrp 2020-05 security patch level for firmware 52.1.A.2.1
Now both twrp should work without a ROM being installed (empty system/vendor/oem partitions) and still be able to decrypt your userdata.
Also the stock twrp touch should now always work instead of playing russian roulette.
Click to expand...
Click to collapse
13.06.2020
Thanks to the fixes in 3.4.0 we got now a TWRP with the following enhancements for STOCK and SODP:
- This TWRP will work with future 10.0 ROMs, you don't need a new build matching the security patch level of your ROM.
- You can install this TWRP again with the buildin ramdisk patcher. Please follow the installation instructions.
Click to expand...
Click to collapse
Please test and report back if you got any touch / decryption problems.
MartinX3 said:
13.06.2020
Please test and report back if you got any touch / decryption problems.
Click to expand...
Click to collapse
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
TacoLoco said:
@MartinX3
XZ2 Compact here, tried the Version from 0611 and 0613 and with both I got stuck at SONY Logo.. Where can I pull a log for you in this case?
Click to expand...
Click to collapse
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
MartinX3 said:
STOCK or SODP based ROM?
STOCK or SODP based TWRP?
You booted into fastboot with software and not with the hardware buttons?
And I hope you didn't flash it with "fastboot flash boot twrp.img"
you could try to press PWR+VolUP for a short time, then shortly after it should crash
Then you should be able to get the /sys/fs/pstore folder files in your system (needs root)
Or if that doesn't work maybe a dump of your TA partition.
You use a 10.0 ROM with kernel 4.14 (SODP) or kernel 4.9 (STOCK)?
Click to expand...
Click to collapse
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
TacoLoco said:
SODP Based ROM and TWRP, did enter bootloader with hardware keys.. I know this stands under known bugs but wouldnt it be more idiot proof to write this into the installation section as a separate step?
Thanks Martin for your ongoing dedication!
Click to expand...
Click to collapse
Aaaand added!
Nice to hear and thank you for your report!
MartinX3 said:
Aaaand added!
Nice to hear and thank you for your report!
Click to expand...
Click to collapse
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
cd /tmp/repackorig/ && /sbin/magiskboot hexpatch kernel 77616E745F696E697472616D667300
736B69705F696E697472616D667300 process endet with ERROR: 1
Error patching kernel.
Click to expand...
Click to collapse
It boots me to TWRP every time, I think this is related..
TacoLoco said:
Nice
But now running into the next issue, when executing "Fix Recovery Bootloop":
It boots me to TWRP every time, I think this is related..
Click to expand...
Click to collapse
What happens if you reboot the twrp and try it again?
Or if you flash magisk and try to boot?
Do you use a modified kernel?
Did you "fastboot flash boot twrp.img" by accident?
14.06.2020
Reuploaded the stock TWRP with a later touch kernel modules initialization.
Hopefully fixing the randomly happening not working touch.
Click to expand...
Click to collapse
Hi there,
what is 'sodp' please ?
moltes74 said:
Hi there,
what is 'sodp' please ?
Click to expand...
Click to collapse
It's described on the first page of the central project thread.
MartinX3, thanks for all your work!
I have a xz2c dual and, thanks to your guides, backed up the TA partition and flashed the latest Unofficial TWRP recovery with the up to date stock image.
My experience is that the problem with some boots not having the touchscreen working is still there. Fortunately, after rebooting you get a new chance ... and sometimes it actually works.
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
tanty0 said:
I used TWRP to install the latest Official LineageOS 17.1. It worked well. However, after that, TWRP was replaced by Lineage Recovery (?!) and I'm now unable to boot into recovery with the Unofficial SODP TWRP to flash it back.
Any guess of what could be the problem? Do you plan to provide a version which would work with the Official LineageOS 17.1 image?
Click to expand...
Click to collapse
Answering myself back. Yes, this is known and you have already stated that you plan to look at this whenever you find the time: https://forum.xda-developers.com/showpost.php?p=83172223&postcount=345 , and below ...
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
02.03.2021
Reuploaded the SODP TWRP with a workaround for Android 11 compatibility.
Click to expand...
Click to collapse
CHEIb00 said:
I'd like to flash my userbuild los 17.1... which file/version do I need? (Android 10>TWRP) Stock or SODP ??
Click to expand...
Click to collapse
It is currently not compatible with the official LOS 17.1 due to technical limitations by google.
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
levone1 said:
@MartinX3 - using twrp3.4 on eXistenZ Q, (stock-based 10), and working great, but...
- max brightness is too low. Can hardly see the screen in daylight. Any options?
- are there any newer TWRPs for XZ2c stock?
Thanks
Click to expand...
Click to collapse
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
MartinX3 said:
Is there no brightness setting?
Only behind the download link.
Since stock reached end of life there won't be any new twrp for it.
Click to expand...
Click to collapse
Max brightness as set in settings is very dim...
So today with some testers i managed to make root on OnePlus 8 Pro, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator).
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
TIPS:
You can get the stock boot images from the fastboot rom: Fastboot ROMs
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use the latest stable Magisk
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images:
https://www.androidfilehost.com/?w=files&flid=308380
or
https://sourceforge.net/projects/fastbootroms/files/OnePlus 8 Pro/Patched-Stock-Boot/
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
I want to specify somethings:
Codename:
OnePlus 8: instantnoodle
OnePlus 8 Pro: instantnoodlep
OnePlus 8 Pro 10.5.4BA (Europe) stock rom link: https://otafsg1.h2os.com/patch/amaz...ygen_15.E.13_OTA_013_all_2004111446_df409.zip
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
pijiman said:
First of all, thank you for the awesome work!
Could you explain a bit what are the modifications made to boot.img?
Click to expand...
Click to collapse
I just patched it with magisk, so it only contains in addition magisk
Wow, that was fast, thanks a lot guys
Before flashing the patched_boot.img you need to unlock the bootloader.
Tick the "Advanced reboot" under Developer options
Then reboot your device in bootloader-fastboot mode
fastboot oem unlock
Many thanks for the quick Root my Device
mauronofrio said:
I just patched it with magisk, so it only contains in addition magisk
Click to expand...
Click to collapse
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Awesome, I had a bit of a struggle trying to find the full stock ROM link, thanks.
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
pijiman said:
I have a follow up question: what are the features needed from Magisk and Magisk Manager that require the Canary release? I can't find anything in their changelog and my curiosity is getting the best of me
Click to expand...
Click to collapse
Canary builds are not needed.
xocomaox said:
Do you know if it passes SafteyNet with Magisk Hide enabled? Assuming not since Google now uses hardware signatures vs spoofable software ones.
Click to expand...
Click to collapse
Sure does
xByt3z said:
Sure does
Click to expand...
Click to collapse
That's interesting. Thanks!
Does this mean Google Pay still works? Thanks
l_p_4_7 said:
Does this mean Google Pay still works? Thanks
Click to expand...
Click to collapse
Yes.
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
SkyDragon dev is awesome! I had that on my LG G3!
xocomaox said:
SkyDragon dev is awesome! I had that on my LG G3!
Click to expand...
Click to collapse
Yeah due to increased price I am worried we wont get as much development on 8 Pro. I might get back into situation I was in on 7 pro 5g which had non existent development
Nekromantik said:
Great work!
Im just sad that my fav kernel devs from OP7P wont be purchasing 8 Pro so no Smurf or SkyDragon kernel!
Click to expand...
Click to collapse
feel free to compile them for us
I have a patched img for the global AA device! Would you like to add it to your post?