• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][ANDROID S BETA 3.1] Android 12 and any GSI larger than 2.6GB

Search This thread

Langduscher

Senior Member
Jan 30, 2012
1,284
348
Texel

I've downloaded the ARM64+GMS file and extracted the system.img

I flashed to both system_a and system_b, which was successful.

However, it doesn't boot: it goes straight back to the bootloader, even after flashing vbmeta.img

How to trouble shoot?

Thanks!

Edit: it won't open twrp either (fastboot boot twrp.img)

Code:
~/platform-tools$ ./fastboot boot twrp.img
Sending 'boot.img' (40960 KB)      OKAY [  3.153s]
Booting                                                  OKAY [  0.001s]
Finished. Total time: 3.193s

But it just goes straight into bootloader again.

Edit2: I used the recovery from your other thread regarding the partitions - that seems to work.

I just followed all the steps to the T again - but it just won't boot. It boots straight into bootloader.


Edit 3: the Beta 3 image flashes just fine...
 
Last edited:

Dollscythe

Member
Jul 23, 2021
44
66
I've downloaded the ARM64+GMS file and extracted the system.img

I flashed to both system_a and system_b, which was successful.

However, it doesn't boot: it goes straight back to the bootloader, even after flashing vbmeta.img

How to trouble shoot?

Thanks!

Edit: it won't open twrp either (fastboot boot twrp.img)

Code:
~/platform-tools$ ./fastboot boot twrp.img
Sending 'boot.img' (40960 KB)      OKAY [  3.153s]
Booting                                                  OKAY [  0.001s]
Finished. Total time: 3.193s

But it just goes straight into bootloader again.

Edit2: I used the recovery from your other thread regarding the partitions - that seems to work.

I just followed all the steps to the T again - but it just won't boot. It boots straight into bootloader.


Edit 3: the Beta 3 image flashes just fine...
What GSI wasnt working for you initially? you mention beta3 flashing properly.
 

Langduscher

Senior Member
Jan 30, 2012
1,284
348
Texel
@Dollscythe FYI, Android 12 Beta 3.1 GSI download link is dead.

Could someone reupload that? I tried GSI beta 5 from Google and also some image named "Pixel-AB-12-20210909-ErfanGSI-TrebleExp.img" but they are not working. Same findings as @Langduscher

When @Dollscythe doesn't mind, I can upload the beta 3 image


Worth pointing out, neither Beta has working call audio folks

Im not in a rush for that, not sure why anyone else would be...

Well, beacuse why not?

The Pixel 2XL isn't my daily driver, that helps in trying this stuff out :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Thank you for taking the time to help and wrap my head around the subject , much appreciated!

    Is this the same way a custom recovery increases the system partition?
    There are no custom recoveries that can do that.

    However. I'm working on a tool that will automate that process. There's a closed beta in the telegram channel and it will see a beta release on xda soon.
    3
    the solution is very simple to fix no audio in call, it is flash this patch: https://drive.google.com/file/d/1HvwSLudIiDqvIvd23Hxi5A4onaplM1Cd/view?usp=sharing, but real problem is our device cann't mount /vendor r/w, so this patch not work, so we have to wait phhtreble
    you can mount vendor r/w if you use a custom vendor from custom rom. flash dot OS or proton AOSP and u can modify vendor.
    try ur tweak and report back, cheers.
    3
    Can you please report on ahat's working and what's not working
    I was also successful in booting pixel 5 android 12 gsi which is much more stable than the 3a port(it was sluggish)
    On both ports:
    NFC, Bluetooth, D2W/D2S and calling doesn't work. Rest all works perfectly.
    Currently I'm on the pixel 5 port and I have to say it's very smooth and stable.

    Note: you will have to make your system partition of 4 GB instead of 3 GB to flash the pixel 5 system image.
    2
    Dont give users technical advice that could brick their devices.

    If you want to increase system partition, IT'S LITERALLY THE FIRST LINK IN THE THREAD.

    there's a STEP BY STEP GUIDE THAT YOU HAVE TO FOLLOW 100% OR ELSE YOUR DEVICE IS PERMANENTLY DEAD.

    Sorry about that, but the advice I gave is tested by me and it works 100% if followed accurately.
    And I even added a Disclaimer at the start and end saying follow this on you own, and it's best to follow the guide given by the link from OP.

    I'm sorry again.

    The reason i advised against your post is because it only works for 64GB variants. If they have 128GB phone, then half of their storage is gone. Cheers

    It's all good ✌ I asked for a clarification to learn and @MridulDR 's explanation on top of your OP wrapped my head around the subject: I know understand what I'm doing. The last part of the resizing (64 vs 128Gb) I actually understood. It is clearly stated too 👍

    That's what XDA is about for me: learning. In fact, I successfully flashed A12b5.

    There are no custom recoveries that can do that.

    However. I'm working on a tool that will automate that process. There's a closed beta in the telegram channel and it will see a beta release on xda soon.

    I found this video where TWRP resizes the system partition, hence my question 🙂

    A tool that automates what I've learned from your post would be awesome.
    I don't use Telegram so I'll patiently wait until it arrives here.
    2
    Is there an easy way to do increase the system partition?

    I get this error message:

    Sending sparse 'system_a' 1/6 (500352 KB) OKAY [ 35.941s] Writing 'system_a' FAILED (remote: 'Image is too large for the partition') fastboot: error: Command failed

    Following the link from OP I am unsure on how to increase the system partition and change the others.

    Thanks in advance 🤗
    Firstly I wouldn't suggest doing this, as you can HARD BRICK your device period.
    Now that that's out of the way, you just have to follow all the steps from the link in the OP in the same order, just instead of adding 3100 to 169 MB(system_a, system_b) you add 4100 to it. And accordingly increase the rest of the values sequentially.
    For eg:
    mkpart system_a ext4 169MB 4269MB
    mkpart system_b ext4 4269MB 8369MB
    mkpart pstore 8369MB 8379MB
    mkpart aes_a 8379MB 8380MB
    mkpart aes_b 8380MB 8381MB
    mkpart align_parti 8381MB 8391MB
    mkpart userdata ext4 8391MB 62400MB

    Edit: This'll only work for 64 GB variant.

    If all goes well then after naming the partitions check whether all the partitions you made are there and are in the sequential order as before as written in the link from OP(DOUBLE CHECK THIS)

    NOTE: As you're modifying the system partition I wouldn't recommend doing anything other than whats written in the link from OP, as that works 100%. This'll work no doubt but if anything goes south it's on you.
  • 15
    If you need help, join the telegram group.

    *REQUIRED* Follow the guide I made here to increase your system partition.

    Download Android 12 Beta 3.1 GSI here: Direct link

    Make sure to use a stable base OS, preferably dotOS, OR ELSE FINGERPRINT WON'T WORK.

    After that, you can install any GSI/flash any size Gapps without issue.

    You don't need Gapps, they are preloaded.


    1. Reboot into fastboot mode.
    2. Wipe your data partition: fastboot format:ext4 userdata
    3. Clean cache and factory reset: fastboot -w
    4. flash the GSI: fastboot flash system_a path/to/system.img
    5. flash the GSI in other slot: fastboot flash system_b path/to/system.img
    6. Test boot.
    If it doesn't boot, download vbmeta for your device and flash in fastboot mode.
    1. fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
    2. fastboot -w
    Bugs:
    • No sound in call.
    Some fixes:
    • Install GMS with adb install -r -d path/to/gms.apk to login to Google
    • 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.

    1627349705135.png
    1627352232766.png
    Screenshot_20210727-043809.png
    Screenshot_20210727-043817.png
    Screenshot_20210727-043846.png
    Screenshot_20210727-043852.png
    Screenshot_20210727-043714.png
    Screenshot_20210727-043323.png

    download
    5
    Thank you for taking the time to help and wrap my head around the subject , much appreciated!

    Is this the same way a custom recovery increases the system partition?
    There are no custom recoveries that can do that.

    However. I'm working on a tool that will automate that process. There's a closed beta in the telegram channel and it will see a beta release on xda soon.
    5
    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?
    4
    Be great to know who's working who no on this rom. Thank you
    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.
    3
    Wait... Does it for Pixel 3 but not Pixel 2 XL?


    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.