Flashing with RF Connect

[ronaldheld]

I cannot flash 1.9.0. it stops at 13%  I tried 1.8.0 and got the same results.  Is this due to recent updates to RF Connect?

[ITCactus]

I cannot flash 1.9.0. it stops at 13%  I tried 1.8.0 and got the same results.  Is this due to recent updates to RF Connect?

it could be you experience this issue... 
if it's on android, try Gadgetbridge app (or Siglo on linux),

and like JF002 suggested, 

So, as other said, reboot your watch between every attempts, try with another phone/computer and another companion app and, if possible, analyze and debug to find out why the transfer failed and how we could improve the code ;-)

Also, note that most of the companion app will only accept the DFU (.zip) file, while Amazfish only supports the image (.bin) file.

[ronaldheld]

I have replaced RF Connect by Gadgetbridge.  I cannot see the option to flash firmware.

[ITCactus]

I have replaced RF Connect by Gadgetbridge.  I cannot see the option to flash firmware.

you can find "Updating InfiniTime" instructions here, and dedicated for Gadgetbridge here.
also, you may find video tutorials on youtube.

[ronaldheld]

I have replaced RF Connect by Gadgetbridge.  I cannot see the option to flash firmware.

you can find "Updating InfiniTime" instructions here, and dedicated for Gadgetbridge here.
also, you may find video tutorials on youtube.

Thanks for the instructions. My problem was not in the procedure, but using Astro file Manager. When I used the Samsung file manager, I was able to flash the firmware. Should I have a boooader version of 0.0.0?

[wibble]

I guess it depends what you mean by 'should' ;-) If I go to the menu on InfiniTime 1.9.0 and pick About it tells me I have bootloader 0.0.0 while if I reboot with a long button press the bootloader tells me it's V1.2.3. I think my bootloader is actually a late release candidate from testing shortly before the 1.0.0 bootloader release, but I'd have to check my notes. The releases and update instructions are here:
https://github.com/InfiniTimeOrg/pinetim...r/releases

If the back is glued on I'd stick with the bootloader that's installed.

[ITCactus]

for me, the About screen on sealed PineTime shows "1.0.0". the same on bootloader screen with triangular pine (v 1.0.0).
unsealed one, where i accidentally flashed the app directly using SWD flasher, that overridden all the content (incl. bootloader, i guess), i have "0.0.0", and i can not reboot the PineTime or do an OTA update. therefore this topic has been created.

there is a Video showing what the InfiniTime 1.0.0 bootloader looks like
@ronaldheld, do you see exactly the same on rebooting PineTime?

regarding "ASTRO File Manager & Cleaner", just tried, and i can confirm some issue - for me Gadgetbridge app ends up with "element cannot be installed" when sharing the file for update. so i can not use that file manager for updates.

[ronaldheld]

@ITCactus, I only see the about screen when I hold down the button.

[ITCactus]

@ITCactus, I only see the about screen when I hold down the button.

keep holding. after about 7-10 seconds it should either reboot and display the pinecone (bootloader, if you still have it),
or resets (dark screen for a second) and display the watchface (in that case it could be a sign you have no bootloader).

[ronaldheld]

@ITCactus, I only see the about screen when I hold down the button.

keep holding. after about 7-10 seconds it should either reboot and display the pinecone (bootloader, if you still have it),
or resets (dark screen for a second) and display the watchface (in that case it could be a sign you have no bootloader).

I did what you said to do. I got a white or light green pinecone. It eventually changed colors and the firmware came up. But it was 1.8.0 not 1.9.0. I declined the validation, and after another boot reverted to 1.9.0. what is going on?