Hello. Please forgive my bad English. My Asus ZE500KL phone with Android 6, almost died. I have collected various things in it, phones, notes, passwords... and I had the stupidity of not having any backup. Sometimes it starts, but it throws up countless signs like "Unfortunately com.android.XXX Has Stopped". To do anything with the phone I have to be able to close them and I have very little time, it can be used and restarted in seconds. It behaves similarly in safe mode. Otherwise, it enters fastboot mode and adb, but I don't know how it got stuck there. Any ideas what I can do? A week ago I installed "SWAP no root", could it be from that?
Do a LOGCAT to get the very reason why you get this notification.
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
jwoegerbauer said:
Do a LOGCAT to get the very reason why you get this notification.
Click to expand...
Click to collapse
E:\platform-tools>adb devices
List of devices attached
G6AZCY00W177EUE recovery
E:\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
E:\platform-tools>adb logcat
adb server version (32) doesn't match this client (41); killing...
* daemon started successfully
- waiting for device -
* daemon still not running
error: cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: N
o connection could be made because the target machine actively refused it. (1006
1)
aIecxs said:
logcat is first thing you should do. you can redirect > into file and upload here
Code:
adb logcat '*:W' -b all > logcat.txt
try to uninstall some recent apps from adb maybe it stabilizes. the -k flag preserves app data
Code:
adb shell 'pm list packages -e'
adb shell 'pm uninstall --user 0 -k <pkgname>'
if you don't close any of that pop-up is phone rebooting anyway? if stable enough you can do backup and pull files (confirm blank no password)
Code:
adb pull -a /sdcard
adb backup -apk -shared -all
Click to expand...
Click to collapse
logcat.txt is empty
do this in android, not recovery
aIecxs said:
do this in android, not recovery
Click to expand...
Click to collapse
If I to load Android, the phone works for 20-30 seconds maximum and when I plug in the USB cable, it restarts immediately.
let usb plugged and adb logcat waiting while phone boots
Related
I adb pushed some .apks from a Froyo zip onto my mytouch1.2 but they didnt work...
when I try to uninstall them I get a failure message... and when I try adb shell... blah blah blah..."ls" the files arent there...
any help is appreciated
how to uninstall
I've tried a few methods.
The one I've found that works the best is this : mv <source> <destination> ...it's supposed to be a move command but it actually deletes files. rm also likely does the same (eg rm <filename.filetype OR foldername>)
BEFORE using these commands though, type in
adb shell <enter>
cd <foldername> <enter>
cd <foldername> <enter>....to get to folder (directory) of your choice
**TO get to app directory to uninstall apps, do cd system -->cd app -->mv appname.apk
I use the /sdcard as the destination for the mv command - I noticed the files NEVER get moved so this is just a delete command.
You could also delete a whole folder with this command. do cd system
mv app /sdcard
(this would delete the entire app folder/directory from the device).
That's pretty much it. Works for me. Was trial and error though - adb uninstall command ALWAYS resulted in 'failure ' or 'file not found' and the same with adb shell --> # uninstall appname.apk ---> 'failure'.
So I hope this works for you! Good luck .
str8arrow
NOTE: I've had an awful time because my stupid tablet has refused to download things from the market. It stalls in the initial 'starting download' bit and then just hangs, and then says 'download failed'. Apparently there's some problem with the sync'ing but I can't log into Gmail or GoogleTalk to try to resolve this (Gmail won't allow me to enter anything - left it on overnight and it said 'getting mail' / 'sync in progress' and the sync never completed after 12 hrs. The GoogleTalk app just displayed a black screen. So I am getting nowhere.
if anyone knows how to fix this pls let me know. I'm apparently not the only one. Others /various tablets have had similar issues - I have a 7" BPDN (Pandigital black novel).
Please, help!
str8arrow
adb shell <enter>
then
cd system
cd app
mv <filename.apk> <destination> (this should move the file BUT it never shows up in destination or elsewhere, so this is effectively a delete command, you could also do mv <foldername> <destination> to delete a whole folder.
**I usu. use /sdcard as my destination. so mv filename.apk /sdcard
OR
cd system
cd app
rm <filename.filetype> does the same sort of thing.
(eg adb shell <enter>
**I tried the uninstall commands listed but.. (adb uninstall-->'failure', or 'file not found' etc, adb shell --> uninstall --> same error).
Commands for removing apps.
I run as root on all my OS's, so I don't have to navigate to my sdk directory. I just type "adb devices", I don't know how your adb is setup, but get adb running and run these commands.
adb remount
adb shell
rm /system/app/whatever.apk
Or whatever path you pushed the files to. Try running fix_permissions to make your apps run properly and stop FC issues
So i'm trying to root my asus transformer by following this guide http://forum.xda-developers.com/showthread.php?t=1106587
i got to the part where it says to type the following command
Code:
adb push gingerbreakBB /data/local/
but i get the error
Code:
C:\Android>adb push gingerbreakBB /data/local/
error: more than one device and emulator
I ran adb devices to see what devices it recognises and it says
Code:
C:\Android>adb devices
List of devices attached
304D197CC264A27E device
28841c943012497 device
what now
unplug one of your devices (maybe your phone?) or use
Code:
adb -s 304D197CC264A27E push gingerbreakBB /data/local/
you might have to swap the serial number, depending what you have plugged in.
thanks mate it seemed like it rooted but it didnt lol. i got the progress bar on when i rebooted the device but it doesnt seem to be rooted hhmmmm any ideas?
Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in
if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714
gee one said:
Sorry, not sure... maybe your phone is rooted instead :0
Try starting over again without your phone plugged in
Click to expand...
Click to collapse
LOLOLOL you were right my phone was plugged in HOWEVER it still didnt work. the progress bar did show up again but wasnt rooted
mrevankyle said:
if you are on linux or have access to a linux machien use this http://forum.xda-developers.com/showthread.php?t=1198303
Otherwise do this http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
thanks i'll try that out later today. i think its sign for my to go to sleep its 3 am right now lolol. i'll post what happens today morning
Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle
kassim3 said:
Oh yeh going to sleep did the trick. I woke up and removed everything by doing the commands
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
and also followed the this video tutorial
http://www.youtube.com/watch?v=WaZ4B60OWmY&feature=player_embedded
aand it worked it!
Thanks gee one and mrevankyle
Click to expand...
Click to collapse
also would like to add to anyone else encountering this error with other uses of adb to make sure all of bluestacks processes are killed.
I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!
---------- Post added at 11:11 PM ---------- Previous post was at 11:10 PM ----------
I had the same issue when I've tried to room my XT1032 (Moto G)... I fail to install with the SuperBoot way! So I've decide to install CWM and a modified recovery.
On my first try, I receive this message:
Code:
error: more than one device and emulator
When I used the command
Code:
adb devices
I've 2 device... My XT1033 and an AndroidEmulator...
C:\Fastboot>adb devices
List of devices attached
emulator-5554 offline
TA88305ZDH offline
Click to expand...
Click to collapse
Also, the command
Code:
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
is not working for me...
I've use the command:
Code:
adb kill-server
After, I've plug back my XT1033 via USB and launch the command:
Code:
adb usb
Only my XT1033 is now show when I use the
Code:
adb devices
!
So, I've finish my installation with
Code:
fastboot-moto-windows flash recovery recovery.testkeys.img
and I've run a sideload installation with:
Code:
adb-windows sideload supersu.motog.zip
Try this and share me your opinion!
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
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.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Got stuck with htc logo after the LeeDroid flash on my HTC
Hi All,
Good morning. I am very new with Android, I did the flash rom using Leedroid 4.3.0 I can flash it ok, but it said I use s-off so I need to extract the boot.img from rom.zip and flash it.
I have no idea how to flash it. Can anyone guide me step by step.
I tried the ADB.exe with CMD but no luck, although it say (sending boot <3853 kb> ... okay, writing boot... OKAY, I still cannot get it to work, after reboot, I still got stuck with htc logo.
I am using HTC flyer, HBOOT 6.10.1002
Thank you in advance for your help
you need to flash it when you are in bootloader using fastboot command:
fastboot flash boot boot.img
You are my first teacher......enjoyed it....Thanks a lot...
Incredible s stuck on loading
Hey All,
Here is my story -
Never felt the need of rooting my phone, until one of my relatives, done that for me. If I ever knew, that i will have so many problems, I would have never let him do that.
Moving on, I couldn't find a rom fitting myself, always had bugs, used too much of my battery, or so on. Got tired losing everything, everytime i had to change the rom, after finding a bug i couldn't stand. So, I came back to original rom 2.3.5. Thought i will just update and will have S-off phone with original software.
Somehow it didn't let me update, I stayed with that for few months, then one day i decided i can't stand the old soft, and started working on getting my phone back to s-on and original rom. Used Android flasher to flash this file engHBOOToverARX . The next step was to flash the original rom, via
Android flasher. But i couldn't find it on internet. Therefore i thought it's just gonna be easier and faster that i'll just go and scan for the update.
It found and finally was updating when I was happy i'll get back to normal phone. Unfortunately, It wouldn't load the software anymore, only the white screen with the HTC logo.
Bootloader still says
Revolutionary
Vivo PVT SHIP S-OFF RL
HBOOT - 6.13.1002
RADIO - 3822.10.08.28_M
eMMC - boot
Apr 1 2011, 18:34:39
I tried to follow the steps, on the cmd.
But it looks like it can not find the device.
My phone is connected to the computer via usb cable and on the bootloader menu.
PLEASE HELP ASAP.
I am using my old Nokia 6310i as the backup plan at the moment, and believe me it is not fun at all, uxcept the fact that I make everyone laugh
when I take it from my pocket
Titas
Where to start:
This is not a general help thread
This is not even in the Q&A forum
You have a VIVO which is an incredible s not SAGA (codename for desire s so you're in the wrong forum)
Sywepd form my DsereiS
explanation
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
ayanah said:
"Setting up fastboot: Your phone must be on bootloader "
1st... what do you mean by "Your phone must be on bootloader" & how to do ??
Click to expand...
Click to collapse
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
ayanah said:
2nd... I accessed this thread from another one concerning nabi II tablet rooting .... but I can't figure out the DIRECT importance to know that ...in regard to rooting the nabi II
.... is it essential ??
Click to expand...
Click to collapse
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
ayanah said:
3rd.. can u please write the prompt commands in full manner ... as sometimes u use "\" or "/" eg:
"adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk "
that's a little bit difficult ..thanks
Click to expand...
Click to collapse
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
a reply
SimonTS said:
If you don't know that then you need to do A LOT of reading before attempting to play around with your device
I have no idea how you got here from the Nabi II forum - unless someone there felt that this was a decent guide to also use on the Nabi II
The OP is NOT going to rewrite his guide just for you after 6 months. Also, the difference between using '\' and '/' depends on whether you are using Windows or Linux - if you can't work that out then I would also suggest that you leave your device alone before you destroy it.
Click to expand...
Click to collapse
by the way .. in less than 1 hrs I used his guide to install programs from my PC (& I had no previous knowledge even where to start command prompt) on my old galaxy i5700 (use it for trials) ... I installed the programs using "adb install ....." & every thing is OK ... & I had successfully rooted my galaxy s6102 using another thread (not the one click programs) also every thing is OK ... I'd like to tell you I know about (rooting) less than 2 days ago ... so I think this is a good start for me ..... SO .. it would be appreciated to anyone who could answer me in short just showing little pit details & the pitfalls to avoid ...
also I thought"\" is where I copy from &"/" where I copy to i.e. concerning the direction of the path ... but I wasn't sure so I needed to get that explained
thanks for help but let OP take the decision HIMSELF.
referral thread :http://forum.xda-developers.com/showthread.php?t=1905674
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
kcallis said:
I have been trying to do a factory reset of the Nabi 2, and since I can't seem to access the "Mommy Mode", I thought I could do it from the recovery menu. So far I have yet to find any factor reset option available. Is there such a beast or am I out of luck?
Click to expand...
Click to collapse
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
c.m.b said:
This is not the Nabi 2 forum...
And don't even know what the hell the "Mommy Mode" is, but with the command <adb reboot recovery> should bring you to the recovery.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Actually, was able to get it sorted... I am not sure how I ended up posting on this thread, because I was replying on the Rooting Nabi thread... Weird!
If my USB debugging was off occurred when the soft brick, is there any way to get access via ADB?
My softbrick was caused by a bad file (framework-res.apk).
Is there any way to replace this file?
Nice work mOh19973 :good:
Your guide came in really handy for rooting the Nabi 2 that we got my son for Christmas. He'll be really excited once he sees that the Google play store is now available
Thanks,
Bodie
HELP!!!
mOh19973 said:
Definition:
ADB is the android debugging bridge that allows you to control your phone from your PC and is a bridge allowing you transfer stuff from it
Fastboot is usually used in bootloader and used a lot in unlocking your bootloader and commands in it
Setting up ADB:
1.Download the ZIP file from the attachments and extract it in C:\SDK\platform-tools (You will need to create these folders)
2. Go to command prompt by typing this word in menu search
3.Start writing
Code:
cd C:\SDK\platform-tools
adb.exe
You will see
Code:
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.
Don't freak out everything will be explained
4.Connect device and make sure that USB Debugging is enabled from Settings:Applicationsevelopment(on GB)
Settingseveloper Options(on ICS and HC)
5.Write
Code:
adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Device name
6.There are common commands used on ADB:
Code:
adb reboot
adb reboot recovery
adb reboot bootloader
adb push C:\<directory>\file /sdcard/
adb pull /sdcard/file C:\<directory>\
adb install C:\<directory>/file.apk
or /sdcard/<directory>/file.apk
adb remount
Push and Pull means copy form directory to another
ADB Shell for in device commands
Code:
adb shell
#mv /sdcard/file /system/app
#cp /sdcard/file /system/app
#rm /sdcard/file
#mkdir /sdcard/yourfoldernamehere
#ls /sdcard/<directory>
Setting up fastboot: Your phone must be on bootloader
Code:
cd C:\SDK\platform-tools
Commands List:
Code:
fastboot devices – lists which devices in fastboot mode are currently attached to your computer
fastboot boot <filename> – boots a rom stored on your pc specified by the filename
fastboot flash <partition> <filename> – flashes a rom stored on your pc, partition can be one of {boot, recovery, system, userdata}
Example: fastboot flash recovery C:\<directory>\recovery.img
PS: When i wrote <directory> it means like C:\Users\Desktop\Desktop\file
Or you can put the file in the the platform-tools folder you created so
write Ex:
Code:
adb push file.apk /sdcard/
Click to expand...
Click to collapse
When I go to command and type in adb.exe i get an error. Also when I try to download the file it doesn't let me have the option of saving the file to platform-tools. I have to move it there myself and then I extract the files. I've done this several different times and still keep coming up with same results on the command prompt! Please help!!!! Been working on this for 4 hours!!!
Once in directory you do not type adb.exe. just type
Adb devices
If your Android device is hooked into the USB it should be listed
Flyer
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
sweetpea8852 said:
When I go
Click to expand...
Click to collapse
In future, please don't quote the entire OP lie that when there is no need. It makes threads much more difficult to follow.
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
This is the Desire S forum. You may have been directed here, but we don't use Nabi tablets I'm afraid.
Nabi 2
Klarkus said:
I am having major troubles trying to root my nabi 2 tablet. I tried replying on the actual thread but it wouldnt let me. If anyone can help me out please do. I've tried 2 ways which are pretty much the exact same.
1. download pdanet - install (whilst tablet is plugged in) and chose samsung and it shows up in devices as working fine
2. downloaded platform-tools and made SDK and platform-tools folder. I have the install files as well
3. Run cmd type cd C:\SDK\platform-tools. type adb.exe and it loads in.
4. Run install and chose option 1.
It goes to the option where I choose reboot kernal then it restarts and I get the green android icon with the red triangle with esclamation mark in it.
What am I doing wrong its been doing my head in for 3 days now if anyone can help it would be great. thanks
Click to expand...
Click to collapse
Try this link
http://forum.xda-developers.com/showthread.php?t=1905674
i need some help in cammand propt for adb devices please. my problem is when i push enter on putting in adb devices it says emulator-5554 device and then my device underneath, i need to some how turn off the emulator because it will only finish process with one adb device. has anyone asked you about this before? can you help me?
I turned off Auto download on WiFi, but I'm not confident it will stop update to Oreo.
Anyone know if/what I need to do to prevent the update?
I found in Developer Options an auto system update option that I turned off but it still updated. Dammit!
No help from anyone here either. Maybe it can't be prevented.
I have deactivated network access for the app „System Update“ and deactivated the search for updates from within the update app.
Seems to work.
I'll keep that in mind if it happens again.
Update on turning off updates in Developer options: I have since found this to be what happens after turning off auto update in dev options:
It downloads the update
It puts a notice up that it has upgraded and I need to boot (that was when I posted about it still updating)
But turns out it does not actually perform the update.
It is a bit annoying. I get that notice and it remains in the notifications, even though I have gone in and turned off that notification. As long as it doesn't update, I guess I can live with it.
As it's already downloaded, I'd say your options won't help me at this point.
To get rid oft the notification, open Settings » Apps and delete data an cache oft the Systemupdate app. Then continue restricting its network access ( all three options) and notifications. To be sure, disable its ability to change system settings.
itsjustmeagain said:
I have deactivated network access for the app „System Update“ and deactivated the search for updates from within the update app.
Seems to work.
Click to expand...
Click to collapse
I presume I disable network access under networked apps menu. The only access listed there is mobile. I would think it could still get there when hooked to Wi-Fi.
Do not see an app called update for which to disable search. But I have applied all of your other suggestions, and appreciate your help.
without root : adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
Done !
I was surprised...just got another prompt to update. Wanted access to photos. I denied and cancelled. I haven't had that particular promo for a while. I bet outs prompting now because I deleted the download. Although I have auto update turned off in developer options.
use my command and you'll never get this update again
mrassol said:
use my command and you'll never get this update again
Click to expand...
Click to collapse
Ok. Thanks. I'll have to get the appropriate stuff installed on the PC to do that. Since moving to this phone from Samsungs, I've not used any of that stuff, or done any rooting (I do miss root a bit).
mrassol said:
use my command and you'll never get this update again
Click to expand...
Click to collapse
So I have just finished a fresh reload of the original ROM, and now want to trh the command you listed
adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
Click to expand...
Click to collapse
But I can't get ADB to recognize the phone. I have USB Debugging turned on. I have Hisuite able to see it. But ADB does not see it.
When I search Google for how to do ADB on the Mate 9, I keep getting led to info about installing fastboot. When I go to the Huwaei site to download the fastboot / adb stuff, the site freezes.
Any suggestions?
ewingr said:
So I have just finished a fresh reload of the original ROM, and now want to trh the command you listed
But I can't get ADB to recognize the phone. I have USB Debugging turned on. I have Hisuite able to see it. But ADB does not see it.
When I search Google for how to do ADB on the Mate 9, I keep getting led to info about installing fastboot. When I go to the Huwaei site to download the fastboot / adb stuff, the site freezes.
Any suggestions?
Click to expand...
Click to collapse
have you tried to uncheck and recheck usb debugging ?
what does adb devices tells you ?
mrassol said:
have you tried to uncheck and recheck usb debugging ?
what does adb devices tells you ?
Click to expand...
Click to collapse
I don't know what was going on. AFter posting, I was chasing USB drivers. But I was having problems finding them to download too. I tried it again though, and it is now working. Not sure what was going on.
Thanks for your input. I appreciate it.
Restore update
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
minzak said:
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
Click to expand...
Click to collapse
adb shell cmd package install-existing com.huawei.android.hwouc
For me it's better to disable/enable this app:
adb shell pm disable-user com.huawei.android.hwouc
adb shell pm enable --user 0 com.huawei.android.hwouc
minzak said:
Hm, and how it restore, again install it com.huawei.android.hwouc ?
Where is download it?
Thanks
Click to expand...
Click to collapse
To disable System Update, use:
adb shell pm disable-user com.huawei.android.hwouc
If you ever want to enable it back, simply go to Settings, Apps, check to show System apps and services, scroll to System Update and Enable
Tuxozaur said:
adb shell cmd package install-existing com.huawei.android.hwouc
For me it's better to disable/enable this app:
adb shell pm disable-user com.huawei.android.hwouc
adb shell pm enable --user 0 com.huawei.android.hwouc
Click to expand...
Click to collapse
When I type in:
adb shell cmd package install-existing com.huawei.android.hwouc
Click to expand...
Click to collapse
I get error "Unknown command: install-existing"
So I tried:
adb shell cmd package install -existing com.huawei.android.hwouc
Click to expand...
Click to collapse
I get this:
Exception occurred while dumping:
java.lang.IllegalArgumentException: Unknown option -e
at com.android.server.pm.PackageManagerShellCommand.makeInstallParams(PackageManagerShellCommand.java:1070)
at com.android.server.pm.PackageManagerShellCommand.runInstall(PackageManagerShellCommand.java:139)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:94)
at android.os.ShellCommand.exec(ShellCommand.java:94)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:19505)
at android.os.Binder.shellCommand(Binder.java:468)
at android.os.Binder.onTransact(Binder.java:367)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2387)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3504)
at com.android.server.pm.HwPackageManagerService.onTransact(HwPackageManagerService.java:659)
at android.os.Binder.execTransact(Binder.java:565)
Click to expand...
Click to collapse
So I did a list of the command parameters, and do not even see anywhere that -existing would be used.
Can someone please provide me correct command to re-install the com.huawei.android.hwouc?
ewingr said:
When I type in:
I get error "Unknown command: install-existing"
...
Can someone please provide me correct command to re-install the com.huawei.android.hwouc?
Click to expand...
Click to collapse
Correct re-install command is as in the Post #15:
Code:
adb shell cmd package install-existing com.huawei.android.hwouc
See also:
https://www.xda-developers.com/uninstall-carrier-oem-bloatware-without-root-access/
https://forum.xda-developers.com/ma...-bloatware-blocking-ads-t3971297/post80526831
and attachments (batch script - rename to bat, and screenshot from PC)
Code:
ECHO OFF
CLS
adb wait-for-device devices
PAUSE
ECHO List packages
adb shell pm list packages
PAUSE
ECHO Disable System Update
adb shell pm disable-user com.huawei.android.hwouc
PAUSE
ECHO List disabled packages
adb shell pm list packages -d
PAUSE
ECHO Re-enable System Update
adb shell pm enable com.huawei.android.hwouc
PAUSE
ECHO Uninstall System Update
adb shell pm uninstall -k --user 0 com.huawei.android.hwouc
PAUSE
ECHO Re-install System Update
adb shell cmd package install-existing com.huawei.android.hwouc
PAUSE
Make sure to have ADB USB debugging enabled in Development menu. PC must be granted for debugging (from the phone side).
Ofc, drivers, etc must be installed to the PC - Minimal ADB and Fastboot package (search on XDA) will do
Problem is, I have already run the delete cmd from earlier in the thread (a reply to my original post here.) Now I need to reinstall. The post I quoted supposedly is how to do that, but I'm getting the errors noted. Going forward I will do it per your suggestion.
Hoping someone can give me correct syntax to revive the update functionality.
ewingr said:
Problem is, I have already run the delete cmd from earlier in the thread (a reply to my original post here.) Now I need to reinstall. The post I quoted supposedly is how to do that, but I'm getting the errors noted. Going forward I will do it per your suggestion.
Hoping someone can give me correct syntax to revive the update functionality.
Click to expand...
Click to collapse
There is no ADB delete cmd - could you be precise and quote exactly the command you originally used?
And the ROGHT commands for ADB re-enabling and re-installing are e.g in my previous post, there are no other 'correct syntax' commands (Google search is also your friend)
If your ADB does not recognize
adb shell cmd package install-existing ...
then something is wrong with your ADB installation on PC or settings on the phone.
Follow the first link in my previous answer and set/install ADB exactly as described in the XDA article
Ofc, if you rooted the phone and you really DELETED hwouc, then you can not reinstall by ADB - but then ADB would not complain that it did not recognize the command but would complain that package did not exist
I am on A13 on a pixie 7 pro running the November update and the kirisakura kernel. I’m rooted with magisk v24.2 with lsposed latest version using aosp mods and xprivacy lua. I had bbs v.24 and it wasn’t working. I updated to the latest version on play store. The app had already been granted root with the old version. The new version didn’t request root permission. BBS did flag me with the message that it needed more permissions. I entered:
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.BATTERY_STATS
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.DUMP
adb -d shell pm grant com.asksven.betterbatterystats_xdaedition android.permission.PACKAGE_USAGE_STATS (needed starting on Lolipop)
adb -d shell settings put global hidden_api_policy_pre_p_apps 0
adb -d shell settings put global hidden_api_policy_p_apps 1
adb -d shell settings put global hidden_api_policy 1
Notice I modified the global hidden api policy to a 0 above because I thought this was some global setting.
At first the device would boot but return right to the Lock Screen upon entering my PIN. After entering safe mode I can get in the phone but after a few seconds or minutes of booting up the UI freezes up and I have to get reboot. I imagine when something starts up now I’m getting the issue.
Any idea of how I fix this up? Any ideas or guidance is appreciated.
The lock screen thing happened with aosp mods. But an update fixed it.
the phone will run in safe mode. i can get in long enough to uninstall magisk- and i did- but it still freezes after 30 seconds or so and then reboots after being frozen for another 30 seconds. i am running and adb logcat but have no idea what to look for