VoLTE Implementation For Google Pixel 3a/3a XL
-
@mr_growl As I understand it, just that /data should be ext4. There is no need for repartitioning if the correct stock ROM was installed beforehand.
-
@arubislander Thanks! I flashed android 12.1 to it, so I'll just try reformatting that partition as ext4.
-
That's great news! Keep us posted how everything goes! Fingers crossed everything works correctly!
-
Did first attempt at flashing. This is on pixel 3a XL:
- flash last stock firmware (android 12.1)
- install twrp
- boot into twrp and open terminal
- umount /dev/block/dm-4 (which was mounted to /data and /sdcard)
- mke2fs -t ext4 /dev/block/dm-4
- mount /dev/block/dm-4 /data
- mount /dev/block/dm-4/sdcard
- boot into bootloader
- flasboot flash boot boot.img
- attempt to reboot into recovery
At this point the device wouldn't boot into recovery. So I'm flashing twrp back on to it.
Any thoughts?
Here's the repo I'm using: https://gitlab.com/mr-growl/ubports-ubuntu-touch-google-bonito-volte
I'm building in a ubuntu server 20.04 vm. I modified the deviceinfo from atarilinux's version slightly which got it building properly for me. -
While I was re-flashing twrp a thought occurred. With TWRP on the pixel 3a (compared to the nexus 5 and 4 which I used to use) I have to boot it using "fastboot boot twrp.img" and then use the "flash current twrp" option (taken from the lineage install instructions)... on the older phones it was "fastboot flash recovery twrp.img". Which makes me think this twrp might be writing to the same place as boot.img when I do the "fastboot flash boot boot.img". Any thoughts on that?
-
@mr_growl Why don't you formtat through the built it in option in TWRP or even better via fastboot:
fastboot format:ext4 userdata? (the partition name may differ)Also, when the block device shows up as dm-something it is encrypted.
-
@ikoz Thanks! I'll give that a go (I'm still new to a lot of this).
I was thinking it was encrypted. Seems to me that encryption is on by default in android 12 / lineage 19.1 and there isn't an option to disable it in the interface. Not sure what to do from this point.
-
@mr_growl If you disable requiring password to login (just swipe to unlock), it will also disable encryption.
But just running the fastboot command will work (if it throws any error, it likely means your fastboot build is broken and you'll have to use the official one from Google).
-
I might be off here, but did you use fastbootd? The Google Pixel 3a has retrofitted dynamic partitons in Android 12.1.
https://source.android.com/docs/core/architecture/bootloader/fastbootd
Info on Retrofitted Dynamic Partitions:
https://lucaweiss.eu/post/2023-03-30-retrofit-dynamic-partition/ -
@atarilinux I did not use or know about fastbootd. I did see it just now as I was flashing it back to stock. I'll have a read up about it.
What would help is if someone could suggest what steps I should take to flash this. Starting with stock android 12 (not even set up, just a fresh flash with all defaults) and a boot.img, system.img, dtbo.img and rootfs.img
I might not have time to test it till the weekend, though. I might try setting up a working build for sargo as well in the mean time. I can only test with bonito and the moment but I gather sargo is the more popular one around here
