today I was searching the global RST line and looked more exactly on J66. 10 9 8 7 6 1 2 3 4 (5) If you look from top the right bottom pin is missing, pinout is as follows: Pin1 - +3V3 Pin2 - IR-reciever to PIC PIN41 Pin3 - GND Pin4 - D7 LED(green) to PIC PIN2 Pin6 - GND Pin7 - D8 LED(green) to PIC ...

it is possible to boot the kernel with qemu if the header is deleted i also tried to boot the cefdk-logitech_ka3.bin included inside 439c26f6af05.mp-signed-ota_update-b39389.zip but that doesn't work out of the box (deleted the first 0x480 bytes) as far as I see. Inside this cefdk are strings contai...

if you take the kernel.img for example out of an update (not the honeycomb one) then the structure is as follows: from 0x00 to 0x18 the pattern is equal, 3 bytes which looks like the total size (but a bit bigger !?!), then 0x1c to 0x47f is also equal! The following pattern is maybe a hash or signing...

a boxee would also be great because maybe it is possible to boot the boxee filesystem on revue ...
but therefore a complete nand dump is neccesary!

the bash script in the post before could be used for dumps which have no ecc data! I think (because of this link, http://www.anandtech.com/show/4029/the-boxee-box-review/3 ) that the internal NAND controller of the SoC is using BCH ECC. But can't try it, because my dump hasn't any ecc data at all. t...

here maybe a helpful script to split the dump! #!/bin/bash # copyright: pcgeil # (c) 2011 progged for GTV revue dumpFile="nand.dump" outputDir="dump" outputName=${outputDir}"/test" # bash check if directory exists if [ -d $outputDir ]; then echo "Directory exists&q...

Just another short update: Some Information about the GTV filesystem is written here: http://gtvhacker.com/index.php/GTV_FileSystem I don't know if anyone dumped the nand before to get some of these information. So what I can confirm is that: 1. 0x00a00000-0x00c00000 "redboot" All FF's but...

i managed it to get a dump of the samsung nand
but till now, I do not know if the dump is correct.

Maybe on monday i will be able to check if the dump is complete and try to update to honeycomb and dump again.

Hi, do we have total access to the 1GB NAND from the recovery mode? Which part is blocked? Why isn't it possible to replace the "normal" kernel by the recovery kernel? I mean the recovery kernel is able to load modules as far as I now. Can't we write the "normal" kernel directly?...

Update, my setup with Yamaichi IC191-0482-004 is ready.
I hope I can desolder the NAND this weekend and then I try to dump it