Quote:
Originally Posted by Renate
It's on the link above. That page include Windows utilities for Android and Android utilities for Android.
You didn't say what the HWID was. Snapdragon numbers can be unique or ambiguous.
Since d40eee... indicates Qualcomm signing we don't need to match the hash. But we do need to match the SoC, the PMIC, the flash type, etc. We can try to match using memory footprint. Be prepared to try a bunch of Firehose loaders.
Did you install 3.5.4 already?
I really could use an xbl for comparison. If somebody could pull a copy from an update it would make my life easier.
|
From:
https://github.com/bkerler/edl/issues/534
I believe I found the loader that works linked.
However looks like "VIP" mode is enabled.
Does anyone have any resources/information on working with VIP locked devices?
C:\Users\shayn\Downloads\root_boox_onyx_devices\ed l>..\env_setup_dependencies\edl /l..\prog_firehose_ddr.elf
Found EDL 9008, handshaking... nope, resetting... version 2.1
HWID: 001b80e100000000, JTAG: 001b80e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending prog_firehose_ddr.elf 100% ok, starting... ok, waiting for Firehose... ok
C:\Users\shayn\Downloads\root_boox_onyx_devices\ed l>edl reset
Qualcomm Sahara / Firehose Client V3.62 (c) B.Kerler 2018-2024.
main - Trying with no loader given ...
main - Waiting for the device
main - Device detected
main - Mode detected: firehose
firehose
firehose - [LIB]: ERROR: Secure Boot *not* enabled BUT VIP *is* enabled. Therefore will *not* check digital signature on Digest Table. This allows easier testing on non-secure targets.