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
- channel selected, bootstrap checked yes (No will assume a working recovery available)
- Reboot to bootloader (it will flash new recovery)
- Reboot to recovery (You will see tiny yellow text)
- Download of partitions
- Reboot to recovery again (This time Yumi appears with blinking eyes, flashing partitions)
- reboot to live system
Thats basically how it should be. Where did you stop?
-
@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 sideloadneeded 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
stablebranch 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.
-
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"} -
@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
-
Darn, no luck for me. I have another nexus 6p that seemed to accept the ubuntu touch but this one which ive had it on in the past is being stuborn lol.
-
I would suggest a few things. First, use the linux installer, people are having problems with the windows one. If that doesn't work...
Follow the manual install instructions. You can succesfully upgrade using the installer after that. Load, do not install, 4-core TWRP in recovery. Wipe all partitions. Flash android factory stock 7.1.2 using fastboot/TWRP. Boot android, enable usb debug, set usb mode to MTP, unplug-replug phone, click yes on the always allow this computer prompt. Reboot to recovery. Load TWRP. Wipe data and cache.
At this point try the installer using linux. If it doesn't work, then manually flash halium and ubports system image as per instructions at the beginning of the thread.
-
@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.
-
@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.
-
@kz6fittycent This I dont understand, did you flash Android 7.1.2 first and then TWRP? YOu must get into TWRP somehow...
-
@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.shscript 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.
-
are there instructions to install manually without ubports installer? I'd like to try that
-
@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.
-
-
-
-
@kz6fittycent Fogot about the 4 core script. Yes, install TWRP the first time to get factory android installed and running.
-
I fixed my problem.. I was not following the steps properly. I would install twrp then sideload oem 7.1.2 then i would jump right into ubports installer.
i realized i needed to install twrp again after i sideloaded and format the whole drive then ubports worked correctly..
-
@augustblake Yeah the factory installation encrypts your drive ^^
-
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
/datadrive. 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. -
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
develchannel (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.
