-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
incremental update #42
Comments
Hi @nareto, as the README noted,
These are the steps I took to extract files for my device.
I hope this helps. |
Thanks @mrwm ! Had somehow missed that in the README. Was able to get the |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
I've seen this mentioned in various issues, but haven't grasped what the definitive solution is: the most recent firmware updates are only incremental, so they have only a
payload.bin
file and noboot.img
, which is what is needed for Magisk.In this case, how do we get the correct
boot.img
? I would rather avoid the alternative procedure described in the "Boot into Emergency Download (EDL) 9008 mode" section on Tho85's blog, because AFAIU it involves googling for some random binary file calledprog_emmc_ufs_firehose_Sdm636_ddr.elf
whose purpose I don't understand and which I can't anyways find from a trusted sourceThe long version: my specific situation and what I tried
I just received a MaxLumi2. At first I downloaded the latest firmware available on this page (3.2), however this seems not decryptable: when running the script on the
update.upx
I getValueError: The decrypted data seems not a zip package
So I got my fingerprint:
$ adb shell "getprop ro.vendor.build.fingerprint" ONYX/BOOX/BOOX:11/RKQ1.210614.002/200:userdebug/release-keys
and the usual MaxLumi2 strings from the GetBoxxUpxKeysApp (they are the same as ones in the README).
I built this url
which however doesn't work. If I remove the fingerprint like this
I do indeed get a JSON file with a download URL. The downloaded
update.upx
though is incremental (has only the payload, noboot.img
), which brings me to the original questionThe text was updated successfully, but these errors were encountered: