Nexis 6P stuck on Google boot screen



  • I just tried flashing Ubuntu Touch on my Nexus 6P using the installer Snap on Ubuntu, and it looked like it went great until the device tried to do its first boot. Now, it is stuck on the Google logo, and it won't go anywhere. I forced the device to boot back into fastboot mode, and did the process again, but I got the same result. I believe I did everything right. I had the device bootloader unlocked, TWRP was installed, so idk why it won't boot. Any thoughts?



  • @phillipprado How long did you wait? First boot can take quite some time.



  • f697604c-8e4a-43c0-aaad-87bcf2525909-grafik.png Hallo,
    I have just the same problem with a nexus 6p... As a last solution I have tryed to delete files in partitions - nothing helped.
    The ubports-installer said everything has been installed successfully, but then it stucks on ubports Recovery (Reboot System now, Ubuntu Actions and Android actions) but nothing works...
    After rebooting it stucks wiht google boot screen. Now additional it is not recogniced by adb tools. I have reinstalled everything (adb tools, driver). When I plugin another android mobile adb recognices the device, but when I plugin the nexus 6 there is no device recognized.
    When I am in fastboot mode no option is working - it ends up in google boot screen.
    Strange is the behavior. Sometimes I can enter the fastboot mode, sometimes not - then it is sometimes the ubports recovery and sometimes Android. AND before the google boot screens comes up the messages turn up "Your device software can't be checked for corruption. Please lock the bootloader. Visit this link on another device: g.co/ABH"...
    Hallo,
    I have just the same problem with a nexus 6p... As a last solution I have tryed to delete files in partitions - nothing helped.
    The ubports-installer said everything has been installed successfully, but then it stucks on ubports Recovery (Reboot System now, Ubuntu Actions and Android actions) but nothing works...
    After rebooting it stucks wiht google boot screen. Now the next day additional it is not recogniced by adb tools. I have reinstalled everything (adb tools, driver). When I plugin another android mobile adb recognice the device, but when I plugin the nexus 6 there is no device in the list.
    When I am in fastboot mode (nexus 6p) no option is working (factory, …) - it ends up in google boot screen.
    Strange is the behavior. Sometimes I can enter the fastboot mode, sometimes not - then it is sometimes the ubports recovery screen and sometimes Android fastboot. AND before the google boot screens comes up the messages turn up "Your device software can't be checked for corruption. Please lock the bootloader. Visit this link on another device: g.co/ABH"...

    Have I killed my Nexus 6P?

    Best regards



  • @sagrotan No, no adb after succesful flash is normal.

    In both these cases, I would suggest to load TWRP via recovery, wipe everything, then flash android 7.1.2 from the google factory builds. Run android once being sure to to enable usb debugging, file transfer mode in usb settings and click the always allow this computer prompt. Reboot to recovery, load TWRP, WIPE DATA and CACHE, then reboot to bootloader and try the installer again.



  • Okay,
    next day, next try. I have plugged in the nexus 6p to my computer and it was recognized. This time I have used instead of "adb" -> "fastboot" commands.
    I have followed this video (but unzipped all the time all files - read comments to the video ;O) and it works: https://www.youtube.com/watch?v=PMltyWYseOw
    Now I have Android 7.1.2 installed and can give Ubuntu Touche the next try ;O)

    One question regarding USB settings: usb debugging was enabled, also file tranfer mode (is set to MFT), but where to I find the setting: "always allow this computer prompt"?
    Additional I have disabled "verify apps over USB"

    best regards
    sagrotan



  • Okay, I've got it!!! Ubuntu Touch is working now on the Nexus 6P, BUT it was realy hard. The UBPorts Installer is not working properly. Less messages what was going on in the background. I have started the installation process 4 or 5 times, until it works.
    The installer says -> transfering files although the connection to the nexus was interupted (when it is rebooting and not reconnecting).
    Says "installation was succesfully" altthough it was not.

    I think it would be better if there was more output while processing from the installer.

    The funiest thing: I was not alowed to open the logfile althouth it was in my folder! I have admin permissions, but not for that file! Now as it was really successfully I am able to open the logfile (ubports-installer.log).

    Best regards
    sagrotan



  • @phillipprado Did you install stock Android 7.1 before you tried to install (as the installer informed you)?



  • Yes, I have installed 7.1.2
    Installed TWRP to wipe "cache" and "data". I was not able to wipe data folder with fastboot (permission denied). But it worked with TWRP.
    I have done all the prerequest which are mentioned in the Installer....



  • @sagrotan humm that is strange. I ported this device, it took me over one year, I would have thought to have found all potential problems.

    Can you see your hosts dmesg after the phone is stuck at the boot screen, if you receive any messages there about an RNDIS interface after you connect a USB cable?



  • Tell me, where I can find this message on a windows 10 mashine... I know "dmesg" only from linux.. I have just searched in the windows protocols for "RNDIS", but did not found anything. Where I have to look for that kind of message?



  • Another strange thing: Ubuntu Touch is working, but when I shutdown the nexus and boot again, first comes the message " "Your device software can't be checked for corruption..." than the Google Logo and after some seconds ubunt touch starts? It seems I can't get rid of google ;O)



  • @sagrotan That is normal because the bootloader is unlocked. N6P doesn't have it's own boot screen yet



  • @rocket2nfinity Its highly unlikely it will ever get one: The pictures are embedded in the bootloader and probably signed. Just to prefent tampering, and basically its a good idea 😉



  • @sagrotan So does it work now? 🙂



  • Yes, it works!!! I have just inserted the SIM Card and can make phonecalls ;O) Network also works.
    The only thing is a high energy consumption, but I think I can live with that.
    Yip yip hurray - this was my first experience flashing a ROM ;O)

    best regards
    sagrotan



  • @sagrotan high power consumption is also normal. Hopefully, Florian, or someone else, will figure out what triggers the performance cores to sleep.

    Or, just wait until the majority of N6Ps turn into 4-core devices....



  • @rocket2nfinity Or we decide as a community to limit to 4 cores for all users 🙂



  • @Flohack No!.... Let me burn it until it's dead!
    .... or at least until it gets twitchy enough.

    Seriously, I do think most will likely need to go to 4 cores at some point. This thing gets hot under load running all 8. It wasn't designed to have all 8 running all the time. But as long as I still have 8, might as well use them.



  • The counter argument would of course be that it would be simpler to keep everyone on four cores, and could prevent a fire or two. This thing runs quite hot using Libertine or anything processor intensive. And most "dead" N6Ps can be revived on 4 core. So, 4 core keeps everyone running.

    So, considering whether to go four core only is something the community should discuss.



  • Yeah that was my thinking. From my first N6P, the only I killed during repair, I know that most workflows are ok with 4 cores as well.

    We anyways do not have the CPU-intense games or other apps that would benefit from 8 cores working at the same time. Sadly also the CPU governor that allows proper schedulding of 4 little and 4 big cores was lost somewhere in the kernel tree and is not possible to be activated anymore (support was discontinued already when Google still pushed for that feature).

    So current governor sees 8 equal cores, and just assigned them randomly. That means big cores are already being used when little ones would be enough.


Log in to reply