building firmware has smaller files to cutting the ROM, how does it effect partition?
building firmware has smaller files to cutting the ROM, how does it effect partition?
(16-09-2020, 03:03 PM)wilemansion when using WWR to process the ROM dump, the build firmware produces much smaller .img/.bin files in contrast to cutting the ROM. Once flashed onto the device, does this re-adjust the partition tables (PGPT) to accommodate difference file sizes?
(17-09-2020, 10:46 AM)X3non(16-09-2020, 03:03 PM)wilemansion when using WWR to process the ROM dump, the build firmware produces much smaller .img/.bin files in contrast to cutting the ROM. Once flashed onto the device, does this re-adjust the partition tables (PGPT) to accommodate difference file sizes?
there's a tooltip for each option when you place the mouse over
build clean firmware trims trailing zeroes, so you get a smaller file (take note that the content of a partition isn't usually the full partition size, a good example could be seen from preloader with partition size 4mb but real content only a few kbs)
cut the rom as it is doesn't trim trailing zeroes, so you get the full partition size
either one doesn't affect pgpt in any way,
(19-09-2020, 01:30 AM)wilemansion so if we flash a custom rom where its' system.img is larger in size than the previous system.img , what happens to the pgpt?