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

kodaxx · 21 Jan 2020, 00:24

This post is deleted!

kodaxx · 21 Jan 2020, 04:15

Actually looks like I'm getting some install errors that I didn't notice before..

The relevant bit being:

adb: error: failed to copy '.halium-install-imgs.Zzv9k/rootfs.img' to '/data/rootfs.img': remote I/O error
.halium-install-imgs.Zzv9k/rootfs.img:....1 MB/s (2194800640 bytes in 257.129s)
I:    Pushing android image to /data via ADB
adb: error: failed to copy '.halium-install-imgs.Zzv9k/system.img' to '/data/system.img': remote Read-only file system
.halium-install-imgs.Zzv9k/system.img:... 1079.7 MB/s (1310720 bytes in 0.001s)

real	4m17.556s
user	0m0.107s
sys	0m0.762s
Error: Couldn't copy the files to the device, is it connected?
I: Cleaning up
umount: .halium-install-rootfs.oRFiq: not mounted.

flohack · 21 Jan 2020, 07:59

@kodaxx Did you wipe your system before? It might be needed if the partition was encrypted. In your TWRP, format all partitions and try again. A readonly filesystem can only be this, I hope

kodaxx · 21 Jan 2020, 17:07

@Flohack yes, I have completely wiped. I have pushed other files with no issue. When I run the tool, it looks like it's working, once it gets to 100% pushing rootfs, I get this error and everything fails.

At that point, pushing other files does not work either until I remount or wipe, and running the tool again immediately fails

flohack · 21 Jan 2020, 19:38

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

shing other files does not work either until I remount or wipe, and running the tool again immediately fails

Can you try to psuh those files manually with adb? Lets at least see if that works. I dont want to tell it, but it might be that your flash ram is faulty.

kodaxx · 21 Jan 2020, 20:00

Try to push which files manually? I can push pictures or other random files manually using adb without issue. If you mean to push the image files, I'm not sure where those are located - they seem to be created in a temporary directory and then deleted?

flohack · 21 Jan 2020, 20:57

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

ey seem to be created in a temporary directory and then deleted?

You can push the downloaded rootfs and the system.img for testing - they are bigger and hopefully trigger this error too.

You might also want to try another cable to be sure.

flohack · 22 Jan 2020, 20:27

Sorry guys, I somehow destroyed the device during a repair, and now I need to see to get a replacement coming. So I wont be able to work on the port for some days. But believe me, I want this to be done still!

phillip.walters · 23 Jan 2020, 02:35

@Flohack That's the one I've been using. I'm gonna see if I can dig a little bit deeper. Sorry if it's a few days, though. Work is wiping me out.

phillip.walters · 23 Jan 2020, 03:24

So I tried it again and it actually built and installed. When you say "Wait with some patience," how long are we talking?

flohack · 23 Jan 2020, 18:35

@phillip-walters Not sure, maybe 2 or 3 minutes. Do you get anything in dmesg -w on the host?

phillip.walters · 24 Jan 2020, 02:08

No. No RNDIS interface or anything. I'm wondering if my phone is hosed up.

rocket2nfinity · 24 Jan 2020, 06:51

@Flohack I'm a hardware guy. I'd be happy to help you troubleshoot your 6P if it wasn't something catastrophic

flohack · 24 Jan 2020, 07:35

@rocket2nfinity Well I changed battery, and that went fine, though one of the connectors became loose, so I planned another investigation for the next day.

On the next day, while being able to remove the parts which need to be warmed up with a hairdryer worked well, I could not get the cover off, and I used too much force and accidentially came between the screen and the PCB, instead between PCB and case. So the screen broke, and I have a full length of damaged area plus a crack in the screen.

I´m an idiot, I did not take out my contact lenses this eve, and so I couldnßt really see what I was doing

I wanted to get this as a daily driver, when I see that the porting status is well enough, but with that screen I cannot use it anymore. Instead I will look for a used one in medium condition, max € 100,-

It would be possible to change a screen (but then this unit also has the CPU bug and cannot run on all 8 cores, so I would not invest in it further) but I dont feel like doing this, or paying for that.

rocket2nfinity · 24 Jan 2020, 19:53

@Flohack Not an idiot. These things are getting harder to service everyday. I especially hate the ones with locking latches. They are designed to break, thus rendering the device unserviceable (unless you get crazy with the glue).

I agree, not really worth it for a device with the cores disabled. However, ebay has plenty in your price range, and if you go on xda-developers and tell the community what you're doing with Ubuntu touch, I'm betting you'll get donations. I'd donate here if there was a button to, and I certainly will there if you do.

There are a lot of us with Nexus 6Ps who would love to get Ubuntu Touch, or any of the other halium based ports on it.

flohack · 24 Jan 2020, 20:54

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

Nexus 6Ps who would love to get Ubuntu Touch, or any of the other halium based ports on it.

Great motivation, thanks. I am already chasing 2 devices. So sad that it might not be here for FOSDEM. I wanted to show it off on the conference but lets see

I am not really active on XDA, do you think it makes sense for UT people to hook up there with the "real" Android community?

BR Florian

rocket2nfinity · 24 Jan 2020, 23:46

@Flohack very sad, but still exciting.

I do think it's worth putting up UT ports up at xda-developers - for the devices that are known mostly working, on their specific device page. It might encourage the curious among the greater Android developer community to give UT a try. I myself have tried several OSes I wouldn't have (or even known about) if it hadn't been posted on XDA.

But if you don't, then add a donate button on ubports so we can encourage developers who are having successes with some monetary incentive. I have a few devices lying around that I would gladly put a port bounty on. For those of us who know enough to follow along and install a successful build but nothing more, this is how we can contribute to the project.

flohack · 1 Feb 2020, 01:38

@phillip-walters Can you boot into recovery right after it locks up with PWR + VolUp, and then get the contents of /sys/fs/pstore/console_ramoops? We might try this

flohack · 29 Jan 2020, 19:30

Good News! Tomorrow I should get a new device

flohack · 30 Jan 2020, 20:22

The new device has arrived. Unfortunately I somehow lost a few updates, so now I am back to a state where modem and network does not work...