Sekiyama-Kernel for Oneplus N200 5G
Features:
Main Features:
- Based on latest kernel sources from OnePlus for Android 11
- Upstreamed against latest kernel-common (android12-5.4-lts)
- Linux-Stable-Upstream included to latest 5.4.179
- compiled with Clang 13.0.1 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Link the kernel with LLD and use RELR-Relocation
- fix several coding issues detected by newer Clang-Toolchains
- include important fixes/improvements from kernel/common
- Supports ALL variants, NA/TMO/OEM
- Wireguard Support
- If you want magisk, you must patch first!!!
Downloads:
https://github.com/ArtiicPanda/oneplus-sm4350/releases
Requirements
- Unlocked Bootloader
- USB Debugging in developer options enabled
- Latest adb and fastboot
How to flash the Kernel:
Boot to fastboot/bootloader to flash boot.img:
Either select Reboot to bootloader option via buttons
or type:
Code:
adb reboot-bootloader
Now in fastboot flash boot.img
Commands:
Code:
fastboot flash boot boot.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
Reboot either via buttons
or by typing
Code:
fastboot reboot
@Freak07 for his kernel thread from which I drew inspiration.
Source Code: https://github.com/ArtiicPanda/oneplus-sm4350
reserved
reserved
Any updates?
blowtorchhonor said:
Any updates?
Click to expand...
Click to collapse
Need some time to create a great OP
Tests builds are available here:
Join «Nord N200 Testers» on Telegram: https://t.me/OnePlusNordN2005G
Released. Thank you to all that helped test prior to release. Enjoy!
I can vouch that this kernel really helps this device run faster. I already tested many things from bluetooth to phone calls and everything works. Enjoy everyone!
11.0.2 Update posted, changelog on github
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Wivioo said:
Wonderful work to you and @Travisholt92. Really surprised how far everyone has gotten in such a small amount of time.
Click to expand...
Click to collapse
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Travisholt92 said:
Apparently all it took to kick things off was me extracting the defconfig from the stock kernel and showing it could be built (partially) and then @ArtiicPanda being awesome decided to get in on the action
Click to expand...
Click to collapse
definitely was a team effort. again thanks to the testers as well. @blowtorchhonor @TheLoonyRebel
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
cognitoinc566 said:
Just flashed 11.0.1 (couldn't find a binary for 11.0.2) and it successfully booted on my TMO/metropcs flashed to unlocked firmare running latest Pixel Experience A12 GSI
Click to expand...
Click to collapse
I think they forgot to post 11.0.2
edit: they forgot to compile the source to a .img
No, there were some minor issues with 11.0.2 so it's being reworked, just use 11.0.1 until then.
Update posted, change log on GitHub
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Tyreethetruth said:
I have this notification that says serial console enabled performance is impacted to disable check bootloader and I have no idea how to disable it. I'm also unable to use usb debugging for more than 2 seconds as it goes away and stops
Click to expand...
Click to collapse
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
lentm said:
Same here. I installed 11.0.2.1, the most recent one on T-Mobile stock 11.0.1.9 and the same notification shows up.
After reboot, the screen got darker, and can't control brightness anymore.
Going back to stock boot...
Click to expand...
Click to collapse
I fixed it, you just have to reflash magisk via fastboot
Tyreethetruth said:
I fixed it, you just have to reflash magisk via fastboot
Click to expand...
Click to collapse
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
lentm said:
I patched kernel image via magisk then flashed magisk patched kernel image via fastboot and it happened.
Click to expand...
Click to collapse
Try flashing the kernal via fastboot then fully boot the phone then flash the magisk patched image again via fastboot and it will get rid of the notification
Related
TeamWin's TWRP Touch Recovery for LG G3 - currently available only for F400 variantshttps://twrp.me/
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like OmniROM
You can find the source code for TWRP at github.com/omnirom/android_bootable_recovery/
Flashing Instructions
To install recovery images use Flashify / Rashr from Play Store or flash in your current recovery. Otherwise do the following:
1. Go to install, find and select the Images... button.
2. Browse to the image that you downloaded and select it.
3. Choose recovery and swipe to flash.
OR
1. Move recovery.img to internal storage.
2. Open terminal window/command prompt to execute following commands
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
exit
exit
adb reboot recovery
About this TWRP
compiled on LineageOS-14.1 source
always up-to-date
fixed screen brightness
permissive selinux
disabled logd/logcat in recovery
fuse exfat, ntfs-3g, jpeg, usb-otg support
external storage as default storage
touch to wake
backup of all partitions including modem, efs
crypto/decryption may work or not..
Changelog
* 170430
- Initial Build
- Disabled HW crypto due to build fails
* 170501
- Deleted unused flags
- Add back HW crypto
- exfat support
* 170507
- Disabled logd/logcat (fix for "device or resource busy", hopefully)
* 170519
- Updated to v3.1.1
- Fix Aroma Installer crash (hopefully)
Known issues
ZIP files with date check assert can't be installed (eg. crDroid) - Users should delete date check assert in binary by themselves.
AROMA Installer stucks at loading - will be fixed soon..
Download Links
Unofficial | Official
Sources
https://github.com/TheNoFace/android_device_lge_g3-common-TWRP/tree/twrp
(Based on https://review.lineageos.org/#/c/160056/)
Remember to do backup of your current recovery before installing
Any plans for suporting other G3 variants in future?
@fprhqkrtk303: Now have 2 version twrp to flash. Which one to choose to flash? Unofficial or official? Thanks!
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
ahk31 said:
Any plans for suporting other G3 variants in future?
Click to expand...
Click to collapse
Planning to support more devices when F400 version is stable.
You can build your own TWRP using my source.
@chuyennho184 @andrewKode Official version from TWRP uses older device tree and actually no one maintains. Recommend using unofficial version.
@fprhqkrtk303: I saw update firmware on March 22th for F400 variants but I don't have a link. Do you have a link? Thanks for bother you.
Updated to v3.1.1 (170519)
fprhqkrtk303 said:
Updated to v3.1.1 (170519)
Click to expand...
Click to collapse
Is aroma bootloop problem fixed in this new version?
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Not tested yet. Can you check?
fprhqkrtk303 said:
Not tested yet. Can you check?
Click to expand...
Click to collapse
Yes. Tried it yesterday. Bootloop problem is still present.
andrewKode said:
Official TWRP for D855 is so bad... sorry to say that. It doesn't work properly and even if LineageOS recommends it it's just not able to flash LOS builds.
When you want to reboot in recovery it hangs in a bootloop and when you want to shut the device off it just turns on back. So far we only have the unofficial version for D855 fully working.
Click to expand...
Click to collapse
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
ZjemCiKolege said:
LoL i maintain twrp for d855 i don't have any issue with that recovery(3.1.1) fully tested..
and this problem cause by bootloader..
or you mean this
Fixed rebooting when no OS is present (Dees_Troy)
"unofficial version for D855 fully working."
Nope dadi11 twrp encrypt no work.. ;]
Click to expand...
Click to collapse
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
andrewKode said:
Dude, Idk what you're maintaining but this is what happens:
- TWRP sometimes does not reboot back in recovery (it hangs on LG screen)
- hangs on flashing LineageOS
- When chosed to turn off the device from the recovery it turns back ON right after it shuts down.
Click to expand...
Click to collapse
1. I try but did not happen.
2. Build of lineage?(i flash each version from february to 21.04) no any issue.
3. Issue of custom rom(problem with turn on charger and boot same issue..) ;]
MESA said:
Is aroma bootloop problem fixed in this new version?
Click to expand...
Click to collapse
Hello, apparently no...
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html
If it's a software problem, it would be the problem of AROMA devs, but if it's related to software keys incompatibility it's will be the work of TWRP devs.
rooted kernel hiding bootloader unlock
with working sony stock fw fota updates
for Sony Xperia XZ1
Firmware Over the Air system updates have been disabled/not working with sony xperia phones with unlocked bootloader.
Also many sony drm functions are disabled if fw detects unlocked bootloader even if device master key was recovered.
I've implemented a kernel patch for xperia XZ1 Compact / XZ1 / XZ Premium phones that properly masks bootloader unlock status so it appears as still locked for sony stock firmwares.
This allows FOTA updates to be installed if running completely unmodified stock firmware. This is possible if this kernel is just booted from usb via fastboot instead of flashing it.
The kernel is pre-rooted, so you can have root as usual with magisk when running this kernel (you can use magisk system less patching to make changes to system/vendor partitions without actually modifying them).
For oreo fw the boot process is patched to hide magisk from sony ric daemon that stops the boot in case it thinks the bootloader is still locked. This special patch allows to pass safetynet including cts while having properly working magisk.
This kernel may be used (flashed) just to properly enable sony drm features, like video image enhancements, if device master key was recovered via locked state TA restore.
The bellow described way to install FOTA system update works with both - phone with TA restored and phone with drm keys lost. Both variants have been tested with xz1c.
How to use this kernel while planning to do FOTA system update eventually
Update: please see here for the latest usage instructions for kernels in flashable zip archive.
Please see screenshots bellow for this kernel in action (with xz1c) doing fota system update from oreo to pie and from pie to next pie version. There is also a video documenting this here. Few longer waiting parts have been cut out to fit the video under 15 minutes of youtube limit for not verified accounts.
if your bootloader is still locked
Use renoroot exploit to backup your TA, unlock your bootloader and restore TA-locked to recover device master key as described in
[XZ1c/XZ1/XZp] temp root exploit to backup drm keys implemented thread.
select one of the prepared kernels and download it
make sure you are running unmodified stock firmware
You need the version corresponding to the selected kernel - reflash the firmware to make sure it is unmodified.
Please note: any mount of /system or /vendor partitions in write mode would result with modifications even if nothing is copied there.
Be aware that some zip packages flashed from twrp may mount the partitions for write access even when that is not needed.
reboot the phone to fastboot mode
Use either "adb reboot bootloader" or
enter fastboot by holding powered off phone's volume up key while connecting it to PC via usb cable and use 'fastboot reboot bootloader' command.
boot the downloaded kernel via fastboot
For example (xz1c):
Code:
fastboot boot boot-G8441-47.1.A.16.20-hideunlock-rooted.img
enjoy your rooted phone which thinks it is still locked
Sony apps will be offered to install/update. System FOTA update may come.
Magisk will provide your root when magisk manager app is installed (offered on the first boot).
if you need to use a custom recovery, like TWRP
Do not flash it. If you do, FOTA update verification will fail.
Instead use 'fastboot boot' the same way as with the kernel above, but instead of the kernel, boot the twrp image without flashing it.
to install a FOTA system update
just start the update as usual
let it run until it finishes the installation
try to catch the restart then and hold volume up that time to enter fastboot
you need to use following command to make next boot working
Code:
fastboot reboot bootloader
use 'fastboot boot' to boot kernel for fw to which fota updating to,
for example (xz1c):
Code:
fastboot boot boot-G8441-47.2.A.4.45-hideunlock-rooted.img
if you miss the restart (or do not have the right kernel version),
it does not matter, the installation will finish even when bootloader unlock is detected with the last reboot to updated system,
so just 'fastboot boot' the corresponding 'hideunlock-rooted' kernel then
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
But if you like to install FOTA system update then, you would need to flash the stock kernel first in order to make the fw untouched again (assuming no other changes to the fw, like system or vendor partitions, have been done) and boot the patched kernel via 'fastboot boot' as described above.
You can backup stock kernel (and recovery) to avoid need to download full stock fw when you need to restore stock kernel & recovery when you decide to install fota system update - see here and following post for more details please.
If you do not care about FOTA, just do not install it.
And use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
In case you like to make some modifications to system or vendor partitions (as you do not care about fota), you would need to disable verity in the kernel - please see post#3 for noverity variants of oreo kernels and linked post describing howto switch verity off via magisk in all pie kernels.
Downloads
See the post#2 please.
Source code
patched kernel sources to hide bootloader unlock (my-bluhide/* branches)
https://github.com/j4nn/sonyxperiadev-kernel-copyleft
patched magisk sources to hide magisk from sony ric daemon on early boot phase (v19.1-manager-v7.1.2-ric branch)
https://github.com/j4nn/Magisk/tree/v19.1-manager-v7.1.2-ric
The patches are provided under GPL (that means you may include them in your builds, but you need to provide buildable source of released binaries /true for any kernel change btw/).
Credits
Thanks to @tonsofquestions for lot of initial testing of this concept when I did not have a phone with unlocked bootloader and for discovering the need to reboot to fastboot by a command to make the 'fastboot boot' command properly boot the supplied kernel image.
Thanks to @topjohnwu for his excelent magisk tool.
If you find my work useful, consider donating here please:
https://j4nn.github.io/donate/
Thank you.
XDA:DevDB Information
kernel_bluhide_poplar, Kernel for the Sony Xperia XZ1
Contributors
j4nn
Source Code: https://github.com/j4nn/sonyxperiadev-kernel-copyleft
Kernel Special Features: proper hiding of bootloader unlock, sony ric with magisk hack
Version Information
Status: Stable
Stable Release Date: 2019-02-10
Created 2019-02-10
Last Updated 2019-08-07
Downloads
- hideunlock kernel pre-rooted boot images:
Xperia XZ1 (G8341/G8343)
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8341-47.2.A.4.45-hideunlock-rooted.img
boot-G8341-47.2.A.6.30-hideunlock-rooted.img
boot-G8341-47.2.A.8.24-hideunlock-rooted.img
boot-G8341-47.2.A.10.28-hideunlock-rooted.img
boot-G8341-47.2.A.10.45-hideunlock-rooted.img
boot-G8341-47.2.A.10.62-hideunlock-magisk-19.3.img
Xperia XZ1 Dual (G8342)
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1.img
boot-G8342-47.2.A.4.45-hideunlock-rooted.img
boot-G8342-47.2.A.6.30-hideunlock-rooted.img
boot-G8342-47.2.A.8.24-hideunlock-rooted.img
boot-G8342-47.2.A.10.28-hideunlock-rooted.img
boot-G8342-47.2.A.10.45-hideunlock-rooted.img
boot-G8342-47.2.A.10.62-hideunlock-magisk-19.3.img
- hideunlock kernels flashable to multi fw versions (see here for usage howto):
Xperia XZ1 (G8341/G8343)
kernel-G8341-47.1.A.16.20-hideunlock.zip
kernel-G8341-47.2.A.10.62-hideunlock.zip
kernel-G8341-47.2.A.10.80-hideunlock.zip
kernel-G8341-47.2.A.10.107-hideunlock.zip
kernel-G8341-47.2.A.11.228-hideunlock.zip
Xperia XZ1 Dual (G8342)
kernel-G8342-47.1.A.16.20-hideunlock.zip
kernel-G8342-47.2.A.10.62-hideunlock.zip
kernel-G8342-47.2.A.10.80-hideunlock.zip
kernel-G8342-47.2.A.10.107-hideunlock.zip
kernel-G8142-47.2.A.11.228-hideunlock.zip
Screenshots of XZ1c FOTA system update from oreo 47.1.A.16.20 to pie 47.2.A.4.45
(video available here)
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-magisk-19.1-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
This should be the first paragraph!
j4nn said:
[...] use this kernel just to enable all sony drm features that are available on a locked phone (assuming locked state TA has been restored).
Click to expand...
Click to collapse
Since I do not care about OTA updates, because we can download every firmware via XperiFirm and flash it via newflasher, I will use your modded kernel in the 'alternative' way! :good:
j4nn said:
Alternative use of this kernel
If you do not like booting from usb via fastboot to startup your phone, you can flash the kernel and boot normally.
Click to expand...
Click to collapse
@j4nn - I flashed "boot-G8341-47.2.A.6.30-hideunlock-rooted.img" on my G8341 which has the latest Pie firmware (G8341_47.2.A.6.30_Customized DE_1310-4290_R6C) installed, but the device did not boot into Android after that! :crying: I flashed the latest official Magisk before your kernel. Do I need to use your patched Magisk instead?
Did you forgot to add the patched magisk flashable img file? "hide magisk from sony ric daemon on early boot phase (v18.1-manager-v7.0.0-ric branch)"
j4nn said:
Downloads
Click to expand...
Click to collapse
Maybe the firmware version is not compatible with the one you took the kernel from? The firmware folder includes:
kernel_X-FLASH-ALL-C93B.sin
boot/bootloader_X_BOOT_MSM8998_LA2_0_P_107_X-FLASH-ALL-C93B.sin
...
Click to expand...
Click to collapse
@SGH-i200, I just compared the stock kernel boot image extracted from G8341_Customized DE_1310-4290_47.2.A.6.30_R6C (which I have used to create it) and it seems all good to me:
- os version and patch level match
- device tree blobs are the same
- kernel command line is the same
- extracted kernel config is (except few comments as it is usual) the same, with poplar target (i.e. single sim XZ1)
- ramdisk is the same except changes that are expected (integrated magisk in order to provide root when booted from usb having unmodified stock fw)
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
I am sorry I forgot to mention the kernels for other targets than xz1c have not been tested (I have only xz1c for testing).
But it should be safe to test the above howto as described. Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Anybody else tested this with XZ1?
j4nn said:
Did it result with an infinite hang during boot (which phase of the boot splash animation)?
Or did it reboot during boot (a boot-loop) - which phase?
Click to expand...
Click to collapse
The SONY white splash screen appeared (with only black SONY text) and then it hang forever.
j4nn said:
Even if the kernel was flashed (instead of just fastboot booted), recovering from this should be as simple flashing stock kernel back.
Click to expand...
Click to collapse
I flashed the kernel_X-FLASH-ALL-C93B.sin (and everything else as I did to upgrade to latest Pie) from the stock fw to recover.
After the XZ1 was booting again, I executed the fastboot booting, without problems!
adb reboot bootloader
fastboot boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
Click to expand...
Click to collapse
@SGH-i200, that sounds good. Now just flash it:
Code:
adb reboot bootloader
fastboot flash boot boot-G8341-47.2.A.6.30-hideunlock-rooted.img
disconnect from usb and power on.
If it booted from usb, I believe it should boot just fine if flashed as above too.
j4nn said:
If it booted from usb, I believe it should boot just fine if flashed as above too.
Click to expand...
Click to collapse
I flashed your patched kernel again and got into a bootloop: Bootloader unlocked warning and white SONY splash screen in an endless loop.
Since my XZ1 was connected to my Windows workstation already, I simply long pressed the volume up button till the notification light went blue, and booted into twrp to restore the stock kernel (rooted by Magisk to remove the dmverity stuff).
@SGH-i200, you are right, it is the verity thing.
I've assumed that verity is ignored when kernel detects unlocked bootloader, because the dm-android-verity kernel component used that is_unlocked() call to:
/* Allow invalid metadata when the device is unlocked */
- that comment is in the dm-android-verity.c source code.
But it looks like that is only a corner case and if verity metadata is valid, verity is active (if not disabled in device tree) even with unlocked bootloader.
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
From this point of view it should be all good then.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img.
Flash that and you should be good to go.
This procedure is valid for all my pie kernel builds.
I will repack the oreo 16.20 build as using magisk manager gui would not keep the magisk patch for sony ric daemon.
-- edit --
Updated post#3 with downloads of oreo kernels noverity repacks.
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
j4nn said:
Now I am wondering: for OTA updates we need untouched system, so having verity enabled in the kernel is good for this purpose - when you flash something that writes to system or vendor, you may detect it soon enough to be able to tell what it was. The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions. From this point of view it should be all good then.
Click to expand...
Click to collapse
I use AdAway and activated NightLight by copying a apk to /vendor/overlay .
Thanks for creating the noverity Oreo kernel versions! :good:
---------- Post added at 09:04 AM ---------- Previous post was at 08:57 AM ----------
j4nn said:
The main feature of magisk is that you should be able to "modify" system "systemlessly", i.e. without really writing to system or vendor partitions.
But I understand that the "alternative" use of this kernel, i.e. not planning to do FOTA at all, just using only the unlock hide feature restoring drm functionality and using root the old way (with real writes to system) may be liked.
For this, just use magisk manager main screen, in "Advanced Settings" unselect the "Preserve AVB 2.0/dm-verity" option and then use the "Magisk INSTALL" button, confirm install of Magisk-v*.zip, select "Patch Boot Image File", browse to sdcard where you put my kernel image and select it.
Magisk will repack the boot image disabling dm-verity in device tree blobs, noting where you can find patched_boot.img. Flash that and you should be good to go. This procedure is valid for all my pie kernel builds.
Click to expand...
Click to collapse
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
sinkoo1979 said:
Thanks for the kernel but after flashing the kernel the phone don't go into doze (deep sleep). Any suggestions on this?
Click to expand...
Click to collapse
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
SGH-i200 said:
If I flash your patched Pie kernel via TWRP and flash Magisk right after, this should have the same effect as patching your kernel via the Magisk app, right?
@j4nn - "using root the old way (with real writes to system)" - will flashing Magisk via TWRP change this to system-less root?
Click to expand...
Click to collapse
Most likely flashing magisk via twrp after flashing the patched pie kernel would disable verity too.
Using the image file - you have it under your control.
Flashing from twrp - some magisk scripting tries to detect if verity should be disabled or not.
Also a kernel image already containing magisk contains the setting of verity and encryption - not sure how that is used when flashing magisk again over it.
I tried it with my xz1c and verity was flipped from enabled to disabled - so the same effect (this time).
But as described, some detection is used, so the results might not always be the same.
j4nn said:
I have no idea. In my opinion, if you get such behaviour with my kernel, you will get exactly the same behaviour with stock kernel of the same version.
My kernel is compiled from sony's open source kernel package, with kernel config that's identical (except few comment lines) to the one compiled in stock kernel.
My kernel patch only fixes kernel command line that comes from bootloader and hijacks trust zone api to mask the bootloader status to appear as still locked to firmware's userspace.
These changes hardly could have any influence on power saving behaviour.
Please flash the same version stock kernel and test again for deep sleep.
Could not be that caused by some app you've installed?
reflashed stock firmware and everything is fine. Thanks for the kernel.
Click to expand...
Click to collapse
j4nn said:
Downloads
This is for alternative use only - please see post#10 for more details.
boot-G8341-47.1.A.16.20-hideunlock-rooted-noverity.img
boot-G8342-47.1.A.16.20-hideunlock-rooted-noverity.img
Screenshots of XZ1c FOTA system update from pie 47.2.A.4.45 to pie 47.2.A.6.30 version
(video available here since 08:10 time)
Click to expand...
Click to collapse
Hi j4nn
I unlocked my bootloader on 47.1.A.16.20 and lost my drm keys. I upgraded via newflasher_v13 to 47.2.A.4.45 Customised SG as that is where i am based and where my phone is from. Unfortunately when I flash boot-G8342-47.2.A.4.45-hideunlock-rooted.img my phone still boots up showing the device has been unlocked and the Backup and Restore feature of Xperia devices does not work. Am I correct to say if I lost my drm keys that I am unable to use this kernel to hide my bootloader unlock?
Thank you for answering me.
Working fine on xz1 pie 47.2.A.6.30 with blx firmware, Kernel flashed with twrp, widevine is L1 now, and Bravia engine working
@leonaheidern, the kernel would hide the unlocked bootloader regardless you lost drm keys or restored locked TA.
Please check you kernel build date when you boot your phone in about menu.
@j4nn, I have a quick question and a bit off topic, I'm still tinkering a bit but I did manage to backup my ta. and I flashed janjan's so things may seem a bit off, (see pic).. but I did restore my ta. before flashing Jan's kernel, any idea what may happen if I flashed yours on top?
oh and everything is working..
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
j4nn said:
@lilbrat, I guess that the result would be the same if you flashed my kernel without flashing janjan's before it.
Just note please, my kernels as they are have verity enabled, so you need to have unmodified stock fw.
Or disable verity as hinted for alternative use.
With my kernel and restored TA your security screen would look perfect as with a still locked phone.
Click to expand...
Click to collapse
OK.. thanks for the info... now I have another question, now that xz1 has a new update out and granted it will take you a bit to catch up if you need to redo all your kernels you have going... (great work by the way) Will I need to reflash my ta. backup for the new firmware and or just your kernel?
AOSP Q for Suzu/f5121
DISCLAIMER
As always use it at your own risk.
Build it in my spare time to test how the development is proceeding.
Installation instructions
NB: This is a full software update in the sense that will replace everything, recovery included, with aosp version. You need to reflash twrp afterwards.
Clean Install
enter twrp and factory reset
format data partition (only if coming from Pie or below)
flash the rom
flash GApps (optional)
reboot
Updating from previous version
enter TWRP and wipe dalvik/cache
flash ROM
reboot
Alternative way to install
You can also unzip the file and flash via flashboot only what you need:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash userdata userdata.img (only if not updating or coming from Pie or below)
fastboot flash oem xxxx.img
Now you can boot into TWRP and flash gapps and other stuff if you want.
First boot will get stuck on Sony logo for 30/40 seconds, and maybe reboot itself one or two time. Just have patience and everything will be all right
Downloads:
ROM: Latest Build
OEM: Binaries for 4.9 kernel
TWRP: Official TWRP for Suzu
BitGapps: Suggested GApps
What's works:
RIL
Bluetooth
Wifi
Fingerprint
NFC
Camera
USB tethering
Everything else?
What doesn't:
Random reboots (should be solved in latest build)
WiFi Hotspot
Expected the same bugs for Pie ROM since the kernel and binaries are the same, but let me know if you find anything else, will do my best to try to fix it.
Click to expand...
Click to collapse
Changelogr41
Update sources to r41
Overvolt BIG processor to improve stability on higher frequencies (should fix random reboots)
r33
Update sources to r33
r32.v1b
Reverted patch to enable developer option by default
r32.v1
Removed default searchbar from Launcher3
Enabled developer settings by default
Add MicroG support (testing)
r32:
Initial booting build
Click to expand...
Click to collapse
ROM Version: r41
ROM Status: Stable
Created: 2019-12-04
Last Update: 2020-09-20
Thanks to:
@twain55 for the screenshot and testing
@dslul to help in the bug fixing
@ix5 for the initial patches
sonyxperiadev project for providing sources
and last but not least thanks to all that will test this.
Screenshots
flashed with fastboot and stuck at splash screen
Adi_OP said:
flashed with fastboot and stuck at splash screen
Click to expand...
Click to collapse
Still testing and had the same results. Can you try to use the old OEM IMG for pie and report if boots? If not I'll try It during the weekend and let you know.
EDIT
Tried with the pie OEM IMG and doesn't boot. Will rebuild the boot image this weekend and see how to fix
Stuck at splash screen too, using fastboot!
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
lookmanns14 said:
Same here with twrp..try with and w/o gapps,stuck at sony logo.It seem the problem is at boot image
Click to expand...
Click to collapse
It seems to me too. I'm trying to find where is the issue. Building another image today and tested on my device but didn't worked either.
Does it work for F5122?
Thank you for your try.
Does it work for F5122 as well.
Hope you to fix this rom as a stable.
Good luck
Sorry for the waiting, I've had a lot of work to do lately. Hope to have news/a new build (at least for boot.img) this weekend.
New images are up. I'll try them this afternoon (out now) but if someone would take the leap before me here it is the link
https://mega.nz/#F!vNtx2QZZ!GuV1qwYXjLk3ajd3xoaPPA
Let me know. And thanks again for helping me testing.
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Iscariah said:
Unfortunately, still stuck at Sony logo... I used the latest OEM released on December 10th, SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2C_loire, will try with SW_binaries_for_Xperia_Android_10.0.7.1_r1_v2B_loire, but I doubt this will change anything!
Click to expand...
Click to collapse
I doubt it too sadly but if still stuck I'm at a loss right now. I've to try to see if I can catch some log even if stuck at Sony. Thanks for the report
Any update on this ROM? Is it still in development?
GOrMHATRe said:
Any update on this ROM? Is it still in development?
Click to expand...
Click to collapse
It is. Latest build still doesn't boot. I'm debugging to see if I can find the problem.
Have we wait for next weekends till any further update?
Any good news
[email protected] said:
Any good news
Click to expand...
Click to collapse
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
ParanoidNemo said:
Sadly not yet. Having trouble with the building of r15. I think that could be some changes in Q building system because pie build correctly. Hope to fix in this holidays.
Click to expand...
Click to collapse
Cheers
Any good news
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
mase76 said:
Are there still this random reboots and homescreen freezes we have with Pie and the 4.9 kernel?
Click to expand...
Click to collapse
Right now the ROM doesn't boot. The issue is upstream and as far as I know this should be fixed when the v3 of the binaries is released (right now we are at v2c). Hopefully the reboot issue will be fixed but we have to wait sadly.
@ParanoidNemo
Which kernel did you use?
So this is not my work some developers had done unofficial build of lineageos 18.1 Android 11 based rom at oneplus nord 2 community I am just tested and sharing it at here.
All credit goes to SakilMondal from nord 2 telegram channel.
Bugs:
1)autobrighness is not working.
2)alert slider is not working.
3)NFC not working.
Prerequisites:
1) Working TWRP
2) You must be on latest OOS A15 or Elixir custom rom.
Steps:
1)If you are on custom rom elixir os download lineageos 18.1 and gapps and place them in pendrive
If you are on oxygenos A15 place both files in internal storage.
2)Now boot your device in to TWRP by using advance reboot if you are on stock oos use adb command
adb reboot recovery.
3)when we booted in to TWRP now connect USB OTG and go to mount and checkmark usb storage,after click to select storage and select usb storage.(skip otg process for oxygen os A15 users)
4)Now click install and select lineageos zip flash then falsh gapps now click reboot and select bootloader.
5)when phone boots to bootloader connect to pc and go to folder where we placed A15 stock boot emmc open command prompt there and type following commands.
fastboot devices
fastboot flash boot boot.emmc.win
For EU user inhave given boot as boot.img so cmd command will be as below
fastboot flash boot boot.img
fastboot -w
fastboot reboot
Phone will boot it May stuck at 1+ logo but don't worry it will boot to lineageos 18.1 within 10min so wait atleast for 10min.
Downloads:
Download LineageOS 18.1:
lineage-18.1-20211228-UNOFFICIAL-denniz.zip
drive.google.com
Gapps:
The Open GApps Project
OpenGApps.org offers information and pre-built packages of The Open GApps Project. The Open GApps Project is an open-source effort to script the automatic generation of up-to-date Google Apps packages. All Android versions and platforms supported.
opengapps.org
Download Indian boot img (emmc.win.format):
{Mod edit: Link removed}
fastboot flash boot boot.emmc.win
Download boot img for EU:
{Mod edit: Link removed}
cmd command:
fastboot flash boot boot.img
Cmd command to erase data:
fastboot -w
Google camera stable app:
https://1-dontsharethislink.celsoazevedo.com/file/filesc/MGC_8.1.101_A9_GV1x_MGC.apk
If you are still want some video instructions here is a guide.
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Ok
jerryhou85 said:
Hi OP, if you are sharing other's work, please give them proper credit, for example, mentioning their ID (even they are not on XDA).
Thanks.
Click to expand...
Click to collapse
I will do
What do you guys prefer? Lineage or Elixir?
Eastw1ng said:
What do you guys prefer? Lineage or Elixir?
Click to expand...
Click to collapse
LineageOS but elixir is love because of android 12
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Fi
vince30 said:
OTA eu device at A14 with clean install.
Installed Gapps and boot.emmc.win from my twrp backup(A14 stock boot).
Installed magisk.
Current bugs:
- Fingerprint not working.
- Device vibration is insanely high(maxed). Turning off "Touch vibration" does not stop vibrations when typing on the keyboard.
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Fingerprint is working vibrations are also OK for me but after some days when u rebooted it cause that vibration bug
vince30 said:
Hopefully the next build would be stable.
Click to expand...
Click to collapse
Stable and bug-free enough for official would be nice.
Give him some time, i find its already good enough for a daily driver on my Nord 2
Thanks for this great build @pankspoo
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Fixed:
Device vibration bug seems to be fixed.
Auto brightness seems to work.
Update more bugs:
- Fingerprint not working.(perist image intact).
- Ringtone doesn't change after changing in sound settings.
- Slider still broken.
- Changing background startscreen/lockscreen with own photo will crash.
vince30 said:
Lineage 19.0 Beta Android 12 released, check telegram channel.
Why are GApps bundled with this release?
Device vibration bug seems to be fixed.
Alert slider still broken.
Click to expand...
Click to collapse
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
pankspoo said:
I will upload video and update this thread to arrow for now I can tell vibration fixed didn't know about later slider
Click to expand...
Click to collapse
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
vince30 said:
Why are GApps added to this new build(LOS 19) it sucks. I wish the developers give the user the freedom to install GApps /MicroG themself if they want.
LOS 18.1 is still preffered no GApps just clean LOS.
Found another bug with this build bluetooth scanning and connecting headsets work. But no sound output. Output is send to phone speakers.
Click to expand...
Click to collapse
U can use vanilla build if your don'ts want gapps inbuilt. If your not able to here sound then disable A2DP developer setting and Reboot your phone and see
vince30 said:
LOS 18.1 is still preffered no GApps just clean LOS.
Click to expand...
Click to collapse
How do you clean GAPPS from LOS?
exis_tenz said:
How do you clean GAPPS from LOS?
Click to expand...
Click to collapse
18.1 is without GApps included.
To remove them from LOS 19 you can use adb:
adb shell pm uninstall --user 0 package_name
Wifi Is not detecting
Pls Help
I am stucked
Turboisonfire said:
Wifi Is not detecting
Pls Help
I am stucked
Click to expand...
Click to collapse
We already got latest android 13 roms please use them
Android Open Source Project android-11.0.0_r46Disclaimer:* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Instruction:
Unlock boot loader
Connect the device to your computer in Fastboot mode (by pressing volume up while inserting the USB cable)
Download and extract the vendor image provided by Sony
Flash the vendor image provided by Sony
Code:
fastboot flash oem SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.img
Download and extract AOSP image android-11.0.0_r46.zip
Flash the boot, recovery, system, vendor and userdata images
Code:
fastboot flash boot boot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash system system.img
Code:
fastboot flash vendor vendor.img
Code:
fastboot flash userdata userdata.img
Code:
fastboot reboot
DONE!
If you have any problem with this recovery image, then download and flash the latest TWRP recovery release.
What's working:
Wifi
Hotspot
Bluetooth
GPS
4G/3G/2G
Camera
Fingerprint sensor (work without press the button)
BUGS:
TWRP recovery goes into bootloop, so start twrp again you need to flash the userdata.img (factory reset) via fastboot. There is this twrp recovery here on xda link.
Screen lag
After each start / restart the screen must be turned off and on again get to the homescreen
Credits:
Sony Xperia Developer World
Source code:
GitHub
Info:
ROM OS Version: Android 11
ROM Release: android-11.0.0_r46
ROM Kernel: Linux 4.14
Based On: AOSP
Status: Testing
Created 2022-02-14
Last Updated 2022-02-17
Reserved
bugs?
nathankaunang said:
bugs?
Click to expand...
Click to collapse
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
D_Riccardo said:
I am currently testing the build, as soon as I find bugs I will report them. If you have specific requests to test, please propose them. At the moment everything seems to be working fine.
Click to expand...
Click to collapse
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
JimKatsanos said:
I mean, are the laggy screen bug or the green camera, or the signal drops bugs fixed?
Click to expand...
Click to collapse
The screen lags slightly, the camera work perfect and for now I did not see any signal drops
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
hihiman1 said:
Hi, the bugs I found:
- after each start / restart the screen must be turned off and on again get to the homescreen
- SIM card is not detected at all
Click to expand...
Click to collapse
Thank you, I have also encountered that problem of the screen at startup. The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
D_Riccardo said:
...The sim card not detected it's strange I tested the data traffic and it works. I think this kernel 4.14 has more problems than the 4.4.
Click to expand...
Click to collapse
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
hihiman1 said:
Maybe it's linked to the latest version of SW_binaries_for_Xperia_Android_11_4.14_v9a_yoshino.zip (released 15.02.2022) v8a is no longer available
Click to expand...
Click to collapse
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
D_Riccardo said:
Yes, I see they updated the .zip file on the official site, luckily I didn't delete the file I used, I uploaded the v8a version here: https://www.udrop.com/6n1x/SW_binaries_for_Xperia_Android_11_4.14_v8a_yoshino.zip
Let me know if at least solved the problem with the sim card, so I will update the link in the post.
Click to expand...
Click to collapse
Yes now it works - please add the link to SW_binaries also in the 1st post
Wouldn't it be said to install the rom on the g8343?
Ramfisrd said:
Wouldn't it be said to install the rom on the g8343?
Click to expand...
Click to collapse
I would not risk to install to g8343, it could work as not