Database Users

Cant get past the initial setup wizard

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)

"Setup assistent has been closed" loop after flashing gApps

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

Whitescreen

Hello,
i got an problem with my Huawei p8 lite.
I got root installed, my device worked perfect for a long time, but yesterday i came across a problem. a couple of apps stopped working. (they started and closed a couple seconds later.)
i turned my phone on and off a couple of times but the problem stayed. I put my phone back to factory settings.
My phone turned on after that and i got the 'setup' screen. after all the settings and agreements, i got a screen with 'restore with and older android device' when i want to skip that, i got an white screen.
Its stuck on there, i can turn off my phone with holding the power button and get the menu with 'boot again' and 'shut off' Also i can use my camera, calculator, flashlight and the recorder.
i tried installing the firmware again (vol+ and vol- and power) but when i do that, i got an message saying 'installation failed'.
Does someone have an solution?
Im sorry for my bad english.
Thank you.

Flash it via fastboot mod

AmINoS007 said:
Flash it via fastboot mod
Click to expand...
Click to collapse
Thank you for your reply.
I get an error 'device not found' when i want to install.
my phone is in fasyboot & rescue under there is in red PHONE Unlocked.

merrie11 said:
Thank you for your reply.
I get an error 'device not found' when i want to install.
my phone is in fasyboot & rescue under there is in red PHONE Unlocked.
Click to expand...
Click to collapse
you should have the drivers installed , search and install adb universal drivers
Then follow this tutorial it will help you on anything you need : http://tundevs.blogspot.com/p/huawei-p8-marshmallow.html

I got my phone working again. But the google apps wont work. Youtube works but i cant login. the rest of the google apps wont work.
the 'huawei' apps are working.
any solutions?
Edit:
I cant add accounts, if i try to add a google or facebook account it will load for a second and then goes back to the previous menu.

Same problem, fixed
Hey, I had the same problem; After a factory reset the phone got stuck on emui activation with a blank screen. I factory restarted again and skipped the wifi connection and during the whole process of activation kept the SIM card off the phone. After that, Gapps acted weird but I noticed that it was because the Google Play Services app was missing. Installed this one http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-8-4-89-release/google-play-services-8-4-89-2428711-240-android-apk-download/ and all started to work fine again, with Gapps at least. I know your issues was some time ago, but I hope this could be useful for you or any other who face the same problem. Have a good one.

pelukin said:
Hey, I had the same problem; After a factory reset the phone got stuck on emui activation with a blank screen. I factory restarted again and skipped the wifi connection and during the whole process of activation kept the SIM card off the phone. After that, Gapps acted weird but I noticed that it was because the Google Play Services app was missing. Installed this one http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-8-4-89-release/google-play-services-8-4-89-2428711-240-android-apk-download/ and all started to work fine again, with Gapps at least. I know your issues was some time ago, but I hope this could be useful for you or any other who face the same problem. Have a good one.
Click to expand...
Click to collapse
Hello,
My phone still isnt working. i tried to install the google play services, but still no luck. But thanks anyway.

VNS L21 Nougat C432B336 working and not working stuff

Hello all, i am planing to describe all good and not working things about this Nougat version i found and also process i did to install it.
I would be grateful if someone can help me resolve not working things or maybe this will help developers fix them.
First, one month ago, i unlocked and rooted my phone because i wanted some additional features. TWRP was installed and worked like it should. I did not unroot phone.
Yesterday, i downloaded those 2 files needed for Nougat 336 update. I used DLOAD method.
Steps i did was:
1. Put BOTH files on SD car in dload folder.
2. Power off phone.
3. Enter TWRP via Power + Volume down button.
4. Flashed 1st (Update.zip) file and got some red line errors. (Because i read it is normal i went further).
5.Flashed 2nd file WITHOUT reboot. All was done in 1 or 2 mins, and no loading and installing screen was shown, just rebooted normally.
6. Huawei logo showed and phone start normally with nougat update (1. December security patch).
Good things i noticed while few hours of testing:
1. Better battery life
2. Twin apps working
3. App drawer working
4. System is a bit faster (apps load and work faster)
5. Less ram is used (900-1000 MB free when cleaned)
THING THAT DON'T WORK AND I NEED HELP TO GET THEM TO WORK:
1. Camera app show black screen, than shut down and restart itself. That happens all the time until i close it with square button and click on trash can. SO CAMERA NOT WORKING. I even tried some apps from app store. App works but screen is full black.
2. I have no Huawei stock apps like clock, alarm, stopwatch, calendar, calculator, file manager, not even stock sound for ringing nor message etc. They are MISSING FROM PHONE apparently.
3. Problem with sound manage. Those bars that regulate sound dont work very well. I put my Ringtone bar to MAX and i hear phone ringing and SMS sound but I dont hear app sound like Viber or Messenger sound.
4. "MOST IMPORTANT ONE": I thought maybe 2nd file did not install normally so i tried to enter TWRP again and flash it again, but I CANT ENTER TWRP!
I pressed Power+ Volume down like 10 times, I tried Power - Volume up too, even all 3 buttons, nothing happens. Just Huawei screen and phone boot up normally. When i did 3 buttons EMUI screen appeared and it said, installing updates, went to 5% and wrote: FAILED, Reboot phone.
So now i cant flash ANYTHING again. Can someone help me with this thing please. Maybe many other people will find this thread helpful.
Thank you.

Hello
I think best and remake to own.
It seems to me that the
MM recovery solution, is written at the bottom of this post. Http://forum.xda-developers.com/hua...t/android-7-emui-5-0-vns-l31-l21-l23-t3513816.
To install nougat b336, maybe you should follow the original post also that is also written down this post.

your bootloader is locked

did you face nfc and bleutooth not working in that case what may i do to fix the problem and thanks in advance

Magisk Causing Looped Lock screen?

when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?

WARKRIME said:
when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?
Click to expand...
Click to collapse
I have exactly the same problem, I installed thirdparty launcher like lawchair 2, and set it to default.
Don't know if it had something to do with this.
Now I flashed back to stock ROM.
Any one have a solution on this?

Not just your phone, I am experiencing this as well as of this moment. I have Galaxy S10, bootloader unlocked, rooted with Magisk and installed hades ROM.
After todays reboot, I cannot use my phone - on lockscreen, I draw a pattern and it just goes back to lock screen. It doesn't matter whether I boot the phone in root mode (Power + Bixby + Vol Up) or normal mode (just start with Power button).
I don't know how to fix it and I want to avoid reflashing the whole phone as I just finished setting it up from scratch.

Well... interesting thing... when this happens to you next time, try to boot into recovery (TWRP) and then back to system.
This has helped me twice now. After such reboot, I can get past the lock screen loop.
Still trying to figure out how to fix this.

zoomsk said:
Well... interesting thing... when this happens to you next time, try to boot into recovery (TWRP) and then back to system.
This has helped me twice now. After such reboot, I can get past the lock screen loop.
Still trying to figure out how to fix this.
Click to expand...
Click to collapse
When you do that, you boot in the non Rooted System. There it works for me too. But when i try booting into rooted System i have a Lockscreen loop as described of you.
btw Galaxy s10 SM-G973F

I ve been there once. In my case it was the SoundAssistant app causing this. Somehow. Luckily I had my PC authorized so I was able to use adb to uninstall the app and reboot. Then reinstall.
A little more details on this fyi, it isnt bootloop because its still in the lock screen. Just the app (with "appear on top" permissions) somehow isnt able to load properly so it keeps opening and closing.
If you happen to have SoundAssistant installed, try above. If not, you can go to safemode see if it still happens. After that you might need to take some time to figure out which app is causing.
I dont think this has anything to do with Magisk or root, at all.

alex.do said:
I ve been there once. In my case it was the SoundAssistant app causing this. Somehow. Luckily I had my PC authorized so I was able to use adb to uninstall the app and reboot. Then reinstall.
A little more details on this fyi, it isnt bootloop because its still in the lock screen. Just the app (with "appear on top" permissions) somehow isnt able to load properly so it keeps opening and closing.
If you happen to have SoundAssistant installed, try above. If not, you can go to safemode see if it still happens. After that you might need to take some time to figure out which app is causing.
I dont think this has anything to do with Magisk or root, at all.
Click to expand...
Click to collapse
I think do too. Had it solved by renaming every item with "keypass" in /vendor/lib/hw
which disabled my pin, so everything worked fine.

WARKRIME said:
when booting up to root , after a few times , it eventually gets stuck in a loop of , pin to open on restart , which just goes black , then returns to pin screen?
Anybody else had this problem or just mt phone?
Click to expand...
Click to collapse
Same problem