[Pie/10] [System-as-root] Multidisabler: encryption, Vaultkeeper, proca, etc.

[Arthur Morgan]

Sir any solution to fix this on my n10plus 5g n976b . After i intall 100% any custom rom in one ui 2.5 it apear this error Updating partitions details....
Failed to mount"/system_root" (invalid argument "
.... done " and rom has erased i use your last twrp

 

[ianmacd]

Wow, that's a serious deal breaker...
What about Samsung devices with Snapdragon?

Snapdragon-based devices can use encryption, but it's finicky. And when it breaks, it's a real inconvenience.

In Europe, we're primarily Exynos users, so we're simply used to having no encryption on our devices. That's the price of using TWRP.

 

[doclucas]

Snapdragon-based devices can use encryption

I meant - can TWRP decrypt encrypted /data on Samsung SD based phones? Does it prompt for PIN when accessing recovery on these devices and then decrypts like on other brands with encrypted data?

but it's finicky. And when it breaks, it's a real inconvenience.

What do you mean? Examples?
Also, is that only on Samsung's SD based encrypted devices or in general encrypted SD devices with TWRP?

 

[admen145]

hmm///
NOT GOOD that very important problem is ignored....:sad

 

[Magendanz]

@ianmacd, the 2019 Galaxy Tab 10.1 [SM-T510] started hanging on reboot with Android 10 OEM firmware (BTFN and later). Boots fine prior to installing Multidisabler v2.6 and than hangs on SAMSUNG logo after. Also works fine after install on custom AOSP 10 and LOS 17.1 ROMs. Sorry, I don't have a logcat dump yet, but I just haven't had the time.

Could this be related to the bug you fixed in the v2.5 release for 2019 devices upgraded to OneUI 2.5?

UPDATE: Okay, it seems that if you wait about 10 minutes, the tablet will eventually reboot and succeed the second time. Not sure what's taking so long.

 

[ianmacd]

@ianmacd, the 2019 Galaxy Tab 10.1 [SM-T510] started hanging on reboot with Android 10 OEM firmware (BTFN and later). Boots fine prior to installing Multidisabler v2.6 and than hangs on SAMSUNG logo after. Also works fine after install on custom AOSP 10 and LOS 17.1 ROMs. Sorry, I don't have a logcat dump yet, but I just haven't had the time.

Could this be related to the bug you fixed in the v2.5 release for 2019 devices upgraded to OneUI 2.5?

UPDATE: Okay, it seems that if you wait about 10 minutes, the tablet will eventually reboot and succeed the second time. Not sure what's taking so long.

I've seen devices take a couple of minutes to start booting after a flash, but never 10 minutes. Subsequent boots start more quickly, and I have no idea what such devices are doing after that first flash, but I would assume they are calculating some kind of CRC over the new image and storing that for future reference.

I don't think this can be related to the bug you mention. That was just to disable the cass service, which wouldn't stall booting.

What happens on third and subsequent boots? Also a 10 minute wait before it boots?

I haven't seen this phenomenon on any other device.

 

[Kovacs-]

Question about multidisabler

Hey @ianmacd I tried using your multidisabler for the A70, sadly it didn't succeed is there any chance that you could add support for it?

Thanks.

 

[Magendanz]

@ianmacd, if I lose WiFi when switching to a custom ROM built from unmodified Samsung source, is it safe to assume that this is caused by the libsecure_storage issue that you document here? And is this the same fix that @Noxxxious used in his R8 release of the NX kernel?

I hadn't hit this before with the Exynos-based tablets, but the Galaxy Tab A 8.0 (2019) is based on the Snapdragon 429. The stock boot image works fine, but anything I build from kernel source has no WiFi whatsoever.

UPDATE: According to @Noxxxious, the real fix is to export the proper Android platform version in your kernel makefile. I'll include more details here after I verify.