Bug description
After a GSI from an OEM rom has been generated using the script, the device fails to get past the bootloader with no bootloop
To reproduce
1 - Patch GSI using script
2 - Wipe userdata and system using Fastboot
3 - Flash vbmeta image using Fastboot
4 - Flash boot image using Fastboot
5 - Flash system image using Fastboot
6 - Boot into TWRP using Fastboot
7 - Flash Permissiver V5 using TWRP
8 - Reboot to system
Expected behaviour
The expected behaviour is for the device to get past the splash logo and boot into Android (or at least go to the boot animation)
Screenshots
Device is stuck in this screen: (I apologise for the poor image, but taking screenshots in the bootloader is not possible)
Logs
I apologise very much if this is not the correct log file, but since it's not possible to boot into anything, this is the only boot log I could access. Please enlighten me if there is any other accessible log I can provide.
dmesg.log
Smartphone information:
- Device: Xiaomi Redmi Note 6 Pro
- Vendor: Lineage 18
- Version: Q
Additional context
The tested OEM GSIs are:
- BLU G91S Android 11 Stock ROM
- LAVA Agni 2 Android 13 Stock ROM
I've tried to generate both by using url2GSI and extracting System myself but both of them give the same situation
Both the source ROMs are A/B and the device is Aonly, but I have prompted to build Aonly GSI in the script (The behaviour of A/B flashing to Aonly is different)
Bug description
After a GSI from an OEM rom has been generated using the script, the device fails to get past the bootloader with no bootloop
To reproduce
1 - Patch GSI using script
2 - Wipe userdata and system using Fastboot
3 - Flash vbmeta image using Fastboot
4 - Flash boot image using Fastboot
5 - Flash system image using Fastboot
6 - Boot into TWRP using Fastboot
7 - Flash Permissiver V5 using TWRP
8 - Reboot to system
Expected behaviour
The expected behaviour is for the device to get past the splash logo and boot into Android (or at least go to the boot animation)
Screenshots
Device is stuck in this screen: (I apologise for the poor image, but taking screenshots in the bootloader is not possible)
Logs
I apologise very much if this is not the correct log file, but since it's not possible to boot into anything, this is the only boot log I could access. Please enlighten me if there is any other accessible log I can provide.
dmesg.log
Smartphone information:
Additional context
The tested OEM GSIs are:
I've tried to generate both by using url2GSI and extracting System myself but both of them give the same situation
Both the source ROMs are A/B and the device is Aonly, but I have prompted to build Aonly GSI in the script (The behaviour of A/B flashing to Aonly is different)