factory default firmware images?

[gizmomelb]

hi all,

is it possible to image the factory default firmware?

ie: connect it to the OTG before you've ran the configuration the first time and copy the firmware image?

also is there any point in doing so (my question is related to if you flash custom firmware, can you get it back to an ''out of the box'' default configuration)?

if this is useful - then is it possible to have / build a repository of Beelink, Tronsmart etc. factory firmware?


I have an unopneed Beelink M8, which I'm happy to image if it is (a) possible and (b) someone can point me to directions on how to do it.

thank you.

[no_spam_for_me]

Beelink AML devices - M8, etc

Tronsmart AML Devices

[Finless]

You can dump the ROM by using ADB. If you have ADB setup, I can tell you how to dump the ROM.

Bob

[gizmomelb]

You can dump the ROM by using ADB. If you have ADB setup, I can tell you how to dump the ROM.

Bob

Hi Bob, I do have ADB - if you have the time and don't mind explaining, I'm happy to dump my factory default firmware and assist wherever I can at the moment.

regards

[Finless]

OK from ADB open a command shell

adb shell

then from that do these commands so we can see partitions and what to dump.

cat /proc/mtd

and

cd /dev/block
ls

Show me what both lists say.

Bob

[JustMe]

OK from ADB open a command shell

adb shell

then from that do these commands so we can see partitions and what to dump.

cat /proc/mtd

and

cd /dev/block
ls

Show me what both lists say.

Bob

Bob I will also try this on my new M8 in next few days apparently all woes have been fixed curious to see what the difference is from Acemax's new firmware released yesterday

JustMe

[Finless]

Bob I will also try this on my new M8 in next few days apparently all woes have been fixed curious to see what the difference is from Acemax's new firmware released yesterday

JustMe

Yes... I am going to flash that new firmware on the S89 but not the bootloader since that bricks the S89.
If it is better than the Tronsmart firmware I will make a ROM.
Seems like 5G is working on the acemax ROM?

Bob

[JustMe]

Yes... I am going to flash that new firmware on the S89 but not the bootloader since that bricks the S89.
If it is better than the Tronsmart firmware I will make a ROM.
Seems like 5G is working on the acemax ROM?

Bob

My friend flies back from china this Friday the wifi issue were sorted on the 23rd of this month. from what my friend said when he visited the factory

Once I dump you can test it and compare it between acemax's and this firmware
JustMe

[gizmomelb]

OK from ADB open a command shell

Show me what both lists say.

Bob

Hi Bob,

my apologies for the slow response, been a busy weekend.

I was going to try to image the unused Beelink device I have, but of course I need to power it on, enable Dev mode, enable USB debug etc. so there's no way I can rip the 'factory image' from it.

cat /proc/mtd
dev: size erasesize name
mtd0: 00060000 00001000 "bootloader"
mtd1: 00010000 00001000 "ubootenv"



cd /dev/block
root@k200:/dev/block # ls
ls
boot
cache
data
logo
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
misc
mtdblock0
mtdblock1
recovery
system
vold
zram0

what next please?

[Finless]

OK so here is what you do next.

From shell type this:

dd if=/dev/block/boot of=/sdcard/boot.img
dd if=/dev/block/logo of=/sdcard/logo.img
dd if=/dev/block/system of=/sdcard/system.img
dd if=/dev/block/recovery of=/sdcard/recovery.img
dd if=/dev/block/mtdblock0 of=/sdcard/bootloader.img
dd if=/dev/block/mtdblock1 of=/sdcard/ubootenv.img

You will now have all the images and these an be made into a update.zip.
But this is where a lot more about how to make zip's come in! You need the tools and you also need Linux to mount system.img and pull out all the files.

Bob

[JustMe]

OK so here is what you do next.

From shell type this:

dd if=/dev/block/boot of=/sdcard/boot.img
dd if=/dev/block/logo of=/sdcard/logo.img
dd if=/dev/block/system of=/sdcard/system.img
dd if=/dev/block/recovery of=/sdcard/recovery.img
dd if=/dev/block/mtdblock0 of=/sdcard/bootloader.img
dd if=/dev/block/mtdblock1 of=/sdcard/ubootenv.img

You will now have all the images and these an be made into a update.zip.
But this is where a lot more about how to make zip's come in! You need the tools and you also need Linux to mount system.img and pull out all the files.

Bob

how about square m8 rom dump?

[gizmomelb]

how about square m8 rom dump?

you can do that if you want

ok Bob - here's the output:


C:\Windows\system32>adb shell
root@k200:/ # dd if=/dev/block/boot of=/sdcard/boot.img
dd if=/dev/block/boot of=/sdcard/boot.img
65536+0 records in
65536+0 records out
33554432 bytes transferred in 4.241 secs (7911915 bytes/sec)
root@k200:/ # dd if=/dev/block/logo of=/sdcard/logo.img
dd if=/dev/block/logo of=/sdcard/logo.img
65536+0 records in
65536+0 records out
33554432 bytes transferred in 4.407 secs (7613894 bytes/sec)
root@k200:/ # dd if=/dev/block/system of=/sdcard/system.img
dd if=/dev/block/system of=/sdcard/system.img
2097152+0 records in
2097152+0 records out
1073741824 bytes transferred in 164.878 secs (6512341 bytes/sec)
root@k200:/ # dd if=/dev/block/recovery of=/sdcard/recovery.img
dd if=/dev/block/recovery of=/sdcard/recovery.img
65536+0 records in
65536+0 records out
33554432 bytes transferred in 4.726 secs (7099964 bytes/sec)
root@k200:/ # dd if=/dev/block/mtdblock0 of=/sdcard/bootloader.img
dd if=/dev/block/mtdblock0 of=/sdcard/bootloader.img
768+0 records in
768+0 records out
393216 bytes transferred in 1.583 secs (248399 bytes/sec)
root@k200:/ # dd if=/dev/block/mtdblock1 of=/sdcard/ubootenv.img
dd if=/dev/block/mtdblock1 of=/sdcard/ubootenv.img
128+0 records in
128+0 records out
65536 bytes transferred in 0.070 secs (936228 bytes/sec)
root@k200:/ #

files copied to my Windows PC, I can possibly set up a VM player for some *nix install