Oct 2025 - Update
🧩 PCBA Update
After an extremely long journey of more than six weeks, the PCBAs have finally arrived in Kyiv, Ukraine. In our previous update, we showed that the shipment was stuck in customs for over two weeks, but in reality, customs held our package for over a month. We are happy to finally share good news and say they are now in our team’s hands. Cheers to that.
 |
 |
 |
We finally received our package for testing: 2 sets of new batteries, 3 sets of main PCBAs, 2 sets of peripheral PCBAs, 3 new screens, new cables, and new chargers. Everything is now ready to be tested. 🎉
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
After receiving the PCBAs and doing an initial review of the chips, we found several small issues that were preventing the main PCBA from turning on and functioning properly. To fix this and move forward with testing, the team made the following corrections:
(A) Added a wire between pin #18 U5 and C69, as shown in the photo:
 |
(B) Removed D23, changed R654 from 330k to 270k, and added a wire between the D23 pad and C212 pad as see in the picture below:
 |
(C) Moved resistors from R49 to R14 (0 ohm) and R27 to R32 (0 ohm), or solder drops could be used between the resistor pads instead of 0 ohm resistors:
 |
(D) Changed R74 to 51K:
 |
(E) To solve an issue with buck boost and PMIC stability, we added a 1uF capacitor between VCDT and GND, and a 330uF capacitor on the VSYS power bus
In simple terms, the PCBAs had a few small component issues that prevented power from flowing correctly and the board from turning on. Our engineers identified the problems, made the corrections by hand, and were able to get power flowing properly so the PCBA could boot.
This work took several days, but after making these adjustments to the PCBA samples, the power finally started flowing to the chip correctly and the PCBA turned on. This was great news.
We were finally at the finish line and ready to move forward. The next step was to burn our firmware and operating system onto the new PCBAs. To do this on a MediaTek chip, we need a specific authorization file that tells the chip we are allowed to install software on it, essentially saying “we are authorized, here is the key.” This file is called a DA, or Download Agent, for MediaTek. In addition to the DA file, there is also an authentication key file that confirms we have permission to flash the chip.
These same files have always worked on all of our previous PCBAs with this exact chip. However, with this new revision, both the DA and the authentication key failed, and the firmware and operating system would not burn or install. Basically, we were locked out.
 |
We did not know why this problem was happening, so we tried multiple DA files and authentication keys, but none of them worked. As we mentioned in a previous update, we discovered that the chip chosen by the Chinese team was EOL. Thankfully, months ago we were able to secure new chips from a supplier, and those chips are what we installed on the PCBAs that just arrived in Ukraine for testing.
The team could not understand why the chip would not flash, so they started to dig deeper. During their review, the Ukrainian team discovered that the chips installed on the boards were not the exact chips we ordered. The model number looked correct, except these chips had a different ending, which means the chips we received were not the correct chips, but a modified version MediaTek made for a specific customer.
The supplier never told us this, and this special version requires its own unique DA and authentication key. Without those files, the chip cannot be flashed.
This type of situation is actually common in tech. For example, an iPhone 17 Pro with 512GB storage may look identical in the United States and Europe, but the internal components can be slightly different depending on the region. It looks identical, but it is technically a different hardware version. It may use a slightly different modem or radio based on a region, but as a consumer, you would never know. That is essentially what happened here. A tiny difference in the chip version blocked us from flashing the firmware. The problem here is that we were never told about it.
When we asked the chip supplier for the files, they told us they did not have them, and when they asked their contact at MediaTek, they were told that this chip is no longer available since it is EOL and there is no support for it. Meaning they are not able to get us the files we need, and MediaTek does not answer anything regarding this chip and does not provide any files or documentation for it. They were completely stonewalled.
Since then, we have been reaching out to different PCBA factories. If any of them have worked with MediaTek and used this chip, we are checking if they have the files we need. So far, we have received several different DA files and authentication keys, but none of them have worked on our chip. Multiple factories have even asked MediaTek on our behalf, but the response has been the same each time: support for this chip is no longer available, and no files can be provided. Which is silly since we aren’t asking for support, we’re just asking for files for a chip they manufactured. They’re basically saying no and not entertaining something that would probably take them 5 min.
Due to this unfortunate circumstance the Chinese team put us in, we have had to pause the team's work until we can obtain the files we need to burn our firmware, or until we can find another solution to burn it. We are going to continue doing everything we can to get the files or purchase different chips from different suppliers.
For those wondering where we got the chips from, the chips came from suppliers who purchase EOL chips in bulk, either when a company has excess inventory or when the chips are being closed out.
This puts us in an unfortunate position, but we will continue reaching out to different vendors and suppliers to try and get these files. The challenge is that most suppliers do not have access to them, and realistically only the chip manufacturer or a PCBA factory that previously used these chips would have the files. Every time a supplier contacts MediaTek on our behalf, the answer is the same: the chip is no longer supported.
That said, we are resourceful and we will keep pushing. If we are not able to get the files, we will have to move on from the chips we purchased and source new ones, then test those instead. We know this stinks, but this is the situation in front of us and we are going to power through it because we have a great product and we need to get it into production.
As a side note, for over two years we have found it nearly impossible to get in touch with anyone at MediaTek. And when we ask a PCBA factory to share their MediaTek contact with us, they do not. Every route we have ever taken to contact them has gone unanswered.
This is very unfortunate news, and we are not happy with where things stand. Over the last two years we have worked nonstop to undo the issues left behind by the Chinese team, and in almost every area we succeeded. This chip situation is the final and most complicated piece. We are still working to get what we need so we can move forward and begin mass production. So everyone is aware, we are extremely confident we will find a solution by the next email update which will allow us to move forward. Please just hang tight!
The software, the mobile app, and the system are all at a place we are really proud of, so we are hoping this situation works out and we can move forward.
As we previously shared, we are exploring new investment opportunities to sell part of the company.
We request that you please hold back from sending individual messages about delivery dates and refunds. We will continue to provide full updates through our monthly updates, so please stay tuned. Your understanding and patience during this crappy time is greatly appreciated.
Thank you for your unwavering support.
Thanks for your support!
