Hi everyone,
I am not a developer, i searched for finding how to make motorola xoom WIFI to connect with Huawei LTE 4G E392,
But i didn`t find.
So please if someone can help developing.
Here is what i found
zerox981 said:
This is the way I get my dongle (Vodafone K4605) working with the latest TeamEOS nightly wingray (84 atm ).
Tools I use:
WinSCP - http://winscp.net/eng/index.php
SSHdroid - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroid&hl=en
putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/
1) Download the latest development overlay from this thread:
http://forum.xda-developers.com/showthread.php?t=1513490
2) Delete the drivers you don't need from the zip file. (xoom_dev_overlay_v4.zip\data\local\lib\modules\).
For my needs it's enough to keep only the option.ko and usb_wwan.ko.
3) Flash the dev. overlay.
4) Install pppd, usb_modeswitch and chat binary
Now you need to install pppd, usbmodeswitch and the chat binary the kernel is missing. You can google them or use my 3gdongle.zip file with my configs.
Run sshdroid so you can ssh to your android device (or use adb shell etc.).
Connect to your andrid device with putty.
Then run
Code:
sysrw
so you can write to your system folder.
Copy the contents of the zip file in the root folder using WinSCP.
Add the execute permission on
/system/xbin/chat
/system/xbin/usb_modeswitch
/system/bin/pppd
/system/etc/ppp/ip-up
/system/etc/ppp/ip-down
(using WinSCP or with chattr via ssh)
5) Plug the dongle to your windows machine & using Vodafone windows application disable pin authentication. (You can let it enabled but you have to modify the gprs-connect-chat i guess).
6) Disable the CD-ROM mode (I think it's not required because we are using usb_modeswitch, but i did it a long time ago and I'm too lazy to enable it back).
Under Control Panel->Phone and Modem look in the Modems tab. There should be the COM port written in the "Attached To" column.
Using putty & connection type serial connect to your modem and disable the CD-ROM mode using the command
Code:
AT^SETPORT="A1;1,2,3"
You can also check if your modem is responding with the AT command (it should write back OK).
Using te ATI command you should get the modem information back.
ex:
Code:
Manufacturer: Vodafone (Huawei)
Model: K4605
Revision: 11.113.21.00.11
IMEI: 353148040378952
+GCAP: +CGSM,+DS,+ES
OK
7) Plug the modem into your android device. You can check if the necessary moodules are loaded with lsmod:
Code:
sh-4.1# lsmod
option 13380 0 - Live 0xbf016000
usb_wwan 8789 1 option, Live 0xbf00d000
8) Check the dmesg or use lsusb to get your devices vendor and product id
dmesg>
Code:
[ 1903.631599] usb 2-1: new high speed USB device number 3 using tegra-ehci
[ 1903.689362] usb 2-1: New USB device found, idVendor=12d1, idProduct=14c1
[ 1903.689606] usb 2-1: New USB device strings: Mfr=3, Product=2, SerialNumber=0
[ 1903.689739] usb 2-1: Product: Vodafone Mobile Broadband (Huawei)
[ 1903.689970] usb 2-1: Manufacturer: Vodafone Group (Huawei)
[ 1903.695541] scsi1 : usb-storage 2-1:1.0
[ 1904.701649] scsi 1:0:0:0: CD-ROM Vodafone CD ROM (Huawei) 2.31 PQ: 0 ANSI: 2
lsusb>
Code:
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 003: ID 12d1:14c1
9) Switch usb mode using usb_modeswitch and the config file for your device. In my case it's 12d1:14c1.
Code:
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
If the switch was succsessful you should see the correct productid now (in my case 14c6):
Code:
sh-4.1# lsusb
Bus 001 Device 001: ID 1d6b:0002
Bus 002 Device 001: ID 1d6b:0002
Bus 002 Device 005: ID 12d1:14c6
10) optional - K4605 or other unrecognized devices
After the modeswitch you should see your device under /dev/ttyUSB*. But with the K4605 we don't because option.ko doesn't know our device. So we need to call
Code:
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
and our device appears.
11) check if modem is responding:
Code:
cat /dev/ttyUSB0 & echo AT > /dev/ttyUSB0
You should get an OK.
12) Set the config files. If you installed my 3gdongle.zip file you will find my config files under /system/etc/ppp .
You have to edit the gprs-connect-chat file and the peers/gprs file.
I will not go into detail about this config files. There is a lot of information about it on xda forums and google should be your best friend too .
bonus) I use this scripts to enable and disable internet via my 3G dongle using the scriptmanager app (https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en)
01_init3g.sh - Run it after plugging the 3g dongle to your android device (k4605 specific)
Code:
# My modem Vodafone K4605 is unknown to option.ko so we manually add it
# you can delete this line if your modem is recognized by option.ko
echo "12d1 14c6" >/sys/bus/usb/drivers/option/module/drivers/usb-serial:option1/new_id
# switch modes with usb_modeswitch
usb_modeswitch -c /etc/usb_modeswitch.d/12d1_14c1
02_connect via 3g.sh - Connect to the internet (you have to wait 10-20sec after using init because the modem has to initialize first)
Code:
#!/system/bin/sh
#save old route & primary dns
OLDROUTE=`/system/xbin/netstat -r | /system/xbin/grep default | /system/xbin/awk '{print $2}' | /system/xbin/head -n1`
OLDDNS=`/system/bin/getprop net.dns1`
/system/xbin/echo $OLDROUTE > /data/ppp/ppp0.route;
/system/xbin/echo $OLDDNS >> /data/ppp/ppp0.route;
# just some logging for debugging. Can be removed :)
/system/bin/log -pw -t zeroxPPPD "OldRoute: $OLDROUTE"
/system/bin/log -pw -t zeroxPPPD "OldDNS: $OLDDNS"
#connect to the internet
pppd call gprs
03_restore wlan.sh - Disconnect the 3g dongle & restore WLAN
Code:
#!/system/bin/sh
# restore the old route & primary dns (you can extend the script to add the secondary dns..
OLDROUTE=`cat /data/ppp/ppp0.route | head -n1`
OLDDNS=`cat /data/ppp/ppp0.route | tail -n1`
/system/bin/setprop "net.dns1" "$OLDDNS"
/system/xbin/route add default gw $OLDROUTE dev wlan0
# delete the settings file
/system/xbin/rm /data/ppp/ppp*.route
Click to expand...
Click to collapse
here is the link for it (http://forum.xda-developers.com/showthread.php?t=1494891&page=4)
It's also in the latest source (http://git.kernel.org/?p=linux/kern...b;hb=9334c4c16e6fa80dc55865897337b49c1753f33b)
I also found this (https://github.com/DerArtem/huaweigeneric-ril).
PLEASE DEVELOPERS TAKE A LOOK INTO IT, if possible fro the source please build a kernel patch or script
thanks to zerox981
Related
I downloaded and installed the sdk manager, downloaded and installed the sdk packages, and rebooted. Since I rebooted, I haven't been able to start up the manager to update anything (I needed to update adb).
Why is this?
Swyped From My Mikrunny'd Superphone Using Magic (TapaTalk 2 Beta 5)
If you're running windows it could be possible that after installing the new ask tools that the filepath for adb was screwed up somehow.
Sent from my Incredible 2 using Tapatalk
disconnecktie said:
If you're running windows it could be possible that after installing the new ask tools that the filepath for adb was screwed up somehow.
Sent from my Incredible 2 using Tapatalk
Click to expand...
Click to collapse
How would I go about fixing it?
Here's what I'm getting:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tyler>adb
Android Debug Bridge version 1.0.29
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment 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
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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] [-s] <file> - push this package file to the device and i
nstall it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
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 th
e 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 u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\Users\Tyler>
Is this right?
Hey all,
So I was using my KF just fine with hashcode's AOSP Jelly Bean rom. That rom was on there for more than a month and then suddenly ,as of yesterday, adb refuses to connect. Fastboot on the other hand works just fine.
I'm running Debian Squeeze on and old Thinkpad R51. Both adb and fastboot binaries are in my PATH, and my 51-android.rules looks as follows...
Code:
# Amazon
SUBSYSTEM=="usb", ATTRS{idVendor}=="1949", MODE="0666", GROUP="plugdev"
# HTC
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
# Lenovo
SUBSYSTEM=="usb", ATTRS{idVendor}=="17ef", MODE="0666", GROUP="plugdev"
# Motorola
SUBSYSTEM=="usb", ATTRS{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
Running "adb kill-server" and then "adb devices" does not show the device at all. I switched to the jandykane rom and it's still the same. I'm currently in the stock amazon 6.3.1 rom and still I get nothing. I did a full /cache /data /system /sdcard wipe after installing each rom. Running "lsusb" I get...
Code:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 040: ID 1949:0006 Lab126
Bus 001 Device 002: ID 1058:1021 Western Digital Technologies, Inc. Elements 2TB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
And running "dmesg | tail" (only posted what is shown after I plug in the KF), I get...
Code:
[ 8851.136202] usb 1-4: new high speed USB device using ehci_hcd and address 40
[ 8851.269079] usb 1-4: New USB device found, idVendor=1949, idProduct=0006
[ 8851.269090] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 8851.269099] usb 1-4: Product: Kindle
[ 8851.269106] usb 1-4: Manufacturer: Amazon
[ 8851.269114] usb 1-4: SerialNumber: 1CDE000600000001
[ 8851.270544] usb 1-4: configuration #1 chosen from 1 choice
[ 8851.277370] scsi29 : SCSI emulation for USB Mass Storage devices
[ 8851.284978] usb-storage: device found at 40
[ 8851.284986] usb-storage: waiting for device to settle before scanning
[ 8856.290243] usb-storage: device scan complete
[ 8856.290897] scsi 29:0:0:0: Direct-Access Amazon Kindle 0001 PQ: 0 ANSI: 2
[ 8856.295474] sd 29:0:0:0: Attached scsi generic sg3 type 0
[ 8856.316198] sd 29:0:0:0: [sdc] Attached SCSI removable disk
I am able to do adb commands just fine on a Droid X2. The DX2 is shown in the device list and I can successfully send commands. I've used the same cable for both the DX2 and the KF. I've tried another working cable and still nothing. I can successfully use adbWireless to send commands. I even went as far as clean installing Debian Wheezy and setting up the udev rules for adb/fastboot access, and still no success.
Is there anything I can try to fix this problem. What could cause fastboot to work but not adb. My best guess is that it may be hardware failure.
Oh and one last thing, In hashcode's jelly bean rom, I was able to mount the sdcard partition when connected via usb to my computer. I could browse the drive and everything. It also works on the stock amazon 6.3.1 update.
Also, I've been using an adb and fastboot binary that has been compiled with the Amazon device id included in the source code (0x1949). I've been using those binaries for the longest without any problems but I don't know if they could have caused any hardware damage.
I noticed as well some changes in device id's . Make a backup and flash this http://forum.xda-developers.com/showthread.php?t=1778010 see if your adb doesn't again work just out of curiosity
Edit: some have complained about not having adb access after flashing JB but this I believe only existed on windows on Linux that should not have become a problem because of static drivers.
The problem seems to be my Thinkpad. I have no idea what happened to it considering USB mass storage mode and fastboot work perfectly fine. I've now plugged the KF to my desktop and I can see my device and am able to send commands via adb just fine. That's weird.
Stranger things have happened I would think more common to have no fastboot and have adb but yes that's strange
Hi guys. I have problem with update my phone to 4.3 because I have error.
Code:
Pushing system.ext4 to (this process will take a while)...
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment 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 [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
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 th
e 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 u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
-------------------------------------------------------------------------------
ERROR: failed to push some files, make sure you have enough free space then try
again. Press any key to exit
Quite obvious ol' chap, try freeing some space either on the computer or the phone.
Sorry if I am appearing a bit condescending to you.
I flash phone to 4.1.2 and root it and I format sd card. My computer is freshly after format so i have space on my phone and computer.
PS. Sorry for my english but I'm still learning the language because I'm from Poland kurwa mać!!
Ok make sure there are no other usb devices plugged into your computer at the same time, make sure you have full root, make sure you have busybox
Sent from my C2004 using xda app-developers app
I have full root for 100 % , To ports usb i have only connected mouse and keyboard. I installed busybox to do root but I uninstall when I finished rooting
ref
make sure you have full root access , i think that's the problem
Fikcyjny said:
I have full root for 100 %
Click to expand...
Click to collapse
Read this. I have full root, for example I uninstall systems apps (few at this same time) and I dont have restart
ref
adb isn't recognizing the push command and it's just displaying help instead. Which language are your OS? For debugging, open root.bat with notepad and remove the first line (@echo off), save and then run again. This time the console will show more details, copy all and post here so I can help...
Code:
C:\DOTELE~1\NICKIR~1>echo Pushing system.ext4 to (this process will take a whil
e)...
Pushing system.ext4 to (this process will take a while)...
C:\DOTELE~1\NICKIR~1>tools\adb.exe push system.ext4
Android Debug Bridge version 1.0.31
-d - directs command to the only connected USB devic
e
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 r
unning.
-s <specific device> - directs command to the device or emulator with
the given
serial number or qualifier. Overrides ANDROID_S
ERIAL
environment 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 [-l] - list all connected devices
('-l' will also list device qualifiers)
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments
will disconnect from all connected TCP/IP devic
es.
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
(-l means list but don't copy)
(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] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
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 backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)
adb restore <file> - restore device contents from the <file> backup
archive
adb help - show this help message
adb version - show version num
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 get-devpath - prints: <device-path>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
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 th
e 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 u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.
C:\DOTELE~1\NICKIR~1>if not 1 == 0 goto err_push
C:\DOTELE~1\NICKIR~1>echo ------------------------------------------------------
-------------------------
-------------------------------------------------------------------------------
C:\DOTELE~1\NICKIR~1>echo ERROR: failed to push some files, make sure you have e
nough free space then try again. Press any key to exit
ERROR: failed to push some files, make sure you have enough free space then try
again. Press any key to exit
C:\DOTELE~1\NICKIR~1>pause 1>nul
Language is Polish .
That's really weird, your command prompt is using paths in DOS style, which Windows version are you using? Meanwhile, try extracting the root tool in C:\ and rename the folder from "NickiRoot" to something very small, like "NR", then try again and see if works...
Make sure that other adb processes are not running. Like an android emulator...
Sometimes I have weird errors because I have installed BlueStacks.
Rename folder didn't work. I have Windows XP Proffessional
WOW, it's time to upgrade your OS (even Microsoft ended its support). If you're using NickiRoot 1.1 or newer, that's your problem. To cleanup my code I dropped a ugly workaround and the script won't work in Windows XP anymore. The last version compatible with it is NickiRoot 1.0.1, anything newer won't work in Windows XP and there's no reason I should care in supporting it anymore
I have same problem..
I'm using windows xp ..
Tried a few methods for getting root, none of which worked. I'm running a d851 with d85120g software. Ubuntu as my desktop. Here's a step by step pulled from various sources.
1. Put your phone in developer mode. Go to settings-->about phone. Click on build 8ish times until you see "you're a developer"
2. Go to settings-->developer options-->enable USB debugging
Now we need the desktop to recognize the phone
3. In your favorite text editor, you'll need to create a text file named /etc/udev/rules.d/51-android.rules
4. Copy this line into the file and save it:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666", GROUP="plugdev"
(Source here)
5. In a terminal:
Code:
sudo chmod a+r /etc/udev/rules.d/51-android.rules
6.
Code:
sudo service udev restart && sudo killall -9 adb
6a. Get this file and
Code:
sudo chmod a+r ./qcdlcomm.py
from that directory. (Source)
Next steps are modified from here.
7. Download and extract the zip file: http://bit.ly/1Ln9FKB .
7a. Move qcdlcomm.py to wherever you extracted the above file.
8. Connect your phone. At some point you can choose your USB connection type. Reports state it only works with PTP mode (v. MTP), but I didn't try MTP.
9. Terminal:
Code:
adb devices
You should see your phone listed. Then, in the same directory as the files from step 7:
10.
Code:
adb push ./busybox /data/local/tmp && adb push ./UPDATE-SuperSU-v2.46.zip /data/local/tmp
Now you want to get in download mode.
11. Unplug and turn off your phone, then hold volume up as you plug the cable back in. You should see "download" or something on the screen.
Next steps taken from here.
12.
Code:
ls /dev/ttyUSB*
Make note of the devices. You'll try the highest device number first in a few steps.
13.
Code:
sudo rmmod cdc_acm && sudo rmmod usbserial
You'll get an error if there's anything else using usbserial. If so, sudo rmmod that module, then rerun
Code:
sudo rmmod usbserial
14.
Code:
sudo modprobe usbserial vendor=0x1004 product=0x633e
15.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*< ./root
Replace the device with the output from step 12. Something should happen here. (BTW, at some point the phone screen says "flashing firmware" or something. There's a progress bar. It never moves past 0%"
16. Type "LEAVE" at the hash prompt that's left. At this point, your phone may not reboot. If not, type "exit" (or ctrl+c) and disconnect your phone. Then reconnect the phone.
17.
Code:
ls /dev/ttyUSB*
again. You may have lost a usb device. If so, repeat:
18.
Code:
sudo python ./qcdlcomm.py /dev/ttyUSB*
with the next highest device from above.
19. Type "LEAVE" again. Device should reboot. You should have root.
Some of this from memory, so if anyone has any suggestions, LMK. Hope this helps someone.
Good
Sent from my SM-G361H using Xposed Modules
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
slow64 said:
These instructions killed my phone....
All steps went absolutely fine, except that the phone refused to boot. After the fact I found other, similar, instructions that also tell you to push and run lg_root.sh.
Click to expand...
Click to collapse
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
nola mike said:
Well, I just got a new d851. This process was still harder than it should be. I had trouble at step 15; it never dropped me back to back to a hash prompt. I had the scary task of battery pulling/ctrl+c in the middle of the flash a couple of times, but no bricking. Also noticed a typo in my instructions, which took me a while to figure out. Those instructions wouldn't have worked as I originally posted them. Anyway, it worked again. Purple drake still didn't work, and there STILL doesn't appear to be an easy way to root on linux.
Click to expand...
Click to collapse
I notice my product ID differs from yours. Is this unimportant? I have been really wanting to get root on this for a while now, and this is the most promising looking aggregation of all available information I've found so far.
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
nola mike said:
Don't know why the product ID would be different (at least the vendor ID should be the same). What's your dmesg/lsusb output? It uses the ID to create the udev rules in step 4, so you'd need it correct there. In step 14 I don't know if it would work if you left the vendor info out and just did a modprobe usbserial.
Click to expand...
Click to collapse
I was thinking I'd just substitute my ProdID in the necessary locations.
dmesg:
Code:
[11036.082260] usb 3-2: new high-speed USB device number 10 using ehci-pci
lsusb:
Code:
[~]$ lsusb | grep LG
Bus 003 Device 010: ID 1004:631d LG Electronics, Inc. Optimus Android Phone (Camera/PTP Mode)
Sounds good, keep us updated.
Well, just got my third d851, running v30e firmware. Now doesn't work, getting stuck at step 15. When I plug in in download mode, the phone switches to the "firmware update" screen before I do anything. This is the dmesg output.
Code:
[ 6277.744082] usb 1-1: new high-speed USB device number 28 using ehci-pci
[ 6277.893938] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6277.893944] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6277.893948] usb 1-1: Product: LGE Android Phone
[ 6277.893950] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6277.893953] usb 1-1: SerialNumber: LGD8511199581b
[ 6277.894874] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6277.894890] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6277.895019] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6277.900634] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6277.900638] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6277.900641] usbserial_generic 1-1:1.2: generic converter detected
[ 6277.900827] usb 1-1: generic converter now attached to ttyUSB0
[ 6534.787683] usb 1-1: USB disconnect, device number 28
[ 6534.791136] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[ 6534.791175] usbserial_generic 1-1:1.2: device disconnected
[ 6550.456114] usb 1-1: new high-speed USB device number 29 using ehci-pci
[ 6550.605565] usb 1-1: New USB device found, idVendor=1004, idProduct=633a
[ 6550.605571] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 6550.605574] usb 1-1: Product: LGE Android Phone
[ 6550.605578] usb 1-1: Manufacturer: LG Electronics Inc.
[ 6550.605581] usb 1-1: SerialNumber: LGD8511199581b
[ 6550.606530] usbserial_generic 1-1:1.0: Generic device with no bulk out, not allowed.
[ 6550.606559] usbserial_generic: probe of 1-1:1.0 failed with error -5
[ 6550.606720] cdc_acm 1-1:1.0: ttyACM0: USB ACM device
[ 6550.612943] usbserial_generic 1-1:1.2: The "generic" usb-serial driver is only for testing and one-off prototypes.
[ 6550.612948] usbserial_generic 1-1:1.2: Tell [email protected] to add your device to a proper driver.
[ 6550.612951] usbserial_generic 1-1:1.2: generic converter detected
[ 6550.613624] usb 1-1: generic converter now attached to ttyUSB0
Locked me out of STDin on adb and and tty and changed my libfs64.so to another destination. So I'm running out of options.
adb pair 192.168.0.1:5037
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /data/user/0/com.github.standardadb/cache/adb.10600.log
Server had pid: 24563
--- adb starting (pid 24563) ---
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Version 31.0.3p1-android-tools
adb I 04-07 11:00:57 24563 24563 main.cpp:63] Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
adb I 04-07 11:00:57 24563 24563 main.cpp:63]
adb F 04-07 11:00:57 24549 24549 main.cpp:155] could not install *smartsocket* listener: Address already in use
adb F 04-07 11:00:57 24561 24561 main.cpp:155] could not install *smartsocket* listener: Address already in use
adb F 04-07 11:00:57 24563 24563 main.cpp:155] could not install *smartsocket* listener: Address already in use
* failed to start daemon
error: cannot connect to daemon
Enter pairing code:
adb
* daemon not running; starting now at tcp:5037
ADB server didn't ACK
Full server startup log: /data/user/0/com.github.standardadb/cache/adb.10600.log
Server had pid: 24734
--- adb starting (pid 24734) ---
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Android Debug Bridge version 1.0.41
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Version 31.0.3p1-android-tools
adb I 04-07 11:01:00 24734 24734 main.cpp:63] Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
adb I 04-07 11:01:00 24734 24734 main.cpp:63]
adb F 04-07 11:01:00 24734 24734 main.cpp:155] could not install *smartsocket* listener: Address already in use
* failed to start daemon
error: cannot connect to daemon
adb
Android Debug Bridge version 1.0.41
Version 31.0.3p1-android-tools
Installed as /data/app/~~x9Yjf_NXboB57BGltSn3LQ==/com.github.standardadb-5k6iLgDWIncOskTOBYobtQ==/lib/arm64/libfs64.so
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 (overrides $ANDROID_SERIAL)
-t ID use device with given transport id
-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]
general commands:
devices [-l] list connected devices (-l for long output)
help show this help message
version show version num
networking:
connect HOST[ORT] connect to a device via TCP/IP [default port=5555]
disconnect [HOST[ORT]]
disconnect from given TCP/IP device [default port=5555], or all
pair HOST[ORT] [PAIRING CODE]
pair with a device for secure TCP/IP communication
forward --list list all forward socket connections
forward [--no-rebind] LOCAL REMOTE
forward socket connection using:
tcp:<port> (<local> may be "tcp:0" to pick any open 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)
vsock:<CID>:<port> (remote only)
acceptfd:<fd> (listen only)
forward --remove LOCAL remove specific forward socket connection
forward --remove-all remove all forward socket connections
ppp TTY [PARAMETER...] run PPP over USB
reverse --list list all reverse socket connections from device
reverse [--no-rebind] REMOTE LOCAL
reverse socket connection using:
tcp:<port> (<remote> may be "tcp:0" to pick any open port)
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
reverse --remove REMOTE remove specific reverse socket connection
reverse --remove-all remove all reverse socket connections from device
mdns check check if mdns discovery is available
mdns services list all discovered services
file transfer:
push [--sync] [-z ALGORITHM] [-Z] LOCAL... REMOTE
copy local files/directories to device
--sync: only push files that are newer on the host than the device
-n: dry run: push files to device without storing to the filesystem
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
pull [-a] [-z ALGORITHM] [-Z] REMOTE... LOCAL
copy files/dirs from device
-a: preserve file timestamp and mode
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
sync [-l] [-z ALGORITHM] [-Z] [all|data|odm|oem|product|system|system_ext|vendor]
sync a local build from $ANDROID_PRODUCT_OUT to the device (default all)
-n: dry run: push files to device without storing to the filesystem
-l: list files that would be copied, but don't copy them
-z: enable compression with a specified algorithm (any, none, brotli)
-Z: disable compression
shell:
shell [-e ESCAPE] [-n] [-Tt] [-x] [COMMAND...]
run remote shell command (interactive shell if no command given)
-e: choose escape character, or "none"; default '~'
-n: don't read from stdin
-T: disable pty allocation
-t: allocate a pty if on a tty (-tt: force pty allocation)
-x: disable remote exit codes and stdout/stderr separation
emu COMMAND run emulator console command
app installation (see also `adb shell cmd package help`):
install [-lrtsdg] [--instant] PACKAGE
push a single package to the device and install it
install-multiple [-lrtsdpg] [--instant] PACKAGE...
push multiple APKs to the device for a single package and install them
install-multi-package [-lrtsdpg] [--instant] PACKAGE...
push one or more packages to the device and install them atomically
-r: replace existing application
-t: allow test packages
-d: allow version code downgrade (debuggable packages only)
-p: partial application install (install-multiple only)
-g: grant all runtime permissions
--abi ABI: override platform's default ABI
--instant: cause the app to be installed as an ephemeral install app
--no-streaming: always push APK to device and invoke Package Manager as separate steps
--streaming: force streaming APK directly into Package Manager
--fastdeploy: use fast deploy
--no-fastdeploy: prevent use of fast deploy
--force-agent: force update of deployment agent when using fast deploy
--date-check-agent: update deployment agent when local version is newer and using fast deploy
--version-check-agent: update deployment agent when local version has different version code and using fast deploy
--local-agent: locate agent files from local source build (instead of SDK location)
(See also `adb shell pm help` for more options.)
uninstall [-k] PACKAGE
remove this app package from the device
'-k': keep the data and cache directories
debugging:
bugreport [PATH]
write bugreport to given PATH [default=bugreport.zip];
if PATH is a directory, the bug report is saved in that directory.
devices that don't support zipped bug reports output to stdout.
jdwp list pids of processes hosting a JDWP transport
logcat show device log (logcat --help for more)
security:
disable-verity disable dm-verity checking on userdebug builds
enable-verity re-enable dm-verity checking on userdebug builds
keygen FILE
generate adb public/private key; private key stored in FILE,
scripting:
wait-for[-TRANSPORT]-STATE...
wait for device to be in a given state
STATE: device, recovery, rescue, sideload, bootloader, or disconnect
TRANSPORT: usb, local, or any [default=any]
get-state print offline | bootloader | device
get-serialno print <serial-number>
get-devpath print <device-path>
remount [-R]
remount partitions read-write. if a reboot is required, -R will
will automatically reboot the device.
reboot [bootloader|recovery|sideload|sideload-auto-reboot]
reboot the device; defaults to booting system image but
supports bootloader and recovery too. sideload reboots
into recovery and automatically starts sideload mode,
sideload-auto-reboot is the same but reboots after sideloading.
sideload OTAPACKAGE sideload the given full OTA package
root restart adbd with root permissions
unroot restart adbd without root permissions
usb restart adbd listening on USB
tcpip PORT restart adbd listening on TCP on PORT
internal debugging:
start-server ensure that there is a server running
kill-server kill the server if it is running
reconnect kick connection from host side to force reconnect
reconnect device kick connection from device side to force reconnect
reconnect offline reset offline/unauthorized devices to force reconnect
usb:
attach attach a detached USB device
detach detach from a USB device to allow use by other processes
environment variables:
$ADB_TRACE
comma-separated list of debug info to log:
all,adb,sockets,packets,rwx,usb,sync,sysdeps,transport,jdwp
$ADB_VENDOR_KEYS colon-separated list of keys (files or directories)
$ANDROID_SERIAL serial number to connect to (see -s)
$ANDROID_LOG_TAGS tags to be used by logcat (see logcat --help)
$ADB_LOCAL_TRANSPORT_MAX_PORT max emulator scan port (default 5585, 16 emus)
$ADB_MDNS_AUTO_CONNECT comma-separated list of mdns services to allow auto-connect (default adb-tls-conne
t0inK said:
Locked me out of STDin on adb and and tty and changed my libfs64.so to another destination. So I'm running out of options.
Click to expand...
Click to collapse
@t0inK Thread closed as duplicate of
Adb wont work. Lib64 moved. Wont read from stdin. Manifest overwrite, rewrite hack.
Here are the most important parts. Literally every command has been changed to lock me out from making ANY move possible to break free of this hacker . He's checked every back door. "reboot the device; defaults to booting system image but...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only ONCE! Thanks for your cooperation.
Regards
Oswald Boelcke
Senior Moderator