Wed Jun 12, 2019 7:48 am
Deau,
I agree to try the recovery mode first,
However, if you're still having a problem getting your phone to run either recovery or as a phone and
if your warranty has ran out (usually after 1 year of ownership) then mention here and I'll try to help you
figure out if you can get your phone back to a usable state.
P.s. a note to the blackview admin(s) however, I've noticed what seems like a firmware signing bug can cause this with signed boot images on the BV9500 in some cases.
I use the older pre-loader binary pulled out of an OTA package from 29th Aug 2018 to work around these.
Also on other brand phones, I've found a bad eMMC chip to cause similar havok, so it'd be something for your devs to think about for all future phone updates, for example, apply the updates twice before rebooting (i.e. write the boot and recovery partitions twice and verify they have written based on the SHA256 sum of those partitions and either re-write on fail or reboot on success, this should get around failing eMMC/storage)