So I have a Google Pixel 2 and I installed the android P preview via sideload but I had my bootloader locked now I can try to toggle OEM unlock and put in my pattern but after I put my password in it still says it's off idk what to do I haven't tried to flash the 8.1 factory image or unlocking yet but idk if I'll be able too there's I'm almost 100,% sure it's not a Verizon model I don't have any Verizon apps and on 8.1 I could toggle this on and it's not greyed out
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
EnormoDerClown said:
I am also not able to change this in the preview, maybe you could install the 8.1 OTA (afterwards a factory reset)to go back. Flashing a factory image will not work with a locked bootloaded, OTA also works with locked BL.
Click to expand...
Click to collapse
That wouldn't brick my phone?
Before you attempt anything extreme, I suggest factory reset your phone and do the minimal setup to get into the settings and try toggling
I did still no luck
To be fair: i can not guarantee that, but i can just imagine 3 scenarios:
1. Update fails, OTA install fails
2. OTA installs but a lot of FC´s with apps (factory reset afterwards shoudl get rid of that)
3. Everything installs and is functional without doing anything (i don´t think so).
i would expect, that option 2 would occure
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
AaronGavin said:
Installation failed, called Google to see if they could do anything they only referred me to the Android beta website, guess I'm stuck till DP2 comes out
Click to expand...
Click to collapse
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
March update could just be to old, April update could work because of newer data. OTA checks whether the update is older/newer.
quakeaz said:
This is a long shot, but try disabling your lock screen security PIN if you have one, then check the setting again. If still greyed out, try setting a PIN, then check again. This typically prompts for your PIN, maybe somehow something got messed up in the sideload.
Click to expand...
Click to collapse
That actually worked xD thank you
AaronGavin said:
That actually worked xD thank you
Click to expand...
Click to collapse
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
It was never greyed out just after I put my password in it wouldn't turn on the slider and at first I just thought maybe it is on but bugged out but after I removed my password it just turned on properly I'm about to test it as soon as the factory image downloads again
quakeaz said:
Glad to hear. Did it become un-greyed without lock screen security, or after it was re-enabled? I have seen similar behavior before, so I thought it might be the same thing in P.
Click to expand...
Click to collapse
Back on 8.1 ?
Related
I've had this really weird problem ever since the update for 4.4.4 got downloaded to my phone automatically as soon as it was released for the Verizon moto g. I'll be using my phone like normal and this black screen will pop up for a second as if it is asking me to do something but nothing is there then it will go away. It happens quickly and doesn't do anything but it is very annoying. I'm wondering if it is because I told the update not to install yet and set a reminder for later? Although it isn't time for that reminder to go off yet and this happens about every 5 minutes or so. I haven't installed any new apps or downloaded anything and I even factory reset my phone and the problem remains.
I'm not rooted and my boot loader is still locked. Running stock android 4.4.2 on Verizon xt1028.
Ideas?
lilrob1213 said:
I've had this really weird problem ever since the update for 4.4.4 got downloaded to my phone automatically as soon as it was released for the Verizon moto g. I'll be using my phone like normal and this black screen will pop up for a second as if it is asking me to do something but nothing is there then it will go away. It happens quickly and doesn't do anything but it is very annoying. I'm wondering if it is because I told the update not to install yet and set a reminder for later? Although it isn't time for that reminder to go off yet and this happens about every 5 minutes or so. I haven't installed any new apps or downloaded anything and I even factory reset my phone and the problem remains.
I'm not rooted and my boot loader is still locked. Running stock android 4.4.2 on Verizon xt1028.
Ideas?
Click to expand...
Click to collapse
It's from the OTA notification service.I have the same issue, coz I'm lazy to disable the update service atm.
To clarify, the problem you get is a quick flash-in/flash-out in black color. Happens quite quick.Right?
liveroy said:
It's from the OTA notification service.I have the same issue, coz I'm lazy to disable the update service atm.
To clarify, the problem you get is a quick flash-in/flash-out in black color. Happens quite quick.Right?
Click to expand...
Click to collapse
Yeah that's exactly what happens! I figured it had to do with the OTA… so how can I stop it from doing that? or should I just update to 4.4.4? Are there any issues?
lilrob1213 said:
Yeah that's exactly what happens! I figured it had to do with the OTA… so how can I stop it from doing that? or should I just update to 4.4.4? Are there any issues?
Click to expand...
Click to collapse
You can disable it if you have root.In case you do, then go to /system/priv-app/ and find motorolaOTA.apk , change its permissions to 0000 and you`re good :>
liveroy said:
You can disable it if you have root.In case you do, then go to /system/priv-app/ and find motorolaOTA.apk , change its permissions to 0000 and you`re good :>
Click to expand...
Click to collapse
Okay… I don't have root… but the verizon moto g can only get temp root without write access… will that still work??
lilrob1213 said:
Okay… I don't have root… but the verizon moto g can only get temp root without write access… will that still work??
Click to expand...
Click to collapse
No idea, just give it a try.
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
I'm having issue unlocking my pin after rebooting my phone, I'd have to input my pin and select ok multiple times in order to unlock my phone and screen shuts off in between untill it randomly unlocks after a few times trying to input pin. I have tried to Google the problem to no avail. Anyone gets this or know the solutions? I'm using face unlock on us based s8+ if that helps anyone.
Same here this morning. Finally 15th attempt did a factory reset as I had set to do in such circumstance.
Restored from Samsung and Google and going again in about an hour. Now I'm leery about using pin*face security.
Just updated my custom rom to the latest version. Maybe help, maybe not.
mlrinoc said:
Same here this morning. Finally 15th attempt did a factory reset as I had set to do in such circumstance.
Restored from Samsung and Google and going again in about an hour. Now I'm leery about using pin*face security.
Just updated my custom rom to the latest version. Maybe help, maybe not.
Click to expand...
Click to collapse
I find it odd you have the issue on custom Rom, I have that issue on stock os.
vyurdin said:
I find it odd you have the issue on custom Rom, I have that issue on stock os.
Click to expand...
Click to collapse
Perhaps Samsung rolling out Bixby changes yesterday, which both roms share.
I'm thinking of trying out Android 12 Beta soon. Anybody try it out? Any bad bugs?
better wait , my phone is stuck in setup process "keep date from old phone" > "enter pin" > keep data from..." blabla
Seems great to me. No issues whatsoever!
I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!
Beta 1 works well so far. There were some minor issues that disappeared, so not even sure if it was the Beta causing it.
Magisk/root works
EdExposed doesn't work yet -- or at least, I couldn't get it to work
So far it's been perfect. No issues whatsoever. Been using it since yesterday when it released. I did perform a factory reset as always. It's really nice I think.
gettinwicked said:
I cleaned flashed to it from DP3 yesterday. Loving it so far! And I wasn't sure about some of the UI changes from the leaked photos.
The bugs I'm getting are:
Bubbles work, but there's a messages 'screen' that opens for each one that you see in recents.
The new conversation widgets still only shows the person. No message or anything. It does launch either messages or whatever bubble.
There's still a pill on the top of the screen when it's locked. Looks like the navigation pill. It started for me on DP3.
That's all I've seen so far. No crashes. Root works but safety net fails, Viper4Android works, GPay works.
Go get it!
Click to expand...
Click to collapse
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable
Anyone able to get safetynet passing?
emkay5775 said:
I've had the same issue (having the pill on the lock screen) since android 11... Otherwise, seems to be relatively usable
Click to expand...
Click to collapse
With A11? Weird! It only started doing it for me on DP3. I even reset my phone on it to try to fix that and a couple other issues. Clean flashed into beta 1 and it's still there...
Go for it. But be sure about how you follow the installation instructions. Don't forget, the Android 12 beta is still a beta release with some known issues and can brick your device. Be cautious.
sw6n21 said:
Anyone able to get safetynet passing?
Click to expand...
Click to collapse
As far as Google pay working? It works for me
I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?
StrangerWeather said:
I'm keen to install but does anybody know if Barclays and Natwest apps work with 12 Beta?
Click to expand...
Click to collapse
Replying to my own question: yes, they work.
is there anyway to swap backbutton? tried magisk modules that worked with android 11. but bootloops
I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug
I'm currently using beta, some bug available, it's ok for me using for daily driver. I don't care bug
Well, just flashed Android 12 beta today and I'm love it so far. I'm really like the Samsung style AOD clock.
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
Chris PL said:
I have installed Android 12 beta. After booting into Recovery mode and performing Hard Reset after rebooting, the system hangs at verify pattern. I mark the correct pattern I have used previously, the system accepts it and then comes back a step back. I cannot enter the system, I cannot upload an older version of the system. Phone locked, bootloader locked, I can't start debugging mode because the system won't let me go any further after verifying the correct pattern or PIN.
Someone help?
Click to expand...
Click to collapse
You need to unlock it and flash again.
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
creezalird said:
Have you tried restarting the phone? I had 1 time yesteday too, suddenly, the phone was idle, and when I checked Wifi found nothing. Restarted and then it works again. Not sure if related to March update or some other stuffs
Click to expand...
Click to collapse
Restarted and also factory reseted
YassGo said:
Restarted and also factory reseted
Click to expand...
Click to collapse
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
simplepinoi177 said:
Wow...after a factory reset, that's pretty much it!
You can try doing the reset network settings button (you can search it in the search bar in Settings or find it in the Internet setting on top right button [wrench and reset circle]), but I can't imagine it doing better than a factory reset.
The best/last thing that can be suggested, since it states you are rooted in your sig, is to flash the latest Full Factory image (March) and/or with the "-w" intact (since you stated that you did a factory reset so I imagine your phone is wiped anyways) and see if that doesn't fix the issue. The best 3 methods to achieve this is using the online Android Flash Tool, the tool PixelFlasher that can be found here on XDA, or manually using platform-tools (you must've used one of these in the past to be rooted, so I assume you're familiar).
Hopefully you get it figured out. Worst case, the phone is still under manufacturer's warranty and you should be able to get it replaced with a refurbished if it truly isn't resolved...
Click to expand...
Click to collapse
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
YassGo said:
Hi friends,
Since yesterday, my wifi and bluetooth don't work anymore. When enabling them, it scans nothing . I've made a factory reser without any psuccess !
Never seen an issue like this on any phone...
Thanks for your help guys
Click to expand...
Click to collapse
YassGo said:
Yesterday I dirty flashed March update bmand disabled verity stuff. It forced me to format data. Is it enough or is there a better clean flash way ?
Btw I tried the reset network thing without success
Click to expand...
Click to collapse
Mmmm...when you stated you "factory reset", it wasn't clear whether it was from the OS system setting or when flashing...
I don't think there is a "better clean" way to flash and/or reset the phone. If you're not flashing/sideloading OTA (which you aren't)...
It (reset network) was a very long shot, but worth exploring just in case it hadn't been tried yet...
I mean, I guess you can try Android Flash Tool and even go as far as to flash to both slots and relock bootloader to get a pure, stock status and see if the problem truly sticks that way. You've already wiped the phone, so I doubt this could hurt or you lose anything important at this point. But I can't imagine dirty flashing the latest March update (or even including disabling the verity stuff) wouldnt've addressed or reset things to set the issue straight...
If it's still there after relocking the bootloader and flashing to both slots, then it's warranty exchange time (if you ever want to resolve the issue)...
*most likely the flashing somehow wrecked the system board radio enough...
If/When this works, you'll need go through the trouble of unlocking the bootloader, and reflashing the Full Factory image with disabling the verity & validation stuff, before rooting again.
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
YassGo said:
Ok I think it's a hardware problem. When I shake my phone, I hear something moving.
I dropped it from my bed saturday night. The wifi module must be disconnected.
Let's send it to Google....
Click to expand...
Click to collapse
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
jaseman said:
Are you sure that what you are hearing move when you shake the phone is just the OIS for the camera? All phones with OIS will make some noise when you shake them.
Click to expand...
Click to collapse
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
YassGo said:
I don't know my friend. Google will send me the return process tomorrow. They told me 7 to 10 days for repairing. Why did I sell my old oneplus ?
Click to expand...
Click to collapse
I have had several OnePlus phones and they have all been great for me! However, I am having no problems with my 7 Pro either so....YMMV