The metawear app now only sees the board if the app is in metaboot mode, and if I connect, it shows the firmware update progress bar for ~10 seconds then gives an error that says "Device disconne

However, when I pressed the switch for 2 seconds, they can be identified as MetaBoot device by iOS. Only when the iOS MetaWear app started to upgrade the firmware, the sensor showed up as a MetaBoot d

iOS is the one that finally worked for me.  I basically had to get the app ready and in MetaBoot mode, then power up the board in metaboot mode.  AS SOON AS I SAW IT SCANNED, I had to tap on it and it

Try putting the board in MetaBoot mode (press the button then power up the board) then reconnect to the either app.  Once connected, attempt a firmware update.

We've also tried to set the sensor in MetaBoot mode by pressing the switch for long. However, that doesn't work.

You don't need the Debug class if the board is already in MetaBoot mode; use the API to download the latest firmware and pass the downloaded file into the Nordic DFU library.  The MetaWear app already

On the FAQ, it says that I can get out of MetaBoot mode by updating the firmware with an iOS device. Is it possible to do this with a custom Android app? I'm using MetaWear as the foundation for a con

I have two CPRO devices (one on 1.2.2) and the second one continues to function without issue. I've tried switching to METABOOT (hold switch - insert battery) to reapply the firmware update, but this

Please re-connect and try again, if you can't connect try MetaBoot Mode to recover.

I got my CPRO today and started playing around with it.  It seems great!  I kept trying all of the options, and I tried one I probably shouldn't have.  When I checked for updated firmware, it said it

I just got my new CPRO from the Kickstarter, but I can't seem to get it to work.  The MetaWear application only seems to see it while in MetaBoot Mode, but I keep getting an update error that says it

Received my C module today.  Using the latest iOS app.  Did a firmware update and got the above error message.  It went into MetaBoot, and when I try to recover it, I still get the same message.  I hi

Nevermind - figured it out - device was stuck in Metaboot

I'm sorry, I misread your last post. I tried to update the firmware via metawear android app. The update process completed but the sensor keep rebooting in metaboot. 

A metawear sensor is stuck in metaboot state after upgrade. I tried to flash the latest firmware ( http://releases.mbientlab.com/metawear/11/vanilla/1.1.3/ ) with nRF app unsuccessfully.

No...I downloaded an app called LightBlue which scans for any nearby BLE peripherals and it didn't show up there. And by enabling the MetaBoot mode switch it does not show the board on the devices lis

I have bought a MetaWear C Pro, which I have not been able to use since it is constantly in Metaboot and whenever I update the firnware it finishes and says it was successful, yet it lingers in the Re

I have also noticed with the same faulty board, if you press the button, the board with become unresponsive and you will have to disconnect, wait and try to reconnect. This happens almost all the time

Version 3.1.0 makes minor UI changes to the home panel, supports boards in MetaBoot mode, redesigns the UI for firmware updates, and has a few implementation changes.  As always, a direct download of

Also did you try to hold down the switch when plugging it into USB.  That will force MetaBoot so you can reflash the MetaWear with the MetaWear Apps.