Have a quick look at the x250 and x260 firmware, it looks like they are both ARC cpus with a similar layout. They both have different checksumming than the xx30 range and the x260 looks like it is not even encrypted (however there is a strange 256byte block at the top of the file - perhaps a signature)

update
Hamish Coleman 8 years ago
parent aebedc8623
commit 9a9dc36289

@ -92,9 +92,13 @@ mec-tools/mec_encrypt: mec-tools/Makefile
# - most of these dependancies could be automatically calculated
x220.8DHT34WW.s01CB000.FL2.slice: 8duj27us.iso.orig
x230.G2HT35WW.s01D3000.FL2.slice: g2uj23us.iso.orig
x250.N10HT17W.s01E5000.FL2.slice: n10ur10w.iso.orig
x260.R02HT29W.s0AR0200.FL2.slice: r02uj46d.iso.orig
x220.8DHT34WW.img.enc.slice: x220.8DHT34WW.s01CB000.FL2.orig
x230.G2HT35WW.img.enc.slice: x230.G2HT35WW.s01D3000.FL2.orig
x250.N10HT17W.img.enc.slice: x250.N10HT17W.s01E5000.FL2.orig
x260.R02HT29W.img.slice: x260.R02HT29W.s0AR0200.FL2.orig
t430.G1HT35WW.img.enc.slice: g1uj38us.iso.orig
t430s.G7HT39WW.img.enc.slice: g7uj18us.iso.orig

@ -0,0 +1 @@
0e4c4ffb99146e50867dc1345ee2ef88c60ea192 n10ur10w.iso.orig

@ -0,0 +1 @@
876a68add32d9c961cbdf80c74b88f92a66443cf r02uj46d.iso.orig

@ -0,0 +1 @@
x250.N10HT17W.s01E5000.FL2.orig 0x20 196608

@ -0,0 +1 @@
0732e80cddd0efcca9ba72dcfbdd0110d3c29dae x250.N10HT17W.s01E5000.FL2.orig

@ -0,0 +1 @@
n10ur10w.iso.orig 0x0083e000 196896

@ -0,0 +1 @@
x260.R02HT29W.s0AR0200.FL2.orig 0x20 286720

@ -0,0 +1 @@
35a9b0d623fea82a440aae816a91da2cb18f6801 x260.R02HT29W.s0AR0200.FL2.orig

@ -0,0 +1 @@
r02uj46d.iso.orig 0x00210e00 286752
Loading…
Cancel
Save