Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Cannot flash my Jesurun DX05

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

    Cannot flash my Jesurun DX05

    I have some problems with flashing my device. I connected it to PC and installed adb driver, but RK Flash tool does not see it. ROM_Flash_Tool_137 does not see it too. I tried on 3 PCs with Windows 7 (both 86 and 64), 2 different usb cables and effect is the same.

    What should I do now?

    #2
    Upd. Problem was probably solved by console command "adb reboot bootloader". After rebooting and installing additional driver RK Flash tool saw the device and firmware 2.0.4 was installed. But after that PC don't see the device at all. I don't have the TV near to check, either it installed successfully and I only need to switch "USB debugging" and "Connect to PC" on in settings menu, or I eventually bricked the device. I could check it only in the evening when I will return home.
    Upd2. Flashing was successful, problem solved.
    Last edited by Brenwen; 03 October 2013, 18:02.

    Comment


      #3
      Originally posted by Brenwen View Post
      Upd. Problem was probably solved by console command "adb reboot bootloader". After rebooting and installing additional driver RK Flash tool saw the device and firmware 2.0.4 was installed. But after that PC don't see the device at all. I don't have the TV near to check, either it installed successfully and I only need to switch "USB debugging" and "Connect to PC" on in settings menu, or I eventually bricked the device. I could check it only in the evening when I will return home.
      Upd2. Flashing was successful, problem solved.
      Hi;

      can you explain me in details what you did? I am unable to recognize my unit as well.
      tks

      Comment


        #4
        Download actual USB drivers for windows for example at Tronsmart ("Class for rockusb device") or geekbuying.
        1. unplug all cables from device.
        2. plug micro usb otg cable into device and into pc (nothing else)
        3. press and hold little restore button on which is under device
        4. plug in power cord (remember to still hold restore button) and you are in flash mod
        5. on first time it may not work before driver are installed but later its working every time.

        Run flashtool as administrator
        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


          #5
          Originally posted by no_spam_for_me View Post
          Download actual USB drivers for windows for example at Tronsmart ("Class for rockusb device") or geekbuying.
          1. unplug all cables from device.
          2. plug micro usb otg cable into device and into pc (nothing else)
          3. press and hold little restore button on which is under device
          4. plug in power cord (remember to still hold restore button) and you are in flash mod
          5. on first time it may not work before driver are installed but later its working every time.

          Run flashtool as administrator
          It doesnt recognize the drivers. Only powered on on normal mode it apears lika "adb android device". On recovery it does not install. Why is that so?

          Comment


            #6
            The mode by "press and hold little restore button on which is under device" needs other drivers (windows 8.1 drivers at the moment not availible) than debug mode at normal startup...
            Or does the windows don't recognize any unknowing device at that moment, if it so, I don't have any idea (perhaps the cable?)...
            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


              #7
              Originally posted by no_spam_for_me View Post
              The mode by "press and hold little restore button on which is under device" needs other drivers (windows 8.1 drivers at the moment not availible) than debug mode at normal startup...
              Or does the windows don't recognize any unknowing device at that moment, if it so, I don't have any idea (perhaps the cable?)...
              I´ve tried on windows 8 and windows 7. On recovery mode it just doesnt work... only on normal mode the pc install the drivers... the pc cant find the driver on recovery mode.
              Last edited by alexjcgdf; 25 November 2013, 03:39.

              Comment


                #8
                can you explain me in details what you did? I am unable to recognize my unit as well.
                If you have all drivers installed, but device don`t reboot into bootloader mode, you must unpack this archive with adb file into any folder and then start windows console (start>search>cmd), go to this folder (if you unpacked it into c:\RK3188_ROOT you should enter "cd c:\RK3188_ROOT"), then enter "adb reboot bootloader". Device will reboot into bootloader mode, additional driver will be installed and flashing software will see the device so you could flash the firmware you need.

                Comment


                  #9
                  I'm not sure, if I understand your problem, but
                  Originally posted by alexjcgdf View Post
                  the pc cant find the driver on recovery mode.
                  couldn't work, because windows cant find the driver automatically, because you have to use manual selection of the correct folder (x89 vs. x64 and then correct OS-Version) during the driver installation...
                  With windows 8 there is eventually a problem because of "unsigned" problem
                  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


                    #10
                    Originally posted by Brenwen View Post
                    If you have all drivers installed, but device don`t reboot into bootloader mode, you must unpack this archive with adb file into any folder and then start windows console (start>search>cmd), go to this folder (if you unpacked it into c:\RK3188_ROOT you should enter "cd c:\RK3188_ROOT"), then enter "adb reboot bootloader". Device will reboot into bootloader mode, additional driver will be installed and flashing software will see the device so you could flash the firmware you need.

                    The .rar file has a password. Can you tell me what it is?

                    tks

                    Comment


                      #11
                      Originally posted by no_spam_for_me View Post
                      I'm not sure, if I understand your problem, but

                      couldn't work, because windows cant find the driver automatically, because you have to use manual selection of the correct folder (x89 vs. x64 and then correct OS-Version) during the driver installation...
                      With windows 8 there is eventually a problem because of "unsigned" problem
                      even forcing it it just doenst work. the windows sais that the driver isnt right for it and it cant start the hardware. I think the driver isnt right for it.

                      Comment


                        #12
                        Originally posted by alexjcgdf View Post
                        The .rar file has a password. Can you tell me what it is?

                        tks
                        GEEKBUYING.COM

                        Comment


                          #13
                          Originally posted by alexjcgdf View Post
                          even forcing it it just doenst work. the windows sais that the driver isnt right for it and it cant start the hardware. I think the driver isnt right for it.
                          I don't know how good you are in linux and or generally at computer , but if so, try lsusb at linux or have al look at the unknowing device at windows and find out witch VID / PID your device have and than check the driver's inf (rockusb.inf) if you can find the same VID / PID at it...
                          if not, try to add it in the inf ....
                          [Rockchip.NTx86]
                          [Rockchip.NTamd64]

                          OR

                          you have to ask your trader to get the correct driver for bootloadermode (NOT Debug Mode, because that works for you, if I understood it correct)
                          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


                            #14
                            Have you look inside our device to confirm witch pcb do you have?
                            (becauseK-R42 3.1 PCB)
                            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


                              #15
                              Originally posted by no_spam_for_me View Post
                              Have you look inside our device to confirm witch pcb do you have?
                              (becauseK-R42 3.1 PCB)
                              Here in this tread there is the photos...

                              Comment

                              Working...
                              X