Detailed, in-depth rom/firmware modding guide and instructions - knowledge gathering from elite rom developers and nerds

[bumerc]

Yes i did notice it, and no the dt still have a job here since its controls the size of the super.img.

Yes, but we are talking about a possibility to change the sizes within the super.img group for each partition in it. Super.img is not the problem here

[superceleron]

anyway, i saw the video now, yes i can also do that the issue is it wont boot... ye... and there nothing in serial debug to see where is the issue.

[superceleron]

Yes, but we are talking about a possibility to change the sizes within the super.img group for each partition in it. Super.img is not the problem here

Yes is not the problem here, the problem here is why after all done it wont boot!
Sorry this forum issue is driving me nuts....

[bumerc]

anyway, i saw the video now, yes i can also do that the issue is it wont boot... ye... and there nothing in serial debug to see where is the issue.

With many new devices the TTL logging is deactivated on the bootloader side, that could be the problem. Unless you meant the kernel bootlog + system?

[superceleron]

With many new devices the TTL logging is deactivated on the bootloader side, that could be the problem. Unless you meant the kernel bootlog + system?

In this one i have it enabled, since is my work device.
And nothing, there is not info whatsoever... pity i cant upload(share) the img for sagert to try doing in that tool!
I might try to flash it, but i do not read russian lol....

[superceleron]

ok i decided to try the tool sagert posted and have the exact same issue as me doing it all manually in linux ->bootloop....

[sagert]

There is a program forum but it is in Russian.I don't know much about it et.

https://4pda.ru/forum/index.php?showtopic=900084&st=2100

[superceleron]

There is a program forum but it is in Russian.I don't know much about it et.

https://4pda.ru/forum/index.php?show...900084&st=2100

Ye well, it does not work ok, i mean it works to unpack build etc.. but the super.img built by it does not.. there is something more in to this that i still did not figure it out!
like i said it has something to do with the size of the partitions inside of it.. looks like it expects to always be the size as it was compiled on the sdk!

[sagert]

There are xda themes for super.img. For example:

https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/

[thanghn90]

Wow, I didn't know there are so many new concepts of rom modding hidden from the community. For example, I was never aware of unpacker kitchen, which is a program invoked WITHIN ANDROID to extract a partition image!!! I thought i had to do modding on the img file itself, totally outside of the tv box before. Thanks sagert and bumerc for this info! Will update my first post accordingly.

Also, I'm sure by now you guys already knew SLIMBOX rom (by SlimHouse ). To me, the concept is cool: you flash a general image, and then patch the correct drivers or rom type (ATV vs regular AOSP) for your own box. I think this is the way forward for the modding community, since I believe this is very similar to Google's Project Treble, in which a vendor builds up from a generic AOSP rom and only add their own stuff to the /product and /vendor partition. There are two problems with this: (1) Somehow one SLIMBOX rom threada was removed in freaktab due to copyright violation with Ugoo rom:

https://forum.freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905x3/firmware-roms-tools-ds/803448-rom-slimbox-x3-atv-and-aosp-for-n5max-s905x3

Any idea what the fuss is this about? Just curious...

And (2) googling "SLIMBOX s905x3" reveal an xda thread to a Russian download site (man, I don't even know what the word "download" is in Russian. My hat off to Google Translate):

https://forum.xda-developers.com/t/project-slimbox.4152049/

superceleron : have you considered to take this approach (i.e. adding TWRP "patches" for separate boxes for your rom)?
Related to this, how can we know what wifi and bluetooth vendor/model name, aside from opening the box and put our eyes about an inch close to the pale chip name painting with flash light at and angle and maximum luminosity, not to mention that we need to find the location of the chip the first place? I've searched a lot about this, but most refer to many linux terminal commandsthat could not be run in android terminal.

[superceleron]

There are xda themes for super.img. For example:


https://forum.xda-developers.com/t/s...id-10.4240703/

I will check it, but i do not get my hopes up.

due to copyright violation with Ugoo rom:
https://forum.freaktab.com/forum/tv-...r-n5max-s905x3
Any idea what the fuss is this about? Just curious...

Well Ugoos did copyright claim to FT because is rom(roms) is(are) using Ugoos work.

And (2) googling "SLIMBOX s905x3" reveal an xda thread to a Russian download site (man, I don't even know what the word "download" is in Russian. My hat off to Google Translate):
https://forum.xda-developers.com/t/p...imbox.4152049/
superceleron : have you considered to take this approach (i.e. adding TWRP "patches" for separate boxes for your rom)?
Related to this, how can we know what wifi and bluetooth vendor/model name, aside from opening the box and put our eyes about an inch close to the pale chip name painting with flash light at and angle and maximum luminosity, not to mention that we need to find the location of the chip the first place? I've searched a lot about this, but most refer to many linux terminal commandsthat could not be run in android terminal.

No that wont happen with me, i hardly have the time this days to do any modding, that is why you see less and less roms made by me and when i do it they are very spaced in time.

[sagert]

Perhaps it is necessary to change the sizes of system , vendor in dtb.Also in boot and recovery there is dtb.They are called boot.img-second , recovery.img-second.Or maybe they won't be there.

[sagert]

For simplicity ,if multidtb is there then dtb can be made with it.This is to make it easler to edit.For example if I have 4gb then I left only dtb for 4gb of memory.

[ath156]

Also, I'm sure by now you guys already knew SLIMBOX rom (by SlimHouse ). To me, the concept is cool: you flash a general image, and then patch the correct drivers or rom type (ATV vs regular AOSP) for your own box........................

.............. have you considered to take this approach (i.e. adding TWRP "patches" for separate boxes for your rom)?
Related to this, how can we know what wifi and bluetooth vendor/model name, aside from opening the box and put our eyes about an inch close to the pale chip name painting with flash light at and angle and maximum luminosity, not to mention that we need to find the location of the chip the first place? I've searched a lot about this, but most refer to many linux terminal commandsthat could not be run in android terminal.

Just for the history. I don't think that anybody does this TWRP - patches for a whole firmware or certain partitions - anymore.
It is true that this was the initial way roms of Slimbox (and Vortex) were delivered, but not anymore. Only complete .img files from a version and then.
Also as far as AOSP or ATV, there is a magisk module that can convert your AOSP version to ATV (of course you must have installed magisk to do that!!!!)

[bumerc]

For simplicity ,if multidtb is there then dtb can be made with it.This is to make it easler to edit.For example if I have 4gb then I left only dtb for 4gb of memory.

For this purpose I have created a MOD that allows up to 15 dtbs (combined in a multiwifi-dtb) to be extracted, decompiled, partition sizes to be changed by user input and combined again to multi-dtb at the same time. The script does this job in just a few seconds. This will be available in the next bc-tool update