# Bootloader 2300 not performing properly on one of my P2's

**URL:** <https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750>\
**Category:** Firmware\
**Tags:** photon\
**Created:** [November 7, 2023, 4:20pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750 "2023-11-07T16:20:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![iitgrad](https://avatars.discourse-cdn.com/v4/letter/i/9de053/32.png) [@iitgrad](https://community.particle.io/u/iitgrad)\
**Post date:** [November 7, 2023, 4:20pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/1 "2023-11-07T16:20:11Z")

</div>

I have two P2's. They both have been upgraded to 5.5.0 using the device restore tool with the Chrome browser. One P2 shows that all is well when connected. The other shows that the bootloader system-part1 is also at 5501 but has a red X next to it. I have reflashed the device forcing everything to be flashed even if it thinks it is correct, but I still get the red X.

Also, when the device boots up it goes into listening mode with a constant blue flashing led. Is this 2nd P2 damaged or am I missing something?

Here is the good P2 report

 ![Screenshot 2023-11-07 at 10.18.52 AM](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/7/4/740da7ba365787418815daccc2bdff342e1e5ef0.png)  
And here is the report from the failing P2  
 ![Screenshot 2023-11-07 at 10.18.17 AM](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/e/d/eda7e06056a2b29ce77965018b3efd9cc2a2cc80.png)

---

<div class="post-metadata">

**Author:** ![no1089](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/no1089/32/24051_2.png) [@no1089](https://community.particle.io/u/no1089)\
**Post date:** [November 8, 2023, 5:36pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/2 "2023-11-08T17:36:54Z")

</div>

[@Support](https://community.particle.io/groups/support) can you please take a look.

---

<div class="post-metadata">

**Author:** ![rickkas7](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/rickkas7/32/8681_2.png) [@rickkas7](https://community.particle.io/u/rickkas7)\
**Post date:** [November 8, 2023, 5:52pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/3 "2023-11-08T17:52:53Z")

</div>

There appears to a bug in upgrading the boot loader on the P2/Photon 2 using using [Device Restore USB](https://docs.particle.io/tools/device-restore/device-restore-usb/). It goes through the step properly, but the update does not take and the bootloader does not get upgraded.

The reason for the red x in your picture is that the bootloader was not upgraded. It was 2100 (5.3.0) and 2300 (5.5.0) is required. It's not a problem with the system-part, it's a problem with a dependency of the system-part.

I tested a Photon 2 by downgrading it to 5.3.0 using Device Restore USB. That appeared to work properly.

I then cleared the Wi-Fi credentials by long press of MODE. This is not a necessary part of upgrading, but it assures that the bootloader will not be upgraded OTA before it can be noticed.

I then used Device Restore USB to upgrade to 5.5.0 which appeared to work properly as all of the steps including the bootloader step progressed normally.

However when I used [Device Inspect](https://docs.particle.io/tools/developer-tools/device-inspect/) the boot loader was not in fact upgraded.

 ![Screenshot 2023-11-08 at 12.50.31 PM](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/2/3/23b1847a6badb165ac7af2e3720264abc6be070f.png)

My guess is that if a device has working Wi-Fi the upgrade of the bootloader happens so quickly you don't notice it happening.

Workarounds include:

- Use [setup.particle.io](https://setup.particle.io/) which uses a different technique for upgrading the bootloader
- Use the `--local` flash option in Workbench or the CLI which also uses a different technique.
- Flash the bootloader manually in `--serial` (listening mode) using the CLI.
- Enter Wi-Fi credentials so the bootloader can be upgraded OTA.

---

<div class="post-metadata">

**Author:** ![iitgrad](https://avatars.discourse-cdn.com/v4/letter/i/9de053/32.png) [@iitgrad](https://community.particle.io/u/iitgrad)\
**Post date:** [November 8, 2023, 6:54pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/4 "2023-11-08T18:54:39Z")

</div>

Thanks Rick. I will try these options you provided. As any FYI, I tried adding my wifi credentials to this device and was also unsuccessful getting the following error.

```auto
particle serial wifi --json credentials.json
! Something went wrong: Error: Resource busy, cannot open /dev/tty.usbmodem2102

```

---

<div class="post-metadata">

**Author:** ![rickkas7](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/rickkas7/32/8681_2.png) [@rickkas7](https://community.particle.io/u/rickkas7)\
**Post date:** [November 8, 2023, 6:56pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/5 "2023-11-08T18:56:34Z")

</div>

Make sure you don't have another serial connection open to the device, such as `particle serial monitor` as that will prevent `particle serial wifi` from working and cause that error.

---

<div class="post-metadata">

**Author:** ![iitgrad](https://avatars.discourse-cdn.com/v4/letter/i/9de053/32.png) [@iitgrad](https://community.particle.io/u/iitgrad)\
**Post date:** [November 8, 2023, 7:02pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/6 "2023-11-08T19:02:11Z")

</div>

My photon 2 is just connected via the usb and the firmware on board, I believe, is tinker from a previous flash. I run into this now and then in my classes with certain students and never quite understand how to fix it.

Also, using `setup.particle.io` worked great. The Photon 2 is now working properly. Thanks Rick.

---

<div class="post-metadata">

**Author:** ![rickkas7](https://sea2.discourse-cdn.com/flex026/user_avatar/community.particle.io/rickkas7/32/8681_2.png) [@rickkas7](https://community.particle.io/u/rickkas7)\
**Post date:** [November 9, 2023, 2:01pm UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/7 "2023-11-09T14:01:34Z")

</div>

Fixed a bug in Device Restore USB on the P2 and Photon 2 (RTL872x) where if both prebootloader-part1 and bootloader required an upgrade, the bootloader might not upgrade (even with the flash even if version unchanged option is set). This was most noticeable if upgrading a P2/Photon 2 to 5.3.0 with no Wi-Fi credentials so the bootloader would not upgrade OTA.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/particle/original/3X/3/2/3291e3c9351789fe8620ae5bcec8d3fec67ff221.png) [@system](https://community.particle.io/u/system)\
**Post date:** [December 10, 2023, 12:02am UTC](https://community.particle.io/t/bootloader-2300-not-performing-properly-on-one-of-my-p2s/65750/8 "2023-12-10T00:02:01Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
