The Orba arrived this morning, I was able to play with it for a bit before downloading the IOS app and being told to update the firmware. I did and after it completed the Orba will no longer turn on.
After reading about some people having success today I was hopeful and worked on my Orba again. Unfortunately nothing worked. I added Orba to the exceptions list of my firewall, turned off virus protection, and ran Orba as Administrator. No luck. Still a dead device. I updated my ticket with the information and added the log file. I sure hope they find a solution soon.
I haved a same problem.When Update firmware on Windows10 pc,
Orba doesn’t work at all.
Orba recognizes as STM Boot Loader in Device manager on Windows10.
( I had change STM32 BOOTLOADER driver to WinUSB driver by Zadig.
But it can not recognise by Orba APP in Windows10.
I found that if your orba goes totally dark while you're connected to your computer, the "shift+click" update may also fail because the device is off. Shift+clicking the update cloud will also fail if you're stuck here. Anyway, this worked for me:
Close the desktop app after you're sure it has been updated. While leaving your "dead" orba connected to the usb, hold power button and volume (-) down until you hear it "beep-boop" from windows (it will power off and unrecognize). Then do it again until you've heard the right beeps when you connect something to windows. Although the orba is still dark with no lights, you at least have it powered on in windows.
Relaunch the app and try shift+clicking the update cloud again. Mine launched and work after going through the power recycle sequence.
Hope it helps guys -
@joe Ferguson, no luck for me. To be honest that's about the (at least) tenth time I tried a power cycle. The fact that some methods work for some people but not for others, while other methods work for another group of people makes me think that there are multiple problems occurring here. Unfortunately, I don't think anything that is proposed here on the forums will be a general fix that gets everyone up and running.
Thanks for the suggestion.
Received my Orba yesterday (9/5) unboxed it (created a video and all, was so excited) played with it, then connected to my MacBook Pro and downloaded the app which updated as soon as I opened it. Once the app updated I began the firmware update. It went through the process and showed successful. I played around with it, then downloaded the app on my iPad. I FINALLY was able to connect it via bluetooth and then I created a song which wasn't much really but enough to try it out to see how it would perform. It worked just as it was supposed to. I then tried to save the song and the app locked up and finally crashed. Now if I try to open the app on my iPad it locks up immediately and is non-functional. What's worse is after turning my Orba off last night and packing it up in the Travel Case, I grab it this morning, take it out of the case and..., dead. Wha? Ok, so let's try charging it. Two hours later Orba still won't turn on. Try the steps given here and nothing. I now have a black brick that resembles a sliced grapefruit. Wow, talk about the proverbial "flash in the pan," geez. I do realize that essentially we are the beta testers for any product offered through the crowdfunding process, but damn. I don't know what's worse, getting beat by a creator and never receiving the backer reward or receiving a backer reward and it turning into a brick less that 24 hours later. What makes it even worse is having to check back here every few hours to see if someone has found a fix. I think the fix is a new firmware update and free replacement of bricked Orbas. Unless someone can find a way to get them turned on that is. Right now though nothing works, not the app, not the Orba. Both are currently buggy, dead, and useless. I'll just box it up and set it on a shelf for a few months and then try it again. Maybe Artiphon will have it all fixed by Christmas. As it is now though it's more suited for the trash bin than a shelf.
FWIW I'm an embedded systems developer familiar with the STM32Fxxx microcontroller family. DFU mode is definitely not a complete bricking. From what the logs tell me, they're in an embarrassing spot for sure, but it should be simple enough to resolve. It just takes time is all. Give them a couple weeks before throwing in the towel eh?
Thanks for the suggestion, @cynthia, but it didn't work for me. The Orba app still doesn't recognize my Orba.