Related
Hi All,
I am writing a batch script to perform functions via ADB to set up our devices.
The device is rooted, and i can do the following via ABD:
adb root
adb remount
adb shell
sqlite3 /data/system/locksettings.db
sqlite3> update locksettings SET value='1' where name='lockscreen.disabled';
sqlite> .quit
There is not issue so far, and this works to disable the screen lock from swipe to "none"
Here is the issue, I have created a batch file, which processes all the various commands I have, which works perfectly, the problem is i cannot execute that as one command I.E.
adb shell sqlite3 /data/system/locksettings.db update locksettings SET value='1' where name='lockscreen.disabled';
This fails, i have tried various syntax changes but i get and error of TO MANY OPTIONS FOR LOCKSETTINGS
any thoughts or solutions would be most appreciated.
Kind regards
Anthony Aveley
AnthonyAveley said:
Hi All,
I am writing a batch script to perform functions via ADB to set up our devices.
The device is rooted, and i can do the following via ABD:
adb root
adb remount
adb shell
sqlite3 /data/system/locksettings.db
sqlite3> update locksettings SET value='1' where name='lockscreen.disabled';
sqlite> .quit
There is not issue so far, and this works to disable the screen lock from swipe to "none"
Here is the issue, I have created a batch file, which processes all the various commands I have, which works perfectly, the problem is i cannot execute that as one command I.E.
adb shell sqlite3 /data/system/locksettings.db update locksettings SET value='1' where name='lockscreen.disabled';
This fails, i have tried various syntax changes but i get and error of TO MANY OPTIONS FOR LOCKSETTINGS
any thoughts or solutions would be most appreciated.
Kind regards
Anthony Aveley
Click to expand...
Click to collapse
Hi Anthony
Please, feel welcome to access our experts at the below forum as they should be able to tackle your question.
Android Development and Hacking > Android General
Nice regards, good luck and mainly, have fun.
.
So recently I saw a post on galaxy s8 that use ADB to make the phone immersive...
I created this post so that if people find cool ADB commands that would improve our experience using s8....
So feel free to share any ADB commands that work on s8
E.g immersive mode or setting up GSAM etc....
Scripts ?
Here is a guide to enable immersive mode: By Rashad83
https://forum.xda-developers.com/ne...tion-bar-status-bar-app-t3509747/post69855521
Working System Ui Tuner: By Zacharee1
https://labs.xda-developers.com/store/app/com.zacharee1.systemuituner
Enable "Mobile data" icon on status bar for locked carriers: By Tnick84
https://forum.xda-developers.com/galaxy-s8+/help/adb-commands-t3598553/post72102222
[ROOT] Set up automatic nandroid backup using TWRP/Tasker:
By RuggedHunter
https://forum.xda-developers.com/galaxy-s8+/help/adb-commands-t3598553/post72096116
Love the idea of this thread! I use a ton of shell scripts you might find interesting and am always looking for new ones. I'll share some here over the next few days/weeks. Hopefully there are lots of useful contributions to your thread!
One suggestion I might make? Use your OP post #1 as a "table of contents" and link to individual posts in your thread with valuable information.
So here's an adb command I use with TWRP:
backup BDSOM
But what makes it useful is taking advantage of TWRP's openrecoveryscript feature so that the command can be written while the system is booted and executed when recovery boots. Many commands can be executed this way.
Using Tasker, I automate nandroid backups every night while I sleep. In the middle of the night it deletes the oldest backup, writes the command "backup BDSOM" to /cache/recovery/openrecoveryscript , and reboots to recovery. As soon as TWRP boots it runs the command and creates a compressed nandroid, then reboots system...So my alarm still wakes me up in the morning.
Of course using Tasker and openrecoveryscript isn't required. You can just use this command with adb while in TWRP to create a backup.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
Here's another:
dumpsys deviceidle
Run in an emulator this will print a list of commands and parameters you can use to manually control Doze. You can force doze on when the screen is on, or switch to any of the various "stages" of doze, or add/remove packages from the whitelist.
Examples:
dumpsys deviceidle force-idle
dumpsys deviceidle whitelist +com.package.name
dumpsys deviceidle whitelist -com.package.name
dumpsys deviceidle step
RuggedHunter said:
So here's an adb command I use with TWRP:
backup BDSOM
But what makes it useful is taking advantage of TWRP's openrecoveryscript feature so that the command can be written while the system is booted and executed when recovery boots. Many commands can be executed this way.
Using Tasker, I automate nandroid backups every night while I sleep. In the middle of the night it deletes the oldest backup, writes the command "backup BDSOM" to /cache/recovery/openrecoveryscript , and reboots to recovery. As soon as TWRP boots it runs the command and creates a compressed nandroid, then reboots system...So my alarm still wakes me up in the morning.
Of course using Tasker and openrecoveryscript isn't required. You can just use this command with adb while in TWRP to create a backup.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
Here's another:
dumpsys deviceidle
Run in an emulator this will print a list of commands and parameters you can use to manually control Doze. You can force doze on when the screen is on, or switch to any of the various "stages" of doze, or add/remove packages from the whitelist.
Examples:
dumpsys deviceidle force-idle
dumpsys deviceidle whitelist +com.package.name
dumpsys deviceidle whitelist -com.package.name
dumpsys deviceidle step
Click to expand...
Click to collapse
I was talking about adb scripts without rooting, but that's fine maybe somebody else will need this
Ah, sorry I missed that.
RuggedHunter said:
Ah, sorry I missed that.
Click to expand...
Click to collapse
But nah it's fine keep posting these as well just in case I root or somebody else might need it...
How to enable Mobile Data Icon in quick settings notification dropdown
https://forum.xda-developers.com/ne...tion-bar-status-bar-app-t3509747/post72057634
tnick84 said:
How to enable Mobile Data Icon in quick settings notification dropdown
https://forum.xda-developers.com/ne...tion-bar-status-bar-app-t3509747/post72057634
Click to expand...
Click to collapse
What do you mean by This, you can rearrange the icons how you want.
underdog_656 said:
What do you mean by This, you can rearrange the icons how you want.
Click to expand...
Click to collapse
Who is your carrier? Tmo doesn't have it enabled by default. Or do you have an app doing it. Cause the point of this thread, correct me if I'm wrong, is to avoid installing an app to do something that a simple adb command can do.
tnick84 said:
Who is your carrier? Tmo doesn't have it enabled by default. Or do you have an app doing it. Cause the point of this thread, correct me if I'm wrong, is to avoid installing an app to do something that a simple adb command can do.
Click to expand...
Click to collapse
My galaxy s8 is European unlocked so no it's not t mobile... probably that's why I have this option... yes you are correct so that we would avoid installing apps. Thank you for sharing
I'm on Sprint and I've seen videos showing that the navbar can have different colors but Sprint left it out. While there is an app to change it, I was wondering if there's an Adb command that can enable that feature?
Ramer said:
I'm on Sprint and I've seen videos showing that the navbar can have different colors but Sprintleft it out. While there is an app to change it, I was wondering if there's an Adb command that can enable that feature?
Click to expand...
Click to collapse
So sprint doesn't have this layout?
Edit: so upon research I wasn't able to find any ADB commands that would do that.... maybe someone else might know.
underdog_656 said:
So sprint doesn't have this layout?
Edit: so upon research I wasn't able to find any ADB commands that would do that.... maybe someone else might know.
Click to expand...
Click to collapse
No, they don't. I was watching S8+ YouTube videos when I noticed it was missing.
I can not get adb to recognize phone. I type in the command and get "error: no devices/emulators found". Installed drivers etc.
Edit: Got it figured out.
Gonna stick in a quick message to revive this thread. So i have certain apps set to be fully immersive using the adb method, but in the app store, this app bxbye, remaps the bixby button to have other uses, for example, toggling immersive mode. Basically when I use this feature it seems to clear all the immersive settings I had input for all my apps eg Instagram,spotify etc, and while I dont want to have to click the remapped bixby button for every app i want in immersive mode, i would like to use the button at times when an app is giving trouble to return it to non immersive mode.
I've not explained this very well but basically is it possible to enter these adb commands and run certain apps in immersive mode, and then use the remapped bixby button to toggle certain apps without it resetting back to non immersive for all apps?
Thanks in advance
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,
I have rooted my pixel 3 by using Magisk,
my version is still Android pie,
it has successfully rooted but then when I type "adb root" it returns adbd cannot run as root in production builds,
I found out it might because I need to disable the verity, but when I type adb disable-verity it shows "verity cannot be disabled/enabled - USER build",
I have tried to follow the steps from https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom but I don't quite understand how to do it,
I was wondering if anyone have more specific steps that will be able to disable the verity.
Thanks!
Skylar514 said:
Hello,
I have rooted my pixel 3 by using Magisk,
my version is still Android pie,
it has successfully rooted but then when I type "adb root" it returns adbd cannot run as root in production builds,
I found out it might because I need to disable the verity, but when I type adb disable-verity it shows "verity cannot be disabled/enabled - USER build",
I have tried to follow the steps from https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom but I don't quite understand how to do it,
I was wondering if anyone have more specific steps that will be able to disable the verity.
Thanks!
Click to expand...
Click to collapse
In magisk advanced settings untick preserve adb verity and reinstall.
wangdaning said:
In magisk advanced settings untick preserve adb verity and reinstall.
Click to expand...
Click to collapse
Hello,
Thank you for your respond.
I have done that and it still doesnt let me disable the verity.
Is there any other way I can disable the verity?
Thanks!
Skylar514 said:
Hello,
Thank you for your respond.
I have done that and it still doesnt let me disable the verity.
Is there any other way I can disable the verity?
Thanks!
Click to expand...
Click to collapse
Use proton kernel!
pheco said:
Use proton kernel!
Click to expand...
Click to collapse
Hello,
I just installed the proton kernel,
and I checked my kernel version it is "Linux version 4.9.191-Proton-v19-g225054cc ([email protected]) (GCC 9.1.0) #20 SMP PREEMPT Sun Sep 8 21:50:57 PDT 2019",
but when I tried adb dm-verity it still shows verity cannot be disabled/enabled - USER build.
I was wondering if you have any idea?
Thank you.
I think you might have to do it to both slots. If it is still enabled on one of them I think it still checks.
Hello,
I upgrade my phone to android 10, and I can't flash the proton kernel,
I have done it to both slots and its still unable to disable.
Any idea?
Thank you!
Skylar514 said:
Hello,
I upgrade my phone to android 10, and I can't flash the proton kernel,
I have done it to both slots and its still unable to disable.
Any idea?
Thank you!
Click to expand...
Click to collapse
As far as I know you cannot do it in 10. I have never updated and tried, but that is what I have heard. There is no way to modify system except systemlessly with magisk modules. What exactly are you trying to do, might help get more suggestions if you tell us.
wangdaning said:
As far as I know you cannot do it in 10. I have never updated and tried, but that is what I have heard. There is no way to modify system except systemlessly with magisk modules. What exactly are you trying to do, might help get more suggestions if you tell us.
Click to expand...
Click to collapse
I am trying to run python script on the phone, so I have found this website https://medium.com/swlh/python-on-android-root-4aa56f22070a
and I was trying to follow the step to install python on the phone, but I am stuck at the adb remount command step.
It shows that I need to type adb root, but when I typed adb root it shows "adbd cannot run as root in production builds",
and I have try mount -o rw,remount /system, it gave me error "mount: '/system' not in /proc/mounts".
I checked mount and for some reason it shows system_root instead of system for "/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)", so I did some research and found out that I need to disable the verity, but when I tried to disable it it gave me the error which is "verity cannot be disabled/enabled - USER build".
Skylar514 said:
I am trying to run python script on the phone, so I have found this website https://medium.com/swlh/python-on-android-root-4aa56f22070a
and I was trying to follow the step to install python on the phone, but I am stuck at the adb remount command step.
It shows that I need to type adb root, but when I typed adb root it shows "adbd cannot run as root in production builds",
and I have try mount -o rw,remount /system, it gave me error "mount: '/system' not in /proc/mounts".
I checked mount and for some reason it shows system_root instead of system for "/sbin/.magisk/block/system_root on /sbin/.magisk/mirror/system_root type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr)", so I did some research and found out that I need to disable the verity, but when I tried to disable it it gave me the error which is "verity cannot be disabled/enabled - USER build".
Click to expand...
Click to collapse
System partition is under /system_root on Pie. I wonder if you could create a magisk module to install the app systemlessly.
wangdaning said:
System partition is under /system_root on Pie. I wonder if you could create a magisk module to install the app systemlessly.
Click to expand...
Click to collapse
Hi,
So now I am trying to unpack the boot.img file that I downloaded from google firmware website in order to try the method that provided by https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom.
But I was wondering instead of editing boot.img, should I just edit the magisk_patched.img?
Thanks!
Skylar514 said:
Hi,
So now I am trying to unpack the boot.img file that I downloaded from google firmware website in order to try the method that provided by https://android.stackexchange.com/q...dm-verity-on-android-with-user-build-type-rom.
But I was wondering instead of editing boot.img, should I just edit the magisk_patched.img?
Thanks!
Click to expand...
Click to collapse
You are going to need root so better to modify the magisk boot image.
wangdaning said:
You are going to need root so better to modify the magisk boot image.
Click to expand...
Click to collapse
Hello,
Thank you for your respond!
Do I need to modify boot.img as well?
Or just the magisk_patched.img?
Thank you!
I think there is a way to disable verity before installing the magisk boot img, but you would have to look at the magisk github information.
Sounds good!
Thanks for your advice!
Beside that I was wondering if you know that is there anyway we can access the battery data through abd command?
I know that we can gather cpu frequency info, but I am not sure if we can get the battery data as well.
Thanks in advance!
Maybe check this thread about battery
https://forum.xda-developers.com/pixel-3-xl/themes/looking-mod-to-make-battery-indicator-t3913080
Basically I froze a system app that should not have been frozen through TitaniumBackup the result being my system refuses to boot, looping once and giving an error "cannot load Android system" and suggesting a full wipe, which I hope to avoid in either case.
What are my options at this point, in defrosting it or undoing what TitaniumBackup has done within the confines of the TWRP recovery or adb systems? I don't remember the package by name as I froze 2-3 of them, but I assume defrosting them all would suffice.
I will try to provide some basic information about the unit and its software if it helps. Moto G Power running Android 10 and TWRP 3.4.0.0 which is not installed but booted using fastboot and it has Magisk as root.
TaZeR369 said:
Basically I froze a system app that should not have been frozen through TitaniumBackup the result being my system refuses to boot, looping once and giving an error "cannot load Android system" and suggesting a full wipe, which I hope to avoid in either case.
What are my options at this point, in defrosting it or undoing what TitaniumBackup has done within the confines of the TWRP recovery or adb systems? I don't remember the package by name as I froze 2-3 of them, but I assume defrosting them all would suffice.
I will try to provide some basic information about the unit and its software if it helps. Moto G Power running Android 10 and TWRP 3.4.0.0 which is not installed but booted using fastboot and it has Magisk as root.
Click to expand...
Click to collapse
Have you tried this?. Don't forget to thank that person if it works.
If it doesn't work, you can use ADB through twrp with the Package Manager binary from /system/xbin/pm to list all disabled apps like this:
Bash:
adb shell pm list packages -d
then you can enable those disabled apps/packages through:
Bash:
adb shell pm enable <userID> <package name>
Slim K said:
Have you tried this?. Don't forget to thank that person if it works.
If it doesn't work, you can use ADB through twrp with the Package Manager binary from /system/xbin/pm to list all disabled apps like this:
Bash:
adb shell pm list packages -d
then you can enable those disabled apps/packages through:
Bash:
adb shell pm enable <userID> <package name>
Click to expand...
Click to collapse
Thank you so much for the prompt reply, this totally answered my question into how TB freeze works in android, and solved my problem I can use my phone again =)