Nexus 6p Stuck On Google Screen
I simply tried flashing Ubuntu Impact my Nexus 6P using the installer Snap on Ubuntu, and it looked like it went great until the device tried to practise its starting time kicking. Now, it is stuck on the Google logo, and information technology won't get anywhere. I forced the device to boot back into fastboot manner, and did the process again, simply I got the same consequence. I believe I did everything right. I had the device bootloader unlocked, TWRP was installed, then idk why it won't boot. Any thoughts?
@phillipprado How long did y'all wait? Starting time kick can take quite some time.
Hallo,
I take just the same problem with a nexus 6p... As a last solution I have tryed to delete files in partitions - goose egg helped.
The ubports-installer said everything has been installed successfully, but and so it stucks on ubports Recovery (Reboot System at present, Ubuntu Actions and Android deportment) but nothing works...
Subsequently rebooting it stucks wiht google boot screen. Now additional it is non recogniced by adb tools. I have reinstalled everything (adb tools, driver). When I plugin some other android mobile adb recognices the device, but when I plugin the nexus 6 there is no device recognized.
When I am in fastboot fashion no option is working - it ends up in google kicking screen.
Strange is the behavior. Sometimes I can enter the fastboot style, sometimes non - and then it is sometimes the ubports recovery and sometimes Android. AND earlier the google boot screens comes up the messages turn up "Your device software can't be checked for corruption. Delight lock the bootloader. Visit this link on some other device: 1000.co/ABH"...
Hallo,
I have just the same trouble with a nexus 6p... As a last solution I have tryed to delete files in partitions - aught helped.
The ubports-installer said everything has been installed successfully, merely then it stucks on ubports Recovery (Reboot System now, Ubuntu Actions and Android actions) but nothing works...
After rebooting information technology stucks wiht google boot screen. Now the side by side solar day additional information technology is non 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 half-dozen there is no device in the listing.
When I am in fastboot manner (nexus 6p) no choice is working (factory, …) - it ends upwardly in google boot screen.
Foreign is the behavior. Sometimes I tin enter the fastboot style, sometimes not - and then it is sometimes the ubports recovery screen and sometimes Android fastboot. AND before the google boot screens comes up the messages plough upwardly "Your device software tin't be checked for corruption. Delight lock the bootloader. Visit this link on another device: g.co/ABH"...
Have I killed my Nexus 6P?
Best regards
@sagrotan No, no adb subsequently succesful wink is normal.
In both these cases, I would suggest to load TWRP via recovery, wipe everything, and so flash android 7.1.two from the google factory builds. Run android once existence sure to to enable usb debugging, file transfer manner in usb settings and click the always allow this calculator prompt. Reboot to recovery, load TWRP, WIPE Data and Enshroud, and then reboot to bootloader and endeavour the installer again.
Okay,
next solar day, side by side attempt. I have plugged in the nexus 6p to my figurer and it was recognized. This fourth dimension I have used instead of "adb" -> "fastboot" commands.
I accept followed this video (but unzipped all the fourth dimension all files - read comments to the video ;O) and it works: https://world wide web.youtube.com/watch?v=PMltyWYseOw
At present I accept Android 7.one.2 installed and tin give Ubuntu Touche the next attempt ;O)
One question regarding USB settings: usb debugging was enabled, besides 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 accept started the installation process 4 or five 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 retrieve information technology would exist ameliorate if at that place was more output while processing from the installer.
The funiest affair: I was not alowed to open the logfile althouth it was in my binder! I have admin permissions, just not for that file! Now every bit it was actually successfully I am able to open the logfile (ubports-installer.log).
Best regards
sagrotan
@phillipprado Did you install stock Android 7.1 before yous tried to install (as the installer informed you lot)?
Yes, I take installed 7.ane.two
Installed TWRP to wipe "cache" and "data". I was non able to wipe data folder with fastboot (permission denied). But it worked with TWRP.
I take washed all the prerequest which are mentioned in the Installer....
@sagrotan humm that is strange. I ported this device, information technology took me over one year, I would have thought to accept constitute all potential problems.
Can yous see your hosts dmesg after the phone is stuck at the boot screen, if yous receive any messages there about an RNDIS interface after yous connect a USB cable?
Tell me, where I can find this bulletin on a windows 10 mashine... I know "dmesg" merely from linux.. I have but searched in the windows protocols for "RNDIS", but did not establish anything. Where I have to look for that kind of bulletin?
Another strange matter: Ubuntu Touch is working, but when I shutdown the nexus and boot again, first comes the message " "Your device software can't exist checked for abuse..." than the Google Logo and after some seconds ubunt bear on 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 kicking screen yet
@rocket2nfinity Its highly unlikely information technology will e'er get 1: The pictures are embedded in the bootloader and probably signed. Just to prefent tampering, and basically its a skillful idea 
@sagrotan So does information technology work now? 
Yes, it works!!! I accept but inserted the SIM Card and tin can make phonecalls ;O) Network as well 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)
all-time regards
sagrotan
@sagrotan high power consumption is likewise normal. Hopefully, Florian, or someone else, will figure out what triggers the operation cores to sleep.
Or, simply wait until the majority of N6Ps turn into 4-cadre devices....
@rocket2nfinity Or we decide as a customs to limit to iv cores for all users
@Flohack No!.... Allow me burn information technology until it'southward dead!
.... or at least until information technology gets twitchy enough.
Seriously, I practice think most will probable need to go to 4 cores at some signal. This thing gets hot nether load running all 8. It wasn't designed to accept all 8 running all the time. But equally long as I still have eight, might likewise use them.
The counter argument would of course be that it would exist simpler to keep everyone on four cores, and could preclude a fire or two. This affair runs quite hot using Libertine or annihilation processor intensive. And nigh "expressionless" N6Ps can be revived on iv core. So, 4 core keeps everyone running.
So, considering whether to get four cadre merely is something the community should hash out.
Yeah that was my thinking. From my offset N6P, the only I killed during repair, I know that most workflows are ok with iv cores also.
We anyways do not have the CPU-intense games or other apps that would benefit from 8 cores working at the same fourth dimension. Sadly also the CPU governor that allows proper schedulding of 4 fiddling and 4 big cores was lost somewhere in the kernel tree and is not possible to be activated anymore (back up was discontinued already when Google still pushed for that characteristic).
So electric current governor sees eight equal cores, and just assigned them randomly. That means large cores are already being used when little ones would be enough.
Source: https://forums.ubports.com/topic/5114/nexis-6p-stuck-on-google-boot-screen
0 Response to "Nexus 6p Stuck On Google Screen"
Post a Comment