Quote:
Originally Posted by Renate
Modern day Qualcomm "loader files" (i.e. xbl/sbl replacements) are all signed ELF format files in either 32 or 64 bit version.
Normally ELF files are named .elf but they can also be named .bin
Most EDL clients don't care in the least how the files are named.
Code:
C:\>elfview /p /l poke3.bin
# Type Flags Filesize Offset Address Memsize
-- ------- ----- -------- ------ -------- -------
0 null 7 792 000000 00000000 0000000
1 null 2.2 6856 001000 85e28000 0002000
2 load RX 356508 003000 14015000 005709c
3 load RWZ 0 05a0a0 14077000 0003000
4 load RW 40704 05a0a0 1407a000 0009f00
5 load RWX 39176 063fa0 14084800 0013400
6 load RWZ 0 06d8b0 85e10000 00176a0
7 load RX 7804 06d8b0 146ae000 0001e7c
8 load RWZ 0 06f730 146b1000 00000e4
9 load RWX 100568 06f730 14098000 00188d8
10 load RWZ 0 088010 146b2000 0002dec
11 load RWZ 0 088010 14680000 0018620
12 load 5RX 77248 088010 14699000 0012dc0
CPU: ARM 64-bit architecture (AARCH64)
In the past .mbn (not ELF) files were used. |
okay so i found a proper loader but now im stuck again.
"Found EDL 9008, handshaking... version 2.1
HWID: 001740e100000000, JTAG: 001740e1, OEM: 0000, Model: 0000
Hash: d40eee56f3194665-574109a39267724a-e7944134cd53cb76-7e293d3c40497955-bc8a4519ff992b03-1fadc6355015ac87 (x3)
Sending 662.bin 100% ok, starting... ok, waiting for Firehose... no response, poking...
Could not write device"
and then after that the device disconnects
"Could not find EDL device"
Im stuck here and I cant figure out what to do next. (I installed the driver and enabled usb debugging)