|Latest product reviews|
OK guys based on making a ROM for the 9 G2 I think I discovered why I cant make a update.img that works. It maybe the parameter file not being setup right. But when I do the math as to whats used in the parameter file for .img sizes it is not making any sense. The math is not coming out right? Maybe I am just stupid here or maybe I am just missing something fundamental that I forgot from my old programming days.
To make a long story short. I could not get the 9 G2 rooted so that on next boot it would work. On the stock parameter file System size and offset comes before backup, cache, userdata, kpanic. So when I converted system from cramfs to ext3 it basically triples in size. It went from 65MB to 200MB.
Now I left the parameter file alone and when users flashed it would come up but on the next boot it would hang. So it is obvious when system gets mounted or something it is walking over other partitions????
When I moved the size and offset deffinition for system to the end of the parameter file it worked fine. I assume because at the end it has nothing to walk over? After that comes -user which is NAND. So to make a update.img that might work I figure I have to move system deffinition back to where it belongs in the parameter file and adjust it's size correctly.
OK but here is where the math does not seem to work and let me explain the easy one that gives some details.
So please this is where it is not making sense. In the stock 10 G2 rom the Userdata deffinition was 0x00080000. This gave the unit 256MB of system ram. When I changed that to 0x00100000 it gave us 512MB of ram.
But this is screwy. If you take 80000 hex in decimal that is 524288. If you take 100000 hex that is 1048576. So what gives? The numbers seem to be doubled from what actually is reported!!! What the hell am I missing here?????
So now I want to figure out how to setup the system deff so my new larger system.img has proper space. Math doesnt work here either. The original rom system.img is 65MB. In the parameter file the size deffinition is 0x80000 (524288 decimal). Going by the Userdata that is 256MB right? Well heck 65MB fits easy into that space... My 200MB system.img should also? What gives?
I am going nuts here? Or am I just missing something fundamental?
Thanks guys I really need the help on this one.
One thing :
0x80000 is 512K so size in not expressed in bytes but maybe
in blocks. With a block size of 512 bytes (which is common),
this wouls give you back your numbers
(512 K-blocks would be 256 MB)
For the last part I don't really know. Maybe check that you
use the same 512 B block size in your image ?
Most Users Ever Online: 749
Currently Browsing this Page:
Devices in use: Desktop (145), Phone (12), Tablet (3)
Guest Posters: 43
Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech