My boss rooted his LG G2-D02 and installing CM 12.1 in the process. Now, after knowing that CM 13 was already released, he downloaded a copy of it and immediately flashed it onto his phone. He got a problem with Gapps and DL-ed a problematic version which caused the notification,"Unfortunately, Setup Wizard has stopped" to pop up repeatedly. We had tried following a few advices from this website but to no avail.
1.) We already tried using Force Stop and Disable under Apps->(Show system apps)->Setup Wizard (CM). I had also tried giving it app permissions, but all app permissions were already available.
2.) The only option is to flash CM 12.1 back again but it can't be done. My boss set the default recovery app to Cyanogenmod's own recovery program, which had limited functions, so I can't
also use TWRP ATM.
3.) My boss also tried something on ADB but to no avail
4.) Factory reset didn't also solve the problems.
I'm almost running out of solutions... Perhaps, I can use a helping hand from brighter minds in this community.
TIA
I'm using cloudyg2 v3.3 because cm13 has got a lot of bug for example
-I can't proceeded to music
-systtem has stopped once a hour
-I can't close touching vibration
I can't remember now but cm13 has got really much bug (yeah my english is very bad,I know this)
Now system is stable and battery is very very good but still İ can't scretch to music
So hey.
I'm facing a really weird issue with my phone. I currently use DU and it works perfectly, however whenever I install 'Ubermallow' or 'Omni ROM' or 'chroma' or even PN for that matter they all initially work perfectly. I go ahead and install AK and xposed it's all still fine, then I randomly restart my device. It starts bootlooping. So I think maybe it's substratum going haywire I remove the overlay, and it's still looping. I end up rm-rF'ing the vendor partition and reflash that to no avail. Now I'm thinking AK kernel is messing up, but it works fine on DU. Xposed could also be it but again I've used it for so long on DU and before that on PA. So if anyone has any advice or anything drop a comment. Thank you
Well typically if you get a bootloop, something isn't playing nice with the system[obviously].
In your case: I'm using Pure Nexus + Kylo Kernel + Substratum and no random reboots / bootlooping on a controlled reboot.
Suggestions:
AK Kernel - Make a profile and then back it up, make sure it is working - no screen glitches or ui crashes, and reboot. Bad kernel settings [undervolting, etc] can cause bootlooping. Once you verified there you can boot, move onto your theme.
Regarding substratum - I would go into the vendor folder, delete the entire overlay folder, reboot, then apply your theme - making sure the themes are compatible. If you experiecing per-app issues, go back and then individually disable its over. Once it is set, backup your theme and reboot. If you experience bootlooping here then you've narrowed it down to the theme. You can delete the overlay folder from TWRP.
As always, install the ROM via clean flash for the best results.
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
alot of people have this problem with 12.0 flash the 11.0 and dont update
survivingarch said:
Hello there, I've been using the V20(H918) for a little while now and was running WETA Rom 4.8.5 with Magisk 11.0. When Magisk 12.0 released after rebooting and being on for a minute or 2 my phone would suddenly go back to the T-mo splash screen as if it were soft rebooting and then would repeat this process. I thought it might have been a download or flash issue so I tried wiping and doing a fresh install but if I ever restarted the device the same issue would appear. I've tried selecting or deselecting a majority of the options in the aroma installer for WETA but nothing seems to work. The rom seems to work fine with SuperSU installed so I'm thinking it might be something about the way my phone is set up but I haven't been able to pinpoint exactly what it is and I really would like to use Magisk for the hide feature. Based on the thread it doesn't seem like there should be any issues and I'm unable to ask my question directly in the thread. I'm not very experienced with these kinds of things so I'm sorry if I'm not being specific enough or if the solution is obvious. Thanks for anyone's help and time with this issue!
Click to expand...
Click to collapse
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
jinkerz9430 said:
Im currently running weta rom with magisk 12.0 on my h918. However there are 2 possible differences between yours and mine. 1) you are not in the latest version of weta rom 4.9.4. 2) you are probably flashing the stock kernel that comes in the weta aroma installer. Try with konvergent or another kernel other than the one from weta rom. (as soon as i flashed the weta kernel my phone was experiencing the dame thing yours did , then after i flashed konvergent back it came back to normal)
Click to expand...
Click to collapse
Did what you said and everything seems to be running smoothly, thanks very much for your help! Hoping a more updated kernel that doesn't force SuperSU and works with magisk comes out soon!
Has anyone tried to flash the Xposed Module that came out earlier today/yesterday? If you don't know what I'm talking about, watch this video real quick: https://youtu.be/eADZK17N7rk
I understand it is unofficial and might be unstable with lots of bugs, & that some modules currently don't work, but would I be at (more) risk of bricking my phone if I flashed it?
I flashed it yesterday and everything went well. The bugs are the following that I've experienced:
1. In order to download a module, you must press save instead of download. After that, a toast notification will prompt you on where to go in your file manager to find the apk.
2. Some force closes such as kernel auditor and Google/services. Those were resolved later on for me.
3. I noticed the fingerprint scanner got a little sluggish after, but a reboot fixed that.
4. Sorta made the UI a little sluggish as well so be careful if you've already under clocked your processor.
There we go. I am currently on the latest version of Lineage OS. I uninstalled it today, but I plan on installing it again with a new ROM tonight.
It doesn't seem to work on AOSP or Extended AOSP, but apparently seems to work on other ROMs. Want to switch ROMs unless EAOSP fixes that because I really want Amplify again
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
MoodlePro said:
Did you touch any configurations before that ?
Go to Display > Advanced > Front Camera Display Area and try the option 'hide the front camera' and then go back to 'show the front camera'
see if it fixes the bug.
Click to expand...
Click to collapse
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
BRANDENDEUCE said:
I only set up my phone. I had previously tried switching the front camera display area when I first noticed it was wrong, but it didn't help. Regardless of what settings I use there's always a 1mm or so black area above the status bar.
Click to expand...
Click to collapse
It looks like a launcher related problem.
Are you using a custom one of just stock? You could try clearing cache for the launcher in settings - apps and then reboot your phone.
Tell us how it goes.
You might also check your DPI settings (
https://www.reddit.com/r/OnePlus8Pro/comments/jh1x9e
)
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Using nova or oneplus launcher, it's both the same. I'll see if I can find an extra camera because screenshot doesn't show it
MoodlePro said:
Also, if you can take a picture or a screenshot (if it shows) i would highly appreciat it.
Click to expand...
Click to collapse
Hope this helps.
BRANDENDEUCE said:
Hope this helps.
Click to expand...
Click to collapse
If you're able to do so, clear the cache for both launchers
Update me as always.
MoodlePro said:
If you're able to do so, clear the cache for both launchers
Update me as always.
Click to expand...
Click to collapse
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
BRANDENDEUCE said:
Same as before. I had tried wiping the cache in twrp and it didn't help. I'm trying to get the full zip for the current rom to dirty flash. I'm assuming that will fix the problem, but I can't find anyone who's got it yet.
Click to expand...
Click to collapse
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
xtcislove said:
it looks like you are not using stock oos or at least some modifications or UI Apps. Some of these apps/mods should be your problem. You are the first on on here reporting this issue so its very likely some of the apps you are using.
I would reset my phone and test every app alone if the issue comes back. Or maybe just deactivate all of them, restart and look what happens.
Stock roms:
[OnePlus 8 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com
Just in case:
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
I'm using Oxygen OS 11.0.10.10.IN11AA that I updated right after initial setup. Bootloader unlocked and rooted, swift installer for theming. I've in uninstalled the swift mods and it stays the same. I have some magisk modules, but they were active initially before the issue arose. I did look at the thread for the OOS version, but the newest available is for the last version. As soon as I get my hands on the full zip I'll start from scratch and find out what is causing the issue.
BRANDENDEUCE said:
Just got my OP8 Pro last week and everything was fine until a few days ago. I noticed my screen size is off. It's almost as if it's shrunk. Everything from the top of the screen has dropped about 1mm, so that the camera hole is wrong and the notification bar is below where it should be. I've looked at the dpi, scaling, etc but can't for the life of me find what's changed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think after all you've tried I would just MSM back then start over.
Hopefully it's just a very weird glitch although my guess is pointing towards hardware and an alignment issue with the screen..was the device new? Or 2nd hand?
If it's the latter then I'd be having a word, obviously after the MSM wipe, you'll be required to unlock the bootloader again and re-root
It's definitely odd.
If the wipe fails then there may be a calibration tool that enables you to bump the alignment of the screen up a bit, I'm sure dpi changes should have an effect (may need a reboot between changes)
Also change from QHD to FHD, I run in FHD and everything has always scaled really well.
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
BRANDENDEUCE said:
So, the latest update was finally released and I dirty flashed it after disabling all my magisk modules and swift theming, but the issue was still there. I factory reset from twrp and it fixed the problem. All swift theming and modules (viper, Dolby digital, acca, oos call recording) are reinstalled with zero problems. The only thing that I can think of that caused it is an app I used to show battery levels around the camera hole, because everything else is the same. It had to have changed something that even after uninstalling and dirty flashing it didn't revert.
Click to expand...
Click to collapse
Nice one..