Quote:
Originally Posted by natemcnutty
Ours is different than theirs, and they added that emptyimgfs to theirs because they were having issues with the Windows flashing utility. I'm curious what their partition table is for and if that might be the key to what we are trying to do.
My theory right now is that the partition table they use contains the MBR that says where the partitions are, then we point to the beginning of each partition using mtdparts. If we want to change the size of the partitions, we would need to modify the partition table. I'd be worried about having others try this out at messing around with tinboot is a brick risk, and I'm willing to do it since my phone is already screwed up.
Also, I believe Wozzer did this, but anyone willing to get me a mtty bootloader log as explained here:
xda-developers - View Single Post - [android]Tinboot - NAND BOOTLOADER BETA *working*
Edit 2: Guess we also need a full dump of mtd to find out what address it actually starts on. I'm sure Wozzer did a lot of this, but still might be a good thing to double check and start it from the beginning. |
To be honest we never got the real numbers from the bootloader log. I dont even know how to get this bootloader log. I know someone in the blackstone forum did it but we need to find out
Edit: still no luck with that bootloader log. But i did study that os.nb file..
http://pastebin.com/WvksyzNY
Hope it makes sense to you guys. Also Vogue's partition table is really small compared to what we have.
cp partition_table output.nb.payload < --- this is what vogue has while we just use whatever is on git.
Their partition table looks like this (different)
http://pastebin.com/anDEWXud