Beelink R89/UBOX ROM/Tools release

[clarkss12]

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.

Inside the A/V hole (you can't see it) there is a tiny button switch. If you take a round toothpick and GENTLY slide it into the A/V hole, you will feel a "click".

[hellomysons]

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.

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

[no_spam_for_me]

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

[hellomysons]

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.

[no_spam_for_me]

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

[oman]

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.

[hellomysons]

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 ?

[no_spam_for_me]

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)

[hellomysons]

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

[linuxerwang]

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!

[oman]

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;

[linuxerwang]

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!

[oman]

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.

[linuxerwang]

Hangs on &quot;Test Device Start&quot;

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.

[bluesmanuk]

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.