MobileRead Forums - View Single Post

wonnew · 11-18-2024, 12:06 AM

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!

11-18-2024, 12:06 AM	#5
wonnew Junior Member Posts: 5 Karma: 10 Join Date: Nov 2024 Device: Poke5(zh_CN)	Bootloop Issue on Onyx Boox Poke5 After Firmware Flash Attempt 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!