Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] Beelink GT1 Ultimate SCV2-ATV (Android TV) (DDR4)

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    Originally posted by Kevin Flynn View Post

    No, I wasn't flashing wrong firmware, and no, the problem in linux was entirely different than the problem in Windows.

    Regardless, here is what I did just now, apparently, to make it finally work. I'm not 100% sure its working as I type this, but it made it all the way through the update progress bar, restarted and displayed the SuperCeleron Beelink GT1 screen, and now its displaying some animated doodads, and I assume its going through some sort of initialization / first boot stage, so I'm letting it run for a bit, unless you tell me different. Okay, as I was typing, I made it to the "Welcome choose your system language" screen, so I think its worked.

    Okay, for the final, I think it worked method, to flash this Gearbest Alfawise H96 Pro+ 3GB/32GB DDR4 box, in detail:

    1) Used a Windows 10 laptop. Probably not important, but just listed for completeness sake. Linux method did not work.
    2) I used a standard speed, budget priced, $13 at Walmart, 32GB Sandisk SD card.
    3) I downloaded SuperCelerons "Standard Android" DDR4 ( not Android TV ) firmware as linked in this forum.
    4) I unzipped the downloaded firmware file, to arrive at the .img file.
    5) I renamed the .img file to remove the hyphen and underline, because another post at http://www.cnx-software.com/2016/11/...ogic-tv-boxes/ seemed to indicate special character were a problem. I tried once with special characters and had no luck.
    6) I ran the Burn Card Maker utility as linked from this forum, changed the language to English, exited and restarted.
    7) I selected the 32GB SD card as the output disk, and checked the following:

    [x] To Partition and Format.
    [x] erase_bootloader
    [x] erase_flash
    [forcefully erase all]
    [x] reboot

    then opened the renamed firmware .img file and clicked "Make" to create the firmware SD card.

    Now, here is where its a little wierd, and I'm not sure if what I did made any difference.

    I booted the SD card in the Alfawise box, while holding down the reset button, and when I saw the Android logo and progress bar, I let off the reset button. Immediately after that, for whatever reason, the update stopped and the screen went blank and the unit appeared to power itself off.

    So, I repeated the above steps again, but this time I held the reset button in a little longer, and the update progress bar made more progress, and it looked like all was working, so I let off the reset button and by the time I sat down in my chair, the unit had powered itself down again.

    So, third times a charm, I held down the reset button, powered the unit back up, and I kept the reset button held down the entire time. The Android logo and updating screen appeared, but it was all corrupted, like, bit shifted or missing a bit plane, but still obviously the screen. I kept the reset button held, and watched it as it made it all the way through the update process and eventually booted the new firmware.

    Phew. So, for anyone that has this box ... this is how I got it to update. Use SuperCelerons DDR4 firmware, rename the .img file before creating the boot SD card to remove the hyphen and the underline, and use the SD card and not a USB flash drive or cable, and you should be able to avoid the hours of frustration and heartache I just went through.
    Thanks to Scooter2014 and others for their input. Peace and hot dogs.
    Please kevin Flynn, help me....
    I have same problem with my Gearbest Alfawise H96 Pro+ 3GB/32GB, i tried flash ddr3 rom or ddr4 rom with USB_Burning_Tool but have error:
    with ddr3 rom at 4% see my pic1.
    with ddr4 rom at 7% see my pic2.
    I tried same with your method, create a sd card first with ddr3 rom img and after with ddr4 rom img but my tvbox not want start flash, it stuck in red light and my tv show not signal.
    My motherboard is this in pic3

    You may only view thumbnails in this gallery. This gallery has 4 photos.

    Comment


      #47
      Originally posted by joemilan View Post

      Please kevin Flynn, help me....
      I have same problem with my Gearbest Alfawise H96 Pro+ 3GB/32GB, i tried flash ddr3 rom or ddr4 rom with USB_Burning_Tool but have error:
      with ddr3 rom at 4% see my pic1.
      with ddr4 rom at 7% see my pic2.
      I tried same with your method, create a sd card first with ddr3 rom img and after with ddr4 rom img but my tvbox not want start flash, it stuck in red light and my tv show not signal.
      My motherboard is this in pic3
      Maybe you should try flash image from here.

      Comment


        #48
        Originally posted by joemilan View Post

        Please kevin Flynn, help me....
        I have same problem with my Gearbest Alfawise H96 Pro+ 3GB/32GB, i tried flash ddr3 rom or ddr4 rom with USB_Burning_Tool but have error:
        with ddr3 rom at 4% see my pic1.
        with ddr4 rom at 7% see my pic2.
        I tried same with your method, create a sd card first with ddr3 rom img and after with ddr4 rom img but my tvbox not want start flash, it stuck in red light and my tv show not signal.
        My motherboard is this in pic3
        Well, I'm by no means an expert on these things, and I tried to be specific as to the exact sequence which allowed me to flash my box.

        All I can suggest is that you follow the instructions EXACTLY.

        As for whether or not you have a DDR3 or DDR4 box, you may have to open it and look at the board. Others have reported theirs as being DDR3 purchased around the end of 2016, but mine is DDR4 purchased at the beginning of 2017. Still others have indicated they might have a board marked DDR4, but the board actually has DDR3 ram.

        You can find pictures of what gearbest sent me, including pictures of the board here.



        Good luck.

        Comment


          #49
          Moved to: [ROM] Beelink GT1 Ultimate SCV1 ("Normal" Android) (DDR4) forum
          Last edited by ReaperMan; 20 April 2017, 22:55. Reason: Wrong forum

          Comment


            #50
            Not needed with supers rom those fixed. Apk for brightness built in
            Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

            Comment


              #51
              uggh, I ment to post in the [ROM] Beelink GT1 Ultimate SCV1 ("Normal" Android) (DDR4) forum.

              Will delete above post? and place in proper forum...hopefully!

              Comment


                #52
                Originally posted by joemilan View Post

                Please kevin Flynn, help me....
                I have same problem with my Gearbest Alfawise H96 Pro+ 3GB/32GB, i tried flash ddr3 rom or ddr4 rom with USB_Burning_Tool but have error:
                with ddr3 rom at 4% see my pic1.
                with ddr4 rom at 7% see my pic2.
                I tried same with your method, create a sd card first with ddr3 rom img and after with ddr4 rom img but my tvbox not want start flash, it stuck in red light and my tv show not signal.
                My motherboard is this in pic3
                Maybe you try this method to see if you can flash ddr4 firmware to your h96. When h96 connect success to ur pc, you don't release the reset button, keep holding the reset button and press Start button to burn the firmware. When the progress bar reach 7% formatting status, you release the reset button. If it is good, it will continue flash the firmware. Good luck.

                Comment


                  #53
                  Originally posted by Kevin Flynn View Post

                  No, I wasn't flashing wrong firmware, and no, the problem in linux was entirely different than the problem in Windows.

                  Regardless, here is what I did just now, apparently, to make it finally work. I'm not 100% sure its working as I type this, but it made it all the way through the update progress bar, restarted and displayed the SuperCeleron Beelink GT1 screen, and now its displaying some animated doodads, and I assume its going through some sort of initialization / first boot stage, so I'm letting it run for a bit, unless you tell me different. Okay, as I was typing, I made it to the "Welcome choose your system language" screen, so I think its worked.

                  Okay, for the final, I think it worked method, to flash this Gearbest Alfawise H96 Pro+ 3GB/32GB DDR4 box, in detail:

                  1) Used a Windows 10 laptop. Probably not important, but just listed for completeness sake. Linux method did not work.
                  2) I used a standard speed, budget priced, $13 at Walmart, 32GB Sandisk SD card.
                  3) I downloaded SuperCelerons "Standard Android" DDR4 ( not Android TV ) firmware as linked in this forum.
                  4) I unzipped the downloaded firmware file, to arrive at the .img file.
                  5) I renamed the .img file to remove the hyphen and underline, because another post at http://www.cnx-software.com/2016/11/...ogic-tv-boxes/ seemed to indicate special character were a problem. I tried once with special characters and had no luck.
                  6) I ran the Burn Card Maker utility as linked from this forum, changed the language to English, exited and restarted.
                  7) I selected the 32GB SD card as the output disk, and checked the following:

                  [x] To Partition and Format.
                  [x] erase_bootloader
                  [x] erase_flash
                  [forcefully erase all]
                  [x] reboot

                  then opened the renamed firmware .img file and clicked "Make" to create the firmware SD card.

                  Now, here is where its a little wierd, and I'm not sure if what I did made any difference.

                  I booted the SD card in the Alfawise box, while holding down the reset button, and when I saw the Android logo and progress bar, I let off the reset button. Immediately after that, for whatever reason, the update stopped and the screen went blank and the unit appeared to power itself off.

                  So, I repeated the above steps again, but this time I held the reset button in a little longer, and the update progress bar made more progress, and it looked like all was working, so I let off the reset button and by the time I sat down in my chair, the unit had powered itself down again.

                  So, third times a charm, I held down the reset button, powered the unit back up, and I kept the reset button held down the entire time. The Android logo and updating screen appeared, but it was all corrupted, like, bit shifted or missing a bit plane, but still obviously the screen. I kept the reset button held, and watched it as it made it all the way through the update process and eventually booted the new firmware.

                  Phew. So, for anyone that has this box ... this is how I got it to update. Use SuperCelerons DDR4 firmware, rename the .img file before creating the boot SD card to remove the hyphen and the underline, and use the SD card and not a USB flash drive or cable, and you should be able to avoid the hours of frustration and heartache I just went through.
                  Thanks to Scooter2014 and others for their input. Peace and hot dogs.
                  Lucky you !
                  I have a Mini M8S II and I'm in the same situation as you were. USB Burning Tool is stuck at 7% with the exact same error.
                  I tried the SD Card method as well and I'm stuck on the "Upgrading..." screen, the bar is fully load but nothing happen after.

                  Also I tried to flash the box unchecking "erase flash", it worked but the box never boot (stuck on the logo MEGABOX).
                  In recovery mode I get a "E: Cannot load volume /misc", I think maybe it's due to the fact that I can't erase the flash...

                  Comment


                    #54
                    my success to update gt1 ultimate is hold reset button plug side usb , still hold reset button , plug power, release reset button...maybe helps someone...

                    Comment


                      #55
                      [13:48:14 587][Global][Inf]--Catch DBT_DEVICEARRIVAL
                      [13:48:14 587][Global][Inf]--Scan usb device
                      [13:48:14 587][Global][Inf]--Aml scan WorldCup Device
                      [13:48:14 588][Global][Inf]--Host: Kontroler hosta zgodny z USB xHCI
                      [13:48:14 588][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e31&subsys_176c103c& rev_04#3&e89b380&0&a0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
                      [13:48:14 588][Global][Inf]---->Roothub:USB#ROOT_HUB30#4&4344002&0&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
                      [13:48:14 588][Global][Inf]-------->[Port0]NoDeviceConnected
                      [13:48:14 588][Global][Inf]-------->[Port1]NoDeviceConnected
                      [13:48:14 588][Global][Inf]-------->[Port2]NoDeviceConnected
                      [13:48:14 589][Global][Inf]-------->[Port3]NoDeviceConnected
                      [13:48:14 589][Global][Inf]-------->[Port4]NoDeviceConnected
                      [13:48:14 589][Global][Inf]-------->[Port5]NoDeviceConnected
                      [13:48:14 589][Global][Inf]-------->[Port6]NoDeviceConnected
                      [13:48:14 589][Global][Inf]-------->[Port7]NoDeviceConnected
                      [13:48:14 589][Global][Inf]--Host: Rozszerzony kontroler hosta USB rodziny mikroukładów z serii Intel(R) 7/C216 — 1E26
                      [13:48:14 590][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e26&subsys_176c103c& rev_04#3&e89b380&0&e8#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
                      [13:48:14 590][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&fc002ee&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
                      [13:48:14 590][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&27412f27&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
                      [13:48:14 590][Global][Inf]---------->[Port0]NoDeviceConnected
                      [13:48:14 590][Global][Inf]---------->[Port1]Other device
                      [13:48:14 591][Global][Inf]---------->[Port2]NoDeviceConnected
                      [13:48:14 591][Global][Inf]---------->[Port3]NoDeviceConnected
                      [13:48:14 591][Global][Inf]---------->[Port4]NoDeviceConnected
                      [13:48:14 591][Global][Inf]---------->[Port5]Other device
                      [13:48:14 591][Global][Inf]---------->[Port6]NoDeviceConnected
                      [13:48:14 591][Global][Inf]---------->[Port7]NoDeviceConnected
                      [13:48:14 591][Global][Inf]-------->[Port1]NoDeviceConnected
                      [13:48:14 591][Global][Inf]-------->[Port2]NoDeviceConnected
                      [13:48:14 592][Global][Inf]--Host: Rozszerzony kontroler hosta USB rodziny mikroukładów z serii Intel(R) 7/C216 — 1E2D
                      [13:48:14 592][Global][Inf]--DevPath:\\?\pci#ven_8086&dev_1e2d&subsys_176c103c& rev_04#3&e89b380&0&d0#{3abf6f2d-71c4-462a-8a92-1e6861e6af27}
                      [13:48:14 592][Global][Inf]---->Roothub:USB#ROOT_HUB20#4&e1028a3&0#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
                      [13:48:14 592][Global][Inf]-------->[Port0]USB#VID_8087&PID_0024#5&2920c867&0&1#{f18a0e88-c30c-11d0-8815-00a0c906bed8}
                      [13:48:14 593][Global][Inf]---------->[Port0]Other device
                      [13:48:14 593][Global][Inf]---------->[Port1]\\?\usb#vid_1b8e&pid_c003#6&1abecf8d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
                      [13:48:14 594][Global][Inf]---------->[Port2]Other device
                      [13:48:14 594][Global][Inf]---------->[Port3]NoDeviceConnected
                      [13:48:14 594][Global][Err]---------->[Port4]Unable to get driver key, 2
                      [13:48:14 594][Global][Inf]---------->[Port5]NoDeviceConnected
                      [13:48:14 594][Global][Inf]-------->[Port1]NoDeviceConnected
                      [13:48:14 594][Global][Inf]-------->[Port2]NoDeviceConnected
                      [13:48:14 594][Global][Inf]--Scan USB host controller complete
                      [13:48:14 594][Global][Inf]--Update data center with HubMap
                      [13:48:14 594][Global][Inf]--Update hub5 device data
                      [13:48:14 594][Global][Inf]--Update HUB5-1
                      [13:48:14 594][HUB5-1][Inf]--Update device path
                      [13:48:14 594][Global][Inf]--Update HUB5-2 \\?\usb#vid_1b8e&pid_c003#6&1abecf8d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
                      [13:48:14 594][HUB5-2][Inf]--Update device path
                      [13:48:14 594][Global][Inf]--Update HUB5-3
                      [13:48:14 594][HUB5-3][Inf]--Update device path
                      [13:48:14 594][Global][Inf]--Update HUB5-4
                      [13:48:14 594][HUB5-4][Inf]--Update device path
                      [13:48:14 595][Global][Inf]--Update HUB5-5
                      [13:48:14 595][HUB5-5][Inf]--Update device path
                      [13:48:14 595][Global][Inf]--Update HUB5-6
                      [13:48:14 595][HUB5-6][Inf]--Update device path
                      [13:48:14 614][HUB5-2][Inf]--Device is connected
                      [13:48:14 614][HUB5-2][Inf]--Close device handle 0x00000844
                      [13:48:14 676][HUB5-2][Inf]--Open device handle \\?\usb#vid_1b8e&pid_c003#6&1abecf8d&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed} 0x00000974
                      [13:48:19 750][HUB5-2][Inf]--0-7-0-16
                      [13:48:19 750][HUB5-2][Inf]--CheckFileRunState succeed
                      [13:48:19 751][HUB5-2][Inf]-- low_power
                      [13:48:19 756][HUB5-2][Inf]--Send command success
                      [13:48:19 760][HUB5-2][Inf]--Read command status success
                      [13:48:19 760][HUB5-2][Inf]-------------Download meson1.dtb-----------
                      [13:48:19 761][HUB5-2][Inf]--0-7-0-16
                      [13:48:19 761][HUB5-2][Inf]-- download mem dtb normal 88064
                      [13:48:19 761][HUB5-2][Inf]--Send download command success
                      [13:48:19 763][HUB5-2][Inf]--Read command status success
                      [13:48:19 779][HUB5-2][Inf]--Transfer complete
                      [13:48:19 779][HUB5-2][Inf]--Send download get_status command succeed
                      [13:48:19 779][HUB5-2][Inf]--get_status success
                      [13:48:20 296][HUB5-2][Inf]-------------ERASE FLASH-----------
                      [13:48:20 296][HUB5-2][Inf]--disk_initial 4
                      [13:48:20 296][HUB5-2][Inf]--Send command success
                      [13:48:21 428][HUB5-2][Err]--failed:[13:48:21 428][HUB5-2][Err]--Check command return failed
                      [13:48:21 475][HUB5-2][Err]--[0x30201004]UBOOT/Disk initialize/Send command/Error result
                      [13:48:21 475][HUB5-2][Inf]--Close device handle 0x00000974


                      Hey Guys,

                      I got stuck on 7% at burning tool - both stock and superceleron rom. Still same error. Anybody can help me ?

                      Thx,
                      klocki

                      Comment


                        #56
                        Hi Superceleron, that was awesome!
                        I followed your instructions and it worked, very easy. Now, I have a question, can I rollback to the original firmware? How can I proceed?
                        Thanks!

                        Comment


                          #57
                          Originally posted by guaronet View Post
                          Hi Superceleron, that was awesome!
                          I followed your instructions and it worked, very easy. Now, I have a question, can I rollback to the original firmware? How can I proceed?
                          Thanks!
                          same way...

                          Comment


                            #58
                            Why would you would be the only question id ask lol....
                            Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                            Comment


                              #59
                              Originally posted by superceleron View Post


                              NO WIFI OR BT READ BUGS SECTION![/B]
                              I'm trying to install the fix but I cant' t swipe to installa.. I have a trackpad but doesn't work...

                              May I have a help?


                              RESOLVED with a normal mouse for pc -.-
                              Last edited by KekkoLinkin; 30 April 2017, 18:18.

                              Comment


                                #60
                                Cant seem to get the wifi fix to flash. Boot into recovery, find the file on the sdcard, twrp asks which partition to flash it to with the options: logo, recovery, or boot. I am pretty sure it isnt logo, and I am assuming recovery is where TWRP is, so I have been attempting to flash it in boot. All appears to go fine, but when it reboots, I cant turn wifi on, it remains off even after attempting to click the on button. Do I need to do any wipes in TWRP before and/or after flashing? Any input would be appreciated!

                                H96Pro+ S912 3/32 DDR4

                                Edit: Figured it out, was trying to install the image in the zip file rather than just installing the zip file, doh! Installed the zip file and is now working great
                                Last edited by smashrvmco; 06 May 2017, 23:51.

                                Comment

                                Working...
                                X