Hi,
The Meteorit MMB-322.HDTV is an Android based MultimediaPlayer for TV's.
Currently it's mainly selled in Germany and there are many owners which are interested in the Box and in Modding them.
Before we can start building custom Firmwares we need a way to recover the System. We are in contact with the manufacturer and he said, that there is no Software-Recovery. And to update to a new Firmware the system must be bootable.
Because here are many experts in this forum, I hope youcan and want to help us developing a recovery-method like Nandroid or a little NANDFlashMode.
Now all information I already have and which could be useful for you:
I think, the best progress would be, if anyone of you could find out how the boot-partitions(bootloader, bootimgs and bootimgs-B) can be extracted.
Here is the FW-Updatefile: ftp://ftp.pearl.de/treiber/PX1534_12_103600.zip
In the Archive is a file named "ouimg.bin". You can open this and the contained file "ouimg" with 7Zip and then there will be a file ./uniimg/uniimg.bin
This is the file which will be flashed on update. I don't know if it's flashed partially or if this is a direct NAND-Backup.
I hope that you can and do help us.
Best regards,
M1cha
The Meteorit MMB-322.HDTV is an Android based MultimediaPlayer for TV's.
Currently it's mainly selled in Germany and there are many owners which are interested in the Box and in Modding them.
Before we can start building custom Firmwares we need a way to recover the System. We are in contact with the manufacturer and he said, that there is no Software-Recovery. And to update to a new Firmware the system must be bootable.
Because here are many experts in this forum, I hope youcan and want to help us developing a recovery-method like Nandroid or a little NANDFlashMode.
Now all information I already have and which could be useful for you:
- The Partitions MTD-based
- That's the list of MTD-partitions:
dev: size erasesize name
mtd0: 00020000 00020000 "block0"
mtd1: 00100000 00020000 "bootloader"
mtd2: 01900000 00020000 "bootimgs"
mtd3: 01900000 00020000 "bootimgs-B"
mtd4: 00080000 00020000 "u-boot.env"
mtd5: 0c000000 00020000 "system"
mtd6: 08000000 00020000 "userdata"
mtd7: 06800000 00020000 "cache"
mtd8: 00400000 00020000 "factory_setting"
mtd9: 00400000 00020000 "factory_data"
mtd10: 01000000 00020000 "sysconf"
mtd11: 20000000 00020000 "mv_nand" - This are the Kernel-bootargs:
sata_reset_done
nfc_shared
androidboot.console=ttyS0
console=ttyS0,115200
root=/dev/mtdblock5
rootfstype=yaffs2
ro
root_part_name=system
init=/init
mtdparts=mv_nand:131072(block0),
1048576(bootloader),
26214400(bootimgs),
26214400(bootimgs-B),
[email protected](u-boot.env),
[email protected](system),
134217728(userdata),
109051904(cache),
4194304(factory_setting),
4194304(factory_data),
16777216(sysconf)
initrd=0x4e00000,0x47b5a
macaddr=00:25:92:14:47:94 - There is a binary "oureboot" which can reboot the system with adding args to the kernel. This would result in using /2ndinit to boot Linux:
oureboot "init=/2ndinit" - The system-partition is mounted to / and contains everything which normally is located on the ramdisk.
I think, the best progress would be, if anyone of you could find out how the boot-partitions(bootloader, bootimgs and bootimgs-B) can be extracted.
Here is the FW-Updatefile: ftp://ftp.pearl.de/treiber/PX1534_12_103600.zip
In the Archive is a file named "ouimg.bin". You can open this and the contained file "ouimg" with 7Zip and then there will be a file ./uniimg/uniimg.bin
This is the file which will be flashed on update. I don't know if it's flashed partially or if this is a direct NAND-Backup.
I hope that you can and do help us.
Best regards,
M1cha
Last edited: