I have a pretty strange issue, and I can't find a similar case online. Sometimes after rebooting my phone will behave differently with adb
Normally on adb devices I have
Code:
<my Android id> device
And prompting an adb shell gives me a usual one, that can be root upon inputing su and confirming with Magisk
But sometimes (like right now) on adb devices my device will identify this way:
Code:
0123456789ABCDEF device
And prompting an adb shell will directly give me a root shell, that really works as root, bypassing Magisk authorization dialog
I installed "adbd Insecure" to control that but even it doesn't change the behavior
Has anyone here experienced it before? What kind of issue could this be?
Device is a Xiaomi Mi A1, ROM is AEX (AOSPExtended) 8.1 rooted with Magisk (currently v. 23.0). Meefik's busybox is installed
Related
In recovery mode, I couldn't access shell window by using adb shell command. (Referring to the attached pic)
The device has already be rooted and OS run very well.
I also checked the hierarchy of the system, system/bin/sh does exist.
So what's wrong with it, any advice welcome!
BTW, this adb file works fine with my another mobile featured with Qualcomm CPU, hence is adb file dependent on type of CPU?
Hey all,
Found the pieces all around the internet, but I am am working on a ROM, and though I would share my steps to enable ADB running as Root, allowing us to adb push/pull /system/app.
1. Download adbd insecure from the Google Play Store, open and select run on Boot and the "insecure" checkbox.
2. Run adb kill-server on your computer.
3. Run adb root on your computer
4. Profit
You can now push/pull/chmod/mkdir in system directories! (However on /system for example, you still need to remount it RW through adb shell first.
I've had a Motorola G4 Amazon Prime edition for sometime now and I was easily able to hide the package that displayed the lock screen ads (com.amazon.phoenix) soon after purchase. Unfortunately, when the Nougat update came rolling around, that hack no longer did the trick. So I spent a couple of hours searching through docs and trying different commands, in doing so I found a way to completely disable any and all packages installed on any Android device, system or carrier/manufacturer bloatware.
**Step by Step**
1. Install USB drivers for your Device
2. Download and Install ADB tools
3. Enable[ Developer Options](http://wccftech.com/enable-developer-options-android-nougat/) and [USB Debugging](https://technosamigos.com/enable-usb-debugging-on-android-nougat-phones/)
4. Find a good USB cable, plug it into your computer and then to your device. When the pop-up appears asking you to authorize the device, allow it.
5. Open a command prompt (cmd in windows) and type:
adb devices
6. This should return the ID of your device. If not, please go back and retrace your steps.
7. Now type:
adb shell
8. Use the following commands to find the apps you want to disable (replace 'amazon' with the manufacturer, i.e. 'samsung')
adb shell cmd package list packages | grep 'amazon
9. This should give you a new prompt, something to the effect of (device-model):/ - here type the following:
pm uninstall -k --user 0 <name of package>
This should return 'Success' at which point the package has been removed!
This has been tried on about half a dozen devices and it works on every single one, including the LG G6, Samsung S8, Google Pixel (Removed System Applications!)
Hope this helps folks out there that are looking to get as clean of an Android experience as possible, good luck!
And how to revert a single package removed with this method?
Please don't say factory reset. I mean, the package is there in the system partition. How I make it available to the user again?
Replying to my self and to the history. Xda user Vordx, found a proper way.
"adb shell cmd package install-existing <package name>"
Hi there
I fiddle largely with MTK based phones and when I tweak a phone, I normally only need ADB root access. So my general process has been to:
1. OEM Unlock the device
2. unpack the boot.img and change the default.prop values (ro.adb.secure etc) to allow ADB root access.
3. Use ADB to get temporary write access using adb Root, then ADB remount Rw. Then you can pull and push files.
However I have an MT8735b, Android 7.0, Alps based device that will simply not give me ADB root access. so when I run "adb remount rw" or any of the equivalent shell scripts you can use instead, it just won't give me write access.
So I heard that newer phones based on these chipsets and also ones like 6737M are locking the device up in other ways.
My question is, does anyone have any ideas or knows anything I could try to get root access?
Any help is much appreciated.
I have rooted my a52 5g with Magisk. Now I'm trying to make a backup through "adb backup". adb spits this line: "adbd cannot run as root in production builds".
I then change in "/system/build.props" "ro.debuggable=1"
Now i get from adb:
restarting adbd as root
timeout expired while waiting for device
I then type adb devices, and no devices are listed and the device does not show up under device manager in win10.
Also if i open developer options in android menu, it crashes.
And when i change the "ro.debuggable=1" back to "0" developer options works again.
Any idea what is causing this?
And is there another way of backing up the whole system?
I rly just wanted to back it up before i ran the debloater app.