View Single Post
Old 06-26-2023, 08:17 PM   #25
Renate
Onyx-maniac
Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.Renate ought to be getting tired of karma fortunes by now.
 
Posts: 3,973
Karma: 18026955
Join Date: Feb 2012
Device: Nook NST, Glow2, 3, 4, '21, Kobo Aura2, Poke3, Poke5, Go6
Your aboot/abl doesn't look like anything that I've ever seen.
This is the (very shortened) boot log of my Poke3:
Code:
B -   2104744 - SBL1, End

...

LoadBitmapImage name[logo1.bmp] size[88860] at Buffer[9AC3C018]
Render Splash  [ 4536]
lcd_display_bitmap(): Display bmp: 139 x 627  with 256 colors at pos(654 222)
bmp_bpix = 8, compression = 0, fb bpix = 16
xpos[654] ypos[222] xact[139] yact[627]

...

PON Reason is 0x415C3411 cold_boot[1] PON1[0] KPDPWR[0] USB[1] DC[0]. [5249 ms]
KeyPress:0, BootReason:0
Fastboot=0, Recovery:0
This is a very typical sort of thing on many devices.
There has always been this little showing of keypress or touch.
You could reboot and try any silly thing that you could think of to get some value to change.
Some things worked with screen touches, buttons or UART.

It could be that your device has a corrupted aboot/abl.
It could be that they all are like that now.
Renate is offline   Reply With Quote