Hi,
I have a Xiaomi Mi 9 with no screen (it is broken). I do not plan to replace the screen but I would like to know how to recycle that smartphone to use at least as Linux server.
Is there a way to boot using USB or fastboot a ROM that provides me a Linux shell (SSH... dropbear... )?
I do not want to drop to the bin a Snapdragon 855 with 6GB RAM.
If USB Debugging got enabled on this phone then you can access it by means of ADB, means you even can run any Android's shell command
Code:
adb devices
adb shell "<YOUR-SHELL-COMMAND-HERE>"
and also run complete shell scripts on the phone
Code:
adb devices
adb shell "mkdir -p -m666 /data/local/tmp"
adb push <YOUR-SHELL-SCRIPT-HERE> /data/local/tmp/
adb shell "chmod +x /data/local/tmp/<YOUR-SHELL-SCRIPT-HERE>"
adb shell "$(cat /data/local/tmp/<YOUR-SHELL-SCRIPT-HERE>); echo $?"
you can write script to get screenshot from your phone by adb (if adb was enabled before)
adb shell screencap -p /sdcard/screenshot[i].png
to download image to your pc
adb pull /sdcard/screenshot[i].png ~/Desktop/screenshot[i].png
then by using "scrpy app" to share you phone screen to your computer
GitHub - Genymobile/scrcpy: Display and control your Android device
Display and control your Android device. Contribute to Genymobile/scrcpy development by creating an account on GitHub.
github.com
You can also use wifi connection to share your screen (with adb wirless) [see link]
you can even unlock bootloader and enable usb-debugging with broken screen.
scrcpy requires special setting in MIUI developer options which is only available with bonded MI account, so you can just mirror the screen but don't control the phone. so once you got adb connected, enable adb over wifi for scrcpy and connect mouse via usb-otg. you can now fully control device. setup mi account, disable the security setting and use scrcpy via usb...
Related
I recently set up Ubuntu Karmic on my laptop's second hard drive, and I finished setting up Eclipse and the Android SDK yesterday. I set up ADB to work directly from the terminal without changing to the SDK Tools directory, and it works... kind of. I can get some ADB commands working, but most others won't. The only things that really work are "adb help" and "adb devices" at the moment. "adb install", "adb push" / "adb pull", and other similar commands seem to register, but then nothing happens after that- the terminal freezes, and inputting keys shows other characters. ]]^A and stuff like that. Can anyone help?
Ubuntu 9.10x64 adb works with sudo
$ sudo adb push...
I usually make sure the first adb command I use is sudo'd so it starts the daemon as root.
adb help - does not send any data to your droid. It's internal
adb device - shows which devices are on the USB bus.
The other adb command need to talk to the devices and depending on how your udev protections, device protections, and your personal group memberships are... it may not work.
sudo works for me always.
Ehud
In this guide I will show you how to use adb to move files to or from your device. Especially helpful if your device has MTP and you can't get it to work with mtpfs on GNU/Linux.
What do you need?
Computer with GNU/Linux.
Connection to the Internet.
The 32bit adb binary or the 64bit adb binary, they are added as attachment to this post. (1)
An Android phone with USB debugging on.
Steps:
Connect your phone with a USB cable to your computer. Make sure you have USB debugging on! (2) Put the adb binary in a folder where you can open a terminal. With the terminal open type:
Code:
./adb devices
Make sure it says something like this:
Code:
List of devices attached
XXXXXXXXXXXXXdevice
Now you know you properly connected your device type:
Code:
./adb pull /sdcard/
or
Code:
./adb push /sdcard/
More info on adb commands you can find here:
http://developer.android.com/tools/help/adb.html
(1): If you are using the Debian or Ubuntu distro (or another wich allows you to install *.deb files) you can install the 32- or 64 bit adb packages and use adb from every folder. Download them from the attachments. If you use this type adb instead of ./adb.
(2): Don't know how to turn on USB debugging? Go to settings, scroll down to the About phone menu item. Tap it and scroll down again to Build number and tap it many times! Then go to settings, and tap developer options and find the USB debugging option.
I hope this was helpful, but I think not, because I get no replies...
AW: [GUIDE] MTP doesn't work for you on GNU/Linux? Use adb.
http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html
I usually use sftp to transfer files. No cable and shell access included.
Sent from my GT-I9100 using xda app-developers app
If you want to copy lots of files, like your music collection or movies, wireless is not fast enough. That's why I use adb, because it's very fast.
Hi,
I'm trying to access ADB shell of a device (Samsung Galaxy s4 Mini LTE) where Androis 4.2 is installed.
Obviously it won't pass me because of missing public key on a device.
/adt-bundle-linux-x86_64-20140321/sdk/platform-tools $ ./adb devices
List of devices attached
x.x.x.138:5555 unauthorized
xxxx17d3 unauthorized
I have an access to ADB shell of a CWM installed on recovery partition and through that shell I'm able to access filesystem.
I have tried of: adb push ~/.android/adbkey.pub /data2/data/misc/adb
where /data2 is: mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data2
But this is not working.
Anything else I could try?
There are apps out there that let you control your device remotely. But these still depend on you being able to install and launch the program.Using a package called Screencast you can get the image from the screen on your computer. It runs on your computer and doesn’t need to be installed on the phone, but it will require a rooted phone.
The phone is rooted but I can not install any apps because I cannot access ADB shell nor use display because it is all black and no touchscreen is working. Not a single pixel is lit up on a screen.
Pixel just updated to 7.1.2 build 47K, running adb devices is not showing any phone connected. I am able to view and transfer files through the file manager, but none of the adb commands will work. My other older androids will display fine. Any ideas?
I have usb debugging enabled and connection type set to file transfer. Tried 2 different usb ports on ubuntu 16.10. It's the google store version for what it's worth.
adb version: Android Debug Bridge version 1.0.32
lsusb: Bus 002 Device 012: ID 1xxx:4xxx Google Inc. Nexus 4 (debug)
Sorry if there is another post for this, I searched and did not find an answer to this on my own.
@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:
Geeks Empire said:
@bdre
try to run adb as root
Code:
adb kill-server
sudo adb start-server
sudo adb devices
:good:
Click to expand...
Click to collapse
so turned out to be just a bad usb cable...
the one that came with the phone of course did not work
Good morning,
This is my first post so please be gentle. This forum was recommended to me by a friend.
I am looking for an application, or someone who could create an application that would block the ability to transfer files from Kruger&Matz tablets via a usb cable. Tablets are used for training purposes and we don't want participants to be able to download files to their computers.
If anyone knows of such an application and could recommend it (it may be paid), I would be grateful. If it doesn't exist, and someone here can create it, we'll pay for it.
If you need any specific details, I'll try to provide them. Unfortunately, I'm not an IT specialist, so it's hard for me to present all the data that may be needed at once.
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
xXx yYy said:
If tablets are rooted and USB Debugging enabled you simply disable USB services like MTP and ADB by means of ADB:
Code:
adb devices
adb shell "su -c 'setprop sys.usb.config ""'"
Click to expand...
Click to collapse
We can't root them, have you ever rooted this model?
Of course not because I'm using Google Pixel phones.