I have a stock factory ROM, ROOTED, MAXX HD. It's on the latest firmware pushed by VZW. After rooting, I had removed a bunch of apk's I knew I wouldn't need. The problem happened when I did a factory reset due to some minor GPS issues. I had forgotten that I removed the Setup.apk. (Yes I'm kicking myself regarding backups... but too late now).
Now my MAXX HD has no launcher. It states the Setup Wizard has stopped working. I have no access to files or applications. I can access the notification bar and the systems menu and such and can see the standard programs running under APPS. Wifi works, etc. I even signed into my gmail accounts, but I don't have access to any apps. Pressing the home button does nothing except bring up the error message again.
I've been trying to use ADB to push the missing files into the /system/app folder and that is described below. If anyone has any other ideas on what I can do, I'm all ears.
This part is for those that know a thing or two about ADB. I'm a noob at this so please correct away!
So, my ADB exploits... I've tried to push the setup files to /system/app via adb but have had no luck. I keep coming across access denied or this action is not allowed in production phone, etc.
The commands I've used are:
adb push setup.apk /system/app/setup.apk (This just gives the copy protected blah blah)
remount and root don't work.
in shell, when I type "su" the "$" does change to "#"
I've remounted the system as rw but pushing the file still gives me a not allowed value.
I'm just going to list the commands I've used now. If anyone has any suggestions or if I'm doing it wrong, please correct away. Thanks!
adb shell (this gives me a @Vanquish:/ $)
su (this changes the $ to a #)
mount | gret system (this gives me a long device-system name. it indicates it is now rw. it was originally ro)
mount -o rw, remount <device name from the previous command> /system
exit
exit (back to C:/adb)
adb push setup.apk /system/app/setup.apk (still says not allowed) (the root and remount commands still don't work)
I read that I need to type in "adb shell su push..." but I cannot get that command line to work at all.
Any help is extremely appreciated. Thanks!
Solved it myself
I guess I need to brush up on my ADB.
I got it to work by pushing the files to /sdcard/, then in shell, used # cp /sdcard/<file> /system/app/<file>
To all the ADB guys out there, how could I have done this in 1 step? I definitely don't have the syntax down.
T0ked said:
I guess I need to brush up on my ADB.
I got it to work by pushing the files to /sdcard/, then in shell, used # cp /sdcard/<file> /system/app/<file>
To all the ADB guys out there, how could I have done this in 1 step? I definitely don't have the syntax down.
Click to expand...
Click to collapse
Android Debug Bridge
-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
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
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.
Related
ok.
i run adb through cmd.
but it doesn't work, i can't enter any commands.
i'm a noob.
sorry.
-Ernest.
Open your cmd window and just run adb without any arguments. It will give you a list of possible arguments and their usages. The most important two would be adb install and adb shell. With adb install, you can install a package, and with adb shell you get an interactive shell access to Dream's filesystem. Here is a part of the help listing from sdk 1.5-pre's adb:
Code:
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
when i try to run a command it says.
"'adb' is not recognized as an internal or external command, operable program or batch file"
Whatever folder you put adb in is not in your system's PATH. In order to run a program not in your current working directory without specifying its absolute location, that location has to be one of the ones specified in the PATH. Let's say for example you put adb.exe and adbwinapi.dll in c:\ When you type cmd in XP, by default it will open a prompt at c:\Documents and Settings\%username%\. If you now type adb, the os will look for a file called adb.exe or adb.bat or adb.com in the Documents and Settings folder. Since you placed the file in a different folder, it will give you an error. You have two options:
A. Type c:\adb.exe every time you want to run adb
B. Add c:\ (or whatever directory adb is in) to the PATH. Here is a quick tut on how to do that.
C. Move adb.exe and adbwinapi.dll to c:\Documents and Settings\%username%\
To a programmer or experienced computer user, A would be a stupid method, B would be the proper method, and C would be a hacky or dirty method.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Admin>"C:\Documents and Settings\Admin\Desktop\G1 Deve
lopment\android-sdk-windows-1.0_r2\tools\adb.exe"
Android Debug Bridge version 1.0.20
-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
-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
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 instal
l 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-product - prints: <product-id>
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
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP 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.
C:\Documents and Settings\Admin>adb shell
'adb' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\Admin>
this is what i get.
The first time you executed it with the full path, which is correct. However, the second time you didn't. If you are going to execute it with the full path then you have to do it every single time. Alternately, type cd c:\Documents and Settings\Admin\Desktop\android-sdk-windows-1.0_r2\tools\ then you can do whatever you want without specifying the full path (because the executable is now in your working directory)
i specified the path.
in Enviorment Variables.
but it doesn't work in cmd.
m00b3rt said:
i specified the path.
in Enviorment Variables.
but it doesn't work in cmd.
Click to expand...
Click to collapse
After changing PATH you need to reboot too.
oh. ok.
Thanks.
i'll try this tommorow.
i have school.
lol.
So I used his new recovery and I had my zip files on my sd card... wiped everything and come to find out that it doesn't read external sd card. How can I mount the internal sdcard so I can put something on it?
You can use adb to push your files to either /sdard/ or /data/media (???)
gee one said:
You can use adb to push your files to either /sdard/ or /data/media (???)
Click to expand...
Click to collapse
Mind throwing me a walkthrough for adb? its been since july since I rooted and haven't used any of adb/nvflash stuff
bukithd said:
Mind throwing me a walkthrough for adb? its been since july since I rooted and haven't used any of adb/nvflash stuff
Click to expand...
Click to collapse
Do you have an SBK v1 TF to use NVFlash? (Serial # of your TF?)
This is a good thread to set up ADB
http://forum.xda-developers.com/showthread.php?t=1071584
Just hoping that you can get it working after the fact, is your USB debugging turn ON?
If you type adb, you'll get this:
Code:
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.
You want to "push" your zip ie "adb push /your/rom.zip /sdcard/" or maybe the last argument is /data/media - I flash from the external sdcard, so take this for what it's worth. Good luck.
baseballfanz said:
Do you have an SBK v1 TF to use NVFlash? (Serial # of your TF?)
This is a good thread to set up ADB
http://forum.xda-developers.com/showthread.php?t=1071584
Just hoping that you can get it working after the fact, is your USB debugging turn ON?
Click to expand...
Click to collapse
I have an older tf B50 I'm pretty sure but I'll just do this through adb and be done with it. I need to learn something new anyways...
bukithd said:
I have an older tf B50 I'm pretty sure but I'll just do this through adb and be done with it. I need to learn something new anyways...
Click to expand...
Click to collapse
That's good you have a B50, it's NVFlash compatible.
Do what gee one posted and see if you can push the ROM file to internal.
bukithd said:
I have an older tf B50 I'm pretty sure but I'll just do this through adb and be done with it. I need to learn something new anyways...
Click to expand...
Click to collapse
screw it, I'm nvflashing prime so I don't have t deal with this all night
My device screen cracked and killed the digitizer. The LCD is fine but I obviously can't interact with it. The device is fully encrypted, and while I have the password, I seem to have no way to unlock it (I don't have an MHL dongle to run a mouse). I'm sending the device back to LG for factory repair, but I'd like to make a full backup before I do. I thought this would be trivial with ADB but I can't seem to get things working and my suspicion is the device encryption is my problem. I'm running TWRP (I tried cwm first but couldn't get that to read by already-encrypted device, which I hear is a know issue somehow 4.2.2 related - I gave up caring about that when TWRP "just worked").
Anyway, what's the process to get a full backup? I've tried following the good tutorial on 'thesuperusersguide' (sorry I'm new xda-dev so I can't post the proper link) but the backup command get's ignored (see scrollback, below). My gut says there's something I need to send to my device to mount the encrypted partition, either a command or adb push a special file then reboot. Am I on the right track?
I thought this was supposed to be as simple as "plug in the device, make sure ADB can see it, then run ADB backup". Obviously I need a some cmdline args to get the backup to get all my data - that's not what I'm asking about. I'm asking the "previous step" that could be paraphrased as, "how to get adb backup to do *anything*?"
Code:
host:platform-tools user$ ./adb devices
List of devices attached
006854cc1d8e2d9e recovery
host:platform-tools user$ ./adb backup
Android Debug Bridge version 1.0.31
-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 <specific device> - directs command to the device or emulator with the given
serial number or qualifier. Overrides ANDROID_SERIAL
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 devices.
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 install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal 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|-nosystem] [<packages...>]
- write an archive of the device's data to <file>.
If no -f option is supplied then the data is written
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 default is noshared.)
(-all means to back up all installed applications)
(-system|-nosystem toggles whether -all automatically includes
system applications; the default is to include system apps)
(<packages...> is the list of applications to be backed up. If
the -all or -shared flags are passed, then the package
list is optional. Applications explicitly given on the
command line will be included even if -nosystem 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 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 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 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.
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 priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
host:platform-tools user$
FWIW this is a Nexus 4 running 4.2.2 rooted cm-10.1-20130304-EXPERIMENTAL-mako-M2 TWRP 2.4.4.0.
Feel free to link me to other threads. I tried both forum search and Google and really couldn't find anything useful to my cause. Also, thanks everyone!
AW: How to perform full backup using ADB w/o touchscreen on PIN locked device (rooted
What about flashing a non touch recovery via adb?
I don't know whether there are some for the n4 since it is a very new device but for my HTC Desire there are some you can control via volume and power buttons.
Tapatalked with my JellyBean powered HTC Desire
I was following this thread http://forum.xda-developers.com/showthread.php?t=2221039
But from the 6th step igot kinda stuck this is a screen shot of my cmd
c:\ace-tools>adb shell
$ su
su
# exit
exit
$ exit
exit
c:\ace-tools>adb push boot.img\data\local\temp
Android Debug Bridge version 1.0.26
-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 ocmmand 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 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 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:\ace-tools>
Risay143 said:
I was following this thread http://forum.xda-developers.com/showthread.php?t=2221039
But from the 6th step igot kinda stuck this is a screen shot of my cmd
c:\ace-tools>adb shell
$ su
su
# exit
exit
$ exit
exit
c:\ace-tools>adb push boot.img\data\local\temp
Android Debug Bridge version 1.0.26
-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 ocmmand 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 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 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:\ace-tools>
Click to expand...
Click to collapse
i believe the person who worked on the ACE tools for the Desire HD and the inspire 4g was getting angry at people that were whining about something cant remember it was a long time ago when i rooted my inspire xD sooo is it S-off right now? to gain root nowadays is to unlock the bootloader. try here http://forum.xda-developers.com/showthread.php?t=2168500
Hello everyone, my name is Massimiliano, I'm Italian and I have a problem with my MWG409, I modified the build.prop (but luckily I have a backup) and now the phone is in bootloop I can get into the stock recovery, but I have a problem the phone considers the internal memory Esternal like that and I do not know how to solve. thanks in advance
bamcam92 said:
Hello everyone, my name is Massimiliano, I'm Italian and I have a problem with my MWG409, I modified the build.prop (but luckily I have a backup) and now the phone is in bootloop I can get into the stock recovery, but I have a problem the phone considers the internal memory Esternal like that and I do not know how to solve. thanks in advance
Click to expand...
Click to collapse
Hi,
Can you see your Excite MGWG409 when you connect it to your PC and can you use cmd line commands.
if yes, use it and especially those are red => adb reboot
Code:
ode:
C:\Users>adb /?
Android Debug Bridge version 1.0.26
-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 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
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] [-s] <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)
('-s' means install on SD card instead of internal 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 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
[COLOR="Red"][B] adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program[/B][/COLOR]
[B][COLOR="Red"]adb reboot-bootloader - reboots the device into the bootloader[/COLOR][/B]
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 partitionis updated.
philos64 said:
Hi,
Can you see your Excite MGWG409 when you connect it to your PC and can you use cmd line commands.
if yes, use it and especially those are red => adb reboot
Code:
ode:
C:\Users>adb /?
Android Debug Bridge version 1.0.26
-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 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
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] [-s] <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)
('-s' means install on SD card instead of internal 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 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
[COLOR="Red"][B] adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program[/B][/COLOR]
[B][COLOR="Red"]adb reboot-bootloader - reboots the device into the bootloader[/COLOR][/B]
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 partitionis updated.
Click to expand...
Click to collapse
On ADB appears an error when i use sideload "installation aborted" help i need my phone
Please you don't need to post several OP for your problem.
You have already opened an OP and I gave you an answer.
You do not need to open an another OP because your old one is no longer on the first page.
If someone can give you an answer, he will answer
And if I remember its' not:
Code:
adb push update.zip \ sdcard \
but its
Code:
adb push update.zip/sdcard
Thanks in advance for your comprehension
philos64 said:
Please you don't need to post several OP for your problem.
You have already opened an OP and I gave you an answer.
You do not need to open an another OP because your old one is no longer on the first page.
If someone can give you an answer, he will answer
And if I remember its' not:
Code:
adb push update.zip \ sdcard \
but its
Code:
adb push update.zip/sdcard
Thanks in advance for your comprehension
Click to expand...
Click to collapse
sorry, but I am very worried about the phone, however only works in adb sideload, in other ways it appears "error: closed", in sideload tells me installation aborted when I go to install my "update.zip" that contains the build.prop I need to replace, maybe I created the wrong "update.zip"
bamcam92 said:
sorry, but I am very worried about the phone, however only works in adb sideload, in other ways it appears "error: closed", in sideload tells me installation aborted when I go to install my "update.zip" that contains the build.prop I need to replace, maybe I created the wrong "update.zip"
Click to expand...
Click to collapse
Go to your recovery
Code:
adb shell
mount -o remount,rw /system
this mounts your /system partition to read and writable extract the build.prop from your update.zip and paste it in desktop
Code:
cd desktop
adb push build.prop /system/build.prop
This should push the build.prop from update.zip right back to system
Regards
MasterAwesome