Develop Bugs

Is It Possible To Avoid (Red) "Your Device Is Corrupt..." Message Using CM13?

Is It Possible To Avoid (Red) "Your Device Is Corrupt..." Message Using CM13?
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary

http://forum.xda-developers.com/nexus-5x/themes-apps/bootloader-theme-material-bootloader-t3298420

I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
- Gary

garybiscuit said:
I appreciate that... but replacing the warning\error screen with a legitimate-looking one is just sort of masking the issue. Can the core problem of the phone needing to display "Your device is corrupt..." be corrected?
Click to expand...
Click to collapse
If you turn off dm-verity integrity checking in the kernel image you won't get the red corrupt message, but you'll instead get the yellow "can't check for corruption" message. That can be masked as noted earlier, but you can't stop the actual 4 second pause or the fact that it is happening without modifying the bootloader. I don't recall anybody working on that. It is likely bootloader is signed, in which case you might need to delve deeper into the phones boot process, probably the qualcomm modules.

I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own. I'm not really interested in taking it to that level. I'd just have assumed that the CM13 developers would have already solved this particular problem if they're considering their ROM an official release.
But, even if the CM13 kernel could be adjusted to not do this check... wouldn't you still get the "There's an internal problem with your device. Contact your manufacturer for details." message?
In general I'm just shocked that CM13 users (on the Nexus 5X) are okay with these messages. It sort of flies in the face of elegance.
- Gary

garybiscuit said:
I just completed following the directions to install CM13 (Release) on my new Nexus 5X. It seems no matter how I slice the CM13 installation, I always receive this message during bootup...
CM13 loads fine after receiving this -- however, once I'm in CM I immediately receive the message:
"There's an internal problem with your device. Contact your manufacturer for details."
I was hoping CM13 would sit cleanly on the device without messages like this. Is there a way these messages can go away?
To be clear, the steps I followed were...
1) Opened the box, started the Nexus 5X, enabled to USB \ ADB modes to let me do things , then...
2) Did: adb reboot bootloader
3) Did: fastboot flashing unlock
4) Grabbed the Nexus Factory Image MTC19V (Android 6.0.1) from here. Put this on the device (flash-all.bat) to make sure I'm starting with the OS that the Cyanogenmod documentation references.
5) Rebooted, back into the bootloader.
6) Installed TWRP Recovery (3.0.2-0) onto the device.
7) Went into TWRP.
8) Did an adb push to get CM13 (Release) and Open GApps (ARM64, Android 6.0, nano) onto the device.
9) Did the standard Wipe \ Factory Reset from TWRP.
10) Installed CM13 (Release) + Open GApps back-to-back.
11) Rebooted, then got the above (Red) message-of-death.
I understand this message can be ignored, but it just seems crappy that I'd have to endure it every time (along with the nagging CM13 message) the device boots up.
Any ideas?
Thanks,
Gary
Click to expand...
Click to collapse
Flash attached zip.
View attachment Bootloader_fix.zip

garybiscuit said:
I'm not an Android developer, just a (technical) Android enthusiast. I assume to set the dm-verity integrity checking I'd have to recompile the CM13 source code on my own.
Click to expand...
Click to collapse
Either flash one of the existing custom kernel/boot images with dm-verity disabled for you or flash SuperSU which will do it on the fly.
It doesn't mean recompiling entire CM13 source. The dm-verity check is an option enabled in the mount tables. Disabling involved unpacking the boot.img into kernel and mini filesystem, editing the mount table to remove the option, then repacking the kernel and mini filesystem. People have already done this for you or you can install SuperSU and it will do it for you.
Keep in mind, this won't get rid of the message or the pause, it'll just change the message from RED corrupt to YELLOW can't check for corruption.
If you don't like either message, best you can do is mask it.
The 4 second pause though will still be there as that would probably require the bootloader itself be modified rather than just the appended images.

glehel said:
Flash attached zip.
View attachment 3809902
Click to expand...
Click to collapse
Thanks here... but what is this .zip and how do I flash it?
- Gary

garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
- Gary
Click to expand...
Click to collapse
Boot Twrp recovery

garybiscuit said:
Thanks here... but what is this .zip and how do I flash it?
Click to expand...
Click to collapse
It appears to be replacing the RED corrupt image with something more legitimate looking, which, when suggested earlier, is what you didn't want to do.

Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.

garybiscuit said:
Yeah... that's just kind of a cludgy workaround in my opinion. Though I appreciate the effort there.
Click to expand...
Click to collapse
What did you expect? you open the bootloader, you use a non-factory system. might even with encryption turned off.
A google so declare his displeasure.
https://support.google.com/nexus/answer/6185381?p=verified_boot

I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.

I had a similar message after an update and found that I forgot to flash vendor.img. I don't use CM, but perhaps you need to fastboot flash vendor vendor.img. If you were only getting the message during the initial boot, before the android logo animation, that would be different, but since you're getting it inside android after the phone boots, this could be the culprit.
dd

garybiscuit said:
I feel like an alternate ROM with the reputation of Cyanogenmod should have the annoyances that subtract from it's seamlessness worked out. That's what I expect.
Click to expand...
Click to collapse
In this "trusted boot" world, CM will probably need to start signing their ROMs, building merkel-trees, and getting their keys distributed with the phone, but I imagine this might be difficult for them to do given the open nature of their builds and the lack of trust.

Honor 7X with installed TWRP bricked by OTA update ... any help?

Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:

ZB2016 said:
Hi,
the first time after years of installation of custom roms ... seems it happens to everyone once a while. What happened? I installed TWRP and Magisk with a bit of trouble but finally it worked well. Put the box aside to finalize installation a day later. During the night an OTA update came in together with a Magisk v15 update. So in the morning not really fresh in my head I looked on the display, thought it was my son's 7X (which is untouced on stock rom) and accepted installation and reboot ... BAMMM ... only the line "Your device is booting now ..." gets added to the unlock message screen, that's it. TWRP can still be reached, it is the only mean of shutting the box down, since holding down the power button until shutdown gets it back to the boot screen.
AH ... just for completeness: It is a BND-L21 ... or at least it has been one.
Update: After another night just laid down and switched off even TWRP is gone, now the EMUI recovery gets booted. No way to shut down the device besides let it drain the battery. I have no idea what this piece of crap will do after next reboot.
Already checked: There is currently no way to download the stock rom. And also the EMUI recovery can't locate a downloadable package on the servers.
Second Update: I still can reach TWRP by pressing all 3 buttons together during boot. By this I can get to bootloader and it gets recognized by fastboot on connected PC. But the EMUI resore kicked in again and now TWRP is again on just Vol+ together with PWR. TWRP is not able to save the settings (e.g. TZ). Is there a corrupted file system responsible for some of the issues? Power off initited by TWRP can only be reached if no charging USB cable is connected.
Any help or any idea? Tnx in advance. :good:
Click to expand...
Click to collapse
Restoring the backup is the only solution it seems.

Yes ... hmmm ... backup ... that was what I intended to do that morning when the BAMMMM happened. I really had a bad start with the 7X ...
So in case someone has a backup of a clean or nearly clean system partition, please send me a PN. Tnx in advance!

Normal make a Backup in Twrp before modify the System Partition.
Make not an Official Ota Update with Rooted and Twrp installed Rom

Its not the phones mistake that you mess up and wakeup and take the phone for a spin in half sleep
and bamm, i really dont know what that meant. i would say go to the honor care center and get it to them to work.
the procedure which i know of is tough and things like bamm happening might worsen things like TWRP not starting at all.
i have seen people bricking their phones but its never the phones fault.
i would never recommend doing a "BAMM" thing doing and flashing all the stuff randomly cz i dont think magisk is supported fully yet to our phone and you flashed it without asking anyone.
the other russian forums are flashing chinese stock firmware which is the only original firmware available, but the task to change the settings to work for other variant is a huge stock which i gave link to a few people but for you i wont recommend that cz obviously your situation is totally different so go to the honor center and explain them and they would help you.
good luck! next time verify and be careful before flashing anything at random cause its not the phones fault.

Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.

ZB2016 said:
Thanks for help, guys. Really ... even though it helped me not a single bit.
My activity has obviously not been on purpose. 2 phones, both looking exactly the same and they are without any apps so far. Since TWRP installation did not went smooth I will not tweak my son's device, therefore even if I have a second device more or less available, I will not touch it to get a system backup. And yes, TWRP backup should be the first thing to do but I have not had the time at that moment. So ... it is the way it is. Magisk is been described as a recommendation at another site, therefore I put it in also for the root hide functionality (my son loves Pokemon go, which will not run on rooted phones), because I wanted to try it first on my phone. Bad luck I would say.
And yes, I'm quite clear about the fact, that the computer just does what you tell it to do ... if you ruin the areas where the OS is located, then it is your own fault and not the device's. Nevertheless it freaks me a bit.
I am really looking forward for a nice AOSP or LineageOS version for the 7X. Oreo or Nougat, I'm fine with any of those. But I would expect, that this will take some time.
Click to expand...
Click to collapse
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release

sid21 said:
I have sent you the pm for a procedure i know of been tested by members of the other forums but since their language is russian i was skeptical and i asked a few devs to test it but none have tried it yet.. Im sending u the link and use google translate but obv.. No one from xda can help you if its from another forum.. Test if you want to at your own risk.. Good luck.. Or wait for a release
Click to expand...
Click to collapse
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!

ZB2016 said:
Thanks a lot, you made my day. Iwill at least try to investigate the content of the articles. If the translation leads to confusing sections, I will hand over the phone to the care center as you suggested earlier. Again ... YOU REALLY MADE MY DAY!
Click to expand...
Click to collapse
I am in contact with the user who posted the article and tested it himself and requested a proper one in english language but he is busy so it hasnt proceeded.. But soon he ll be free to write one up for me so i will post it on XDA..

I'm in a very similar boat. The Magisk v15 update bricked my L24. I had another one available and have made back ups through twrp to restore on the bricked one. It actually boots, but all I get is a black screen with the menu, home, and back buttons now. Holding power gives me the options to restart and power off. Hope they release the stock rom soon, or custom roms be available soon.

root your son's 7x, make a boot and system backup and restore that in your phone.
reboot

Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread

Sudeep Duhoon said:
root your son's 7x, make a boot and system backup and restore that in your phone.
reboot
Click to expand...
Click to collapse
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Back to life ... at least about 80%. Rooting leads to corrupt system partition (unable to boot afterwards) and bootloader can only be reached while a USB cable is connected (unusual behaviour). Nevertheless ... got it running. SID ... you are my hero of the day. Will PM you regarding comments for your thread.

ZB2016 said:
As long as the 7X behaves unusual compared to other phones that I know (entered Android's world with Gingerbred), I will not customize my son's device.
Click to expand...
Click to collapse
i think i have to write a guide now. this was the first but more can come soon enough. may be today i'll write a guide to backup your phone (all 48 partitions) and then root so you always have all the necessary files to restore it back to life.

sid21 said:
Kindly refer to my thread for the procedure in order to unbrick or flash the stock firmware : Link to the thread
Click to expand...
Click to collapse
Plz give link of custom rom for honor 7x

dhananjay 007 said:
Plz give link of custom rom for honor 7x
Click to expand...
Click to collapse
Who made custom rom for the phone?

sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
sid21 said:
Who made custom rom for the phone?
Click to expand...
Click to collapse
I have honor 7x.

dhananjay 007 said:
I don't know
---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------
I have honor 7x.
Click to expand...
Click to collapse
So why are you even asking me for a custom rom?
If you know no one has made yet

UPDATE ... got it back to life, at least partly. The only thing is, that constantly the android adaptions of Huawei is making it unnecessary complex or is stopping progress at all. This is the log of my actual tasks. Key to progress was the unlocking of the system fs, which has some inconsistencies in the file system. In general, it gives me a 7X, that boots and I can install apps via HiSuite. Nevertheless I have no idea how to deal with Gapps. If I install opengapps, I will not be able to register an account - just hangs for a long period and then comes back (are there any logs written on the device to analyze a bit deeper?). Gapps without an account maks no sense. So I tried it without opengapps but with installing play services via HiSuite, granting rights, rebooting twice, installing Playstore, granting rights, rebooting twice, but starting Playstore after this procedure just tells me, that gms has to be installed (which in fact is already).
Any hint?
- prep like described by SID21 including HiSuite-Installation
- optional: download Nova Launcher, Firefox and Total Commander from "apkmirror.com"
- boot into TWRP
- mount system r/w
- format data
- wipe all partitions besides external SD
- mount vendor
- install image VENDOR.IMG
- reboot to bootloader​- USB-connect to PC
- kill HiSuite in case it comes up
- Start MultiTools
- Click on "Unbrick" in upper list
- enter Path to prepared folder in grey field
- Validate: at least 4 checked boxes
- Click on Box labeled "Unbrick"
- Validate messages: "Completed", "All images are flashed successfully"
- Click "Recovery" in upper list
- in frame labeled "Flash custom Recovery/eRecovery":
- Click Button labelde "Select image" and navigate to file twrp_Honor_7x.img and select
- Click button "Flash Recovery"
- in Popup window select "Restart from fastboot" and unplug the phone from USB​- Stop Multitools
- Wait for first restart, phone comes up
- Adapt phone settings:
- Security & Privacy/Additional Settings:
- set "Unknown sources"
- set "Allow HiSuite to use HDB"​ - About phone:
- Click 7 times in a row on "Build number" to activate developer options​ - Developer options:
- Activate "USB debugging"
- optional: Activate "Allow ADB debugging in charge only mode"​ - WiFi:
- connect to your WiFi network​- USB-connect phone
- Phone popup: set "Allow access to device data?" to "Yes, allow access"
- Phone popup: set "Allow connection in HDB mode?" to "Yes, allow access"
- Phone popup: set "Allow USB debugging?" to "Ok"
- PC HiSuite Popup to inform about installation of services to manage device
- optional: PC HiSuite Apps:
- Install a proper Launcher (e.g. Nova Launcher) and make it the default launcher
- Install a proper file manager (e.g. Total Commander)
- install a browser (e.g. firefox)
- Download opengapps from opengapps.org and save to sd card​- USB-disconnect phone
- Restart phone into TWRP
- do not get access to system partition
- Mount: Validate: system is not mounted at all
- Advanced/Terminal:
- enter "ls -l /dev/block/platform/hi_mci.0/by-name/system"
- validate: the filesystem points to /dev/block/mmcblk0p44
- ONLY DO THE FOLLOWING IF YOU KNOW WHAT YOU ARE DOING!!!
- enter "resize2fs /dev/block/mmcblk0p44"
- Validate Message: The Filesystem is now 1200128 blocks long.
- enter "e2fsck /dev/block/mmcblk0p44"
- Validate message: system clean, ...​ - Mount:
- check "system"
- uncheck "Mount system partition read-only" and swype in next screen to get access to system
- check "system"​ - Install:
- Select storage: Micro SDCard
- install SuperSU (I've chosen 2.82)
- Wipe Cache/Dalvik​ - Reboot:
- reboot to system
- do not install TWRP app​- Reboot takes long time
- During boot animation another reboot occurs
- Boot animations gets finalized, phones comes up normally

[ROM][All Quark][10.x]LineageOS

ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open GApps :
Open Gapps Click Here
Choose Platform: ARM, Android: 10.0, and a Variant the one that have all you need, I recommend the nano pack but it may not have all you need so check before download.
TWRP For Quark:
TWRP Use laste Mod version that I release Click Here
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 10 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
Can't swipe/draw the pattern in lock screen : Screen lock pattern is set with the extra option of patterns "Directly show pattern view" and ambient display enable all at the same time, will bug ambient display for the wave or pick featuring of gestures, this doesn't bug when you received a notification, disable one or the other until the bug is fixed.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][10.x]LineageOS ROM for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community the quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 17.x
Version Information
Status: Stable
Created 2020-24-01
Last Updated Check Changelog click here

Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up

duplicated

Really nice! Getting a battery replacement for my Droid so that it can work as a backup phone. Tysm for Android 10!

Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk

Einsteindks said:
Won't stay on long enough to do hardly anything. Reboots into recovery on its own, thankfully. What am I missing?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
Inform what you are doing

The ROM is much much smoother than pie ROMs...Thank you so much bro ......Android 10 on this 6 year old handset is just unbelievable....

fgl27 said:
Inform what you are doing
Click to expand...
Click to collapse
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk

Einsteindks said:
Full wipe, except internal storage, Flashing rom, gapps, onto xt1254, in twrp 3.2.3mod4, reboot. About a minute into setup, phone powers down & reboots into recovdry
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
And just the ROM? What happens

fgl27 said:
And just the ROM? What happens
Click to expand...
Click to collapse
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk

Einsteindks said:
Same thing. This ain't my first rodeo, and I'm stumped!
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.

Thanks / Flashlight issue
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!

fgl27 said:
The odd thing is what is doing the call to recovery? it doesn't just go to recovery because of a fail to boot something is calling it.
Maybe a problem on data partition don't know but is a odd behavior.
Try to log that, adb is enable but you must give permission connect the usb cable during boot try to connect "adb shell" will refuse as is missing permission, as soon as the device finishes boot do again "adb shell" give the permission, next boot after the bootanimation start, you will be able to "adb shell" but before enable ROOT for adb "adb root" then after connect "adb shell" open two windows one do a "logcat" another "dmesg -w"
share the log information.
Click to expand...
Click to collapse
Yoiks! Not quite that tech savy. Even tried after a full wipe & zip-by-zip install. If I have to be happy with RR Pie, so be it. Not all that bad. My Turbo has some miles on it, rebuilt twice already. Got one last battery & display in the wings. Best, last phone Motorola made. Don't waste your time, further, on what's likely a hardware flaw.
Sent from my LM-V405 using Tapatalk

I think your not using latest twrp

newbe1droidx said:
I think your not using latest twrp
Click to expand...
Click to collapse
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk

Kinzhal said:
Thank you for your invaluable contributions. Keep up the good work!
So far, the ROM has been working fine except for two bugs: the flashlight function is not working (I took a photo with flash so the leds on the device are OK), and the home/launcher app (Trebuchet) keeps crashing.
Kind regards!
Click to expand...
Click to collapse
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
Einsteindks said:
Looks like I wasn't. I thought 3.2.3mod4 was the last best available.
Update: Um, yeah, still no luck. Used 331m1. My Turbo has a weird glitch, apparently. [emoji34]
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?

fgl27 said:
Trebuchet doesn't crash for me try to share a log.
On next build flashlight is OK
twrp doesn't affect this I tested And 10 on it before making 331 was all fine...
does the custom kernel I share works for you on Pie?
Click to expand...
Click to collapse
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk

Einsteindks said:
Overall answer; I don't know. I've stopped trying for now. It doesn't stay on long enough to access the logs. There's a pop up saying a certain file has stopped working. I'll look into that this weekend and post that information. I can only think that it's something to do with my phone's Hardware, one small minor flaw is screwing the whole thing up.
Update: well, I had a little time to kill. I reinstalled just the ROM only. 'com.android.phone keeps stopping' Would not having a SIM card installed be related to this error?
Sent from my LM-V405 using Tapatalk
Click to expand...
Click to collapse
noting crashing to me, sim or no sim.

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 17.1 source and Quark Changelog (Click Here)

[ROM][STAG OS 11][RAV*/SOFIA*][UNOFFICIAL][NO GAPPS]

�
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1) You need have a custom recovery installed (TWRP recommended)​
Hey another day another rom, that's what you might be thinking. but we at stag (I'll try not to use big words, because the idea is to be simple) aim at something towards elegance. We are learners just like everyone out there, This is small something we have started which helps us learn every single day. Why Stag, you might question, my answer would be why not. After all Harry's patronus was a stag(pun intended). Anyway, so the aim here is to provide a really good experience to everyone who uses, everyone on telegram channel can contact us and request, everything will be considered, because if you as users feel something missing, it obviously must be missing. So looking forward for people using our StagOS and giving us all your precious feedback.
~Sic Parvis Magna~
PS: for people wondering what sic parvis magna is, it translates to great endings from small beginnings, Something i picked up while playing a game.
Credits where they are Due
Google(No explanation needed n this regards)
Lineage(For starting of the custom rom war)
KCUF Rom(For acting as base)
Omni Rom, Slim Rom, DirtyUnicorns, AospExtended and every other project whose contributions lead to many of the features present.
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
1. StatusBar
Traffic Indicators
Battery Icon
Clock Settings
Carrier Label
Old Mobile Type Icons
Brightness Control
4G - LTE Toggle
Volit Icon Toggle
2. Quick Settings
Header Images
QS panel Opacity
QS Tile Animations
Brightness Slider Position
Auto Brightness Icon Toggle
Status Bar Header Clock
QS Rows And Columns Customisation
3. Volume Keys
Volume Keys Cursor
Playback Control
Volume Rocker Wake
4. Animations
System Animations
Listview Animations
Screen Off Animations
Power Menu Animations
QS tiles Animations
5. Navigation Bar
Full Screen Gesture Mode
Invert Layout
Pulse
6. Gestures
AOSP Gestures
Prevent Ringing
DT2S On Lockscreen Ans Statusbar
Three Finger Screenshot
7. Lock Screen
Lock Screen Clock Styles
Music Visualiser
Charging info
8. Power Menu
Advanced Restart
Screenshot
Settings
9. Styles And Wallpapers
Lockscreen Clock Faces
Styles (Icon Shapes And All)
10. Notifications
Notification Light
Battery Charging Light
Heads Up Notifications toggle
Edge Lighting
11. Display
Ambient Display
Night Light
Icon Shapes
Color Bucket
RGB Accent Picker
Gradient Accents
Font Manager
12. System
RGB Accent Picker
Dashboard Icons
-Gaming Mode
ROM -Fastbootd Images
ROM -Twrp Flashable zip
For installing roms you have two forms
1- via twrp flashable zip
2- via fastbootd
for twrp install make sure you have both your a and b slot filled , then :
1- copy the zip of the rom and the gapps to a sd card
2-format data
3-flash the zom rip
4-reboot recovery so the slot where the rom as installed changes
5-flash gapps or micro g or whatever you uses
6-reboot to system and set up
7-flash magisk and whatever other things u like
2-via fastbootd :
1-copy all imgs extracted from the fastbootd zip in your platfoorm tools folder
2- format data of your device
3- put the device on fastbootd mode : if using stock recovery put phone in bootloader mode connect to pc and then open adb and then write fastboot reboot fastboot
4- if using twrp , go to reboot menu and reboot to fastboot
5- flash images : fastboot flash boot boot.img fastboot flash vbmeta vbmeta.img fastboot flash system system.img fastboot flash product product.img
6-reboot to twrp or boot and install gapps , micro g or whatever you use
7- reboot to system and setup
8- reboot to recovery and install magisk or whatever u want
Whatever Features you find in first build there's no guarantee that they will carry on to the subsequent builds.
As 69+ features help only to boast, and this ROM over here is not only meant for that. We want you to boast but not by the features, We want you to fall in love with the touch. So here I'll be adding up the features that i intend on adding/removing. we are starting of with many features just to find out what you like/what you don't.
There's a huge list here
Very firstly there're two people who i'd like to extend my big thanks
@darshan1205 The person who taught me everything i needed to start and @hridaySharma who always helped.
nextly @the_Darkbeast who helped me through all the rom and device related stuff.
@shekawat2 for letting us reference on his rom, which helped in making a great base for stag
Then there are the precious testers without whom many things would still be broken, These change from device to device and will properly be given credits.
In garlic Pritish Joshi, Saqid, Sandeep and myself tested the rom thoroughly to rid it of all the major bugs.
Finally Me and @phenom87 We work on the source
we also have vinothraja and Abhimanyu shekhawat, who always guide us in times of issues a big thanks to them
the wallpaper and bootanimation yu experience all thanks to pritish joshi
and the last member in group Rakesh rakhi samuel, who takes care of coding things and web management
also thanks to :
@bcrichster
@Beetle84
@asineth
@Rondeau79
@gearsofwar567
@kjjjnob
Special thanks:
@vache
ROM
Kernel
Device Tree

reserved

pd : if you have troubles with the screen recorder easy fix , use the one plus recorder that the rom also features

Well Done, Thanks

Hi, I am about to give your rom a try after having had some issues with a few others, among other things. I'll let you know how it turns out, do you have a chatroom I can drop into later?

zxiion said:
Hi, I am about to give your rom a try after having had some issues with a few others, among other things. I'll let you know how it turns out, do you have a chatroom I can drop into later?
Click to expand...
Click to collapse
yes the oficial telegram group

thanks

Can't seem to flash with either method... Twrp errors out with error 28, and fastbootd fails on flashing system.IMG with "unable to resize partition".

FYI, I figured this out...at least on my device from newest stock, I have to flash product.img BEFORE system.img or it will fail. Perhaps someone can confirm.
StagOS looks great, BTW. Nice work!

Tried the rom which went well. Thanks for giving the community another choice!
I absolutely love your implementation of network speed. Its actually useful again for those of us with numerous eye problems or are getting older

I'm getting a lot of "operation not permitted" while trying to flash with TWRP. If I try to do I on the fastboot it refuses to flash vbmeta (anti-downgrade), system, and product (both "Command failed" "FAILED (remote: '')".
What should I do?

qmjNiYmRdvLSWo said:
I'm getting a lot of "operation not permitted" while trying to flash with TWRP. If I try to do I on the fastboot it refuses to flash vbmeta (anti-downgrade), system, and product (both "Command failed" "FAILED (remote: '')".
What should I do?
Click to expand...
Click to collapse
Are you using the newest version of TWRP? If so, then re-flash back to stock recovery and try the fastbootd option

ShadowWeasel said:
Are you using the newest version of TWRP? If so, then re-flash back to stock recovery and try the fastbootd option
Click to expand...
Click to collapse
The one here (https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/) is the last one, right?
The model the device reports to be (XT2043-7) is indeed the 2020 one and not the 2021 one.
As I've said in my previous post, I've tried the fastboot option and it doesn't work. I've even tried the "trick" used by mightysween to no success. Should I try to run sudo chmod -R 777 / (at least the vast majority of "operation not permitted" errors are when trying to access folders)?

qmjNiYmRdvLSWo said:
The one here (https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-0.4155041/) is the last one, right?
The model the device reports to be (XT2043-7) is indeed the 2020 one and not the 2021 one.
As I've said in my previous post, I've tried the fastboot option and it doesn't work. I've even tried the "trick" used by mightysween to no success. Should I try to run sudo chmod -R 777 / (at least the vast majority of "operation not permitted" errors are when trying to access folders)?
Click to expand...
Click to collapse
I'd say give it a shot. If it fails, attempt an adb sideload. That would be my last ditch effort.

ShadowWeasel said:
I'd say give it a shot. If it fails, attempt an adb sideload. That would be my last ditch effort.
Click to expand...
Click to collapse
Tried both. I haven't got any error, but the end result is the same: stuck at boot animation.
Maybe I should wait a few months to see if there's any development.

qmjNiYmRdvLSWo said:
Tried both. I haven't got any error, but the end result is the same: stuck at boot animation.
Maybe I should wait a few months to see if there's any development.
Click to expand...
Click to collapse
It took about 3-5 minutes for mine to get out of the boot animation and actually start. Perhaps we can compare and see what happens?

ShadowWeasel said:
It took about 3-5 minutes for mine to get out of the boot animation and actually start. Perhaps we can compare and see what happens?
Click to expand...
Click to collapse
I've left it running for sever hours, and what happened is simply nothing. If that's not stuck I don't know what is.

qmjNiYmRdvLSWo said:
I've left it running for sever hours, and what happened is simply nothing. If that's not stuck I don't know what is.
Click to expand...
Click to collapse
This is quite interesting here.
Let's try it by this steps.
1. Download the moto flash tool and flash the latest rom by your carrier. Run the stock rom once, don't put in your info into google for it will be a waste of time.
2. Go to the bootloader and flash TWRP to slots a and b
3. In TWRP wipe the data and nothing else.
4. If you're doing fastbootd method flash in this order (boot, vbmeta, product, system). If you're doing this thru TWRP, just flash the .zip file
5. Flash gapps then reboot into system
Hopefully this works, if not please telegram the op.

ShadowWeasel said:
This is quite interesting here.
Let's try it by this steps.
1. Download the moto flash tool and flash the latest rom by your carrier. Run the stock rom once, don't put in your info into google for it will be a waste of time.
2. Go to the bootloader and flash TWRP to slots a and b
3. In TWRP wipe the data and nothing else.
4. If you're doing fastbootd method flash in this order (boot, vbmeta, product, system). If you're doing this thru TWRP, just flash the .zip file
5. Flash gapps then reboot into system
Hopefully this works, if not please telegram the op.
Click to expand...
Click to collapse
Wait, Gapss/MigroG are mandatory?
It's stuck on the boot anymation even after flashing MicroG.

qmjNiYmRdvLSWo said:
Wait, Gapss/MigroG are mandatory?
It's stuck on the boot anymation even after flashing MicroG.
Click to expand...
Click to collapse
I decided to give it a go and test things out. Unfortunately, it's not working for me anymore. I did several attempts thru TWRP and stock versions of fastbootd. I'm going to find a workaround this, hopefully we'll get through this, if not, I'll just try a different OS. Hate having to swap different OS's for that it's time consuming...

[ROM][All Quark][Android 11] LineageOS 18.1

ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open Gapps
Choose Platform: ARM, Android: 11.0, and a Variant the one that have all you need, I recommend the Nano pack, but it may not have all you need so check before download, if any problem with a diferent version try the Nano before reporting issues.
TWRP For Quark:
TWRP Use laste Mod version from xda
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 18.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 11 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][Android 11] LineageOS 18.1 for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community, quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 18.x
Version Information
Status: Stable
Created 2021-30-05
Last Updated Check Changelog click here

Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up

Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?

imcensored1 said:
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
Click to expand...
Click to collapse
I figured it out. I started playing with all the network settings, and i found one that allowed me to set the "access point". I found the access point somehow was set to "Xfinity", once i changed it to "Verizon" my data came back. I am not sure how it changed or why it changed, as it was working before I entered the no coverage zone.

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

fgl27 said:
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Click to expand...
Click to collapse
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.

It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.

SecretPotatoChip said:
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
Click to expand...
Click to collapse
Sorry I was busy didn't check xda for a while.
If those don't help the best option is to try Einsteindks from above post
On Android was added a update to the GPS libs that fixed most of the issue, that is way most don't have any issue anymore, but if you have one is probably something very odd that need a full clean to resolve.

Active display is not working. How do I turn it on?

DobrRk said:
Active display is not working. How do I turn it on?
Click to expand...
Click to collapse
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions

fgl27 said:
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
Click to expand...
Click to collapse
Thank you very much. It is a pity that it does not work as on the old motorola, with a separate processor under this option. I really liked the firmware.

Power Functions was an awesome option on Motorolas, at one point. Shame they didn't carry over. At least other options exist. Neat idea, though. Good to see the display stuff be standard, albeit under different names.

Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.

imcensored1 said:
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
Click to expand...
Click to collapse
I believed HD voice needs VoLTE something that doesn't work in custom ROM

opengapps release they version for Android 11, I updated OP with the link.
Sometimes after not using my device from a few hours it became very slow the first few minutes I try to use it, some apps freeze giving me that warning "app is freeze kill it" or something like that, I notice that a lot of service don't run as they did on old version of android regularly on background, but they sometimes run all together when you wake the device up.
Most are service from google apps and frameworks, to improve this I'm using this new battery option that show on each app info, that allows you to enable "Background restriction" see attached.
You have to manually set to restrict each individually app that you wanna to be restricted, after I did to almost all available apps, notifications are working as expected and I don't have slows down at least not from service on the background.
If anyone has some issue related try to use those options to improve.

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

Einsteindks said:
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
Click to expand...
Click to collapse
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.

SecretPotatoChip said:
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
Click to expand...
Click to collapse
Next step would be to save internal on an OTG, along with ROM & Gapps, Titanium Backup, etc, eject/remove OTG. Get into TWRP, wipe ALL, plug in OTG, reboot into TWRP, install ROM, Gapps & modem reset zips after selecting OTG as source. Double check yourself along the way, trust me! It's easy to forget a step and have to re copy files onto the OTG from computer backup.