I am a Chinese Android fan and bought pixel2xl on a second-hand website. . I accidentally upgraded Android 9. I can open ome now, but can't unlock it in Bootloader mode. help me very thanks everybody love yours
Android Debug Bridge version 1.0.39
Revision 5943271ace17-android
Global options:
* -a listen on all network interfaces, not just localhost
* -d use USB device (error if multiple devices connected)
* -e use TCP/IP device (error if multiple TCP/IP devices available)
* -s SERIAL
***** Use device with given serial number (overrides $ANDROID_SERIAL)
* -p PRODUCT
***** Name or path ('angler'/'out/target/product/angler');
***** Default $ANDROID_PRODUCT_OUT
* -H name of adb server host [default=localhost]
* -P port of adb server [default=5037]
* -L SOCKET listen on given socket for adb server [default=tcp:localhost:5037]
Related
(Did I say Device bridge, oops. Android Debug Bridge)
So I'm trying to get some port forwarding happening - had a look at the forward function in the ADB; seems like it wont do UDP ports. Am I getting that right?
It says forward forwards socket connections (but isnt UDP a connectionless protocol?)
adb forward <local> <remote> check it below:
Code:
>adb
Android Debug Bridge version 1.0.25
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
envivornment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>:<port> - connect to a device via TCP/IP
disconnect <host>:<port> - disconnect from a TCP/IP device
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
If ADP cant set up port forwarding on the g1, what other ways can I go about it without using ADB?
I have use this on my win machine for testing apps
redir - Vdm-Redirector
redir add udp:<host machine port>:<emulator listen port>
example:
redir add udp:4444:4444
This will then have the emulator "listen" on your local machine's port
4444 for UDP packets, and forward those to the emulator's adapter
on port 4444
found this in the android-developers mailing list before
Finally found a way to get this usb 3g modem to work with android x86. Looks like there are significant differences in android kitkat, the other tutorials didn't work for me. Here's what i did in case somebody else finds it useful:
Model: Huawei E1752 HSPA USB Stick
Android x86 4.4.2 on Acer Netbook
Get modem to work under Ubuntu first so you have chat scripts that are known to work with your modem/provider. (If having trouble finding the right AT commands to initialize your modem you can record them under windows. Try free serial port monitor)
Install PPP Widget. It doesn't work, but that gives us usb_modeswitch and pppd to play with.
Install busybox if you don't have it already. Your device should be rooted.
I disabled modem's cdrom mode so that i wouldn't have to modeswitch it with PPP Widget every time (did it from linux)
http://ma.juii.net/blog/disable-usb-mode-switching
Tweak and install pppd/chat scripts for your provider:
/sdcard/pppwidget/ppp/free-chat
Chat script to initiate connection. Change AT commands and dial number (*99#) if yours differ.
Code:
ABORT BUSY
ABORT 'NO CARRIER'
ABORT 'NO ANSWER'
ABORT DELAYED
REPORT CONNECT
TIMEOUT 2
"" AT
OK-AT-OK AT&FE0V1X1&D2&C1S0=0
OK-AT-OK AT
OK-AT-OK ATS0=0
OK-AT-OK AT
OK-AT-OK AT&FE0V1X1&D2&C1S0=0
OK-AT-OK AT
OK ATDT*99#
TIMEOUT 30
CONNECT ''
SAY '\rReport from chat:\r'
/sdcard/pppwidget/ppp/peers/free
pppd config file
Code:
#/etc/ppp/peers/free
# Usage: root>pppd call free
ttyUSB0
3600000
crtscts
connect '/data/data/de.draisberghof.pppwidget/app_bin/chat -v -f /sdcard/pppwidget/ppp/free-chat'
noauth
defaultroute
usehostname
user fooooooo
noipdefault
usepeerdns
idle 0
/sdcard/3gmodem/connect
script to start connection
Code:
#!/system/bin/sh
pppd call free
# use own DNS (OpenDNS)
ndc resolver setifdns ppp0 208.67.222.222 208.67.222.220
ndc resolver setdefaultif ppp0
To connect, open a terminal and type:
Code:
$ su
# cd /sdcard/3gmodem
# ./connect
Now you're connected. browser should work now.
Connection is there but android doesn't know about it, so apps like play store which check connectivity will think you're offline. Install Fake Wifi Connection to deal with those.
Done !
how to get chat script for other modem
Hello, Can I use your chat script with Huawei E3531, and replace only the AT commands?
Do I need busybox?
I have no knowledge of commands, just very basic commands on android terminal.
I am having a really hard time to connect to internet, mainly because Broadcom BCM43142 wifi is not compatible with android 9.0-r2, and older versions.
Thank you
Hello ,
I have 2 rooted Android phones , I downloaded Droidsshd on both running on port 22 with password , I want to allow passwordless ssh between the 2 phones
I generated the key using the following cmd:
Code:
/data/data/br.com.bott.droidsshd/files/bin/dropbearkey -t rsa -f /.ssh/id_rsa.pub
and copied the key to the other device
Code:
cat .ssh/id_rsa.pub | ssh -p port ip "cat - > /mnt/sdcard/.key"
and Added it to the other device authorized_keys
Code:
cat .ssh/id_rsa.pub>>.ssh/authorized_keys
the I uploaded the key on the Droidsshd APP but still asks for password .. do you have any suggestions on how to setup a passwordless ssh between 2 Android phones
Hi Guys,
My phone's screen has broken and I can't see anything, although the touch still works. I have been able to connect it to the PC to take my music and photos off the internal storage, and my contacts are backed up to Google, but my texts are not and I'd like to recover them.
I've read that they normally reside in /data/data/com.android.providers.telephony/databases/mmssms.db and I should be able to pull this via ADB.
When the phone is booted to the OS it is not detected by ADB at all with 'error: device not found'. I thought USB debugging was on, but obviously not. I can boot to recovery (custom CWM) and now adb will connect to the device. However, when I try to pull the sms db I get 'No such file or directory'
Code:
[email protected] ~ $ sudo adb start-server
[sudo] password for james:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected] ~ $ adb shell
error: device not found
[email protected] ~ $ adb devices
List of devices attached
[email protected] ~ $ adb devices
List of devices attached
CB5122TH5B device
[email protected] ~ $ adb shell
~ # mkdir /mnt/sdcard/tmp
~ # cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
~ # su cat /data/data/com.android.providers.telephony/databases/mmssms.db > /mnt/sdcard/tmp/mmssms.db
cat: can't open '/data/data/com.android.providers.telephony/databases/mmssms.db': No such file or directory
/sbin/sh: su: not found
~ # exit
[email protected] ~ $ adb pull su /data/data/com.android.providers.telephony/databases/mmssms.db
remote object 'su' does not exist
~ # ls /data
~ #
It would appear the directory /data is empty but I bet that's because I don't have permissions to view the contents. I'm guessing this is also why su is not found.
Can anyone help me to get over this hurdle? Please bear in mind I'm not familiar with ADB and not great in a Linux shell either; the above commands took a bit of reading to find, but I do understand what they're trying to do.
My phone is a Sony Xperia T LT30p and is rooted running Xperiment 3.5 and Clockworkmod recovery 6.0.4.6 and I'm running ABD on Linux.
Any help would be appreciated! Cheers :good:
I am using adb version 1.0.32 on an armv7l development board. In an attempt to use scrcpy to connect remotely to the adb I first set:
on the armv7l remote board:
adb kill-server
adb -a nodaemon server start
then from another terminal on the remote board try doing a "adb devices" to make sure it sees the connected android device but what happens is unexpected I get:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
with no devices showing up. It is lighting off a completely new adb server and ignoring the fact that it is already running.
ps shows
1304 root 30184 S adb -a nodaemon server start
1315 root 20964 S adb -P 5037 fork-server server
If I don't have the first adb running and do "adb devices"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
001e06481bc3 device
I tried this same scenario on my ubuntu 18.04 box with adb 1.0.32 and had no problem with "adb devices" launching an extra process:
ps only shows
xxx 18322 10891 0 16:49 pts/2 00:00:00 adb -a nodaemon server start
and adb devices shows:
List of devices attached
001e064809ac device
without the extra daemon getting launched.
This is causing scrcpy to not function properly when I am trying:
export ADB_SERVER_SOCKET=tcp:<ip of remote board>:5037
scrcpy --tunnel-host=<ip of remote board>
it returns :
scrcpy 1.23 <https://github.com/Genymobile/scrcpy>
INFO: Tunnel host/port is set, --force-adb-forward automatically enabled.
ERROR: Could not find any ADB device
ERROR: Server connection failed
naturally it couldn't find any devices because "adb devices" is not working properly on the remote board. Incidently I tried the same scenario with just the localhost and it works flawlessly.
The question is why is the same version adb not working on one platform vs another?