Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

11 (and or) 13 - tulip - Stuck on splash screen #202

Open
loongruige opened this issue Sep 4, 2023 · 0 comments
Open

11 (and or) 13 - tulip - Stuck on splash screen #202

loongruige opened this issue Sep 4, 2023 · 0 comments

Comments

@loongruige
Copy link

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)
Unlock icon on top of screen, large "Redmi" text in the middle and android image at the bottom

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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant