Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Need help ASAP with firmware for "DIAOTEC J22" cyx_809III v5_1 20140726

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

    Need help ASAP with firmware for "DIAOTEC J22" cyx_809III v5_1 20140726

    I was working on an rk3188 tv stick for a client named DIAOTEC J22. Everything was working great and things were coming together well, until I decided to try a 1080p kernel. It came loaded with kitkat 4.4.2 on test keys.

    I already knew that it was a 3188 and I suspected it was a t variant despite the 1.6ghz clock speed. So I looked in the thread about all the different 3188 kernels (d33?) and was aware that they come with different wifi chipsets and such, so I looked to see which wifi was loaded in /proc and selected to download the ones with realtek 8723bs support.

    I then flashed the HD kernel in rktool 1.7 i believe. Whatever is the latest one before 2 series tool.

    Anyway, since then I can't get it to boot. I made the stupid mistake of not backing up the original first.

    I popped the thing open and the board says cyx_809III v5_1 20140726.

    I have tried NUMEROUS ROMs both custom ones from the site here and stock ones from various chinese and russian sites which are for 809iii with 8723 wifi, or cyx with 8723, any variation of 3188(t) with realtek 8723bs that I can find, both 1080p and 720p. So many different roms and not a single one will go beyond the boot screen. At this point I have tried wiping the whole thing and started installing whole roms and not just kernels, but nothing seems to work!

    If it helps this is the specific device http://www.amazon.com/DIAOTEC-antenn.../dp/B00ECBY5VS

    Internally it looks almost identical to the 809iii v5 systems.

    My customer really wants this device ASAP so any help is GREATLY appreciated!

    Cheers,
    -SB
    ---------------------------------------
    Currently using U-BOX R89 with mo123 v1.6.
    Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
    Pipo M9S -- CrewRKTab custom rooted 4.4.2
    RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
    ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

    #2
    Hello,

    You Device is a J22 Device. Normaly they come with a AP6210 Chipset.
    Try the AP6210-ALT Kernel from D33.

    Neomode

    Comment


      #3
      Originally posted by neomode View Post
      Hello,

      You Device is a J22 Device. Normaly they come with a AP6210 Chipset.
      Try the AP6210-ALT Kernel from D33.

      Neomode
      Yes, I know that a normal j22 comes with the 6210 Wi-Fi, but as I posted above this one is internally labeled cyx 809iii v5_1 and has 8723bs realtek Wi-Fi. I have opened it.

      None of the firmwares I have tried for 809iii with Realtek 8723bs will boot though. It just bootloops the start up animation.

      Thanks,
      -SB
      ---------------------------------------
      Currently using U-BOX R89 with mo123 v1.6.
      Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
      Pipo M9S -- CrewRKTab custom rooted 4.4.2
      RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
      ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

      Comment


        #4
        Hi

        Originally posted by sawbones999 View Post
        I was working on an rk3188 tv stick for a client named DIAOTEC J22. Everything was working great and things were coming together well, until I decided to try a 1080p kernel. It came loaded with kitkat 4.4.2 on test keys.

        I already knew that it was a 3188 and I suspected it was a t variant despite the 1.6ghz clock speed. So I looked in the thread about all the different 3188 kernels (d33?) and was aware that they come with different wifi chipsets and such, so I looked to see which wifi was loaded in /proc and selected to download the ones with realtek 8723bs support.

        I then flashed the HD kernel in rktool 1.7 i believe. Whatever is the latest one before 2 series tool.

        Anyway, since then I can't get it to boot. I made the stupid mistake of not backing up the original first.

        I popped the thing open and the board says cyx_809III v5_1 20140726.

        I have tried NUMEROUS ROMs both custom ones from the site here and stock ones from various chinese and russian sites which are for 809iii with 8723 wifi, or cyx with 8723, any variation of 3188(t) with realtek 8723bs that I can find, both 1080p and 720p. So many different roms and not a single one will go beyond the boot screen. At this point I have tried wiping the whole thing and started installing whole roms and not just kernels, but nothing seems to work!

        If it helps this is the specific device http://www.amazon.com/DIAOTEC-antenn.../dp/B00ECBY5VS

        Internally it looks almost identical to the 809iii v5 systems.

        My customer really wants this device ASAP so any help is GREATLY appreciated!

        Cheers,
        -SB

        Hi, I have the same stick, but I can't enter in flash mode. I pressed the reset button and connect them to my win 7 PC and nothing happens, maybe the drivers what I install are wrong. I read what the led light must be red in flash mode.
        Please Help!!
        Click image for larger version

Name:	20150122_113954.jpg
Views:	1
Size:	186.4 KB
ID:	436062

        Comment


          #5
          Here is a link to updated stock firmware which supports 1080p resolution (though i think it's naive 720 upconverted). https://yadi.sk/d/kw9BKrrFdZhWE

          Try plugging power into the power slot, then connect otg cable to pc/laptop and after it boots hold down the switch on the side for like 10 seconds. It's important that there is enough power for the thing to run and your laptop won't provide it on 1 port. I have successfully flashed with power on 1 laptop USB and otg cable on another.

          If that doesn't work you may have to open it and short some pins. 2 ways to do it one is for regular flash, other is for mask ROM mode.

          Try my first suggestion, first.
          Cheers,
          -SB
          ---------------------------------------
          Currently using U-BOX R89 with mo123 v1.6.
          Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
          Pipo M9S -- CrewRKTab custom rooted 4.4.2
          RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
          ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

          Comment


            #6
            I try, but no connect. Maybe the drivers what I install are wrong. You can give me a link with the drivers what you install?


            Originally posted by sawbones999 View Post
            Here is a link to updated stock firmware which supports 1080p resolution (though i think it's naive 720 upconverted). https://yadi.sk/d/kw9BKrrFdZhWE

            Try plugging power into the power slot, then connect otg cable to pc/laptop and after it boots hold down the switch on the side for like 10 seconds. It's important that there is enough power for the thing to run and your laptop won't provide it on 1 port. I have successfully flashed with power on 1 laptop USB and otg cable on another.

            If that doesn't work you may have to open it and short some pins. 2 ways to do it one is for regular flash, other is for mask ROM mode.

            Try my first suggestion, first.
            Cheers,
            -SB

            Comment


              #7
              Are you trying to get to bootloader mode? On some of these you must open it and short 2 pins for it to work properly. Search the forum. I'd instruct but I'm on a strict timeline today and am having trouble with ADB not working on the rom I just linked above. I'm trying to root.

              Good luck to us both!
              Cheers,
              -SB
              ---------------------------------------
              Currently using U-BOX R89 with mo123 v1.6.
              Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
              Pipo M9S -- CrewRKTab custom rooted 4.4.2
              RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
              ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

              Comment


                #8
                Originally posted by sawbones999 View Post
                Are you trying to get to bootloader mode? On some of these you must open it and short 2 pins for it to work properly. Search the forum. I'd instruct but I'm on a strict timeline today and am having trouble with ADB not working on the rom I just linked above. I'm trying to root.

                Good luck to us both!
                Cheers,
                -SB
                It's works when short 2 pins the PC recognize the android stick. But now when I upgrade or restore shows an error like this:
                Attached Files

                Comment


                  #9
                  Originally posted by AndreuSurfer View Post
                  It's works when short 2 pins the PC recognize the android stick. But now when I upgrade or restore shows an error like this:
                  You might need to go to mask mode, erase flash, then upgrade. That's how I did it.

                  Problem with the ROM i posted, the otg USB port doesn't work. So no adb. I downloaded Wi-Fi adb for no root and was able to connect adb that way. Can't use root in ROM, but when I connect adb shell, I get a root shell by default. Still haven't figure out how to install supersu and have it work. With original stock room USB adb working fine on otg port.

                  Adb restart-bootloader goes to bootloader but still not recognized by pc. Was going to try fastboot but not recognized.

                  Adb restart recovery will go to recovery and then with no prompt hard reset.

                  Su it's already on the system. I tried using dd from shell to install cwm, then adb restart recovery and install supersu zip. Afterwards system only boots cwm.

                  I wish I could find the original ROM for v5.1

                  Cheers,
                  -SB
                  ---------------------------------------
                  Currently using U-BOX R89 with mo123 v1.6.
                  Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
                  Pipo M9S -- CrewRKTab custom rooted 4.4.2
                  RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
                  ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

                  Comment


                    #10
                    Also I used the rockchip android tool 2.3 to erase flash on mask mode then flash the ROM.

                    It's a little bit easier to use for that than the 1.7 tool. You may not have to go into mask mode if your stick is being recognized. Get the 2.3 tool and go to the second tab, click on firmware and select your image. Then click erase flash. If that completes successfully click upgrade and the fw should install, and it will run an integrity check.

                    If any of that errors, you'll probably have to put it into mask mode. Google for detailed instructions with pics, but short version is you must short pins 7&8 on the NAND flash while inserting the otg USB cable. If you do this correctly the device will show up in tool 2.3 as mask mode, then follow my instructions above again.

                    My biggest problem right now is that this ROM doesn't seem to recognize the otg port after boot. PITA!

                    I haven't checked it yet, but I just thought maybe the power micro USB and otg micro USB port are switched in this ROM. If not there is some difference between the v5.1 hw and 5.2(this ROM is 5.2).

                    Perhaps the otg port can be enabled in config files somewhere. At least i can get a root shell via wireless adb, even though I haven't figured out how to get su working for android apps.

                    I'm going out of town tomorrow, but I'll test Wednesday to see if otg and power are switched. I hope so, bc as it is I can't connect usb adb, therefore I can't use kingo root. Kingo root won't recognize wireless adb.

                    Maybe you can test it first. Try putting power in the otg port and connect power port to pc and see you if can start adb. Otherwise you might be able to use the full size USB port but I don't have the correct combination of cables and adapters to go from USB "A" to USB "A".

                    If I have to I might try and make one. Otherwise only way to root will be manually over wireless adb and that's a pain as well in kitkat.

                    The full size USB is working for hdd and keyboard/mouse. I tried connecting those to the otg port via otg cable adapter but it's not working. I didn't try it with the "power" micro USB port.

                    Keep me posted. If you can't figure it out I'll try some things Wednesday.

                    Remember if you need adb, wireless adb for no root in play store works and actually does have root privilege.

                    Cheers,
                    -SB
                    ---------------------------------------
                    Currently using U-BOX R89 with mo123 v1.6.
                    Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
                    Pipo M9S -- CrewRKTab custom rooted 4.4.2
                    RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
                    ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

                    Comment


                      #11
                      I finally found a ROM that works correctly on this HW!!!!

                      This is the link:


                      If anyone else is having issues like I was try this.

                      Cheers!
                      -SB
                      ---------------------------------------
                      Currently using U-BOX R89 with mo123 v1.6.
                      Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
                      Pipo M9S -- CrewRKTab custom rooted 4.4.2
                      RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
                      ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

                      Comment


                        #12
                        Help needed: no input anymore on CX919II V5.1

                        @ sawbones999: super thanks for finding the ROM!

                        I have the same CX919II (or "DIAOTEC J22") as you
                        The motherboard is the same: CYX_809III V5_1 20140726




                        I NEED YOUR HELP!!




                        After I tried to root mine, and did all the steps accordingly with TPSparkyRoot.bat
                        It said the device was rooted. But after I started it, the app Root Checker said it wasn't rooted properly.
                        Also SuperSU said: "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root. Consult the relevant forums for your device!"




                        After this, I found a forum saying some folks with the same chipsets (v5.1) were only able to root the device properly using Kingo-Root.
                        So I installed this software, and plugged the OTG usb back into the device and laptop, and pressed 'connect to PC' (and USB debugging was on), but now my laptop didn't popup with recognizing the device anymore.
                        So I thought, Kingo-Root overwrote the Google USB driver with the one installed from PDAnet+, and therefore is in conflict. I tried cleaning all USB drivers from the registry with USBOblivion, but no luck.
                        I can't "uninstall" the Android ADB interface in device manager, because it simple doesn't show.
                        [edit]: found the ADB Interface driver and uninstalled it....




                        So I tried to factory reset my CX919II, but then the worst happend:
                        Factory reset worked fine, And I see the normal first time startup the way I bought it.
                        But WiFi and BT is not on, so I needed to plug in a normal wired mouse via it's USB port, so to go to the settings menu and set WiFi and BT on.
                        But the device won't show the mouse anymore!!
                        So I can't do anything on the device anymore!!!
                        (mouse is connected via the USB port on the device, and looks like the mouse is on power (red laser shows), but no mouse pointer is shown on screen.)




                        What should I do?
                        I looked at hard resets, but only found to hold the only button on the device (the Fn button) while putting the power USB into the power socket. But all I get then is the blue LED light on, and nothing else. (black screen, tv says no HDMI devices connected)




                        So:
                        1.no mouse input available
                        2.hard resets don't work with the Fn button
                        3.can't connect device to PC (because I can't select the option "connect to PC"...)
                        4.If I have to unbrick my device, can you tell me step by step how to? (i'm really new at this... which pins on the NAND to connect? )




                        Please help!?
                        What can I do to at least enter the device again with a mouse or keyboard....??




                        Cheers....
                        Attached Files
                        Last edited by paultje_007; 04 February 2015, 08:51. Reason: attached photos

                        Comment


                          #13
                          I'm 99% sure I know how to fix this but dinner is ready and gotta eat with my wife and son. I will post immediately after we eat.

                          It won't be that long before I'm back.

                          Cheers,
                          -SB
                          ---------------------------------------
                          Currently using U-BOX R89 with mo123 v1.6.
                          Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
                          Pipo M9S -- CrewRKTab custom rooted 4.4.2
                          RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
                          ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

                          Comment


                            #14
                            BTW tsparky doesn't work on this device.
                            ---------------------------------------
                            Currently using U-BOX R89 with mo123 v1.6.
                            Other android tv device - ADT-1 running latest PureNexus 6.0.1 MM and very impressed with the changes vs stock molly!
                            Pipo M9S -- CrewRKTab custom rooted 4.4.2
                            RCA Viking Pro 10 -- Custom stock rooted 5.1 by me <- FOR SALE
                            ----------- ROM by me, the first way to update ZTE Force 4G from ICS to JB http://androidforums.com/threads/fin...om-ics.886408/

                            Comment


                              #15
                              Thank you so much! Bon appétit from Europe
                              Awaiting your answers

                              Comment

                              Working...
                              X