AOSP 10 v222 Huawei P8 lite 2017 (PRA-LX1) bootloop

[rgcv]

Hey, been a while. Thought I'd try flashing a new custom ROM. Interestingly enough, a new patched ROM was just published.

So I've been through the hoops a couple times and I've decided to try this again. Completely factory reset the phone (Android 8.0), tried flashing the ROM using TWRP or just plain ol' fastboot. Unfortunately, I get stuck in a bootloop. Can't quite pinpoint the reason, but looking briefly at the outputs of adb logcat, it's repeatedly hitting a segmentation fault somewhere, something related to /vendor/bin/gnss_watchlssd_thirdparty, backtrace reports some stuff about the ART linker. I can append the outputs of logcat at a later time if need be. EDIT: logcat.txt

I'm not really sure if this has to do with me jumping from vendor Android 8 to AOSP 10 in one go, but it wouldn't make much sense if I had to flash it one version at a time.

[phhusson]

Yeah attach adb logcat. You have EMUI10 on that old device?

Le jeu. 6 août 2020 à 14:03, Rui Ventura notifications@github.com a écrit :

Hey, been a while. Thought I'd try flashing a new custom ROM. Interestingly enough, a new patched ROM was just published.

So I've been through the hoops a couple times and I've decided to try this again. Completely factory reset the phone (Android 8.0), tried flashing the ROM using TWRP or just plain ol' fastboot. Unfortunately, I get stuck in a bootloop. Can't quite pinpoint the reason, but looking briefly at the outputs of adb logcat, it's repeatedly hitting a segmentation fault somewhere, something related to /vendor/bin/gnss_watchlssd_thirdparty, backtrace reports some stuff about the ART linker. I can append the outputs of logcat at a later time if need be.

I'm not really sure if this has to do with me jumping from vendor Android 8 to AOSP 10 in one go, but it wouldn't make much sense if I had to flash it one version at a time.

— 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/1431, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OUP7B4P53PQ4LWDUVTR7KLYJANCNFSM4PWQKB4Q .

[rgcv]

I just rebooted the device so I could get a fresh one: logcat.txt. It's a large one and full of repetition. If you'd like an inline log in the message, please let me know.

You have EMUI10 on that old device?

No, Huawei P8 lite 2017 on Android 8.0 ships with EMUI 8.

[phhusson]

why do you say "Vendor android 10.0" then?

Le jeu. 6 août 2020 à 14:30, Rui Ventura notifications@github.com a écrit :

I just rebooted the device so I could get a fresh one: logcat.txt https://github.com/phhusson/treble_experimentations/files/5034761/logcat.txt. It's a large one and full of repetition. If you'd like an inline log in the message, please let me know.

You have EMUI10 on that old device?

No, Huawei P8 lite 2017 on Android 8.0 ships with EMUI 8.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1431#issuecomment-669897758, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4ORHMIJEPQZHVTQTYVDR7KO5DANCNFSM4PWQKB4Q .

[phhusson]

Looks like your data partition is corrupted. My easiest proposal is to factory reset from stock recovery.

Le jeu. 6 août 2020 à 14:30, Rui Ventura notifications@github.com a écrit :

I just rebooted the device so I could get a fresh one: logcat.txt https://github.com/phhusson/treble_experimentations/files/5034761/logcat.txt. It's a large one and full of repetition. If you'd like an inline log in the message, please let me know.

You have EMUI10 on that old device?

No, Huawei P8 lite 2017 on Android 8.0 ships with EMUI 8.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1431#issuecomment-669897758, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4ORHMIJEPQZHVTQTYVDR7KO5DANCNFSM4PWQKB4Q .

[rgcv]

why do you say "Vendor android 10.0" then?

I didn't, I'm sorry if I've confused you. I just expressed my concern about this issue arising because I was flashing AOSP 10 over stock Android 8

Looks like your data partition is corrupted. My easiest proposal is to factory reset from stock recovery.

I've done that once or twice now. Gone into eRecovery, restocked the device, factory reset, and flash AOSP over it. Still no good.

[phhusson]

How did you flash AOSP? Maybe you used -w parameter of fastboot? If that's the case, then that's the issue, don't use fastboot -w or fastboot format or fastboot erase

Le jeu. 6 août 2020 à 14:34, Rui Ventura notifications@github.com a écrit :

why do you say "Vendor android 10.0" then?

I didn't, I'm sorry if I've confused you. I just expressed my concern about this issue arising because I was flashing AOSP 10 over stock Android 8

Looks like your data partition is corrupted. My easiest proposal is to factory reset from stock recovery.

I've done that once or twice now. Gone into eRecovery, restocked the device, factory reset, and flash AOSP over it. Still no good.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/phhusson/treble_experimentations/issues/1431#issuecomment-669899876, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA4OSBK2ZH6WPIMWIJQGDR7KPN7ANCNFSM4PWQKB4Q .

[rgcv]

Hmm interesting. I did end up using fastboot erase, the XDA GSI flashing guide is pretty old at this point, so that could be it. Still doesn't quite explain why TWRP flashing broke as well. I'll try another reset and a proper fastboot flash ASAP.

[rgcv]

I'm afraid this isn't it. I've factory reset using stock recovery and flashed using fastboot (without erasing the partition). It seems it gets stuck regardless. It again hits a segfault multiple times, complaining about some vendor binary, but that's as far as I can get.

[bahamut657]

If it does not boot, I can suggest to you to perform the following steps in a single fastboot session:

fastboot -w (will erase all your data)

Flash Stock BOOT.img

Flash GSI ROM

Flash vbmeta ( fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img)

After all these step perform a reboot

[rgcv]

@bahamut657 Thanks for the help. Any suggestions how I should get my hand on these BOOT.img and vbmeta.img? Never really got so far as to need them.

EDIT: After some reading, I don't think flashing a custom vbmeta will help me at all. It's not that the device won't go into a boot phase, it's just that it gets stuck there. Why it is so, I can't quite tell...

I recall having been able to flash AOSP 8 and 9. I then ran into a bootloop trying 10, restocking it, trying 9 and getting into a bootloop again. At that point, I just gave up and ran stock. Until today, when I felt like giving it another try, assuming the situation had stabilized.

[bahamut657]

I also had that problem in my Cubot QUEST. But following that procedure make my device boot. For example, if I flash the GSI ROM only my device stuck in bootloop. Flashing the boot.img before (and the vbmeta.img after) make my device boot Android 10 GSI with no problem (probably this is a form of security) You can find these files in the device's manufacturer homepage. Remember to perform all the steps in a single fastboot session (if you make different step order, or reboot the device each time, it will results in NON-bootable system)

[rgcv]

You can find these files in the device's manufacturer homepage

I very much doubt huawei is just publicly handing out these files to consumers. In fact, I was lucky enough to unlock the bootloader when I did since soon after huawei stopped handing out unlock codes.

A quick search leads to unofficial posts here and there claiming some image files, except scarcely do I find specific images for my device. If I can extract them from my device in some way, I can try that procedure. Otherwise, I think I'll pass for the time being. It was yet another day I wasted on this.

[cigny61]

hello.I have the same hardware, and I always install the phhusson roms, try like this. after the rom flash go to recovery mode and format (data).