Develop Bugs

[KERNEL] Stock Kernel + SafetyNet Patch

Stock Pixel 2 XL/Pixel 2 Kernel + SafetyNet Patch
Current version: android-9.0.0_r0.112
Suitable for build(s): All August 2019 builds
Suitable for devices(s): Pixel 2 XL (taimen) | Pixel 2 (walleye)
I compiled the stock kernel for the Pixel 2 XL/Pixel 2 and applied the SafetyNet patch by sultanxda. The kernel name says wahoo, which is the unified kernel that works on both taimen (Pixel 2 XL) and walleye (Pixel 2) devices.
Use case for this kernel:
- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay and Netflix.
- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.
- This kernel is only for the builds listed above!!!! This will not work on any prior build.
- All stock features will work with this kernel (since it's just the stock kernel + patch).
- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the stock kernel, except with the addition of the SafetyNet patch.
- This will not prevent SafetyNet from tripping for other reasons, like rooting.
- This will not remove the "device corrupted" warning when the phone is turned on or rebooted.
Installation:
- Be prepared with backups or the factory image from Google in case you do something wrong
- Extract kernel from zip file
- Test with command: fastboot boot <filename>
- Flash with command: fastboot flash kernel <filename>
**WARNING**
If flashing this kernel for whatever reason ruins your device, I am not accountable. Use this at your own risk!
The current version will always be attached to this post (check the Downloads tab). Older versions can be found HERE.
XDA:DevDB Information
Stock Kernel + SafetyNet Patch, Kernel for the Google Pixel 2
Contributors
iissmart
Kernel Special Features:
Version Information
Status: Stable
Created 2017-11-18
Last Updated 2017-12-11

I want to apply this patch to my Huawei P9, but obviously can't use this one kernel. How would I go about applying the patch to my kernel? What programs / apps are needed?

Updated OP with the 8.1.0 kernel for December 2017 builds.

Hey anyone else having issues with windows defender seeing this as a virus when trying to download?

iissmart said:
Updated OP with the 8.1.0 kernel for December 2017 builds.
Click to expand...
Click to collapse
Works like a champ! Thanks so much!

Updated OP with the latest kernel for January 2018 builds.

Jan Security Patch
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?

rweddy1 said:
Hello I have been unable to update to the January, my pixel shows "Couldn't update - installation problem"
Could the safetynet patch be be causing the issue?
Where would I get the stock kernel for 8.1.0 December 5th security patch level?
Click to expand...
Click to collapse
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.

iissmart said:
What I do is revert back to the stock boot image (found here), reboot and let the phone install the OTA, then flash the new patched kernel.
I don't think it's possible to have the phone install an OTA successfully with a custom kernel, unfortunately.
Click to expand...
Click to collapse
I didn't even think about that, thank you very much! I am all good now.

Can the kernel zip be flashed directly from twrp on the phone rather than extracting and using fastboot?

I've updated OP with the mid-month update to r0.18.

Anyone know if ViperAudio works with this ROM?

xD3CrypTionz said:
Anyone know if ViperAudio works with this ROM?
Click to expand...
Click to collapse
It's a kernel. Try viper and let us all know.

----REDACTED----

xD3CrypTionz said:
Did not try stock kernel but I have elementalx kernel with the Viper4Android Magisk module v2.9.
Click to expand...
Click to collapse
I haven't tried no. I'm happy with the sound on my phone.

Updated OP for February 2018.

Updated OP for March 2018.

Anyone else seeing issues with fast charging with Patched Kernel?
I have a run a few test & looks like patched kernel is not charging as fast as sock.
See below:
Patched Kernel: Battery at 82% when plugged in
After 10 min @ 86% After 20 min @ 89%
Stock Kernel: Battery at 82% when plugged in
After 10 min @ 90% After 20 min @96%
Again testing was done with same charger, same apps running, etc.

Updated OP for April 2018. I believe there is a confirmed issue with fast charging in the previous kernels - please test with this one and let me know if it still exists.

Updated OP for May 2018.

[UNOFFICIAL] LineageOS 14.1 | Celox [July 9, 2022]

BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.
BACKUP YOUR DATA AND OLD ROM BEFORE trying this rom.
I'm simply offering this rom for those who cannot build it themselves.
What works.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
FAQ.
Q1. How did you build this? Where can I find the source code and kernel source code?
A1. This is a continuation of bryan2894's 14.1 code found on github. His last rom was built Nov 19, 2017. His github repo shows the last changes on Nov 24, 2017. So you will get the following changes as seen at
Commits · thewizrd/android_kernel_samsung_msm8660-common
Contribute to thewizrd/android_kernel_samsung_msm8660-common development by creating an account on GitHub.
github.com
You will also get whatever LineageOS 14.1 changed in the last 3.25 years including the latest March 2021 security patches.
Thanks to @bryan2894 for his repos so I can build this rom. I have added no value, changes or edits to this rom other than compiling it for 2021.
Q2. Can you fix this GSM/LTE/voice/call/text bug?
A2. No. I recently bought the SGH-I727 (code named skyrocket), but I have no SIM card and I do not plan to get one. So I cannot fix any GSM/LTE/voice/call/text bugs that exist in this rom. Any questions regarding lost, dropped, poor quality calls, low or high volume, poor sound quality, bad microphone, can't recognize sim, etc will go completely unanswered. Do not report these bugs as they will not be fixed by me. If you want to fix them, you can look at the code repositories in post #1.
In addition, there are proprietary voice/radio Samsung blobs where there is no source code so changes are virtually impossible to make.
Q3. What version of TWRP should I use?
A3. You must follow the instructions in post #2 as written by bryan2894 exactly. I followed them and was able to flash my build successfully. If you can't flash the rom, it's likely you are not following the instructions provided. Do not ask TWRP questions in this thread, they will go unanswered.
Q4. How long does the first boot take?
A4. Booting the initial LineageOS 14.1 takes about 7.5 to 8 minutes. Be patient. After it boots, let it sit untouched for 5 minutes and then reboot the phone again. After it boots, let it sit untouched for 5 minutes again before proceeding. This will let the phone do all its stuff and get itself ready.
Q5. Does it run gapps?
A5. This phone was released in Nov 2011 so it's almost 10 years old. It only has 1GB DRAM so I would suggest that you DO NOT install gapps for best performance. There are many alternatives to gapps including Aurora Store and/or installing apks directly onto the phone. Similarly, if you watch youtube videos, I suggest newpipe which is an open source viewer and can skip ads. I use the Brave browser because it has an adblocker and anti tracking features and it works well with this 10 year old phone.
Obviously, it's going to be slower than a new phone, but it's useable as a second phone or some young person's first phone.
I use all the software below.
Aurora Store | F-Droid - Free and Open Source Android App Repository
A Google Playstore Client
f-droid.org
Releases · TeamNewPipe/NewPipe
A libre lightweight streaming front-end for Android. - TeamNewPipe/NewPipe
github.com
Secure, Fast, & Private Web Browser with Adblocker | Brave Browser
The Brave browser is a fast, private and secure web browser for PC, Mac and mobile. Download now to enjoy a faster ad-free browsing experience that saves data and battery life by blocking tracking software.
brave.com
If you must install gapps, choose pico as it's the smallest one.
Q6. Will there be monthly security patches?
A6. Yes as long as I have high speed Internet, I will try to release the rom monthly to incorporate the security patches around mid month (10th to 20th). At some point, LineageOS will discontinue back porting security patches to the 14.1 code and that's when I will stop releasing roms. Google does not provide security patches for Android 7.1 anymore (aka LineageOS 14.1).
Q7. Will there be a 15.1, 16.0, 17.1 or 18.1 release?
A7. I compiled 15.1 and while it compiled without errors, it does not boot. I get no boot animation and there is no adb output which makes debugging very difficult. I suspect a kernel problem. If someone can assist, maybe a team of people can get 15.1 running?
Q8. Can you provide step by step instructions?
A8. You can do your own research on how to install a rom and you must read bryan2894's TWRP post #2. There's lots of written FAQ or videos that show you how. In addition, I don't run Windows so I cannot answer any questions regarding drivers, odin, etc. Questions regarding how to install roms, TWRP and Windows will go unanswered.
Q9. Why is my question not answered?
A9. It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q10. Can I build this rom myself?
A10. Yes, I have provided the roomservice.xml file that I used to build the rom. With it, you can follow any LineageOS build guide/template like
Build for chagallwifi | LineageOS Wiki
wiki.lineageos.org
That's how I built my first rom.
If you are running a newer version of Linux, you may need this additional command to compile the rom.
Code:
export LC_ALL=C
For the June 2021 security patch, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Q11. Does this rom run on Hercules?
A11. I have no idea. I only have SGH-I727 and that's what I tested it on. Celox is supposed to be the unification of Hercules and skyrocket, but I can't verify if it runs on Hercules. Having said that, member squircular in post #4 says it works on his/her Hercules device. There's no guarantee that with each monthly security update/patch that this will be true going forward.
Q12. I don't like this rom, can you help me revert back to stock or my old rom?
A12. No. If you want to try this rom, you must backup your data and know how to revert back yourself. Questions of this nature will go unanswered.
Q13. I bricked my phone trying to install this rom. Can you help me?
A13. You assume all responsibilty for trying this rom including a possibly bricked device, lost data, security vulnerabilities, etc. If you are not comfortable flashing roms and don't know how to revert back to stock or older rom, do not install this rom.
Q14. Okay, I accept all the risks and know what I'm getting into, now where can I download this rom?
A14. You can get it at
retiredtab - Browse /SGH-I727/14.1 at SourceForge.net
sourceforge.net

NOTE OS will show June 5th, 2021 security patches due to hold up of
https://review.lineageos.org/c/LineageOS/android_build/+/313397
Release notes for July 9, 2022
1. UNOFFICIAL July 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-07
2. Whatever LineageOS changed since June 5th security patches (about 2,100 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for June 10, 2022
1. UNOFFICIAL March, April, May and June 5th, 2022 security patches as per
https://review.lineageos.org/q/topic:n-asb-2022-03
https://review.lineageos.org/q/topic:n-asb-2022-04
https://review.lineageos.org/q/topic:n-asb-2022-05
https://review.lineageos.org/q/topic:n-asb-2022-06
2. Whatever LineageOS changed since Feb 5th security patches (about 2,000 files had to be recompiled).
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Feb 24, 2022
1. UNOFFICIAL Feb 5th security patches as per ttps://review.lineageos.org/q/topic:n-asb-2022-02
2. Whatever LineageOS changed since Jan 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Jan 28, 2022
1. Jan 5th security patches as per https://review.lineageos.org/q/topic:n-asb-2022-01
2. Whatever LineageOS changed since Dec 5th security patches.
3. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Dec 8, 2021
1. Nov 5th and Dec 5th, 2021 security patches as per https://review.lineageos.org/q/topic:n-asb-2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12 (about 2,100 files had to be recompiled).
2. A reboot after flashing the new build will take about 6 to 10 minutes. Be patient.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:eek:pen OR status:merged)https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:eek:pen OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(statuspen OR status:merged)
2. A reboot after flashing the new build will take about 6 minutes. Be patient.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.
Release notes for March 8, 2021
1. Initial build for Celox.
2. March 5, 2021 security patches
3. Built from bryan2894 repos with no changes or edits.
4. Please be patient on first bootup. It can take up to 8 minutes. If you installed gapps, then it will take even longer.

Reserved

I can verify that this ROM works on Hercules (SGH-T989D). Thanks very much for your effort.

squircular said:
I can verify that this ROM works on Hercules (SGH-T989D).
Click to expand...
Click to collapse
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?

retiredtab said:
Thanks for information. Does GPS work on hercules? If yes, how long does it take to get a lock?
Click to expand...
Click to collapse
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start). Both of these measurements were taken inside near a window so it might be faster outside.

squircular said:
Yes, GPS works. It took about 2 minutes to get the first fix (cold start) and about 15 seconds to get subsequent fixes (warm start).
Click to expand...
Click to collapse
Thanks for the feedback. I appreciate it.
Since I bought my phone used, I'm not sure if my GPS is working 100% due to hardware. It shows the satellites, but never gets a fix. If it does work, it takes about 10 minutes to get a fix. It's completely useless for a car GPS.
There are some error messages in the adb logcat which might be related to why I can't get a fix, but I will have to investigate.

I'm going to give this a try - this will be my first modded phone and so I'm taking it very slow. I've got a Rogers Samsung Galaxy S II Skyrocket SGH-I727R which I'm ok with making a mistake on. I don't want Gapps. I've currently got TWRP 3.1.1 and I'm reading through everything multiple times.
My current task is to do my best to understand bryan2894's notes on repartitioning.

Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.

JMSchneider said:
Hello retiredtab (or anyone else),
I just want to clarify one little thing. In step 4 of the ROM Installation Instructions as follows:
4. In TWRP, go to Wipe -> Advanced Wipe -> check Internal Storage -> press on "Repair or Change File System" -> press on "Change File System" -> press on "EXT4", and then swipe to start formatting the internal SD card. This can take up to a minute.
As can be seen by the picture of my screen, there is no partition called 'Internal Storage'. Instead I'm wondering if it should be 'SDCard'.
Is this correct?
Many thanks for anyone who can confirm this.
Click to expand...
Click to collapse
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.

retiredtab said:
I think your assumption is correct. I followed the instructions back in February 2021, but honestly can't remember if I ran into the same thing or not with the naming.
Click to expand...
Click to collapse
Thank you for the reply retiredtab - your input is greatly appreciated!

I think I found an article on TWRP that explains the partition name change.

Because the 'Internal Storage' seems to have changed spots (as indicated in the last post), I came up with a workaround for a problem that I encountered.
Initially, I was using the twrp-3.0.0-0-skyrocket.tar.md5 and reasoned it would be the "latest OFFICIAL TWRP" file for the ROM Installation instructions but in step #9 I ran into a problem - a red-highlighted section of the log read "Updater process ended with ERROR: 7". I later discovered this has something to do with version compatibility mismatching. So I decided to regress to the older Official TWRP (v2.8.6-0) recovery and go at the whole process with the exact files in the links. Then, when I went to flash the ROM I had no problems.

bryan2894 and others did all the initial work on TWRP and building this rom. I'm only updating his work + others so I don't know why specific versions of TWRP are required. All I know is that I followed his instructions exactly so that I could build a 2021 rom. As I stated, I'm adding NO VALUE other than compiling a 2021 version.
Once the 14.1 April security patches get merged in LineageOS, I will compile a new version, test it and then share with others who are interested. It looks like there are 5 patches for April as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
A number of people says it compiles, builds and boots with no problems, but I prefer to wait until it's officially merged before I start the compile process.

New build called lineage-14.1-20210415-UNOFFICIAL-celox.zip (had to try 3 or 4 times before upload succeeded).
Release notes for April 15, 2021
1. April 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307154
2. A reboot after flashing the April build will take about 6 minutes. Be patient.

The May security patches still aren't merged yet into LineageOS as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
It's waiting approval since May 6. There are 3 CVEs for May.
At this rate, I'll probably skip making the May security patches and wait for June 5th as it's May 26 as I write this.

The May 5th security patches finally got merged today, June 7, as per
https://review.lineageos.org/c/LineageOS/android_build/+/309293
However, seeing how the June 5th patches should be announced shortly on LineageOS, I will wait until those are announced and then make a June build. No sense making a May build, testing and uploading it if June patches will be out in a few days.

New build called lineage-14.1-20210609-UNOFFICIAL-celox.zip.
Release notes for June 9, 2021
1. May 5 + June 5, 2021 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309293 and https://review.lineageos.org/q/topic:"n-asb-2021-06"+(statuspen OR status:merged)
2. A reboot after flashing the June build will take about 6 minutes. Be patient.
3. For builders, there were problems building with 4GB with Jack server which worked before. I had to increase to 6GB using
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx6G"

New build called lineage-14.1-20210709-UNOFFICIAL-celox.zip
Release notes for July 9, 2021
1. July 5, 2021 security patches as per https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
2. A reboot after flashing the July build will take about 6 minutes. Be patient.

New build called lineage-14.1-20211011-UNOFFICIAL-celox.zip
I have not forgotten about this device, but there's a holdup with the security monthly patches starting with the July 5 patch not being merged due to a problem as per https://review.lineageos.org/c/LineageOS/android_build/+/313397
However, the August patches are officially merged while the September and October ones are pending approval. Rather than wait any longer, I decided to merge September and October security patches into this build.
So while the OS may report that it's on the June 5th security patch, that not true in this case. It has all the October 5th 2021 patches included.
Release notes for Oct 11, 2021
1. July 5 + August + September + October, 2021 security patches as per
https://review.lineageos.org/q/topic:"n-asb-2021-07"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-08"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-09"+(status:open OR status:merged)
https://review.lineageos.org/q/topic:"n-asb-2021-10"+(status:open OR status:merged)
2. A reboot after flashing the October build will take about 6 minutes. Be patient.

[STOCK][HD1907][OnePlus7TTMO][Android 10-12][OTA] 10.0.13.HD63CB to 11.0.1.1.HD63CB to 11.0.1.11.HD63CB to 12

Android 11
10.0.10.HD63CB to 11.0.1.5.HD63CB
url: , payload: (size: 2763742131, metadata_size: 163455, metadata signature: , hash: B75BB0090A5EDA20DFC2ADD3A39F1609782F440C6916DD95FEBB3EFF07785C89
SHA1 597E476A4998CB26B6A61B6D57A9677EBC1EEFFE
February 2021 Security update
10.0.13.HD63CB to 11.0.1.1.HD63CB:
url: , payload: (size: 2751257860, metadata_size: 162370, metadata signature: , hash: C1603970CAAF4869F7BD2FBEF177C377A18984D40947B7F96F3B67D09D16744E)
Size 2.75GB SHA1 176630595d901676a111f951d7bff5e0aa6a6404
April 2021 Security update
11.0.1.1.HD63CB to 11.0.1.2.HD63CB
url: , payload: (size: 325611615, metadata_size: 594919, metadata signature: , hash: 49353DE7B9F9831148C78FC2F38EEC33CEB43126607A0ADF2EAE32A2BC006BBF)
Size 326MB SHA1 9e9f6e647af70b7be8f3f05580ffc320af603d33
June 2021 Security update
11.0.1.2.HD63CB to 11.0.1.3.HD63CB
url: , payload: (size: 214605343, metadata_size: 588720, metadata signature: , hash: 6FDBC3037553A76AF6AB0401558913A2F4D8897E0D83C10948459F5BE00EB741)
SHA1 8a8a8689be965d2cee98bc9b89606a156eef478e
August 2021 Security update
11.0.1.3.HD63CB to 11.0.1.4.HD63CB
url: , payload: (size: 106363136, metadata_size: 441012, metadata signature: , hash:
6143AA11441BE6A9DB246BDB370872B8879B560A52F94289225448E01E158B76)
SHA1 42622490acb227b2af72a2ed779664902cbe8f2d
October 2021 Security update
11.0.1.4.HD63CB to 11.0.1.5.HD63CB
url: , payload: (size: 97763397, metadata_size: 531922, metadata signature: , hash: 20C0BC7D9CBC92117368E8DBADEE9A7E251E04B67337A9697F36FFCC9F86C46D
SHA1 5DFD8A279B1205179EA5A2F477FE94D8BA492F4C
December 2021 Security update
11.0.1.5.HD63CB to 11.0.1.6.HD63CB
url: , payload: (size: 82469170, metadata_size: 368639, metadata signature: , hash: F47B9735E6BB0ACF9CFD9D62EA8558B07FDBAB6830D2A7FF43FF63A324CF17CC
SHA1 11e77affc3412357689b0ac1a57af0000748c874
February 2022 Security update
11.0.1.6.HD63CB to 11.0.1.7.HD63CB
url: , payload: (size: 93163747, metadata_size: 439227, metadata signature: , hash: F113AFFB50E86B37DF675D5689F55ECCA7131C9ABA597550E412E0AC6D502A66
SHA1 ddb3c95704b64d9573c07d3a8a1952819fd69dd8
April 2022 Security update
11.0.1.7.HD63CB to 11.0.1.8.HD63CB
url: , payload: (size: 88754173, metadata_size: 554010, metadata signature: , hash: 5A11D422AC4081B8F50780FDCEF97F74637A9E2B9DEC808DF5AA5890D6C0AE1D
SHA1 38e22c7e6126e13851e9ef1fe8b17246ca358c71
June 2022 Security update
11.0.1.8.HD63CB to 11.0.1.9.HD63CB
url: , payload: (size: 95790995, metadata_size: 446000, metadata signature: , hash: 1770D116AA16FBA1DFF9CC4B8AD68C2ED9565AB17D99C66F4A51032AC5A57501
SHA1 e9bc427e2da0f31f951d2e181ddee328c02b2d31
August 2022 Security update
11.0.1.9.HD63CB to 11.0.1.10.HD63CB
url: , payload: (size: 104399629, metadata_size: 405719, metadata signature: , hash: E84EDFE896F1F39D98F47E133353A15DCAFC967940186AAB5A5B7A43E4511198
SHA1 12140cf105cedd3d780bde75f4d1f4eb39f7a8dc
October 2022 Security update
11.0.1.10.HD63CB to 11.0.1.11.HD63CB
url: , payload: (size: 90963856, metadata_size: 520229, metadata signature: , hash: DCABB33EA9912B046180836F0A996BA9DFCE01D5FD8F7589702CA4F52E0DE02B
SHA1 cbeeb41f8dbe37f6c6dd1325b4d3461514a8c755
December 2022 Security update
11.0.1.11.HD63CB to 12
url: , payload: (size: 4083260429, metadata_size: 157030, metadata signature: , hash: DAF81C20C3101E1A31E883A9B05BD686A037EEDE5AC5EA6FD5384F7F69559E93

If you look at my post history you will se why i'm not happy with this update.
Every version after 10.0.13 is broken. I randomly am unable to place or receive calls. The phone simply states that network is unavailable.
I'm also unable to use my USB-C to USB-C and 3.5mm splitter to charge the phone and use the headphones at the same time. This issue was not present on 10.0.14 but was in 0.15
I was hoping that T-Mobile was holding the update back to fix these issues as I was using the global version before but it looks like it's just as broken on their release. I'm sick of this phone and of OnePlus. I'll be looking for a way to downgrade back to x.13 which has no issues, but now I'll have to wipe my phone. Great.

Delta105RUS said:
If you look at my post history you will se why i'm not happy with this update.
Every version after 10.0.13 is broken. I randomly am unable to place or receive calls. The phone simply states that network is unavailable.
I'm also unable to use my USB-C to USB-C and 3.5mm splitter to charge the phone and use the headphones at the same time. This issue was not present on 10.0.14 but was in 0.15
I was hoping that T-Mobile was holding the update back to fix these issues as I was using the global version before but it looks like it's just as broken on their release. I'm sick of this phone and of OnePlus. I'll be looking for a way to downgrade back to x.13 which has no issues, but now I'll have to wipe my phone. Great.
Click to expand...
Click to collapse
Maybe you have to flash the other images for the calls to work because I was on it and it works for me... I just flashed the europe firmware because all the custom ROMs use the firmware from EU but you need the flash all bat to do that...

[email protected] said:
Maybe you have to flash the other images for the calls to work because I was on it and it works for me... I just flashed the europe firmware because all the custom ROMs use the firmware from EU but you need the flash all bat to do that...
Click to expand...
Click to collapse
I guess I could try the EU version, but it works on the 10.0.13 global. And if custom ROMs are based on EU ROM, then I think the issue would persist, because the issue also happened on 2 custom roms I've tried.

I'm sorry... but that's not the case with me... I'm running a personal build of lineage Os now... and I had to flash EU firmware from T-Mobile firmware because mobile data wouldn't work but it's ok now... I'll upload it to drive later if you want to try it out (Los)

[email protected] said:
I'm sorry... but that's not the case with me... I'm running a personal build of lineage Os now... and I had to flash EU firmware from T-Mobile firmware because mobile data wouldn't work but it's ok now... I'll upload it to drive later if you want to try it out (Los)
Click to expand...
Click to collapse
You built los for op7t? Hallelujah !! Please share

HueyT said:
You built los for op7t? Hallelujah !! Please share
Click to expand...
Click to collapse
It's buggy right now... I have to rebuild it... everything was good but for some reason COD won't open up on the rom but I know what is wrong

Google Drive - Virus scan warning
drive.google.com

But the first one I built is good but the kernel was outdated..28 instead of 31

[email protected] said:
But the first one I built is good but the kernel was outdated..28 instead of 31
Click to expand...
Click to collapse
This deserve its own thread !!!

HueyT said:
This deserve its own thread !!!
Click to expand...
Click to collapse
I'm not going to do that because there's a Dev that is going to be getting the phone and doing Official Los so... I'll leave that up to him.

Luk's builds r unofficial also

HueyT said:
Luk's builds r unofficial also
Click to expand...
Click to collapse
Well I'm building something now... when it finishes I'll give you the link

HueyT said:
This deserve its own thread !!!
Click to expand...
Click to collapse
[email protected] said:
I'm not going to do that because there's a Dev that is going to be getting the phone and doing Official Los so... I'll leave that up to him.
Click to expand...
Click to collapse
this thread topic is the ota lets keep on topic please.

[email protected] said:
Well I'm building something now... when it finishes I'll give you the link
Click to expand...
Click to collapse
This works awesome. Thanks

cars1189 said:
this thread topic is the ota lets keep on topic please.
Click to expand...
Click to collapse
Oxygen updater app can give access to eu, usa, indian stock roms easily:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com

HueyT said:
Oxygen updater app can give access to eu, usa, indian stock roms easily:
Oxygen Updater - Apps on Google Play
Skip staged rollout queues and update your OnePlus device ASAP!
play.google.com
Click to expand...
Click to collapse
This topic is stock for tmobile otas updater app doesn't apply here.

You're asking for trouble to do partial OTA flashes, especially with locked bootloader--difficult to unbrick

cars1189 said:
This topic is stock for tmobile otas updater app doesn't apply here.
Click to expand...
Click to collapse
Sure it does as it's much safer to do whole rom stock clean flashes

HueyT said:
Sure it does as it's much safer to do whole rom stock clean flashes
Click to expand...
Click to collapse
No Oxygen Updater doesn't work for t-mobile stock. Nothing to do with safe or not the app is irrelevant here.
"
In the same way as OnePlus 6T and 7 Pro sold by T-Mobile, it is not possible to install any updates retrieved from another source than T-Mobile.
Therefore it is not possible to offer updates for this device in the app."
so again please stay on topic.

June patch

Is anyone able to provide a stock boot image for the june patch which has the following name:
OnePlus7TOxygen_14.E.28_OTA_0270-0280_patch_2107182116_ac2d98f93eafd.zip
Decided I wanted to root after doing fine without it for months and now the wifi is busted as I have used the wrong boot image to patch with Magisk......
I am unable to extract the boot.img usind payload dumper as its only a patch file and it doesnt like it....
EDIT: Crisis averted......I managed to find a list of update zips on here......
[OnePlus 7T][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
heres the link if anyone else has a similar issue.....
flashed the latest boot image and all is well.....

[SODP][ROM][AOSP] SonyAOSP 13 [Alpha]

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Official site
Unofficial site
Source Code
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
This is the AOSP ROM for the Sony Xperia XZ2 (akari)
This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.
FAQ:
fastboot & adb
https://developer.sony.com/develop/open-devices/get-started/flash-tool/useful-key-combinations/
https://wiki.lineageos.org/adb_fastboot_guide.html
https://developer.android.com/studio/releases/platform-tools
Stuck at SONY logo? Maybe you need to flash the OEM binary to oem_a and oem_b, while just oem is not enough.
Bugtracker:
SODP Bugtracker -> If you think the problem is in SODP
My Bugtracker -> If you think the problem is in my implementation
Bugreport:
A bugreport needs
Code:
logcat -b all
and a way to reproduce the issue.
A crash of the system requires the content of the /sys/fs/pstore folder as bug report
Be aware that a second reboot erases this folder
A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
To rescue a not responding phone:
VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
@jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
@dhacke for providing a download server
And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
GCAM Camera App:
GCAM Issue
Suggested GCams
Installation with a recovery:
fastboot flash oem _a oem_*.img (Only needed until the device receives mainline support by SODP)
Flash the ROM in a recovery
Reboot into recovery just to make sure you're on the new slot
OpenGapps (Requires TWRP or a custom ROM recovery)
Dual Sim Patcher (Requires TWRP or a custom ROM recovery)
(In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Flash the ROM without a recovery:
Extract the payload.bin from the .zip file
Extract the .img files with the Playload Dumper
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot -w (Wipes your internal storage and the userdata; only if needed)
Now you got the AOSP recovery, to please continue with the normal installation
fastboot flash oem_a oem_*.img (Only needed until the device receives mainline support by SODP)
fastboot flash vendor vendor.img
fastboot flash system system.img

News
26.06.2023
android-13.0.0_r52 (June security patchlevel)
Click to expand...
Click to collapse
26.05.2023
android-13.0.0_r43 (May security patchlevel)
Click to expand...
Click to collapse
Compiling AOSP is working again since LTS kernel 6.1.30
Click to expand...
Click to collapse
12.04.2023
android-13.0.0_r38 (April security patchlevel)
Click to expand...
Click to collapse
04.04.2023
android-13.0.0_r35 (March security patchlevel)
Click to expand...
Click to collapse
Fixed build issue
Click to expand...
Click to collapse
07.10.2022
android-13.0.0_r7 (October security patchlevel)
Click to expand...
Click to collapse
OTA.zip generation is working again
Click to expand...
Click to collapse
08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse
06.09.2022
android-13.0.0_r1 (August security patchlevel)
Click to expand...
Click to collapse

Thanks, @MartinX3! There are no Android 13 SW binaries for the Tama platform in the Sony servers. Should we make use of the ones for Android 12, instead?

casouzaj said:
Thanks, @MartinX3! There are no Android 13 SW binaries for the Tama platform in the Sony servers. Should we make use of the ones for Android 12, instead?
Click to expand...
Click to collapse
You're welcome
As far as I know it's fine to use the A12 binaries for now on the tama devices.
The A13 binaries will come later.

Thanks, @ MartinX3!
How to install Gapps?

I followed the installation instructions, but it ended up in a recovery loop: after some minutes of boot animation, it restarts to the stock recovery. After some attempts with the same results, I'm now back to my previous setup, AwakenOS 2.10. Will wait for it to be updated to A13. Thanks, anyway!

Thanks for the test but without logs it can't get fixed

casouzaj said:
I followed the installation instructions, but it ended up in a recovery loop: after some minutes of boot animation, it restarts to the stock recovery. After some attempts with the same results, I'm now back to my previous setup, AwakenOS 2.10. Will wait for it to be updated to A13. Thanks, anyway!
Click to expand...
Click to collapse
The same here. Bootloop: /

osa355 said:
The same here. Bootloop: /
Click to expand...
Click to collapse
Looogs
pstore from the recovery would be helpful. <3

I wonder if the stock A10 ROM would be required beforehand. In my case, I started from A12.1.

casouzaj said:
I wonder if the stock A10 ROM world be required beforehand. In my case, I started from A12.1.
Click to expand...
Click to collapse
Luckily the stock Voodoo for every new stock rom version only needs to be done once in your device UFS lifetime.
(Of course booting to the desktop after the google assistant to apply every firmware upgrade).
(And it should be done for the right LTE region if you move the country/provider for the best signal strength experience, since the old sony devices had different rom regions for the lte providers)

casouzaj said:
I wonder if the stock A10 ROM world be required beforehand. In my case, I started from A12.1.
Click to expand...
Click to collapse
I installed stock Android 10 and had to restart without the Android animation screen. As I installed directly from Lineage 19.1 it was at least an Android boot screen. I don't have logs because I don't know how to save them: /

MartinX3 said:
Luckily the stock Voodoo for every new stock rom version only needs to be done once in your device UFS lifetime.
(Of course booting to the desktop after the google assistant to apply every firmware upgrade).
(And it should be done for the right LTE region if you move the country/provider for the best signal strength experience, since the old sony devices had different rom regions for the lte providers)
Click to expand...
Click to collapse
sorry to post here but you have the dm closed.can you patch the walkman apk in order to work? see here->https://forum.xda-developers.com/t/...es-a100-nw-a100-series.4324181/#post-87388081

With my own compiled A13: (+ latest TAMA SW for A12)
On startup message: "There's an internal problem with your device. Contact your manufacturer."
For about a minute phone lagging - then working normally.
Camera not working, BT/WIFI working.
Upd: some issues with branch rep sync, compiled old A12...

alexisnik199111 said:
sorry to post here but you have the dm closed.can you patch the walkman apk in order to work? see here->https://forum.xda-developers.com/t/...es-a100-nw-a100-series.4324181/#post-87388081
Click to expand...
Click to collapse
Sorry, but its a pure AOSP ROM for SODP devices.
Hacks could raise the amount of issues.

08.09.2022
android-13.0.0_r4 (September security patchlevel)
Click to expand...
Click to collapse

I have now tried to install the newly released build on a XZ3 in the house. Again, a recovery loop. The difference is that in the XZ3 there is no boot animantion, and it takes a lot longer to boot to recovery. I have attached the recovery.log (zipped) file.

casouzaj said:
I have now tried to install the newly released build on a XZ3 in the house. Again, a recovery loop. The difference is that in the XZ3 there is no boot animantion, and it takes a lot longer to boot to recovery. I have attached the recovery.log (zipped) file.
Click to expand...
Click to collapse
Thank you but was there a pstore like described in the first post?
Sadly the log of the recovery doesn't help, since the recovery works.

MartinX3 said:
Looogs
pstore from the recovery would be helpful. <3
Click to expand...
Click to collapse
Sorry for the noob question, but where to find this pstore?