Can i get DXOCARD_3.2.0.ecef5ef809.BIN?

[hanrw]

I have an issue with my dxo one which couldn't connected to my Iphone I want upgrade firmware manually to see if working or not. Thx.

[xzczcz]

这真的是电池问题，我换了电池，现在脚本似乎可以工作（更新时取景器黑屏）这是导入第九 （9） 个的日志log.zip

现在它失败了，固件接头再次失败，并显示“SD卡错误”。我只能在这里推测，这是script-9中的正确文件吗？，也许驱动器没有正确弹出？

1. 您可以尝试修复PC上的SD卡吗（大致：右键单击驱动器号，[属性]，选项卡[工具]，[检查错误]）
2. 您是否有另一张SD卡可以放置文件，使用外部SD卡读卡器可以在PC上正确弹出？
3. 您可以在没有 SD 卡的情况下重试（只有 .ash 文件和 ）吗？AmbaUpdaterFW.bin``AmbaSysFW.bin

CardUp_LoadFWHeader:FW file not exists
CardUp_IsFileValid:load fw header fail
Not Allow to Add Event!!!
[USB TEST](80) {"token":4660, "msg_id":7, "type":"FW_VALID_COMPLETE", "param":"SD_CARD_ERROR"}
_UpgradeFail(-11)

Yes, I changed an sd card and tried again without putting AmbaUpdaterFW.bin in the sd and running it once (the viewfinder shows a black screen after long pressing the shutter) Here is the log of the re-attempt (9)log.zip

[rickdeck]

Yes, I changed an sd card and tried again without putting AmbaUpdaterFW.bin in the sd and running it once (the viewfinder shows a black screen after long pressing the shutter) Here is the log of the re-attempt (9)log.zip

Hm ok. Same error... [USB TEST](80) {"token":4660, "msg_id":7, "type":"FW_VALID_COMPLETE", "param":"SD_CARD_ERROR"}

Maybe this method also doesn't work for your device...

[rickdeck]

Yes, I changed an sd card and tried again without putting AmbaUpdaterFW.bin in the sd and running it once (the viewfinder shows a black screen after long pressing the shutter)

Hello, me again!

Got one more script and file-set for you now, with a binary that might be accepted by your Android DxO-ONE:

1. unzip the attached files (.ash and .bin) to your SDcard root. Delete dmesglog_rtos.txt on the SD
2. Disconnect the camera and switch it off
3. While switched off, press the shutter button, keep it pressed and connect a charger to microUSB
4. Keep the button pressed for several seconds (if we're lucky, until you see a progress bar) (or, whatever you did last time to make it show that black square in the viewfinder)

#10-upgradeFW.zip

Good luck!

[xzczcz]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

No, no, no. The viewfinder's not moving at all 10log.zip

[rickdeck]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

No, no, no. The viewfinder's not moving at all 10log.zip

You mean after doing this procedure? I can't see in the log that any update was executed...

[xzczcz]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

No, no, no. The viewfinder's not moving at all 10log.zip

You mean after doing this procedure? I can't see in the log that any update was executed...

Yes, I did not react to any of these movements

[rickdeck]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

No, no, no. The viewfinder's not moving at all 10log.zip

You mean after doing this procedure? I can't see in the log that any update was executed...

Yes, I did not react to any of these movements

Can you delete the files on the SD (Amba., dmesglog_rtos.txt), only keeping the autoexec.ash and start the camera again. I'm wondering if a new dmesglog would be created....

[xzczcz]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

不 不 不。取景器根本没有移动10log.zip

你的意思是做完这个程序之后？我在日志中看不到任何更新已执行...

是的，我没有对这些动作做出任何反应

您可以删除 SD 上的文件（Amba.、dmesglog_rtos.txt），只保留 autoexec.ash 并再次启动相机。我想知道是否会创建一个新的 dmesglog......

I deleted all (Amba., dmesglog_rtos.txt) leaving only autoexec.ash This is the log after starting the camera 10log(1).zip

[rickdeck]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

不 不 不。取景器根本没有移动10log.zip

你的意思是做完这个程序之后？我在日志中看不到任何更新已执行...

是的，我没有对这些动作做出任何反应

您可以删除 SD 上的文件（Amba.、dmesglog_rtos.txt），只保留 autoexec.ash 并再次启动相机。我想知道是否会创建一个新的 dmesglog......

I deleted all (Amba., dmesglog_rtos.txt) leaving only autoexec.ash This is the log after starting the camera 10log(1).zip

Okay this is strange, it is still booting the previous OS of the camera, and initializes all components according to the log. IF it accepted the firmware of #10-upgradeFW.zip, it didn't state anything in the log. And then, it also didn't boot into that new firmware...

But autoexec.ash is still executed.

We still have the option to write directly to memory in case you want to try that. But here we are skipping the pre-check of the device itself, so it's possible that it doesn't boot anymore at all after this is done... Let me know.

[xzczcz]

是的，我更换了 SD 卡并再次尝试，没有将AmbaUpdaterFW.bin放入 sd 并运行

不 不 不。取景器根本没有移动10log.zip

你的意思是做完这个程序之后？我在日志中看不到任何更新已执行...

是的，我没有对这些动作做出任何反应

您可以删除 SD 上的文件（Amba.、dmesglog_rtos.txt），只保留 autoexec.ash 并再次启动相机。我想知道是否会创建一个新的 dmesglog......

I deleted all (Amba., dmesglog_rtos.txt) leaving only autoexec.ash This is the log after starting the camera 10log(1).zip

Okay this is strange, it is still booting the previous OS of the camera, and initializes all components according to the log. IF it accepted the firmware of #10-upgradeFW.zip, it didn't state anything in the log. And then, it also didn't boot into that new firmware...

But autoexec.ash is still executed.

We still have the option to write directly to memory in case you want to try that. But here we are skipping the pre-check of the device itself, so it's possible that it doesn't boot anymore at all after this is done... Let me know.

Come on, I think you can try to write directly to memory. If you really can't open it after writing, is there any other way to solve it?

[rickdeck]

Come on, I think you can try to write directly to memory. If you really can't open it after writing, is there any other way to solve it?

If you understand the risk, then let's do it.

Here's the script.

1. It will enable lots of logs (that will not work on your current OS, but will start working in case the new OS boots up)
2. It then executes flash.ash which (tries to) write the binary directly and then deletes itself (to be sure it's only done once)

I tried the script on my (iOS) camera, it worked as expected (broke my camera because it's the wrong hardware, but I was able to reflash it back to the correct firmware and now it works again)

To be very clear: There is a serious risk that this will make your device unbootable. Since we failed to extract the firmware currently running on your camera (in our 10 previous attempts), I also see no way to revert the change in case the new firmware doesn't boot.

Procedure:

1. unzip the attached files (.ash and .bin) to your SDcard root. Delete dmesglog_rtos.txt and other txt-files on the SD
2. Disconnect the camera and switch it off
3. Switch on the camera and wait a bit. You may see a progress bar after a few seconds. If not, keep the camera on for a minute or so.

If it works, your camera should shutdown or reboot by itself after a while. After completion, remove the SD again then and check if you got some new files for me. If it reboots with the new firmware, you should also see a new "console_debug.txt" file on your SD

#11-upgradeFW.zip

[xzczcz]

来吧，我想你可以尝试直接写到内存中。如果写完真的打不开，还有别的办法解决吗？

如果您了解风险，那么让我们去做吧。

这是脚本。

1. 它将启用大量日志（在当前操作系统上不起作用，但在新操作系统启动时将开始工作）
2. 然后它执行 flash.ash，它（尝试）直接写入二进制文件，然后删除自身（以确保它只执行一次）

我在我的（iOS）相机上尝试了脚本，它按预期工作（损坏了我的相机，因为它是错误的硬件，但我能够将其重新刷新回正确的固件，现在它再次工作）

_需要明确的是：_这存在使您的设备无法启动的严重风险。由于我们未能提取当前在您的相机上运行的固件（在我们之前的 10 次尝试中），我也看不到在新固件无法启动的情况下恢复更改的方法。

程序：

1. 将附件（.ash 和 .bin）解压缩到 SDcard 根目录。删除 SD 上的其他 txt 文件dmesglog_rtos.txt
2. 断开相机连接并将其关闭
3. 打开相机，稍等片刻。几秒钟后，您可能会看到一个进度条。如果没有，请保持相机打开一分钟左右。

如果它有效，您的相机应该在一段时间后自行关闭或重新启动。完成后，再次删除 SD，然后检查您是否为我提供了一些新文件。如果它使用新固件重新启动，您还应该在 SD 上看到一个新的“console_debug.txt”文件

#11-upgradeFW.zip

The update was successful, but I still cannot connect to my phone (a pop-up appears asking whether the DXO One is connected to this USB device). The app does not support live view, and the connection keeps disconnecting and reconnecting intermittently. I have tried multiple versions of the app. Here is the log (11)log.zip

[rickdeck]

来吧，我想你可以尝试直接写到内存中。如果写完真的打不开，还有别的办法解决吗？

如果您了解风险，那么让我们去做吧。 这是脚本。

1. 它将启用大量日志（在当前操作系统上不起作用，但在新操作系统启动时将开始工作）
2. 然后它执行 flash.ash，它（尝试）直接写入二进制文件，然后删除自身（以确保它只执行一次）

我在我的（iOS）相机上尝试了脚本，它按预期工作（损坏了我的相机，因为它是错误的硬件，但我能够将其重新刷新回正确的固件，现在它再次工作） _需要明确的是：_这存在使您的设备无法启动的严重风险。由于我们未能提取当前在您的相机上运行的固件（在我们之前的 10 次尝试中），我也看不到在新固件无法启动的情况下恢复更改的方法。 程序：

1. 将附件（.ash 和 .bin）解压缩到 SDcard 根目录。删除 SD 上的其他 txt 文件dmesglog_rtos.txt
2. 断开相机连接并将其关闭
3. 打开相机，稍等片刻。几秒钟后，您可能会看到一个进度条。如果没有，请保持相机打开一分钟左右。

如果它有效，您的相机应该在一段时间后自行关闭或重新启动。完成后，再次删除 SD，然后检查您是否为我提供了一些新文件。如果它使用新固件重新启动，您还应该在 SD 上看到一个新的“console_debug.txt”文件 #11-upgradeFW.zip

The update was successful, but I still cannot connect to my phone (a pop-up appears asking whether the DXO One is connected to this USB device). The app does not support live view, and the connection keeps disconnecting and reconnecting intermittently. I have tried multiple versions of the app. Here is the log (11)log.zip

Ah, finally!

Now we should be able to reflash the whole OS. I'm not in front of a PC right now, could you try the following?

1. Keep autoexec.ash from script#11
2. Put DXOSYS_3_2_0_267b1a9e02.bin to SD-card (from script #7 ot #8 I think, important is that it's written in CAPS, so "DXOSYS" not "dxosys")
3. Remove all other Text-files and bins from SD
4. Insert SD-card, keep shutter button pressed and connect camera to a charger (not a PC)

If it works, the device should enter upgrade mode and perform a full firmware upgrade to the latest Android firmware (and take some logs along the way)

[xzczcz]

来吧，我想你可以尝试直接写到内存中。如果写完真的打不开，还有别的办法解决吗？

如果您了解风险，那么让我们去做吧。 这是脚本。

1. 它将启用大量日志（在当前操作系统上不起作用，但在新操作系统启动时将开始工作）
2. 然后它执行 flash.ash，它（尝试）直接写入二进制文件，然后删除自身（以确保它只执行一次）

我在我的（iOS）相机上尝试了脚本，它按预期工作（损坏了我的相机，因为它是错误的硬件，但我能够将其重新刷新回正确的固件，现在它再次工作） _需要明确的是：_这存在使您的设备无法启动的严重风险。由于我们未能提取当前在您的相机上运行的固件（在我们之前的 10 次尝试中），我也看不到在新固件无法启动的情况下恢复更改的方法。 程序：

1. 将附件（.ash 和 .bin）解压缩到 SDcard 根目录。删除 SD 上的其他 txt 文件dmesglog_rtos.txt
2. 断开相机连接并将其关闭
3. 打开相机，稍等片刻。几秒钟后，您可能会看到一个进度条。如果没有，请保持相机打开一分钟左右。

如果它有效，您的相机应该在一段时间后自行关闭或重新启动。完成后，再次删除 SD，然后检查您是否为我提供了一些新文件。如果它使用新固件重新启动，您还应该在 SD 上看到一个新的“console_debug.txt”文件 #11-upgradeFW.zip

The update was successful, but I still cannot connect to my phone (a pop-up appears asking whether the DXO One is connected to this USB device). The app does not support live view, and the connection keeps disconnecting and reconnecting intermittently. I have tried multiple versions of the app. Here is the log (11)log.zip

Ah, finally!

Now we should be able to reflash the whole OS. I'm not in front of a PC right now, could you try the following?

1. Keep autoexec.ash from script#11
2. Put DXOSYS_3_2_0_267b1a9e02.bin to SD-card (from script #7 ot #8 I think, important is that it's written in CAPS, so "DXOSYS" not "dxosys")
3. Remove all other Text-files and bins from SD
4. Insert SD-card, keep shutter button pressed and connect camera to a charger (not a PC)

If it works, the device should enter upgrade mode and perform a full firmware upgrade to the latest Android firmware (and take some logs along the way)

7 and 8, the bin files are all AmbaSysFW.bin I looked at only the script 5 bin file name is DXOSYS_3_2_0_267b1a9e02.bin Should I import a bin file of 5?

[rickdeck]

7 and 8, the bin files are all AmbaSysFW.bin I looked at only the script 5 bin file name is DXOSYS_3_2_0_267b1a9e02.bin Should I import a bin file of 5?

Yes, that's the file. Sorry, we already tried so many scripts ^^

[xzczcz]

7 和 8，bin 文件都是 AmbaSysFW.bin 我只看了脚本 5 bin 文件名是 DXOSYS_3_2_0_267b1a9e02.bin 我应该导入 5 的 bin 文件吗？

是的，就是文件。对不起，我们已经尝试了很多脚本^^

I'm the one who should apologize. If there weren't so many problems with the equipment, I wouldn't be bothering you. I have no choice but to ask for your help You have been very patient to help me solve this problem and have come up with many solutions. Thank you very much! But now there's a problem. I imported autoexec.DXOSYS_3_2_0_267b1a9e02.bin and tried to update it manually, but there was no response. (12)log.zip

[rickdeck]

I'm the one who should apologize. If there weren't so many problems with the equipment, I wouldn't be bothering you. I have no choice but to ask for your help You have been very patient to help me solve this problem and have come up with many solutions. Thank you very much! But now there's a problem. I imported autoexec.DXOSYS_3_2_0_267b1a9e02.bin and tried to update it manually, but there was no response.

I'm back at a PC again. Thanks for the log, the file is not found by the updater application, I think I found the issue. Can you please try the following file? Now it should start updating, at least that's what my iOS HW is doing...

1. Unzip the attached files (.ash and .bin) to your SDcard root. Delete dmesglog_rtos.txt and other txt-files on the SD
2. Disconnect the camera and switch it off
3. Insert SD-card, keep shutter button pressed and connect camera to a charger (not a PC), keep it pressed for a few seconds (until you see the FW-update progress-bar)

Let me know. #13-upgradeFW.zip

[xzczcz]

我是应该道歉的人。如果设备没有那么多问题，我不会打扰你。我别无选择，只能请求你的帮助，你一直很有耐心地帮我解决这个问题，并想出了很多解决方案。谢谢！但现在有一个问题。我导入了autoexec。DXOSYS_3_2_0_267b1a9e02.bin并尝试手动更新它，但没有响应。

我又回到了电脑前。感谢您的日志，更新程序应用程序找不到该文件，我想我找到了问题。你能试试下面的文件吗？现在_它应该_开始更新了，至少我的 iOS HW 正在这样做......

1. 将附件（.ash 和 .bin）解压缩到 SD 卡根目录。删除 SD 上的 dmesglog_rtos.txt 和其他 txt 文件
2. 断开相机连接并将其关闭
3. 插入SD卡，按住快门按钮并将相机连接到充电器（不是PC），按住几秒钟（直到看到固件更新进度条）

让我知道。 #13-upgradeFW.zip

He is very useful and the update was successful, but I still cannot connect to the mobile app. As I mentioned earlier (when I inserted the phone, a pop-up window appeared asking if DXO One was connected to this USB device), do you think there are any other issues? After importing your script, the iOS version can be connected to the phone through the OTG charging port and used normally with the app, and Type-C should not have any compatibility issues with the phone.

(13)log.zip

[rickdeck]

He is very useful and the update was successful, but I still cannot connect to the mobile app. As I mentioned earlier (when I inserted the phone, a pop-up window appeared asking if DXO One was connected to this USB device), do you think there are any other issues? After importing your script, the iOS version can be connected to the phone through the OTG charging port and used normally with the app, and Type-C should not have any compatibility issues with the phone.

Well, I don't have experience with the Android version of DXO-ONE, but now that you're on a recent firmware, we can assume that your connection issue is not related to SW.

The popup may just be the permission to allow the App to connect to this USB-Device (on Android, the user needs to confirm where to route the USB-connection). But that should be the same for the iOS-camera with the script.

The difference in behavior should not be related to the phone if your iOS device works fine using the script and the same phone. So yes, I would assume that something doesn't work well with your camera hardware.

You can try to use the Android-enable script for the iOS camera on the Android camera to see if you have the same app connection issues also on the microUSB port (--> to find out if it is an issue of the connector or the Mainboard).

You could consider trying to swap the iOS and USB-C connectors between your two cameras (if the pins in the camera are compatible), with a modified Android-enable script you might be able to use the iOS-Hardware with USB-C on an Android device (and without a script possibly also on iPhone 15)

Otherwise I'm out of ideas. There is a possibility that your hardware was never working properly because it was an early prototype, there's also a possibility that the whole Android DXO-ONE was never working well because it never entered mass-production...

[xzczcz]

他非常有用，更新成功，但我仍然无法连接到移动应用程序。正如我之前提到的（当我插入手机时，出现了一个弹出窗口，询问 DXO One 是否连接到此 USB 设备），您认为还有其他问题吗？导入脚本后，iOS版本可以通过OTG充电口连接手机，与App正常使用，Type-C应该不会与手机有任何兼容性问题。

好吧，我没有使用Android版本的DXO-ONE的经验，但是现在您使用的是最新的固件，我们可以假设您的连接问题与软件无关。

弹出窗口可能只是允许应用程序连接到此 USB 设备的权限（在 Android 上，用户需要确认将 USB 连接路由到何处）。但对于带有脚本的 iOS 相机来说，这应该是一样的。

如果您的 iOS 设备使用脚本和同一部手机工作正常，则行为差异不应与手机相关。所以，是的，我认为您的相机硬件无法正常工作。

您可以尝试在 Android 相机上对 iOS 相机使用启用 Android 的脚本，以查看您在 microUSB 端口上是否也存在相同的应用程序连接问题（--> 以确定这是连接器还是主板的问题）。

您可以考虑尝试在两台相机之间交换 iOS 和 USB-C 连接器（如果相机中的针脚兼容），使用修改后的支持 Android 的脚本，您也许可以在 Android 设备上使用带有 USB-C 的 iOS 硬件（如果没有脚本，也可能在 iPhone 15 上）

否则我就没有想法了。您的硬件可能从未正常工作，因为它是早期的原型，也有可能整个 Android DXO-ONE 从未正常工作，因为它从未进入批量生产......

Yes, after importing the good news script, I can connect the app via OTG and adjust the parameters normally. I also tried connecting it directly to the phone via Type-C and it worked well. However, after turning off the camera and restarting the phone, it often enters a sleep state and does not turn on. I can only turn it on by pressing the reset button. The app update notification says I can update, but I am already using the latest version 3.2.0.

[rickdeck]

Yes, after importing the good news script, I can connect the app via OTG and adjust the parameters normally. I also tried connecting it directly to the phone via Type-C and it worked well. However, after turning off the camera and restarting the phone, it often enters a sleep state and does not turn on. I can only turn it on by pressing the reset button. The app update notification says I can update, but I am already using the latest version 3.2.0.

You are not on the VERY latest version of the Android Firmware. I did this intentionally, so you can still do a "proper" upgrade via the Smartphone app if our recovery works. With the script I sent, your device is on version 3.2.0_12504d1481 (from App v1.2). App v1.3 shipped a newer 3.2.0 firmware (see here)

I haven't found any change-notes for the firmware, so it might be an issue fixed in the newer firmware. So, give it a try and let me know if you notice a difference.

[xzczcz]

Yes, after importing the good news script, I can connect the app via OTG and adjust the parameters normally. I also tried connecting it directly to the phone via Type-C and it worked well. However, after turning off the camera and restarting the phone, it often enters a sleep state and does not turn on. I can only turn it on by pressing the reset button. The app update notification says I can update, but I am already using the latest version 3.2.0.

You are not on the VERY latest version of the Android Firmware. I did this intentionally, so you can still do a "proper" upgrade via the Smartphone app if our recovery works. With the script I sent, your device is on version 3.2.0_12504d1481 (from App v1.2). App v1.3 shipped a newer 3.2.0 firmware (see here)

I haven't found any change-notes for the firmware, so it might be an issue fixed in the newer firmware. So, give it a try and let me know if you notice a difference.

I updated it to feel that there is no difference, but the camera will not sleep dead. It seems that there has been no sleep death problem since the last time I slept dead. All functions are normal. Except for WiFi, which should be a problem.

[rickdeck]

Yes, after importing the good news script, I can connect the app via OTG and adjust the parameters normally. I also tried connecting it directly to the phone via Type-C and it worked well. However, after turning off the camera and restarting the phone, it often enters a sleep state and does not turn on. I can only turn it on by pressing the reset button. The app update notification says I can update, but I am already using the latest version 3.2.0.

You are not on the VERY latest version of the Android Firmware. I did this intentionally, so you can still do a "proper" upgrade via the Smartphone app if our recovery works. With the script I sent, your device is on version 3.2.0_12504d1481 (from App v1.2). App v1.3 shipped a newer 3.2.0 firmware (see here) I haven't found any change-notes for the firmware, so it might be an issue fixed in the newer firmware. So, give it a try and let me know if you notice a difference.

I updated it to feel that there is no difference, but the camera will not sleep dead. It seems that there has been no sleep death problem since the last time I slept dead. All functions are normal. Except for WiFi, which should be a problem.

Sounds good. I didn't get WiFi to work yet with Android, no matter which firmware, so it's probably not your device. It's possible that Android changed dramatically since 2016 that the procedure of the app simply doesn't work anymore...

[xzczcz]

Yes, after importing the good news script, I can connect the app via OTG and adjust the parameters normally. I also tried connecting it directly to the phone via Type-C and it worked well. However, after turning off the camera and restarting the phone, it often enters a sleep state and does not turn on. I can only turn it on by pressing the reset button. The app update notification says I can update, but I am already using the latest version 3.2.0.

You are not on the VERY latest version of the Android Firmware. I did this intentionally, so you can still do a "proper" upgrade via the Smartphone app if our recovery works. With the script I sent, your device is on version 3.2.0_12504d1481 (from App v1.2). App v1.3 shipped a newer 3.2.0 firmware (see here) I haven't found any change-notes for the firmware, so it might be an issue fixed in the newer firmware. So, give it a try and let me know if you notice a difference.

I updated it to feel that there is no difference, but the camera will not sleep dead. It seems that there has been no sleep death problem since the last time I slept dead. All functions are normal. Except for WiFi, which should be a problem.

Sounds good. I didn't get WiFi to work yet with Android, no matter which firmware, so it's probably not your device. It's possible that Android changed dramatically since 2016 that the procedure of the app simply doesn't work anymore...

Once again, thank you very much. I wouldn't have been able to use this camera properly without your help. Thank you so much. If you have any new ideas in the future, please feel free to contact me. After all, you were the one who discovered the method to use the iOS version on Android phones, which I think is very impressive. It seemed impossible to me.