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

[GUIDE] System partition too small? Installing Android 12, GApps & large GSIs on Pixel 2 XL!

Search This thread

我是十七

Senior Member
Dec 17, 2020
57
9
134|taimen:/ # parted /dev/block/sda
Warning: Device /dev/block/sda has a logical sector size of 4096. Not all parts
of GNU Parted support this at the moment, and the working code is HIGHLY
EXPERIMENTAL.

GNU Parted 1.8.8.1.179-aef3
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
p free


You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Error: SEGV_MAPERR (Address not mapped to object)
Aborted
What caused this????
 

Dollscythe

Senior Member
Jul 23, 2021
147
357
134|taimen:/ # parted /dev/block/sda
Warning: Device /dev/block/sda has a logical sector size of 4096. Not all parts
of GNU Parted support this at the moment, and the working code is HIGHLY
EXPERIMENTAL.

GNU Parted 1.8.8.1.179-aef3
Using /dev/block/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p free
p free


You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (1.8.8.1.179-aef3)
along with the error message below, the output of

parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Error: SEGV_MAPERR (Address not mapped to object)
Aborted
What caused this????

make sure to push parted again and give it chmod perms (even if you did it before.)
 
  • Like
Reactions: jonpjingleheimler
IMG_20210913_045724.jpg

M stock here bro help me 🤣
 

vatva69

Member
Sep 5, 2016
32
13
Hanoi
Also, dotOS contains gapps already and as such it takes a lot of space. So maybe that's why you arent able to fit in more GAPPS.

What you could try is flashing a GSI and installing gapps. Try lineageOS as well.

Had issues with:

Almost all partition steps complaiend about not beign able to inform the kernel and i had to ignore the warnings all the way through....so just be aware, not for the faint of heart

fastboot erase aes_a
fastboot erase aes_b
fastboot erase align_parti
fastboot erase userdata
fastboot format:ext4 system_a
fastboot format:ext4 system_b
fastboot format:ext4 userdata

Aka:

$ fastboot erase pstore
Erasing 'pstore?' FAILED (remote: 'Check device console.')
fastboot: error: Command failed


Booted TWRP and at least fixed the data and system parts - Ext4 to Ext2 to Ext4 again....properly mounted

Tried flashing A12...nope

Flashed A11 Stock (to hopefully fix partitions)..booted

Now back in fastboot erasing system (a/b) and userdate and trying to flash to A12 again

Nope, that didnt work...boot warning - your device is corrupt...

Flashing back to A11 again (hopefully)

Update, back in A11....
you need to remove space in command fastboot erase pstore, there is a space in the last letter
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,776
Sydney
Google Pixel 2 XL

@Dollscythe

fwiw, i did this again to increase partition to 4Gb, and the commands quoted as failing in my original post on the subject, still failed using the latest platform-tools ....though i updated 3 of them thinking logically about why they failed..incorrect naming, as you will see and will make sense...last time i did this at 4am and i missed seeing the errors :)

At Step 11, heres all that worked

( please note the change to:

fastboot erase system
from
fastboot erase system_a

and


fastboot erase aes
from
fastboot erase aes_a


and

fastboot erase align_part
from
fastboot erase align_parti

)


fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(that you downloaded earlier)
fastboot erase system
fastboot erase system_b


i had to do a reboot here before any of the following commands would complete...

fastboot reboot bootloader

fastboot erase pstore
fastboot erase aes
fastboot erase aes_b
fastboot erase align_part
fastboot erase userdata


none of these would work:

fastboot format:ext4 system (from fastboot format:ext4 system_a)
fastboot format:ext4 system_b
fastboot format:ext4 userdata


i formatted them in TWRP...usual trick to get them to format and mount properly - change/repair filesystem on both /system and /data, first changing them to EXT2, before changing them back to EXT4 again...
 
Last edited:

Dollscythe

Senior Member
Jul 23, 2021
147
357

@Dollscythe

fwiw, i did this again to increase partition to 4Gb, and the commands quoted as failing in my original post on the subject, still failed using the latest platform-tools ....though i updated 3 of them thinking logically about why they failed..incorrect naming, as you will see and will make sense...last time i did this at 4am and i missed seeing the errors :)

At Step 11, heres all that worked

( please note the change to:

fastboot erase system
from
fastboot erase system_a

and


fastboot erase aes
from
fastboot erase aes_a


and

fastboot erase align_part
from
fastboot erase align_parti

)


fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(that you downloaded earlier)
fastboot erase system
fastboot erase system_b


i had to do a reboot here before any of the following commands would complete...

fastboot reboot bootloader

fastboot erase pstore
fastboot erase aes
fastboot erase aes_b
fastboot erase align_part
fastboot erase userdata


none of these would work:

fastboot format:ext4 system (from fastboot format:ext4 system_a)
fastboot format:ext4 system_b
fastboot format:ext4 userdata


i formatted them in TWRP...usual trick to get them to format and mount properly - change/repair filesystem on both /system and /data, first changing them to EXT2, before changing them back to EXT4 again...
Probably misnamed the partiton when making them. It's align_parti for sure, and not align_part

That's why it's wise to screenshot your partition table before making any modification to it.

I will soon release a tool that automates this entire process anyway
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,776
Sydney
Google Pixel 2 XL
Probably misnamed the partiton when making them. It's align_parti for sure, and not align_part

That's why it's wise to screenshot your partition table before making any modification to it.

I will soon release a tool that automates this entire process anyway

Nope, i did not misname anything :)

current partiton list for part 12:

Number Start End Size File system Name Flags

12 8381MB 8391MB 9437kB align_parti

Am aware of your tool, been a tester on TG, as well as waiting for that awesome ROM to end all ROMs from Sean :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 9
    SPECIAL THANKS TO
    @Lunarixus on XDA
    https://t.me/lunarixus_work on Telegram Posts
    I wouldn't have figured out how to maneuver the pixel 2 XL partition table without him.


    WARNING!
    This tutorial only applies to Taimen (2XL). There's already another tutorial for Walleye, click here for link. I need Walleye testers so please join the telegram group if you can! Google Pixel Development Group.
    REQUIREMENTS:
    STEPS:

    1. Enable USB Debugging

    2. Reboot into fastboot mode
    adb reboot bootloader

    3. Boot into the recovery
    fastboot boot path/to/recovery.img
    (optional) you can flash TWRP permanently if you wish. fastboot flash boot_a path/to/recovery.img and fastboot flash boot_b path/to/recovery.img DO NOT FLASH TWRP. JUST BOOT TO IT.

    4. In TWRP...
    • If it asks you to decrypt your data, do it.
    • If it asks you to swipe for RW permissions on system partition, do it.
    • Unmount all partitions. Click on Mount, then un-tick everything.

    5. Back to your PC. Copy parted to /sbin.
    adb push path/to/parted /sbin

    6. Enter shell mode.
    adb shell

    7. Change permissions of parted.
    chmod 777 /sbin/parted

    8. It's time to use parted!
    We mainly use 3 commands. Here's how they work.
    rm x - Removes partition number x. For example: rm 13
    mkpart name fstype startUNIT finishUNIT - Makes a partition where fstype is the type of filesystem (like ext4), start is the beginning of the partition, and finish is the end of the partition. UNIT is the unit for the start and finish arguments (like KB, MB, B, or s) For example: mkpart system_a ext4 32KB 1000KB
    name x part_name - Names partition number x and gives it part_name as a label. For example: name 14 userdata
    • In your terminal (still in shell mode), type parted /dev/block/sda
    • It should greet you with a welcome screen. Type p free, and save what you get in a screenshot or text file (on windows you can copy and paste in notepad, or use Snipping Tool, since it's installed by default). THIS IS VERY IMPORTANT IF YOU GET STUCK!!!!
    photo_2021-07-22_22-45-58.jpg
    • We have to delete all partitions starting from the bottom until system_a. Make sure to keep the screenshot or text file you saved earlier from p free, because we are gonna need it to recreate the deleted partitions later. YOUR PARTITION SCHEME MIGHT BE DIFFERENT THAN THIS. Make sure to STOP after system_a is removed.
      • rm 13
      • rm 12
      • rm 11
      • rm 10
      • rm 9
      • rm 8
      • rm 7
    • Once you are done, it's time to recreate those partitions. We do it in the proper order now, starting from system_a. Refer to the screenshot or text file you saved earlier. We will increase the partition size to 3GB to be able to boot most GSIs, including Android 12. If it says that the partition isn't aligned, type Ignore.
      • 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 (if you have 128GB Taimen, do mkpart userdata ext4 8391MB 126300MB)
    • Check your partitioning with p free and compare with your screenshot/text file. It should be similar, with some extra free spaces.
    • Time to name the partitions.
      • name 7 system_a
      • name 8 system_b
      • name 9 pstore
      • name 10 aes_a
      • name 11 aes_b
      • name 12 align_parti
      • name 13 userdata
    • Check your partitioning again with p free. It should show the named partitions. If everything looks good to you, leave parted.
      • quit

    9. Exit shell mode.

    exit

    10. Reboot into fastboot mode

    adb reboot bootloader

    11. Format all the partitions we made

    fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (that you downloaded earlier)
    fastboot erase system_a
    fastboot erase system_b
    fastboot erase pstore
    fastboot erase aes_a
    fastboot erase aes_b
    fastboot erase align_parti
    fastboot erase userdata
    fastboot format:ext4 system_a
    fastboot format:ext4 system_b
    fastboot format:ext4 userdata
    And that's all!

    NOTICE: At this point, the partitions should repopulate themselves on the next boot. If they don't, flash latest Android 11 stock ROM (And flash it using flash-all.bat for windows/flash-all.sh for linux) OR flash dotOS (it has a better vendor, so FP works).
    Flashing the stock ROM won't undo your partitioning. You will keep your 3GB system partition!

    You can start immediately flashing GSIs/Android 12. If you're stuck on splash screen, that means the partitions didn't repopulate correctly. Follow the advice above!

    If you need Android 12 GSI, here.

    If you have any questions, or accidentally brick your device, join the telegram group for direct support.
    2
    True, and i sure do (thats where i pulled it from), but for this users sake i was trying to be generous, maybe just once :)
    I agree with you, thank you for helping!
    2
    Or find one from the last taimen (Pixel 2XL) factory image attached to this post...saves downloading 1.6gb
    It's always better to have the full stock image in hand especially when dealing with repartitioning. You never know :)
    2
    Or find one from the last taimen (Pixel 2XL) factory image attached to this post...saves downloading 1.6gb
    2
    A lot of us managed to flash android 12 by the way. At this point 90% of bugs are fixed.

    you can try it already, if you can live with a non-working sound in calls.