Call for testing: Google/Huawei Nexus 6P (angler) owners
-
Finally some news:
- I have uploaded now 2 versions of the kernel, 4 and 8 cores, you might want to try 8 cores on your phones to see if you are affected by the CPU bug
- I have removed the root fs from my server. You can now use the 32bit rootfs that we build every day on our CI, which will contain latest fixes etc. IF
- system.img is updated also (download from my server)
Description has been updated (look for the downloads around item 1)
-
@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 rebootNow I just get the google logo over and over. I am able to boot into bootloader and recovery. So, what have I done wrong?
-
@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.
-
@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.
-
@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.
-
@Rondarius How do you run the script not using terminal? I used terminal to do everything.
-
@rocket2nfinity
You right click the script under Properties you are able to make it executable. -
I am half GUI half terminal user.
-
@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?
-
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.
-
@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.....
-
@rocket2nfinity did it work with 4 cores before?
-
@Flohack Never tried it. Always had it running on 8
-
@Flohack 8-core TWRP still works just fine. Android works with all 8 cores enabled
-
@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
-
@Flohack Android stock 7.1.2 - check
bootloader unlocked - checkoutput 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: falseI: 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: closedreal 0m0.016s
user 0m0.003s
sys 0m0.004s
I: Cleaning up
umount: .halium-install-rootfs.1KyDM: not mounted.
error: closed -
This post is deleted! -
@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: closedYes 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.
-
@Flohack Tried on two computers, one I am sure only has one copy of adb. Same result
-
@rocket2nfinity Its just strange that it worked for many people but you
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login