If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
https://play.google.com/store/apps/details?id=fme.adb
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
No need for multiple threads on same topic,
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
I'll close this one.
Darth
Forum Moderator
Related
I'm trying to get my computer set up for when my Nexus 6 arrives so that I can just flash the factory images onto it as sort of a learning experience. I'm using my 2014 Moto X Pure (XT1095) to try to get it to be recognized in Terminal using ./adb devices but it just keeps returning permission denied. I have USB debugging enabled and I'm following TechnoBuffalo's guide on YouTube but I can't seem to get it to work.
I'm using a 2014 Moto X Pure Edition (XT1095), stock, unrooted 5.1.1, 2015 rMBP OS X El Capitan 10.11.1, both Android Studio and Standalone Android SDK Tools installed with all of the tools and packages installed.
Update: Today I uninstalled Android Studio, all SDK files, and then reinstalled just the Standalone tools (Android 6.0 tools and the entire Platform Tools package) and after changing the directory and running ./adb devices, it is still returning this: "-bash: ./adb: Permission denied" every single time. I can't do anything with su or sudo commands because it keeps returning "su: sorry" after I type my admin password. I really can't do anything because it looks as if I have no permissions on my own computer. Is there any way I can gain root/super user privileges on my computer so I can use ADB/Fastboot?
Hi,
Here are a few threads about ADB,
Beginner’s Guide to the Android Debug Bridge
[GUIDE] ADB Workshop and Guide for everyone
[GUIDE] ADB For Beginners (Setup, Use, and More!)
[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.2
[TOOL]Minimal ADB and Fastboot [11-6-14]
I think your system is read only at the moment, and ADB will not work if so.
You can ask in one of the above threads if you still have issues. But read the first couple posts of each one, and it may help you.
Good luck!
If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
LordFME said:
If you're looking to skip the Chinese invading your privacy, or not having to start up a PC just to use ADB you should try MTK ADB which gives you full ADB on your MediaTek device running Android 4.x. This was made to prevent the rooting process that clogs your phone with so many weird files that a total unroot is near impossible, resulting in a brick if you mess with the wrong binary or update your device which is actually really easy now that root apps replace system binaries with theirs to persist root when the binary gets run by init. MTK ADB makes no change to your device files whatsoever. It also allows you to get Root ADB on some devices (about 2 in 5, depending on manufacturer), all devices can get Shell access (Regular ADB).
https://play.google.com/store/apps/details?id=fme.adb
http://www.youtube.com/watch?v=_bt8BVaDCf0
https://slaycode.WordPress.com
Click to expand...
Click to collapse
This is useful. Thanks :good:
Glad you like it
No need for multiple threads on same topic,
http://forum.xda-developers.com/android/software-hacking/app-mtk-adb-adb-directly-device-t3313315
I'll close this one.
Darth
Forum Moderator
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://www.youtube.com/watch?v=_bt8BVaDCf0
http://slaycode.WordPress.com
Bump
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
Proof:
http://forum.xda-developers.com/gen...iled-error-t3191150/post62611445#post62611445
More Proof:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546/page10
When I open the app it opens but it doesn't work when I enter the commands and moreover the app when I try to start the adb it says unsupported device
Am using infinix hot 4 pro running NOUGAT xos 2.2
LordFME said:
MTK ADB gets you a privileged shell at the push of a button, allowing you to run commands directly on your MediaTek device. Some might wonder if rooting hasn't already solved this. Firstly, root access is persisted by modifying system files. When the real binary gets substituted by that of the root app's, if the device is rebooted, the init daemon running as root runs the binary giving the app root. What's wrong with this? If you have “purist” tendencies, you probably would want your phone as stock as possible, or at least with your permission. Sadly, not only binaries are dumped. Extra temp files, logs and helper binaries too, that manually removing them is like dancing on floor of pins and a prick means a brick. Not only that, consider yourself blocked from updates. If you're unfortunate enough, an update could result in bricking your phone as the files supposed to be present had been changed. This is more common than you think. MTK ADB makes no changes to your files whatsoever. Also, there's the matter of security/privacy. Root apps tend to always do something in the background. Either sneaking in a new app, or phoning home with your private data, or both. MTK ADB doesn't steal your data. The Internet permission is for Telnet, etc. On some devices, MTK ADB can get root access (depending on manufacturer) while all devices can get shell access. You just have to check which yours belongs.
IMPORTANT
•Refresh before (and after) clicking Start to check ADB status.
•Supports all ADB functionality. Just run "adb <command>" eg "adb pull" (without quotes).
•The minimalist terminal is for those who haven't any. Feel free to use your regular terminal (I use Terminal IDE) and keyboard (Hacker's Keyboard is really good). Just run "adb shell" on it.
•You can connect to your device using another phone, PC, or anything with a terminal and in the same network by running "adb connect IP_address".
•If you get a " device offline" error, disable and enable USB debugging. Next time connect to the network before running the app.
http://slaycode.WordPress.com
Click to expand...
Click to collapse
Are you familiar with an APK that utilizes mtk_bypass to directly flash firmware to device.
I'm looking for an APK that basically does what sp flash tool does because I don't have a computer.
A friend of mine has a Stylo 6 that says corrupted when it boots. It is however already set to USB debugging. However, I do not have access where I'm at to a PC or a Chromebook to install the dev tools. Is it possible even with third party paid software to install the dev environment on another Android phone and use it for fastboot etc?
You don't need to add ADB and/or Fastboot to any Android device. In common both ADB and Fastboot ( the latter only unless OEM decided to omit it ) are integral part of every Android release: ADB is housed in Android's user-space, Fastboot typically is part of device's bootloader unless Android has a Dynamic Partition layout, then Fastboot is also housed in Android's user space.
Ok, I guess what I need to know if I can install and use adb server on an Android device. I don't have access to a PC Mac or Chromebook to install the sdk tools. Can this be installed on my phone ( using a Linux or windows emulator maybe) to use to fix his phone?
ADB is nothing more than a tool that allows you to execute commands which would interact with Android shell. So you can install / open in Android a shell app ( e.g. Termux ) and run the commands ( Linux compliant ) therein. Will say you don't need a computer to operate on Android system of device,
To make this a short as possible I successfully unlocked my Motorola G7 power using an Android device rather than a PC I need help rooting my G7 power with magisk using my designated Android device rather than a PC
ADB⚡OTG - Android Debug Bridge - Apps on Google Play
⚡ Run ADB commands without a computer [No Need ROOT] ⚡
play.google.com
Thank you I appreciate your reply but I use another application for this purpose bugjaeger premium
@Sativa33
Either in magisk manager from device or you can also get the magisk module from Osm0sis' Odds and Ends- (multiple devices scripts) XDA thread. If you go there https://forum.xda-developers.com/t/...-and-ends-multiple-devices-platforms.2239421/
Scroll down halfway oe maybe 2/3 of fge way and click his "adb and fastboot " magisk module and install via magisk manager. Then use termux terminal and type "su" (enter) for root and place files you wish to install in ter
Termux's directory which it will show you after you tape sy and push enter on the screen in terminal just after you grant it root. Then you use an otg cable and connect two Android devices together throw files in Termux's directory and send fastboot and adb commands whenever. I've used this method on two phones so unlock my bootloader ad well. The only prerequisite being you need another (2nd) Android device that is bporloader unlocked and rooted so you can send commands to other device and an OTG cable which are $3-5 USD online. Sure does come in handy when you need it through. Like years ago when my laptop was stollen!! Life saver FR!!!
After reading it that sounds like a reasonable option. But wouldn't it be easier just to download the bugjaeger premium app on a second Android device. And that's basically all you need and a double ended USB c cord. No need for all this other programs or downloades . It's basically running fast boot commands it's purest form one Android device talking to the other using the same language no need to download packets drivers nothing because you're already in the Android shell talking to another Android