Modded ROM's for Tronsmart R68 "Tronsplant your ROM"

[lonix]

Yes I am a real dummy not to figure that one out sooner. On the Tronsmart forums there was one person, Mikael that had almost 5 or 6 extremely long posts with great detail on what exactly he had done, and could not figure out why he could not get the device to be recognized at all in windows and I wonder if he did the same thing as me or not?


I just want to ask when the device is off will the remote power button serve to power up the device? I tried a couple of times and the power button seems to only power down the device.

No, unfortunately unless you leave it in standby.

[androidfr33k]

Its included, no need to flash.

Lol, the cable that comes with the tronsmart is an OTG cable it has pin5 grounded which puts the device into host mode.

As you found out you need a regular microUSB cable. LOL

Yes I am a real dummy not to figure that one out sooner. On the Tronsmart forums there was one person, Mikael that had almost 5 or 6 extremely long posts with great detail on what exactly he had done, and could not figure out why he could not get the device to be recognized at all in windows and I wonder if he did the same thing as me or not?


I just want to ask when the device is off will the remote power button serve to power up the device? I tried a couple of times and the power button seems to only power down the device.

[lonix]

Is the Activation Fix part of Release 9 v2 or I need to still run the activation fix?

Its included, no need to flash.

Lol, the cable that comes with the tronsmart is an OTG cable it has pin5 grounded which puts the device into host mode.

As you found out you need a regular microUSB cable. LOL

[androidfr33k]

Is the Activation Fix part of Release 9 v2 or I need to still run the activation fix?

[androidfr33k]

You should be able to flash system from twrp, have a look inside the 9.2 flashabe zip, there is a file called updater-script have a read of that, you can change things around and flash any partition with any file.

To enter bootloader on r68, plug in usb to pc and power cord, then use a toothpick press the small hole then press power button

Weird it keeps going to recovery when I do that. I checked with HDMI cable. I tried with HDMI cable and without. I'll keep trying. I did try boot to bootloader partition from Tronsmart Recovery partition but I can only get it to do that if I plug in a keyboard. The remote will not. Actually the power button seems to serve as an enter button if I am not mistaken? I will continue to try but if I cannot get this to work I have to return this one that I just got in today and just get a second Zidoo R6 Pro



Edited:
OMG!!!! The USB cable included with the Tronsmart is Garbage!! I used my micro USB cable to USB from my Nexus 7 2013 Android tablet and immediately worked. Very sorry for all the confusion.

[Stzo]

If that doesn't work just put the script directly into /system/bin

Hi lonix,

Putting the script into the bin directory resulted in successful install of TWRP. Why did you make this simlink and put the script into the etc directory?

What is strange, however, when entering TWRP, the file manager cannot see any file in the directories (except the root and the external SD card), and when attempting to reboot, it tells me "no OS on the device, am I sure that want to reboot"? It reboots flawlessly otherwise. Is this the normal operation? I dont remember yet how it was previously... The install section of TWRP seems working, here it sees the files (zips and imgs) as expected. I'm not sure I may use it now...

Regards,
STZO

[lonix]

Hi lonix, I managed to get a working firmware for my Z4 wich looks like not to suffer from the HDMI-handshake problem (yeah!) It is a combination of the Z4_UGOOS_MOD_V1.2 firmware and the Tronsmart kernel + resource (L206). It looks like to work all great, but the moment I disconnect the USB cable between my laptop and the TV box, the tv box switches off....

I tried also the kernel of the first Tronsmart firmware (L105), and it behaves exactly the same. Do you have an explanation for this?

Its something with the kernel + resource, i have noticed that with stock Tronsmart Kernel on r68 it allows the usb port to power the device but not turn it on, for example if i plug the power and usb then switch the r68 on, i can unplug the power cord and the r68 will remain powered by the usb port, only happens with stock kernel though.

Must be something to do with the power regulator drivers

[lonix]

Guest


Thanks again for sharing your great work. Can you go over some of the questions I had a couple posts back. Mainly about the UBoot, a full rom version zip installable format for TWRP and a link to amazon, wanted to know if this was the device you had and if this is the common device most people buy at least in this thread? If not is this fully supported with your Rom, kernel and all? When I opened mine up it did have a sticker in there saying it was the 1000mbit ethernet chip.

Well this makes no sense. I got the new R68 Tronsmart in today and same problem it will not make any connection to PC via OTG/Usb? Is there a way to go straight into the bootloader rather then getting there from recovery? This has vanilla stock rom from factory.

Thanks

You should be able to flash system from twrp, have a look inside the 9.2 flashabe zip, there is a file called updater-script have a read of that, you can change things around and flash any partition with any file.

To enter bootloader on r68, plug in usb to pc and power cord, then use a toothpick press the small hole then press power button

[lonix]

Hi again,

Permission of the symlink file is 777 and cannot be changed, it should make no problem. Permission of file in the etc directory set to 755 as you suggested.
I'm almost sure however, that the problem is with the symlink itself. Probably the file is changing during the unpacking/repacking of the ROM, and it will not remain a symbolic link anymore.

I'll try it yet with changing the file name to install-recovery-2.sh, and modify the link accordingly (or newly create it from the terminal), maybe that helps. I'll come back with the results.
Btw.: which software you use to pack the firmware?

Best regards,
STZO

If that doesn't work just put the script directly into /system/bin

[JosD]

Hi lonix, I managed to get a working firmware for my Z4 wich looks like not to suffer from the HDMI-handshake problem (yeah!) It is a combination of the Z4_UGOOS_MOD_V1.2 firmware and the Tronsmart kernel + resource (L206). It looks like to work all great, but the moment I disconnect the USB cable between my laptop and the TV box, the tv box switches off....

I tried also the kernel of the first Tronsmart firmware (L105), and it behaves exactly the same. Do you have an explanation for this?

[androidfr33k]

lonix


Thanks again for sharing your great work. Can you go over some of the questions I had a couple posts back. Mainly about the UBoot, a full rom version zip installable format for TWRP and a link to amazon, wanted to know if this was the device you had and if this is the common device most people buy at least in this thread? If not is this fully supported with your Rom, kernel and all? When I opened mine up it did have a sticker in there saying it was the 1000mbit ethernet chip.

Well this makes no sense. I got the new R68 Tronsmart in today and same problem it will not make any connection to PC via OTG/Usb? Is there a way to go straight into the bootloader rather then getting there from recovery? This has vanilla stock rom from factory.

Thanks

[Stzo]

yes, in 9.2 i moved the script to /system/etc/install-recovery-2.sh, to play nice with supersu please make sure that the symlink exists between /system/bin/install-recovery.sh and /system/etc/install-recovery.sh.

and also make sure that both /system/etc/install-recovery.sh and /system/etc/install-recovery-2.sh have 755 permissions.

Hi again,

Permission of the symlink file is 777 and cannot be changed, it should make no problem. Permission of file in the etc directory set to 755 as you suggested.
I'm almost sure however, that the problem is with the symlink itself. Probably the file is changing during the unpacking/repacking of the ROM, and it will not remain a symbolic link anymore.

I'll try it yet with changing the file name to install-recovery-2.sh, and modify the link accordingly (or newly create it from the terminal), maybe that helps. I'll come back with the results.
Btw.: which software you use to pack the firmware?

Best regards,
STZO

[lonix]

Hi lonix,

In 8.3 this is the install-recovery.sh in the etc directory:

#!/system/bin/sh

if [ ! -e /data/twrp.installed ]; then
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/ff0f0000.rksdmmc/by-name/recovery
touch /data/twrp.installed
fi

and this is in the bin directory:

㰡祳汭湩㹫 /system/etc/install-recovery.sh

install-recovery-2.sh is in v9.2 only, otherwise that's the same as above, in the etc directory. (Chilese characters may be due to the encoding only, I can see latin characters when opening the file on the android device.)

I checked the access rights, all are correct, but twrp does not install at the boot. I did not flash the whole rom again, I just wanted to have twrp installed with rebooting the device.
I also checked the data directory: file "kodi.installed" exisits, but file "twrp.installed" doesn't. File "system.notfirstrun" exists too, so I assume, the preinstall script have run successfully.

Maybe, simply flashing twrprecovery.img with android tool, wouldn't it do?

Best regards,
STZO

yes, in 9.2 i moved the script to /system/etc/install-recovery-2.sh, to play nice with supersu please make sure that the symlink exists between /system/bin/install-recovery.sh and /system/etc/install-recovery.sh.

and also make sure that both /system/etc/install-recovery.sh and /system/etc/install-recovery-2.sh have 755 permissions.

[Stzo]

Sorry, just remembered, please check the script at /system/etc/install-revovery-2.sh

Hi lonix,

In 8.3 this is the install-recovery.sh in the etc directory:

#!/system/bin/sh

if [ ! -e /data/twrp.installed ]; then
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/ff0f0000.rksdmmc/by-name/recovery
touch /data/twrp.installed
fi

and this is in the bin directory:

㰡祳汭湩㹫 /system/etc/install-recovery.sh

install-recovery-2.sh is in v9.2 only, otherwise that's the same as above, in the etc directory. (Chilese characters may be due to the encoding only, I can see latin characters when opening the file on the android device.)

I checked the access rights, all are correct, but twrp does not install at the boot. I did not flash the whole rom again, I just wanted to have twrp installed with rebooting the device.
I also checked the data directory: file "kodi.installed" exisits, but file "twrp.installed" doesn't. File "system.notfirstrun" exists too, so I assume, the preinstall script have run successfully.

Maybe, simply flashing twrprecovery.img with android tool, wouldn't it do?

Best regards,
STZO

[Stzo]

Hi lonix,

In 8.3 this is the install-recovery.sh in the etc directory:

#!/system/bin/sh

if [ ! -e /data/twrp.installed ]; then
dd bs=1024 if=/system/twrp/twrprecovery.img of=/dev/block/platform/ff0f0000.rksdmmc/by-name/recovery
touch /data/twrp.installed
fi

and this is in the bin directory:

㰡祳汭湩㹫 /system/etc/install-recovery.sh

install-recovery-2.sh is in v9.2 only, otherwise that's the same as above, in the etc directory. (Chilese characters may be due to the encoding only, I can see latin characters when opening the file on the android device.)

I checked all access rights, all are correct, but twrp does not install at the boot. I did not flash the whole rom again, I just wanted to have twrp installed with rebooting the device.
I also checked the data directory: file kodi.installed exisits, but file twrp.installed doesn't. File system.notfirstrun is existing too. By studying the scripts I assume, file twrp.installed should be available in the data directory to have the script run successfully. Is it?

Or maybe, simply flashing twrprecovery.img with android tool, wouldn't it do?

Best regards,
STZO

(quoting still dont work...)