Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strings for Max3; Another method to fetch decrypted update.zip FYI #1

Closed
shunf4 opened this issue Sep 28, 2020 · 4 comments
Closed
Labels
new strings Strings for new model

Comments

@shunf4
Copy link

shunf4 commented Sep 28, 2020

First thanks for your work, it works perfectly on my Max3 with strings below:

MODEL = "Max3" 
STRING_7F00500 = "1wdvUHZmcz32N1pgG4fkHmDsTDVihMJsPCNV4mW/6u1k" 
STRING_7F00501 = "3nxuLgdpBE3B3n1Yyymt4cOS8dNucfQxK8YOsmcemuyO" 
STRING_7F00502 = "yCA9YlFxLBdLbDUl3vwzPkn9vtYuVFZCfhrOTvR1" 

Just for information purposes, there is another method that has been discussed in the thread Max3 Rooted in MobileRead Fourms.

To get the decrypted update.zip from system upgrade process:

  • Ensure you have root permission, preferably by installing Magisk, preferably by booting from a patched recovery.img from fastboot (It's always safer that the system and the boot image are not tainted), as per Magisk installation instruction
  • In adb shell, gain root permission by su, then go to /data/local
  • Ensure there is no update.zip in /data/local/assets
  • Duplicate assets directory: cp -a assets assets_2
  • Mount assets_2 to assets: mount -o bind /data/local/assets_2 /data/local/assets
  • Check for updates, download and install upgrade in settings, just as if you were in a normal upgrading process (If you encountered with some error that says something like "incorrect version", check permissions of the directory above. This is probably because the updater can't access /data/local/assets)
  • Decrypted update.zip is generated in mounted /data/local/assets, then the device reboots to recovery and upgrade process hangs, because the decrypted update.zip is now missing under /data/local/assets, but in /data/local/assets_2
  • Reboot and with root permission, fetch /data/local/assets_2/update.zip. That is the decrypted update data.

Also beware of possibility that all the methods could be invalidated by Onyx. In the thread above they quickly blocked EDL mode after the OP publicly mentioned that.

@Hagb
Copy link
Owner

Hagb commented Sep 28, 2020

Thanks for your information! I didn't know whether boox uses the same algorithm to decrypt update.zip in different models until this issue.
And may I mention the issue in README.md for this method to get update.zip?

@shunf4
Copy link
Author

shunf4 commented Sep 28, 2020

And may I mention the issue in README.md for this method to get update.zip?

Sure

Hagb added a commit that referenced this issue Sep 28, 2020
@Hagb Hagb added the new strings Strings for new model label Oct 6, 2020
@Hagb
Copy link
Owner

Hagb commented Oct 16, 2020

The strings are verified.
(By the way, there is a method to get url of boox firmware. #2 (comment))

@Hagb Hagb closed this as completed Oct 16, 2020
@talamascool
Copy link

talamascool commented Dec 22, 2021

has someone tried this method on the new 3.2 update?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new strings Strings for new model
Projects
None yet
Development

No branches or pull requests

3 participants