Boox OS 4.0 is coming

[Renate]

The new NoteAir4C has been released with the latest iteration of the Boox software, version 4.0 (vs the current 3.5.4).

Model:  NoteAir4C (English)
Finger: Onyx/NoteAir4C/NoteAir4C:11/2024-10-23_17-54_4.0_6f06cb790/1287:user/release-keys
Link:   http://firmware-us.boox.com/ba79cb9d838c5623e35b6469da625159/update.upx
Size:   1,879,050,044
MD5:    ba79cb9d838c5623e35b6469da625159

Normally we haven't seen any updates on new devices before. The updates come 6-12 months later.

[Renate]

Poke5P (English) got 3.5.4 two months ago.
http://firmware-us.boox.com/18f6e5a5...eb6/update.upx

[starkruzr]

excited for 4.0 on my Tab Mini C. at least until they finally update the 7.8" formfactor. :P

[Renate]

Originally Posted by starkruzr

excited for 4.0 on my Tab Mini C. at least until they finally update the 7.8" formfactor. :P

3.5.4 for TabMiniC came out in September.

It's not clear which devices will get 4.0

[wonnew]

Hello Renate,
I left a message on a GitHub issue, but since you mentioned that it would be better to discuss it here, I signed up and am leaving a message.

I have read your post about the Poke5P on This site and wanted to reach out
for help.

In Korea, there is a method being shared to switch from the Chinese ROM to the global ROM on Onyx Boox devices. The process involves decrypting the `update.upx` file using decryptBooxUpdateUpx.py, extracting the resulting ZIP file, and then unpacking the `payload.bin` file to flash the ROM images via fastboot.

Following this guide, I downloaded the 3.5.3 firmware you posted in your MobileRead thread and attempted to flash the ROM images using fastboot. Unfortunately, my device is now stuck in a bootloop.

To recover my device, I have tried several methods based on both Korean and international guides, but none of them have worked. Here are the steps I have taken:

1. Attempting to sideload the 3.5.3 zh_CN firmware via ADB:
This method failed with the error message:
`"Update package is older than the current build, expected a build newer than timestamp 1723879554 but package has timestamp 1719833874 and downgrade not allowed."`
The `update.upx` file I found was from July, but my device had an August update of version 3.5.3 installed.

2. Attempting to sideload the 3.5.4 zh_CN firmware via ADB:
This method also failed with the error:
`"failed to verify whole-file signature, update package verification tool 106.2s, Signature verification failed."`
I also raised this issue on GitHub but haven’t found a solution yet.

3. Flashing via fastboot:
I tried reversing the guide shared in Korea for switching to global firmware by decrypting the 3.5.3 firmware that was rejected due to timestamp issues and extracting the ROM files from `payload.bin`. I then flashed these files using fastboot, but my device still remains in a bootloop.

The current firmware version installed on my device is as follows:
Version: 2024-08-17_15-25_3.5.3_3dc612b21 / 9285

I suspect that if I could find exactly the same firmware that is currently installed on my device, I might be able to recover it through sideloading, but it seems difficult to obtain that specific version.

Do you have any suggestions or alternative methods that could help me recover my device?

Thank you in advance for your help!

[Renate]

Originally Posted by wonnew

Do you have any suggestions or alternative methods that could help me recover my device?

Yes. You can use my custom recovery to flash the latest Poke5P 3.5.4 to a Poke5. I'll send you a PM for a link.

[Renate]

Originally Posted by wonnew

Do you have any suggestions or alternative methods that could help me recover my device?

Poke5P 3.5.4 update is http://firmware-us.boox.com/18f6e5a5...eb6/update.upx
Download it and decrypt it. You need to put the decrypted update.zip on either an SD card or a USB flash drive. Do not insert either until ready.

Take the custom recovery and flash it to recovery_a and recovery_b using EDL or fastboot or (if rooted) ADB and dd.

Go to recovery using "reboot recovery" in bootloader or on ADB. If not you can flash in EDL to go to recovery also.

Recovery will boot and you have a white screen. You should have ADB also.

With ADB, go "adb shell start autoupdate". The screen should tell you that it's waiting for a flash drive (or SD). Insert. Sit back. It should type stuff and complete in ~5 minutes and reboot.

[wonnew]

I attempted to flash a custom recovery to **recovery_a** and **recovery_b** using the **fastboot flash** command. However, an error occurred during the flashing of **recovery_a**, and I was unable to proceed with flashing **recovery_b** or any subsequent steps. Below is the error log from the attempt to flash **recovery_a**:

```
Sending 'recovery_a' (23708 KB) OKAY [ 0.669s]
Writing 'recovery_a' FAILED (remote: 'Unrecognized command flash')
fastboot: error: Command failed
```

Is there something I might have missed?

Originally Posted by Renate

Poke5P 3.5.4 update is http://firmware-us.boox.com/18f6e5a5...eb6/update.upx
Download it and decrypt it. You need to put the decrypted update.zip on either an SD card or a USB flash drive. Do not insert either until ready.

Take the custom recovery and flash it to recovery_a and recovery_b using EDL or fastboot or (if rooted) ADB and dd.

Go to recovery using "reboot recovery" in bootloader or on ADB. If not you can flash in EDL to go to recovery also.

Recovery will boot and you have a white screen. You should have ADB also.

With ADB, go "adb shell start autoupdate". The screen should tell you that it's waiting for a flash drive (or SD). Insert. Sit back. It should type stuff and complete in ~5 minutes and reboot.

[Renate]

Oh, I thought that you were using fastboot before with the old version.

You need to use EDL. It's on my website, read the instructions, download the Firehose loader for Poke5 there, install WinUsb driver with Zadig, flash recovery.

If you still have a working system "adb reboot recovery".
If not use EDL to flash the misc partition with misc-recovery. (Just rename the file.)

edl /w /pmisc misc-recovery /z

[Quyen607]

Hi Renate, is 3.5.4 a full update ?

[Renate]

For the Poke3, Poke5 and Leaf2 3.5.4 is a full update.

[wonnew]

I tried accessing EDL using the `adb reboot edl` command, but the device shows as unauthorized and cannot boot. Unfortunately, my device is stuck in a bootloop, so it’s difficult to reactivate USB debugging mode.
I’ve ordered an EDL cable from AliExpress. Once it arrives, I’ll try again and ask if I have further questions.
Thank you, Renate!

[Renate]

You can make your own EDL cable too. Just make sure to leave the red wire alone. There are instructions online.

The Poke3 doesn't work with an EDL cable, the Poke5 does. I never even checked my Go6 since I built in a magnetic EDL switch anyway. But the Go6 does work with an EDL cable. I built an automatic "EDL cable" (that's a box) where you don't even have to push a button or get the timing right.

[wonnew]

Wow, that’s amazing, Renate.
But I don’t have the skills like you. 😭
So I think I’ll have to buy a cable and use it instead of making one…

Originally Posted by Renate

You can make your own EDL cable too. Just make sure to leave the red wire alone. There are instructions online.

The Poke3 doesn't work with an EDL cable, the Poke5 does. I never even checked my Go6 since I built in a magnetic EDL switch anyway. But the Go6 does work with an EDL cable. I built an automatic "EDL cable" (that's a box) where you don't even have to push a button or get the timing right.