After low battery status: Nexus 6P stucks in Bootloop

sagrotan · 26 Apr 2021, 15:56

Hallo,
UT was working properly for half a year on my Nexus 6P. Yesterday the battery was nearly empty. So I have connected it to the charger. After a while it seems it has rebooted on it's own and since than it stucks in a bootloop?!
I have entered the bootloader - but following options are not working: Reboot Bootloader, Recovery Mode, BP tools, Start (all are ending in bootloop)... After powering it off and start it again -> Bootloop.

It is strange - I have not done any updates in the last view days....
Maybe someone has a tip?

regards
sagrotan

AppLee · 26 Apr 2021, 16:36

@sagrotan
If the internal memory was somehow corrupted, you can try and run the installer again WITHOUT wiping the data.
I hope that's it but it could be a loose cable or anything hardware related.

Note that I don't own this device and it's just a general observation.

Lakotaubp · 26 Apr 2021, 17:36

@sagrotan Is the device charging? could the battery be on the way out. Low power can result in a failure to boot..

Rondarius · 26 Apr 2021, 18:03

@sagrotan
I have a 6P and I had to reinstall it a while back, because it wouldn't charge. Do a reinstall like @AppLee suggested. When it comes to the battery, you will get shorter running time. When I bought my phone, it turned itself off around 3-10%, I could use it for browsing the internet for about 3 hours. At the end, just before I changed the battery, it turned itself off at 60% with 30 minutes of running time. Changing the battery is not for the fainthearted.

sagrotan · 26 Apr 2021, 19:26

thanks for the replies. The battery should be okay - it was changed before 8 months or so. It was only strange, that this failure happens when the battery was nearly empty while UT was running... I will try to reinstall without wiping data ;O)

Best regards
sagrotan

flohack · 26 Apr 2021, 21:08

If you cannot boot into recovery mode then its likely you have an ageing device that suffers from the notorious CPU bug on those devices. You could try flashing TWRP to rule any UT related stuff out. Try with the normal TWRP version. If that bootloops, try this special 4-core version: https://androidfilehost.com/?w=files&flid=240199 - If that runs stable, your device has a damaged bonding with the big CPU cluster (most devices get this over time), and you can only run on the 4 little cores. Thats unfortunate, since it will mean you have to flash a special kernel and recovery each time an OTa is being published by us.

Ezio · 26 Apr 2021, 22:49

@sagrotan

As @Flohack said, try that recovery and flash this
Blod Fix
if it works then your phone is suffering from bootloop of death

sagrotan · 28 Apr 2021, 14:44

@flohack @flohack Okay, I have tryed to flash without the BLOD Workaround and than it went really wrong (Android symbol with a warning triangle with exclamation mark. Under it was written "no commands").
After that I have tryed the BLOD Workaround and the special TWRP (found on XDA-developers). Now it is working, but with my hated Google Android...

You have written, UT is working only with a special Kernel in this case... It sounds like much work for a "mobile" telephone box... but, is there a Kernel for this case to download?

Best regards

flohack · 28 Apr 2021, 14:52

@sagrotan I can build you one, its not so easy to do such things in our automated CI

sagrotan · 28 Apr 2021, 14:55

@flohack That would be great nice and phantastic ;O) !!!