Develop Bugs

[RECOVERY][UNOFFICIAL][X00R][v3.3.1] TeamWin Recovery Project [12/10/2019]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.3.1-0:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
DOWNLOADS: TWRP-3.3.1-0.img
HOW TO FLASH:
Fastboot Method :
Code:
fastboot flash recovery $RECOVERYNAME
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp.img > Select it & Swipe to Flash
CREDITS:
TeamWin
Team twrpbuilder
Omni Team
XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the Asus Zenfone Max
Contributors
raza231198, Theprofessionals, shaikh lukman
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: 3.3.1.0
Stable Release Date: 2019-10-12
Current Beta Version: 3.2.3
Beta Release Date: 2019-10-12
Created 2019-10-16
Last Updated 2019-10-16

Reserved

THREAD CLOSED on request of OP!

[RECOVERY][OFFICIAL][X00P][SAR][v3.3.1] TeamWin Recovery Project [26/01/2020]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.3.1-0:
Fix selinux issues during formatting - dianlujitao
Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
Add option to uninstall TWRP app from /system - Dees_Troy
Create digest for subpartitions - bigbiff
DOWNLOADS: https://dl.twrp.me/X00P/
HOW TO FLASH:
Fastboot Method :
Code:
fastboot flash recovery $RECOVERYNAME
Code:
fastboot oem reboot-recovery
Boot to OLD TWRP > INSTALL > Select Image > Navigate to twrp.img > Select it & Swipe to Flash
CREDITS:
TeamWin
Team twrpbuilder
Omni Team
XDA:DevDB Information
TeamWin Recovery Project, Tool/Utility for the Asus Zenfone Max
Contributors
raza231198
Source Code: http://github.com/omnirom
Version Information
Status: Stable
Current Stable Version: 3.3.1.0
Stable Release Date: 2019-12-04
Current Beta Version: 3.2.3
Beta Release Date: 2018-12-10
Created 2019-12-03
Last Updated 2020-01-25

New Build is Up
Click Here To Download
Changelogs
• 26/01/2020
Official Now
• 04/12/2019
Fixed Decrytion On Pie
Updated Blobs To Pie
Use ToolBox instead for BusyBox
Enable System-As-Root
• 26/06/2019
Fixed Decryption on Oreo
Enable MTP

Reserved

New Build is Up
Click Here To Download
Changelogs
• 26/01/2020
Official Build Now

THREAD CLOSED on request of OP!

[CLOSED]CRUEL KERNEL S10 V2.3

CRUEL KERNEL S10 V2.3
The development moved to this thread. From V3 kernel supports multiple devices.
Introduction
This kernel is based on BTA8 samsung sources. Only G973F device for now. It is possible to use it on BSKO, BSL4, BTA8 firmware. All sources are open on GitHub.
Continuous integration with GitHub Actions is set up. This means you can customize the kernel from browser and build the version suitable for you without leaving the browser (see сustomization section).
Features
Customizable build with config presets
Only part of samsung security features disabled (DEFEX, Process Authentification, root restrictions)
Switchable SELinux (by default it's locked in "always enforcing" mode in samsung sources)
Built-in in Magisk
Wireguard for VPN
CIFS for SMB
Iptables TTL and HL editing modules for bypassing tethering restrictions
Build commands (configuration presets) used for V2.3 kernel:
Code:
$ ./build mkimg name=CRUEL-V2.3-BTA8 +magisk +nohardening +wireguard +ttl +cifs
$ ./build mkimg name=CRUEL-V2.3-BTA8-CANARY +magisk+canary +nohardening +wireguard +ttl +cifs
Installation Instructions
First of all, TWRP Recovery + multidisabler should be installed in all cases. This is a preliminary step. Backup your existing kernel. You will be able to restore it in TWRP Recovery in case of any problems.
Dowload an *.img file and
With TWRP: Reboot to recovery. Install > Install Image > CruelKernel.img > BOOT.
With Heimdall: Reboot to Dowload mode.
Code:
sudo heimdall flash --BOOT CruelKernel.img
With FK Kernel Manager: Flasher > Manual Flasher.
ChangeLog
V1 is based on BSKO sources and was privately used. You can find V1 by the link.
V2 is based on BTA8 sources. nohardening, nohardening2, cifs configuration presets added.
V2.1 is for internal use only (testing release) +nohardening preset activated by default
V2.2
Canary Magisk updated to 20305 version
MALI_KUTF kernel driver removed (it's required only for kernel developers)
Pin code problem fix (thanks geiti94)
+nohardening (disable samsung protections)
V2.3
Canary Magisk updated to 20306 version
Small fixes for image format
Downloads
CruelKernel-G973F-BTA8-v2.3
CruelKernel-G973F-BTA8-v2.3-CANARY
Sources
How to customize the kernel build
It's possible to customize the kernel and build it from the browser. First of all, create and account on GitHub. Next, fork this repository. Switch to the "Actions" tab and activate GitHub Actions. At this step you've got your own copy of the sources and you can build it with GitHub Actions. You need to open github actions configuration file (.github/workflows/main.yml) and edit it from the browser. For example, to alter the kernel configuration you need to edit lines:
Code:
- name: Kernel Configure
run: |
./build config name=CRUEL-V2-BTA8
+magisk
+ttl
+wireguard
+cifs
You can change the name of the kernel by replacing name=CRUEL-V2-BTA8 with, for example, name=my_own_kernel. You can remove wireguard from the kernel if you don't need it by changing "+" to "-" or by removing the "+wireguard" line and "" on the previous line.
Available configuration presets can be found at kernel/configs folder. Only the *.conf files prefixed with "cruel" are meaningful. For example:
magisk - integrates magisk into the kernel. This allows to have root without booting from recovery. Enabled by default.
magisk+canary - integrates canary magisk into the kernel.
ttl - adds iptables filters for altering ttl values of network packets. This helps to bypass tethering blocking in mobile networks.
wireguard - adds wireguard VPN module to the kernel.
cifs - adds CIFS (SMB) support.
nohardening - removes Samsung kernel self-protection mechanisms. Potentially can increase the kernel performance. You can enable this config if you face rooting or some other kind of restrictions. Other kernels usually use settings from this config by default. It's safe to enable this config, it just makes your system less secure.
nohardening2 - removes Android kernel self-protection mechanisms. Potentially can increase the kernel performance. Don't use it if you don't know what you are doing. Almost completely disables kernel self-protection. Very insecure.
nodebug - remove debugging information from the kernel.
300hz - increases kernel clock rate from 250hz to 300hz. Potentially can decrease response time. Disabled by default, untested.
1000hz - increases kernel clock rate from 250hz to 1000hz. Potentially can decrease response time. Disabled by default, untested.
For example, you can alter default configuration to something like:
Code:
- name: Kernel Configure
run: |
./build config name=CruelCanary
+magisk+canary
+wireguard
+nohardening
After editing the configuration in the browser, save it and commit. Next, you need to switch to the "Actions" tab. At this step you will find that GitHub starts to build the kernel. You need to wait about 25-30 mins while github builds the kernel. If the build is successfully finished, you will find your boot.img in the Artifacts section. Download it, unzip and flash.
To keep your version of the sources in sync with main tree (following updates), please look at this tutorial.
Support
This thread. Feature requests accepted.
Telegram (testing and intermediate releases).
GitHub Pull Requests if you want to contribute.
Credits
Samsung for kernel sources
topjohnwu for Magisk
geiti94 for showing that it's possible to built-in Magisk into the kernel. Initially I experimented with ASIG kernel, but ASIG+Magisk on ASIG firmware just stucks on boot with an SELinux initialization problem. At that time I doubted that built-in Magisk will work.
geiti94 for his help and advices
franciscofranco for FK Kernel Manager
XDA:DevDB Information
CRUEL KERNEL S10 , Kernel for the Samsung Galaxy S10
Contributors
evdenis, evdenis
Source Code: https://github.com/CruelKernel/exynos9820-beyond1lte
Kernel Special Features:
Version Information
Status: No Longer Updated
Current Stable Version: v2.3
Stable Release Date: 2020-02-12
Created 2020-02-10
Last Updated 2020-03-16

Reserved

How to build the kernel locally on your PC
This instruction assumes that you are using Linux. Install: mkbootimg, heimdall (if you want to flash the kernel with it).
Next:
Code:
$ git clone https://github.com/CruelKernel/exynos9820-beyond1lte
$ cd exynos9820-beyond1lte
# List available branches
$ git branch -a | grep remotes | grep cruel | cut -d '/' -f 3
# Switch to the branch you need
$ git checkout samsung-g973f-bta8-cruel
# Install compilers
$ git submodule update --init --recursive
# Compile (install mkbootimg first)
$ ./build mkimg name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening
# You will find your kernel in boot.img file after compilation.
$ ls -lah ./boot.img
# You can automatically flash the kernel with heimdall
# if you connect your phone to the PC and execute:
$ ./build :flash
# Or in a single command (compilation with flashing).
# ./build flash name=CustomCruel +magisk+canary +wireguard +ttl +cifs +nohardening

Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f

gillim74 said:
Boots phone but after entering pin goes to black screen then right back to the pin screen.g973f
Click to expand...
Click to collapse
What ROM are you using? I tested it mostly on samsung BTA8 firmware.

evdenis said:
What ROM are you using? I tested it mostly on samsung BTA8 firmware.
Click to expand...
Click to collapse
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first

gillim74 said:
Ambassadi same firmware but i think i know what it is.i never uodated the bootloader.i will try that first
Click to expand...
Click to collapse
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.

evdenis said:
If your phone was able to boot to pin screen, then I doubt the problem is in bootloader. Could you try V1 kernel https://github.com/CruelKernel/exynos9820-beyond1lte/releases/tag/v1.0
If it will work, then probably V2 will also work with +nohardening option. V1 compiled with this option, V2 without it. I will rebuild V2 then.
Click to expand...
Click to collapse
Same thing with version 1.could it be the twrp im using?

gillim74 said:
Same thing with version 1.could it be the twrp im using?
Click to expand...
Click to collapse
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.

It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.

evdenis said:
No, it's definitely not related to twrp. Well, I don't know what is an exact problem here, but some guys told me they were able to flash the kernel on ambassadi with data wipe or immediately after flashing the rom itself.
Click to expand...
Click to collapse
Data wipe or format data

gillim74 said:
Data wipe or format data
Click to expand...
Click to collapse
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!

hello installation successfully the nikel kernel market for now

evdenis said:
Data wipe should be enough. I will test compatability with Ambassadi today-tomorrow and will provide more detailed feedback. Thanks!
Click to expand...
Click to collapse
Worked with data wipe

evdenis said:
It would be very nice if people will just write if the kernel works or not on their roms. This will be a huge help for me.
Click to expand...
Click to collapse
write me on telegram so i can say you why all get the pin code problem so you can fix it

Does this work with BSL7? Or know of kernel that will. Need my su permission to work

Paulturn84 said:
Does this work with BSL7? Or know of kernel that will. Need my su permission to work
Click to expand...
Click to collapse
Hi, no it will not work on BSL7. This kernel is for S10 (G973F) device. This device has only BSL6 firmware. BSL7 is for other devices. Try to look at nemesis kernel.

Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?

vomad said:
Is it possible to build magisk rooted kernel for pie (9) roms? Or it's only for Q like LOS 17?
Click to expand...
Click to collapse
Download: https://cruelkernel.org/release/special/CruelKernel-G973F-ASJG-v1.1-LOS.img
This version is based on Android 9 (ASJG) sources and should work on ASIG firmwares. I've included some patches from ivanmeler LOS tree specifically for LOS. Features: Magisk v20.3, wireguard, ttl modules and cifs. Not tested

will he s10+ every be supported with this kernel?

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 11 [BETA]

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
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), XZ2C (apollo) and XZ3 (akatsuki)
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:
Sony [*Kim Jong*Un]official OD Chat
https://developer.sony.com/develop/open-devices OEM binaries: @SMDW_downloads Bug Tracker: https://github.com/sonyxperiadev/bug_tracker This group is only for dev stuff. For support: https://t.me/xdadevelopershub
t.me
XDA:DevDB Information
AOSP, ROM for the Xperia XZ2
Contributors
MartinX3, Sony, SonyAOSP
Source Code: https://github.com/sonyxperiadev
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest Stock Firmware
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 11
Beta Release Date: 2020-10-23
Created 2020-10-23
Last Updated 2020-10-23

Download & Installation
Download ROM:
Android File Host
FTP-Server from @dhacke
Download Drivers:
OEM (Tama) binaries
Please use the the OEM build which came before my last release, if you getting problems like a not bootable or crashing device.
GCAM Camera App:
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 --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot -w (Wipes your internal storage and the userdata)
Now you got the AOSP recovery, to please continue with the normal installation

News
09.02.2022
android 12
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [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...
forum.xda-developers.com
Click to expand...
Click to collapse
20.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
19.09.2021
Revoked the r43 buiild because of error
AndroidRuntime: java.lang.IllegalArgumentException: invokeOemRilRequestRaw failed with rc = -2
We need to wait until the following PRs get merged
[TRANSPOWER] [3/4] Convert all makefiles to BluePrint by MarijnS95 · Pull Request #14 · sonyxperiadev/transpower
Depends on #13 Blueprint is easier to read, has less possibilities for complicated configuration (for the better) and is much quicker to parse by the build system. Note that an extra android_librar...
github.com
[TRANSPOWER] [4/4] [WIP/RFC] Make SDK-28 compliant, use HookMediator for qcrild by MarijnS95 · Pull Request #11 · sonyxperiadev/transpower
Depends on #14 Hi @jzoran, This PR attempts to fix a multitude of things related to recent changes on SODP and Android API compatibility. Let me run through them sequentially: Kumano requires qcril...
github.com
Click to expand...
Click to collapse
17.09.2021
android-11.0.0_r43 (September security patchlevel)
OEMv7 support
Click to expand...
Click to collapse
17.08.2021
android-11.0.0_r40 (August security patchlevel)
OEMv6 support (Now our device uses the same camx camera framework like Xperia 1/5 (I / II / III)
Click to expand...
Click to collapse
25.07.2021
android-11.0.0_r39 (July security patchlevel)
Click to expand...
Click to collapse
10.06.2021
android-11.0.0_r38 (June security patchlevel)
OEMv5 support!
Click to expand...
Click to collapse
10.05.2021
android-11.0.0_r36 (May security patchlevel)
Click to expand...
Click to collapse
08.04.2021
android-11.0.0_r34 (April security patchlevel)
OEMv4 support!
Click to expand...
Click to collapse
12.03.2021
android-11.0.0_r32 (March security patchlevel)
Fixed mobile and wifi
Click to expand...
Click to collapse
13.02.2021
android-11.0.0_r29 (February security patchlevel)
Click to expand...
Click to collapse
12.01.2021
android-11.0.0_r27 (January security patchlevel)
Click to expand...
Click to collapse
12.12.2020
android-11.0.0_r18 (December security patchlevel)
Click to expand...
Click to collapse
14.11.2020
android-11.0.0_r17 (november security patchlevel)
Click to expand...
Click to collapse
23.10.2020
hello android-11.0.0_r4 (october security patches!) for the xz2, xz2c & xz3
Click to expand...
Click to collapse

23.10.2020
Hello android-11.0.0_r4 (October Security patches!) for the XZ2, XZ2C & XZ3
Click to expand...
Click to collapse

Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

NYGGAZ said:
Wow..thanks a lot bro. I go test it tomorrow
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
You're welcome
And please report back if the dual sim patcher is still working

MartinX3 said:
You're welcome
And please report back if the dual sim patcher is still working
Click to expand...
Click to collapse
Of course bro.. I hope it work. Thanks a lot for your work[emoji6][emoji6]
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

thank you i am going to try it soon

Thank you very much for the effort to keep this phone alive!

Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk

NYGGAZ said:
Can I flash oem directly over the LOS 17.1 or need to reflash the latest FW?
Envoyé de mon Xperia XZ3 Dual (AOSP) en utilisant Tapatalk
Click to expand...
Click to collapse
Depends if you booted the latest FW on both slots the last time you came from stock.

Deleted

NYGGAZ said:
All is very VERY GOOD.. thanks Martin.. [emoji6][emoji6]View attachment 5123697
Envoyé de mon Xperia XZ3 (AOSP) en utilisant Tapatalk
View attachment 5123699
Click to expand...
Click to collapse
Thank you
But please hide several numbers in your screenshots.

Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.

zhka said:
Is it works with latest october blobs?
Coz my compiled one doesn't. Only works with latest A10 blobs.
Click to expand...
Click to collapse
Yes, this one only works with the newest OEM released before my builds.

which gapps to use

logan123456 said:
which gapps to use
Click to expand...
Click to collapse
Every
I prefer pico

I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?

y2kbugleung said:
I have been following the "no recovery" steps.
I have got the payload.bin extracted with this https://github.com/vm03/payload_dumper
Afterwards, I have got all the img flashed with fastboot.
Where should the SW_binaries_for_Xperia_Android_11_4.14_v1a_tama.img be used?
Click to expand...
Click to collapse
Nice!
The OEM step of the normal installation above

MartinX3 said:
Nice!
The OEM step of the normal installation above
Click to expand...
Click to collapse
So I fastboot flash oem SW...tama.img after flashing all ROM images.
Afterwards, do I still need a recovery (TWRP) to flash GApps and dual-sim-patch?
How could I install a recovery? I cannot find one from TWRP official site.
Thanks.

[ROM][13.0][walleye] Pixel Experience [AOSP]

{
"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"
}
PixelExperience for Google Pixel 2 [walleye]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 13.0.0_r43
Security patch level: May 2023
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_wahoo
https://github.com/PixelExperience-Devices/device_google_walleye
https://github.com/PixelExperience-Devices/kernel_google_wahoo
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_walleye
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09

Reserved

Good jobs very happy

Going to try this out.

PixelBoot said:
PixelExperience for Google Pixel 2 [walleye]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 13.0.0_r7
Security patch level: October 2022
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_wahoo
https://github.com/PixelExperience-Devices/device_google_walleye
https://github.com/PixelExperience-Devices/kernel_google_wahoo
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_walleye
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Click to expand...
Click to collapse
Thank you for keeping my old device up to date.
The recovery image does not seem to work. Flashes fine onto the device. Fastboot output:
Code:
target reported max download size of 536870912 bytes
sending 'boot_b' (32768 KB)...
OKAY [ 0.091s]
writing 'boot_b'...
OKAY [ 0.161s]
finished. total time: 0.253s
But when I reboot the device, it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.
If I try to use the recovery image from Android 12 it will not boot into the OS after flashing Android 13 and will boot loop forever (I waited 30 minutes).

00pflaume said:
感谢您让我的旧设备保持最新状态。
恢复映像似乎不起作用。在设备上闪烁良好。快速启动输出：
Code:
target 报告的最大下载大小为 536870912 字节
发送“boot_b”（32768 KB）...
好的 [ 0.091s]
写“boot_b”...
好的 [ 0.161s]
完成的。总时间：0.253s
但是当我重新启动设备时，它显示“错误：BootLinux 失败：缓冲区大小错误”，我无法启动恢复或进入系统。
如果我尝试使用 Android 12 中的恢复映像，它在刷新 Android 13 后将无法启动到操作系统，并且将永远启动循环（我等了 30 分钟）。
00pflaume said:
感谢您让我的旧设备保持最新状态。
恢复映像似乎不起作用。在设备上闪烁良好。快速启动输出：
Code:
target 报告的最大下载大小为 536870912 字节
发送“boot_b”（32768 KB）...
好的 [ 0.091s]
写“boot_b”...
好的 [ 0.161s]
完成的。总时间：0.253s
但是当我重新启动设备时，它显示“错误：BootLinux 失败：缓冲区大小错误”，我无法启动恢复或进入系统。
如果我尝试使用 Android 12 中的恢复映像，它在刷新 Android 13 后将无法启动到操作系统，并且将永远启动循环（我等了 30 分钟）。
Click to expand...
Click to collapse
you need new boot，for plixel2/2xl telegram enes
Click to expand...
Click to collapse

Thank you. The boot image from telegram worked.

For those struggling to get their boot.img going, give this one a try.

PixelBoot said:
PixelExperience for Google Pixel 2 [walleye]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 13.0.0_r7
Security patch level: October 2022
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_wahoo
https://github.com/PixelExperience-Devices/device_google_walleye
https://github.com/PixelExperience-Devices/kernel_google_wahoo
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_walleye
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Click to expand...
Click to collapse
It seems like the camera app is not working correctly.
When I am in camera mode the front and back camera just show a black screen, but if I switch to video recording or use a third party app everything works fine.
I am using the here provided recovery image.

00pflaume said:
似乎相机应用程序无法正常工作。
当我处于相机模式时，前后摄像头只会显示黑屏，但如果我切换到视频录制或使用第三方应用程序，一切正常。
我正在使用此处提供的恢复映像。
Click to expand...
Click to collapse
don“t update google play camera

00pflaume said:
Thank you for keeping my old device up to date.
The recovery image does not seem to work. Flashes fine onto the device. Fastboot output:
Code:
target reported max download size of 536870912 bytes
sending 'boot_b' (32768 KB)...
OKAY [ 0.091s]
writing 'boot_b'...
OKAY [ 0.161s]
finished. total time: 0.253s
But when I reboot the device, it says "ERROR: BootLinux Failed: Bad Buffer Size" and I am unable to boot into recovery or into the System.
If I try to use the recovery image from Android 12 it will not boot into the OS after flashing Android 13 and will boot loop forever (I waited 30 minutes).
Click to expand...
Click to collapse
I have the same problem,
PixelBoot said:
PixelExperience for Google Pixel 2 [walleye]
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13.0
Whats working?
Wi-Fi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FM radio
Sound/vibration
Known issues
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download from PixelExperience website
Donate
Liked my work? Give me a beer
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog​
Android OS version: 13.0.0_r7
Security patch level: October 2022
Build author/Device Maintainer: PixelBoot
Device Source code:
https://github.com/PixelExperience-Devices/device_google_wahoo
https://github.com/PixelExperience-Devices/device_google_walleye
https://github.com/PixelExperience-Devices/kernel_google_wahoo
https://gitlab.pixelexperience.org/android/vendor-blobs/vendor_google_walleye
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
Click to expand...
Click to collapse
Hey new bug found, Chrome keeps crashing

setting keeps crashing too

PixelBoot said:
For those struggling to get their boot.img going, give this one a try.
Click to expand...
Click to collapse
this one is also failing for me? any advice?

monikmax said:
this one is also failing for me? any advice?
Click to expand...
Click to collapse
same with mine as well

HenryTham said:
same with mine as well
Click to expand...
Click to collapse
for me the official installation guide failed, so i find a solution on reddit
download twrp, pe recovery (i use 12 because 13 doesn't work), product partition and the rom
reboot bootloader and
fastboot flash boot_a [twrp img file]
fastboot flash boot_b [pe recovery img file]
fastboot --set-active=a
fastboot reboot recovery (or do it with volume/power buttons)
now go to advanced settings (or something like that) and select adb sideload
adb sideload [productpartion zip file]
go back and reboot to bootloader
in bootloader
fastboot --set-active=b
fastboot recovery
in recovery format data a first time, go to apply update, adb and
adb sideload [rom zip file]
once finished format a second time
if you used PE 12 recovery reboot to bootloader and
fastboot flash boot [boot img file] (the file is up in the thread)
if it doesn't work i don't have any other solution sorry :/

Can confirm @Maseko.san's steps - they work great! SO far no issues at all
Don't forget that second format + 'fastboot flash boot [boot img file]' above, it replaces replacing slot a's boot with the one given by @PixelBoot!

Hey, sorry but I have to temporarily use my factory rom, on PE 12 and 13 It has a bug with audio media which is very disturbing,In fact when I put my phone to sleep and turn it on with music, the sound stops, it doesn't pause it just stops for 2-3 seconds and resumes
Someone have this issues?
(Sorry if my English is bad i'm just a 16 yo french so my English isn't really good)

Maseko.san said:
Hey, sorry but I have to temporarily use my factory rom, on PE 12 and 13 It has a bug with audio media which is very disturbing,In fact when I put my phone to sleep and turn it on with music, the sound stops, it doesn't pause it just stops for 2-3 seconds and resumes
Someone have this issues?
(Sorry if my English is bad i'm just a 16 yo french so my English isn't really good)
Click to expand...
Click to collapse
Known issue since PE 12. Disable "Now playing" (the Pixel feature that listens to ambient music).

Hey, now can't root with magisk patched boot image, I've tried to flash the img file but my phone isn't booting, and charge seems to stop randomly I don't know why (my charger and the cable works correctly)

The tutorial specifically tells me not to repeat any step, so I think I have a problem. I flashed the recovery image... successfully?
Code:
Sending 'boot_a' (32768 KB) OKAY [ 0.742s]
Writing 'boot_a' OKAY [ 0.164s]
Finished. Total time: 0.920s
Now when I try to boot into recovery mode with USB plugged in, the device just restarts and boots into Android. When I boot into recovery mode without USB plugged in, it boots into the "No command" screen (google images for "Android No command screen" to see what I mean) . But the tutorial says this:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
There's obviously nothing to select there.
Also, heads up: for some reason the first time I downloaded the recovery image it was 0 KB in size (and I tried to flash it). Fortunately, fastboot wouldn't allow flashing it, showing an error:
Code:
Sending 'boot_a' (0 KB) FAILED (File is too large to download)
.
But hey, it's not a brick (yet!)