Open vyktorjonas opened 5 years ago
Fwiw, the very first generic guide about flashing gsi I know of is XDA's, and it does mention vbmeta. Does my pie gsi boots fine on it?
Le ven. 15 nov. 2019 à 01:35, vyktorjonas notifications@github.com a écrit :
It won't boot at all after using the generic instructions (boot fastboot, wipe system then flash new system), if I flash vbmeta.img after flashing the ROM, it boots but gets stuck on bootanimation. logcat2.txt https://github.com/phhusson/treble_experimentations/files/3849264/logcat2.txt I got this logcat from adb with vbmeta flashed over the 10.0 ROM.
Chipset | Mediatek MT6771 Helio P70M (12nm) CPU | Octa-core (4x2.1 GHz Cortex-A73 & 4x2.0 GHz Cortex-A53) GPU | Mali-G72 MP3
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/910?email_source=notifications&email_token=AAAA4OTVIIXQNYWVYU324NDQTXVFFA5CNFSM4JNTW4TKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HZPGD4Q, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OUGYGIXA6ZGMM6JWOLQTXVFFANCNFSM4JNTW4TA .
Also which gsi version is that? It seems to be rather old
issue could be
01-01 00:47:27.302 0 0 I init : [libfs_mgr]__mount(source=/dev/block/platform/bootdevice/by-name/prodpersist,target=/mnt/product/persist,type=ext4)=-1: No such file or directory 01-01 00:47:27.302 0 0 E init : [libfs_mgr]Failed to mount an un-encryptable or wiped partition on /dev/block/platform/bootdevice/by-name/prodpersist at /mnt/product/persist options: noauto_da_alloc,commit=1,nodelalloc: No such file or directory
Le ven. 15 nov. 2019 à 01:35, vyktorjonas notifications@github.com a écrit :
It won't boot at all after using the generic instructions (boot fastboot, wipe system then flash new system), if I flash vbmeta.img after flashing the ROM, it boots but gets stuck on bootanimation. logcat2.txt https://github.com/phhusson/treble_experimentations/files/3849264/logcat2.txt I got this logcat from adb with vbmeta flashed over the 10.0 ROM.
Chipset | Mediatek MT6771 Helio P70M (12nm) CPU | Octa-core (4x2.1 GHz Cortex-A73 & 4x2.0 GHz Cortex-A53) GPU | Mali-G72 MP3
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/910?email_source=notifications&email_token=AAAA4OTVIIXQNYWVYU324NDQTXVFFA5CNFSM4JNTW4TKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HZPGD4Q, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OUGYGIXA6ZGMM6JWOLQTXVFFANCNFSM4JNTW4TA .
I followed XDA's instructions, it mentioned flashing this VBA for the Pixel 2 in case it doesn't boot, which was my case, with this VBA I managed to see the bootanimation, without it my phone bootlooped between the moto logo then the bootloader unlocked warning over and over, I didn't flash permissive zip or anything cuz my phone isn't support by TWRP yet and the guides didn't mention it. I tried both the latest Android 10 GSI and Android 9 GSI This VBA: https://drive.google.com/open?id=1ifnXCIdkqKnk_a1HII9RqQd5CVFWz1xR found here: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
I used system-quack-arm32_binder64-ab-gapps.img, as the app told me to
Ok but which version?
Le ven. 15 nov. 2019 à 11:43, vyktorjonas notifications@github.com a écrit :
[image: IMG_0903] https://user-images.githubusercontent.com/57778484/68937684-975c4580-077b-11ea-9dd4-18418327f8e6.jpg I used system-quack-arm32_binder64-ab-gapps.img, as the app told me to
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/910?email_source=notifications&email_token=AAAA4OTBVDHJ6QDRT7F4HBTQTZ4ORA5CNFSM4JNTW4TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEFBU4Q#issuecomment-554310258, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OTGKYMV4YT7EN7NIHLQTZ4ORANCNFSM4JNTW4TA .
the latest build of android 10 (201) and also tested the latest of android 9 as of yesterday
Please try again with v206
Also please provide the result of ls /dev/block/platform/bootdevice/by-name/
or ls /dev/block/bootdevice/by-name/
is that fails
Please also attach /vendor/etc/fstab.xxxx
so sorry but I actually sold the phone (because of this issue in fact)
No problem, we'll leave this issue for the next courageous soul
It won't boot at all after using the generic instructions (boot fastboot, wipe system then flash new system), if I flash vbmeta.img after flashing the ROM, it boots but gets stuck on bootanimation. logcat2.txt I got this logcat from adb with vbmeta flashed over the 10.0 ROM.
Chipset | Mediatek MT6771 Helio P70M (12nm) CPU | Octa-core (4x2.1 GHz Cortex-A73 & 4x2.0 GHz Cortex-A53) GPU | Mali-G72 MP3