View Single Post
Old 01-16-2025, 08:35 PM   #16
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
Ok, I've sent you a link for a recovery image.

First, you determine which slot you are on using ADB in the normal system. Follow these instructions, but stop if doesn't look like this. The ... is where it reboots.
Code:
C:\>adb shell
$ getprop | grep suffix
[ro.boot.slot_suffix]: [_a] -- or it might say _b
$ adb reboot edl
...
C:\>edl /lwhatever
C:\>edl /w /precovery_a rec.img -- or you might need to say _b
C:\>edl /z
...
C:\>adb shell
$ reboot recovery
...
-- You should see it boot to a white screen --
C:\>adb shell
# start ttyscreen
-- Do you see text on the screen or at least wiggly lines? --
# reboot
...
Good luck.
Renate is offline   Reply With Quote