ROM ❯ PIXEL 5 ❯ OFFICIAL ❯ ProtonAOSP 11

[kdrag0n]

Nice work on the rom. I was able to get it up and running on MacOS without any issues. Although seems to be security concerns for using it as daily driver.. according to GrapheneOS lead keeping bootloader unlocked is highly unsecure as it opens up attack vector:

Locking the bootloader is important as it enables full verified boot. It also prevents using fastboot to flash, format or erase partitions. Verified boot will detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system, vendor) and it will prevent reading any modified / corrupted data. If changes are detected, error correction data is used to attempt to obtain the original data at which point it's verified again which makes verified boot robust to non-malicious corruption.

In the bootloader interface, set it to locked:

fastboot flashing lock
The command needs to be confirmed on the device since it needs to perform a factory reset.

Unlocking the bootloader again will perform a factory reset.

BTW have you thought about joining GrapheneOS as Pixel 5 maintainer? You'd be a great addition to team and project is lacking Pixel 5 dev.

Cheers

That's true, but I am not personally concerned about malicious images being flashed . As a developer, I will frequently flash unbootable and can't justify the risk of losing data.


It's possible that my ROM will support verified boot in the future so you will have the option to lock the bootloader, but I wouldn't count on that happening in the near future since my ROM is in its early days and the underlying infrastructure is immature; AVB support will require managing signing keys securely between the different machines I build ROMs on.


As much as I want to get involved, I don't have the time for it and my own ProtonAOSP project is what I'm most satisfied with using as a daily driver on my own device. GrapheneOS is great from a security and hardening perspective, but its performance and UI are lacking due to being nearly uncustomized AOSP with performance. I understand that some people will prioritize security, but personally, I don't want to make that trade-off.

I didn't see any posts covering this, but does this work for the japanese variant? I upgraded from 2xl (mine was really broken somehow) and am loving this new device and don't want to risk breaking it if the Japanese variant isn't supported/tested

It should work as long as the bootloader is unlockable. The only low-level variants are the Pixel 4a 5G, Pixel 4a 5g UW (Verizon), and Pixel 5; other hardware variations should not matter at the software level.

Is there a native call recording function? one that records the other side as well, not just your side.
If not, do you plan to add it in or would rather not bother because of country laws?
I still don't have my device yet so I can't install it yet to find out myself.
Thanks.

Call recording is not a feature I'm personally interested in, and as a small project with no other core team members at the moment, I don't have time to add every feature people want while keeping the same level of quality across the board. It's also illegal to record calls without mutual consent in my location, so I wouldn't be able to use it anyway.

 

[mousse04]

Hi @OP,
I will ask a stupid question but how can you build a better battery saving ROM than the tons of google devs? No offense here, I'm just here to understand

 

[Yanagibashi]

I managed to flash it but whenever I boot it gets stuck on this animation of a flaming flask, any ideas?

 

[rav101]

I managed to flash it but whenever I boot it gets stuck on this animation of a flaming flask, any ideas?

Have you wiped data once you've flashed the ROM? You can do this in the recovery if you want.

Sent from my Pixel 5 using XDA Labs

 

[Yanagibashi]

Have you wiped data once you've flashed the ROM? You can do this in the recovery if you want.

Sent from my Pixel 5 using XDA Labs

I dont think I did, ill try that when I get home

 

[kdrag0n]

Hi @OP,
I will ask a stupid question but how can you build a better battery saving ROM than the tons of google devs? No offense here, I'm just here to understand

A lot of the battery drain on stock comes from how bloated it is from my experience — minimal in comparison to most other OEMs, but there is still bloat. AOSP does not have said bloat, and I've avoided adding too much Google bloat to help with battery life.

 

[Jackie Coyote]

Do you think it's possible to run this kernel on the stock factory image? Would I also have to flash the roms DTBO image?

 

[kdrag0n]

Do you think it's possible to run this kernel on the stock factory image? Would I also have to flash the roms DTBO image?

This ROM does not include a custom kernel. It's exactly the same as stock, so there's no point in flashing it over stock.

 

[veedubrocks]

Hello. Anyone knows why it failed at this spot? Thanks


Checking product... KAY [ 0.069s ]

ending 'boot_a' (98304 KB)...

OKAY [ 3.270s]

writing 'boot_a'... OKAY [ 1.960s]

sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 9.078s]

writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 14.739s

Press any key to exit...


Sorry couldn't attach pic

 

[TikiThePug]

Hello. Anyone knows why it failed at this spot? Thanks


Checking product... KAY [ 0.069s ]

ending 'boot_a' (98304 KB)...

OKAY [ 3.270s]

writing 'boot_a'... OKAY [ 1.960s]

sending sparse 'system_a' 1/4 (262140 KB)...
OKAY [ 9.078s]

writing 'system_a' 1/4...
FAILED (remote: Partition should be flashed in fastbootd)
finished. total time: 14.739s

Press any key to exit...


Sorry couldn't attach pic

Sounds like your phone did not reboot into fastbootd when it got to this stage. Does it keep happening?

 

[veedubrocks]

Sounds like your phone did not reboot into fastbootd when it got to this stage. Does it keep happening?

Sorry my fault. Need updated platform tools. All good. Now for magisk

 

[Vadotic]

Regarding UI tweaks: can I center my clock in the status bar and show seconds? Thanks.

 

[grisly grizzly]

Hey y'all, I've been trying to install this ROM but no matter what I do I can't get it to install correctly. I navigate to where I have the flash-all.bat saved and I run that using ./flash-all.bat in powershell and it gives me this output...

PS C:\platform-tools\proton-aosp_redfin_11.2.0-gapps\redfin-rd1a.201105.003.c1> .\flash-all.bat
target reported max download size of 268435456 bytes
sending 'bootloader' (8890 KB)...
OKAY [  0.325s]
writing 'bootloader'...
(bootloader) Flashing Pack version r3-0.3-6776358
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition featenabler_a
(bootloader) Flashing partition logfs
OKAY [  0.876s]
finished. total time: 1.202s
rebooting into bootloader...
OKAY [  0.051s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
sending 'radio' (134660 KB)...
OKAY [  3.316s]
writing 'radio'...
(bootloader) Flashing Pack version SSD:g7250-00016-200911-B-6826885
(bootloader) Flashing partition modem_a
OKAY [  2.792s]
finished. total time: 6.109s
rebooting into bootloader...
OKAY [  0.050s]
finished. total time: 0.051s
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: r3-0.3-6776358
Baseband Version.....: g7250-00016-200911-B-6826885
Serial Number........: 09281FDD40054G
--------------------------------------------
checking product...
OKAY [  0.070s]
sending 'boot' (98304 KB)...
OKAY [  2.450s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.828s
Press any key to exit...

I originally tried on a rooted version of the November update, then I tried installing from a stock November update, then a stock October update, eventually gave up and install and rooted October's update. I'm now trying again and having no luck. Whenever I search the error 'FAILED (remote: Failed to write to partition Not Found)' everyone just says "Make sure your adb and fastboot is up to date" but it IS up to date, I downloaded a fresh copy of the tools straight from google the night I tried. I have the latest adb and fastboot, I have the latest and correct USB drivers. Gonna go try on my roommate's PC but if that doesn't work I really have no clue what to do. Initially when I tried to install this I semi-bricked my device for a few hours and had to make an XDA post about it. I'd really like to try this custom ROM, if anyone has any suggestions I'd appreciate it.

 

[veedubrocks]

What version of platform tools you're using. That was my issue at the start. Lastest version is like 30.x.x. something like that. Just a suggestion. Good luck

 

[Regys]

hi,

What is the advantage over stock ROM ?

 

[TikiThePug]

hi,

What is the advantage over stock ROM ?

Read the first post.

 

[hanni2301]

Is there any dark dark mode? I'm looking for black (0/0/0) and not the grayish colour like in the settings.

 

[Hellshell]

ProtonAOSP • Pixel 5
Android 11 ROM​

ProtonAOSP is a minimal custom Android 11 ROM focused on UI/UX and performance, with a touch of privacy.

Screenshots
Screenshots for v11.2.0
If you don't like Imgur, you can also find the screenshots on the public Telegram channel (no login needed).

Features


Downloads
Downloads and changelogs can be found on GitHub. The topmost release is the latest. Builds with and without gapps included are provided for convenience.

Make sure you download a ROM ZIP, not source code! Source code cannot be flashed.


Installation
This ROM is currently distributed as factory images similar to stock due to the lack of TWRP. Flash it as you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.

Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.

Known issues

• Wi-Fi calling doesn't work on some carriers (most notably Verizon)
• Now Playing, Live Captions, and screen attention are missing

Join the Telegram group for support and extras
Donate to support development

Kernel source code

Brother I'm so confused do I have to flash the GAPPS as well? I know some roms have gapps already.

 

[sic4672]

Two versions. One already has gapps. The other doesn't

Sent from my Pixel 5 using Tapatalk

 

[rav101]

Brother I'm so confused do I have to flash the GAPPS as well? I know some roms have gapps already.

No you don't. The version with gapps only has Google play store and one or two other things just to get it working. Anything else you install from the play store once you've set up the ROM.

Sent from my Pixel 5 using XDA Labs