# XStick Bricked?

**URL:** <https://forums.digi.com/t/xstick-bricked/399>\
**Category:** XBee - Zigbee\
**Created:** [November 25, 2010, 1:15am UTC](https://forums.digi.com/t/xstick-bricked/399 "2010-11-25T01:15:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dynamolabs](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@dynamolabs](https://forums.digi.com/u/dynamolabs)\
**Post date:** [November 25, 2010, 1:15am UTC](https://forums.digi.com/t/xstick-bricked/399/1 "2010-11-25T01:15:00Z")

</div>

After using X-CTU to install the XB24-SE profile for a ZIGBEE SE END DEVICE API, with updated firmware, the XStick reset.

Now, when it’s plugged in (and after the reset) an amber light stays solid and it is not responding normally in any tool (including X-CTU).

When I’m on the PC Settings tab and click Test/Query:

Communication with modem. OK  
Modem type = Name unknown (ID = 42949672481228512)  
Modem firmware version =

On the Modem Configuration screen, when I try to READ the parameters I get:

Failed to enter command mode  
Unable to read Version (ATVR)  
Read parameters. Failed.

On the Modem Configuration screen, when I try to WRITE parameters:

Getting modem type…OK  
Programming modem… Lost communication with modem  
Write Parameters…Failed.

I can’t figure out how to get the stick to respond, it feels like it’s bricked or in a state where it’s not letting in commands.

---

<div class="post-metadata">

**Author:** ![dynamolabs](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@dynamolabs](https://forums.digi.com/u/dynamolabs)\
**Post date:** [November 25, 2010, 1:16am UTC](https://forums.digi.com/t/xstick-bricked/399/2 "2010-11-25T01:16:43Z")

</div>

Also, when I use the In-Premise Display / Meter Simulator

I switch the Baud rate to 9600, select COM3 (the correct port), and Open COM Port.

I see at the bottom:

Failure on serial port: COM3 - ddo\_get\_param: error fetching DDO parameter

---

<div class="post-metadata">

**Author:** ![dynamolabs](https://avatars.discourse-cdn.com/v4/letter/d/f4b2a3/32.png) [@dynamolabs](https://forums.digi.com/u/dynamolabs)\
**Post date:** [November 26, 2010, 5:51pm UTC](https://forums.digi.com/t/xstick-bricked/399/3 "2010-11-26T17:51:20Z")

</div>

Well I fixed it, via button mashing hack.

I brought up X-CTU… unplugged the XStick, started to button mash the write button to hopefully catch the XStick before it gets itself stuck… and plugged it in. Gave it a whirl and it worked.