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

@kz6fittycent you can always get the latest images from our CI as follows:

• The rootfs is built multiple times by day and can be downloaded here: https://ci.ubports.com/job/xenial-hybris-rootfs-arm64/
• The system image is built daily but it does not change very often, probably you dont need to replace it that much. Download this here: and then extract it from the archive from this location https://ci.ubports.com/job/Device Compatibility Images/job/halium-angler/ , and put it in the very same location in /system/var/lib... or, if you use the halium install only, just put it into /data partition - anyways just overwrite it, dont create an additional one somewhere

E.g.:

Does this answer your question? Not the rootfs is then what you would have in the devel channel. There is no direct download for RC or stable, but we are quite stable also in devel ^^

Thanks! Will I need to wipe before installing these coming from the older files or just flash over them?

@Flohack can you provide the latest system.img and rootfs so I can flash to a new version that would allow me to perform updates more easily? I have used these files to get to where I'm at.

@neothethird

Testing on Nexus 6p isn't going well. Will not flash - stalls at 75%. I opened an issue on GH that was closed as a "duplicate". That was for 0.7.4-beta.

That said, see this thread for what I've been dealing with getting UBPorts flashed to the angler.

This is an odd problem and there aren't any real logs to provide you. It just will not flash through the snap (or AppImage, or .deb). Seems to be specific to the angler. Or maybe just mine? I dunno - but I can flash manually, which might indicate something.

@Flohack yes and I'd start it out with everything one would need to get the OS flashed - everything...

@rocket2nfinity PM'd you

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

@kz6fittycent Don't remember how old the image is you used. If your build does not have update channels, running the installer will bring you up to date.

That's the same cable I used to flash it manually - good cable - bad installer?

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

@kz6fittycent Don't remember how old the image is you used. If your build does not have update channels, running the installer will bring you up to date.

Do I need to run through the entire installation process again (via the UBports Installer)? It is still giving me grief when trying to push the new update over - did not tick the bootstrap button.

Alright everyone - I got it.

I was misunderstanding what was being said - this is how I did it:

• Download files needed here
• Flash 7.2.1 (stock ROM from Google)
• Flash 4-core TWRP after flashing stock image
• Boot into android
• Enable USB Debugging in Developer menu < - this wasn't needed because I did the rest via TWRP
• Boot into TWRP
• Wipe dalvik, data, and cache
• Reboot into recovery (TWRP)
• Run manual installation steps:

sudo apt install qemu-utils binfmt-support qemu-user-static e2fsprogs sudo simg2img binutils

cd /path/to/files/

./halium-install-standalone.sh -p ut ubports-touch.rootfs-xenial-armhf.tar.gz system.img

adb reboot bootloader

fastboot flash boot halium-boot-4-cores.img

fastboot reboot

I now have a working installation of UBPorts on my angler

Thanks all!

P.S. I have extra files on my NC server that I needed, including the 4-core.img, the 7.2.1 files from Google, TWRP-4-core and it's associated boot script. - if you need them, I have them. Otherwise, they should all likely be hosted by the team in one spot.

This is where I'm at using the manual setup instructions provided (thanks @rocket2nfinity ).

I: Unmounting images
I: Pushing rootfs and android image to /data via ADB
I:    Pushing rootfs to /data via ADB
adb: error: failed to copy '.halium-install-imgs.RNTTa/rootfs.img' to '/data/rootfs.img': remote couldn't create file: Permission denied
.halium-install-imgs.RNTTa/rootfs.img: 0 fil... pushed. 43.1 MB/s (2752512 bytes in 0.061s)
I:    Pushing android image to /data via ADB
adb: error: failed to copy '.halium-install-imgs.RNTTa/system.img' to '/data/system.img': remote couldn't create file: Permission denied
.halium-install-imgs.RNTTa/system.img: 0 fil... pushed. 59.3 MB/s (2621440 bytes in 0.042s)

Followed this set of instructions:

./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

/data, dalvik, and cache were wiped so I don't know what would cause this.

I ran the script with sudo as I was getting permission denied previous to do anything without it. Should I have su'd to root?

All very odd to me.

@augustblake Pop! 20.04 - I'm actually a snap "developer", too. Snaps work fine for me - this one is no exception. The .deb didn't work either. Tried the AppImage, too. Same results.

I think the problem is either the phone or some step that's getting missed or misunderstood on my part.

@rocket2nfinity

Okay, so, as I mentioned, the manual flash instructions are a hot mess - hard to read and definitely not clear cut. At least the one's I found here: https://pad.ubports.com/p/nexus-6p-alphatesting

I didn't see any others about manual installation. You posted several threads/posts but each one has some difference in the instructions/methods - leading to some confusion and likely issues.

Basically, need something very clear cut - exactly what order things are done and what is done - maybe even with screenshots. I realize that this can be a tall order during the testing phase but in my line of work (dev-ops), I have to clearly outline each step taken in order to determine any deviation that may have occurred on the user's end that would lead to failures or issues. Given the current state, it's kind of all over the place.

Please don't think I'm being a jerk, or overly critical, I'm trying the help the project along and I am going to assume that there is some dummy out there like me facing similar issues.

Now, on to the next bit:

When using the installer, this is what I see (screenshot). What I need to know is, do I tick both blocks in the ubports-installer? See screenshot.

Because if I do, it just BLODs. If I don't tick the bootstrap box, it just fails to load the OS. Basically just quits.

Okay - last time and I give up.

Here are the CURRENT steps I am taking as of RIGHT now -

• Flash 7.1.2
• Flash TWRP 4-core
• Perform wipe AND format /data
• Run Installer app
• Select bootstrap stuff and format personal data
• Select devel channel (actually I've tried them all so I don't think this matters one bit at this point
• Begin installation
• BLOD

I am going to just walk away from this thing and let it BLOD endlessly. Sometimes the BLOD will end and get to the recovery. I doubt it though.

JUST TO BE CLEAR-
I have also tried leaving TWRP on there just to see what would happen - nothing. Nothing happened.

Okay - pardon my ignorance with Android devices...

When you say "format whole drive" - what exactly do you mean? Are you using TWRP to format? This isn't wipe partition is it?

BTW, I just double-checked and I HAVE indeed formatted the /data drive. So then the question becomes, are there others that need to be formatted? Because the documentation/steps seem to differ depending on the post and definitely within the installer snap.

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

@kz6fittycent This I dont understand, did you flash Android 7.1.2 first and then TWRP? YOu must get into TWRP somehow...

To be clear - yes I can get to TWRP and even use it - but cannot flash UBPorts -

If I choose to flash the bootloader in the installer, it bootloops

If I choose to forego flashing the bootloader, and try to force it to use TWRP, it fails to flash the OS.

Sometimes, I think a video chat would do better - trying to explain what's happening in a post seems straight forward enough but it never actually is.

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

@kz6fittycent This I dont understand, did you flash Android 7.1.2 first and then TWRP? YOu must get into TWRP somehow...

I flashed 7.1.2 via the ./flash-all.sh script provided from Google. This was to ensure that everything needed was there.

Then flashed TWRP.

Then the rest.

Bear in mind that I've tried it several ways outside of manually installing everything as suggested by @rocket2nfinity - need clean instructions to ensure I don't goof it up royally.

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

@kz6fittycent Yeah i've been struggling getting this to work on my nexus 6p as well. I got it working in the past but I just went to install it again because i had to go back onto android for a moment and now im struggling to get back on to ubuntu touch. I follow all the same procedures as well. install twrp, format, install 7.1.2. then im using ubports from snap on ubuntu 20.10. I just get to the ubuntu recovery screen but only options are reboot and wipe / factory reset but nothing will get me into ubuntu touch. I've gone through the steps 4 times now. now im trying to install on different channels right now on edge. wish me luck

I don't even get to the recovery screen - immediate BLOD if I follow the default instructions.

@rocket2nfinity those notes you mentioned are a hot mess lol. Maybe they need some cleaning up. There are enough typos that might lead to a mistake in process/steps.

BTW, I am running on Linux (Pop!_OS 20.04).

If I don't install the 4-core TWRP, it'll just go straight to bootloop. I've tried just loading it before and it was a no go. There are two files required for it to work as intended. The mod'd TWRP and a shell script that edits the kernel to run on 4 cores. Without that last bit, it'll BLOD.

@Flohack

Here's a truncated version of the logs I'm seeing:

"/home/james/snap/ubports-installer/320/.cache/ubports/system-image/ubuntu_command\",\"/cache/recovery/\"],\"code\":1}"}
{"level":"warn","message":"lost connection to device"}

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

@kz6fittycent humm no but can you describe exactly whats the sequence of events on the phone? So, if you begin in e.g. TWRP recovery:

• device detected - YES
• channel selected, bootstrap checked yes (No will assume a working recovery available) - TRIED BOTH WAYS - see below
• Reboot to bootloader (it will flash new recovery) - see below
• Reboot to recovery (You will see tiny yellow text) - yes
• Download of partitions - yes?
• Reboot to recovery again (This time Yumi appears with blinking eyes, flashing partitions) - never happens
• reboot to live system - nope

Thats basically how it should be. Where did you stop?

• Flashed 7.1.2
• Flashed twrp-3.2.1-0-fbe-4core-angler.img
• adb sideload needed kernel mod to prevent immediate BLOD - regardless of ROM/OS
• wipe partitions in TWRP
• Start up ubports-installer (snap) - tried older version you listed and latest from stable branch of the snap - same results either way
• bootstrap selected
• flashes bootstrap - then just BLOD's

Alternative steps taken:

• Everything's the same up until the next bullet point
• deselected bootstrap
• ignore errors
• everything is "successful" until about 75%-80% of when it's pushing system files to device when it fails. Logs show no errors. Literally nothing. Just a sudden "stop".
• tried 2 different cables and same result <- that's all that I have...

I can flash Android ROM's with the same cable and same TWRP.

What is ubports-installer actually pushing to the device when it's flashing a "new recovery"?

I believe this is the problem for me and possible others that might experience this.

• does this recovery allow for the 4-core mod or does it assume 8-cores?

Perhaps there's a workaround? I'd really like to see this working on my device.