Unprecedented Corruption in Adopted Storage: Please Insert SD Card Again

[tberma]

I have adopted my whole SD card and I have flashed Syberia custom kernel latest version and SELinux is permissive. It was working fine until I have used SWAPRAM by HuskyDG magisk module and rebooted It became unmountable though the encryption key exists in /data/misc/vold, but It does not work and even though I tried “sm mount private:179,194”, It seems applied as It does not throw any error but still It is not working after I recheck with “sm list-volumes” as It stills show unmountable. My /data is decrypted, but the SD card is not decrypted. How can I decrypt the card without losing data and prevent the problem from happening again?

 

[Droidriven]

I have adopted my whole SD card and I have flashed Syberia custom kernel latest version and SELinux is permissive. It was working fine until I have used SWAPRAM by HuskyDG magisk module and rebooted It became unmountable though the encryption key exists in /data/misc/vold, but It does not work and even though I tried “sm mount private:179,194”, It seems applied as It does not throw any error but still It is not working after I recheck with “sm list-volumes” as It stills show unmountable. My /data is decrypted, but the SD card is not decrypted. How can I decrypt the card without losing data and prevent the problem from happening again?

Try flashing the kernel you had before. Then undo the Adoptable Storage process to return to default storage settings. Then boot into recovery and wipe the cache partition and dalvik cache. Then install the new kernel and reboot into system. Then set up Adoptable Storage again.

 

[tberma]

Try flashing the kernel you had before. Then undo the Adoptable Storage process to return to default storage settings. Then boot into recovery and wipe the cache partition and dalvik cache. Then install the new kernel and reboot into system. Then set up Adoptable Storage again.

Well, I was trying to recover, not to destroy the data in my SD. It seems whenever It changes fingerprint and/or use swap file It breaks along with /data.

 

[Droidriven]

Well, I was trying to recover, not to destroy the data in my SD. It seems whenever It changes fingerprint and/or use swap file It breaks along with /data.

I did not say to factory reset or wipe the data partition. I said to wipe the cache/dalvik cache partition. This does not wipe your precious user data.

 

[tberma]

I did not say to factory reset or wipe the data partition. I said to wipe the cache/dalvik cache partition. This does not wipe your precious user data.

Why should I undo the Adoptable Storage then?

 

[tberma]

I did not say to factory reset or wipe the data partition. I said to wipe the cache/dalvik cache partition. This does not wipe your precious user data.

I had only Siberia kernel before applying adopted storage. Where is the problem? Is it in the kernel or not. Even TWRP do not want to work, and it crashes rebooting.

 

[tberma]

After Ejecting SD temporally I managed to enter to TWRP, but It shows (I/O error) When I try to wipe Cache and Dalvik-Cache

I did not say to factory reset or wipe the data partition. I said to wipe the cache/dalvik cache partition. This does not wipe your precious user data.

 

[Droidriven]

After Ejecting SD temporally I managed to enter to TWRP, but It shows (I/O error) When I try to wipe Cache and Dalvik-Cache

When you setup adoptable storage, the external sdcard became incorporated into internal as if they are one complete drive. TWRP is looking for the external sdcard so it can wipe the cache partition.

 

[Droidriven]

Why should I undo the Adoptable Storage then?

I'm saying to return the device to an unmodified stock working state without the custom kernel and without Adoptable Storage. Then you can install your custom kernel then setup adoptable storage again.

If flashing the kernel caused the issue and if the kernel and adoptable storage are able to work together, then, what I posted would be the best way to get to that point.

 

[tberma]

I'm saying to return the device to an unmodified stock working state without the custom kernel and without Adoptable Storage. Then you can install your custom kernel then setup adoptable storage again.

If flashing the kernel caused the issue and if the kernel and adoptable storage are able to work together, then, what I posted would be the best way to get to that point.

I can't verify if It is a kernel problem. I need some many experiences. Still, I had to flash Syberia kernel for SELinux to be permissive. However, can you compile this new updated kernel for me, hopefully It fixes it? https://github.com/hi6250-oss-old/android_kernel_huawei_hi6250-8

 

[tberma]

I'm saying to return the device to an unmodified stock working state without the custom kernel and without Adoptable Storage. Then you can install your custom kernel then setup adoptable storage again.

If flashing the kernel caused the issue and if the kernel and adoptable storage are able to work together, then, what I posted would be the best way to get to that point.

I was trying to insert my SD using Syberia kernel into the EMUI 8 ROM, but I could not and the UI gets freeze until I flashed stock kernel. I become able to use my SD. However, I cannot use this kernel on GSI because It is not permissive. Therefore, It is a kernel issue as far as I can see.

 

[xXx yYy]

Android's kernel is the most important component to run a mobile device as it is a bridge between hardware and software of a mobile device. Without kernel it is not possible for a device to run. Installing a new kernel can be a bit dicey, but when done correctly there’s really a minimal risk. But, it is not necessary to flash a Custom Kernel in your device unless you want some additional features because the Stock Kernel provided by OEMs works out of the box and without any issues.

IMO a replacement of Stock Kernel by a Custom Kernel like Syberia doesn't always benefit you, especially if it wasn't compiled for the mobile device in question.

 

[tberma]

Android's kernel is the most important component to run a mobile device as it is a bridge between hardware and software of a mobile device. Without kernel it is not possible for a device to run. Installing a new kernel can be a bit dicey, but when done correctly there’s really a minimal risk. But, it is not necessary to flash a Custom Kernel in your device unless you want some additional features because the Stock Kernel provided by OEMs works out of the box and without any issues.

IMO a replacement of Stock Kernel by a Custom Kernel like Syberia doesn't always benefit you, especially if it wasn't compiled for the mobile device in question.

Stock kernel does not support Selinux Permissive

 

[xXx yYy]

Stock kernel does not support Selinux Permissive

This statement for me is absolute nonsense. Each Android's SELinux can set to permissive if Android is got rooted.

Depending on how your device was rooted and what Android ROM your running will determine how you can disable it. The first thing to try is:

adb shell su 0 setenforce 0

This is NOT the same as:

adb shell setenforce 0

The execute on su causes a domain transition from shell (which cannot setenforce) into the su domain (which can call setenforce).

 

[tberma]

This statement for me is absolute nonsense. Each Android's SELinux can set to permissive if Android is got rooted.

Depending on how your device was rooted and what Android ROM your running will determine how you can disable it. The first thing to try is:

adb shell su 0 setenforce 0

This is NOT the same as:

adb shell setenforce 0

The execute on su causes a domain transition from shell (which cannot setenforce) into the su domain (which can call setenforce).

Still, It throws an error until I change the kernel. It is something famous with HW Hi6250.

 

[tberma]

This statement for me is absolute nonsense. Each Android's SELinux can set to permissive if Android is got rooted.

Depending on how your device was rooted and what Android ROM your running will determine how you can disable it. The first thing to try is:

adb shell su 0 setenforce 0

This is NOT the same as:

adb shell setenforce 0

The execute on su causes a domain transition from shell (which cannot setenforce) into the su domain (which can call setenforce).

This is the error: setenforce: Couldn't set enforcing status to '0': Invalid argument

 

[xXx yYy]

Then try

adb shell "su -c 'setenforce permissive'"

 

[tberma]

I went through a big error when the battery drained and the phone shutdown and could not turn it back on and redirect me to ERecovery until I flash the stock kernel. I booted, but ADB needs to be authorized from TWRP, therefore I have launched the command in Termux: "su" then "setenforce permissive": same error: Invalid argument.

 

[xXx yYy]

Really weird.

 

[tberma]

Really weird.

And there is no good kernel yet to handle /data while SELinux is permissive.