Help
previous post moded because nonsense detected
.well i have been checking around the t9 firmware agains its effects on the internal microsd card.
firmware contains 3 important files:
u-boot.bin ( in whatever version of it ex. u-boot-929.bin )
boot.img (inside the update.zip )
system.img (inside the update.zip )
now, i was checking the tasselhof's backup image ( from a previous firmware, by the way
thanks so much for that file, its really handy )
i have somehow found out the following.
the first 512K of the image/microsd card are in tasselhof's image zeros 00, in my microsd
have some random values, however, i think they are partitioning information.
comparing u-boot-0929.bin to other boot.img files from similar devices it seems that
T9 u-boot its only the bootloader (it doesn't contain the initial 512 bytes).
there maybe some bootloaders bin files that contains this first 512 bytes and flashing them
will overwrite previous partition information ( i think that is why partitions were
erased/created in the internal microsd card and lost the size moddings ).
the bootloader begins with 00 20 then somewhere next to those values there is a `
and a xV4 (in hexadecimal ), that is the beggining of the bootloader which is
located exactly after the first 512 bytes of the microsd.
after the bootloader i have been unable to identify what is written, it seems
the boot.img file has some "fastboot special format" as the command fastboot knows
how to read it and what to write, but it seems what ever it writes i does it after
the 512 bytes + bootloader size (about 385KB).
then about 43MB later there is the first partition "system" that is basically
the system.img file contained in the update.zip ( system.img is an ext3/4 partition image ).
now it seems fastboot does search for a partition labeled system to write the system.img file
into the right partition.
after the system partition there is the data partition ( which contains some other files
and it is also an ext3/4 partition and it is considered by the T9 as "internal storage" ).
in tasselhofs image it is 385MB in my original microsd it was 800MB.
this is where the apps are installed that are considered in phone memory.
after data partition its the cache partition ( about 108 MB )its basically an ext3/4 partition
for temporal data
and last there is a FAT32 partition ( the user data partition ), this one contains the files
you see when you plug your device to your PC for use as a removable device.
it contains a lot of settings files, app defined directories, etc. basically its where your
"user profile lives".
now there is something weird, the physicall order of partitions doesn't match.
fat32 is partition 1
system is partition 2
data is partition 3
cache is partition 4
at least in the tasselhof's backup image ...
i want to create a "depured" 2.3 backup image that is ready to image and use,
i have already bouth an 16GB class 10 microsd and a 4gb class 4 extra microsd
when i am done with them, i will publish the files for all of you interested.
best regards.
This post has been edited by miguel.arce: 02 November 2011 - 01:30 AM
hard to get so far...
