Hey guys,
I flashed this ROM on my LG G2 (802) http://forum.xda-developers.com/lg-g2/development/rom-official-mokee-source-project-t3274849/page2. Everything has been okay so far.
In the Mokee thread I read installing gApps would work like this:
"you can go MokeeCenter after starting rom, there you can download the small gapps integrated into the system and have a lighter and clean rom."
Unfortunally for me there was no option to download gApps via "MokeeCenter". Of course I found Settings -> MokeeCenter.
So I decided to download open_gapps-arm-6.0 (has been the minimal version, I think) and flashed it.
After I rebooted into system, I now am stuck at a popup which immediately and continiously pops up, saying "setup assistent has been closed". So I cannot do anything else than pressing "ok ok ok ok ok ok"
Big problem for me now is, that for some unknown reason, I cannot boot into twrp recovery using one of the hardkey methods.
I usually was able to do it like this:
- Shut down.
- Press power + volume down until LG logo appears.
- Release only power button, then immediately press power button again (while still pressing volume down).
I think I now tried any of the other methods as well (power + volume up instead of down... or release power AND volume down, then press both again... and so on...)
None of them work for me.
I might have to mention, that after the first appear of the popup loop, I read something about flashing "bootstack-d802-CAF-signed" as part of a solution.
I did so, but it diddn't help. Instead of a solution this might be part of my problem, because since I was able to flash it I obvously must have been able to enter twrp before this step.
What should I do now?
By the way: Can some of you tell me, if the annoying crackle/hissing of my headphones is gone with Android M?
I want to know this, because this has been the ONLY reason for me to flash Android M, since I wasn't able to find a solution for Android Lollipop (CM12). I find it extremely (!) uncomfortable to talk to people using my bose qc25 headphones/headset since my Lollipop update, because everytime when a person speaks just a few words with longer pauses between the single words, I have sound errors and hissing/crackles and even some really wired kind of "distortion" at the beginning of each single word and often have to ask people to repeat what they said.
The headphones themselves sound absolutely okay, it's just with the LG G2 phone. (i.e. a friend's Samsung S5 works fine with the bose qc25)
If this bug isn't gone with Android M (or at least fixable) I think I will buy a new cellphone instead of trying to unbrick my LG G2 if unbricking will be a pain in the ass, so I am very interested in an answer regarding the sound bug as well.
Thank you for reading.
with best regards,
Milan
I now have been able to setup a guest account. Running the guest account, I can quit the popup by pressing "ok" once. It doesn't return and is followed by "Gallery stopped" which I am able to quit too. But as guest I cannot get root access to use a software based reboot to recovery, right?
follow these steps
1. go to settings and find applications menu
2. select find system applications from menu
3. find installiation wizard or something else (i am using my rom in Turkish "Kurulum Sihirbazı".
4. click on it and edit permissions
5. enable people and phone sections.
6. cheers
gttrk said:
1. go to settings and find applications menu
2. select find system applications from menu
3. find installiation wizard or something else (i am using my rom in Turkish "Kurulum Sihirbazı".
4. click on it and edit permissions
5. enable people and phone sections.
6. cheers
Click to expand...
Click to collapse
Thank you
Problem was, I could not navigate because there has been this fu*** popup always on top.
I have been able to enable root access and advanced shutdown options by clicking almost 1000 times "ok" at the annoying popup while I used another finger to tap something at the screen as soon as possible. Scrolling was like stuck motion this way... So I have been able to enter twrp and flash another rom.
Nonetheless I tested calling a person with the guest account (by allowing phone calls for guests via the same "tapping-technique"... took me aboout 10 minutes) and found out, there are exactly the same hissing /crackling problems with Android M than with Android L. So I will try Android Kitkat now. This bug is very common. Is there someone who can tell me a working solution? I am pretty sure my phone did not have this bug when I bought it with Kitkat OS installed. So a kitkat rom is my last hope right now.
regards,
Milan
Hi! As the title says, I somehow can't use that option.
I had fingerprint scanning for a while but got tired of it so wanted to go back to just swiping but that option is not clickable. I have tried switching to other password methods and that works just fine and I also deleted my fingerprint. But it still doesn't work to use the just swipe option... Any solution? Except factory reset.
Hamstern said:
Hi! As the title says, I somehow can't use that option.
I had fingerprint scanning for a while but got tired of it so wanted to go back to just swiping but that option is not clickable. I have tried switching to other password methods and that works just fine and I also deleted my fingerprint. But it still doesn't work to use the just swipe option... Any solution? Except factory reset.
Click to expand...
Click to collapse
Hi,
It could be that you have a device administrator active (Google Device Manger) that requires the screen to be locked by PIN or password. To check and disable it go to Settings> Advanced settings> Security> Device administrators.
Cheers
I tried that now when you answered, but disabling that feature didn't help either..
This option is locked in kernel by Huawei because of encryption policy or credential storage.
alexpurcaru said:
This option is locked in kernel by Huawei because of encryption policy or credential storage.
Click to expand...
Click to collapse
What does that mean? And is there a way to bypass that?
Hamstern said:
What does that mean? And is there a way to bypass that?
Click to expand...
Click to collapse
It mean, that Huawei try to mentain the security of device. Maybe if you root the phone you can get full acces. You saw if you reset the phone, at start up it's required to insert the pin code. I will analyse this situation.
i have the same problem, the only way to disable the lockscreen code is by skipping it during first setup after resetting the phone
It's possible with a little workaround. Change screenlock to pattern and make a recovery pin -> Turn screen off and on -> Input wrong pattern 5 times -> Wait for the 60 second countdown and press use pin in bottom right corner -> Use your recovery pin to unlock phone and then press home button. That's it.
I contacted Huawei customer service. They told me if I have used encryption before even if you removed it the only way to turn swipe to unlock lockscreen again is to backup your data and factory reset.
hey guys whenever i restart the phone it asks for pin or the password i setup and than only it will start the phone, why
is this normal, how to fix this
That's normal.... You'll always have to provide password or pin for the first time after phone reboots. Unless you select none for your lockscreen unlock method
My phone in the beginning asked every time I restarted but now it doesn't ask for anything. Is something wrong?
z1_nile said:
My phone in the beginning asked every time I restarted but now it doesn't ask for anything. Is something wrong?
Click to expand...
Click to collapse
There's two levels of lock. One is the lock before android starts and second one after boot is finished.
If your phone isn't asking for an unlock password/pin it's possible you may have disabled it. You can enable the lock before device starts by going through the same process as normal but checking Yes when it asks the question. See my attached image for how the screen looks. If you select No you can apply a regular after boot lock.
asn0304 said:
There's two levels of lock. One is the lock before android starts and second one after boot is finished.
If your phone isn't asking for an unlock password/pin it's possible you may have disabled it. You can enable the lock before device starts by going through the same process as normal but checking Yes when it asks the question. See my attached image for how the screen looks. If you select No you can apply a regular after boot lock.
Click to expand...
Click to collapse
Figured it out just after posting. But thanks a lot for helping.
Change secure start up settings
Is there a way to change secure start up settings aside from reset factory settings? Thanks in advance
[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -
I experienced the mishap of locking back the bootloader after flashing the device with my signed custom build. The result was that i was no long able to activate the "OEM unlock" in the "Developer options".
The fact is that If you Signe your build you will not be able to rollback to stock build with ADB update / ADB Sideload / SDRAM zip ... because your Bootloader check the signature.
The only way to do it is to flash the OTA or google Factory Build by Fastboot and for that you need your Bootloader to be unlocked.
Here's in red what i did wrong :
- Activate the "OEM Unlock" in Developer options.
- Unlocked the bootloader with Fastboot
- Flash my signed ROM
- At this time the "OEM Unlock" will turn Gray and we can no more use it to activate or desactivate.
- To test some security functions, i did re-lock my bootloader with fastboot. (Forgot that the OEM unlock is disabled).
Here's what i tryed in order to solve :
I did the steps discribed in [How-to] Unlock bootloader on Verizon Pixel/XL by burduli.
That did not solve my issue but it gives me an idea where to look for. Big Thanks to @burduli (Cedit to @Qu3ntin0 and @LeoTheRomRasta)
Here's the steps i did to solve :
No need to be on internet or so on
I did notice on the Device that there was a Guest User account but i had no way to remove it.
To do so i managed to :
1 - Wipe (factory reset) : Setting / System / Advanced / Reset options / Erase all data (Factory reset) => (Find the entry according to your Built / Android version)
2- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volum down button until the device finish booting.
3- Go to setting / System / Advanced / Multiple users
4- tap on Guest, then on "Menu" the [...] on top right of the window
5- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
6- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
7- Your Device will reboot and at this time hold pressed the volum down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
8- Enable Developer mode (tap 7 times on Build number under "About phone")
9 - Goto Developer options and you are done (The OEM unlock option is back and you can enable or disable it)
You can now reboot your device in normal mode .
In Booltloader mode you can use the "Fastboot flash unlock" or Fastboot OEM unlok command to unlock the bootloader
Will this work on Verizon Android 10 ? Thanx
BelligerentGnome said:
Worked for me.
Click to expand...
Click to collapse
Really ? It worked for u on a Verizon locked bootloader ???
Do you think will work on 2xl verizon?
I just tried it out. Android 10, October update. It didn't work. There's nothing we can do at this point, I'm afraid.
BelligerentGnome said:
It did. I just got one off of Swappa, and the OEM Unlock option was greyed out. This fixed it. I'm running Lineage OS 16 now.
Click to expand...
Click to collapse
You didn't happen to take any screens during the process did you? No offense meant, but it's kind of strange that other than the OP, there's no one else confirming their success. Was it Android 10 with the October update?
Confirmed for myself, does not work. I have only taken the Android 10 update, no other updates since. OEM unlocking still disabled.
Oh verizon, still no one else to hummer this? I will donate who can sure to unlock oem method, hahaha
Going into safe mode there's no way for me to delete the guest user...was hoping it'd work for me - Pixel3/Verizon/Android 10
after doing this (unsuccessfully) my sim card is not being recognized?
This happen to anyone else?
jb
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Verizon Pixel 1 - unable to get it working still. as a note, when holding down the power down button during the 'erasing data' phase, the phone goes into Android Recovery Mode (shows me the BL, Baseband, Product/Variant, SN, CPO, UFS, DRAM, Boot-slot, Console (DISABLED), Secure Boot (PRODUCTION), Device is (LOCKED)). From here I can enter recovery mode, see barcodes, Power off, or Start.
I tried the following steps:
. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
. Eject sim card from your device.
. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock.
- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volume down button until the device finish booting.
. Go to Developer Options and enable USB debugging.
. Connect your phone to PC.
. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
- Go to setting / System / Advanced / Multiple users
- tap on Guest, then on "Menu" the [...] on top right of the window
- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
- Your Device will reboot and at this time hold pressed the volume down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
- Enable Developer mode (tap 7 times on Build number under "About phone")
- At this step i went to OEM Unlock and saw it was still disabled.
Is this something we can look at solving through the legal system?
I also was unable to get this to work
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
jedpublic said:
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
Click to expand...
Click to collapse
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
tronoftroy said:
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
Click to expand...
Click to collapse
Yes I did do the 2nd factory reset, which may be significant based on other people's reports...
If I recall correctly, the second time I factory reset, I held Volume Down from the moment I confirmed the restart. Honestly, I was trying so many different things though, so everything kind of blurred together.
One thing to point out is that my Really Blue Pixel was obtained from Google directly, not Verizon.
I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?
For those in previous versions, I can only think of using zero-day exploit with an app such as Qu1ckR00t. But we would need a dev or something to tailor such app for our Pixel. Any other idea is welcome!
I gave up and sold my Pixel 1 XL - thinking of getting a used Pixel 2 instead. I just need this as my backup phone and for travelling. My primary is the Pixel 4 XL.
dfx12345 said:
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Click to expand...
Click to collapse
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Taswim said:
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Click to expand...
Click to collapse
My understanding is that you're out of luck with a Verizon Pixel. Mine was a non-Verizon Pixel.
Hi everyone,
I don't know if this is a Tab A question, a Samsung question, an Android question, or a Marshmallow question.
I have an older tablet (SM-P350 with stylus) that I haven't been using a lot and I have forgotten the unlock pattern I was using. I am able to log in using the backup PIN, which I do remember, but I have to make several failed attempts to draw the pattern before I am prompted to enter the PIN. I'd like to start using the tablet more, but I don't want to have to do this every time.
I went to the security settings to change my login, but under "Screen lock type," it prompts me for my pattern, and after a failed attempt, it tells me I have to wait 45 minutes to try again! I am not given the option of entering the PIN. So I can't change the pattern OR change the screen lock type without knowing the old pattern! Does anyone know how I can use the backup PIN to do this?
As a last resort, I decided to do a factory reset. When I tried to do so from the menu, it prompted me for the security pattern!
I've tried twice to use the power and volume down buttons to reset, but I don't seem to be able to get to the recovery menu.
Now I can't log in to shut down and try again, because it's telling me I have to wait an hour!
And finally, one additional complicating factory is this: the tablet has been rooted -- not by me, but by the previous owner.
What can I do?