Skip to content

Add support for Pixel 6a (bluejay) #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Add support for Pixel 6a (bluejay) #190

wants to merge 2 commits into from

Conversation

tejasraman
Copy link

@tejasraman tejasraman commented Jul 29, 2023

Adds configuration file for Pixel 6a (bluejay). Process for unlocking BL is extremely similar to that of the Pixel 5a (barbet).

I set the required Android version to 13.0.0 (as firmware was changed for Tensor-based devices with A13). Config files for 6a should also work with 6 and 6 pro (if modified).

Tested and working here @tsterbak

@tsterbak tsterbak added this to the Release Beta-Version 0.4.5 milestone Jul 29, 2023
@tsterbak tsterbak added the device Request to add or improve a specific device. label Jul 29, 2023
@tsterbak
Copy link
Member

Hey, thanks a lot for the contribution! ☺️
It will be part of the next release.

So it seems this part (https://wiki.lineageos.org/devices/bluejay/install#flashing-additional-partitions) isn't required if you use TWRP? I was not sure about this yet, but it would open up support for some more devices.

@tsterbak tsterbak changed the base branch from main to dev July 29, 2023 08:58
@tejasraman
Copy link
Author

tejasraman commented Jul 29, 2023

Hey, thanks a lot for the contribution! ☺️ It will be part of the next release.

So it seems this part (https://wiki.lineageos.org/devices/bluejay/install#flashing-additional-partitions) isn't required if you use TWRP? I was not sure about this yet, but it would open up support for some more devices.

So afaik there is no twrp for the 6 series (and instead lineage recovery needs to be flashed) - so that step is required. However, same holds true for the 5a, was that actually working for you?

@tejasraman tejasraman marked this pull request as draft July 29, 2023 15:01
@tsterbak tsterbak removed this from the Release Beta-Version 0.4.5 milestone Jul 29, 2023
@tsterbak
Copy link
Member

@tejasraman
Copy link
Author

That makes sense, but it seems that for 6 and 7 los recovery is needed. I already had it on my phone and it flashed the correct rom but, in hindsight, that was bad testing procedure. I’ll try to add LOS recovery support to this.

@ghost
Copy link

ghost commented Jul 29, 2023

I’ll try to add LOS recovery support to this.

Does LOS recovery support "adb shell twrp..." commands ?
If yes, please wait a while, I'm working on how OAI handle recoveries (I'm adding OrangeFox support, see #188 )
After I commit all my changes, it should be very simple (I hope ^^)

@tsterbak
Copy link
Member

Does LOS recovery support "adb shell twrp..." commands ?

That is actually the issue... I suspect there is some scripting possible, but I found it documented nowhere and was not able to use it yet.

This is the source file of the LOS recovery (as far as I understand it): https://github.com/LineageOS/android_bootable_recovery/blob/lineage-20.0/recovery.cpp

@ghost
Copy link

ghost commented Jul 29, 2023

In the worst case, we can make some more steps for the user :
The Lineage recovery UI is very simple, so something like "Click on advenced, then adb sideload" shouldn't be too complicated for the average user

Let's see how it works, there may be solutions to this problem : https://doc.e.foundation/easy-installer

@MagicLike MagicLike added this to the Release Beta-Version 0.5.1 milestone Oct 2, 2023
@tsterbak tsterbak removed this from the Release Beta-Version 0.5.1 milestone Oct 19, 2023
@tejasraman tejasraman closed this by deleting the head repository Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
device Request to add or improve a specific device.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants