Restored “App+Data” with Titanium Backup for com.android.providers.telephony and now Messaging is crashing

I have a Moto G 4th Edition (harpia) running LineageOS 14.1 nightly. I was trying to debug some issues with its MMS and I used Titanium Backup to take a backup of the APN settings because I was about to follow some tutorials and I wanted to know I could certainly undo them if I needed to. I wasn’t able to fix the problem, so I tried to restore using Titanium Backup. When I was restoring the settings, it asked me if I wanted to restore App, Data, or App+Data. Without thinking too much about it, I clicked “App+Data”. Then, I went back to the APN settings page to see if the APN settings I had were restored. When I clicked on an APN, it crashed. I think the exception in question is:

06-27 18:44:22.454  2067  3374 E DatabaseUtils: java.lang.SecurityException: Permission Denial: reading com.android.providers.telephony.TelephonyProvider uri content://telephony/carriers/1265 from pid=4901, uid=1000 requires the provider be exported, or grantUriPermission() 06-27 18:44:22.454  2067  3374 E DatabaseUtils:     at android.content.ContentProvider.enforceReadPermissionInner(ContentProvider.java:608) 06-27 18:44:22.454  2067  3374 E DatabaseUtils:     at android.content.ContentProvider$  Transport.enforceReadPermission(ContentProvider.java:483) 06-27 18:44:22.454  2067  3374 E DatabaseUtils:     at android.content.ContentProvider$  Transport.query(ContentProvider.java:212) 06-27 18:44:22.454  2067  3374 E DatabaseUtils:     at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:112) 06-27 18:44:22.454  2067  3374 E DatabaseUtils:     at android.os.Binder.execTransact(Binder.java:565) 

(But another suspicious-looking message I see is 06-27 18:44:20.760 2067 5631 W ContextImpl: Failed to ensure /data/user_de/0/com.android.settings/databases: mkdir failed: EACCES (Permission denied).) I reached out to Titanium Track via their “Contact Us” page but haven’t gotten a response so far (it’s only been about 36 hours). In the meantime, I noticed that I also can’t even use the Messaging app on my phone. When I try to enter an SMS conversation, it crashes. I think the exception for that is:

06-27 18:43:54.101  1141  2774 W ActivityManager: Permission Denial: opening provider com.android.providers.telephony.SmsProvider from ProcessRecord{890eeb3 3530:com.android.messaging/u0a73} (pid=3530, uid=10073) that is not exported from uid 1001 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel: wtf 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel: SyncMessagesAction: unexpected failure in scan 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel: java.lang.SecurityException: Permission Denial: opening provider com.android.providers.telephony.SmsProvider from ProcessRecord{890eeb3 3530:com.android.messaging/u0a73} (pid=3530, uid=10073) that is not exported from uid 1001 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.os.Parcel.readException(Parcel.java:1684) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.os.Parcel.readException(Parcel.java:1637) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.app.ActivityManagerProxy.getContentProvider(ActivityManagerNative.java:4199) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.app.ActivityThread.acquireProvider(ActivityThread.java:5534) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.app.ContextImpl$  ApplicationContentResolver.acquireUnstableProvider(ContextImpl.java:2239) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.content.ContentResolver.acquireUnstableProvider(ContentResolver.java:1520) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.content.ContentResolver.query(ContentResolver.java:518) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.content.ContentResolver.query(ContentResolver.java:475) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.mmslib.a.VL(SourceFile:40) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.sms.i.ahs(SourceFile:1498) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.sms.DatabaseMessages$  SmsMessage.getProjection(SourceFile:120) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.q.<init>(SourceFile:450) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.m.Lg(SourceFile:131) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.SyncMessagesAction.Jf(SourceFile:293) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.SyncMessagesAction.IU(SourceFile:244) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.BackgroundWorkerService.Kk(SourceFile:146) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at com.android.messaging.datamodel.action.BackgroundWorkerService.onHandleIntent(SourceFile:123) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.app.IntentService$  ServiceHandler.handleMessage(IntentService.java:68) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.os.Handler.dispatchMessage(Handler.java:102) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.os.Looper.loop(Looper.java:154) 06-27 18:43:54.103  3530  3843 F MessagingAppDataModel:     at android.os.HandlerThread.run(HandlerThread.java:61) 06-27 18:43:54.103  3530  3843 E MessagingAppDataModel: SyncMessagesAction: unexpected failure in scan 

Based on these two exceptions, I’m guessing that I shouldn’t have restored the app but just the data, and some important metadata of the app got lost or wasn’t restored correctly. However I’m not sure where I would find that metadata or what it should be.

  • I tried TWRP “Restore Contexts”.
  • Someone on the /r/Android Discourse suggested I dirty load the same ROM. Unfortunately support for LineageOS on my handset is discontinued and there’s no images to download. I tried re-using the latest update from /data/lineageos_updates, but that didn’t fix my problem.
  • I took a backup of my phone in its current (semi-working) state and I’ve tried wiping data for the messaging app, the telephony provider, the settings app, but I still have the same crashes.

Has anyone seen these exceptions before? What are these providers? Where are they kept on a normal Android system? What creates them, and is there a way to manually cause them to be created?

Boot Camp cannot install Windows because “The startup disk cannot be partitioned or restored to a single partition.” [duplicate]

This question already has an answer here:

  • The startup disk cannot be partitioned or restored to a single partition. Windows 10 and Mojave 1 answer

I have installed macOS Mojave 10.14.5 on a MacBook Pro early 2011. Now I want to install Windows 10 but I am unable to do it. Boot Camp shows the error

The startup disk cannot be partitoned or restored to a single partition.

Below is the output of diskutil list

/dev/disk0 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *500.0 GB   disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:          Apple_Corestorage Mac-OS                  499.0 GB   disk0s2    3:                 Apple_Boot Recovery HD             650 MB     disk0s3  /dev/disk1 (internal, virtual):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:                  Apple_HFS Mac-OS                 +181.3 GB   disk1                                  Physical Store disk0s2    1:                APFS Volume Macintosh HD            116.4 GB   disk1s1    2:                APFS Volume Preboot                 44.6 MB    disk1s2    3:                APFS Volume Recovery                512.8 MB   disk1s3    4:                APFS Volume VM                      4.3 GB     disk1s4 

Fixing “The startup disk cannot be partitioned or restored to a single partition” error on a fresh Mac OS installation

I’ve been working on this problem for over 10 hours. First of all, I installed Mojave using the Mojave patcher on an older MacBook. I completely erased my disk before installing Mojave. Here is the output of diskutil list:

    /dev/disk0 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *1.0 TB     disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:          Apple_CoreStorage Local Disk              999.3 GB   disk0s2    3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3  /dev/disk1 (internal, virtual):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:                  Apple_HFS Local Disk             +999.0 GB   disk1                                  Logical Volume on disk0s2                                  17B0E440-563B-4759-B442-CC8FE78F58DB                                  Unencrypted 

and sudo gpt -r show disk0:

       start        size  index  contents            0           1         PMBR            1           1         Pri GPT header            2          32         Pri GPT table           34           6                    40      409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B       409640  1951845952      2  GPT part - 53746F72-6167-11AA-AA11-00306543ECAC   1952255592     1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC   1953525128           7            1953525135          32         Sec GPT table   1953525167           1         Sec GPT header  

Why am I still getting this error when I run boot camp assistant? I’ve already followed a guide that involved deleting any hidden Microsoft files in the EFI EFI partition. But I don’t think it really did anything because as I said, I completely erased this disk before installing Mojave. I’m at a complete loss here, and I’m desperate for help.

EDIT: I know this question has been asked before, but from what I can tell, no one has had this exact problem. On the posts I see involving this problem you can clearly see Microsoft partitions in the diskutil list. I have no visible Microsoft partitions. I performed a clean install. So I’m at a loss for why I keep getting the error.

Active Directory Group permissions ignored after User Profile Sync on restored site

I’ve restored a content database into a Sharepoint Server 2019 web application. Any user that does not have Full Control is not able to get in and just get a ‘Sorry, this list hasn’t been shared with you.’

Most users are allowed permission through Domain\Domain Users active directory group. The site works and admins are able to use and browse. I’ve run the Active Directory Import with default mappings. I’m using claims authentication through windows auth.

If I remove and re-add the user or group then they are able to see the site fine.

Is there a way to update all the users and groups so they’re able to access? Does the AD import need to be updated?

How to run GCESysprep on an image restored from a snapshot

I followed the directions for cloning a Windows Server Virtual Machine as described in the following thread and everything seemed to go fine. I even tried both options for fixing the Boot Config Data EasyBCD and bcdboot.exe. However, if I try to create a reusable image with GCESysprep the new image will not boot any more.

Normally GCESysprep works ok, but it does not seem to work on an image restored from a snapshot. Is there a step that that I may be skipping?

Note, the same instructions are also posted on ServerFault here.

Why stock kernel is not being restored even after flashing boot.img?

I have a moto g4 plus(rooted) which is stuck on bootloop. I dropped the device and 1/3 of the screen was gone but the game I was playing was still on the screen. So I restarted my device but it stuck in a bootloop of starting screen which tells you that “your device has been unlocked and can’t be trusted”. I tried restoring my copy of Stock rom via fastboot but it did not work. The bootloop continues. Out of curiosity I tried getvar command on Fastboot and then I saw that my kernel is still ElementalX and not stock kernel even after flashing the stock rom several times. Can you guys tell me what’s wrong?

The startup disk cannot be partitioned or restored to a single partition. Windows 10 and Mojave iMac Fusion Drive

The startup disk cannot be partitioned or restored to a single partition.

The startup disk must be formatted as a single Mac OS Extended (Journaled) volume or already partitioned by Boot Camp Assistant for installing Windows.

I had installed Windows 10 via bootcamp in my mac. Current version is 10.14.2

I received a strange blue screen error and repaired windows. After the repair the boot camp assistant and tools was not installed so its just a copy of windows without boot camp assistance. I would like to erase that volume and try again but boot camp assistant will not erase the drive.

This is the output of diskutil list

enter image description here

And here is the output of diskutil cs list

enter image description here

Can anyone please help me, I would follow the advice already provided on this site concerning this issue, but my fusion drive issue is just a little different.

Passing restored packages as artefacts in GitLab Continuous Integration


Introduction

I’m writing a script in YAML for building ASP.NET Core 2.2 project using GitLab Continuous Integration. In all YAML samples I could find (and there are not many) for building .NET Core based applications using GitLab CI I could see something like this:

before_script:  - 'dotnet restore' 

before_script is running a dependency restore before every job. It makes sense because if you use free GitLab runners (like I do) every job is executed on a different machine. There is no possibility to preserve state from previous jobs (with exception on cache and artifacts, but I’ll get to that later). What that means is that on the next job, all previously restored packages will be gone, and they need to be restored again. And on the next job once again. And again on every job in the pipeline which needs the packages. I noticed a redundancy there. A redundancy that takes precious time, because a huge project with a lot of third-party packages takes a while for a full restore.

Using job artifacts

I found a way to preserve those packages and then pass them to the next job via GitLab artifacts:

restore:  stage: restore  script:   - 'dotnet restore --packages .nuget/'  artifacts:   paths:    - 'src/**/obj/*'    - '.nuget/' 

Let’s break it down. With dotnet restore --packages .nuget/ I explicitly specify a custom directory for packages to be restored. Then I specify two paths which GitLab CI will be interested in when creating a job artifacts. dotnet restore creates a few files with metadata about packages inside a obj/ directory, so these will be needed as well. I include them in src/**/obj/*. Finally, I include the .nuget/ directory which after dotnet restore should contain all restored dependencies.

Note: A dependency restore saves the path where the packages will be kept inside <PROJECT_NAME>/obj/project.assets.json file. After that, there is no need for explicitly specifying where the restored packages are e.g. when building the project.

Eventually, in the next job I use previously created job artifacts by specifying a job dependecy. In that way, GitLab CI knows that it should download job artifacts from the dependant job.

build:  stage: build  script:   - 'dotnet build --no-restore'  dependencies:   - restore 

Whole YAML script:

image: microsoft/dotnet:2.2-sdk  variables:  SOURCE_CODE_DIRECTORY: 'src'  BINARIES_DIRECTORY: 'bin'  OBJECTS_DIRECTORY: 'obj'  NUGET_PACKAGES_DIRECTORY: '.nuget'  stages:  - restore  - build  restore:  stage: restore  script:   - 'dotnet restore --packages="$  NUGET_PACKAGES_DIRECTORY"'  artifacts:   paths:    - '$  SOURCE_CODE_DIRECTORY/**/$  OBJECTS_DIRECTORY/*'    - '$  NUGET_PACKAGES_DIRECTORY/'  build:  stage: build  script:   - 'dotnet build --no-restore'  dependencies:   - restore 

Feedback

Please tell me what you think, any weaknesses of my approach, code smells, or maybe a better solution. All kind of constructive feedback appreciated.