So this is what is going on? http://gizmodo.com/5656921/t+mobiles...er-a-jailbreak
This is nuts. We need Cyanogen and Modaco to get on this.
Some people (particularly over in the T-Mobile forums) are quoting this post and pointing to the 4407296 number as being proof of a 4G chip and that this means it is somehow accessible to the kernel. I just wanted to clarify that that number is probably simply reporting the size of the mmcblk0 partition in 512-byte blocks since that number happens to be exactly double the number that /proc/partitions reports. Is that a fair assessment of these numbers?
In other words, the only confirmation we have of the 4GB part is the partial teardown that found it and these numbers are simply further ways to confirm that the system only sees 2.1-ish GB of it. Correct?
The size of a write block in the iNAND device is 512B
The iNAND offers the possibility for the host to configure additional split local memory partitions with independent addressable space starting from logical address 0x00000000 for different usage models.
2.9. Enhanced Write Protection
To allow the host to protect data against erase or write, the iNAND supports two levels of write protect command:
• The entire iNAND (including the Boot Area Partitions, General Purpose Area Partition, and User/Enhanced User Data Area Partition) may be write-protected by setting the permanent or temporary write protect bits in the CSD.
• Specific segments of the iNAND may be permanently, power-on or temporarily write protected. Segment size can be programmed via the EXT_CSD register.
For additional information please refer JESD84-A441 standard.
|Thread Tools||Search this Thread|