I'm having a strange issue with carbon ROM, thought I would try here since no one else has been able to help. After a clean wipe of the phone and fresh install of any nightly, and not signing in to google at start up, I am getting bootloops when I turn off the lockscreen and adjust the navbar height. Only these two things cause the bootloops. If I turn the lockscreen on or put the navbar to default height I can boot fine. I have tested this with nothing loaded onto the phone and it still happens. If anyone has any ideas on how to fix it would be helpful. Thanks.
Related
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
mrnathanman said:
Question:will someone help me?
I will begin by saying that I have no idea where the problem exists for my individual situation, and it would be great if I could get some help.
Background:
I used to run Dead Rage 1.2.
Now I have been back and fourth between Skrilax nightlies and Bytecode's cm10.1 with little to no hiccups.
Over time I began to notice a little lag(notification drawer, swiftkey, and basic ui elements).
Problem description:
Then I decided to try some other roms to fix my issues.
When I flash Carbon rom:
- It has no lock screen by default (and I have not been able to fix this in lockscreen settings)
- The home button does not work (neither in pie controls)
- the quick settings panel button in the notification drawer does not open the quick settings( nor can I access the quick settings any other way)
- the home screen apps are strangely and slightly above the software buttons
I saw someone with similar problems in the posts of carbon but it was resolved by a single reflash.
I also tried a relatively new rom called Revolt on droidrzr:
- I experienced similar issues with the home button
- I did not delve into the issues more because the issues were similar to carbon
Explained, further:
As explained above I have flashed without issue before.
I am under the impression that the way to flash is:
1. mount system
2. wipe system
3. repeat
4. reboot recovery
5. mount system
6. flash
I have tried every variation on this set of rules I think is possible for carbon. I initially had TWRP 2.3. I have flashed without rebooting recovery, without mounting system, with a factory reset on the previous rom, wiping cache and delvik as well. If I don't wipe the system I get weird crashes and the home button still doesn't work but it fixes other things like quick settings. Sometimes when I would wipe system, and not do a factory reset, and flash carbon all my apps from the Bytecode build persisted. This made me think it was a recovery problem.
Then I flashed TWRP 2.5. I have similarly tried everything with TWRP 2.5 and get the same results. I have tried 6/21, 6/23, 7/2, 7/4 carbon on both recoveries.
I have a backup of bytecode cm10.1 and I am running that currently.
If some one would help me troubleshoot or fix my problem, I would love to get carbon. And I would be very much appreciative.
If I am in the wrong place please point me.
I did not post in the carbon topic because I do not have more than 10 posts.
I know that people are not paid to help me so I respect when they do.
Also if you need screenshots, I can reflash carbon and take some shots too.
Click to expand...
Click to collapse
see post #7 here: http://forum.xda-developers.com/showthread.php?t=2355676
this should probably be in the Q&A/Help/Troubleshooting section....
Thank You So Much!!!!!!!!!!!!!!!!!
I know its soon and I am still crossing my fingers, but thank you!
The Problem:
Updated my ROM the other night and I tried to set Pattern as my Screen Lock security and it just stayed on "Slide" I tried every other lock screen choice and none of them would stick.
Troubleshooting:
1. I cleaned flashed the latest nightly I was using and the problem persisted
2. I wiped my phone completely and reinstall stock images and flashed Carbon ROM and the problem still persists.
3. Flashed another ROM and the problem still persists.
I don't know if anyone secures their phone but to me this is an URGENT matter, if anyone has any suggestions, Im open to fix this ASAP.
SOLVED!!
N4Solomon said:
The Problem:
Updated my ROM the other night and I tried to set Pattern as my Screen Lock security and it just stayed on "Slide" I tried every other lock screen choice and none of them would stick.
Troubleshooting:
1. I cleaned flashed the latest nightly I was using and the problem persisted
2. I wiped my phone completely and reinstall stock images and flashed Carbon ROM and the problem still persists.
3. Flashed another ROM and the problem still persists.
I don't know if anyone secures their phone but to me this is an URGENT matter, if anyone has any suggestions, Im open to fix this ASAP.
Click to expand...
Click to collapse
UPDATE: I figured it out, turns out that it was the "PROFILES" option set to home with an "Unsecure" lock screen
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.
So I just updated Magisk from v11 to v12 and my phone is totally douched up. After rebooting there's an "Unable to use fingerprints" message at the bottom of the screen, the touch screen is janky and my unlock pattern no longer works. The screen goes to sleep randomly too and then comes on without being touched. On the off occasson that the unlock pattern DOES work, the screen loads with no icons, just the page dots and status bar with my wallpaper and nav buttons. Uninstalled Magisk and got the same. Rebooted after uninstall, same thing. I guess I'll be reflashing the ROM, but this is a huge pain in the ass.
Same happened to me on ls997 but i dirty flashed my rom. It fixed the issue without losing anything. Not sure witch carrier you have or witch rom.
Well VS995 and H918 seem safe to update magisk on. Ive seen multiple people have 0 issues with it. Maybe a bad download? Never had that happen while updating magisk :|
Sounds more like a system issue. Id try reflashing your rom and see if that works
hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
algebrathebard said:
hi there,
I got a new AGM phone model A1Q some weeks ago, and I am manage to install LOS (unofficial) found on a China website, because the phone go wrong after trying to install Gapps, making none apps work.
After several trials, LOS install to the phone with working Gapps, however I got 2 issues right now.
1. the screen never come back after screen is off, I have to reboot the phone to get it back.
2. notification bar is not updating, I am using Nova Launcher right now, I tried disabled the notification bar and reboot, nothing happen.
For the moment, I am not able to get back TWRP recovery after installing LOS, I have to figure out other way to redo the LOS installation.
Please someone throw me some suggestions.
Sorry for my bad English.
Click to expand...
Click to collapse
Update:
Notification bar issue fixed after several reboot, but screen issue still exist.