(03-May-2023, 10:59 AM)ShaneG057 Wrote: Sheesh... Its things like this that make me not want to update the code in my RealDoll(TM).

Oh man you just killed me. Fantastic. Just have to clean my dinner from the wall where it ended up after i read this with my mouth full.

The latest official Fix just came in.

Quote:[The update is ready to download!]

DOWNLOAD NEW FIRMWARE (https://orqafpv.com/downloads)
Please follow the procedure;

Orqa FPV.One (V1) unbrick procedure

First, make sure to format your SD card.

Next, unzip the ONE_V1.zip folder on the root of your SD card. Then, turn on your goggles, and once they've powered up, insert the SD card in the goggles. You’ll hear some beeps and goggles will turn off automatically after a few seconds. Then, turn on the goggles again and wait for the update process to complete. Once the update is finished, the goggles will restart automatically - once that happens, make sure to format your SD card and you're all done!

IMPORTANT NOTE: If the update process is taking longer than 5 minutes, make sure to repeat all the mentioned steps at least once or twice before contacting Orqa support, since the procedure has already been tested on V1/V2/Race models of the goggles.

Orqa FPV.One Pilot (V2) Unbrick Procedure
 
First, make sure to format your SD card.

Next, unzip the ONE_V2.zip folder on the root of your SD card. Then, turn on your goggles, and once they've powered up, insert the SD card in the goggles. You’ll hear some beeps and goggles will turn off automatically after a few seconds. Then, turn on the goggles again and wait for the update process to complete. Once the update is finished, the goggles will restart automatically - once that happens, make sure to format your SD card and you're all done!



IMPORTANT NOTE: If the update process is taking longer than 5 minutes, make sure to repeat all the mentioned steps at least once or twice before contacting Orqa support, since the procedure has already been tested on V1/V2/Race models of the goggles.



Orqa FPV.One Race Unbrick Procedure

First, make sure to format your SD card.

Next, unzip the ONE_RACE.zip folder on the root of your SD card. Then, turn on your goggles, and once they've powered up, insert the SD card in the goggles - 10 seconds after you’ve inserted the SD card, make sure to turn off your goggles manually by pulling out the battery! Then, turn on the goggles again and wait for the update process to complete. Once the update is finished, the goggles will restart automatically - once that happens, make sure to format your SD card and you're all done! 

IMPORTANT NOTE: If the update process is taking longer than 5 minutes, make sure to repeat all the mentioned steps at least once or twice before contacting Orqa support, since the procedure has already been tested on V1/V2/Race models of the goggles.

Be aware that quite a few people are reporting that the "fix" isn't working on their V1 goggles. See the comments under the Facebook post linked to below. I guess the beta testing yesterday didn't go as well as it could have done.

https://www.facebook.com/groups/64223506...1497472675

Well the plot thickens. In each of the new Orqa firmware ZIP files is a license subfolder containing a "repair.bin" file. This is the license file for the bootloader firmware which contains an expiration date. I've just done a binary file compare of the "repair.bin" license files in each of the Orqa released firmware files, and their contents are identical to the "update.bin" license files that SWARG posted a few days ago (see post #2 in this thread) which SWARG stated would extend the bootloader licence until July 2023. And these are the files that Orqa told users NOT to install because they contained malware and would void any warranty on the goggles.

So what on earth is going on? Orqa don't appear to have fixed / changed anything with the bootloader firmware themselves at all (which is a separate firmware to the main goggles firmware) and just appear to have issued exactly the same bootloader license files that SWARG did (except named "repair.bin" inste4ad of "update.bin") to extend the license date. Maybe that is all they have actually done and the new 3.4.0 firmware on top of that then just sets the RTC date back to the past and prevents it being set to 29th April 2023 or later. Can anyone who has successfully applied this "fix" confirm if that is the case or not? What is the RTC date showing as in the goggles after flashing this "fixed" firmware, and can it be changed?

There definitely seems to be some smoke and mirrors coming from Orqa, but they're not exactly known for their transparency.

EDIT: Some other people have found the same. It's being discussed on Facebook at the link below...

https://www.facebook.com/groups/64223506...097467515/

It’s hard to say what is happening between Orqa and Swarg.
 Here shortly I will try the firmware fix and see what happens on my Pilots which I haven’t turned on since the middle of last month.
  Right now it’s very important for Orqa to get their goggles fixed for they are very popular with the racers.I think Orqa are the most used goggles for racing.
   I hope Orqa V1 goggles gets the fix working for all goggles.

 Swarg did say they have codes written so it could happen in the future up until 2025 depending on the date of manufacture.

    I’ll post my results shortly after I get my goggles updated which should be within an hour or two.

Yeah, the main thing here is that people have their goggles back in a working state so they can fly with a product they paid good money for, but Orqa certainly don't help themselves with some of the BS they appear to have been spewing. Now that people have figured out that Orqa have simply just supplied the same unchanged license files that SWARG themselves posted a few days ago it makes you wonder what they have spent the last 5 days actually doing. Maybe Orqa are just using those original SWARG license files to buy themselves some time while they work on a proper solution between now and July, but they are starting to make people question their honesty and integrity.

One thing is for sure. There never seems to be a dull day in the world of FPV 

I got mine updated and working properly with today’s date.

 Hopefully Orqa removed the codes for good.

 I had to power cycle mine after the last step because the firmware wasn’t downloading and stuck at 0% for over 10 minutes.
 Then it went per directions and seems to be working properly with the current date.

   I guess if a person really wanted to avoid the headaches is to do the tear down,jump the pads,and do not set the RTC.
  10 years from now if Orqa isn’t in business I’d still want goggles to work,given analog still exists which I think it will.
According to Swarg there’s more codes written for dates up until 2025.
I’d hate to turn on googles later and see that F monkey wearing a helmet.

Orqa are claiming that they have used the original SWARG files to get them into the system so they can then replace the SWARG bootloader with one of their own. See the Facebook post linked below...

https://www.facebook.com/groups/64223506...5447457280

Maybe that is true and maybe it isn't. Only Orqa knows the real truth but the fact is that they weren't transparent about the use of those files, previously stating they contained malware but now happy to use them for their own solution while failing to disclose that until they were found out. Not to mention all their promises and drip-feeding information to customers who paid $600 for a product that suddenly stopped working. It's completely understandable that people are upset and sceptical.

Someone at that company really needs to go on a PR training course.

So the question still remains that if they needed to use the original SWARG files to unlock the bootloader, those files still have a license expiration date of 1st July 2023, so what if people do not perform this procedure before 1st July for some reason? And what about goggles still sitting in vendor stock cupboards?

I also don't personally believe that Orqa have written a brand new bootloader from the ground up and tested it properly in just 4 days. Call me cynical but something still doesn't smell right to me. I wish Orqa would stop spinning so much deception and lies then maybe people would start to trust them a bit more. Which reminds me, where is the digital system they promised us nearly 18 months ago?

(04-May-2023, 05:58 PM)SnowLeopardFPV Wrote: Orqa are claiming that they have used the original SWARG files to get them into the system so they can then replace the SWARG bootloader with one of their own. See the Facebook post linked below...

https://www.facebook.com/groups/64223506...5447457280

Maybe that is true and maybe it isn't. Only Orqa knows the real truth but the fact is that they weren't transparent about the use of those files, previously stating they contained malware but now happy to use them for their own solution while failing to disclose that until they were found out. Not to mention all their promises and drip-feeding information to customers who paid $600 for a product that suddenly stopped working. It's completely understandable that people are upset and sceptical.

Someone at that company really needs to go on a PR training course.

So the question still remains that if they needed to use the original SWARG files to unlock the bootloader, those files still have a license expiration date of 1st July 2023, so what if people do not perform this procedure before 1st July for some reason? And what about goggles still sitting in vendor stock cupboards?

I also don't personally believe that Orqa have written a brand new bootloader from the ground up and tested it properly in just 4 days. Call me cynical but something still doesn't smell right to me. I wish Orqa would stop spinning so much deception and lies then maybe people would start to trust them a bit more. Which reminds me, where is the digital system they promised us nearly 18 months ago?

I asked almost the same question in the Orqa Owners Lounge facebook page.
Joshua Bardwell commented this:

Quote:I tested this by setting my goggles to 2024. The fix did not work. The workaround for the V2 goggles at least, was to open up the goggles and bridge the bootloader pads, then update firmware using the original method that was posted earlier this week. After that, the goggle date was set back to 2021 and I could then use the newer method to complete the fix.

For V1 goggles, I don't know.

So as far as I understand this isn't a "fix" as orqa is calling it. As soon as July 1 comes around they will need to come up with something else.


Wish they didn't leave us in the dark like this

(04-May-2023, 09:23 PM)apple010 Wrote: I asked almost the same question in the Orqa Owners Lounge facebook page.
Joshua Bardwell commented this:

So as far as I understand this isn't a "fix" as orqa is calling it. As soon as July 1 comes around they will need to come up with something else.

Wish they didn't leave us in the dark like this

Well JB's answer pretty much confirms what we suspected. As long as no-one has inadvertantly set the date in their goggles to something greater than 1st July 2023 the "fix" will work, otherwise you are either left having to open the goggles up to get to the bootloader two test point pads, or if you have a pair of V1 goggles then you are totally screwed. I don't see Orqa make any reference to that important piece of information anywhere in their unbricking instructions.

For anyone interested, the Facebook post being referred to that contains JB's reply is HERE.

I see that Tony has answered your post with the usual smoke and mirrors reply. I don't believe they have replaced the original SWARG bootloader with one of their own and I don't buy their story about the bootloader code being encrypted apart from the one piece of code in it which happens to do the date check. How convenient. Orqa must think their customers are all a complete bunch of idiots to believe that farfetched BS. The best intelligent guess I can come up with is that they have used the original SWARG licence files (the ones with the supposed malware in them) to gain access to the goggles so they can then flash new google firmware (not to be confused with the separate bootloader firmware) which now probably sets the internal RTC to a date way back in the past (i.e. 1st January 1700) and then just applies an offset to that date for the UI of the main goggle firmware and the DVR files to bring it up to up to the current date (i.e. forward 3 centuries). The real (hidden) underlying RTC date which is way back in the past will then never get anywhere near the expiry date that the (still installed) SWARG developed bootloader is looking for.

I should probably stop bashing Orqa but I haven't seen a single sincere apology from them about this whole charade. They just seem to be more concerned about directing the blame elsewhere than apologising. I wouldn't be at all surprised if Orqa knew about the license expiry but just totally forgot to issue new firmware before that happened and have ended up being caught with their pants down. Then they try to proclaim themselves as heroes and miracle makers for "fixing" an issue that should never have occurred in the first place if they had actually bothered to have sufficient due diligence as part of their software practices. It used to be FatShark who was the laughing stock of the FPV world but I think Orqa have probably now taken that crown.

I’m curious if anyone will try changing to a later date to see if there are any other date codes for bricking goggles.
 Swarg did say they have dates scattered until 2025 for the same thing to happen.

  From what I understand nothing has been changed in the codes from what Swarg had posted which only works until July 2023.
 A simple test is to change the date to after July 2023 and then 2025 and see what happens.
 If they brick up Swarg statement about the extension and other dates is true and Orqa saying they are fixed is false.

(05-May-2023, 02:17 AM)Rob3ddd Wrote: I’m curious if anyone will try changing to a later date to see if there are any other date codes for bricking goggles.
 Swarg did say they have dates scattered until 2025 for the same thing to happen.

  From what I understand nothing has been changed in the codes from what Swarg had posted which only works until July 2023.
 A simple test is to change the date to after July 2023 and then 2025 and see what happens.
 If they brick up Swarg statement about the extension and other dates is true and Orqa saying they are fixed is false.

Someone already tested changing the date to 2099 and their goggles continued to boot without issues. The real test would be to set them to the maximum date possible (31/12/9999 if allowed) and see what happens, but only people with the Orqa FPV.One Pilot (V2) or FPV.One Race goggles should try doing that because if it goes wrong then at least they have a fallback option of opening the goggles and shorting the two test pads to bypass the bootloader check, and it should be done before 1st July 2023 because that is the only date up until which the Orqa "fix" can use the SWARG license extension files to unlock the bootloader. Any V1 goggle users should NOT try this because there is no fallback option for those if something goes wrong.

The 2023 and 2025 SWARG extension dates don't matter. If Orqa have just done what I suggested in the 3rd paragraph of post #25 with a date offset for the UI then the internal RTC will never reach 2023 or 2025, or maybe not even 9999.

Another interesting thing to note here is that if SWARG hadn't published those license extension files then Orqa would have been up creek without a paddle because it was only the existence of those files that allowed them to create a "fix". It is still sh*tty what SWARG did to cause customer hardware to end up being soft bricked, but Orqa certainly aren't free of blame here because they were the ones who let it happen in the first place.

The only way we would ever know the real truth as to how Orqa really "fixed" the issue is if they make their firmware open-source, but they will never do that (not now anyway) because then the proof will all be there in black and white that they've been lying to people.

(04-May-2023, 02:14 PM)SnowLeopardFPV Wrote: Well the plot thickens. In each of the new Orqa firmware ZIP files is a license subfolder containing a "repair.bin" file. This is the license file for the bootloader firmware which contains an expiration date. I've just done a binary file compare of the "repair.bin" license files in each of the Orqa released firmware files, and their contents are identical to the "update.bin" license files that SWARG posted a few days ago (see post #2 in this thread) which SWARG stated would extend the bootloader licence until July 2023. And these are the files that Orqa told users NOT to install because they contained malware and would void any warranty on the goggles.

So what on earth is going on? Orqa don't appear to have fixed / changed anything with the bootloader firmware themselves at all (which is a separate firmware to the main goggles firmware) and just appear to have issued exactly the same bootloader license files that SWARG did (except named "repair.bin" inste4ad of "update.bin") to extend the license date. Maybe that is all they have actually done and the new 3.4.0 firmware on top of that then just sets the RTC date back to the past and prevents it being set to 29th April 2023 or later. Can anyone who has successfully applied this "fix" confirm if that is the case or not? What is the RTC date showing as in the goggles after flashing this "fixed" firmware, and can it be changed?

There definitely seems to be some smoke and mirrors coming from Orqa, but they're not exactly known for their transparency.

EDIT: Some other people have found the same. It's being discussed on Facebook at the link below...

https://www.facebook.com/groups/64223506...097467515/

The second I unzipped the "fix" archive and saw the license folder I suspected it contained the Swarg file. My v1s have been down since the beginning of my second session on brick day and it's had a major impact on my flying. This is not a unique experience among orqa owners. However, V1 owners were left completely out of the conversation in most threads/videos. I haven't subjected my self to FB for many years now, and the little taste I got on orqas page was a strong reminder (of why I left) that I didn't need. I would give orqa all the slack they needed in the event of such an error, if they were forthright about it, because mistakes happen, but the deception, clamoring to save face, and shameless shilling have turned me off entirely. I really enjoy flying with my v1s and will continue to use them, but it is extremely unlikely I will ever buy anything orqa again.

More importantly, Snow, I want to express my gratitude for your integrity as you've followed this debacle, providing prompt, useful information in a far more organized and accessible format. From Ytube to Fbook all I found was people shamelessly shilling for orqa, congratulating them on their "quick/awesome/tremendous/" response to the issue, and thanking them for a fix that didn't even exist yet. Also, the fact that Swarg openly used their official logo for the "bricked" bootloader screen is, in my experience, not consistent with the general approach of "ransomware/malware," as orqa called it. Nobody that's behind real ransomware is saying, give me $xxxxx if you want access again, and oh, by the way, here is exactly who, what, and where I am." Then, seeing that orqa used the Swarg file after threatening to void warranties for anyone that used it is just over the top. I could have been flying analog again days earlier. Anyway, I'm going to try the "fix" from orqa now. It will be nice to have my goggles back.

Yes, the longer this has gone on the more suspicious the whole "ransomware" claim seems to have become. While implementing a time-bomb that soft bricks end consumers products through no fault of their own is a strange way for SWARG to try and enforce licensing renewals on a manufacturer (Orqa), it does now seem more plausible to me that there was probably some kind of contract between Orqa and SWARG for licensing the bootloader which Orqa either just forgot about or which they failed to honour.

Orqa have stated more than once that they have started legal action against SWARG with strong words like police, arrest, and prison being thrown around, but I wouldn't be surprised if that turns out to be another lie to try and deflect any blame away from Orqa. I will wait with bated breath to hear more about this apparent lawsuit and what the outcome is, but I would probably bet money on the fact that it will all just end up going silent and we won't hear anything more about it. I guess we'll find out in due course if I'm right or wrong.

If a bootloader license contract does exist, with Orqa having written code to purposely bypass that license, they themselves could now actually find themselves on rocky ground from a legal perspective with the tables turned.

People are still reporting issues when trying to apply the "fix" but there has been radio silence from Orqa since Thursday with users just left trying to help each other out to try and find a solution. So it looks like we are back to the whole bizarre Orqa PR setup.

The incident caught the attention of Louis Rossmann