Related
So, I installed this new rom: Commotio Android 6.0.1 and with it the latest open gapps for Android 6.0.
I rebooted the device and everything was fine and I got to the setup wizard, chose the language, chose the wifi, but after chosing "No thanks" when asked if I got another device, it just says that "Google play services has stopped working".
The thing is, that I can't get to recovery, or I would've flashed another gapps package. I mean I can fix it all by going to download mode and flash stock rom then go back to my custom rom. But that just takes longer and I don't have the time right now.
Edit: By experience I know this problem is caused by the Gapps package. Because I've solved it many times before by flashing other Gapps packages
Is there a way I can just bypass the setup wizard??
OK, I figured this by (accidently) rebooting into safe mode. I did this by turning the phone off, holding power, volume up and down buttons and releaasing only the power button when logo shows up. Then I continued normally with the setup wizard but it didn't ask me a couple of things, witch actually made it work!
Remove sim card and reboot without connect to WiFi and when to choose mouthed of internet connection do not choose ethir WiFi or mobile data that work on miui ROM and all lp stock ROM (normally I do not install gapps with aosp because I love to try fast experience of android)
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,
I am having a kind of weird issue with my Oneplus 5.
At first I used LineageOS but decided to switch to OmniROM because of signature spoofing. That worked but OmniROM asked my for an encryption pattern right after the first boot and didnt accept the one I had before, so I googled and deleted the locksetting files in /system ( I am not sure if this is relevant for the problem). But when I rebooted OmniROM started but then it showed a black screen but the volume control overlay is visiable when I press the volume buttons and also the shutdown overly is functioning when I press the power button and the screen flashes and shows the real screen when I press the Back Button.
I tried wiping Chache (and System and data) and tried installing LineageOS and OmniROM several times but its always the same error.
Some people seemed to have similar problems but the suggestions didnt work for me:
https://forum.xda-developers.com/oneplus-5/help/black-screen-pin-code-t3654329
https://forum.xda-developers.com/oneplus-5/help/op5-dead-t3655315 ( I did not try to install the linked zip because I have no idea what it does)
Any suggestions for me, please?
thanks in advance
Sounds like the problem is the encryption of the internal storage, I'm not a pro, but it seems like a full wipe is the only way to go.
By that I mean everything, including the internal storage, but let's wait a little till others respond.
I fixed it. I did a a reset to HydrogenOS with the official Unbrick Tool and this guide:
http://www.droidviews.com/unbrick-oneplus-5-using-the-official-unbrick-tool/
This should be linked somewhere here on xda.
My phone battery went to 0% earlier and I plugged it back in to charge.
Annoyingly, this phone tries to turn on when you plug it in and it's dead/off. So it tried to boot the phone and I got the typical boot loader unlocked warning screen.
Now I can't turn off the phone or do anything with it. Does not respond to fastboot/ADB.
Try pressing power + Volume up and down buttons simultaneously for like 10" / 15"
Yes try those two buttons, same thing happened to me. By any chance are you rooted with Magisk? I was when that happened, and from reading around I gather there might currently be a bug in Magisk that causes that. It's not really a bootloop, it just gets stuck but will boot up eventually. Although I was not at 0% battery.
YrrchSebor said:
Yes try those two buttons, same thing happened to me. By any chance are you rooted with Magisk? I was when that happened, and from reading around I gather there might currently be a bug in Magisk that causes that. It's not really a bootloop, it just gets stuck but will boot up eventually. Although I was not at 0% battery.
Click to expand...
Click to collapse
Yes it is rooted with Magisk -
The volume up button combo worked. Thanks for the info guys
What version of majisk. I am on stable 17.1 and haven't had this yet
It's a bug with the latest magisk.
geminium said:
It's a bug with the latest magisk.
Click to expand...
Click to collapse
By latest do you mean latest stable or latest beta?
cwalker0906 said:
By latest do you mean latest stable or latest beta?
Click to expand...
Click to collapse
Beta. 17.3
I had the issue on the latest stable Magisk 17.1. There was no problem for the first few days, but then it did happen
me too it happened on Magisk beta 17.3. Volume up and Power restarted it.
According to me this is completely normal and the way out of the apparent "frozen" screen is by pressing the Volume + and power button simultaneously for about 5 seconds and the phone should restart on its own
Thanks
Hi!
I've started to have problems with my home button sometimes not working. Also fingerprint sensor stops working same. This started to happen lately and it happens more every week. I've tried with many roms fully clean installed (also data formatted), with ob 28-30 and 9.0.4 firmwares. Now my fingerprint scanned doesn't work at all in crdroid. and in los it works for a few minutes. On omni and Aicp i haven't had any problems. On Oxygen roms it is fully random, sometimes work. It once happened on clean ob30 install so i fear it's a hardware based issue, but i still want to hear your opinions.
I tried unbrick tool that flashed stock 9.0.4. Fingerprint scanner and home button worked great until first reboot. After that, nothing. Tried another rom clean install, no go. Installed 9.0.4 clean from twrp. Fingerprint and home button worked, until first reboot. What is really going on?
Edit: When fp scanner and home button stops working after reboot, also self-test fails instantly in *#808#
Vika__ said:
I tried unbrick tool that flashed stock 9.0.4. Fingerprint scanner and home button worked great until first reboot. After that, nothing. Tried another rom clean install, no go. Installed 9.0.4 clean from twrp. Fingerprint and home button worked, until first reboot. What is really going on?
Edit: When fp scanner and home button stops working after reboot, also self-test fails instantly in *#808#
Click to expand...
Click to collapse
My opinion: More likely a hardware issue if self test fails.
That was my fear too, well. Have to rip few euros and buy a new fp scanner. Hopfully that one solves it
Interestingly, if i hold fingerprint scanner and press self test, it passes. After that home button and fp scanner works for a few minutes, but very slow. Have to hold button about 2 seconds to get home command