Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Beelink R89/UBOX ROM/Tools release

Collapse
This is a sticky topic.
X
X
Collapse
 
  • Page of 20
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19 20 template Next
    #121
    Originally posted by bluesmanuk View Post
    The first thing that I did when I got the box was to make a backup before I destroyed it lol...
    Maybe you can upload it at the Tronsmart-Sub-Forum...
    Maybe download my all-in-on and replace it with your dumps...
    Forums - FreakTab
    http://www.freaktab.com/showthread.php?16490-Beelink-R89-UBOX-ROM-Tools-release&p=221237&viewfull=1#post221237
    vBulletin Forums
    RK3288 Devices
    - Overview BOX (LINK !)
    - Overview STICK (Dongle) (LINK !)

    MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
    UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
    Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
    Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

    RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
    Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

    Comment

      #122
      Originally posted by no_spam_for_me View Post
      Maybe you can upload it at the Tronsmart-Sub-Forum...
      Maybe download my all-in-on and replace it with your dumps...
      http://www.freaktab.com/showthread.p...l=1#post221237
      I'll take a look and see what I can do.
      R-TV BOX S10, Beebox N3150, Chuwi Hibox, Nvidia Shield, A95X Max

      Comment

        #123
        Hangs on "Test Device Start"

        Hi, I have a tronsmart R28 pro, and somehow I bricked it. I can not flash or erase with normal ways. I opened the box and found that the PCB looks exactly the same as R89, so I found the two pins besides the emmc component. I short cut these two pins, and the tool "Found One MASKROM Device". However, further operations always hang at the "Test Device Start" step:

        Download Boot Start
        Download Boot Success
        Wait for Maskrom Start
        Wait for Maskrom Success
        Test Device Start

        It hangs there for long long time, I think it won't proceed, forever.

        Is my device severely damaged, even the MASK_ROM can't restore it? Please help me.

        Thanks.

        Comment

          #124
          Originally posted by linuxerwang View Post
          Hi, I have a tronsmart R28 pro, and somehow I bricked it. I can not flash or erase with normal ways. I opened the box and found that the PCB looks exactly the same as R89, so I found the two pins besides the emmc component. I short cut these two pins, and the tool "Found One MASKROM Device". However, further operations always hang at the "Test Device Start" step:

          Download Boot Start
          Download Boot Success
          Wait for Maskrom Start
          Wait for Maskrom Success
          Test Device Start

          It hangs there for long long time, I think it won't proceed, forever.

          Is my device severely damaged, even the MASK_ROM can't restore it? Please help me.

          Thanks.
          Give the right log in AndroidTool_Release_v2.3\Log\ to me,let me check.
          Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

          Comment

            #125
            Originally posted by oman View Post
            Give the right log in AndroidTool_Release_v2.3\Log\ to me,let me check.
            Log2014-09-14.txt output:

            16:33:45 600 AndroidTool v2.3.0.0 start run
            16:34:37 595 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
            16:34:37 896 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
            16:34:37 896 Error:ResetDeviceProc-->RKU_ResetDevice failed,err=-3
            16:34:52 911 Layer<1-2>ownload Boot Start
            16:35:49 953 Layer<1-2>ownload Boot Success
            16:35:49 954 Layer<1-2>:Wait For Maskrom Start
            16:35:50 454 Layer<1-2>:Wait For Maskrom Success
            16:35:50 455 Layer<1-2>:Test Device Start
            16:35:50 455 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
            16:39:15 122 Error:RKU_Write-->WriteFile failed,bRet=0,err=5,size=31,write=0
            16:39:15 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
            16:39:16 122 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&7BDD D4C&0&02#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
            16:39:16 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
            16:39:17 122 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&7BDD D4C&0&02#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
            16:39:17 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
            16:39:18 124 Error:Layer<1-2>:Test Device Fail
            16:39:26 112 AndroidTool v2.3.0.0 start run
            16:40:49 156 Layer<1-2>ownload Boot Start
            16:41:46 100 Layer<1-2>ownload Boot Success
            16:41:46 102 Layer<1-2>:Wait For Maskrom Start
            16:41:46 598 Layer<1-2>:Wait For Maskrom Success
            16:41:46 599 Layer<1-2>:Test Device Start
            16:41:46 599 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0


            ScanLog2014-09-14.txt output:

            16:09:52 492 Error:EnumerateHubPorts-->DeviceIoControl failed,err=0x57


            Thank you for the help!

            Comment

              #126
              Originally posted by linuxerwang View Post
              Log2014-09-14.txt output:

              16:33:45 600 AndroidTool v2.3.0.0 start run
              16:34:37 595 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
              16:34:37 896 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
              16:34:37 896 Error:ResetDeviceProc-->RKU_ResetDevice failed,err=-3
              16:34:52 911 Layer<1-2>ownload Boot Start
              16:35:49 953 Layer<1-2>ownload Boot Success
              16:35:49 954 Layer<1-2>:Wait For Maskrom Start
              16:35:50 454 Layer<1-2>:Wait For Maskrom Success
              16:35:50 455 Layer<1-2>:Test Device Start
              16:35:50 455 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0
              16:39:15 122 Error:RKU_Write-->WriteFile failed,bRet=0,err=5,size=31,write=0
              16:39:15 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-3),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
              16:39:16 122 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&7BDD D4C&0&02#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
              16:39:16 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
              16:39:17 122 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&7BDD D4C&0&02#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
              16:39:17 122 <LAYER 1-2> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&7BDDD4C&0&02#{ a5dcbf10-6530-11d2-901f-00c04fb951ed}
              16:39:18 124 Error:Layer<1-2>:Test Device Fail
              16:39:26 112 AndroidTool v2.3.0.0 start run
              16:40:49 156 Layer<1-2>ownload Boot Start
              16:41:46 100 Layer<1-2>ownload Boot Success
              16:41:46 102 Layer<1-2>:Wait For Maskrom Start
              16:41:46 598 Layer<1-2>:Wait For Maskrom Success
              16:41:46 599 Layer<1-2>:Test Device Start
              16:41:46 599 Error:RKU_Write-->WriteFile failed,bRet=0,err=31,size=31,write=0


              ScanLog2014-09-14.txt output:

              16:09:52 492 Error:EnumerateHubPorts-->DeviceIoControl failed,err=0x57


              Thank you for the help!
              It might be related to USB signal,so:
              1.Change another USB port on your PC or another PC;
              2.Change one more better USB cable;
              Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

              Comment

                #127
                Originally posted by oman View Post
                It might be related to USB signal,so:
                1.Change another USB port on your PC or another PC;
                2.Change one more better USB cable;
                I am sure it's not the issue of USB port or cable, because I used the same USB port and cable to successfully flashed many times.

                BUT, I did try to use a different USB port and cable, and after a few more times trying, it worked! I can't explain why, the first a few times it failed as before, then suddenly it proceeded more and failed, then finally it can finish what it should. Now it's completely back.

                Thanks a lot!

                Comment

                  #128
                  Hi all ,

                  i am a new user , and i see the upgraded step from bob post ,
                  i already flash the TWRP recovery rom , and then try to upgrade 108k407
                  however , in the step 6 , i can't find "updated rkimage" from TWRP menu ,
                  please help me , thanks

                  HOW TO FLASH from SDcard

                  OK the stock recovery CAN flash the ROM Oman uploaded. e.g. the large IMG file.

                  Instructions:
                  1) You will need an IR remote. The one I got with the HPH works but the power button is select not the OK button.
                  2) download OMan's 107K4 from the posts here.
                  3) rename it to update.img
                  4) copy it to SDcard.
                  5) reboot into the recovery menu (using reboot app or whatever).
                  6) from the menu select "update rkimage from external storage".
                  7) It will flash the ROM then select reboot.
                  If you want to erase, then select factory reset before selecting reboot.

                  Bob

                  Comment

                    #129
                    1. "stock recovery"... nothing about TWRP
                    2. he means something like "update from EXT" at 6)... (I think the "6) from the menu select "update rkimage from external storage"." is a copy&past issue)
                    RK3288 Devices
                    - Overview BOX (LINK !)
                    - Overview STICK (Dongle) (LINK !)

                    MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
                    UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
                    Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
                    Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

                    RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
                    Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

                    Comment

                      #130
                      Originally posted by no_spam_for_me View Post
                      1. "stock recovery"... nothing about TWRP
                      2. he means something like "update from EXT" at 6)... (I think the "6) from the menu select "update rkimage from external storage"." is a copy&past issue)
                      can i rename the update.image to update.zip ,
                      and then execute the "install from zip" to upgrade ?

                      Comment

                        #131
                        Originally posted by hellomysons View Post
                        can i rename the update.image to update.zip ,
                        and then execute the "install from zip" to upgrade ?
                        Just rename 108k4107.img to update.img...copy it to sd card or usb stick,then power on into android OS,the OS will find it and show the hint.
                        Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

                        Comment

                          #132
                          Originally posted by hellomysons View Post
                          can i rename the update.image to update.zip ,
                          and then execute the "install from zip" to upgrade ?
                          If I remember correctly, you CAN'T use TWRP for this way (only stock recovery is able to handle the .IMG)...
                          RK3288 Devices
                          - Overview BOX (LINK !)
                          - Overview STICK (Dongle) (LINK !)

                          MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
                          UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
                          Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
                          Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

                          RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
                          Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

                          Comment

                            #133
                            Hi all ,

                            in order to erase TWRP recovery , i wipe the data and cache partition ,
                            and miss operation wipe "system" partition ,
                            now , the box is stuck in blue Beelink logo ,
                            what can i do now ? is it possible to rescue my box
                            thanks.

                            Comment

                              #134
                              Originally posted by hellomysons View Post
                              Hi all ,

                              in order to erase TWRP recovery , i wipe the data and cache partition ,
                              and miss operation wipe "system" partition ,
                              now , the box is stuck in blue Beelink logo ,
                              what can i do now ? is it possible to rescue my box
                              thanks.
                              I don't understand if you now have back the stock recovery?
                              If yes, I think then you are able to update with the update.img,
                              if not, you have to use the windows flash tool via OTG to flash the img...
                              RK3288 Devices
                              - Overview BOX (LINK !)
                              - Overview STICK (Dongle) (LINK !)

                              MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
                              UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
                              Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
                              Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

                              RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
                              Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

                              Comment

                                #135
                                i wipe my cache , data , and system partition,
                                and now , my tvbox stop in the beelink screen (power on screen)
                                i think , cause i wipe my system , so no os in the box ,
                                and i try the updated fw way , one and two and three ,
                                i still can find my device to updated ,
                                and then i use another normal r89 , try to use way 2 to updated ,

                                Another update method:
                                1.Power up the device,select Setting->USB->Connect to PC;
                                2.Deselect Setting->Developer options->USB debugging;
                                3.Then Click 'switch',it will go into Update Mode.

                                still can't found device , i dont know what i can do now ?

                                another problem is in following step ,
                                3.Plug in PSU(Power supply unit),and push and hold the button in the AV hole,then plug into the OTG cable..
                                i dont know what is "push and hold the button in the AV hole" , i just can push power button , no av button

                                please help me.

                                Originally posted by no_spam_for_me View Post
                                I don't understand if you now have back the stock recovery?
                                If yes, I think then you are able to update with the update.img,
                                if not, you have to use the windows flash tool via OTG to flash the img...

                                Comment

                                Previous 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 19 20 template Next

                                What's Going On

                                Collapse

                                There are currently 2106 users online. 1 members and 2105 guests.

                                Most users ever online was 63,956 at 18:56 on 20 March 2025.

                                Working...
                                X

                                We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                I Agree