Related
Fairly straightforward question. Is it possible to disable ART and re-enable Dalvik other than via the settings dialog, either via ADB, some sort of flashable zip or from a recovery?
I ask for two reasons. Firstly, when I flashed an experimental 4.4 build on my Galaxy Nexus, I made the mistake of enabling ART. When I restarted, because I'd stupidly flashed an incompatible gapps package, apps would force close so frequently that the constant notifications made it extremely difficult to get into the settings and turn it off again.
Secondly, I just saw a thread on Reddit where somebody was claiming that their Nexus 5 went into a bootloop after enabling ART, and they had to do a wipe to fix it.
So it seems to me it would be quite helpful to be able to disable or enable ART without having to be able to boot.
If you've found a way to fix this, I would love to know. I just turned ART on after installing a new rom, and I'm stuck in a boot loop without a recent backup.
+1
I've enabled ART on my Nexus 4 without issue. Stock ROM.
Enabling it on my 2013 Nexus 7 caused it not to boot past the boot animation anymore.
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
theesotericone said:
Just reflash the ROM from recovery. Wipe system and flash. Done. Dalvik will be enabled again. If your not rooted that's another matter but the OP seems to be.
Click to expand...
Click to collapse
I figured flashing wiping would do it but wasn't willing to wipe if there's an easier solution.
In my case it was Xposed. I flashed the disable zip and that did it. Guess I didn't reboot fully after disabling it from in the ROM.
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
MisterEff said:
He said wipe system, not data. It is possible to wipe the system information and leave your data intact.
Click to expand...
Click to collapse
Ah yes. I mistook system as data..
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
(IRoN) said:
I don't know if it allow to switch runtime, but it helps me to avoid bootloop after ota 4.4.2 on my Nexus 5.
To check current library
adb shell getprop persist.sys.dalvik.vm.lib
To set art one
adb shell setprop persist.sys.dalvik.vm.lib libart.so
Click to expand...
Click to collapse
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
THANK YOU!!!! It worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanx, it worked for me
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
It worked for me too, and I don't even use Nexus device, And done it from adb but in recovery mode with properly mounted partitions.
Thx again.
Boot into Recovery and Fix Permissions has fixed this for me (Galaxy Nexus)
EDIT: Apparently that switches it back to dalvik?!?
twistedumbrella said:
adb pull /data/property/persist.sys.dalvik.vm.lib
open the file and replace the "libart.so" with "libdvm.so" (no quotes)
adb push persist.sys.dalvik.vm.lib /data/property/
Reboot and smile
Click to expand...
Click to collapse
Thanks, this help save my day !
Saved my day too! HTCONE on Viper and I was able to use twrp and a USB otg drive. Thanks!
Sent from my HTCONE using Tapatalk
Quicker way to switch back to Dalvik
My phone was stuck in a bootloop because I did not have enough free space to switch to ART, making my device crash on boot. For a quick way to switch back to Dalvik, see below.
Boot into recovery ('adb reboot recovery' if possible), then mount /data and run this command:
Code:
adb shell "echo libdvm.so > /data/property/persist.sys.dalvik.vm.lib"
adb reboot
It will now be in Dalvik. Enjoy
I've just tested ART feature from friend's recommendation. After activating ART in my CM11 ROM, NFC and Themes Provider keep crashing and phone is not usable. So I think it's good idea to share how to revert ART setting without wiping phone or restore from backup.
Instructions to revert ART
1. Boot into recovery.
2. Run adb shell to access terminal.
3. Type 'rm /data/property/persist.sys.dalvik.vm.lib' This will remove setting default VM runtime to ART.
4. Clear Dalvik cache and reboot. Your phone should run normally now.
Instructions to set ART again
1. Boot into recovery.
2. Run adb shell to access terminal.
3. Type 'echo "libart.so" > /data/property/persist.sys.dalvik.vm.lib' This set default VM to art library file.
4. Clear Dalvik cache and reboot. Your phone should run with ART VM now.
Hope this helps.
tested on huawei honor (u8860)
[email protected]:~$ adb shell
~ # echo "libart.so" > /data/property/persist.sys.dalvik.vm.lib
/sbin/sh: can't create /data/property/persist.sys.dalvik.vm.lib: nonexistent directory
any suggestion? thank you.
hi.
the solution to get art fully working was the following one:
replacing dalvik.vm.dexopt-data-only=0 with dalvik.vm.dexopt-data-only=1 and all went fine...(build.prop)
at least it worked for me. hope it would help.
You need to mount the data partition before running the commands mentioned in the first post there...
This saved my ass! Switched to ART and after reboot, settings would only FC. Could not change anything or switch back through Dev Options. Thank you!!!!
Sent from my HTC6525LVW using Tapatalk
Thanks for the instruction. You save me as I don't have PC now and my custom ROM not support ART.
excuse me, i've been try to switch to art with adb shell, and my phone is boot up but can't get into home screen, it just stuck on starting apps? why ya?
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
s1dest3pnate said:
I installed the 8.1 Dev Preview on my Pixel XL and it can't boot due to SystemUI crashing. I think it's just because I still have overlays installed. Anyway to remove all the overlays via ADB? I'd appreciate any help! Thanks!
Click to expand...
Click to collapse
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Acid0057 said:
Can you get into recovery? There's a script that's installed that you can run to remove themes in recovery.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
s1dest3pnate said:
Yup, I remembered and found it. All fixed! Thank goodness for SubstratumRescue.zip! Thanks Substratum team!
Click to expand...
Click to collapse
Awesome!
Sent from my Pixel XL using Tapatalk
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
GBpfan95 said:
I am in the same boat. You are very ambiguous on how you actually fixed this. I am not rooted and have a Pixel 2 XL with access to adb through recovery
Click to expand...
Click to collapse
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
s1dest3pnate said:
You're right, my apologies.
adb reboot bootloader (do this as soon as you hear USB connect at the Google logo)
fastboot boot twrp (I downloaded the 3.1.1.1 version from TWRP website)
Install SubstratumRescue.zip from the substratum folder on storage.
Did not install TWRP when prompted. I might have been asked one other question during the install or somewhere in TWRP but I don't recall.
Click to expand...
Click to collapse
Does that work even if I am locked and not rooted?
GBpfan95 said:
Does that work even if I am locked and not rooted?
Click to expand...
Click to collapse
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
I just ended up factory resetting. Most of everything is backed up anyway. Definitely learned my lesson
Could you please post the SubstratumRescue.zip? I cannot get to the directory on my phone via ADB and want to try running the script commands manually.
EDIT: Nevermind, I tracked it down on the dev's AFH page.
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
pR0wl3r said:
Is it possible for you to guide me step by step on how to do this? My nexus 6p is locked and non-rooted. thanks
Click to expand...
Click to collapse
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
jeremywh7 said:
Same with my 5X; once in ADB (using the Android SDK platform tools and Google USB drivers), when you run `adb shell` to open a shell connected to your phone, `cmd overlay list` will show all available overlays, and which are active or not. In my case (I was using BalticUI) I had...
Code:
C:\platform-tools>adb shell
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[x] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
So then you can enable or disable each overlay by name. E.g.:
Code:
bullhead:/ $ cmd overlay disable com.android.systemui.BalticUI
bullhead:/ $ cmd overlay list
com.android.settings
[x] com.android.settings.BalticUI
com.android.systemui
[ ] com.android.systemui.BalticUI
[x] com.android.systemui.navbars.BalticUI
[ ] com.android.systemui.theme.dark
That "....systemui.theme.dark" I presume is the new auto-theme component in 8.1 based on wallpaper color. I tried enabling it, but after trying to open a themed component, that overlay resets off. Luckily, BalticUI didn't cause any major problems like many other themes did; the main settings screen was the biggest difference, being just a text-only list of all the strings. Now to find a dark wallpaper...
Click to expand...
Click to collapse
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
bobby janow said:
Thanks but that did not work for me. Tried to disable but it's still there. Perhaps you need root?
Click to expand...
Click to collapse
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
jeremywh7 said:
You mean you tried to disable but it still shows an [X] showing enabled for that overlay? I am not rooted, nor with unlocked bootloader, and I could toggle them off (as shown above) and on. The overlays still show up for me, but are all disabled, and resolved the issues I was having as a result.
Click to expand...
Click to collapse
Yeah still shows an x.
Sent from my Pixel using XDA-Developers Legacy app
Thanks!
AXP said:
I faced with same issue: Updated to 8.1 without disabling overlays first.
No root, locked bootloader.
In my case, system did load but was crashing every other minute.
I was able to launch subscratum+andromeda but they failed to disable overlays - it simply did not work.
So, I had do disable overlays manually via adb:
Code:
$ adb shell
$ cmd overlay list
$ cmd overlay disable OVERLAY_NAME_1
$ cmd overlay disable OVERLAY_NAME_2
,,,
Click to expand...
Click to collapse
Thanks so much mate this worked for me perfectly!
This can be done in a less manual fashion. It looks like many of you are on Windows, but I'm sure theres a way to accomplish something similar. I'm on Linux and this is how I did it.
Code:
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 echo cmd overlay disable
cmd overlay disable com.samsung.android.app.aodservice.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.smartmirroring.StatusBarIconsforSamsungextras
cmd overlay disable android.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.app.smartcapture.StatusBarIconsforSamsungextras
cmd overlay disable com.android.settings.StatusBarIconsforSamsungextras
cmd overlay disable com.samsung.android.lool.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.navbars.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.tiles.StatusBarIconsforSamsungextras
cmd overlay disable com.android.systemui.statusbars.StatusBarIconsforSamsungextras
➜ andromeda-substratum adb shell cmd overlay list | ag -Q [x] | awk '{ print $2 }' | xargs -n 1 adb shell cmd overlay disable
For reference, ag is very similar to grep. So the explanation is adb shell allows you to pass a command to it so it can run that command immediately. So adb shell cmd overlay list is the same as typing adb shell followed by cmd overlay list except it prints the output and immediately exits. So I take that output, grep (using ag in this case) for the enabled overlays and then programmatically disable them. xargs -n 1 says take at most one of the arguments passed to this command and append it to the rest of the line. So this calls adb shell cmd overlay disable __insert-overlay-here__ repeatedly.
I messed up good....
So, I tried flashing the 8.1 Final using Chainfire like a tutorial suggested. That was my second mistake.
My first one was apparently not removing my overlays. So anyway...
My device rebooted after Chainfire, and was on the G/progress bar for like 5 mins so I knew something was up.
I decided to flash the complete factory image, and I removed the '-w' from the flash-all script so it wouldn't wipe my data.
Now the device boots, and of course I have the System UI issue because I didn't clear the overlays. But wait... it gets better!
I found this thread, so I fastboot booted into TWRP to run the commands. It asks for my password- and when I enter it, it says it's invalid!! I tried numerous times, rebooted etc, and it still does not accept my passcode.
It appears I should be able to use ADB in TWRP without my passcode, so I give it a try. I am able to sideload no problem, however when I type 'adb shell' it tells me 'error:closed'. I've searched that error, which everyone says was fixed for them with either a reboot or updating their adb/fastboot. I did both of those things, and the error still persists.
I have also tried sideloading the substratumrescue.zip file I found in another thread, however it doesn't seem to be made for this systemless setup or something.
I have had to set this device up twice since I got it, and I am really not looking forward to doing it a third time, so if anyone has any suggestions that will keep my data, I would be happy to hear them out!!
What could be causing TWRP not to accept my passcode?
Why do I get the 'error:closed' when I try to adb shell?
Any help is greatly appreciated!
EDIT: Resolved. I was able to delete all overlaid apk's from /data/app.
Hi there,
Question, I got a non-rooted S8, Stock in like everything, and it runs everything fine, including Substratum!
I am wondering about one thing though after reading this thread, imagine something went wrong, what would be my options? I found the Rescue ZIP on my phone, can I apply this if needed with the original recovery from the S8? Or do I need TWRP for that?
---------- Post added at 08:44 PM ---------- Previous post was at 08:39 PM ----------
s1dest3pnate said:
Works without root, but not if you're locked I don't think. I'm not an expert and don't want to steer you in the wrong direction, but hopefully you can unlock bootloader via adb first, and then do the steps, but I'm not sure.
Click to expand...
Click to collapse
Hi mate, do I read correctly, that its possible to only boot TWRP temporaly without flashing it?
I have to put the folder/files in the same folder as platform tools?
Hello guys, this guide is for creating backup of persist partion which is holding important data about sensors, wifi + bluetooth data, imei and other stuff.
Before installing any other custom room, this is best thing to do, lot of custom roms rewrites persist partition with different data than your mobile devices has, you will have problem with calling(missing imei), problems with Wifi and other stuff, i think you get it...
REQUIRED TOOLS:
Code:
[URL="https://drive.google.com/open?id=1LW1CM6gLT9wRyy950rC6GmWAzEbcyfzE"]PersistBackupTool[/URL]
Follow this steps:
Code:
1. Root your device, this is pretty much easy guide: [URL="https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654"]LINK[/URL]
2. After rooting your device, enable Developer options (Go to settings >> System >> About phone >> tap Build number 7 times)
3. Enable usb debugging, go to Settings >> System >> Developer options >> and enable USB debugging
4. Run PersistBackup.bat and wait
5. Your persist partition will be saved in Backup folder.
ENJOY!!!
When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile
VolpeXDA said:
When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile
Click to expand...
Click to collapse
Damn, thanks for the info, will fix it soon!
Does it do the same as the following adb commands?
Code:
adb shell "su -c dd if=/dev/block/mmcblk0p27 of=/sdcard/Download/persistbackup.img"
adb pull /sdcard/Download/persistbackup.img
oreo27 said:
Does it do the same as the following adb commands?
Code:
adb shell "su -c dd if=/dev/block/mmcblk0p27 of=/sdcard/Download/persistbackup.img"
adb pull /sdcard/Download/persistbackup.img
Click to expand...
Click to collapse
Yes it is the same
VolpeXDA said:
When I lauch the PersistBackup.exe it tells me "This program was made with an Unlicensed compiler. Please buy the PRO version to distribute your exe. " And then it closes when you press any key.
I guess you missed this in your last compile
Click to expand...
Click to collapse
Fixed, thanks again for the info!
pulja9 said:
Yes it is the same
Click to expand...
Click to collapse
Cool. I think you'll want to update the OP though. As far as I know, the IMEI data is stored on the modemst1 and modemst2 partitions.
(EDITED, check the end)
First, I've tried with the "adb" commands, but I get "Permission Denied".
So, I decided to try the tool, which still gives me a "Permission Denied", but still prints a sucess message at the end "Persist partition has been successfully backed up! Partition has been saved in Backup folder!"
Not sure if it's my mistake. I'm rooted + USB_debugging.
EDIT:
OK, I've read that for adb "su" to work, you need to have device unlocked, with screen on, and grant permission.
Turns out Magisk was rejecting root permissions to Perfdump automatically.
Should work now. Nevertheless, perhaps you could check why it prints that backup worked when permission was denied. Someone could be fooled there =D
Finally: Thanks for the app
ok, this do the backup! but how to restore it?
jucaftp said:
(EDITED, check the end)
First, I've tried with the "adb" commands, but I get "Permission Denied".
So, I decided to try the tool, which still gives me a "Permission Denied", but still prints a sucess message at the end "Persist partition has been successfully backed up! Partition has been saved in Backup folder!"
Not sure if it's my mistake. I'm rooted + USB_debugging.
EDIT:
OK, I've read that for adb "su" to work, you need to have device unlocked, with screen on, and grant permission.
Turns out Magisk was rejecting root permissions to Perfdump automatically.
Should work now. Nevertheless, perhaps you could check why it prints that backup worked when permission was denied. Someone could be fooled there =D
Finally: Thanks for the app
Click to expand...
Click to collapse
riccetto80 said:
ok, this do the backup! but how to restore it?
Click to expand...
Click to collapse
I will create this week improved tool with gui, and it will have backup, restore and maybe root option.
Suspicious EXE from a junior member.
Why is it not just a script?
pulja9 said:
I will create this week improved tool with gui, and it will have backup, restore and maybe root option.
Click to expand...
Click to collapse
soo this is really work if my mac, bt wiped with rr .,, or i just need to place that original file or i need to flash stock rom and place this backup file
How can I locate the Backup folder to also backup the /persist files in another folder/device?
how to restore?
Sir, can you please help me , i totally messed up my phone , mac address -unavailable, Bluetooth- unavailable , how to get back all , i m on RR latest build , i want to back to stock . Please help me if possible .
pulja9 said:
Hello guys, this guide is for creating backup of persist partion which is holding important data about sensors, wifi + bluetooth data, imei and other stuff.
Before installing any other custom room, this is best thing to do, lot of custom roms rewrites persist partition with different data than your mobile devices has, you will have problem with calling(missing imei), problems with Wifi and other stuff, i think you get it...
REQUIRED TOOLS:
Code:
[URL="https://drive.google.com/open?id=1LW1CM6gLT9wRyy950rC6GmWAzEbcyfzE"]PersistBackupTool[/URL]
Follow this steps:
Code:
1. Root your device, this is pretty much easy guide: [URL="https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654"]LINK[/URL]
2. After rooting your device, enable Developer options (Go to settings >> System >> About phone >> tap Build number 7 times)
3. Enable usb debugging, go to Settings >> System >> Developer options >> and enable USB debugging
4. Run PersistBackup.bat and wait
5. Your persist partition will be saved in Backup folder.
ENJOY!!!
Click to expand...
Click to collapse
Lots of thanks @devs you guys are really awesome
where is my backup? i not found that
I have tried the setup procedure that was in op, however it comes up and says not recognised, can I have a step by step procedure eg do I have to go to EDL mode.
Thanks
enricogrim said:
Hello,
I see that this tool creates a .img file. Can I restore using TWRP?
thank you
Click to expand...
Click to collapse
I don't think so
TWRP recognize ISO as a recovery
I think it's dangerous because backup don't have any instructions for twrp to tell it where recover it, on which partition
Correct me if I'm wrong
Sent from my Mi A1 using Tapatalk
Does anyone know how to restore a backup?
Can we use fastboot? Or tool have restore option?
Hello everyone, I'm new from XDA and I have a problem in android system file replacing.
1. I managed to reboot my device Motorola Shamu 7.1.1 to recovery mode(TWRP3.3.1.0) and adb sideload xposed.zip.
2. Everything is ok and after I'm reboot XposedInstaller still says framework not installed. adb shell to see /system and there is no "xposed.prop" in the path.
3. Rebooting to rec and resee /system and "xposed.prop" is in /system indeed, and it just disappeared after reboot.
I could just root my device to make XposedInstaller installing framework in booted system so there is no need to recommend magisk.
I just wanna figure out what I'm encountering in this situation. What does it happen.
Thanks for your help
I have heard about the slot A/B but it seems not the reason in shamu.