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

rocket2nfinity · 23 Apr 2020, 18:28

@Flohack I think either I did something wrong, or something isn't right in the build.

I used the updated instructions, item 3 from https://pad.ubports.com/p/nexus-6p-alphatesting

The halium install script errored out saying it couldn't connect with adb. So, I loaded TWRP and connected to adb through that. It errored out again because of a reboot command in the script. So, I decided to wipe the device from scratch, re-installed android and wiped dalvick, data, and cache. Then re-tried the install script. It worked with no errors. Did the next part replacing halium-boot-image with halium-boot-8-cores.img following the instructions in item 3 using these commands(I am using the 8 core TWRP and UT build previously with no problems):

./halium-install-standalone.sh -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img
adb reboot bootloader
fastboot flash boot halium-boot-8-cores.img
fastboot reboot

Now I just get the google logo over and over. I am able to boot into bootloader and recovery. So, what have I done wrong?

Rondarius · 23 Apr 2020, 18:30

@rocket2nfinity Did you use the flash-all script in the android rom? And did you run it in terminal? When I ran the script in terminal i got an error and the script stopped, I had to install the Android images manually instead.

rocket2nfinity · 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.

Rondarius · 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.

rocket2nfinity · 23 Apr 2020, 18:48

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

Rondarius · 23 Apr 2020, 18:49

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

Rondarius · 23 Apr 2020, 18:53

I am half GUI half terminal user.

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?

Rondarius · 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.

rocket2nfinity · 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.....

flohack · 23 Apr 2020, 21:25

@rocket2nfinity did it work with 4 cores before?

rocket2nfinity · 23 Apr 2020, 21:31

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

rocket2nfinity · 23 Apr 2020, 21:34

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

flohack · 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

rocket2nfinity · 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

rocket2nfinity · 25 Apr 2020, 01:44

This post is deleted!

flohack · 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.

rocket2nfinity · 25 Apr 2020, 18:26

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

flohack · 25 Apr 2020, 18:28

@rocket2nfinity Its just strange that it worked for many people but you

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