View Single Post
Old 02-10-2020, 12:56 PM   #20
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Well, if you can't read the serial output because of transmission issues, you can't really tell what's happening ;o).

In any case, IIRC, the actual force downgrade procedure on devices where the OTA updater rejects downgrades, but not the initrd updater, is to *NEVER* unplug the USB side of things. Just let it sit to hope the file has been flushed to storage properly, and then hard-reboot.

That's (probably) ridiculously easier if you have serial access, because you can sync && reboot manually. But then you can just flash it manually from diags in the first place.

But that's not even exactly what's happening here, since that's not the OTA updater, that's the initrd's recovery menu.

(i.e., you shouldn't have to jump through any hoops here).

Last edited by NiLuJe; 02-10-2020 at 01:01 PM.
NiLuJe is offline   Reply With Quote