Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

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

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    im sorry to ask again, but when i connect the device the program recognize it, then swith the device to what i supouse its the bootloader, where it said that the device its found but i can not read or write anything. I always read the messae faild. What i'm missing?

    pd: allready solve, parently i cannot read but i can write.
    one more thing, anyone how can give a info on how ir remote work and how can be modify?
    Last edited by harry_arg; 23 March 2016, 03:26.

    Comment


      lonix ,

      How are you doing. I cannot get the Tronsmart R68 ADB tool nor the Factory tool to work in windows 10 since the driver will not load when the device is connected. IT just does not recognize this device when I plug it into the USB port. The Zidoo R6 connects immediately so its not the driver issue. Is there some setting in TWRP or in the settings from the OS that needs to be enabled? Until I get this to work I cannot ever do a clean install unless you have a v9 r2 full version that can be updated through TWRP? Then I can wipe everything and install the Full version from there until I figure out exactly why this device will not be recognized.

      Uninstall and Re-install of the Factory Tool Driver Assistant USB driver installer just is not working is why I think something is wrong with the kernel or settings. Maybe OTG/Usb Port broken, although If I put a flash drive on the OTG cable its recognized no problem after it boots into Android OS.

      Thanks
      Last edited by androidfr33k; 23 March 2016, 06:18.

      Comment


        Originally posted by Stzo View Post

        Hi lonix,

        Thank you for the advices, I'll check the install-recovery.sh this night. (I'm in CET.)
        Also thanks for sharing the Rockchip tool to flash the MAC address. I'm looking forward couriously. Shall I build it into the ROM, or how it works?

        Best regards,
        STZO
        Hi lonix,

        Thank you for the flashtool! I assume, the previously written MAC address was cleared for some reason when I flashed 8.3, and now I have to re-flash it again with this tool. Do you know why it could have been cleared?

        I checked install-recovery.sh, this exists in both packages, and the contents of them are the same (in two existances at different locations, with different contents at each location). Also localized twrprecovery.img in both packages. Despite of these existances, TWRP was not flashed, similarly to some other programs that were dropped into the preinstall directory. Is it possible if one of the apps here cannot be installed (install fails), the remaining apps will be omitted? Is it possible to change the order of which the apps are installed (on the first boot probably)?

        Thank you again, with best regards
        STZO

        (Yesterday night the forum was unreachable...)
        Regards, STZO

        Comment


          THIS ROM IS AWESOME!

          newest kodi with rockchipencoder, no stuttering, twrp/root all is there, and working nicely.
          spdif no stuttering.


          thank you so mutch!

          Comment


            Hi I have suceesfully downloaded and installed the latest package from Tronsmart for R68G (206L1). I found the box is snappier. I don't really have many problems except for odd Stutter

            A couple of questions 1) How much better is this Rom then Tronsmart

            clarify steps 2) Do I have to first install v8 rev 3 FULL ROM 1st

            Then install v9 rev 2 FULL ROM 2nd

            I'm not sure of the terms you use when you talk about just Kernel and if I flash the Full Rom is the Kernel part of the Full Rom etc.

            Comment


              Originally posted by Stzo View Post

              Hi lonix,

              Thank you for the flashtool! I assume, the previously written MAC address was cleared for some reason when I flashed 8.3, and now I have to re-flash it again with this tool. Do you know why it could have been cleared?

              I checked install-recovery.sh, this exists in both packages, and the contents of them are the same (in two existances at different locations, with different contents at each location). Also localized twrprecovery.img in both packages. Despite of these existances, TWRP was not flashed, similarly to some other programs that were dropped into the preinstall directory. Is it possible if one of the apps here cannot be installed (install fails), the remaining apps will be omitted? Is it possible to change the order of which the apps are installed (on the first boot probably)?

              Thank you again, with best regards
              STZO

              (Yesterday night the forum was unreachable...)
              Please ensure the scripts have the linux 755 permission set and all apk 644

              Also on Tronsmart and beelink devices MAC was never set from factory, so they wrote a script that sets it in android every boot
              Last edited by lonix; 23 March 2016, 23:42.

              Comment


                Originally posted by androidfr33k View Post
                Guest ,

                How are you doing. I cannot get the Tronsmart R68 ADB tool nor the Factory tool to work in windows 10 since the driver will not load when the device is connected. IT just does not recognize this device when I plug it into the USB port. The Zidoo R6 connects immediately so its not the driver issue. Is there some setting in TWRP or in the settings from the OS that needs to be enabled? Until I get this to work I cannot ever do a clean install unless you have a v9 r2 full version that can be updated through TWRP? Then I can wipe everything and install the Full version from there until I figure out exactly why this device will not be recognized.

                Uninstall and Re-install of the Factory Tool Driver Assistant USB driver installer just is not working is why I think something is wrong with the kernel or settings. Maybe OTG/Usb Port broken, although If I put a flash drive on the OTG cable its recognized no problem after it boots into Android OS.

                Thanks
                Has it worked on this pc before?
                In windows does it make the sound when you insert the usb?
                You can flash the kernel with twrp, although i would consider being extremely cautious as you do not have any other recovery options

                Comment


                  Originally posted by lonix View Post

                  Has it worked on this pc before?
                  In windows does it make the sound when you insert the usb?
                  You can flash the kernel with twrp, although i would consider being extremely cautious as you do not have any other recovery options


                  If I remember correctly it worked in all of the versions of 7 and 8. I tried to connect on a mac no go there either. I did update to 9v2 along with the kernel you posted via TWRP method and its running fine. But I just wanted to do a clean install with the Factory tool. Is it working for you? Can anyone else try to see if at least a connection (sound) is made when you connect to a PC with the OTG/Usb connection after updating to version 9.

                  Thanks

                  Comment


                    Originally posted by androidfr33k View Post



                    If I remember correctly it worked in all of the versions of 7 and 8. I tried to connect on a mac no go there either. I did update to 9v2 along with the kernel you posted via TWRP method and its running fine. But I just wanted to do a clean install with the Factory tool. Is it working for you? Can anyone else try to see if at least a connection (sound) is made when you connect to a PC with the OTG/Usb connection after updating to version 9.

                    Thanks
                    Use quickboot to reboot to bootloader, the kernel can in no way affect bootloader mode

                    If your pc cannot detect your device in bootloader mode it means there is another problem possibly bad solder on the otg port.

                    Rockchip devices are virtually unbrickable, unless you flash the wrong loader, and even then its recoverable

                    Comment


                      Originally posted by robot20 View Post
                      Hi I have suceesfully downloaded and installed the latest package from Tronsmart for R68G (206L1). I found the box is snappier. I don't really have many problems except for odd Stutter

                      A couple of questions 1) How much better is this Rom then Tronsmart

                      clarify steps 2) Do I have to first install v8 rev 3 FULL ROM 1st

                      Then install v9 rev 2 FULL ROM 2nd

                      I'm not sure of the terms you use when you talk about just Kernel and if I flash the Full Rom is the Kernel part of the Full Rom etc.
                      Just flash 9.2 full rom.

                      Comment


                        Originally posted by lonix View Post

                        Use quickboot to reboot to bootloader, the kernel can in no way affect bootloader mode

                        If your pc cannot detect your device in bootloader mode it means there is another problem possibly bad solder on the otg port.

                        Rockchip devices are virtually unbrickable, unless you flash the wrong loader, and even then its recoverable


                        Thanks I am just returning it for another one. Amazon gives me free shipping return. I just re-ordered another one not gonna bother with trying to figure out what it wrong at this point. I am going to completely wipe it and install there Rom or at least get rid of TWRP and wipe system etc.

                        Is this the one you have or most people have using your Rom?

                        How can I erase TWRP if I have no connection between PC and Tronsmart. Is there some series of buttons I depress to completely wipe and bring in stock bootloader? If not would you have a copy of the stock tronsmart recovery/boot I can install from TWRP?

                        I figured it out. I just downloaded the full image from Tronsmart and extracted all the individual images using the android tool. I was able to flash the kernel, Boot and recovery so now its back to stock recovery and bootloader and even when I boot into tronsmart bootloader the device is not loaded in windows. OTG must be bad. I removed bottom cover and PC board and all solder and surface mounted diodes, caps and resistors in that area are perfect. I cannot figure out what went wrong but its going back.


                        lonix

                        Is this the device you have?


                        http://www.amazon.com/Tronsmart-R68-...ilpage_o00_s00


                        Edited 3-24-16

                        From a search on Tronsmart Forum and at least one post in Freaktab more than one person has reported issues with the OTG/Usb no longer being recognized on the PC. Many reporting dead boxes as well very strange? What is even more strange is the way it remains powered if I leave the USB cable inserted into the OTG/USB port and PC after the power has been removed from the Tronsmart. Maybe some kind of design flaw?


                        I have another question, what is the Uboot option in TWRP when I choose image at the bottom right and choose the image I want I am presented with a choice of partitions obviously you choose the one that correlates with the image name but one of those choices is Uboot? So there is no choice for System.img have to assume we cannot flash that one. Can't an entire full rom be flashed in TWRP using the zip method? I know I have done this before on my Nexus 7 2013 tablet. It just won't update the recovery or boot, but updates the kernel and system partitions but thats on the android tablets.
                        Last edited by androidfr33k; 25 March 2016, 00:46.

                        Comment


                          Hi lonix,

                          The MAC flash tool worked for me fine! I set MAC successfully, thank you again! The permissions I'll check tomorrow.
                          Best regards,
                          STZO

                          (Today the quoting does not work for me, I'm sorry...)
                          Regards, STZO

                          Comment


                            Originally posted by Stzo View Post
                            Hi lonix,

                            The MAC flash tool worked for me fine! I set MAC successfully, thank you again! The permissions I'll check tomorrow.
                            Best regards,
                            STZO

                            (Today the quoting does not work for me, I'm sorry...)
                            Sorry, just remembered, please check the script at /system/etc/install-revovery-2.sh

                            Comment


                              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...)

                              Regards, STZO

                              Comment


                                Originally posted by lonix View Post
                                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

                                Regards, STZO

                                Comment

                                Working...
                                X