1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
|
files: 0.099
device: 0.091
PID: 0.090
permissions: 0.089
semantic: 0.088
debug: 0.084
other: 0.075
boot: 0.073
graphic: 0.073
performance: 0.067
vnc: 0.057
network: 0.043
socket: 0.037
KVM: 0.036
files: 0.320
debug: 0.212
device: 0.126
other: 0.062
boot: 0.052
semantic: 0.041
PID: 0.035
network: 0.033
graphic: 0.025
vnc: 0.024
socket: 0.020
permissions: 0.020
performance: 0.018
KVM: 0.010
qemu don't start *.abs firmware files
Hello Devs,
I'm here to report this bug/issue because i'm using Win64 Qemu but i can't start a *.abs firmware at normally this firmware is based in Linux Kernel and this type of firmware is made for STB Receivers,
So this is all information i provide to get support.
Files extracted by ( binwalk -e )
Terminal output:
# binwalk -e AMIKO_HD8150_2.4.43_emu.abs
DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
196736 0x30080 LZMA compressed data, properties: 0x6C, dictionary size: 8388608 bytes, uncompressed size: 11883876 bytes
3866752 0x3B0080 LZMA compressed data, properties: 0x6C, dictionary size: 8388608 bytes, uncompressed size: 3255512 bytes
5636224 0x560080 LZMA compressed data, properties: 0x6C, dictionary size: 8388608 bytes, uncompressed size: 87904 bytes
Files extracted with ALI TOOLS or Ali FirmwareDecriptor.
Windows files output:
Software used: Ali Main Code Decrypter 8.9
Files unpacked:
bootloader
MemCfg
maincode(AV)
seecode
default_lang
cipluskey
countryband
logo_user
logo_menu
logo_radio
logo_boot
patch
defaultdb(PRC)
userdb(64+64)
Terminal OUTPUT:
# hexdump -C
part of file
00b51a30 00 00 00 00 4c 69 62 63 6f 72 65 20 76 65 72 73 |....Libcore vers|
00b51a40 69 6f 6e 20 31 33 2e 31 36 2e 30 40 53 44 4b 34 |ion 13.16.0@SDK4|
00b51a50 2e 30 66 61 2e 31 33 2e 31 36 5f 32 30 31 36 31 |.0fa.13.16_20161|
00b51a60 30 31 39 28 67 63 63 20 76 65 72 73 69 6f 6e 20 |019(gcc version |
00b51a70 33 2e 34 2e 34 20 6d 69 70 73 73 64 65 2d 36 2e |3.4.4 mipssde-6.|
00b51a80 30 36 2e 30 31 2d 32 30 30 37 30 34 32 30 29 28 |06.01-20070420)(|
00b51a90 41 64 6d 69 6e 69 73 74 72 61 74 6f 72 40 20 46 |Administrator@ F|
00b51aa0 72 69 2c 20 4a 75 6c 20 32 38 2c 20 32 30 31 37 |ri, Jul 28, 2017|
00b51ab0 20 31 32 3a 35 33 3a 32 38 20 41 4d 29 0a 00 00 | 12:53:28 AM)...|
00b51ac0 44 4d 58 5f 53 33 36 30 31 5f 30 00 00 a1 03 18 |DMX_S3601_0.....|
When I use readelf it says files isn't an ELF file, so i can't run it like a kernel (Bootloader,Maincode, and etc. )
so this is the cmd output when i use qemu Win64 (I don't whant to use linux to do the emulation about this *.abs extension firmware so please help me for win64 version from Qemu)
CMD OUTPUT:
C:\Program Files\qemu>qemu-system-mips.exe -machine mips -cpu mips32r6-generic -drive file=C:\30080.bin,index=0,media=disk,format=raw
qemu-system-mips.exe: warning: could not load MIPS bios 'mips_bios.bin'
I also tried a lot of diferents qemu-system... and a lot of diferent configs like -machine -cpu -kernel -driver root= -PFLASH and etc... and nothing hapenned
How can i reproduce this issue ?
Reply:.
Donwload *.abs firmware in amikoreceiver.com (only *.abs) and download AliDekompressor in http://www.satedu.cba.pl/
Direct tools:
FirmwareDecrypter_v8.9.zip :
http://www.satedu.cba.pl/index.php?action=downloadfile&filename=FirmwareDecrypter_v8.9.zip&directory=Test%20Folder&
Ali__tools_Console_v4.0__CRC_FIXER.rar :
http://www.satedu.cba.pl/index.php?action=downloadfile&filename=Ali__tools_Console_v4.0__CRC_FIXER.rar&directory=Test%20Folder&
so if Qemu can explain how can i fix this issue this can be highly helpfull.
With my best regards,
David Martins
Screamfox
As far as I understand the original description, this was about running an arbitrary firmware in QEMU that has been written for a board that we do not support in QEMU? This can not work. A machine consists of a CPU and various devices that are on board, so you can only run the software that has been written for the CPU and the corresponding devices. If I've got you right, you want to run some software for a board that we do not model in QEMU, so it just can't work since the required devices are not emulated. Thus I'm closing this as "Invalid" now ... unless I've misunderstood your description, then please complain and we can open the ticket again.
Comment #1 from Thomas is correct, this MIPS machine is not modelled.
|