I wanted to install this rom but it does not start.
androidfilehost.com/?w=files&flid=191959
I noticed that in the rom zip the system folder containing the build.prop is not found. This is the cause of the problem? Can I add any system folder from another rom?
Maybe it's not 100% finished but this is REALLY good news.
Edit: Tried installing and it doesn't seem to go past the splash screen.
Yes, I hope the error is resolved.
If you like Paranoid Android, probably Dirty Unicorns (another a "few devices" rom) it's of your liking too.
I suggest you to try the Weeklies of Dirty Unicorns 'unofficial builds', by Frostbite, here.
It's absolutely stable, haven't found any bug there.
You can try with any other kernel. Some roms I'd tried like this and got success.
I actually found a ROM called CypherOS and it's got a few PA features like Pie Control, Color Engine, and Pocket Lock. I'd try it out!
Related
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
Hi,
I use BasicPlus 2 rom by t-shock (http://forum.xda-developers.com/s7-edge/development/rom-basicplus-1-t3402601).
When I reboot my device, specific apps are complety missing and I have to restore them with TB to go on.
This is reproducible with these certain apps, for example Swiftkey, Es Explorer and Google Calendar.
I had this issue before and I fixed it by deleting the 'Android' folder on my external microsd (128GB Samsung Evo Plus), since the missing apps always create an empty folder there. Now this seems not to be working anymore, therefore I'm asking for a permanent solution in this thread.
Unfortunatelly I'm not able to post in the rom's thread since my account is locked for the development section, but I hope I will get some help here.
Thanks!
Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.
iSaitama said:
Did you dirty flash?
If you did, I highly recommend clean wiping after every update to a custom ROM.
Click to expand...
Click to collapse
Yes I dirty flashed from 1.1.1 to 2.0, since this was supported by the developer and he provided a fix to have a stable rom.
I also tried a clean install, but for any reason battery life wasn't that good compared to the dirty flash from 1.1.1.
It seems that no one else has such an issue, that would mean no one else did a dirty flash from 1.1.1, otherwise there would be more reports!?
In the meanwhile I made a clean install in each case of 2.0 and 2.1, but the issue still exists. I also wiped all caches after rom install, but there is no change. All apps survive several restarts but all of a sudden some apps disappeared after restart. I will try now with 3.1 and Prometheus kernel, too bad I cannot post to the main thread of the rom, since the developer doesn't see this thread I think
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
SiqMawsh said:
Hey guys. I just recently updated to Android 7 via the resurrection ROM. I have flashed 2 different rooms and this problem still persists. I have done absolute full wipes in between and I have also tried flashing other kernels. This only started as a problem when I went from 6 to 7. Any ideas?
Click to expand...
Click to collapse
Try different GApps packages.
Gapps solution didn't work. I tried all the way back to Feb gapps packages. I can't get any 7.0 Roms to work without crashing when location is requested. I am back to 6.0 and working fine. What could the issue be? I might try to go fully back to stock then back again.
I'm also having the same problem. I've tried both Resurrection and Lineage.
OP - did you find any solution?
I was having problems with Google Play Services, related to location, and I did type this command on the terminal:
pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION
See if it works.
Sorry bad english
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
purplegreendave said:
I've tried Lineage, AOKP, AICP, AOSCP, RR; Delta Gapps, Open Gapps. This problem won't go away.
As far as I can tell there aren't any MM ROMs still being updated? At least the threads are all dead. Really at this point I'm debating going back to stock and waiting for Moto to give me something. Maybe the same bug is what's tripping them up.
Click to expand...
Click to collapse
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
smsporto said:
Did you try the command, mate? I don't know if someone did try it, and I want to know if it works, because it did work for me
Click to expand...
Click to collapse
Just got several messages telling me the action wasn't allowed, even with root
purplegreendave said:
Just got several messages telling me the action wasn't allowed, even with root
Click to expand...
Click to collapse
I tried the command it didn't work for me. The command itself went ok without errors, but it did not fix the rebooting issue. The only solution for me is to put GPS onto battery saver mode, which is not ideal.
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