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

user

Hey everyone, so I've decided to try as well.

So far, I've managed to flash the image to my 6p. It apparently boots up because I can ssh into it. However, the phone itself is stuck on the Google screen. I ran dmesg -w on the phone and get this happening in a loop:

[ 91.664666] init: Starting service 'perfd'...
[ 91.667370] init: Starting service 'time_daemon'...
[ 91.668649] init: Starting service 'qcamerasvr'...
[ 91.671437] init: Starting service 'ril-daemon'...
[ 91.672204] init: Starting service 'fps_hal'...
[ 91.716873] init: Service 'ril-daemon' (pid 1405) exited with status 1
[ 91.716895] init: Service 'ril-daemon' (pid 1405) killing any children in process group
[ 91.766425] init: Service 'qcamerasvr' (pid 1404) killed by signal 6
[ 91.766451] init: Service 'qcamerasvr' (pid 1404) killing any children in process group
[ 91.770755] init: Service 'per_proxy' (pid 1399) killed by signal 6
[ 91.770779] init: Service 'per_proxy' (pid 1399) killing any children in process group
[ 91.771072] init: Starting service 'per_proxy'...
[ 91.858763] init: Service 'per_mgr' (pid 1398) killed by signal 6
[ 91.858794] init: Service 'per_mgr' (pid 1398) killing any children in process group
[ 91.946013] init: Service 'thermal-engine' (pid 1400) killed by signal 6
[ 91.946044] init: Service 'thermal-engine' (pid 1400) killing any children in process group
[ 92.030662] init: Service 'perfd' (pid 1402) killed by signal 6
[ 92.030687] init: Service 'perfd' (pid 1402) killing any children in process group
[ 92.143446] init: Service 'time_daemon' (pid 1403) killed by signal 6
[ 92.143493] init: Service 'time_daemon' (pid 1403) killing any children in process group
[ 92.257922] init: Service 'qmuxd' (pid 1401) killed by signal 6
[ 92.257962] init: Service 'qmuxd' (pid 1401) killing any children in process group
[ 92.344606] init: Service 'fps_hal' (pid 1407) killed by signal 6
[ 92.344638] init: Service 'fps_hal' (pid 1407) killing any children in process group
[ 92.451645] init: Service 'per_proxy' (pid 1417) killed by signal 6
[ 92.451680] init: Service 'per_proxy' (pid 1417) killing any children in process group

I'm not sure if this has anything to do with the problem I'm facing or if I just need to send some signal to the device while ssh'd in. any ideas?

rocket2nfinity

@Flohack Still tells me, Anbox kennel is not installed! Please flash this first!

Did you just add it?

rocket2nfinity

@user Did you flash Android 7.1.2 the version required? It won't work if you flash any other version of Android.

If so, you may need to try using 4-core TWRP, and 4-core halium

user

@rocket2nfinity Thanks, I may not have successfully managed to flash the android image for some reason, so that could be the problem. I'll also make sure that my twrp is 4 core and I'll use the 4 core halium to see if that helps.

rocket2nfinity

@user Try 4-core, and if that works, switching to 8-core halium is flashing one file.

flohack

@user Yes that seems to be wrong vendor partition, please install stock Android 7.1.2 before...

flohack

@user You only need to use 4-core if you experiencing boot loops. If you have a damaged CPU cluster than the phone wont even boot TWRP with 8 cores. If that works, just use 8 cores always.

user

@Flohack Thanks for that info, I'll keep to 8 core for now in that case and reflash 7.1.2 and try again

user

@user For posterity:

I was using lineageOS prior to this, there was an issue flashing back to android. namely, mke2fs failed because unimplemented ext2 function while setting up superblock

quick google search said I need to go into the flash-all.sh and edit it.

I had to change the last line from fastboot update -w <image.zip> to fastboot update <image.zip>

the -w flag is to wipe userdata and cache.

So far, the image seems to be flashing without issues.

rocket2nfinity

@Flohack Ok, I'm having a problem. I thought I'd go back and reflash android and start from scratch, thinking that maybe that might be the hangup with camera. So, I did, successfully, several times. Android runs fine. Then I enable usb debugging and wipe dalvick, data, and cache. But every time I use the halium-install script after that, I get this:

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.uRLbP/system.img to 48434 (4k) blocks.
Begin pass 2 (max = 967)
Relocating blocks XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Begin pass 3 (max = 2)
Scanning inode table resize2fs: No space left on device while trying to resize .halium-install-imgs.uRLbP/system.img
Please run 'e2fsck -fy .halium-install-imgs.uRLbP/system.img' to fix the filesystem
after the aborted resize operation.
I: Cleaning up

Any help on what I can do to fix this and re-install UT?

flohack

@rocket2nfinity Is your PC out of disk space maybe?

rocket2nfinity

@Flohack No, this is regarding the file system on the phone. I had libertine on it. could that have changed the file system?

rocket2nfinity

@Flohack when I do e2fsck on it, it tells me its not an ext2 file system.

I don't get it. I completely wiped the device and re-installed android and it did the same again.

flohack

@rocket2nfinity It has nothing to do with the device, the preparation fails on your local PC. halium-install is a bit stupid sometimes. Try to run it as root maybe. Also reboot can help to clean up the mounted images that are still in your temp area ^^

rocket2nfinity

@Flohack No, it's definitely something not right with the phone. Just reflashed android and it now says:

extracting vendor.img (190 MB)...
archive does not contain 'vendor.sig'
wiping userdata...
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-l1pvvW: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata

Somehow my file system got messed up...

flohack

@rocket2nfinity Sorry no idea right now. Though I saw this error from above somewhere I forgot what was the fix ^^

flohack

Ok guys camera is now clear why it would not work: There are still beta packages that are not in the normal rootfs. So that one is only for people who want to fiddle a bit with the console. But the result is rewarding. Shall I link the description here: https://pad.ubports.com/p/InstallGStreamerCamera

I managed to get back to full working camera with that ^^

flohack

@Flohack Oh and I forgot it needs a system.img update as well... I will upload a new system.img in a minute....

user

@rocket2nfinity

try going into the flash-all.sh script and take out the -w flag on the last command then run it again?

rocket2nfinity

Can someone take a look at their phone's file structure and tell me what their drive is formatted to - especially system?

The problem seems to be with Android developer tools not functioning properly. Before I try it again with the updated tools, just want to make sure my drive is roughly the right sizes and formats (ext2 for instance)