adb – Disable Audio Notifications on Android 10

I have a Samsung Galaxy S20FE, running Android 10 and One UI 2.5. Previously on my Galaxy S8 I had the ability to toggle audio and vibration independently for notifications on a per-app basis. This meant, for example, that I could have Facebook Messenger only vibrate for messages, and not chime unless I was tagged in a group chat.

I have spoken to a Samsung representative today, who told me that this feature has indeed been removed. I would like to know if there is a way (using ADB, for example) to forcefully re-enable it myself.

I have done some research which has come up fruitless, and I would appreciate any and all help.

Does adb backup/restore still work because it says it’s deprecated?

I want to reset my phone but want to recover the system data before doing so. I tried to create a backup with adb and tried to restore it on a virtual device to see if it works. So I tried to restore it with adb on the virtual device and it would say that it fully restored it at the end. But nothing really changed. I wonder if adb backup/restore still works or if I did something wrong.

Thank you in advance

How can I boot to a specific partition with ADB?

Though it requires adb root, one method to do this would be to use bootctl if available.

#> bootctl set-active-boot-slot SLOT
#> reboot

Note: SLOT is a number, you can find out the labels by looping through them and calling get-suffix for example this little shell script,

for slot in $(seq 0 $(expr $(bootctl get-number-slots) - 1)); do
  echo $slot: $(bootctl get-suffix $slot);
done;

Which will return the mapping,

0: _a
1: _b

See also: How can I tell whether I am booted into the A or B partition?

TWRP tells me: adb: sideload connection failed: insufficient permissions for device: user in plugdev group; are your udev rules wrong?

❯ adb sideload lineage-17.1-20201108-nightly-guacamole-signed.zip
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: sideload connection failed: insufficient permissions for device: user in plugdev group; are your udev rules wrong?
See [http://developer.android.com/tools/device.html] for more information
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: insufficient permissions for device: user in plugdev group; are your udev rules wrong?
See [http://developer.android.com/tools/device.html] for more information

adb – Regen default.prop – Android Enthusiasts Stack Exchange

So there is this settop box in india, called airtel internet tv(codename ganesa) It’s gone 2 years with no updates, stuck on android 6. it has no usb adb but does have wireless adb. got root using dirtycow and updated default.prop to this:

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.hardware=ganesa
ro.product.board=ganesa
ro.adb.secure=1
ro.secure=0
security.perf_harden=1
ro.allow.mock.location=0
ro.debuggable=0
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Tue Jul 16 04:42:11 UTC 2019
ro.bootimage.build.date.utc=1563252131
ro.bootimage.build.fingerprint=airtel/ganesa/ganesa:6.0.1/MUE91/06.02.73:user/release-keys
persist.sys.usb.config=none

#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.hardware=ganesa
ro.product.board=ganesa
ro.adb.secure=0
ro.secure=1
security.perf_harden=1
ro.allow.mock.location=0
ro.debuggable=1
ro.zygote=zygote32
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
ro.dalvik.vm.native.bridge=0
debug.atrace.tags.enableflags=0
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Tue Jul 16 04:42:11 UTC 2019
ro.bootimage.build.date.utc=1563252131
ro.bootimage.build.fingerprint=airtel/ganesa/ganesa:6.0.1/MUE91/06.02.73:user/release-keys
persist.sys.usb.config=none

After a quick reboot wifi adb went rip, I dont have a male-to-male usb cable rn, but can quickly make one if it is the only option!

So I would want to regen stock default.prop

Many thanks!

custom roms – Enable USB debugging through recovery mode and ADB sideload

This is a follow up question to this one. Basically, I intend to somehow use this command to remove the lock screen:

>adb sideload customROM.zip

But, the customROM.zip should be something like described here to enable USB debugging. The problem is, those steps are incomplete:

Steps to Enable USB Debugging Using Recovery Mode

  • Unzip the stock ROM.

  • Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker

  • Also, extract the Update-SuperSU.v1.65.zip file.

  • Now open the folder where you have extracted the system.img files

  • Grab any .apk file from this folder and change the extension from .apk to .zip

  • And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist)

  • Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder

  • Locate the update-script file within this folder and edit it using Notepad++

  • You need to update the build.prop file after adding the following line at the bottom
    persist.service.adb.enable=1

  • Next step is updating SQLite Database

  • Which can be done by adding the following code to the update-script file
    sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"

Cheers! You have Enabled USB Debugging
Now you can install your custom or stock ROM using ADB – USB Debugging

Although the above steps seem incomplete, they look convincing that there might be a way to modify a stock ROM to enable USB debugging by:

>adb sideload modified-stock-ROM-which-just-enables-USB-debugging-and-does-nothing-else.zip

Is there any better explanation than those steps?

adb – how to fastboot mode without Enable USB Debugging?

I have a cellphone which I can’t get access to the system, so Enable USB Debugging is not a option here. I need to factory reset this phone or upload a fresh firmeware to make it functional again, I figure it out that the way to do it is through Fastboot.

So, is there a way to unlock Fastboot mode in this phone without having to Enable USB Debugging?

Meizu Pro 6 Plus

recovery mode – Apply update from ADB: how to use it when you are locked out of the device

My cousin’s kid has played with his Samsung A8 (2018) phone and has changed his unlock pattern. So, nobody knows the pattern the child has set.

  • The phone has no Google account set up
  • The USB debugging is not activated on device before

I have rebooted into recovery mode, and entered the option Apply update from ADB:

Recovery screen

There is a message on recovery screen saying:

Now send the package you want to apply
to the device with adb sideload <filename>

I’m able to see the device by adb devices command:

Command line screenshot

According to another post, looks like it is possible to use TWRP for Samsung Galaxy A8 2018 to clear the screen lock. So, I have downloaded the following apk package:

TWRP for Samsung Galaxy A8 2018

Now I plan to install TWRP on phone by the following command and then follow the previous post:

adb sideload me.twrp.twrpapp-26.apk

Questions

Now, before doing so, I have these questions:

  • Is it possible to install *.apk packages by adb sideload? Is there any possibility that it would mess up the phone?
  • What else can I do with adb sideload to clear the screen lock?
  • What else can be done with adb sideload to back up the phone camera images and videos without wiping the data?

Thanks =)

how to edit .adb backup files

i want to edit the contents of a .adb backup file. I found a command to extract the contents:
dd if=mybackup.adb bs=24 skip=1 | zlib-flate -uncompress | tar xf –
I edited the extracted files as needed but how do i build a .adb files with the modified files?
Any ideas?
I though of streaming the directory, compressing it with zlib-flate and generating the tar file. Is it possible?

adb – Android fails to open serial port

I’m trying to run the sample apps from the following projects, android-serialport-api and Android-SerialPort-Tool.

My device is DART-MX8M-MINI Developer Kit
It’s running Android 9 (userdebug build).

The first problem I had was that I wasn’t able to see any devices.
I was able to fix this by disabling SELinux on adb.

Now, I’m faced with a different problem.
Both adb su and adb root seem to work, yet I am unable to open the ports despite being able to see them.
This is the error I get, even after setting the device and baudrate:

enter image description here

I thought, maybe this is a permission problem. So I did the following:

dart_mx8mm:/dev # chmod 777 ttymxc2
dart_mx8mm:/dev # ls -l /dev/ttymxc*
crw-rw---- 1 system    system    207,  16 2000-01-01 00:00 /dev/ttymxc0
crw-rw---- 1 system    system    207,  17 2000-01-01 00:00 /dev/ttymxc1
crwxrwxrwx 1 system    system    207,  18 2000-01-01 00:00 /dev/ttymxc2
crw-rw---- 1 bluetooth bluetooth 207,  19 2000-01-01 00:00 /dev/ttymxc3

However, the problem prevails.
The issue seems similar to that outlined here, but my .so file is in the right location.
I am also unable to reboot into bootloader and run fastboot for some twisted reason.
How is it that I am able to access su and root, I but can’t open these ports?