Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
About the project
Sony Stock Patcher is a minimal and easy transition from Sony's Stock ROM
(flashed directly from an FTF for example) to a modifiable ROM that can be modded as you like.
Built out of my evolutions of libbootimg for MultiROM to support Sony ELF bootimages,
a custom modified kernel based on Sony's copyleft with a minimal set of needed custom changes,
and an automated installation process to patch completely a Stock ROM,
this will allow you to use the Stock ROMs as you wish to.
Relevant features of Sony Stock Patcher
Using my Sony ELF 64bits port to libbootimg, Stock boot partition is automatically converted
Modified copyleft Stock kernel to support alterations and remove limitations
Patches the ramdisk to disable automatically Sony RIC security
Patches the fstab automatically for verity
Injects my init_sony project used on Sony custom ROM projects
Supports making the ROM usable as secondary MultiROM
List of changes made to the kernel
Disable Selinux trap security (allows to boot with stock ramdisk sepolicies)
Disable Device-Mapper verity (needed for example to patch system partitions)
Disable kernel modules forced validation (avoids failures on modules signature)
Disable coresight (unneeeded and irrelevant, just to avoid unsupported error logs)
Disable Sony RIC security (needed to use a recovery and alter /system, /data, ...)
Inline kernel modules compilation (to avoid kernel installation fragmentation)
Clearpad touchscreen updates for MultiROM UI
Minor kernel updates
Installation
Needed: Device has to be with an Unlocked Bootloader
Use Stock ROM or flash a clean FTF ROM from Nougat
Needs a working TWRP flashed into the FOTA partition (fastboot flash recovery...)
> Fully working TWRP builds : See below with downloads
Boot to TWRP (Power and Volume -)
Flash the relevant sony_stock_xz_patcher: n for 7.x
(Optional) Flash SuperSU by Chainfire if you want to have root access
Reboot to Android
Reasons to use this project ?
Unlocked Bootloader customizations allowed on Stock
Converts the bootimage to support systemless tools
Ability to root with tools like SuperSU
Retains the original Sony bootimage files
Minimal needed changes, no additional kernel mods
Downloads (Unlocked Bootloader only)
Xperia XZ : https://mega.nz/#F!K8kUDSaD!LNVmLKHANgwYPuc-aFO-Mg
Personal TWRP releases
TWRP 3.x.x : https://mega.nz/#F!bg9QhDzC!TTkhy2Fi6cNTZ1ojlmobRQ
Source code
Kernel sources - https://github.com/AdrianDC/kernel-sony-copyleft (branch 41.2.A.7.xxx)
libbootimg sources - https://github.com/AdrianDC/multirom_libbootimg (branch master)
init_sony sources - https://github.com/AdrianDC/device-sony-common-init (branch master)
MultiROM sources - https://github.com/AdrianDC/multirom_core (branch master)
TWRP sources - https://github.com/AdrianDC/twrp_development_sony/commits/device_sony_kagura (branch device_sony_kagura)
Sony Stock Patcher for Xperia XZ created also thanks to :
- Sony for their original copyleft kernel sources
- Tasssadar for the original libbootimg / MultiROM sources
- The XperiaMultiROM team for our evolution of MultiROM
- Everyone involved in testing it
XDA:DevDB Information
Sony Stock Patcher for Xperia XZ, Kernel for the Sony Xperia XZ
Contributors
AdrianDC
Source Code: https://github.com/AdrianDC/kernel-sony-copyleft
Kernel Special Features:
Version Information
Status: No Longer Updated
Created 2017-03-20
Last Updated 2020-08-15
Reserved
Changelog
Code:
Sony Stock Patcher for XZ - 23/10/2019
=================================================
* Update release to resolve 3.18 ramoops (o_v7.2.157)
> See commit 71d1aa14bdae1f38a56be10468556d43f108478a
Sony Stock Patcher for XZ - 08/09/2018
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.2.149/157 (o_v6.2.157)
Sony Stock Patcher for XZ - 19/05/2018
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.2.128 (o_v5.2.128)
Sony Stock Patcher for XZ - 24/03/2018
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.2.99 (o_v4.2.99)
Sony Stock Patcher for XZ - 12/03/2018
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.2.75 (o_v3.2.75)
Sony Stock Patcher for XZ - 25/12/2017
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.2.24 (o_v2.2.24)
Sony Stock Patcher for XZ - 17/12/2017
=================================================
* Upgrade to Oreo 8.0.0 41.3.A.0.401 (o_v1.0.401)
Sony Stock Patcher for XZ - 26/11/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.7.76 (n_v8.7.76)
Sony Stock Patcher for XZ - 25/09/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.7.65 (n_v7.7.65)
Sony Stock Patcher for XZ - 19/08/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.7.53 (n_v6.7.53)
Sony Stock Patcher for XZ - 16/07/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.7.35 (n_v5.7.35)
Sony Stock Patcher for XZ - 08/06/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.7.8 (n_v4.7.8)
Sony Stock Patcher for XZ - 21/05/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.2.223 (n_v3.223)
Sony Stock Patcher for XZ - 26/04/2017
=================================================
* Upgrade to Nougat 7.1.1 41.2.A.2.199 (n_v2.199)
Sony Stock Patcher for XZ - 21/03/2017
=================================================
* Initial release for Stock 7.0 (n_v1, 39.2.A.0.442)
* Based on my initial releases for Xperia X Performance
I've already tested this patcher and can confirm, it works like a charm :good:
My steps:
- Flashed the current 442 ftf via FlashTool (ejected the ext sd after poweroff, ofc), checked every checkbox in the wipe sector (don't know, if that's really neccessary).
- rebooted into system to check, if it boots fine, then power off again
- installed Adrian's current TWRP 3.1.0 via fastboot command (fastboot flash recovery <name of the recovery>.img)
- boot into recovery (<power> + <vol-> together until one time vibration, then left <power>)
- flashing the provided patcher.zip via TWRP and reboot, then - after booting - choose reboot
- now wait until vibration and the purple led, then push <vol+> => now you have to be in TWRP :good:
- flash the SuperSU.zip, if you want root
- if you want also the drm fix:
Connect your device via usb and type:
# adb -d shell
# su
# dd if=/dev/block/bootdevice/by-name/boot of=/sdcard/kernel.img
Then pull the kernel.img from /sdcard/kernel.img and go on with the unofficial rootkernel 5.23 @serajr I said yes to everything but SuperSU, TWRP and busybox (but test it by your own, it's not related to this thread). Btw, if you've managed to backup your ta before unlocking your bootloader, you can also use the PoC @munjeni for that (I unfortunately can't, because I don't have such a ta backup). But no mor ot here
I can confirm, it works like a charm - and it's like in mm times: you don't have to poweroff your device; just wait for the purple led and push <vol+> = enter TWRP :good::good::good:
Thank's @AdrianDC for your brilliant job :highfive:
You have just made the news!
@AdrianDC Congrats :good:
...
So it's works for both XZ (F8331 and F8332)?
Ryuu. said:
So it's works for both XZ (F8331 and F8332)?
Click to expand...
Click to collapse
Just try it and report back! Create a backup of your boot partition via TWRP before, of course
@AdrianDC
Thanks for your work
TWRP 3.10 works perfect on F8332 XZ Dual
I installed Stock Patcher on my patched kernel with PoC for load Kcal Module from here
after load kcal module got reboot and that module cant be loaded , any Help ?
@ AdrianDC
Thanks for your work
TWRP 3.10 works perfect on F8331 XZ
Can you make a Overcloked and Undervolted version? Thanks
Enviado desde mi F8331 mediante Tapatalk
RomanSkyline said:
Can you make a Overcloked and Undervolted version? Thanks
Enviado desde mi F8331 mediante Tapatalk
Click to expand...
Click to collapse
It's only possible with a custom kernel. On the other hand, it's really not neccessary, because battery drain and performance are really awesome as it is :good:
RomanSkyline said:
Can you make a Overcloked and Undervolted version? Thanks
Click to expand...
Click to collapse
It is "possible" but I won't do it, the purpose is not to waste time creating a 'modded custom' kernel,
but to stay as close as possible to the official Stock kernel while providing a modifiable ROM / bootimage.
Klaus N. said:
It's only possible with a custom kernel. On the other hand, it's really not neccessary, because battery drain and performance are really awesome as it is :good:
Click to expand...
Click to collapse
I disagree, the battery life on my XZ is TERRIBLE, recharging 2-3 times a day, to be fair though my day starts at like 4a and one Fridays ends at like 10p so meh lol... any recommendations for me?
Announcement said:
I disagree, the battery life on my XZ is TERRIBLE, recharging 2-3 times a day, to be fair though my day starts at like 4a and one Fridays ends at like 10p so meh lol... any recommendations for me?
Click to expand...
Click to collapse
Try my kernel, duality kernel and ROM. See if it helps
@AdrianDC great, might use this for my kernel
_LLJY said:
Try my kernel, duality kernel and ROM. See if it helps
@AdrianDC great, might use this for my kernel
Click to expand...
Click to collapse
I can't confirm @Announcement's statement. On my device it works very well; also the battery consumption is ok: I charge my device most of the time the 2nd day since the last charge, sometimes even on the 3rd day :good:
But it's a question of use, indeed!
Awesome work as always, Adrian!
The new patcher for the 7.1.1 fw (41.2.A.2.199) works flawlessly as expected! :good::good::good:
As mentioned by Klaus :good::
New release for Sony 41.2.A.2.199 release, Android 7.1.1.
There's only one little issue (only for me?) atm: When entering TWRP by pushing <vol+> while the purple led lights up, the display doesn't react. I've to turn off/on the display, then swipe to unlock the display. After doing that, it works as it should.
Regular TWRP 20170521: TWRP 3.1.1 release, including changes
to match 7.1.1 touchscreen init (to confirm for XZ) and Nougat decryption of course.
Regular TWRP 20170524: Re-release that avoids a touchscreen init race condition
on a specific variant of the device's touchscreen that prevented use without lock / unlock.
Made public the new release for Sony 41.2.A.2.223, Android 7.1.1.
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
This is a fully custom ROM for the Huawei Mate 9, derived from the AOSP Pie device tree for the HiKey960 development board, with minimal usage of the existing Huawei vendor stack.
This ROM does include Gapps for Pie.
IMPORTANT: See the broken features below. Most importantly: Phone and cellular is currently entirely non-functional, as there is no RIL implemented. If I can get away with it, I'm not importing code from Huawei's existing vendor stack. The graphics stack is fully sourced from the HiKey960 development board sources, as provided by Google on the Driver Binaries page for AOSP; the only blobs which are sourced directly from the Mate 9 system images are the device firmware blobs from /vendor/firmware.
Working features:
Basic graphics hardware acceleration & 3d support.
Wifi
Bluetooth (partial: kernel wakelock permanently held, preventing deep sleep. Generally functional, you will need to bring over your MAC address and configure it yourself.)
Touchscreen
Notification LED
Screen brightness
USB
Fast charging
Vibration
Battery information
Broken or not hooked up yet:
Reboot / shutdown: always cycles to eRecovery. (BFM is disabled, so the loader doesn't know that boot was successful.
Audio via wired headset, earpiece, speaker. (Bluetooth audio works. Over USB-C, untested.)
Cellular. (No RIL yet.)
SD card.
Camera
Fingerprint sensor
NFC
Any and all sensors.
GPS
More that I have yet to list, I'm sure.
Installation Instructions
Make note of your bluetooth hardware address.
Factory reset your device, preferably using stock recovery. TWRP builds will not work once this ROM is installed.
Install the kernel, ramdisk, and system image with fastboot.
Boot the system
Once booted: adb shell setprop persist.service.bdroid.bdaddr <your bluetooth hardware address>
Notes
The image is pre-rooted (it is an AOSP "eng" build). ADB is on by default, running as root, with no authentication.
Even though it is pre-rooted, I still recommend installing Magisk for the time being. Use the ramdisk image provided here with "Patch Boot Image". Magisk 17.1 with Magisk Manager 5.9.1 work. (Installing Magisk also works around a few other issues - for example, Developer Options is completely inaccessible on the default install.)
Changelog
2017-09-03: Initial release.
Download
GitHub release
Thanks
@wirmpolter for the Serenity kernel (which is used as the basis for the kernel image)
@TheHitMan for BiTGApps Pie
Sources
ironydelerium/device_huawei_mha on GitHub
ironydelerium/vendor_huawei_mha on GitHub
ironydelerium/Serenity on GitHub
XDA:DevDB Information
Custom AOSP Pie for Huawei Mate 9, ROM for the Huawei Mate 9
Contributors
irony_delerium, wirmpolter
Source Code: https://github.com/ironydelerium/device_huawei_mha/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: AOSP
Version Information
Status: Alpha
Beta Release Date: 2018-09-03
Created 2018-09-03
Last Updated 2018-09-03
Reserved
Reserved
Wooohoo .. is amazing .. more roms .. thanks .. dev ..?
You are amazing Man. I hope you will do it fully functional as soon as. Thanks bro.
Thank you much.
I tried this ROM. But too much bugs. I had to roll back to original EMUI ROM.
Hope you can fix the bugs in future.
Thank you very much for your efforts anyway.
luyongfeng said:
Thank you much.
I tried this ROM. But too much bugs. I had to roll back to original EMUI ROM.
Hope you can fix the bugs in future.
Thank you very much for your efforts anyway.
Click to expand...
Click to collapse
I'm planning on it.
There's a lot of work to do - cellular, audio, basic sensors, camera - none of those things are even there yet.
What's there works, unfortunately as you can tell, that's not a lot yet.
Are you still working on the rom? Any progress? tried to build lineage?
I am still working on it.
Not even considering Lineage at this point - just trying to get a complete device tree constructed, of which there are a lot of pieces to construct (not the least of which because I'm basically building it up from scratch, instead of using Huawei's vendor image).
Development in Kirin is very difficult. So far only see aosp rom in Honor 8 pro based on 7.1. Which is very similar to Mate 9
As some of you know s21 source is out, it is possible to build custom recovery and obtain root.
Actually ordinary magisk root method is not working for us: patched boot image does not boot...no old method is working.
I asked a skilled developer, @afaneh92 (he already made custom twrp for galaxy phones in past) to help us but at present he does not have the phone so what he builds is actually tested just by me.
WHAT WE NEED
- many alpha tester (if many people help us we can test things almost intanctaneily)
- some good ideas from other skilled developers
- someone who can make a "BOUNTY" so we can encourage development
I have made a telegram group forstarting this adventure and to share real time our progresses.
https://t.me/joinchat/H7UFBxjpms2aubmO
devs and testers u are welcome!
Work in progress...
Nobody knows how to make a bounty?
Nobody interested?
Im interested just not sure how to help...ive tried everything on sm-996B.. have joined the chat..
any progress?
Samsung Galaxy S21Ultra Exynos stuck on bootscreen (21407) (21408) · Issue #3808 · topjohnwu/Magisk
Hello, I'm on a new Samsung Galaxy S21Ultra (Exynos) FW: G998BXXU1AUAC , which is unrooted but Knox tripped. Its not possible for me to boot the device properly after patching the usual files. Magi...
github.com
Root is near guys!
How come? Any Source?
TWRP working for samsung s21 ultra exynos users
credit - PAUL
How is the process?
I've tried to flash it: error vbmeta - had to flash original recovery.img again to boot the device again
bhammler said:
I've tried to flash it: error vbmeta - had to flash original recovery.img again to boot the device again
Click to expand...
Click to collapse
I think you need to use this:
WETA Kernel SM-G998U/U1/0 Snapdragon only
*** This will only work on Snapdragon devices with an unlocked bootloader..
SM-G998U/U1 - SM-G9980
Telegram thread at bottom of this post
See post #2 for install steps
Changelog...
R5.02
Telegram thread merged into N20.S20 group, check new links.
Upstreamed to 5.4.127
all modules now inlined, no need for magisk helper module.
added wireguard
Power usage tweaks
More
R4.04
Upstreamed to 5.4.123
R4.03
Upstreamed to 5.4.122
R4.02
Upstreamed to 5.4.121
R4.01
Upstreamed to 5.4.120
R4
Testing phase complete
Upstreamed to 5.4.119
R3
Rebased off UAG source code
R2
Upstreamed to 5.4.118
Fixed Torch/Flash
R1
built using CU8 kernel source
Upstreamed to 5.4.117
Fully permissive
KNOX disabled
Wireguard
Misc debugging disabled
Kernel Downloads
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
Kernel for the Samsung Galaxy S21 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: - Kernel Source
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: R1
Created 2021-05-10
Last Updated 2020-05-10
*** Be aware, there may be a need to wipe data if you desire to go back to stock kernel, my suggestion is to backup your stock BOOT partition and DATA before flashing. This way you can return to your original setup easily. It is unknown at this stage what data is causing an issue going back to stock. If you find it, be sure to share.
* You must have bootloader unlocked and rooted your device with Magisk before flashing this kernel. Magisk is essential for camera and wacom.
* Boot times are approx 60-75sec at the moment, itll sit on the yellow triangle splash for approx 60sec and the bootanimation for 5sec.
* When flashing this kernel, an AnyKernel helper module is installed. This is a Magisk Module that is essential for the operation of Camera and Wacom. Removal of this module while running this kernel will break camera and spen.
* Kernel zip labels have either a P or E in them, P=Fully Permissive, E=Enforcing (switchable)
To install
download and flash the kernel installer zip in TWRP or any custom recovery
--->
mine 2
Amazing to see some development, i thought this phone thread was gonna be dev dead
I am a little surprised myself.
Status update
I have found a couple of bugs I'm working on, #1 camera module only loads on permissive version of kernel, #2 the flash doesn't work, #3 random reboots maybe 4-5 times a day.
Working on having a stable R2 this week.
Edit: so it seems the hourly bootloop happens on stock kernel for me also. So it isn't an issue with this kernel. Though I do need to fix the flash
WETA Kernel R2
Upstreamed to 5.4.118
Fixed Torch/Flash
--->
WETA Kernel R3
Starting from scratch with different source code. It seemed there were problems booting for most. The new test kernels have been successful.
This is a basic start, with the intention of upstreaming and testing along the way.
--->
WETA Kernel R4
Upstreamed to 5.4.119
* Testing was successful with the different source code kernel
* Remember you MUST have magisk installed Pryor to flashing this kernel, this kernel needs it's ak3-helper magisk module for camera operation.
--->
I have used your Kernels in the past for other devices, really loved them. Was wondering if you plan to make a custom kernel for the s21 ultra Exynos in the future ?
Excuse my ignorance but please elaborate on "knox disabled"? I have unlocked bootloader/magisk and knox is already disabled as far as I know. Would this mod to the kernel allow me to use knox locked features that have been lost, eg biometric security for some apps? Thank you for your work, look forward to trying it out
dsdavis6 said:
Excuse my ignorance but please elaborate on "knox disabled"? I have unlocked bootloader/magisk and knox is already disabled as far as I know. Would this mod to the kernel allow me to use knox locked features that have been lost, eg biometric security for some apps? Thank you for your work, look forward to trying it out
Click to expand...
Click to collapse
Kernel based Knox ncm is disabled, it has nothing to do with your "Knox fuse" which is blown when your bootloader is unlocked.
paul_cherma said:
I have used your Kernels in the past for other devices, really loved them. Was wondering if you plan to make a custom kernel for the s21 ultra Exynos in the future ?
Click to expand...
Click to collapse
I don't plan on building anything for devices I don't hold in my hand. Reliable testing is hard otherwise
WETA Kernel 4.02
Upstreamed to 5.4.121
--->
Just a note regarding boot times, I can achieve a 35sec boot time, though in doing so it breaks double tap to wake, and fingerprints. I won't release a version with those broken items.
WETA Kernel 4.03
Upstreamed to 5.4.122
--->
WETA Kernel 4.04
Upstreamed to 5.4.123
--->
Hi all
I have problem in compiling kernel source for Moto G9 Plus. There are apparently 2 versions of kernel source for Moto G9 Plus. There is one source in this link that 's the stock kernel (company released kernel ver. 4.14.117) and the other source that 's released by the experts community in this link.
I can build the community released kernel source, easily through clang or gcc but I can build the stock kernel neither by clang nor gcc (aosp or my host ubuntu or gcc-linaro versions) and I face with different types of errors consecutively (related to compiler version or configuration and code syntax)!
The main question and ambiguity for me is that if it is possible for a company to release a source code, erroneous and buggy or it can be built with a special compiler config or version or under a specific condition?!
Thanks in advance
Sapper Morton said:
The latest tag is available here:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QPAS30.19-Q3-32-50-5
github.com
As for the compiling errors; audio drivers, wlan and etc, are not included in that repository, you should included yourself:
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-audio-kernel
https://github.com/MotorolaMobilityLLC/vendor-qcom-opensource-wlan-qcacld-3.0
About the Toolchain, you got that right, usually OEMs will use the default compiler that's matching the release tag.
The custom tree you linked in has these and more resolved; not to blame Motorola or Lenovo, but CAF itself, so a learning curve is necessary.
Click to expand...
Click to collapse
Thanks for your help
but now another question is how can we understand which additional source (just like above two other sources you mentioned alongside the original source) is needed when we want to compile a kernel source?
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
deheshjou said:
hi
I have compiled stock kernel of Moto G9 Plus (odessa) based on the tutorial on this link successfully. when I replace the stock kernel (in boot.img) with the new compiled one (Image.gz), the phone has no problem in boot process but it's touch screen does not work and I can not login to the OS. can anyone help me to understand the issue and help to fix the problem?
note:
I know 3 commits (1, 2, 3) is needed to solve the issue about working the core kernel (kernel modules not compiled and not integrated with the core) correctly with kernel modules existing inside the OS from before (thanks @erfanoabdi for explanations and the commits!)
Click to expand...
Click to collapse
Hi, just curious how your kernel worked out? Is there any chance you are planning on sharing your work? This device could really benefit from a good custom kernel for stock sdcardfs A11, and one for asop(A11&A12) roms.