Encryption Pattern not showing up After boot - Nexus 6P Q&A, Help & Troubleshooting

I have a Nexus 6P and last night I tried rooting it with Nexus Root Kit by Wugfresh.
Everything went well. I was rooted.. I installed all my back ups and what not. This morning I was gonna install the dbrand skind I received a while bad so I turned the phone off. After skin installation when I tried booting the phone, it boots to the "Encrypt/decrypt Pattern" part and the pattern input area is not there.. it is blank.. Not the whole page, just the 3x3 dots for pattern input.
I have the stock rom, latest build
help.. please.. someone

Related

N7 wont boot after flashing Kernel - borderline bricked

Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
thebullfrog said:
Okay so I finally got my shiny new Nexus 32GB a couple days ago. Rooted it last night no problem. This morning I flashed Trinity Alpha4. worked great but my OC/governer/etc settings wouldn't stick. So I tried to flash the latest build of Faux Kernel. After flashing it got stuck in a boot loop. So I got back into Recovery and flashed Trinity back on again. Now it won't boot at all. After the splash screen the device completely locks up at a blank black screen. Went back to Recovery, wiped cache/dalvik, reflashed Trinity. After going through the "Android has been upgraded, optimizing apps" thing, it got stuck on "starting apps". After a couple min. I forced it to reboot, and again just gets stuck at a blank screen. I apparently completely forgot to do a Nandroid backup which I realized when I tried to restore it back lol.
Anywho, any thoughts on getting the thing to boot? Bricking it 2 days after I got it home is not my idea of a good time.
Click to expand...
Click to collapse
You might try and flash the stock kernel which should not allow any under/over clocking or under/over volting. Otherwise flash back to stock using the manual way here http://forum.xda-developers.com/showthread.php?t=1907796 or download the Nexus 7 toolkit and use it to do the same.
Try WugFresh's Nexus Root Toolkit. It has an option to go back to stock if you're soft-bricked.
Well I just did a factory restore/wipe (because Im SO looking forward to setting everything up again...) and it made zero difference. I'll try the stock kernel if someone could point me in the right direction to find a copy of it.
NVM found it. I'll give it a shot.
Ummmm okay then. I had my N7 turned off while looking for a solution to this fiasco. I picked it up so I could flash the stock kernel, and it had turned itself back on. Not only that, but it was fully booted up. Granted it's back to the initial setup after doing a factory restore, but there we go. It automagically fixed itself. Now to spend a couple hours putting everything back how it was. Yay.
Protip children: Always. Be. Nandroiding.

OEM STOCK S4 suddenly showing CUSTOM at boot! WTF?

My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
What's funny is, I am running the Task650 AOKP rom and Goldeneye rom and my custom padlock icon went away on its own. Many others have reported the icon randomly showing up too. I'm betting it will go away. Try rebooting your device a couple of times and if it really bothers you do a factory reset.
It's really not that big of a deal. Your're still running the samsung recovery.
Interestingly, my phone did this for the first time last night as well. I've been rooted since the beginning. Since you mentioned it I'm also using Nova launcher but can't imagine that matters.
Well my concern is when it happens at the wrong time, say during a warranty repair/replacement. A message like that is show and bam, no warranty.
I went to the AT&T Device Support Center for my Note II and they booted the phone, and then into download mode to see if it was modified or not (obviously I had returned to stock). So they do check
Nova launcher in not the culprit, because I am on TW and it does the same, in and out that message appears, haven't seen it in a week or 2, but it will pop up occasionally. I think anytime you approach the bootloader with a modification, that will show, and then disappear. I could be wrong, but there has been no certain pattern confirmed by anyone.
do any of you guys have a 64gb Sandisk microsd?
polish_pat said:
do any of you guys have a 64gb Sandisk microsd?
Click to expand...
Click to collapse
no. I have a 32GB Samsung micro-sd.
n19htmare said:
no. I have a 32GB Samsung micro-sd.
Click to expand...
Click to collapse
then try this: http://forum.xda-developers.com/showthread.php?t=2296014
polish_pat said:
then try this: http://forum.xda-developers.com/showthread.php?t=2296014
Click to expand...
Click to collapse
He can't do that if he's not rooted.
CZ Eddie said:
He can't do that if he's not rooted.
Click to expand...
Click to collapse
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom
polish_pat said:
he can root and then unroot. Or he can do the following: take our SD card, reboot twice and check if your system status is still custom
Click to expand...
Click to collapse
Just an update. rebooted a few times and CUSTOM message was still there. then I turned the phone off and left it off for a few minutes rebooted and it was gone.
WEIRD!
I did a bit of research and seems like this issue (If you wanna call it that) has been lingering around on GS3 too. Wonder what the cause is.
If someone knows or figures it out, please update this thread. THanks.
n19htmare said:
My phone is bone stock, never rooted, flashed modded. Last night I put the phone on charger and woke up to phone being locked up. I removed/reinstalled battery and booted up.
TO my surprise on boot below the samsung logo, it says "CUSTOM" with an unlocked picture of a lock.
Anyone else have this issue? I've never modified the rom/recovery nor have I rooted.
I do have Nova launcher and Foxfi......could those be a culprit?
Update: I tried going into stock recovery. WHen I boot with buttons pressed it says "Recovery Booting" but nothing happens and phone reboots itself.
Click to expand...
Click to collapse
Same thing happen with me by replacing the battery. Just now. Nova launcher was acting up earlier. Galaxy S4 AT&T I was trying to keep this virgin I guess I now have to root and unroot.. But is this an option actually because they have protected the firmware so far to say that you cannot make yours virgin anymore without the original virgin firmware??
i have a sgh i337 at&t.. my phone suddenly freezed and went to bootloop
It suddenly freezed and after some minutes, it automatically went to bootloop.. All I see is the at&t logo for hours.. After that, I wiped data n cache from recovery and the phone started to work well, but after 30 minutes or more , same things are repeated.. Freezes and Wents to bootloop.. And the option I only have is to do a hard reset which works only for 30 minute.. And when I use the phone for 5 minutes after reset and then I restart it, it freezes on lock screen and goes to bootloop.. Please help.. Will flashing a custom ROM will work?.. I want to change the carrier and remove at&t.. Please help..
I had this same exact problem, with stock S5. One thing I noticed with mine that no one else mentioned was if I went into settings and then storage it would say SD Card - READING I believe and I couldn't access my pictures. Nor could I format it or erase it when i was doing a factory reset through the settings options. My phone would also freeze, and then there was times the screen would go black and on the very top of the screen would only display the time and battery life the time would change as well as the battery percentage but I was unable to leave that screen except if I would hold the power button down it would show me all the normal reset, power off options and I was able to select any one the options available. What ended up working for me was, removing the SD Card and replacing it. Then I did a factory reset through the settings options menu. Once it finished I instantly ( did not proceed with setup) I turned the phone off and then held the power button the volume up and home button and reset it that way as well. Once it rebooted I noticed the problem was gone and everything was back to normal.

[Q] nexus 4 died on reboot one week after flashin, now stuck in boot loop

Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
albinhj said:
Hi!
Rom: CM12 20150320
Recovery: CWM 6051 touch
Bootloader: MAKOZ30f (if that helps)
About a week ago i unlocked and flashed my nexus 4 to CM12. After that the phone has worked well until today. The phone was acting a bit laggy, so I thought a reboot would be nice. However, after the reboot it only gets past the first google screen. After that it gets stuck in a weird animation (see picture) I have never seen before for about 5 minutes, and after that the screen just shows a black image (completely black but you can see the screen is still on). This repeats when I retry. I can still enter bootloader and recovery.
Any idea why this happened? And how to fix? I guess a reset (or reflash?) could solve it, but it would be nice if that was not necessary. =)
I made two observations during the day, related?
-some app prompted for some CM12 updates, but I had no time to deal with them at the time so I just closed the app.
-while playing music from spotify while working, the sound lagged for a second at a time, about one time per hour.
Thanks in advance! Let me know if there are details missing!
Click to expand...
Click to collapse
Flash stock image from google... maybe some stuff from CM12 go wrong...
Not use CWM recovery...better TWRP...this is updated.

[Q] Nexus 4 update not working

Hi Everyone
First post on this forum and first time trying to fool around with android.
I just replaced a new lcd + touch+ frame to an N4 its build was JOP40C
1) I said to myself why not trying to update manually to lollipop, well the N4 stayed stuck while booting with the colored dots.
2) I said to myself lets go back to JOP40c but that does not exist on google anymore so tried for hours many until JDQ39 and finally could get into my phone, but the number 6 and 7 where missing on the touch (???).
3) I said to myself well lets reinstall again and got totally my touch working.
4) Once done I received automatically an OTA from google, said to myself well lets do google, well the same happened again the phone was kind in a bootloop with the colored X.
Any help would be appreciated on why I am not able to update this phone, do I miss something that I should know and not found over all what I have read over the internet.
I have spent at least 3 working days on this and now I have to go back, make a living and hope that a pro will help.
I assume you're flashing the factory image and then you get a bootloop? Go into the stock recovery after flashing and do a factory reset.
Sent from my Nexus 5 using XDA Free mobile app
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
invitro59 said:
Tried that too lots of post over the internet about that but nothing keep getting blocked on the colored cross or bowls.
Tried also with Nexus Root Toolkit
Just received again the google update to 4.3 jelly beans on the N4 pressed restart and install then got the green robot and saying installing system update.
Then the phone got stuck in his bootloop and tird again the factory reset.
Still stays stuck in its bootloop.
Click to expand...
Click to collapse
Try checking the SkipSoft.net Android Tool Kit
I hope that helps
You ever check all sensors work?
Maybe the same problems with this http://forum.xda-developers.com/nexus-4/help/issue-sensors-update-t2973047#post60470486
HI
I have checked with another N4, installed a software and checked the differences.
Well you are wright on this one the luminosity and proximity sensors are not showing any sign of life.
It is already past midnight here in France, so I will check tomorrow if I can do something on these sensors.
Will keep you posted if I can fix the sensors and do an update after that.
Hi
How stupid I am, after screen change connector sensor was not pluged in and since I had placed the plastic cover with the screws, could not see it anymore.
At least after have lost so much time, next time I will post a little earlier and at least tonight I will go bed less stupid than yesterday
Google just send the 4.3 upgrade and everything went smooth just no touch anymore so cannot use the phone.
ok installed lollipop but still the same no touch, but now I can install an update but not use the phone.
Anyone on that touch problem

72 Hour Lock Bypass

So before I get into this know you need to have a custom recovery.
Hey guys, so I don't know if there is a thread about this or not but I think this might be helpful in certain occasions. So recently I found out about googles 72 hour lock down when you reset your password. Which means if you own a nexus phone and you try to flash a new rom you must sign in with your last google account. BUT they don't let you because of their 72 hour security so you have to wait 3 days to finally use your phone again unless you have a back up. So this happened to me last night, couldn't sign in with the new password, so I put my sim back in my nexus 6 and decided I could wait. I slept on it and this morning decided to figure out a way how. So it was actually an easy fix. I installed chroma rom with no gapps knowing I could get into the system, then rebooted and went back to recovery and flashed gapps recommended in the chroma thread. After I got a few force closes but nothing I couldn't tap out of and I signed into the device by going to settings-accounts. (BTW I got to settings by dropping down status bar and clicking the gear icon as the launcher was not working.) From there I went to developer mode and checked the box OEM unlocking. Went back to recovery cleaned wiped my phone and installed rom and gapps. Since I checked on the OEM unlock I didn't have to use an email to get into the phone. Now I have everything working like normal! so i hope this helps at least someone in the future! [emoji1]
Sent from my Nexus 6P using Tapatalk

Categories

Resources