openATV Forum

... lief vorher schon mal auf der Box) bleibt aber im startbildschrim hängen. Das OpenATv 6.4 lief vorher einwandfrei auf der Box. Klar auch zu erst erase gemacht (image gelöscht) vor jedem installieren. So war meine Vorgehensweise: - Receiver per Netzschalter ausschalten - Powerknopf vorne am R ...

Please let me know a link to a manual of reseting a tuner to default settings and data. All of data, partitions and settings also erase all user data with system slots. Will you call it a reciever not tuner that is a different thing , Have you thought of backing up partitions then delete the enigma2 ...

Please let me know a link to a manual of reseting a tuner to default settings and data. All of data, partitions and settings also erase all user data with system slots.

... protocol family 17 <5>[ 1.950000] Registering the dns_resolver key type <5>[ 1.958000] UBI: attaching mtd3 to ubi0 <5>[ 1.962000] UBI: physical eraseblock size: 131072 bytes (128 KiB) <6>[ 1.962000] usb 1-1: new high-speed USB device number 2 using ehci-brcm <5>[ 1.975000] UBI: logical eraseblock ...

... 2097152 bytes read byte at 0x01000025 (0x00) != byte at 0x04000025 (0x01) Total of 37 bytes were the same MMC erase: dev # 0, block # 40960, count 4096 ... sanitize ... 4096 blocks erased: OK MMC write: dev # 0, block # 40960, count 4096 ... 4096 blocks written ...

... 4096 <5>UBI: good PEBs: 4016, bad PEBs: 0, corrupted PEBs: 0 <5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 <5>UBI: max/mean erase counter: 3/1, WL threshold: 4096, image sequence number: 1918703567 <5>UBI: available PEBs: 0, total reserved PEBs: 4016, PEBs reserved for bad PEB ...

... DDR1 @ 1200MHz, DDR2 @ 1200MHz RESET CAUSE: 0x000003 main_chip_input power_on (2 of 21 possible causes) CS0: SFDP SPI, 4MB, 64kB blocks, 64kB erase block, 256B pages CS1: NAND: unrecognized ID: 0xffffff 0xffffffff RTS0: 0x1101004, 256 clients, ok RTS1: 0x1181004, 256 clients, ok RTS2 ...

... DDR1 @ 1200MHz, DDR2 @ 1200MHz RESET CAUSE: 0x000003 main_chip_input power_on (2 of 21 possible causes) CS0: SFDP SPI, 4MB, 64kB blocks, 64kB erase block, 256B pages CS1: NAND: unrecognized ID: 0xffffff 0xffffffff RTS0: 0x1101004, 256 clients, ok RTS1: 0x1181004, 256 clients, ok RTS2 ...

... 0.262000] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xda <6>[ 0.262000] nand: AMD/Spansion S34ML02G1 <6>[ 0.262000] nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 <6>[ 0.262000] nand: device found, Manufacturer ID: 0x01, Chip ID: 0xda <6>[ 0.262000] nand: AMD ...

... 512MB <6>flashcache: initialize nand flash cache feature. <6>flashstats: Create nand flash statistics interface. <6>flashstats: nand:-read,-write,-erase,-ecc, <5>11 cmdlinepart partitions found on MTD device hinand <5>Creating 11 MTD partitions on "hinand": <5>0x000000000000-0x000000100000 : "boot ...

... 4096 <5>UBI: good PEBs: 1930, bad PEBs: 6, corrupted PEBs: 0 <5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 <5>UBI: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 4241821769 <5>UBI: available PEBs: 0, total reserved PEBs: 1930, PEBs reserved for bad PEB ...

... 1.155000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.155000] nand: Hynix H27U4G8F2DTR-BC <6>[ 1.155000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 <6>[ 1.156000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.156000] nand: Hynix ...

... 1.155000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.155000] nand: Hynix H27U4G8F2DTR-BC <6>[ 1.155000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 <6>[ 1.156000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.156000] nand: Hynix ...

... 1.161000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.161000] nand: Hynix H27U4G8F2DTR-BC <6>[ 1.161000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 <6>[ 1.162000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.162000] nand: Hynix ...

... 1.161000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.161000] nand: Hynix H27U4G8F2DTR-BC <6>[ 1.161000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 <6>[ 1.162000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc <6>[ 1.162000] nand: Hynix ...

... offset: 4096 UBI: good PEBs: 1778, bad PEBs: 6, corrupted PEBs: 0 UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 UBI: max/mean erase counter: 152/88, WL threshold: 4096, image sequence number: 1195924642 UBI: available PEBs: 0, total reserved PEBs: 1778, PEBs reserved for bad PEB ...

... 4096 <5>UBI: good PEBs: 1795, bad PEBs: 5, corrupted PEBs: 0 <5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 <5>UBI: max/mean erase counter: 129/31, WL threshold: 4096, image sequence number: 30333257 <5>UBI: available PEBs: 0, total reserved PEBs: 1795, PEBs reserved for bad ...

... like. If that is the case: Flash a normal image either via online / local (enigma2 gui) or better flash a normal image from recovery menu. Therefor erase everything from your flash drive and extract the normal image. Folder structure should look like this zgemma/h7/imageversion zgemma/h7/kernel.bin ...

... 1.162000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc [ 1.162000] nand: Hynix H27U4G8F2DTR-BC [ 1.162000] nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB siz e: 64 [ 1.163000] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xdc [ 1.163000] nand: Hynix ...

... 4096 <5>UBI: good PEBs: 1778, bad PEBs: 6, corrupted PEBs: 0 <5>UBI: user volume: 1, internal volumes: 1, max. volumes count: 128 <5>UBI: max/mean erase counter: 135/80, WL threshold: 4096, image sequence number: 1250788236 <5>UBI: available PEBs: 0, total reserved PEBs: 1778, PEBs reserved for bad ...