I am trying (for the first time ever) to install LineageOS on my S9+. I am using a Windows 10 laptop. I have tried installing the correct driver using Zadiag, I have found two occurrences of Gadget Serial. Anyway heimdall is erroring out with:
C:\Users\codru\Downloads\Heimdall Suite>heimdall print-pit --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
<link removed>
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
<link removed>
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
WARNING: Control transfer #2 failed. Result: -7
WARNING: Control transfer #5 failed. Result: -7
WARNING: Control transfer #6 failed. Result: -9
ERROR: Failed to send data: "ODIN"
Releasing device interface...
C:\Users\codru\Downloads\Heimdall Suite>
Likewise using latest Heimdal 1.4.2
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send handshake!ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
eduuk said:
Likewise using latest Heimdal 1.4.2
Code:
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Setting up interface...
Initialising protocol...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer. Retrying...
ERROR: libusb error -7 whilst sending bulk transfer.
ERROR: Failed to send handshake!ERROR: Failed to receive handshake response. Result: -7
ERROR: Protocol initialisation failed!
Releasing device interface...
Click to expand...
Click to collapse
Heimdall does not work any more. It has not for a while. You must use odin.
Related
I'm trying to flash an SHW-M440S with the KIES_HOME_M440SKSALG2_M440SSKTALEE ROM using heimdall. heimdall seems to detect the phone OK, but when trying to flash, I get the following:
Code:
$ sudo heimdall flash --normal-boot boot.img --cache cache.img --hidden hidden.img --modem modem.bin --recovery recovery.img --system system.img --verbose --stdout-errors
[sudo] password for akos:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VID:PID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 131072
Downloading device's PIT file...
PIT file download sucessful
ERROR: Partition corresponding to -modem argument could not be located
when printing the partitioning, the modem part is stored in a partition named radio:
Code:
--- Entry #10 ---
Unused: No
Partition Type: 2 (EXT4)
Partition Identifier: 7
Partition Flags: 5 (R)
Unknown 1: 1
Partition Block Size: 114688
Partition Block Count: 65536
Unknown 2: 0
Unknown 3: 0
Partition Name: RADIO
Filename: modem.bin
I wonder what the solution is - is there a way to tell heimdall to use the above partition instead?
Akos
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
I am trying to unbrick my i777 using Enthropy512's post in the stickies on dev.
It died during the night while on CM10 and I am unable to flash a rom on it.
I go into download mode and run this:
heimdall flash --KERNEL zImage --no-reboot --verbose
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Manufacturer: "SAMSUNG"
Product: "Gadget Serial"
length: 18
device class: 2
S/N: 0
VIDID: 04E8:685D
bcdDevice: 021B
iMan:iProd:iSer: 1:2:0
nb confs: 1
interface[0].altsetting[0]: num endpoints = 1
Class.SubClass.Protocol: 02.02.01
endpoint[0].address: 83
max packet size: 0010
polling interval: 09
interface[1].altsetting[0]: num endpoints = 2
Class.SubClass.Protocol: 0A.00.00
endpoint[0].address: 81
max packet size: 0200
polling interval: 00
endpoint[1].address: 02
max packet size: 0200
polling interval: 00
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading KERNEL
0%
12%
25%
37%
50%
62%
75%
87%
100%
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet. Retrying...
ERROR: libusb error -7 whilst receiving packet.
ERROR: Failed to confirm end of file transfer sequence!
ERROR: KERNEL upload failed!
Ending session...
^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[B^[[BERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet. Retrying...
ERROR: libusb error -7 whilst sending packet.
ERROR: Failed to send end session packet!
Releasing device interface...
Re-attaching kernel driver...
Click to expand...
Click to collapse
dcunited08 said:
I am trying to unbrick my i777 using Enthropy512's post in the stickies on dev.
It died during the night while on CM10 and I am unable to flash a rom on it.
I go into download mode and run this:
Click to expand...
Click to collapse
Did you ever resolve this issue? I have exactly the same problem.
Hi all,
I have a Redmi Note 3 Special Edition (KATE) using MIUI 8 global 7.1.19 | Beta (6.0.1 MMB29M)
and I'm trying to unlock it using the official metod but, as I see it on a loot of cases, it is stuck at 50%.
I tried to follow a lot of threads (including unofficial method), but nothing works.
Now I'm using a USB sniffer (h**p://freeusbanalyzer.com/) (this is a free one, but any usb sniffing tool could be enough) and I watch what happen between MiUnlock tool (MiFlashUnlock_1.1.0317.1_en) and my phone.
this is the log:
Code:
000000: PnP Event: Device Connected (UP), 2017-02-05 09:50:43,9853586 (1. Device: Android Bootloader Interface)
The USB device has just been connected to the system.
000001: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,4340120 +10,4486485 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000002: Control Transfer (UP), 2017-02-05 09:50:54,4352269 +0,0012149. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000003: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,4353628 +0,0001359 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xe bytes to the device
67 65 74 76 61 72 3A 70 72 6F 64 75 63 74 getvar:product
000006: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,4362125 +0,0006771. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x8 bytes from the device
4F 4B 41 59 6B 61 74 65 OKAYkate
000007: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,5170053 +0,0807928 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000008: Control Transfer (UP), 2017-02-05 09:50:54,5182476 +0,0012423. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000009: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,5183864 +0,0001388 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xd bytes to the device
67 65 74 76 61 72 3A 73 6F 63 2D 69 64 getvar:soc-id
000012: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,5192327 +0,0005505. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000013: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,5861826 +0,0669499 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000014: Control Transfer (UP), 2017-02-05 09:50:54,5873706 +0,0011880. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000015: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,5875075 +0,0001369 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xd bytes to the device
67 65 74 76 61 72 3A 73 6F 63 5F 69 64 getvar:soc_id
000018: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,5883543 +0,0006893. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000019: Get Descriptor Request (DOWN), 2017-02-05 09:50:54,6663795 +0,0780252 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000020: Control Transfer (UP), 2017-02-05 09:50:54,6676384 +0,0012589. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000021: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:50:54,6677675 +0,0001291 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0x14 bytes to the device
67 65 74 76 61 72 3A 62 6F 61 72 64 5F 76 65 72 getvar:board_ver
73 69 6F 6E sion
000024: Bulk or Interrupt Transfer (UP), 2017-02-05 09:50:54,6686480 +0,0007040. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000025: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,3349831 +59,6663351 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000026: Control Transfer (UP), 2017-02-05 09:51:54,3362591 +0,0012760. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000027: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,3366136 +0,0003545 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0x7 bytes to the device
6F 65 6D 20 6C 6B 73 oem lks
000030: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,3374902 +0,0001624. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x13 bytes from the device
46 41 49 4C 75 6E 6B 6E 6F 77 6E 20 63 6F 6D 6D FAILunknown comm
61 6E 64 and
000031: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,4131364 +0,0756462 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000032: Control Transfer (UP), 2017-02-05 09:51:54,4143474 +0,0012110. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000033: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,4144867 +0,0001393 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xf bytes to the device
6F 65 6D 20 64 65 76 69 63 65 2D 69 6E 66 6F oem device-info
000036: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4153437 +0,0006957. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1b bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 74 61 6D 70 INFO.Device tamp
65 72 65 64 3A 20 66 61 6C 73 65 ered: false
000038: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4163381 +0,0009279. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1b bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 75 6E 6C 6F INFO.Device unlo
63 6B 65 64 3A 20 66 61 6C 73 65 cked: false
000040: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4173369 +0,0009572. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x24 bytes from the device
49 4E 46 4F 09 44 65 76 69 63 65 20 63 72 69 74 INFO.Device crit
69 63 61 6C 20 75 6E 6C 6F 63 6B 65 64 3A 20 66 ical unlocked: f
61 6C 73 65 alse
000042: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4183362 +0,0009577. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x21 bytes from the device
49 4E 46 4F 09 43 68 61 72 67 65 72 20 73 63 72 INFO.Charger scr
65 65 6E 20 65 6E 61 62 6C 65 64 3A 20 74 72 75 een enabled: tru
65 e
000044: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4193375 +0,0009602. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x14 bytes from the device
49 4E 46 4F 09 44 69 73 70 6C 61 79 20 70 61 6E INFO.Display pan
65 6C 3A 20 el:
000046: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4203363 +0,0009568. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x4 bytes from the device
4F 4B 41 59 OKAY
000047: Get Descriptor Request (DOWN), 2017-02-05 09:51:54,4849557 +0,0646194 (1. Device: Android Bootloader Interface)
Descriptor Type: String
Descriptor Index: 0x3
Transfer Buffer Size: 0x40 bytes
LanguageId: 0x409
000048: Control Transfer (UP), 2017-02-05 09:51:54,4861066 +0,0011509. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: Control Pipe
12 03 63 00 38 00 37 00 63 00 31 00 34 00 37 00 ..c.8.7.c.1.4.7.
34 00 4.
Setup Packet
80 06 03 03 09 04 40 00 €[email protected]
Recipient: Device
Request Type: Standard
Direction: Device->Host
Request: 0x6 (GET_DESCRIPTOR)
Value: 0x303
Index: 0x409
Length: 0x40
000049: Bulk or Interrupt Transfer (DOWN), 2017-02-05 09:51:54,4862122 +0,0001056 (1. Device: Android Bootloader Interface)
Pipe Handle: 0x9feaba34 (Endpoint Address: 0x1)
Send 0xc bytes to the device
67 65 74 76 61 72 3A 74 6F 6B 65 6E getvar:token
000052: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,4870975 +0,0006893. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x1c bytes from the device
4F 4B 41 59 45 44 71 49 31 37 50 42 51 6F 7A 4B OKAYEDqI17PBQozK
74 50 61 6B 77 7A 36 38 42 41 59 6F tPakwz68BAYo
Now I see that the oem lks command is failing with unknown command
6F 65 6D 20 6C 6B 73 oem lks
000030: Bulk or Interrupt Transfer (UP), 2017-02-05 09:51:54,3374902 +0,0001624. (1. Device: Android Bootloader Interface) Status: 0x00000000
Pipe Handle: 0x9feaba14 (Endpoint Address: 0x81)
Get 0x13 bytes from the device
46 41 49 4C 75 6E 6B 6E 6F 77 6E 20 63 6F 6D 6D FAILunknown comm
Is somebody else who tried to sniff the USB communication between Mi Unlock tool and the phone?
If your OFFICIAL unlock process is working, can you please post a log of your sniff? Maybe we can find the true commands that can unlock the phone without any permissions/ rights.
Do you know what the oem lks command is doing?
I have Beelink GT1 Ultimate tv box (Amlogic S912 CPU). One day some app froze and I turned power off and on. After turning power on, I had no signal on TV and it’s been like that ever since. I contacted Beelink and they gave different 2 images (GT1_709D0.img and GT1_708D0) to try flashing with USB Burning Tool. However, USB Burning Tool always gets stuck at 7% formatting with the following error:
Code:
error: [0x32030201]Uboot/Get result/DiskInitial error.
I tried every possible combination (different ports, power on/no power after reset, force erase, etc). The only positive is that the box is detected by USB Burning Tool.
I also tried making bootable sd card with Burn card maker using those images but it didn’t help either – UART output provided.
Can someone tell me based on the UART logs below what is going on and suggest steps to debug/resolve it?
The interesting part is that every time UART output stops at these two lines and when I googled those lines, it seems other people tv boxes logs, where I found these lines, there is more output following them but in my case it always stops at those lines:
Code:
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
Here is the UART output with normal operation – endless loop:
Code:
GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;READ:800;SD:800;USB:8;LOOP:1;EMMC:0;READ:800;SD:800;USB:8;
...
Here is the UART output when trying to flash with USB Burning Tool:
Code:
GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;READ:800;SD:800;USB:8;0.0;
TE: 1981641
BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - [email protected]
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 12
CPU clk: 1200MHz
BL2 USB
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
0.0;
TE: 2129485
BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - [email protected]
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 12
CPU clk: 1200MHz
BL2 USB
0.0;
TE: 2192478
BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - [email protected]
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 12
CPU clk: 1200MHz
BL2 USB
Load fip header from USB, src: 0x0000c000, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from USB, src: 0x00010000, des: 0x01100000, size: 0x0000d600
Load bl31 from USB, src: 0x00020000, des: 0x05100000, size: 0x0002c600
Load bl33 from USB, src: 0x00050000, des: 0x01000000, size: 0x00065800
NOTICE: BL3-1: v1.0(release):a625749
NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017
NOTICE: BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 [email protected]]
OPS=0x82
wdt: reset registers!
c4 68 a7 67 35 33 5f ce 11 6f 7c e2 [2.436513 Inits done]
secure task start!
high task start!
low task start!
ERROR: Error initializing runtime service opteed_fast
U-Boot 2015.01-ge6b8bc9 (May 05 2018 - 10:41:07)
DRAM: 3 GiB
Relocation Offset is: 76eb4000
[MSG]MMC init in usb
aml_priv->desc_buf = 0x0000000073eb4640
aml_priv->desc_buf = 0x0000000073eb6960
SDIO Port B: 0, SDIO Port C: 1
InUsbBurn
[MSG]sof
Set Addr 6
Get DT cfg
Get DT cfg
Get DT cfg
set CFG
Get DT cfg
Get DT cfg
Get str 300
Get DT cfg
Get DT cfg
Get str 300
Get DT cfg
Get DT cfg
ID[16]
tplcmd[ echo 12345]
12345
[MSG]ret = 0
[info]success
BULKcmd[ low_power]
[info]success
ID[16]
tplcmd[ download mem dtb normal 141312]
[MSG]Down(mem) part(dtb) sz(0x22800) fmt(normal)
[MSG]totalSlotNum = 0, nextWriteBackSlot 3
[info]success
[MSG]Burn Start...
[MSG]load dt.img to 0x0000000001000000, sz=0x22800
[MSG]Burn complete
BULKcmd[download get_status]
[info]success
BULKcmd[disk_initial 4]
dtb magic 5f4c4d41
Amlogic multi-dtb tool
Multi dtb detected
Multi dtb tool version: v2 .
Support 3 dtbs.
aml_dt soc: gxm platform: q201 variant: 3g
dtb 0 soc: gxm plat: q201 vari: 1g
dtb 1 soc: gxm plat: q201 vari: 2g
dtb 2 soc: gxm plat: q201 vari: 3g
Find match dtb: 2
start dts,buffer=0000000001000000,dt_addr=000000000100b800
Amlogic multi-dtb tool
Multi dtb detected
Multi dtb tool version: v2 .
Support 3 dtbs.
aml_dt soc: gxm platform: q201 variant: 3g
dtb 0 soc: gxm plat: q201 vari: 1g
dtb 1 soc: gxm plat: q201 vari: 2g
dtb 2 soc: gxm plat: q201 vari: 3g
Find match dtb: 2
parts: 10
00: logo 0000000002000000 1
01: recovery 0000000002000000 1
02: rsv 0000000000800000 1
03: tee 0000000000800000 1
04: crypt 0000000002000000 1
05: misc 0000000002000000 1
06: boot 0000000002000000 1
07: system 0000000080000000 1
08: cache 0000000020000000 2
09: data ffffffffffffffff 4
[MSG]run cmd [store disprotect key; store disprotect hynix]
[store]disprotect key
disprotect hynix
emmc/sd response timeout, cmd8, status=0x3ff2800
emmc/sd response timeout, cmd55, status=0x3ff2800
Here is the UART output when trying to use bootable SD card:
Code:
GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:80;POC:3;RCY:0;EMMC:0;READ:800;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected
TE: 191592
BL2 Built : 20:32:17, Sep 8 2017.
gxl g6296b83 - [email protected]
set vdd cpu_a to 1120 mv
set vdd cpu_b to 1050 mv
set vddee to 1000 mv
Board ID = 12
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
STICKY_REG0: 0x00000000
STICKY_REG1: 0x00000000
STICKY_REG9: 0x00000000
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x0002c600
Load bl33 from SD, src: 0x00050200, des: 0x01000000, size: 0x00065800
NOTICE: BL3-1: v1.0(release):a625749
NOTICE: BL3-1: Built : 11:25:15, Aug 25 2017
NOTICE: BL31: BL33 decompress pass
mpu_config_enable:ok
[Image: gxl_v1.1.3243-377db0f 2017-09-07 11:28:58 [email protected]]
OPS=0x82
wdt: reset registers!
c4 68 a7 67 35 33 5f ce 11 6f 7c e2 [0.543459 Inits done]
secure task start!
high task start!
low task start!
ERROR: Error initializing runtime service opteed_fast
U-Boot 2015.01-ge6b8bc9 (May 05 2018 - 10:41:07)
DRAM: 3 GiB
Relocation Offset is: 76eb4000
register usb cfg[0][1] = 0000000077f5b0e8
[CANVAS]canvas init
boot_device_flag : 1
set wlan gpio pin 6.
set bluetooth gpio pin 17.
Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc.
init bus_cycle=6, bus_timing=7, system=5.0ns
reset failed
get_chip_type and ret:fffffffe
get_chip_type and ret:fffffffe
chip detect failed and ret:fffffffe
nandphy_init failed and ret=0xfffffff1
MMC: aml_priv->desc_buf = 0x0000000073eb4790
aml_priv->desc_buf = 0x0000000073eb6ab0
SDIO Port B: 0, SDIO Port C: 1
emmc/sd response timeout, cmd8, status=0x1ff2800
emmc/sd response timeout, cmd55, status=0x1ff2800
Thanks in advance for your help
Nobody knows what is going on based those UART logs?
Hello everyone,
I am in need of some help with decrypting the locked rootfs on my Allwinner H6 (sun50iw6p1) SoC. I have been trying to access the rootfs for a while now, but with no success.
I have unpacked the image using imgrepacker, I was able to repack the image with success, The issue I face is that the rootfs is encrypted, and I need to decrypt it to access it. I have searched online for solutions, but there isn't much information available on how to decrypt the rootfs on this particular SoC.
This rootfs is accessable/unlocked and mounted on boot but this SoC has all UART write disabled and no SSH access.
I am hoping to decrypt the drive to gain access to the rootfs to modify some core functions such as UCI and other bash files and repack using imgrepacker.
If anyone has experience with this and knows how to decrypt the locked rootfs, please do share your knowledge and expertise.
Please note my knowledge is very limited but willing to learn.
I have attached:
- LUKS Encryption Header
- RAMDISK Logs
- BINWALK Signatures
Spoiler: View Luks Encryption
Code:
Version: 1
Cipher name: aes
Cipher mode: xts-plain64
Hash spec: sha256
Payload offset: 4096
MK bits: 256
MK digest: 80 18 47 cf b6 62 fd 22 d6 24 22 45 0b c8 69 dc 85 3b 67 4d
MK salt: 78 55 50 2d 86 d8 ad ab 31 52 c3 09 41 39 cf 8b
c1 66 1d c8 4c 71 e4 7a 05 74 fc 92 b0 a1 a7 65
MK iterations: 225986
UUID: 03e0a71e-ce09-4ec0-b459-93e973f0304c
Key Slot 0: ENABLED
Iterations: 178633
Salt: 8e 41 7d 59 d5 a0 9e c4 e1 8b 94 b0 8a 9f 41 7f
f3 af b3 f7 3d ac 11 c3 68 3b 7d 1f 44 b4 37 e3
Key material offset: 8
AF stripes: 4000
Key Slot 1: DISABLED
Key Slot 2: DISABLED
Key Slot 3: DISABLED
Key Slot 4: DISABLED
Key Slot 5: DISABLED
Key Slot 6: DISABLED
Key Slot 7: DISABLED
Spoiler: View RAMDISK Logs
Code:
01-02 08:00:00.27 W kernel: [ 4.802070] [ramdisk]: ======================ramdisk start====================
01-02 08:00:00.27 W kernel: [ 4.816451] [ramdisk]: [/init]: RootDevice is "/dev/system"
01-02 08:00:00.27 W kernel: [ 4.822840] [ramdisk]: [/init]: Boot_type is "0"
01-02 08:00:00.27 W kernel: [ 4.842118] [ramdisk]: [/init]: Try to load Nand ...
01-02 08:00:00.27 I kernel: [ 6.513301] device-mapper: crypt: xts(aes) using implementation "xts-aes-ce"
01-02 08:00:00.27 W kernel: [ 6.557444] [ramdisk]: /dev/mapper/rootfs already has journal
01-02 08:00:00.27 W kernel: [ 6.564081] [ramdisk]: e2fsck -y /dev/mapper/rootfs
01-02 08:00:00.27 W kernel: [ 6.575236] [ramdisk]: mount nand /dev/mapper/rootfs on /root temporarily
01-02 08:00:00.27 W kernel: [ 6.589585] EXT4-fs: Warning: mounting with data=journal disables delayed allocation and O_DIRECT support!
01-02 08:00:00.27 I kernel: [ 6.617284] EXT4-fs (dm-0): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 W kernel: [ 6.627217] [ramdisk]: check partition /dev/by-name/data
01-02 08:00:00.27 W kernel: [ 6.708009] [ramdisk]: mount /dev/by-name/data on /mnt
01-02 08:00:00.27 I kernel: [ 6.734417] EXT4-fs (nandf): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 E kernel: [ 6.770892] [NAND]unknow cmd 0x4c01!
01-02 08:00:00.27 W kernel: [ 6.775302] [ramdisk]: /dev/by-name/data has ext4
01-02 08:00:00.27 W kernel: [ 6.780658] [ramdisk]: check_and_mount_data_parts
01-02 08:00:00.27 W kernel: [ 6.786059] [ramdisk]: check partition /dev/by-name/data
01-02 08:00:00.27 W kernel: [ 6.797751] [ramdisk]: mount /dev/by-name/data on /mnt
01-02 08:00:00.27 I kernel: [ 6.817645] EXT4-fs (nandf): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 E kernel: [ 6.854879] [NAND]unknow cmd 0x4c01!
01-02 08:00:00.27 W kernel: [ 6.859282] [ramdisk]: /dev/by-name/data has ext4
01-02 08:00:00.27 W kernel: [ 6.864638] [ramdisk]: mount /dev/by-name/data on /root/data
01-02 08:00:00.27 I kernel: [ 6.880546] EXT4-fs (nandf): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 W kernel: [ 6.890563] [ramdisk]: check partition /dev/by-name/data_bak
01-02 08:00:00.27 W kernel: [ 6.968366] [ramdisk]: mount /dev/by-name/data_bak on /mnt
01-02 08:00:00.27 I kernel: [ 6.995460] EXT4-fs (nandg): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 E kernel: [ 7.030895] [NAND]unknow cmd 0x4c01!
01-02 08:00:00.27 W kernel: [ 7.035305] [ramdisk]: /dev/by-name/data_bak has ext4
01-02 08:00:00.27 W kernel: [ 7.041056] [ramdisk]: mount /dev/by-name/data_bak on /root/data_bak
01-02 08:00:00.27 I kernel: [ 7.057376] EXT4-fs (nandg): mounted filesystem with journalled data mode. Opts: data=journal
01-02 08:00:00.27 W kernel: [ 7.075673] [ramdisk]: ======================ramdisk end====================
Spoiler: View Binwalk of Extracted Files
binwalk *.fex
Code:
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/arisc.fex
MD5 Checksum: f9f8acd107fc4eeda65a709c943c1212
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/aultls32.fex
MD5 Checksum: 3ef6e294e5db103f666cd9663f6ab62a
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
141311 0x227FF Unix path: /home/user/lichee/tools/pack/out_android/
142030 0x22ACE Unix path: /home/user/lichee/tools/pack/out_android/boot.img /home/user/imgdata/boot
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/aultools.fex
MD5 Checksum: 53c1610f722fd281f1e479ce6a20b6bc
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
154631 0x25C07 Unix path: /home/user/lichee/tools/pack/out_android/
155490 0x25F62 Unix path: /home/user/lichee/tools/pack/out_android/boot.img /home/user/imgdata/boot
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/board.fex
MD5 Checksum: 962f9346fd771aa3659d48016a255b4d
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/boot0_nand.fex
MD5 Checksum: 2be93fa43b62dfc0350d3d69de19b5e8
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/boot0_sdcard.fex
MD5 Checksum: c9161a4455bbfb49a1d8fec081f5d530
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/boot_package.fex
MD5 Checksum: 0ffaa05834e907c9362cc65c8c86559f
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
489984 0x77A00 SHA256 hash constants, little endian
592493 0x90A6D Certificate in DER format (x509 v3), header length: 4, sequence length: 5416
745084 0xB5E7C CRC32 polynomial table, little endian
746540 0xB642C Intel x86 or x64 microcode, sig 0x0000000c, pf_mask 0x01, 2000-07-02, rev 0x4a0cec49, size 2
781880 0xBEE38 Android bootimg, kernel size: 2037543936 bytes, kernel addr: 0x206F7420, ramdisk size: 1684104562 bytes, ramdisk addr: 0x72617020, product name: "ash read :offset %x, %d bytes %s"
783386 0xBF41A Copyright string: "Copyright (C) 2010 Charles Cazabon."
1561600 0x17D400 Flattened device tree, size: 134167 bytes, version: 17
1700864 0x19F400 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: -1 bytes
Scan Time: 2023-04-07 23:57:03
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/boot-resource.fex
MD5 Checksum: 59a8cdc4034da50def07f0c7c8ac7c84
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
281088 0x44A00 PC bitmap, Windows 3.x format,, 1280 x 720 x 32
4315648 0x41DA00 PC bitmap, Windows 3.x format,, 246 x 257 x 24
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/cardscript.fex
MD5 Checksum: e4f356976ba71d8793e12195295527d9
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/cardtool.fex
MD5 Checksum: 1f4762529fb56865d97257345fa7abf1
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Microsoft executable, portable (PE)
47876 0xBB04 Intel x86 or x64 microcode, sig 0xffffffe0, pf_mask 0x01, 1E2C-10-01, size 1
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/config.fex
MD5 Checksum: 09ed242e0e0d4e4198edde482544352f
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/data.fex
MD5 Checksum: c9bb33f2a10c1ce1be952964f5b8a98b
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Linux EXT filesystem, blocks count: 8192, image size: 8388608, rev 2.0, ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9c0f9
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/dlinfo.fex
MD5 Checksum: 3dcf38789b7d901b414ef43969bf6489
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/env.fex
MD5 Checksum: 1227c5c850bd07b15f8c66b522354cec
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/fes1.fex
MD5 Checksum: 45078a8d866278ddab9cd2fc757065d1
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:04
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/fit-image.fex
MD5 Checksum: 94f9cb25dbd42e8c1824e892faa96fd3
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Flattened device tree, size: 4600731 bytes, version: 17
220 0xDC gzip compressed data, maximum compression, from Unix, last modified: 1970-01-01 00:00:00 (null date)
Scan Time: 2023-04-07 23:57:05
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/rootfs.fex
MD5 Checksum: 0aa27d708ef48cd9b7d4e936d0d50358
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 LUKS_MAGIC version 0x1 aes sha256
44597269 0x2A88015 MySQL MISAM index file Version 6
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/split_xxxx.fex
MD5 Checksum: 2d2624044f1e232bd241a715e5a1f6e1
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/sunxi.fex
MD5 Checksum: c6dc189788e7c9de9df189dfaa7d39a9
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Flattened device tree, size: 134167 bytes, version: 17
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/sunxi_mbr.fex
MD5 Checksum: 8d2446421ab43775894d321781084e11
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
76 0x4C LZMA compressed data, properties: 0x65, dictionary size: 0 bytes, uncompressed size: 128 bytes
16460 0x404C LZMA compressed data, properties: 0x65, dictionary size: 0 bytes, uncompressed size: 128 bytes
32844 0x804C LZMA compressed data, properties: 0x65, dictionary size: 0 bytes, uncompressed size: 128 bytes
49228 0xC04C LZMA compressed data, properties: 0x65, dictionary size: 0 bytes, uncompressed size: 128 bytes
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/sys_config.fex
MD5 Checksum: c3b711269b46003723e72bc14b2ef9f4
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/sys_partition.fex
MD5 Checksum: 21af51dfa675a97744e052c8107d4456
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/toc0.fex
MD5 Checksum: e257f181c14a4020211370442475f703
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/toc1.fex
MD5 Checksum: b51ad39c87e98314ba53cedb090a0930
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/u-boot-crash.fex
MD5 Checksum: be07519778e697b6b716e410b5bea85d
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:11
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/u-boot.fex
MD5 Checksum: e25cce6dcf4578c9c6a9f1a3da2b8acc
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
486912 0x76E00 SHA256 hash constants, little endian
589421 0x8FE6D Certificate in DER format (x509 v3), header length: 4, sequence length: 5416
742012 0xB527C CRC32 polynomial table, little endian
743468 0xB582C Intel x86 or x64 microcode, sig 0x0000000c, pf_mask 0x01, 2000-07-02, rev 0x4a0cec49, size 2
778808 0xBE238 Android bootimg, kernel size: 2037543936 bytes, kernel addr: 0x206F7420, ramdisk size: 1684104562 bytes, ramdisk addr: 0x72617020, product name: "ash read :offset %x, %d bytes %s"
780314 0xBE81A Copyright string: "Copyright (C) 2010 Charles Cazabon."
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/usbtool_crash.fex
MD5 Checksum: 6dadd3708ab6ca078c9fc4aa99664fa6
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Microsoft executable, portable (PE)
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/usbtool.fex
MD5 Checksum: 3432a655c6538edcda599f0aae265eb2
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 Microsoft executable, portable (PE)
130824 0x1FF08 Intel x86 or x64 microcode, pf_mask 0x00, 1918-10-02, rev 0x10021910, size 2048
132132 0x20424 Intel x86 or x64 microcode, sig 0x19930522, pf_mask 0x01, 1DFC-10-02, rev 0x0001, size 2048
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/Vboot-resource.fex
MD5 Checksum: f885e16904bda1f7f699fd2904f2cffe
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/Vdata.fex
MD5 Checksum: f869eb23e402940059cb3ec761dde81f
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/Venv.fex
MD5 Checksum: fe31c777c7957410bf7c8246e76ef9ab
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/Vfit-image.fex
MD5 Checksum: 1cd297409cd6d19f55983f7ae6ab6040
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/vmlinux.fex
MD5 Checksum: b8f97a4ddd7b48a17ea22b90b716490e
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
0 0x0 bzip2 compressed data, block size = 900k
Scan Time: 2023-04-07 23:57:12
Target File: /home/ap/Firmwares/H6OS/h6os.img.dump/Vrootfs.fex
MD5 Checksum: 55e7e002eb9bfb9268e84cc81c2dd2c9
Signatures: 411
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------