{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am sharing my kernel/boot.img, which is build from Sony Open Source/Qualcomm/ and android source (Very close to Stock KERNEL). Designed to keep balance security/ with high Performance and battery life.
Code:
###Disclaimer###
I am not responsible for any damage, broken or boot looping.
Please read the instructions and notes before flashing anything. Don't ask me if you don't read the instructions.Please respect and try to help each other. You may face sometimes that I cannot answer your questions/or answer your questions a bit later. I am busy with my work and don't have enough time to read and answer all your questions at the same time.
DONATE ME HERE
DONATE-HERE
##############################
Requirements-
##############################
- A working driver for your device.
USB drivers for Xperia devices
- Unlock bootloader
- A Working TWRP-with latest patch security
- YOUR firmware must match my kernel version. I used to update the kernel with latest firmware.
- Backup your stuff for future
- YOU NEED a refresh stock ROM (means you have to wipe EVERYTHING). Use flashtool to flash the latest firmware. (Remember to check Wipe USERDATA in flashtool). It seems not necessary if you have already flashed my kernel and have a working camera
- USE LATEST FLASHTOOL VERSION TO FLASH THE LATEST FIRMWARE
- (DOWNLOAD FROM HERE:- LATEST FLASHTOOL)
##############################
Features 11/MARCH/2019
##############################
- Based on latest kernel source VERSION = 4, PATCHLEVEL = 4, SUBLEVEL = 148 (47.2.A.8.24) MARCH, 2019
- Up to date with the September security update—MARCH, 2019
- Hide verifiedbootstate from /proc/cmdline in order to fix the failed SafetyNet CTS check(It can still fail through other means)-GOOGLE PAY SHOULD WORK
- Remove verifiedbootstate flag from /proc/cmdline - Disable CRC check
- Support wireguard VPN protocol
- dm-verity removed
- Sepolicy is patched for latest Oreo (deodex ROMs)
- Scheduler optimize/support for heterogeneous multi-core. Battery efficiency
- Energy Aware Scheduling (EAS) feature is enabled/optimize energy consumption for advanced multicore SoCs
- Update and add Qualcomm PM driver/APM driver updated reduce battery usage during sleeping
- Enable latest energy aware scheduling patches
- Multi-core scheduler enable/optimized
- A lot subsystems converted to use power efficient work-queues
- CAF improvements and optimized
- Enable latest energy aware scheduling patches
- Enable work-queue power-efficient mode by default
- Several other patches to improve the speed and battery usage
- Tweaked the scheduler to reduce/save power by scaling down the frequency of the CPU's or idling them,
- Tweaked to predict the best time to save power on the CPU without affecting performance
- Tweaked/optimized the scheduler to balance the load across all CPUs without any regards to the power costs.[/SIZE]
##############################
Instructions-
##############################
- Reboot into bootloader mode and following the following steps
Code:
- adb devices
- adb reboot bootloader
- fastboot devices
- fastboot flash boot boot.img (flash my kernel/boot.img)
- fastboot reboot
##############################
Downloads
##############################
XPERIA-XZ1 (G8341)+XPERIA XZ1 Dual-(G8342)-LATEST-47.2.A.8.24-(11/MARCH/2019)
##############################
XPERIA XZ1 (G8341)+(G8342)-ALL-BOOT IMAGES-[KERNEL][DRM-PATCHING]-
##############################
Source/GitHub
##############################
Kernel Source
-47.1.A.12.xxx
https://github.com/Nexusma/msm-4.4
https://github.com/toffyjan/android_kernel_Sony_lilac_poplar
https://github.com/sonyxperiadev/device-sony-lilac
IF YOU LIKE MY WORK AND WANT ME TO CONTINUE, THEN DON'T FORGET TO BUY ME COFFEE
DONATE ME HERE
DONATE-HERE
Special Thanks To:
If you can, donate and respect all the devs
@Chainfire for his great work to achieve root SuperSU
@Sultanxda for his great work in android kernel and SafetyNet CTS check
@modpunk for TWRP-recovery 3.2.1-0 and drm-fix THANK YOU
@Androxyde for Flashtool. merci beaucoup pour tout
@munjeni for his great knowledge and tools for extracting SIN images
@sToRm// for his effort on DRM work, THANKS
@SuperR. for SuperR's Kitchen , THANK YOU
@M-Rom Thanks for sharing drm-fix and patch
@serajr Thanks for DRM Fix Workaround and Sony RIC disabler @tobias.waldvogel thanks for older drmfix and his great effort.
THANK YOU SONY FOR SUPPORTING DEVs AND ALLOWING US TO UNLOCK THE BOOTLOADER
ALSO THANKS FOR EVERYONE ELSE EVEN I FORGET TO MENTION THEIR NAMES.
Thanks to XDA And everyone else who share their knowledge and works among us in xda.
Yeaaaah!! Now time to custom stock rom! [emoji7]
Wysłane z mojego G8342 przy użyciu Tapatalka
janjan said:
-
Click to expand...
Click to collapse
Finally! Will download and try your kernel tomorrow!
Is it needed to flash SuperSU, or is this kernel pre-rooted through Magisk?
Thank You! Amazing Work!
All works fine on my G8341!
xFirefly93 said:
Finally! Will download and try your kernel tomorrow!
Is it needed to flash SuperSU, or is this kernel pre-rooted through Magisk?
Click to expand...
Click to collapse
I had to patch the boot.img manually with magisk and then flash with it via TWRP.
Now Magisk SafetyNet and Xposed are working like a charm!
Gnome1911 said:
Thank You! Amazing Work!
All works fine on my G8341!
I had to patch the boot.img manually with magisk and then flash with it via TWRP.
Now Magisk SafetyNet and Xposed are working like a charm!
Click to expand...
Click to collapse
How-to do this? This is my first Android device after being away from the OS for 1,5-2 years, so I am basically a newbie from scratch on the more "advanced" stuff.. ?
Want to help me out?
xFirefly93 said:
How-to do this? This is my first Android device after being away from the OS for 1,5-2 years, so I am basically a newbie from scratch on the more "advanced" stuff..
Want to help me out?
Click to expand...
Click to collapse
Sure
Your Bootloader is unlocked and TWRP is installed?
Then just download the the Zip from the first post for your device and extract the boot.img
Download and install Magisk Manager.
When you now open open Magisk Manager on your Smartphone, you will be asked to install the latest Magisk.zip. Now press patch boot image and navigate to the extracted boot.img.
When the progress is finished boot into TWRP press install, select install img (bottom of the screen), navigate to the patched boot.img (internal memory/Magisk Manager) and press install.
After installation you can reboot and now Magisk should be working
Thank you, great work. Tried it and booting and root with magisk is fine.
Except camera doesn't take a picture. It opens buth freezes when i want to take the picture
Gnome1911 said:
Sure
Your Bootloader is unlocked and TWRP is installed?
Then just download the the Zip from the first post for your device and extract the boot.img
Download and install Magisk Manager.
When you now open open Magisk Manager on your Smartphone, you will be asked to install the latest Magisk.zip. Now press patch boot image and navigate to the extracted boot.img.
When the progress is finished boot into TWRP press install, select install img (bottom of the screen), navigate to the patched boot.img (internal memory/Magisk Manager) and press install.
After installation you can reboot and now Magisk should be working
Click to expand...
Click to collapse
Ramdisk is already patched. No need to patch it again. Flash the zip from first thread and then flash the latest magisk. Done
Xposed is also working..no issue (unofficial build)
Carlovn said:
Thank you, great work. Tried it and booting and root with magisk is fine.
Except camera doesn't take a picture. It opens buth freezes when i want to take the picture
Click to expand...
Click to collapse
It shouldn't effect your camera. Did you flash anything else maybe?
Don't tested the Cam before...
Same here. Cam freezes on focus
---------- Post added at 09:22 AM ---------- Previous post was at 09:20 AM ----------
janjan said:
Ramdisk is already patched. No need to patch it again. Flash the zip from first thread and then flash the latest magisk. Done
Xposed is also working..no issue (unofficial build)
Click to expand...
Click to collapse
I tried to flash Magisk.zip and get an error.
So i tried it as i wrote before and this worked
janjan said:
It shouldn't effect your camera. Did you flash anything else maybe?
Click to expand...
Click to collapse
I flashed part-1 of the previous drm fix. That could be the problem.
When i get home I will flash .34 to start over and check if this fixes the problem
Or does anybody know how to change back to the original secd
Does this kernel work with the DRM fix? What I mean is, can we flash the kernel, then flash the DRM fix and flash Magisk so we can have both the DRM fix for the camera and Magisk for root?
N1ghtr08d said:
Does this kernel work with the DRM fix? What I mean is, can we flash the kernel, then flash the DRM fix and flash Magisk so we can have both the DRM fix for the camera and Magisk for root?
Click to expand...
Click to collapse
The whole meaning for this is that you don't need the DRM fix with this kernel. So flashing this kernel and magisk you shuld be good to go.
Edit: Camera doesn't seem te work. I misread in the title that it said DRM fix but is dm fix...
I'm going the new firmware now then this kernel and Magisk to test.
Fingers crossed ?
---------- Post added at 11:42 AM ---------- Previous post was at 10:47 AM ----------
Ok so I upgraded the OS to 12.34 then reflashed TWRP latest from modpunk then rebooted to recovery and flashed the kernel and Magisk and I got a bootloop so....
I reflashed again with newflasher, TWRP, reboot to recovery, flash the kernel then this time I rebooted to system and again back into recovery then I flashed Magisk and it all booted fine, but here's the problem.....
The camera doesn't work. It has no DRM fix so all the pictures are that horrible green square.
Should I flash the DRM fix separately or what?
---------- Post added at 11:52 AM ---------- Previous post was at 11:42 AM ----------
So I decided to boot into recovery again and flash 2 of the 3 DRM fix files (the DRM fix and Ricoff) and they flashed fine, then I rebooted and tested the camera and it just hangs even I try to take a picture.
Does anybody have any ideas what we can do to have the DRM fix working alongside Magisk?
I am going to upload new build. Optimized more for battery improvement, remove some boosting to reduce error, bootloop, re-patched the ramdisk proper to minimize bootloop, and other tweaks.
janjan said:
I am going to upload new build. Optimized more for battery improvement, remove some boosting to reduce error, bootloop, re-patched the ramdisk proper to minimize bootloop.
Click to expand...
Click to collapse
Thank you! Is there any hope for a working camera?
Carlovn said:
Thank you! Is there any hope for a working camera?
Click to expand...
Click to collapse
Unfortunately I haven't own the device. I have only XZ1 compact. I have no issue with camera. But I will take a look when I have time.
janjan said:
Unfortunately I haven't own the device. I have only XZ1 compact. I have no issue with camera. But I will take a look when I have time.
Click to expand...
Click to collapse
Yes, please do. We really appreciate your work but we desperately want Magisk and a working camera
Thank you very much, @janjan for your effort.
There seems to be a difference in the DRM handling between XZ1 and XZ1Compact, resulting in a non-working camera on the XZ1 even if it works on the Compact.
It is really nice of you to compile this kernel for our device, but unfortunatly it doesn´t really work all the way
pergoteborg said:
Thank you very much, @janjan for your effort.
There seems to be a difference in the DRM handling between XZ1 and XZ1Compact, resulting in a non-working camera on the XZ1 even if it works on the Compact.
It is really nice of you to compile this kernel for our device, but unfortunatly it doesn´t really work all the way
Click to expand...
Click to collapse
I just found out some issue with G8342-Dual. It seems G8341 and G8342 are used two different deconfig for building Kernel. I am going to fix it now. I will try to look at DRM soon.
So don't flash G8342 boot.img yet. Going to remove the link.
Related
I love DooMKernel by DooMLoRD , but he does not have Z3 (also Z3 Compact).
So I started to port DooMKernel for Z3 and Z3 Compact.
Please do not ask me to add something, I don't know much about kernel and git right now...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
* banner by MysticEnforcer
View attachment 2995202
View attachment 2995203
juggly.cn and other Japanese website - please do not use this thread as a source.
I have Japanese post at androplus.org
Download from official website
Changelog
What is FOTA kernel recovery?
NOTE: this is old info
Xperia doesn't have recovery partition for user,
but we have FOTA kernel partition for OTA.
Since we have to unlock bootloader and OTA won't work on unlocked,
we can re-use useless FOTA kernel as recovery partition using Dees-Troy's "extract_elf_ramdisk".
With FOTA kernel recovery, you can update your recovery without updating kernel.You can flash images to FOTA kernel by fastboot command like
Code:
fastboot flash recovery fotakernel.img
To enter into FOTA recovery, press power key when LED is on.
How to restore DRM functions?
When you unlock bootloader you will lose X-Reality, noise reduction and so on,
but you can restore them!
Original thread is here, but I updated steps for Z3 and Z3 Compact.
1. Download zip from original thread
* Choose KitKat version (for 4.4) or Lollipop version (for 5.0)
2. Place zip in internal or external storage of your device
3. Reboot into recovery and do Factory Reset
4. Reboot into flashmode and flash FTF with Flashtool
Any FTF is OK, but of cource use FTF for same version you are using now.
Wipe: Check APPSLOG and CACHE
Exclude: Don't check
5. Close Flashtool, unplug and plug your phone and reopen Flashtool, then relock bootloader
Click BLU icon to show relock button and click it.
6. Flash FTF (same as 4.)
7. Close Flashtool, unplug and plug your phone and reopen Flashtool, then unlock bootloader
Click BLU icon to show unlock button and click it.
8. Reboot into fastboot mode and flash my kernel
9. Reboot into recovery and install DRM Restore zip
10. Reboot
11. Done!
After doing this, do not restore old data since it will revert DRM restore.
You can restore system with recovery and use Titanium Backup or something to restore app data.
Note: When you flash new ROM (not kernel), you must flash DRM Restore zip.
If you get "net::ERR_NAME_NOT_RESOLVED" when connecting xda,
please disable PrototypeProtection with Titanium Backup or something similar.
How to use F2FS?
Read this:
http://forum.xda-developers.com/xperia-s/s-development/tutorial-migrate-filesystem-to-f2fs-ext4-t3004755
Kernel sources
https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
I should learn how to use git before creating custom kernel...
Credits
DooMLoRD
Faux123
Dees_Troy & TeamWin
Phil3759
Myself5
glocklee
pec0ra
and many other people involved in Z3 development
DO NOT talk about rooting with locked bootloader here.
XDA:DevDB Information
AndroPlusKernel for Z3 Compact, Kernel for the Sony Xperia Z3 Compact
Contributors
AndroPlus, [#APK_cont]
Source Code: https://github.com/WedyDQ10/android_kernel_sony_msm8974ac
Kernel Special Features:
Version Information
Status: Stable
Created 2014-12-28
Last Updated 2016-04-09
great! can't wait to test it... i'll see what the result is
Thanks for this. Also, I donated to Doomlord lately, in the hope he might end up buying a Z3C (and also just a general thank you for all he's done for the Android development community).
AndroPlus said:
I love DooMKernel by DooMLoRD , but he does not have Z3 (also Z3 Compact).
So I started to port DooMKernel for Z3 and Z3 Compact.
Please do not ask me to add something, I don't know much about kernel and git right now...
View attachment 2995202
View attachment 2995203
juggly.cn and other Japanese website - please do not use this thread as a source.
I have Japanese post at androplus.org
Features
Fixed entering to recovery -v4
CPU OverClock upto 2.89GHz -v3
Intelli-Plug driver v3.8 -v2
Intelli-thermal v2 -v2
Intelli-KSM -v2
Sound Control driver v3.6 -v2 [Not working]
PowerSuspend drivers -v2
Force FastCharge -v2
kernel level Color Control -v2
kernel mode NEON -v2
msm_cpufreq_limiter "Snake Charmer" -v2
per-core overall stats -v2
NTFS R/W support -v2
I/O schedulers -v2
BFQ
FIOPS
CPU governor (Some are not tested) -v2
Intelli-active
LionHeart
SmartAssV2
LagFree
Wheatley
Disabled ric -v1
CWM -v1
TWRP Recovery -v1
PhilZ touch recovery -v1
CPU OverClock upto 2.8 GHz -v1
GPU OverClock -v1
CPU Undervolting -v1
SIO I/O scheduler -v1
Requirements
Xperia Z3 Compact [D5803 & D5833]
stock 4.4.4
23.0.A.2.105 or .93 -v1~
DO NOT use this kernel with CM or CM based ROM.
This kernel is only for stock or stock based ROM.
Unlocked bootloader
Apps such as FauxClock
Download
v4 - Z3 Compact D5803 23.0.A.2.105
v4 - Z3 Compact D5833 23.0.A.2.93
v3a - Z3 Compact D5803 23.0.A.2.105 (beta)
How to flash
1. Reboot into bootloader
2. Flash kernel using fastboot
Code:
fastboot flash boot AndroPlusKernel_[B][version and variant][/B].img
3. Reboot
Code:
fastboot reboot
Kernel sources
https://github.com/WedyDQ10/AndroPlusKernel_leo
I should learn how to use git before creating custom kernel...
Credits
DooMLoRD
Faux123
Dees_Troy & TeamWin
Phil3759
and many other people involved in Z3 development
DO NOT talk about rooting with locked bootloader here.
Click to expand...
Click to collapse
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
shafiq01 said:
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
Click to expand...
Click to collapse
What happened, I don’t experienced anything but seamlessly perfect… I love this kernel and my experience now in my z3c is absolutely great! Try to re download maybe you got the corrupted downloaded.
shafiq01 said:
It doesn't work, it goes into bootloop, i couldn't even boot into cwm afterwards
i had the to reflash CWM thrugh fastboot and then i could boot my device.
firast i thought it could be related to cooperate mail, so i removed password and account
and tried to flash the kernel again, same bootloop again. so i'll wait to there is a stable one
or am i doing something wrong?
fw xxx.105 rooted with cwm on it and all kinf of other stuff
Click to expand...
Click to collapse
One member confirmed it's working on his D5803 .105, so it might be corrupted download.
Please redownload from mirror (mega).
AndroPlus said:
One member confirmed it's working on his D5803 .105, so it might be corrupted download.
Please redownload from mirror (mega).
Click to expand...
Click to collapse
Indeed, I believed it is corrupted copy… for me .105, I highly recommend using this kernel, truly awesome! the graphic really works very well now, the battery perform very fine as well, I liked the new version of the cwm too! I think a lot of benefits will provide this to your z3c device, many thanks @AndroPlus you rock men! Cheers
flashed on my z3c with .105. no bootloops, haven't come across any other issues yet. I will say that my battery life seems to be lasting a bit longer. i'll keep an eye on it for the next couple of days and report back! I still haven't played with any kernel settings. thank you for porting this over!! if you have any suggestions for the kernel settings let us know!
it is working now, you guys were correct, it was a corrupt download. I could see the first file downloaded was 8mb the next one was 18mb
thank you xda members, appreciated
Thanksss
When i use Trickster to amend sound control, device reboots, anyone else get the same, also get the same when adjusting voltage, tried -25mv, same thing occurred.
Ill post a logcat shortly
Cheers
@AndroPlus
Could you please post the MD5 hash in the OP or upload the files to a site that shows the MD5 so we can confirm the file, because flashing a corrupted kernel could harm our devices.:good:
Dsteppa said:
@AndroPlus
Could you please post the MD5 hash in the OP or upload the files to a site that shows the MD5 so we can confirm the file, because flashing a corrupted kernel could harm our devices.
Click to expand...
Click to collapse
Yes please. Or a zip file will do because Winzip or 7zip usually shows error while extracting.
spida_singh said:
When i use Trickster to amend sound control, device reboots, anyone else get the same, also get the same when adjusting voltage, tried -25mv, same thing occurred.
Ill post a logcat shortly
Cheers
Click to expand...
Click to collapse
OP says sound control driver isn't working. Use undervolt at your own risk. If it rebooted, try a lower value like -5 mv
Btw how do I get into Philz recovery? Up is for CWM, down is for TWRP. found it... camera button : )
Changed to flashable zip and uploaded to BasketBuild which can show MD5
Hello, is it possible to get the stock original kernel for Z3 Compact D5803 23.0.A.2.105 img (Not modified or rooted one ) to flash it via fastboot without restoring the whole stock ROM again? Thanks!
wrwr said:
Hello, is it possible to get the stock original kernel for Z3 Compact D5803 23.0.A.2.105 img (Not modified or rooted one ) to flash it via fastboot without restoring the whole stock ROM again? Thanks!
Click to expand...
Click to collapse
You can create stock kernel flashe zip by extracting jernel.sin from ftf, then rename to boot.img and overwrite boot.img in the zip.
AndroPlus said:
You can create stock kernel flashe zip by extracting jernel.sin from ftf, then rename to boot.img and overwrite boot.img in the zip.
Click to expand...
Click to collapse
Thanks AndroPlus, but there is two files: kernel.sin and fotakernel.sin, which one, and can I flash it via fastboot after renaming to boot.mg? easier than to include in a zip and flash via recovery.
wrwr said:
Thanks AndroPlus, but there is two files: kernel.sin and fotakernel.sin, which one, and can I flash it via fastboot after renaming to boot.mg? easier than to include in a zip and flash via recovery.
Click to expand...
Click to collapse
Oh I forgot to say you have to decrypt kernel.sin (not fotakernel) with Flashtool.
You can decrypt kernel.sin by "Tools" -> "Sin Editor" and select kernel.sin, then "Extract data".
Then you can flash kernel via fastboot:
Code:
fastboot flash boot kernel.elf
AndroPlus said:
Oh I forgot to say you have to decrypt kernel.sin (not fotakernel) with Flashtool.
You can decrypt kernel.sin by "Tools" -> "Sin Editor" and select kernel.sin, then "Extract data".
Then you can flash kernel via fastboot:
Code:
fastboot flash boot kernel.elf
Click to expand...
Click to collapse
Hey AndroPlus, I did all the steps OK, but when flashing (fastboot flash boot kernel.elf) I got this error via fastboot: FAILED (remote: image is not a boot image) ?
wrwr said:
Hey AndroPlus, I did all the steps OK, but when flashing (fastboot flash boot kernel.elf) I got this error via fastboot: FAILED (remote: image is not a boot image) ?
Click to expand...
Click to collapse
hmm...I thought it can be done with fastboot, but it seems I'm wrong...
so you have to rename kernel.elf to boot.img and overwrite boot.img in zip, then install it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Machao44(the original dev) has now created the XDA thread over here,head here instead of this link,use this thread only if you want to use the older versions of the ROMs or some fixes:
https://forum.xda-developers.com/z3-compact/development/rom-los-xperia-ui-z3c-t3654894
It has the stock Sony Nougat theme and apps found on Xperia XZ Premium,XZs,Xperia L1 and so on.
Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect etc.
Usually the ROM itself is very fast and it is good as a daily driver.
You can download Xposed for this ROM as an addon,but not sure how stable it is.
Install guide:
NOTE: If you are coming from Concept ROM,it is NECESSARY to flash back to stock MM,or you will have a bootloop or the ROM will just fail to install.
1. Download the ROM from here:
https://mega.nz/#F!ZgAhhJLI!PvIf-ZLY0Ihs6fY-8c6SBA (link from Machao44's thread)
2. Download SuperSU or Magisk,both do work(they are not included in ROM zip)
3. Download & install TWRP recovery found on the Lineage thread(if you don't know how to install go to @tomascus's thread and read the second post where the install guide is)
4. Install the zip and start Aroma
5. Select the apps and features you need
6. Once it's done,flash any additional zips and reboot.
NOTE 2: Recovery might get removed after you flash the ROM(if you flash unmodified versions of ROMs),so you need to re-flash through fastboot.
For custom kernels,as reported for now Kernel12 version 11 works fine with this ROM,if you want to try something else then try to flash it and report back if it works,since I believe that not all custom kernels for LineageOS do work.
If Wi-Fi has very weak signal or it doesn't work at all,download and flash this zip:
https://mega.nz/#!hh8m3aIb!z1X66R8uK8BrG9g853lvDtkDiMdTAl7wbACGyXNxwjo
If you have issues with Bluetooth calling,flash this zip(thanks to @jimmy123322):
https://www.androidfilehost.com/?fid=673368273298979213
If you use M-ROM 1.2.0 or 1.2.5 you will have a brightness issue,to fix download the framework-res.apk from this post(thanks @wolfmannight):
https://forum.xda-developers.com/z3...ny-themed-android-7-1-1-t3627518/post73000345
Current issues:
-Sony Themes doesn't work,themes won't apply
If you do find any other issues,please report them here.
Links for older versions:
https://mega.nz/#F!YlAkxBLL!mJra95HcQu9ZjD0JbTvyjw - M-ROM 2.2.0
https://mega.nz/#!B0EBxIAD!8fa0OmRI1Z5nUpa8j-2GqmLH63wkmUXNFwj0QmRrQjI - M-ROM 2.1.0
https://mega.nz/#!88l2ybTB!xVuQJIJZ8x8yGAt4j2U8aFFiE6aDogg92ttttg3kfZo - M-ROM 2.0.0
https://mega.nz/#!hwkC0SKZ!KKs0RTnK1ASeYKG6IGtH8pxg5wP96gaMeDMU9D7qhJ4 - M-ROM 1.2.5
https://mega.nz/#!0oNh0BQL!xy8Z53b_SpChzFZbcy24jPAnvX6hhVVG5UaEpiamc5g - M-ROM 1.2.0
If anyone needs for experimental purposes here are the links to the unmodified ROMs:
https://mega.nz/#!w4kClZCZ!puWpP9Y-uwg8kZUcVLDFM_TlD9gVMfFL4YDkslsTLLk - M-ROM 2.1.0
https://mega.nz/#!Ak1kHaja!xVTh-K8NX-g9YIjlnVn0t0X2W9K93NtbR42JDJm0XQ0 - M-ROM 2.0.0
https://mega.nz/#!EhsQxRBR!E214YYEfcBc_MirbwvV2ghRE6SC9M7xQrTAdYsiiZAA - M-ROM 1.2.5
https://mega.nz/#!dls0HJSS!Zu0brC3-FFfkvvxJDVAwL2ohlbt3QmMVLH4y_-VoC5c - M-ROM 1.2.0
Big thanks to the original devs of this ROM:
@M-Rom - seen as machao44 on bbs.gfan.com
@SuperLamic
@rcstar6696
@nailyk
@xkeita
@Myself5 - original dev of CarbonROM which is based of LineageOS kernel sources
@tomascus - original dev of the base ROM - LineageOS
Also thanks to:
@vooR9er - helped to translate the Aroma installer
@ztxgeol - found every single download link for every version of this ROM including the link to Xposed,and I have just re-uploaded them all to a better download provider so you are not forced to download from Baidu
@unpair - thanks for testing almost every single version of this ROM and also thanks to everyone who tested the ROMs,but he did help the most
"Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect and so on."
Does this also mean that image enhancing (Settings -> Display) is working also? (if TA.img was "sideloaded" with PoC Tool od DK.ftf)
Is this that ROM where framework etc were modded that LOS reacts like Sony stock regarding all this DRM stuff?
fluffi444 said:
"Also includes the stock Sony camera app with 4K 60FPS recording support,AR effect and so on."
Does this also mean that image enhancing (Settings -> Display) is working also? (if TA.img was "sideloaded" with PoC Tool od DK.ftf)
Is this that ROM where framework etc were modded that LOS reacts like Sony stock regarding all this DRM stuff?
Click to expand...
Click to collapse
To be honest,I don't really know,and I believe there is no image enhancing of any sort,I wasn't really able to reach the Settings to see that.
Oops,I uploaded by accident the wrong build to MEGA,the link won't work for 45 minutes,will keep you updated.
EDIT: You can now download the ROM and try to install it.
HUGE CHANGELOG:
-First of all,when installing the ROM do not press to install Google Play services,that actually corrupts everything,will mention in it in OP
-Google Play works fine
-To answer @fluffi444 image enhancing is actually there with Sony Sound mods,but Sony themes currently doesn't work
-The ROM doesn't come with any keyboard installed,so I will include Gboard inside the ROM
-I will debloat the ROM from chinese apps
New build will be up with screenshots in the end of the night.
EDIT: Build is now up! Download it and tell me how it runs!
First of all thank you for this ROM, planning to try some day soon
How is camera quality?
Do I need to flash stock image first or can I flash directly from lineageos?
k13tas said:
First of all thank you for this ROM, planning to try some day soon
How is camera quality?
Do I need to flash stock image first or can I flash directly from lineageos?
Click to expand...
Click to collapse
Camera quality is like in stock ROM,and it doesn't really matter what you have before installing this ROM,but it only won't work if you are now running Concept ROM,if that is the case then yes you need to flash the stock image first
Dinkec27 said:
Camera quality is like in stock ROM,and it doesn't really matter what you have before installing this ROM,but it only won't work if you are now running Concept ROM,if that is the case then yes you need to flash the stock image first
Click to expand...
Click to collapse
Thank you for answering
So DRM keys are not needed with this ROM, right?
k13tas said:
Thank you for answering
So DRM keys are not needed with this ROM, right?
Click to expand...
Click to collapse
Nope
After Clean installation I get system ui crash cant use this rom..
shrazy said:
After Clean installation I get system ui crash cant use this rom..
Click to expand...
Click to collapse
SystemUI crash? Try to get a logcat and I'll look into it,while you can in that time try to re-download the ROM and try to install it again,and make sure you use TWRP from the link in the Lineage thread.
Would like it very much, but i cannot receive calls, can make phone calls though.
Second time i started fresh from stock, unlocked bootloader and fastboot flashed fotakernel twrp from lineage thread, same problem: when i call myself from another phone the screen turns white with xperia logo and the call ends.
Sorry i can't take logs (never tried actually)
Also when i reboot into recovery chinese twrp appears and i can switch only to english (needed to watch a youtube video to figure out which was the settings button). I'm quite sure it's not the one i installed (don't remember the number version).
Google play works fine: don't understand what you wrote in op about unchecking it. In the aroma you are asked to check what you don't want to be installed, and without it i wouldn't know how to do.
Well i hope to use this ROM in the future, Thank you for your efforts so far
The brightness on my screen is always high, I can't change it... The brightness is in automatic and the sensor works well
unpair said:
Would like it very much, but i cannot receive calls, can make phone calls though.
Second time i started fresh from stock, unlocked bootloader and fastboot flashed fotakernel twrp from lineage thread, same problem: when i call myself from another phone the screen turns white with xperia logo and the call ends.
Sorry i can't take logs (never tried actually)
Also when i reboot into recovery chinese twrp appears and i can switch only to english (needed to watch a youtube video to figure out which was the settings button). I'm quite sure it's not the one i installed (don't remember the number version).
Google play works fine: don't understand what you wrote in op about unchecking it. In the aroma you are asked to check what you don't want to be installed, and without it i wouldn't know how to do.
Well i hope to use this ROM in the future, Thank you for your efforts so far
Click to expand...
Click to collapse
I wrote in the OP that you don't install Play because after I checked that it always crashed and dissapeared after a reboot.
For chinese TWRP,I didn't even know it was on there lol,so that's I guess another reason to flash TWRP from the Lineage thread after you flash the ROM.
For phone calls I really can't do much without logs or anything,so would highly appreciate if you try to get me a logcat of some sort,there are many guides online.
As for future plans for this ROM,I am looking to re-build it and use the latest Lineage build as base ROM to remove as much bugs as possible.
Kriztian96 said:
The brightness on my screen is always high, I can't change it... The brightness is in automatic and the sensor works well
Click to expand...
Click to collapse
So when there is no automatic brightness enabled the brightness is always high? I couldn't really notice that the only reason being I use my phone on the highest screen brightness all the time.
How about the blouetooth and reboot bugs of the other llineageOS? If there aren't, this rom can help find this bugs!
andry360 said:
How about the blouetooth and reboot bugs of the other llineageOS? If there aren't, this rom can help find this bugs!
Click to expand...
Click to collapse
Not sure,haven't had any random reboots tbh,even with the latest build I haven't had any random reboots nor any bluetooth issues,maybe those can apply for something else but I only use Bluetooth for connecting a Bluetooth speaker,headphones and occasionally transfering files and all of that worked.
Dinkec27 said:
So when there is no automatic brightness enabled the brightness is always high? I couldn't really notice that the only reason being I use my phone on the highest screen brightness all the time.
Click to expand...
Click to collapse
When the automatic brightness is enabled or not, the brightness is always high, and when I use the slider for change the level of it, it doesn't change, it's always the same high brightness... I can't use it in the dark because it's so high
Kriztian96 said:
When the automatic brightness is enabled or not, the brightness is always high, and when I use the slider for change the level of it, it doesn't change, it's always the same high brightness... I can't use it in the dark because it's so high
Click to expand...
Click to collapse
I'll look into it,thanks.
keep it up
It includes DRM patch and disabled force encryption.
Because fstab.qcom has been moved to system since 8.0, I cannot modify the boot image.
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
- It will not decrypt your data. In other words, you have to do factory reset (wipe data) if it's already encrypted.
- See encryption status in Setting->Security
You can download from the attachments.
41.3.A.2.24
G8231 - View attachment xzs-p3-2.24.zip Based on Nordic Combined
G8232 Dual - View attachment xzsd-p3-2.24.zip Based on Customized TH
41.3.A.0.401
G8231 - Download from a thread by @Pandemic
G8232 Dual - View attachment xzsdp3.0.401-unzip.zip Based on Customized VN (for fingerprint)
Also, patch View attachment drmfix.zip before first system boot.
41.2.A.7.76
G8231 - View attachment xzs-p2.7.76.img.zip
G8232 Dual - View attachment xzsd-p2.7.76.img.zip
41.2.A.7.65
G8231 - View attachment xzs-p2.7.65-extract-first.zip
G8232 Dual - View attachment xzsd-p2.7.65-extract-first.zip
41.2.A.7.53
G8231 - View attachment 8231-boot753noencrypt.zip
G8232 Dual - View attachment boot-7.53-noforceencrypt.zip
It's not flashable zip, so please extract before use.
It will bootloop if you flash wrong version.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to disable by yourself? - Not for Oreo
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
zlRampageSlz said:
Some of you guys might have a problem with TWRP encryption password. With stock kernel, /data will be encrypted in a few boots even if you set no password.
About this kernel:
- Working camera (DRM-patch)
- Disabled dm-verity (so we can use magisk)
- Can mount /data in recovery (it means we can install magisk inside /data)
- Pass both safetynet
- You can still encrypt any time
You can download from attachment.
View attachment 4246515
It's not flashable zip, so please extract it before use.
View attachment 4246527
How to disable by yourself?
Prerequisite:
- 32-bit linux (you can use it on liveboot drive or VM)
It doesn't work on cygwin (windows) because of its native executable. So use linux 32 bit (i386), or 64 bit (amd64) with multiarch.
- Unpack using mkbootimg tool made by xiaolu (I tried kitchen and it won't work)
- Open fstab.qcom
- Replace "forceencrypet" with "encryptable"
- Pack again
- Done!
Thanks tobias.waldvogel and xiaolu for their awesome tools.
If you have any question, feel free to ask me or some nice guys here.
Click to expand...
Click to collapse
i'd just like to ask a question.. are we gonna be able to have the tap2wake feature back? or it's just not possible...
Thank you! Can you recover?
谢谢!超逼真可以恢复吗?
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
tapperyaus said:
In what order to I flash recovery, root and the kernel? (I've never used a kernel before)
Click to expand...
Click to collapse
You have to unlock bootloader first before you can flash anything. Then just "fastboot flash boot <thatkernel>.img" in fastboot (blue LED). Recovery and root is optional. Normally, you have to use TWRP recovery to flash zip (su installer).
So, unlock bootloader -> flash kernel -> flash recovery -> install su in TWRP
Also, you can read detailed my tutorial here.
HellFish23 said:
Great, but you can just flash twrp-3.0.2-0-kagura.img instead of a newer version and it will work perfectly. For some reason the newer twrps for xz will ask for password to decrypt data
And can you make this for g231?
Click to expand...
Click to collapse
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
I've added G8231 kernel in the attachments.
zlRampageSlz said:
When you use 3.0.2-0, does it work while being encrypted? Or you have to do a factory reset to prevent further encryption.
Sure, I'll make for you guys when I'm free.
Click to expand...
Click to collapse
I understood the issue was twrp saying is encrypted while you didn't encrypt it yourself, may have misunderstood but I didn't test it while I actually encrypt it myself. And thanks!
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
tapperyaus said:
Everything is working fine for the kernel, I no longer get the green photos and I can download Super Mario Run (my go to Safetynet app), but when I try to boot into recovery to flash Magisk all I get is a black screen. I tried flashing another TWRP version and still get a black screen. I'm on the dual sim variant.
Even if this problem can't be fixed, thanks for the kernel!
Click to expand...
Click to collapse
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
zlRampageSlz said:
Could you give me TWRP log while installing magisk? Try using uninstaller and wiping cache first. Then flash stock kernel before install magisk again.
Click to expand...
Click to collapse
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
tapperyaus said:
The problem wasn't installing magisk, it was that TWRP wasn't installing correctly. Attempting to reach TWRP leads to a black screen. It's easily avoidable by booting the twrp.img through adb/fastboot (then flashing magisk there), I just can't install TWRP onto the phone.
Click to expand...
Click to collapse
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
zlRampageSlz said:
Sorry I misunderstood your question, TWRP right now cannot boot in the normal way (from fastboot/adb, or even TWRP itself). You have to hold power+vol down at the same time.
Click to expand...
Click to collapse
Why can't i enter the TWRP by hold power+vol down at the same time? The screen just turned between black and logo.
Thanks.
I found the problem is that i forgot to flash recovery
Hi, Does this kernel support DoubleTap2Wake?
Ok
AWESOMEE..
Xenroe said:
Hi, Does this kernel support DoubleTap2Wake?
Click to expand...
Click to collapse
Not yet, I'll look around if I have some time.
zlRampageSlz said:
Not yet, I'll look around if I have some time.
Click to expand...
Click to collapse
Thanks, i would've flashed XZ Kernel just so i can have DoubleTap2Wake if i could.. I'll be looking forward to your update...
This kernel is good, but I have a question: When I brush the kernel, I can't enter TWRP through the combination of the volume key and the power button. Instead, my phone switch between the logo and the black screen. Do I need to write a TWRP again?(My English is not good, please fogive me:crying
MARS SOM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into a simple Magisk Module.
Features:
Ported Pixel Apps
Ported Pixel Features
Ported Pixel UI & Colors
Ported Pixel Black Dark Mode
Xperia Sound Enhancements
Xperia Pro-I Content Ported
HTC UI & User Sounds
Xperia Live Wallpapers
Enabled various Android Features
Enabled various Hardware Features
Enhanced Security Support
Enhanced Display Quality
Enhanced Audio Output
Enhanced Audio Input
Enhanced FHD/4K HDR Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Stable 24+
Android 13 Stock Xperia FW
Magisk Init.d Injector
Download:
Sign in - Google Accounts
Bugs:
Report them if You found one!
Donations:
paypal.me/miustone
Reserved <3
Nice work. I'm glad to already see some custom ROMs (well, in that case, SOM).
However, this is the first time I encounter a SOM, is it just a Magisk module that can be turned on and off at will, switching between stock and Mars? Or shouldn't I do that?
Miustone said:
Welcome to MARS SOM
The first so called SOM
Systemless-On-Memory
SOM - The right naming for a new age of Android ROMs
Years of porting, Stock ROMs and My Patches came to an end...
Since Magisk has grown to a full root and modding Solution for Android have i switched with My Development to creating Magisk Module Patches. Or in other Words, Systemless ROMs.
Mainly focusing on extending the Android Build Props are there also pure Parts of the latest Pixel Device Firmwares. Get the full Pixel UI Expierence, get extra Pixel Functions and Apps together with a better overall Experience. Better Audio In- and Output, better Display Calibrations, better Performance, more Functions packed into two Zip Files...
Features:
Full Camera API2 Support
Full Pixel User Interface
Full Darkmode Support
Ported Pixel Apps
Ported Pixel Features
Enabled various Android Features
Enhanced Security Support
Enhanced Display 4K HDR Support
Enhanced Audio Output
Enhanced Audio Input
Enhanced Display Output
Enhanced Camera Functionalities
Enhanced Graphical Handling & Rendering
Enhanced Network Functionalities
Faster booting and Reboots
Requirements:
Magisk Beta or Canary Channel
Android 11
A way to extract and create Zip Files
(For GitHub Zips)
Downloads:
Miustone - Overview
Founder of Dev Ice Software Technologies. Miustone has 10 repositories available. Follow their code on GitHub.
github.com
Note: Zips from GitHub can't be flashed ootb.
GitHub?!:
Extract the 2 Downloaded Zips and repack everything inside of the second "MARS_SOM_XXX" Folders to Zips
Flash these Zips with Magisk and enjoy <3
Bugs:
QuickSwitch is needed for the Pixel Launcher
Donations:
paypal.me/miustone
Click to expand...
Click to collapse
Could you please tell me where can I obtain more information about this "Mars Som" and more details instruction to install it. Thanks for your reply.
Thanks for Your Interest! I'm reconstructing the SOMs on GitHub and the ReadMe's there will be updated soon with more Infos! For now, just Check My (Discontinued) MARS-SOM Repo on GitHub...
BR
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
tonysunshine said:
Hrm guessing this isnt rdy yet? Just tried installing the base and rom in Magisk 23 as modules but it causes a bootloop. Noticed on GitHub says android 12 is required?
Click to expand...
Click to collapse
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Miustone said:
Sorry for the Issues! Could You try again now? I have removed the Vendor stuff for now...
Can You also try to use them seperated? I do actually not own the 1 III so i can't test Myself. Feel also free to collab. with Me on GitHub
Click to expand...
Click to collapse
Hi what do you mean by use them separated? Like install/activate the base module, reboot, then do the system module?
Yep, it could be one of them or both which causes the Bootloops. I updated the Base so it might be that... The System should cause less Problems at the end... @tonysunshine
I also got a bootloop after installing the zips. I tried following the instructions on your github and was able to do the device simulation with the props config module, but can't follow the next step "Download and extract the NgaResources.apk to /MARS_SOM_SYSTEM/system/product/app/NgaResources" as there's no NgaResources.apk file anywhere on the github that I can find. Could it be this missing file that's causing issues?
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
akkk44 said:
Xperia 1 III here.
I followed the steps on github and everything went smoothly even after I flashed the MARS_SOM_BASE zip. However, after flashing the MARS_SOM_SYSTEM , I stuck in a bootloop. I have downloaded the MARS_Product_Overlay apk and place it.
I am willing to help if you need further info.
Click to expand...
Click to collapse
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Miustone said:
Wow, I'm glad the BASE zip worked so far. You are getting a lot out of it. But I'm pretty sure there will be bugs around somewhere...
And thanks a ton for Your Post! I'm on the go but if You want to test around...
Move folders out of the _SYSTEM /system Folder like /product, /vendor and so on. Start with removing all except for one Folder and try if it boots up. If You can tell Me which folder causes issues or even which files will I handle it on GitHub for You.
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
akkk44 said:
I wanna help but recovering from bootloop is a real pain in my a**. I somehow managed to disable all magisk moudules and get out of boot loop but I am not sure if I can do it again. The only two methods I knew about getting out od a bootloop is removing modules with TWRP but currently 1 iii doesn't have one, the other method is using the adb command but I am not sure how to send adb commands to the phone while it stucked in a bootloop.
Any ideas?
Click to expand...
Click to collapse
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Miustone said:
You can simply hold Volume down while booting to get into "Recovery Mode". It disables all Modules and most Apps. You can reboot from that into the normal state again... Should mention that somewhere I think... (It's a Magisk Feature too)
Edit: Does not work with USB Connected! Hold Volume down after You see the Bootloader Unlocked Message. Keep holding until You are in Android
Edit 2: Think Ill make Video guides too for some needs if there is enough Interest...
Click to expand...
Click to collapse
Understood! I will test the module out sometime……
akkk44 said:
Understood! I will test the module out sometime……
Click to expand...
Click to collapse
Great! Thanks in advance!
Miustone said:
About the Files @tardis_42 . You can find the Files on My Website / Google Drive. The link is in the Readme on GitHub
Click to expand...
Click to collapse
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
tardis_42 said:
I tried there, but the file mentioned on the github readme (NgaResources.apk) isn't there - just these two:
View attachment 5445471
Click to expand...
Click to collapse
Thanks for pointing out. I'm uploading the latest Version to this Google Drive Directory rn! Sorry for the Trouble...
Updated the Thread, MARS_SOMs and GitHub<3
HUGE UPDATES INCOMING!
MARS will be available over GitHub Releases so You can easily Download ready-to-use Zips of MARS for Magisk. Also included are now OTA Updates for MARS over Magisk and the focus Changed to GSIs again. Use PHH AOSP 12 or PIXEL EXPIERENCE 12 by Ponces to unleash Your Xperias
tbalden's
CleanSlate kernel
for Google Pixel 6
The User Experience Kernel leaning towards Stock Stability plus UX features.
Rock stable stock approach, performance smooth and issue free
"No-Root is a State of Mind"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No root elevation (magisk) needed for all functions and preference switches through CS Config App
Release Calendar
Version 1.3.1 - 15 of Jan 2021
Version 1.1.0 - 20 of Nov 2021
Should work on official ROM bases Nov 2021 sec level.
Features:
- Sweep to Sleep gestures - highly customizable
- DoubleTap & LongTap & SwipeUp on corner area gestures - new way to pull down android Notification Area or screen off
- Sweep/Tap gesture to force close foreground app - DETAILS HERE
- Battery Saver cut back max CPU freqs, 3 levels + touch boost limiter options
- Flashlight Notification/Call blinking (see video below)
- Vibrating Notification Reminder (DETAILS)
- Notification In-Pocket Booster boost notifications vibrations while phone is in pocket
- Vibration Booster boost haptic feedback strength (closer to Pixel4/Pixel3 levels)
- K.AdAway adblocking built-in kernel only, All browsers, Apps web-ads, except YouTube / streaming / Facebook ads
- SafetyNet pass - BASIC passes Basic, without Magisk/Rooting. CTS won't pass.
- ThinLTO + CFI security hardened Read: https://source.android.com/devices/tech/debug/cfi
- Kernel Log / Crash dump to internal storage/sdcard - no root/magisk needed, from Companion App use Kernel Log button
- CleanSlate Companion / Config - rootless app to configure
Facts:
- no root required, use /sdcard/Android/data/org.cleanslate.csconfig/cache/uci_user.cfg file to configure 99% of the features without rooting. If you need tweak apps (e.g. EXKM / FK) you'll need rooting!
- built on top of kernel sources released by Google
- built with standard toolchain for stability and efficiency
- built with Control Flow Integrity sec hardening from Android S versions onwards
- kept stable, no tweakings, just features
- stable and reliable, keeping close to stock except addition of Usability features
Feature demo
Sweep2Sleep, DoubleTap notif pull down
--
Foreground App Kill gesture
Requirements
- Unlocked Pixel 6, stock or with magisk root
- From Android S, vbmeta verification must be disabled. ONLY if you use Magisk Manager canary latest (to patch boot image with Magisk) you can skip vbmeta verification disabling! If using the boot image provided in the zip without Magisk, you MUST disable verification! Download the stock full firmware for you phone, extract Vbmeta.img and do:
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
--- In Android S, you might need to do a factory reset when disabling Verity after the system booted before with vbmeta enabled! If it doesn't boot with corruption problem, you need to do a factory reset with 'fastboot -w'
--- When updating with next OTA on Android S, I recommend to 'adb sideload ota.zip' and then BEFORE booting, go to Bootloader and with latest Vbmeta.img, make sure to switch off verity again with fastboot flashing vbmeta again, and boot only after that. That way factory reset won't be necessary it seems by experience so far.
- BACKUP: make sure you have a stock image downloaded (boot, dtbo, vendor dlkm img) from Google (https://developers.google.com/android/images) before installing this!
Installation Guide
Firstly install CleanSlate configuration and CleanSlate companion BETA program apps on your phone (both found down below in Download section). Set them up initially.
- When installing Premium version from Play Store, you should join the Beta program for both apps, and install the beta version! Otherwise features won't work.
- Non-rooted method: 0. download the installation zip, Unzip it to your PC.
Code:
1. reboot to bootloader:
$ adb reboot-bootloader
2. Flash boot image and stock dtbo img:
$ fastboot flash boot cleanslate-raven-boot-xxxxxx.yyy--ZZZ.img
$ fastboot flash dtbo stock-dtbo-boot-xxxxxx.yyy.img
3. if everything went fine, reboot to FastbootD and flash vendor_dlkm modules image:
$ fastboot reboot fastboot
$ fastboot flash vendor_dlkm cleanslate-raven-vendor_dlkm-xxxxxx.yyy--ZZZ.img
4. reboot (fastboot reboot), enjoy
- Rooted method: do the same as above, but before flashing boot, root it on the phone from Magisk Manager
Known bugs
- None, please tell
- please disable magisk modules before reporting issues, and please provide logs if possible
- if it cannot boot at all after flash because of signature verification, read vbmeta requirements (Android S)
Download
Android S
Latest updates here in one common thread: https://forum.xda-developers.com/t/...-0-s2s-adblock-vib-batterysvr-mar-26.4364671/
Non rooted, Android S images (redfin)
Pixel6/6pro Images zip (DO NOT FLASH AS ZIP) for Android12 (2022.01.05)
CS 1.3.1: https://www.androidfilehost.com/?fid=17825722713688269355
Pixel6/6pro Images zip (DO NOT FLASH AS ZIP) for Android12 (2021.08.17)
CS 1.1.0: https://www.androidfilehost.com/?fid=7161016148664842834
Config Applications
Companion App 3.3.x-- Donation premium on PlayStore
--- MUST Use BETA program for this phone:
https://play.google.com/store/apps/details?id=org.cleanslate.csservice
Configuration App 3.2.x -- Donation premium on playstore
--- MUST Use BETA program for this phone:
- additional features in premium app: App Themes, Profiles, Profile Switch QuickTiles
https://play.google.com/store/apps/details?id=org.cleanslate.csconfig
Companion App 3.3.4 -- Normal free download:
https://www.androidfilehost.com/?fid=17825722713688265361
Configuration App 3.2.3 -- Normal free download:
https://www.androidfilehost.com/?fid=17825722713688265360
Donation:
If you appreciate this, don't forget to hit the Like button, or consider to Donate. Donations here
Thank you!
Donators Hall of Fame
Much appreciation and many thanks go to...
@velimirchek
@MarcoG:
@guidogsbn
@The Great Dane
@Whiskey103
@purple patch
@panosmdma
@sttw1fa
@jelive
@beartiger
@st_voss
@bigruss
@deagleone
@DroidIt!
@8bitbang
@Will972
@smallKING81
@mick_soul
@p50kombi
@K4Y3
@ dieter
@michaelbsheldon
@dioooi
@ali nz
@bstiti
@Oddvin94
@norgan
@lol8888
@twinnfamous
@cameljockey1
@Cryptycat7
@Pasqui1978
@4ntagonist
@turbo jjjang
@munkyvirus
@knopie
Src: https://github.com/tbalden/android_kernel_gs_raviole
GitHub - tbalden/google-modules-sec_touch
Contribute to tbalden/google-modules-sec_touch development by creating an account on GitHub.
github.com
GitHub - tbalden/google-modules-amplifiers
Contribute to tbalden/google-modules-amplifiers development by creating an account on GitHub.
github.com
GitHub - tbalden/google-modules-lwis
Contribute to tbalden/google-modules-lwis development by creating an account on GitHub.
github.com
Special thanks
To @Freak07 for all his work on XDA and help
To @flar2 for his original works
To @Captain_Throwback
Sharing policy:
As this is all GPL licensed kernel source, you can use it in your code, but don't forget about proper credit.
Whoop @tbalden is in the house!
My goto kernel in the HTC days.
back up first, right? otherwise all data will be gone?
Thanks. Nice to see cleanslate here. Should Gpay work unrooted? I cant add a card unrooted... anybody able to use Gpay unrooted on cleanslate?
Donric13 said:
Thanks. Nice to see cleanslate here. Should Gpay work unrooted? I cant add a card unrooted... anybody able to use Gpay unrooted on cleanslate?
Click to expand...
Click to collapse
No, the safetynet check fails CTS profile unfortunately. No longer possible to pass with custom kernel only. Possibly kdragons module could help, but it needs root indeed
Can I install Clean Slate over ProtonAOSP?
flyl0 said:
Can I install Clean Slate over ProtonAOSP?
Click to expand...
Click to collapse
Yep, I did that.
I paid for the beta configuration app but I got this message.. how to make it away?
trai_th said:
I paid for the beta configuration app but I got this message.. how to make it away?View attachment 5472011
Click to expand...
Click to collapse
Hmm, sorry for the inconveniences, this is an issue with the app. Please for now set a smaller font in system display settings, so that the message fits and then you'll get the dismiss button visible.
Will fix it a bit later, thanks for reporting
tbalden said:
Hmm, sorry for the inconveniences, this is an issue with the app. Please for now set a smaller font in system display settings, so that the message fits and then you'll get the dismiss button visible.
Will fix it a bit later, thanks for reporting
Click to expand...
Click to collapse
Thank you!
oh, it's gone after I set a smaller font!
trai_th said:
Yep, I did that.
Click to expand...
Click to collapse
Thank you! I can comfirm it works
trai_th said:
oh, it's gone after I set a smaller font!View attachment 5472017
Click to expand...
Click to collapse
Ok, it's supposedly won't come back a second time then.
Update for cleanslate companion app, 3.3.3
- fix issue with P6 (oriole) detection, causing loss of setting for Proximity sensor on/off, and that caused 60fps
Download: https://www.androidfilehost.com/?fid=7161016148664854061
Update rolling out also to play store as soon as google approved it.
- Update Android SP1A A12 - 1.2.2 - Android S stable - December
- December sec update - google sources
- adblock hosts file updated
CleanSlate S 1.2.2 Downloads:
Android S images zip (sp1a 2021-12-05)
Pixel6/pro (not flashable, contains images) CS 1.2.2: https://www.androidfilehost.com/?fid=17825722713688250034
vbmeta inside the zip of SP1A.016 to deactivate verity checks on the custom boot image and most probably to do factory reset, DO IT BEFORE FLASHING THE KERNEL, or it won't boot
You can try to deactivate the vbmeta check before the first booting up right after sideloading the OTA , maybe that will let you boot without factory reset after vbmeta verify disabling.
Deactivate, you might need to factory reset if you don't follow the OTA-update/disable-before-first-boot procedure (fastboot -w for factory reset)
fastboot flash --disable-verity --disable-verification vbmeta stock-vbmeta-211205.016.img
How to re-activate if you need later?
fastboot flash vbmeta stock-vbmeta-211205.016.img
Read first post in thread for installation details.
trai_th said:
Yep, I did that.
Click to expand...
Click to collapse
Are you rooted or not? If not does it pass Safetynet checks?
bobby janow said:
Are you rooted or not? If not does it pass Safetynet checks?
Click to expand...
Click to collapse
my P6 is rooted and passed SafetyNet
bobby janow said:
Are you rooted or not? If not does it pass Safetynet checks?
Click to expand...
Click to collapse
trai_th said:
my P6 is rooted and passed SafetyNet
Click to expand...
Click to collapse
Indeed, currently I think the only way to pass on an unlocked p6 is to use kdragons module. I've updated the first post to reflect that clearer
sorry long time no touching stupid question. Unlocked requirement here means unlocked bootloader yes? How to check if my phone is unlocked or not?
aleck0112 said:
sorry long time no touching stupid question. Unlocked requirement here means unlocked bootloader yes? How to check if my phone is unlocked or not?
Click to expand...
Click to collapse
Well, if you bought it second hand, easy way, if you restart your phone, on unlocked bootloader, it will give you a long yellow text for a few seconds, telling you that it's unlocked and unsecure.