Quote:
Originally Posted by natemcnutty
I am totally stoked by that information. For partition tables, I'm going to take a look into that. What we need at this point is to find out where the NAND starts, position tinboot with the small partition table so it only uses one block, figure out the offset for the rest of it, and put that into the mtdparts command. It's all HEX based for sizes, and is pretty easy to compute. I think following along the way the Vogue does things for now would be good until we can learn why they did them that way :P
Also, I'll try to get info on mtty, and you can always use snoopy pro: Usb Sniffer for Windows | Download Usb Sniffer for Windows software for free at SourceForge.net |
there is really no need right ? We are sending the imgfs in the payload. Vogue adds this separately through tinboot. So we we need to mod our payload and strip the imgfs portion so we can add it to tinboot as well. We can actually use their emtpy imgfs which will just wipe one block. I dont think the partition table on the vogue even matches the mtd parts.
I can try to snoop the mtty tonight and see what the whole flash process looks like.
who isnt working right now? come on someone lets try this !!!