search

phhusson / treble_experimentations

Notes about tinkering with Android Project Treble
3.4k stars 660 forks source link

Bootloop on Lenovo Tab M10 FHD Plus #1338

Open dyeray opened 4 years ago

dyeray commented 4 years ago

Steps:

  1. fastboot flash system system-quack-arm64-ab-floss.img (also tried vanilla). v217
  2. fastboot -w
  3. fastboot reboot

It's not A/B but its Android 9 system-as-root.

Tablet keeps rebooting. Stays on the first screen for a couple of seconds. I haven't played with GSIs before, but can follow instructions to troubleshoot.

phhusson commented 4 years ago

Don't use fastboot -w, do factory reset from stock recovery. How did you choose that variant? Did you flash vbmeta?

Le sam. 30 mai 2020 à 02:31, Domingo Yeray Rodríguez Martín < notifications@github.com> a écrit :

Steps:

  1. fastboot flash system system-quack-arm64-ab-floss.img (also tried vanilla). v217
  2. fastboot -w
  3. fastboot reboot

Phone keeps rebooting. Stays on the first screen for a couple of seconds. I haven't played with GSIs before, but can follow instructions to troubleshoot.

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

dyeray commented 4 years ago

Ups, my bad, I had no idea about vbmeta. So, now I flashed vbmeta and did factory reset from recovery, and it reaches the android logo, but keeps loading indefinitely.

How did I choose the variant: It's a new tablet, so I picked arm64, and it's A/B because Treble Info says it has system-as-root.

phhusson commented 4 years ago

Do you have adb when on android logo? If so dump logcat

Le sam. 30 mai 2020 à 12:36, Domingo Yeray Rodríguez Martín < notifications@github.com> a écrit :

Ups, my bad, I had no idea about vbmeta. So, now I flashed vbmeta, and it reaches the android logo, but keeps loading indefinitely.

So regarding factory reset from recovery, I'm still trying to find out how to start the recovery on this device... I'll keep trying and see what happens. Just in case, I did factory reset from the OS before flashing system image.

How did I choose the variant: It's a new tablet, so I picked arm64, and it's A/B because Treble Info says it has system-as-root.

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

dyeray commented 4 years ago

There you go. file2.txt

phhusson commented 4 years ago

Damn I thought that error was gone :( While the device is trying to boot, do adb shell su -c 'setprop debug.stagefright.ccodec 0'. I think it should manage to boot after that.

Please provide adb shell getprop ro.hardware so I can add it to the list of devices that requires it

dyeray commented 4 years ago

Device: mt8768.

Just for the record, the command returned an error, saying the property does not exist, but with adb shell setprop debug.stagefright.ccodec 0 it boots. Thanks!

dyeray commented 4 years ago

I flashed th latest version and there is no need for the fix. I think this can be closed and you can list this as supported devices if you like. Thanks again!

dyeray commented 3 years ago

There is a bootloop again on the latest stable version based on Android 11 (I haven't tried the alphas): v300.l. It boots if I start fastboot mode and do

fastboot erase userdata fastboot erase cache

However, after turning it off it will go to bootloop again until cleared the user/cache partitions again. Images tried:

system-roar-arm64-ab-vanilla.img system-roar-arm64-ab-vndklite-vanilla.img

Unfortunatelly, there is no adb available during boot in this case.

phhusson commented 3 years ago

Enable a lockscreen, and secure boot on first boot. I've been told it helps booting.

Le dim. 10 janv. 2021 à 17:08, Domingo Yeray Rodríguez Martín < notifications@github.com> a écrit :

There is a bootloop again on the latest stable version based on Android 11 (I haven't tried the alphas): v300.l. It boots if I start fastboot mode and do

fastboot erase userdata fastboot erase cache

However, after turning it off it will go to bootloop again until cleared the user/cache partitions again. Images tried:

system-roar-arm64-ab-vanilla.img system-roar-arm64-ab-vndklite-vanilla.img

Unfortunatelly, there is no adb available during boot in this case.

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

dyeray commented 3 years ago

You are right, having a pin to boot fixes the issue. Thanks!