Unmentioned in my original post -
The process also sets a re-try time delay (maybe 9 hours, I wasn't watching closely enough).
So I think one solution would be to JBpatch the re-try time delay constant - -
To something like 100 years or so.
= = = = =
Anyway -
This is getting hard to keep track of -
What it would probably take is a Wiki table, for firmware "xyz" use method "abc".
Note: This was on a KT3 running 5.8.5 firmware.
I think my retry delay should have timed out now, I'll try another idea or two and see if Amazon turns my KT3 into trash.