- Breaking: Android 12 Beta GSI goes live ahead of Google I/O 2021
- Android 12 Beta GSI Downloads
- Android 12 Beta GSI Installation
- Android 12 custom GSIs bring the latest Android OS to any Project Treble-supported device
- [ROM][GSI] How to install Android 12 GSI with GApps
- Breadcrumb
- Quantizr
- [GSI][ANDROID 12 STABLE] Android 12 and any GSI larger than 2.6GB
- Breadcrumb
- Dollscythe
- 73sydney
- irmas5
- Dollscythe
- 123哆3
- Dollscythe
- irmas5
- Dollscythe
- Dollscythe
- irmas5
- Dollscythe
- irmas5
- irmas5
- Dollscythe
- Dollscythe
- irmas5
Breaking: Android 12 Beta GSI goes live ahead of Google I/O 2021
The first Android 12 Developer Preview was released back in February, followed by Preview 2, and recently, Preview 3. Google is supposed to release the Android 12 Beta 1 today to the Pixel lineup during Google I/O 2021. However, it looks like the official Android 12 Beta 1 Generic System Image (GSI) packages are already available for download!
A GSI is a prebuilt system image that can be booted on devices that support Project Treble. Even if you don’t own a compatible Pixel smartphone, you can still install Google’s official GSI binaries to test Android 12, provided your device is compatible with Project Treble. You also need an unlocked bootloader. The last thing that we need to say is that flashing a GSI will require you to factory reset your device, so be sure you’re prepared to lose app data before you proceed with this. We recommend you make an off-device backup (such as on your PC or an SD Card) in case anything goes wrong.
Android 12 Beta GSI Downloads
Please refer to the following table for the download links:
Architecture | Download Link |
---|---|
x86+GMS | Click Here |
ARM64+GMS | Click Here |
x86_64 | Click Here |
ARM64 | Click Here |
You should pick the appropriate version of the GSI binary based on your device’s architecture. To see which architecture your device has, run the following command:
Android 12 Beta GSI Installation
Before attempting to install the Android 12 GSI, make sure you have access to a PC/Mac with adb and fastboot installed.
- Extract the .zip file, and copy and paste the resultant files (system.img and vbmeta.img) onto your ADB and fastboot folder on your computer for convenience.
- Enable USB Debugging on your phone — Go to Settings > About Phone > Tap “Build Number” 7 times, (optionally) enter your pattern, PIN or password to enable Developer Options, and then navigate to Settings > Developer Options > Enable “USB Debugging”.
- Connect your phone to your computer. Authorize your computer connection on your phone when the prompt comes up on your phone, if this is the first time you are connecting with this ADB computer.
- On your computer, run:
This will reboot your phone into Fastboot mode.
In case you have a device running Android 11, then you can also try out the DSU Loader utility from Developer Options to boot the Android 12 GSI without needing to fiddle with any Fastboot or ADB commands.
Credits to XDA Recognized Developer luca020400 for the tip!
Источник
Android 12 custom GSIs bring the latest Android OS to any Project Treble-supported device
Android 12 is here, albeit the stable version is available only on Google’s Pixel lineup — including the newly introduced Pixel 6 series — for now. A handful of OEMs like Samsung and OnePlus are also offering public beta builds of their customized skins based on the stable Android 12 codebase, but the list of eligible devices is quite small. Nonetheless, the aftermarket development community is helping us experience all the new features of Android 12 through custom ROMs across a growing list of devices. Besides, Google does offer its own set of Android 12 Generic System Image (GSI) packages on its website, so that developers can test their apps against the latest API level.
While you should be able to boot Google’s AOSP GSI onto any Project Treble-supported device, you’ll be missing out on many features that lend to a proper day-to-day experience. This is exactly where XDA Recognized Developer phhusson‘s custom GSI distribution comes in. These GSI packages come with a plethora of bug fixes and feature additions that aren’t available in the barebone Google-provided GSIs. The developer has now rebased his custom Project Treble GSI project (AKA “Phh-Treble”) on top of Android 12 and started publishing pre-release builds with new device-specific patches required for the latest Android version.
If the vanilla AOSP experience is not enough for you, then you can also try out an unofficial build of the Pixel Experience GSI, courtesy of XDA Senior Member ponces. It comes with all the goodies that you’d usually find on a Google Pixel device, including the Pixel launcher, wallpapers, icons, fonts, and even the boot animation. Keep in mind that the GSI backbone is based on phhusson’s release, which means it does carry forward nearly the same set of bugs and glitches.
At the time of writing this article, there is no A-only build available for download, so you do need a device with A/B partitioning to boot the aforementioned GSIs. Once phhusson’s custom AOSP GSI becomes more stable, he and other developers will start building more variants. Before you go ahead and flash any of the custom Android 12 GSIs on your device, be sure to take a backup of your data and then only go through our GSI installation guide.
Источник
[ROM][GSI] How to install Android 12 GSI with GApps
Breadcrumb
Quantizr
New member
Then skip to step 10 and continue in order to be able to use play store.
Sorry in advance for the confusing nature of this guide. I had no idea what was going on half the time. This is the result of me trying to get Android 12 to work for around 12 hours (mostly time spent reflashing system images after screwing something up).
I probably won’t link every single tool and define every term as I’m just trying to outline what to do and why. There are probably some unnecessary steps in here, but I have no idea which ones are unnecessary..
For the Android 12 GSI, I used Andy Yan’s (he’s a LineageOS Contributor) Lineage 19 personal build found here: https://sourceforge.net/projects/an. IAL-treble_arm64_bvS-personal.img.xz/download
Edit: that version has been deleted now and replaced with a version that doesn’t work for me at least.
If you don’t care for installing gapps, this whole thing becomes a lot easier, just follow the instructions here (https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/) except with the above ROM.
If you do want to install gapps, there are quite a few extra steps. (Or maybe I’ve been doing it wrong the whole time)
Known bugs:
- I keep getting a push notification that says “android system intelligence has stopped” but everything else works fine
- Disabling app in settings fixes this
- Carrier voice calls and SMS do not work (Google Voice/Whatsapp work fine)
Background:
- The touchscreen in TWRP stopped working after the September 2018 software update, if you have an OTG adapter, you can still use a mouse.
- TWRP is useful in expanding the system partition and installing gapps
- the PH1 uses an A/B slots, we can keep an old August 2018 version on the B slot to work with TWRP and the new Android 12 GSI on the A slot
Step 1: Flash the August 2018 ROM onto the B slot
This ROM allows for TWRP to work with touch.
Extract the folder, right click the file called “flashallwipe.bat” and edit it. Delete any lines with “fastboot flash” followed by something “_a” for example “fastboot flash nvdef_a nvdef” so that the only things remaining are the ones with “_b”s.
Once you’ve done that save the file.
Reboot your phone to the bootloader (hold power button + volume down or run “adb reboot bootloader” in the command prompt).
With your phone plugged in, run the edited “flashallwipe.bat” and wait
Step 2: Flash the October 2019 ROM onto the A slot:
This step might not be necessary, depending on what your current ROM is, however, if you have an older ROM, for example, the August 2018 ROM on the A slot, your touchscreen will stop working on the GSI, so its probably better just to do this just in case.
Extract the file and do the same thing as the last step, except deleting the lines in “flashallwipe.bat” containing “_b” instead of “_a”.
Save the file, run it and wait.
Step 3: Flash stock AOSP onto the A slot:
The next thing you have to do is flash a stock AOSP ROM in order to disable verity.
Follow steps 1-6 of this guide: https://forum.xda-developers.com/t/gsi-rom-aosp-android-gsi-support-for-essential-phone.4326297/
Edit: that version has been deleted now and replaced with a version that doesn’t work for me at least.
Источник
[GSI][ANDROID 12 STABLE] Android 12 and any GSI larger than 2.6GB
Breadcrumb
Dollscythe
Senior Member
If you need help, feel free to post logs here. For more discussions about Android 12/GSIs join the telegram group!!
Make sure to use Android 11 as base before flashing the GSI.
After that, you can install any GSI/flash any size Gapps without issue.
- Reboot into fastboot mode.
- Wipe your data partition: fastboot format:ext4 userdata
- Clean cache and factory reset: fastboot -w
- flash the GSI: fastboot flash system_a path/to/system.img
- flash the GSI in other slot: fastboot flashsystem_b path/to/system.img
- Test boot.
If it doesn’t boot, download vbmeta for your device and flash in fastboot mode.
- fastboot flashvbmeta —disable-verity —disable-verification vbmeta.img
- fastboot -w
Bugs:
- No sound in call.
Some fixes:
- Install GMS with adb install -r -dpath/to/gms.apk to login to Google (not necessary anymore)
- After flashing system image, don’t reboot into system, immediately boot into TWRP and flash this file ! This is necessary to disable encryption, so TWRP can boot successfully.
73sydney
Senior Member
Appreciate the resize guide, especially as i like a full GApps install
But the ROM is impossible to download it seems.
Note: Im able to download other files at SF
Update: Finally found a working mirror — for anyone else try the Gigenet mirror (Chicago), by clicking «Problems Downloading»
irmas5
Senior Member
If you need help, join the telegram group.
Follow the guide I made here to increase your system partition.
USE STOCK RECOVERY.
After that, you can install any GSI/flash any size Gapps without issue.
Download Android 12 Beta 3.1 GSI here: Direct link
You don’t need Gapps, they are preloaded.
- Reboot into fastboot mode.
- Wipe your data partition: fastboot format:ext4 userdata
- Clean cache and factory reset: fastboot -w
- flash the GSI: fastboot flash system_a path/to/system.img
- flash the GSI in other slot: flash system_b path/to/system.img
- Test boot.
If it doesn’t boot, flash this file in fastboot mode.
- fastboot —disable-verity —disable-verification flash vbmeta vbmeta.img
- fastboot -w
View attachment 5371367View attachment 5371395View attachment 5371423View attachment 5371425View attachment 5371427View attachment 5371429View attachment 5371431View attachment 5371433
Dollscythe
Senior Member
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.
123哆3
Member
Dollscythe
Senior Member
This guide is for pixel 2xl.
the GSI is ported from pixel 3 android S beta 3.1, but it works on pixel 2xl and all A/B devices.
irmas5
Senior Member
For now FP and calling is not working. Everything else is perfect. This rom is for those who want to test new theming etc.
I am working on a fix for fp and RIL.
Dollscythe
Senior Member
Dollscythe
Senior Member
Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there’s no sound! Any devs can chime in and help?
irmas5
Senior Member
Update! With GMS, overlay, and fingerprint sensor fixes. We are getting closer!
And the users that had unbootable slot error, it should be fixed too if you flash vbmeta. Make sure to follow the fixes section too.
EDIT: RIL is fine, SMS is fine, we can even accept and take calls. But there’s no sound! Any devs can chime in and help?
Dollscythe
Senior Member
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda
irmas5
Senior Member
show me your new partition table
boot to twrp
Copy parted to /sbin.
adb push path/to/parted /sbin
Enter shell mode.
adb shell
Change permissions of parted.
chmod 777 /sbin/parted
then do parted /dev/block/sda
PS C:\platform-tools> adb push «C:\Users\irmas\Desktop\Pixel 2 xl\parted»/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
irmas5
Senior Member
Dollscythe
Senior Member
PS C:\platform-tools> adb push «C:\Users\irmas\Desktop\Pixel 2 xl\parted»/sbin
2250 KB/s (470788 bytes in 0.204s)
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted)
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 2853MB 2684MB ext2 system_a
8 2853MB 5538MB 2684MB ext2 system_b
9 5538MB 5546MB 8389kB pstore
10 5546MB 5546MB 524kB aes_a
5546MB 62.5GB 57.0GB Free Space
You didnt finish the partitions.
there’s supposed to be aes_b, and userdata, etc.
you didnt follow the tutorial properly
Dollscythe
Senior Member
irmas5
Senior Member
I restarted again everything from begining and now goes well. Now flashed proton aosp and booting. now showing
PS C:\platform-tools> adb shell
taimen:/ # chmod 777 /sbin/parted
taimen:/ # parted /dev/block/sda
GNU Parted 3.2
Using /dev/block/sda
Welcome to GNU Parted! Type ‘help’ to view a list of commands.
(parted) p free
Model: SAMSUNG KLUCG4J1ED-B0C1 (scsi)
Disk /dev/block/sda: 62.5GB
Sector size (logical/physical): 4096B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
12.3kB 24.6kB 12.3kB Free Space
1 24.6kB 50.4MB 50.3MB laf_a
2 50.4MB 101MB 50.3MB laf_b
3 101MB 101MB 8192B ssd
4 101MB 134MB 33.6MB ext4 persist
5 134MB 135MB 1049kB misc
6 135MB 169MB 33.6MB ftm
7 169MB 3269MB 3100MB ext2 system_a
3269MB 3269MB 459kB Free Space
8 3269MB 6369MB 3100MB ext2 system_b
9 6369MB 6379MB 9953kB pstore
10 6379MB 6380MB 999kB aes_a
11 6380MB 6381MB 999kB aes_b
12 6381MB 6391MB 9998kB align_parti
6391MB 6391MB 69.6kB Free Space
13 6391MB 62.5GB 56.1GB ext4 userdata
62.5GB 62.5GB 12.3kB Free Space
Источник