You are reading a single comment by @lunctis-viribus and its replies.
Click here to read the full conversation.
-
were all your apps up to date?
All but 4 apps were up to date
And Gadgetbridge repeatedly complained that it couldn't connect?
Yes
Did you have any other bluetooth options set like a Pin code?
Yes I have a pincode
I guess you might have hit that (but unpairing/repairing should have fixed it).
Probably, I haven't tried repairing indeed.
was that when updating using https://banglejs.com/apps/?id=fwupdate ?
Yes
I tried updating to v2.19 again (all apps up-to-date), same issue, infinite 'BOOTING...' loop again... :-(
Then I tried it again after removing the pincode and that worked.I'm now wondering whether the pincode functionality works at all?
lunctis-viribus
That's an odd one - were all your apps up to date? I think most people are using 2v19 now without issues.
And Gadgetbridge repeatedly complained that it couldn't connect? Or did you only try it once? Did you have any other bluetooth options set like a Pin code? I know we did add some code (in 2v19 I think) to ensure that if the pin pairing was requested, you couldn't communicate with the watch without the watch having been properly paired and I guess you might have hit that (but unpairing/repairing should have fixed it).
Sorry to hear that - was that when updating using https://banglejs.com/apps/?id=fwupdate ?
It can happen when using the DFU updater (especially from iOS) but it's rare it happens with the fwupdate app - at least (as you found) when it gets in that state you can update it with a DFU app