Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] AlfaWise H96 PRO+ 3/16Gb - 3/32Gb - 3/64Gb - SCV7A 7.1.2 (DDR3/DDR4 and 9377 Wifi Chipset)

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

    Originally posted by tombraga View Post

    that means, that i have to open the box and "break the wall", because i heared that the only ota-usb port is hidden. There are more 2 usb connectores hiddeen in the box and one of it i have to make the connection with the usb a cable.

    is this correct?
    No, that's not what I heard. I heard that the USB burning port is "port 3" which on the same side as the reset button.

    This site has an image of the box with labelled ports:



    I have not done it myself yet, because I always did SD card burning. But I just bought a USB A-to-USB A cable which arrived today, so I will try it myself sometime soon. Or wait a bit and an expert will be here to confirm 100% for you.
    Last edited by TheBloke; 02 August 2017, 16:28.

    Comment


      Originally posted by Belyakov View Post
      I dont have an usb a to usb a cable, I read that TheBlokeÂ*did it with burn card maker 2.0.2, that's why I tried with itÂ*
      Gonna try again renaming the image file to update.img
      Sorry, I had forgot to put about update.img in my first post I have updated it now so it is right for future.

      I think that now you have the "red X", your only option is to do the USB burning method. That is what I read in this thread. So you need to get yourself a USB A to USB A cable.

      Note that superceleron said since the very first post that USB burning method is the correct and safe one. I did SD card only because I did not have (at the time) a USB A to USB A cable. So SD card method is always "unsupported" I guess

      Comment


        Just to be clear, the flashing method with an SD card and burn card maker works? Sadly I don't have the USB cable to use USB burning  tool method 

        Comment


          Originally posted by Belyakov View Post
          Just to be clear, the flashing method with an SD card and burn card maker works?Â*
          It did work for me when I renamed the file to update.img. That's all I can confirm for sure.

          I believe it definitely won't work now that you have a red X. At that point you must use USB A cable. I haven't yet experienced that personally, but that's what it says in this thread. (You should probably read the whole thread if you want full details on everything.)

          Comment


            Update : the upgrade process with an SD card was sucesfull, just had to rename the image file to update.img


            Update 2: can't upgrade to Ota v3, i opened the update app, looked for the Ota in the local update, choose wipe data and finally confirm, but the box just shutdown itself.

            Enviado desde mi ONEPLUS A3000 mediante Tapatalk


            Last edited by Belyakov; 03 August 2017, 04:10.

            Comment


              Originally posted by Belyakov View Post
              Update : the upgrade process with an SD card was sucesfull, just had to rename the image file to update.img
              Great news. I think I understand this now. The issue is simply that superceleron's default filename has a special char in it that the updater doesn't like. Specifically ,the filename is SCV2-BETA-A7.1-Alfawise.H96.Pro+.img and the + at the end stops the update, giving the red X.

              I experienced this before when I was doing stock ROM flashes - I tried three different ROMS, two worked, one didn't. The one that didn't, which I now remember also gave the red X, had ( and ) in its filename. At the time I just thought it was a bad ROM download, but now I realise what caused the problem.

              That is why renaming to update.img works, but I think there is nothing special about the name 'update'. It could be any name, just as long as there are no special characters (except dot, dash and underscore. which are OK.)

              So superceleron if you would consider renaming the ROM file to remove that + I think everyone could use Burn Card Maker and it would work immediately. I know you prefer the USB method But SD card is really convenient for people without a USB A-to-USB A cable. Rename Pro+ to Pro and I think it will just work. (And anyway your ROM would work for H96 Pro users as well as Pro+, so it makes sense )

              Originally posted by Belyakov View Post
              Update 2: can't upgrade to Ota v3, i opened the update app, looked for the Ota in the local update, choose wipe data and finally confirm, but the box just shutdown itself.
              Don't know why that would be, sorry. You copied the ZIP file direct to the root of an SD card and found the file and selected it in Update app? Did you use a freshly formatted SD card? I don't know if it would cause problems if you used an SD card that also contained update.img and the updater files. If you used the same SD card, you might want to try again.

              If you still can't get it working, what I would do myself is try the whole process over from the beginning to make sure everything is done right. With these steps:
              1. Flash the stock 7.1.1 ROM using SD card, and for this flash tick all 4 boxes in Burn Card Maker - including tick "Erase Bootloader"
              2. Boot to confirm it is back to vanilla/stock ROM
              3. Now flash SCV2 again, renaming the ROM file to update.img (or just remove the + from filename), and for this burn do not tick "Erase Bootloader" (tick 3 boxes but not Erase Bootloader)
              4. After confirming SCV2 is OK, format a clean SD card and copy the SCV3 OTA zip file to its root, then select it in OTA update, choose Wipe Data, Confirm. It should reboot into TWRP Recovery and do the update.

              I don't know if all this is required, but it is what I would try - and it only takes a few minutes once you've done it a few times Just to ensure everything is being done from a stock position, including stock bootloader. The OTA update is meant to reboot into TWRP to do the update, so maybe the reason it did not for you is some issue with Bootloader

              Or perhaps someone more experienced will know the possible reason for this before you need to do things over.

              Comment


              • superceleron
                superceleron commented
                Editing a comment
                k i rename it as Plus instead of the +!
                Thks for the warning!

              Had to reboot manually to twrp holding the reset button, and update manually the Ota.zip
              Found this error and finally installed the Ota


              Enviado desde mi ONEPLUS A3000 mediante Tapatalk



              Last edited by Belyakov; 03 August 2017, 14:38.

              Comment


                Ummmmm Install V2 THEN select Ota... Thats the best way as Ota to update from V2 to version 3.
                Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                Comment


                  I indeed did that, and did not worked 

                  Comment


                    Then your doing something else wrong or not same device as Alf because it works perfect for everyone else. Re check that you unpack zip to directory and copied zip onto sd formated correctly. Ensure not corrupted file.

                    Flashed it 60 or more times so its proven working.
                    Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                    Comment


                      The box is working just fine, but i had to run the update to Ota v3 manually with twrp 

                      Comment


                      • superceleron
                        superceleron commented
                        Editing a comment
                        well at least you could flash it

                      Originally posted by superceleron View Post

                      Dont do it.. that is why i installed a moded supersu app....
                      In the next build it will be unrooted then you guys can install supersu or magisk by twrp as your linking.
                      Hey Superceleron,

                      Can You add Samba/CIFS to your Build as I can NOT get the mount to work on your svc3 ...

                      thanks in advance

                      Michael T.
                      3.0.x Lollipop firmware RK3288 By Wasser/ My Standard Remote IR
                      CVSB-K200-Wireless Mini QWERTY Keyboard / Motion Mouse for Android RF
                      Rii Mini i25 Qwerty Keyboard/Motion Mouse For Android RF
                      Media Flow Suite ... 24 TB ReadyNas Pro wired 1 GB Ethernet

                      Comment


                        Samba does not work with 7.1

                        Comment



                          Can someone help me? I have a wireless logicool mouse that works perfectly, for example in a Beelink GT1, but not in this box. Is there any configuration change I can make. If you connect a wired logitech mouse, it works fine.
                          Both in the stock Rom and V3, nothing

                          Comment


                            Hi all.
                            I have an Alfawise h96 pro plus 3g 32g 7.1 that I got from Gearbest about 2 weeks ago.
                            Sadly it hasn't worked correctly since the first minute I plugged it in, with constant crashes and error codes like, "play store has stopped working" and "SPMC has stopped working please close or restart the app".

                            I did at least 5 factory resets to try and resolve the issues, with no luck.

                            In the end I just gave up and put it back in the box ready to post back to Gearbest and ask for a refund.

                            As it turns out, if you choose to send an item back to Gearbest you have to pay for the postage, in my case that would of cost me approximately £7 so I decided to have Gearbest send me a replacement at a cost of $30 approximately £23 and I get to keep the faulty/temperamental box.

                            I'm a bit of a technophobe when it comes to stuff like this, but am willing to give stuff a try. Dose anyone think that this ROM could do the trick and get the box working for me?

                            If so, could someone point me a step by step tutorial on how to load this ROM, and the correct files and programs/tools that I would need to attempt such a thing. I have an micro sd card and a windows laptop.

                            Many thanks in advance.
                            Simon.

                            Comment

                            Working...
                            X