• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Call for testing: Google/Huawei Nexus 6P (angler) owners

Scheduled Pinned Locked Moved Porting
627 Posts 43 Posters 447.0k Views 13 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R Offline
      rocket2nfinity @Rondarius
      last edited by 23 Apr 2020, 18:44

      @Rondarius Just re-installed bootloader manually with fastboot and tried again with the flash all script. No errors. But still hung at the google logo. When I re-installed android, I did reboot it to turn on usb debugging, then rebooted to TWRP to wipe Dalvick, data, and cache before I ran the install instructions in item 3. So the bootloader did properly install.

      R 1 Reply Last reply 23 Apr 2020, 18:47 Reply Quote 0
      • R Offline
        Rondarius @rocket2nfinity
        last edited by 23 Apr 2020, 18:47

        @rocket2nfinity Did you run the script in the terminal? I ran the script not using the terminal and it gave no errors but it did in the terminal.

        4 Google Pixel 3A
        1 Google Nexus 6P
        2 Google Nexus 5
        2 Pinephones
        2 Sony Xperia X

        R 1 Reply Last reply 23 Apr 2020, 18:48 Reply Quote 0
        • R Offline
          rocket2nfinity @Rondarius
          last edited by 23 Apr 2020, 18:48

          @Rondarius How do you run the script not using terminal? I used terminal to do everything.

          R 1 Reply Last reply 23 Apr 2020, 18:49 Reply Quote 0
          • R Offline
            Rondarius @rocket2nfinity
            last edited by 23 Apr 2020, 18:49

            @rocket2nfinity πŸ™‚ You right click the script under Properties you are able to make it executable.

            4 Google Pixel 3A
            1 Google Nexus 6P
            2 Google Nexus 5
            2 Pinephones
            2 Sony Xperia X

            R 1 Reply Last reply 23 Apr 2020, 18:57 Reply Quote 0
            • R Offline
              Rondarius
              last edited by 23 Apr 2020, 18:53

              I am half GUI half terminal user.

              4 Google Pixel 3A
              1 Google Nexus 6P
              2 Google Nexus 5
              2 Pinephones
              2 Sony Xperia X

              1 Reply Last reply Reply Quote 0
              • R Offline
                rocket2nfinity @Rondarius
                last edited by rocket2nfinity 23 Apr 2020, 18:57

                @Rondarius I guess I have some old habits. I always right click scripts to make them executable but then I start them with ./ anyway. I never just click the file. Guess I should take the easy path from time to time.

                Were you able to get the new build running on your device?

                1 Reply Last reply Reply Quote 0
                • R Offline
                  Rondarius
                  last edited by 23 Apr 2020, 19:00

                  Sorry, I haven't tried it yet. It feels like it is something else that is not working maybe @Flohack could help you out here.

                  4 Google Pixel 3A
                  1 Google Nexus 6P
                  2 Google Nexus 5
                  2 Pinephones
                  2 Sony Xperia X

                  R 1 Reply Last reply 23 Apr 2020, 19:04 Reply Quote 0
                  • R Offline
                    rocket2nfinity @Rondarius
                    last edited by 23 Apr 2020, 19:04

                    @Rondarius That's what I was thinking. Re-installed Android worked, bootloader is 3.68 and is working and able to reboot to bootloader or recovery, radio is 3.81. No errors installing anything after re-installing android, it all said ok. But then, no boot.....

                    F 1 Reply Last reply 24 Apr 2020, 18:47 Reply Quote 0
                    • F Offline
                      flohack @rocket2nfinity
                      last edited by 23 Apr 2020, 21:25

                      @rocket2nfinity did it work with 4 cores before?

                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                      R 2 Replies Last reply 23 Apr 2020, 21:31 Reply Quote 0
                      • R Offline
                        rocket2nfinity @flohack
                        last edited by 23 Apr 2020, 21:31

                        @Flohack Never tried it. Always had it running on 8

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          rocket2nfinity @flohack
                          last edited by 23 Apr 2020, 21:34

                          @Flohack 8-core TWRP still works just fine. Android works with all 8 cores enabled

                          1 Reply Last reply Reply Quote 1
                          • F Offline
                            flohack @rocket2nfinity
                            last edited by 24 Apr 2020, 18:47

                            @rocket2nfinity Please try to verify whats in the pst:

                            • Phone reset to stock Android 7.1.2 by Google
                            • Bootloader unlocked
                            • Please paste output of halium-install

                            I am about to preparing a custom script for the UBports installer, that will make things much easier to handle

                            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                            R 2 Replies Last reply 25 Apr 2020, 01:42 Reply Quote 0
                            • R Offline
                              rocket2nfinity @flohack
                              last edited by 25 Apr 2020, 01:42

                              @Flohack Android stock 7.1.2 - check
                              bootloader unlocked - check

                              output of hallium -install script:

                              Debug: Chosen rootfs is ubports-touch.rootfs-xenial-armhf.tar.gz
                              Debug: Chosen android image is system.img
                              Debug: Chosen release is ut
                              Debug: Compress images before pushing: false

                              I: Writing rootfs into mountable image
                              I: Writing android image into mountable image
                              I: Running post installation tasks
                              enabling Mir ... [done]
                              enabling SSH ... [done]
                              Please enter a new password for the user 'phablet':
                              Enter new UNIX password:
                              Retype new UNIX password:
                              passwd: password updated successfully
                              I: Shrinking images
                              e2fsck 1.44.1 (24-Mar-2018)
                              resize2fs 1.44.1 (24-Mar-2018)
                              Resizing the filesystem on .halium-install-imgs.eazbo/system.img to 48516 (4k) blocks.
                              The filesystem on .halium-install-imgs.eazbo/system.img is now 48516 (4k) blocks long.

                              I: Unmounting images
                              I: Pushing rootfs and android image to /data via ADB
                              I: Pushing rootfs to /data via ADB
                              adb: error: connect failed: closed
                              I: Pushing android image to /data via ADB
                              adb: error: connect failed: closed

                              real 0m0.016s
                              user 0m0.003s
                              sys 0m0.004s
                              I: Cleaning up
                              umount: .halium-install-rootfs.1KyDM: not mounted.
                              error: closed

                              F 1 Reply Last reply 25 Apr 2020, 15:53 Reply Quote 0
                              • R Offline
                                rocket2nfinity @flohack
                                last edited by rocket2nfinity 25 Apr 2020, 01:44

                                This post is deleted!
                                1 Reply Last reply Reply Quote 0
                                • F Offline
                                  flohack @rocket2nfinity
                                  last edited by 25 Apr 2020, 15:53

                                  @rocket2nfinity said in Call for testing: Google/Huawei Nexus 6P (angler) owners:

                                  adb: error: connect failed: closed
                                  I: Pushing android image to /data via ADB
                                  adb: error: connect failed: closed

                                  Yes the data cant be pushed to the device. Maybe you have multiple adbΒ΄s on your computer and they are fighting with each other? I had this once.

                                  My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                  R 1 Reply Last reply 25 Apr 2020, 18:26 Reply Quote 0
                                  • R Offline
                                    rocket2nfinity @flohack
                                    last edited by rocket2nfinity 25 Apr 2020, 18:26

                                    @Flohack Tried on two computers, one I am sure only has one copy of adb. Same result

                                    F 1 Reply Last reply 25 Apr 2020, 18:28 Reply Quote 0
                                    • F Offline
                                      flohack @rocket2nfinity
                                      last edited by 25 Apr 2020, 18:28

                                      @rocket2nfinity Its just strange that it worked for many people but you πŸ™‚

                                      My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                                      R 3 Replies Last reply 25 Apr 2020, 18:33 Reply Quote 0
                                      • R Offline
                                        rocket2nfinity @flohack
                                        last edited by rocket2nfinity 25 Apr 2020, 18:33

                                        @Flohack It worked for me before too using your rootfs from your server. But with the new rootfs it hangs

                                        1 Reply Last reply Reply Quote 0
                                        • R Offline
                                          rocket2nfinity @flohack
                                          last edited by 25 Apr 2020, 18:39

                                          @Flohack what does the "ut" after -p do in the hallium-install script?

                                          F 1 Reply Last reply 25 Apr 2020, 19:44 Reply Quote 0
                                          • R Offline
                                            rocket2nfinity @flohack
                                            last edited by rocket2nfinity 25 Apr 2020, 18:53

                                            @Flohack Oops! I do have two adb installed on both machines. Forgot that I used both and needed su adb to flash a ROM to a Mediatek device.

                                            Thanks for the tip!

                                            1 Reply Last reply Reply Quote 0
                                            175 out of 627
                                            • First post
                                              175/627
                                              Last post