NEW - R28/R89/HPH Finless 1.2 ROM

[Finless]

Dear Bob,
I know that you said for us not to ask you for other ROMs but will you consider adapt this ROM to the HPH 4Gb / 32Gb box?
Thanks.

Possibly. I think all that is needed is to flash the resource.img from the stock 4gb ROM.
I really do not know what the other differences are as I do not have the 4gb box to test with.

But if you want to try it, get the resource.img from the stock 4gb ROM and replace that file in my ROM kit and try it.

Bob

[mo123]

Dear Bob,
I know that you said for us not to ask you for other ROMs but will you consider adapt this ROM to the HPH 4Gb / 32Gb box?
Thanks.

It's already compatible.
The extra 16GB automatically gets assigned to user.img by the parameter file.
For more compatibility flash resource.img from your stock ROM also.

[Finless]

It's already compatible.
The extra 16GB automatically gets assigned to user.img by the parameter file.
For more compatibility flash resource.img from your stock ROM also.

Yes most ROM's do not care about the extra NAND space. But some will care about the amount of memory. That is defined in resource.img. Since I have never had a 4gb 3288 box yet, I really do not know what happens if the DTD (resource.img) is not correct. Maybe it thinks it only has 2gb?

Mo123, do you know?

Bob

[mo123]

Yes most ROM's do not care about the extra NAND space. But some will care about the amount of memory. That is defined in resource.img. Since I have never had a 4gb 3288 box yet, I really do not know what happens if the DTD (resource.img) is not correct. Maybe it thinks it only has 2gb?

Mo123, do you know?

Bob

I'm also not sure.
I flashed a 4GB/32GB ROM on my 2GB RAM/16 GB ROM box and it worked, so maybe the kernel picks it up automatically just like a PC?
As soon as someone is willing to flash, we'll find out.
The resource.img is important for the wifi and sensor settings that is device specific.
Even if the kernel is universal, works on more than 1 device, there is something else also to consider. The stock remotes might differ from devices and they are inside the kernel, don't know if it has changed from the new 3.10 kernels or are also in the resource.img now?

[Finless]

I'm also not sure.
I flashed a 4GB/32GB ROM on my 2GB RAM/16 GB ROM box and it worked, so maybe the kernel picks it up automatically just like a PC?
As soon as someone is willing to flash, we'll find out.
The resource.img is important for the wifi and sensor settings that is device specific.
Even if the kernel is universal, works on more than 1 device, there is something else also to consider. The stock remotes might differ from devices and they are inside the kernel, don't know if it has changed from the new 3.10 kernels or are also in the resource.img now?

I guess we will both learn as we go...
Right now I only have two 3288 boxes so this leaves me a little light on testing different hardware and remotes with ROMs.

Bob

[bluesmanuk]

It's only for 16GB devices, the 8GB parameter is for 8GB user app space, if you want to flash it on your device, you have to use the 2GB parameter file or you can dump the parameter file of your stock ROM and use that instead. You can use the flash tool to split the stock image file into separate images including parameter file, if your ROM comes as one file, otherwise just replace the seperate parameter file.
All the images except user add up to less than 3GB, the rest ends up as user space until the end of the ROM automatically. If you use the 8GB parameter it will use 9GB space and the rest 7GB end up as user space automatically, so it's more than the 8GB ROM you only have and won't work.

The kernels are usually inside the boot.img. If you flash, all the previous data is erased.
You should keep/dump the boot.img and resource.img from your original ROM image file that should be posted by someone in the forum and use it in combination with the new ROM if the ROM doesn't boot for you. Remember the different parameter file.

My experience from the past has been that it should work.

I had a K-R42 with 8Gb and I flashed a ROM that had both an 8Gb and 16Gb parameter file with no issues.

The flashing process simply formatted all the available space such that I just had 1 partition, which worked perfectly.

It seems that we are also in a rather nice position right now with both having the vendors producing regular ROM updates as well as having Bob and others producing custom ones.

Being spoiled for choice is rather nice

[jacko]

For anyone flashing this rom to a Ugoos UT3 make sure you replace the resource and boot images with the Ugoos official rom ones.
I did this and the not working LED issue i mentioned earlier in this thread is now fixed, not sure which file did it though.

Edit,
The above fixed my LED not working issue but my air mouse now does not work.
So i may have to undo the above, just take note of this.

[mo123]

For anyone flashing this rom to a Ugoos UT3 make sure you replace the resource and boot images with the Ugoos official rom ones.
I did this and the not working LED issue i mentioned earlier in this thread is now fixed, not sure which file did it though.

The resource.img contain the wifi pins, led lights and other sensors.
So it seems the HPH & Ugoos UT3 does have minor differences.
The different remotes will work with a different boot.img(with kernel).
These kernels(boot.img) are universal and work on all devices which is nice, everyone can use their stock resource.img to make their box specific settings work, no need for 100's of custom kernels anymore.

[Finless]

Only thing is in my ROM I removed kernel from boot.img so other kernels could be used without changing boot.img which is where some of my tweaks are like adding init.d, tcpip buffers etc, etc.

Good chance if you used the boot.img from ugoos then you now are running the ugoos kernel (because the kernel is probably in boot.img) AND you have lost all the tweaks I made in boot.img

As mo123 said. What you should try is keeping my boot.img and flashing the resource.img from the ugoos ROM.

Bob

[jacko]

Thanks guys.
Ok guys read my edit above.
I am going to try just the resource file from Ugoos UT3 and Bobs Boot image.
Will report back soon.

[jacko]

Ok guys just flashed Bobs full rom with the UT3 resource image and the box does not boot at all.
Very strange as if i use Bobs rom and boot and resource images from UT3 official rom the box boots and works fine apart from my air mouse does not work, maybe the USB ports have stopped working. .. forget about the airmouse not working i took the battery out of it and it reset .. all is ok with it now.

Edit,
I have just put your full rom back on Bob, all Ok again.
Maybe someone can look at the resource file of the UT3.
If i flash bobs rom and resource and boot images from UT3 everything works but i lose bobs boot image tweaks.
Maybe the boot and resource files are tied together somehow ?????
I will mess around and see if i can solve anything.

[Moulin1980]

Hi all, the new ROM ( R28/R89 HPH 3288 TV Box - Finless 1.2 ROM ) is for :

Tronsmart-Orion-R28-Pro -> wifi AP6210
or
Tronsmart-Orion-R28-Meta -> wifi AP6335

Thank you in advance for any answers.

[blinkone]

Hi all, the new ROM ( R28/R89 HPH 3288 TV Box - Finless 1.2 ROM ) is for :

Tronsmart-Orion-R28-Pro -> wifi AP6210
or
Tronsmart-Orion-R28-Meta -> wifi AP6335

Thank you in advance for any answers.

It should work with both.

[jeffben]

uboot.img is not used. It was not in the 110K4109.
I do not know what uBoot partition is used for as every box I have dumped to date that has been empty. Also there is a new partition called radical_update. That so far is also unused. So it's possibly there for something later or maybe for manufacturing / debugging.

For you 8gb guys, I can make a 6mb parameter file if you like. Let me know.

Bob

Yes please. Again thank you for this rom. Could it be also used on The Bluetimes RK3288 box?

[jacko]

Thanks for the help and support of,
Finless
mo123
shomari

I can comfirm that for flashing the Finless 1.2 rom to a UGOOS UT3 you need to swap the following files in the Finless rom with the same files from the official Ugoos UT3 rom,

kernel.img
misc.img
resource.img

Then you will have all the goodness of the Finless rom but with the UT3 kernel and LED working as it should.
So thanks to all 3 of you.
I now know what to do for future custom rom updates for my Ugoos UT3.
Hope the above info helps other Ugoos UT3 users.