Please Help.
So I have rooted 16gig nook tablet running CM7 and all is well except I want to do the repartition thing so that I have more than 1 gig available to me.
I believe I have found the method to do that however for the liffe of me I can not get adb working.
I have adb drivers on computer. Computer is recognizing the nook tablet as an adb android device with the drivers that I installed to it. I can use cmd and get into adb however adb will not find any device. Please help.
Or anyone know an easier way to repartition so I can get more than one gig?
Reboot into recovery and try.
Solar.Plexus said:
Reboot into recovery and try.
Click to expand...
Click to collapse
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
Good Idea I didnt think of that. I tried that and here is what I am getting
C:\Users\Realtorizzle>cd C:\Users\Realtorizzle\Desktop\Nook Tablet Drivers\Drive
rs+adb\ntroot
C:\Users\Realtorizzle\Desktop\Nook Tablet Drivers\Drivers+adb\ntroot>adb shell
error: device not found
C:\Users\Realtorizzle\Desktop\Nook Tablet Drivers\Drivers+adb\ntroot>adb kill-se
rver
C:\Users\Realtorizzle\Desktop\Nook Tablet Drivers\Drivers+adb\ntroot>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Realtorizzle\Desktop\Nook Tablet Drivers\Drivers+adb\ntroot>
still not finding any devices
Solar.Plexus said:
Reboot into recovery and try.
Click to expand...
Click to collapse
also it apperars nook tablet drivers are installed correctly
Which ROM is currently being run?
Also, what is your NT listed as in the Device Manager?
Solar.Plexus said:
Which ROM is currently being run?
Also, what is your NT listed as in the Device Manager?
Click to expand...
Click to collapse
Running Celtics cm7
See pic for device manager
Sent from my SPH-D710 using Tapatalk
Do you use any other android devices with this computer?
Cubanluke88 said:
Do you use any other android devices with this computer?
Click to expand...
Click to collapse
No. Actually just a very recent wipe to this computer and fresh windows 7 professional 64 bit install.
I am sure it is something I am missing or doing wrong though because I have tried on 4 different computers and get same result always. So clearly I am missing a step or something.
Sent from my SPH-D710 using Tapatalk
Did you run the runmefirst.bat? that file should create a .android folder with a file adb_ubn.ini under it.
Check the path and the content of the adb_usb.ini in the following picture:
If you don't have it then check my thread [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Video - Tutorial to get all you need. I have a windows 7 64 bit aswell and those drivers worked for me.
If you say it's a fresh install of windows 7 then you should be good to run adb after you set it up correctly.
~ Veronica
is usb debugging enabled under application settings?
lavero.burgos said:
Did you run the runmefirst.bat? that file should create a .android folder with a file adb_ubn.ini under it.
Check the path and the content of the adb_usb.ini in the following picture:
If you don't have it then check my thread [HOW-TO] Install & Use ADB tool | Android Debug Bridge | Drivers - Video - Tutorial to get all you need. I have a windows 7 64 bit aswell and those drivers worked for me.
If you say it's a fresh install of windows 7 then you should be good to run adb after you set it up correctly.
~ Veronica
Click to expand...
Click to collapse
I did not run run me first I didny think it was something you could run. Just a text doc or something. I will watch your video and check it out and try. Maybe that is my problem . Also to the other person who asked I do have USB debugging enabled. Thanks for all the help everyone I will give update after trying Veronica suggestions.
Sent from my SPH-D710 using Tapatalk
OK veronica After running runmefirst now adb seems to be working and it finds a device !!! (however I do not have a adb_usb.ini file is this a problem? I mean adb seems to be working)
Anyways I can now do adb shell and I get the # however when running the parted /dev/block/mmcblko i get the parted not found.
I donloaded nt_repartition_files.zip and put them in the same file as adb zipped and unzipped just to be safe and I try to run the
$ adb push parted /system/bin
* tune2fs and e2fsck may not be needed *
~ $ adb push tune2fs /system/bin
~ $ adb push e2fsck /system/bin
for each one though I do not think it is doing anything. I just get a really long thing like this
C:\Users\mobizzle>cd C:\Nook Tablet Drivers\Drivers+adb\ntroot
C:\Nook Tablet Drivers\Drivers+adb\ntroot>adb push parted/system/bin
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
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 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.
C:\Nook Tablet Drivers\Drivers+adb\ntroot>
So it does not seem to be doing anything rather just giving me a bunch of info.
I really want to get my nook all repartitioned so I can start setting it up and getting it how i like and using it !
towir022 said:
OK veronica After running runmefirst now adb seems to be working and it finds a device !!! (however I do not have a adb_usb.ini file is this a problem? I mean adb seems to be working)
Anyways I can now do adb shell and I get the # however when running the parted /dev/block/mmcblko i get the parted not found.
I donloaded nt_repartition_files.zip and put them in the same file as adb zipped and unzipped just to be safe and I try to run the
$ adb push parted /system/bin
* tune2fs and e2fsck may not be needed *
~ $ adb push tune2fs /system/bin
~ $ adb push e2fsck /system/bin
for each one though I do not think it is doing anything. I just get a really long thing like this
C:\Users\mobizzle>cd C:\Nook Tablet Drivers\Drivers+adb\ntroot
C:\Nook Tablet Drivers\Drivers+adb\ntroot>adb push parted/system/bin
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
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 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.
C:\Nook Tablet Drivers\Drivers+adb\ntroot>
So it does not seem to be doing anything rather just giving me a bunch of info.
I really want to get my nook all repartitioned so I can start setting it up and getting it how i like and using it !
Click to expand...
Click to collapse
run
$ adb devices
and post the output
~ Veronica
lavero.burgos said:
run
$ adb devices
and post the output
~ Veronica
Click to expand...
Click to collapse
OK here is what I get doing adb devices. (also do I need to do something to get the $, I have not had the $ so maybe that is my problem. Do I need to type su or something?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\mobizzle>cd C:\Nook Tablet Drivers\Drivers+adb\ntroot
C:\Nook Tablet Drivers\Drivers+adb\ntroot>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
2014920069854000 device
C:\Nook Tablet Drivers\Drivers+adb\ntroot>
Also here is a photo of what all is in the folder that I CD to to use adb
Sent from my SPH-D710 using Tapatalk
towir022 said:
OK here is what I get doing adb devices. (also do I need to do something to get the $, I have not had the $ so maybe that is my problem. Do I need to type su or something?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\mobizzle>cd C:\Nook Tablet Drivers\Drivers+adb\ntroot
C:\Nook Tablet Drivers\Drivers+adb\ntroot>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
2014920069854000 device
C:\Nook Tablet Drivers\Drivers+adb\ntroot>
Click to expand...
Click to collapse
I just realized your error in the command you didnt leave a space between parted and /system/bin
First you need to mount /system in CWM from mount&storage >> Mount /system, then issue the command
> adb push parted /system/bin
Unmount /system in CWM once you finish pushing the tools.
Sorry i put $ because im used to linux , on windows is > so that has nothing to do.
~ Veronica
Sent from my Nook Tablet using xda premium
lavero.burgos said:
I just realized your error in the command you didnt leave a space between parted and /system/bin
First you need to mount /system in CWM from mount&storage >> Mount /system, then issue the command
> adb push parted /system/bin
Unmount /system in CWM once you finish pushing the tools.
Sorry i put $ because im used to linux , on windows is > so that has nothing to do.
~ Veronica
Thanks once again. I got it all to work and I followed this tutorial
http://forum.xda-developers.com/showthread.php?t=1531120
Sent from my Nook Tablet using xda premium
Click to expand...
Click to collapse
It definatley changed things because now I have 3.89 GB of space available for internal storage however I am confused because I thought I would have like a bunch more.
towir022 said:
It definatley changed things because now I have 3.89 GB of space available for internal storage however I am confused because I thought I would have like a bunch more.
Click to expand...
Click to collapse
Do you have 8gb or 16 gb model?
post your (parted) print here so i can check the partition table.
Here is an example:
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
p
p
Model: MMC SEM16G (sd/mmc)
Disk /dev/block/mmcblk0: 15.9GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.8MB 33.6MB 16.8MB boot
5 33.6MB 83.9MB 50.3MB fat32 rom
6 83.9MB 134MB 50.3MB fat32 bootdata
7 134MB 522MB 388MB ext4 factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 11.6GB 9989MB fat32 media msftres
11 11.6GB 15.9GB 4326MB ext4 userdata
Click to expand...
Click to collapse
~ Veronica
OK I think I got it all figured out. There is 9. Something gigs available in mnt media or something and then the 3. Something gigs is like seperate. Not sure why it is like this but I am transferring 8 gigs of music to it right now so assuming it works I should be all good.
I would be interested why it is mnt media where the 9 gigs are but i guess it does not matter much as long as it works.
One million thanks Veronica
Sent from my SPH-D710 using Tapatalk
towir022 said:
OK I think I got it all figured out. There is 9. Something gigs available in mnt media or something and then the 3. Something gigs is like seperate. Not sure why it is like this but I am transferring 8 gigs of music to it right now so assuming it works I should be all good.
I would be interested why it is mnt media where the 9 gigs are but i guess it does not matter much as long as it works.
One million thanks Veronica
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
No prob, i think you saw it wrong because depending where you look at "internal storage" is actually /userdata (partition #11) so that is fine. means you have 3.89GB to install apps.
Edit: Please add [SOLVED] tag to the title of this thread.
~ Veronica
Related
I really hope someone can help me. I don't know what else to do.
My rooted slide was stolen last week. Just got a new one but of course it with 2.2.1 and I am trying to root it. I made the gold card, installed Adb, and followed all the directions find here to root the phone but below is what I am getting.
I really need to get this phone rooted.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Ladyr>cd c:\
c:\>cd c:\android\android-sdk\android-sdk-windows\platform-tools
c:\Android\android-sdk\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT069PS08148 device
c:\Android\android-sdk\android-sdk-windows\platform-tools>adb push flash_image/d
ata/local
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:\Android\android-sdk\android-sdk-windows\platform-tools>
I don't think you are using the correct windows path for you file you are trying to push. Try using the file paths in your adb commands.
do it this way works in 5 min no gold card needed http://forum.xda-developers.com/showthread.php?t=1108316 .WORKS everytime just did it again 3 hours ago.....
just thank me if it works
Thank you, I am not rooted thanks to you. had one small problem but was easy to remdy.
kitila said:
do it this way works in 5 min no gold card needed http://forum.xda-developers.com/showthread.php?t=1108316 .WORKS everytime just did it again 3 hours ago.....
just thank me if it works
Click to expand...
Click to collapse
Hey sry.I already had to update.zip on my sd root so I didn't know...but ty for telling me....but yea it still rooted ur phone u just didn't have the cwm..so um yea I did help u root you phone just didn't help u get cwm.....so wooot for me lol
Didn't work for me.
kitila said:
do it this way works in 5 min no gold card needed http://forum.xda-developers.com/showthread.php?t=1108316 .WORKS everytime just did it again 3 hours ago.....
just thank me if it works
Click to expand...
Click to collapse
I tried the superoneclick and all I got was device not found or wating for device. I couldn't find a error fix for that so that is where I stopped. I have a new MT3GS 2.2.1. Nothing I have tried from last june in 2010 until today has worked. Even in a shell when I do adb it just comes up device not found and yes I have done all the changes to the phone with the charge only shutting down the wifi and debugging oh and screen on. I had to get a new phone since I did a OTA update and when I try to make a call my phone reboots all the time. T-Mobile sent me new phones but they all do the same thing and it is a HTC problem so I need to root and get rid of HTC
Did someone have the files for the goldcard method and can be gentle enough to send them to me Ill be really thanksfull, please I have done the oficial update and lost my root. Help me out please I know how to do everything just needs the files cause links are dead.
Pm me or send to my email please
[email protected]
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
well, i tried to make it as clear as possible step by step, hope this helps everyone
http://www.youtube.com/watch?v=dS8h7l_KwSw
LMFAO man...how do you find ANYTHING on that desktop...heheh. Nice Vid man, thanks for the contribution!
Bandage said:
LMFAO man...how do you find ANYTHING on that desktop...heheh. Nice Vid man, thanks for the contribution!
Click to expand...
Click to collapse
lol, i manage, i even get lost sometimes,lol, but anything to help everyone out, since i don't know a lot of about andriod or making roms or root methods, i figured my small video would help
Thanks for the video very helpful.
And yes how do you find anything, I got distracted from the video for a few mins look at your desktop, and also your bookmarks on explorer
predwing said:
Thanks for the video very helpful.
And yes how do you find anything, I got distracted from the video for a few mins look at your desktop, and also your bookmarks on explorer
Click to expand...
Click to collapse
hahaha, after seeing this for what, 5 years now, i got use to it, you guys should have seen my last rig, the entire screen was full
Although i am already rooted via HD dock, good video and holy **** on the icons, i am one of those people who don't even use desktop icons.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\ralph>cd ..
C:\Users>cd ..
C:\>cd c:/root
c:\root>adb push photon-torpedo.tar /data/tmp
cannot stat 'photon-torpedo.tar': No such file or directory
c:\root>adb push photon-torpedo.tar/data/tmp
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
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 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.
c:\root>adb shell
$ cd /data/tmp
cd /data/tmp
$ /bin/tar xf /data/tmp/photon-torpedo.tar
/bin/tar xf /data/tmp/photon-torpedo.tar
/bin/tar: /data/tmp/photon-torpedo.tar: Cannot open: No such file or directory
/bin/tar: Error is not recoverable: exiting now
$ /bin/tar xf/data/tmp/photon-torpedo.tar
/bin/tar xf/data/tmp/photon-torpedo.tar
/bin/tar: Old option `f' requires an argument.
Try `/bin/tar --help' or `/bin/tar --usage' for more information.
$
as you see does not work for me i could not get the 64 bit drivers to extrace on my comp so lmk.
c:\root>adb push photon-torpedo.tar /data/tmp
cannot stat 'photon-torpedo.tar': No such file or directory
"No such file or directory"...It looks like you may not have the photon-torpedo.tar in the correct folder on your computer. Did you put the downloaded file "photon-torpedo.tar" in your computer's directory c:/root ? The file has to be in the same folder so adb will know where to look to push it to the correct directory on the photon.
Yes it is in c:root along with the files of ADB
rdcrds said:
Yes it is in c:root along with the files of ADB
Click to expand...
Click to collapse
take a screen shot of your folder please, so i can see if all the right files are in, because this should work perfectly
I tried again and when i try this i get stuck
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\ralph>cd..
C:\Users>cd ..
C:\>cd c:/root
c:\root>adb push photon-torpedo.tar/data/tmp
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
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 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.
c:\root>
are you spacing it?
c:\root>adb push photon-torpedo.tar/data/tmp
it should look like this
c:\root>adb push photon-torpedo.tar /data/tmp
and is your phone in debug mode
got past that now stuck at /data/tmp/install-su.sh says no such file or directory
rdcrds said:
got past that now stuck at /data/tmp/install-su.sh says no such file or directory
Click to expand...
Click to collapse
Did you install superuser and terminal emulator from the market? When I tried to install terminal emulator the first time I got an error and had to reinstall.
kimmied2000 said:
Did you install superuser and terminal emulator from the market? When I tried to install terminal emulator the first time I got an error and had to reinstall.
Click to expand...
Click to collapse
Huh??? What's terminal emulator for?? Didn't even have to touch that
Sent from my MB855 using XDA App
What is terminal emulator for? see bold From the original post
Instructions:
Use your favorite method to get photon-torpedo.tar into /data/tmp
Install Superuser from the Market
***Install Android Terminal Emulator from the Market
Run Android Terminal Emulator
Run cd /data/tmp
Run /bin/tar xf /data/tmp/photon-torpedo.tar
Run /data/tmp/photon-torpedo.sh
Run /data/tmp/install-su.sh
Download:
Photon Torpedo
kimmied2000 said:
What is terminal emulator for? see bold From the original post
Instructions:
Use your favorite method to get photon-torpedo.tar into /data/tmp
Install Superuser from the Market
***Install Android Terminal Emulator from the Market
Run Android Terminal Emulator
Run cd /data/tmp
Run /bin/tar xf /data/tmp/photon-torpedo.tar
Run /data/tmp/photon-torpedo.sh
Run /data/tmp/install-su.sh
Download:
Photon Torpedo
Click to expand...
Click to collapse
didn't have to do that, so i don't know what method your using
It's from edgan's original post when he found the root method
http://forum.xda-developers.com/showthread.php?t=1216131
(I should have put the link in my previous post).
Anyway, I don't really know what it is, I just know how to follow directions and it worked for me. Guess you didn't need to do it, so I guess it's a moot point. Just thought that might be why the other poster was having such problems getting root to work.
By the way, thanks for posting the video.
Can someone help me? after the second command I'm getting device not found??
khaag27 said:
Can someone help me? after the second command I'm getting device not found??
Click to expand...
Click to collapse
did you install the drivers and is your phone in debug mode???
Ok im working on something big for the amaze but need someone to dump the boot.img here are the comands
1. Download ADB: http://www.mediafire.com/?5d0v316g9bg97
2. Extract the contents of the zip to C:\
3. Run the commands below:
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Note: If your device is not detected, download and install HTC Sync.
4. Connect your phone in USB Mode, copy the hboot.img file from your SD card and upload it to Multiupload.
Love to do it but I'm at work. If no one does by the time I get home ill be happy to.
Sent from my HTC_Amaze_4G using XDA App
I'll do it when I get home from school
Sent from my HTC_Amaze_4G using XDA Premium App
xboarder56 said:
Ok im working on something big for the amaze but need someone to dump the boot.img here are the comands
1. Download ADB: http://www.mediafire.com/?5d0v316g9bg97
2. Extract the contents of the zip to C:\
3. Run the commands below:
Code:
cd c:\adb
adb shell
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Note: If your device is not detected, download and install HTC Sync.
4. Connect your phone in USB Mode, copy the hboot.img file from your SD card and upload it to Multiupload.
Click to expand...
Click to collapse
Didn't work. Any other ideas. This was the output.
List of devices attached
HT19RVP07371 device
C:\Users\Administrator>adb shell
$ dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
/dev/block/mmcblk0p22: cannot open for read: Permission denied
$
Click to expand...
Click to collapse
Binary100100 said:
Didn't work. Any other ideas. This was the output.
Click to expand...
Click to collapse
maybe try this
adb pull dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
Click to expand...
Click to collapse
xboarder56 said:
maybe try this
Click to expand...
Click to collapse
Here's the output:
C:\Users\Administrator>adb pull dd if=/dev/block/mmcblk0p22 of=/sdcard/boot.img
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:\Users\Administrator>
Click to expand...
Click to collapse
ohh i mean
adb pull dd if=/dev/block/mmcblk0p22
xboarder56 said:
ohh i mean
adb pull dd if=/dev/block/mmcblk0p22
Click to expand...
Click to collapse
remote object 'dd' does not exist
I tried and got the same errors...
Would it help to push busybox then try the adb pull?
EDIT: Nevermind. The reason none of this is working is because the block is only readable by root. I'm still a little too squimish to try the temp root thing, but that's the only way to get the file.
Here ya go.
HTC Amaze boot.img
Can someone return the favor an post a stock recovery image. I ruined mine and now I cannot do a factory reset or reboot into recovery.
After temp rooting the phone do this:
Code:
adb shell dd if=/dev/block/mmcblk0p23 of=/sdcard/recovery.img
Thanks,
-xdadevelopers-user
xdadevelopers-user said:
Here ya go.
HTC Amaze boot.img
Can someone return the favor an post a stock recovery image. I ruined mine and now I cannot do a factory reset or reboot into recovery.
After temp rooting the phone do this:
Code:
adb shell dd if=/dev/block/mmcblk0p23 of=/sdcard/recovery.img
Thanks,
-xdadevelopers-user
Click to expand...
Click to collapse
Will do so after phone arrives (and if i don't brick it with temp root + permanent fix). Hope you get it earlier, as that will be end of week at the earliest.
I used NVflash to originally flash Recovery on G2X - can Nvflash be used the same way here?
gaww said:
Will do so after phone arrives (and if i don't brick it with temp root + permanent fix). Hope you get it earlier, as that will be end of week at the earliest.
I used NVflash to originally flash Recovery on G2X - an Nvflash be used the same way here?
Click to expand...
Click to collapse
no its gonna have to be done through hboot
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to 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.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
As explained above, the quick ADB pusher is an interface over the code based ADB. I will be a much easier approach for new user of android to get to grips to, that is why I am including it.
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, so here we go:
First of all you want to download the quick adb pusher program, this is in both this thread and the revolution Rom thread on XDA, the link for the program is listed below:
Quick ADB Pusher
Now you want to make sure your phone is plugged into your computer, but do not put it into USB storage mode. Make sure your USB de-bugging option is enabled it is located at:
Settings --> Developer options --> USB De-bugging
Now you will start the quick ADB pusher program, once it has started it should detect your phone. If it does not then post a comment in the thread below and we will resolve the issue.
Watch the video below to clarify a few things, such as how to copy system apps etc...
Again I hope this tutorial helps some people out, remember to read the FAQ first before posting,, to prevent the same questions being asked time and time again.
FAQ
Do you guys want a guide on how to build roms for your device?
Sent from my HTC Desire C using xda premium
russell664 said:
Do you guys want a guide on how to build roms for your device?
Sent from my HTC Desire C using xda premium
Click to expand...
Click to collapse
Yes please I think it would be very interesting.
And thanks for your time in doing this :good:
AW: [GUIDE][HOWTO] How to push files using ADB Desire V
Me too
Sent from my HTC Desire V using xda premium
I will when I have time guys, if you want more guides and stuff, surely you can smash the thanks button right in the face for me. To show your support, and that you appreciate my work.
Creating our own custom roms
Yup. It really would be a great tutorial for newbies to get started to make things, which once they could only appreciate. I am myself good at programming and algorithms, but Android development is quite alien to me. I consider myself a potential developer, if only would I get a kick start at ROM making. Also we could be able to support unknown or local market devices. I think that would be really beneficial for the entire Android community to see new budding developers with their innovations. :angel:
Hit thanks if you agree.
russell664 said:
As explained above, the quick ADB pusher is an interface over the code based ADB. I will be a much easier approach for new user of android to get to grips to, that is why I am including it.
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, so here we go:
First of all you want to download the quick adb pusher program, this is in both this thread and the revolution Rom thread on XDA, the link for the program is listed below:
Quick ADB Pusher
Now you want to make sure your phone is plugged into your computer, but do not put it into USB storage mode. Make sure your USB de-bugging option is enabled it is located at:
Settings --> Developer options --> USB De-bugging
Now you will start the quick ADB pusher program, once it has started it should detect your phone. If it does not then post a comment in the thread below and we will resolve the issue.
Watch the video below to clarify a few things, such as how to copy system apps etc...
Again I hope this tutorial helps some people out, remember to read the FAQ first before posting,, to prevent the same questions being asked time and time again.
Click to expand...
Click to collapse
It told me my devices wasn't rooted?
When trying to push a file to my internal storage on my Moto X does the file need to be located in a specific location? I am trying to root my device and need to push a file to my device. I am very new to this, and have adb working and my device showing up when i run "adb devices". I have a folder on my desktop titled "android" which contains adb, fastboot, sdk, and eclipse. Do I need to save the files I want to push to the root of this folder on my desktop? Thanks for the help!
stavebomb said:
When trying to push a file to my internal storage on my Moto X does the file need to be located in a specific location? I am trying to root my device and need to push a file to my device. I am very new to this, and have adb working and my device showing up when i run "adb devices". I have a folder on my desktop titled "android" which contains adb, fastboot, sdk, and eclipse. Do I need to save the files I want to push to the root of this folder on my desktop? Thanks for the help!
Click to expand...
Click to collapse
So push whole folder by
Code:
adb push <path on PC> <path on Moto X>
How to push this command
Please help me:
http://forum.xda-developers.com/showthread.php?t=2708466
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
on my LG G2 (D802 ver 20B without root indian version)
My tablet is stuck in the recovery mode on a permanent loop. Please help
I'm just learning to code and honestly as of 6 months ago I didn't even know how to turn a computer on although I practice and take classes I'm petrified I'm going to screw up my computer. Anyway, my tablet is stuck in the recovery mode on a permanent loop so I can't put it in debug development mode. Please help me fix it. I can't afford a new one and I use it for work when I'm at a job site. I downloaded the Android Suite bundle zip (the one that said recommended) also the sdk tools zip, the quick adb pusher and the lollipop image file, lollipop rom file. I've tried every one of the commands from your site and many many other sites and it's not fixing my tablet. I know you guys don't like stupid questions but I'm feeling like a moron because I can't figure it out. Could someone please please help me fix me tablet.
russell664 said:
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to 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.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
Click to expand...
Click to collapse
I Want to Thank Russell664. I followed your instructions and my tablet works again.
Thank you very much. You do not know how appreciative I am for your help. I hate feeling so stupid about these things. Your detailed guide was so informative and so so helpful. Debbie from Handyman-Girl
:good:
russell664 said:
Hello guys today I am going to show you how to use a program called quick adb pusher, it is a great starting point for new android users who want to copy modified system files, without flashing update Zip’s all the time, it will also let member do things manually instead of relying on update ZIP's all the time. Besides of explaining how to use a simple program such a quick ADB Pusher, i will also explain in depth the commands of ADB through the actual command line interface, so here we go:
First of all we will start with The command line ADB, the quick adb pusher tutorial is further down the post.
Before we start explaining some of the code what is used in ADB, it is important you know what it is, it is called the Android-Debug-Bridge.
In order to even get ADB to wokr you need to follow these procedures:
Settings -> Developers options -> USB-de bugging
Then check that box, it will make you feel like a boss.
Now once you have done that your android device, is now setup for both development and ADB. Next you are going to plug your device into your computer, via a usb cable.
Once you have done that you need to go to the directory of your ADB interface, this is where you have the android SDK installed too, on a linux or mac based system this could be:
Code:
cd /home/yourusername/android-sdk-mac/tools
Once you have the ADB interface loaded into your terminal, if you type help it will show something similar to 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.
Now that you have ADB running here are some simple commands on how to use it:
How identify that your device is being recognised by ADB:
Code:
adb devices
Once this has been typed it should show something like this:
Code:
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT26GW507639 device
C:\Users\Daniel\Android development\ADB, Fastboot\adt-bundle-windows-x86_64\adt-
bundle-windows-x86_64\sdk\platform-tools>
If there is a line what says "HT26GW507639" with "device" at the end your devices is successfully recognised by ADB!
How to pull data from your device:
Code:
adb -s [yourdeviceADBNUMBERHERE] pull /system /the directory you want it saved too
This command will pull all the files from your devices system directory, to the directory you told it to be saved too.
I did the pull command on a PC and I was able to get all the data from following directories on my Desire C:
/data
/system
How to push data to your device:
Code:
adb -s [yourdeviceserialnumberhere] push /system/app/whatever.apk
This command will push the files you wish to your phone, though this command.
The most basic ADB commands
ADB push, as explained before this command is used to send files to your device
Code:
adb push
ADB pull, as explained before it pulls files from your phone, and makes a copy of them.
Code:
adb pull
ADB Install and example of this code would be "adb install c:\users\app.apk"
Code:
adb install c:\users\app.apk
ADB Shell, this command begins a shell connection to the device on the other end.
Code:
adb shell
ADB reboot, it does what it says
Code:
adb reboot
ADB reboot recovery, this also does what it says
Code:
adb reboot recovery
ADB reboot bootloader, this also does what is says, like the ones above.
Code:
adb reboot bootloader
ADB remount, this remounts the devices file system for editing etc...
Code:
adb remount
ADB Shell commands:
cd, this command changes directories in your devices filesystem.
Code:
cd /system/app
is, this command listes all of the file present in the directory you are at.
Code:
is /system/app
rm, this command removes file from your device.
rm /system/app/whatever.apkcp, this command copies files, and is very similar to the cat command below.
Code:
cp /system/app/whatever.apk /sdcard/whatever.apk
cat, this command is also used to copy files to your device.
Code:
cat /system/app/whatever.apk > /sdcard/whatever.apk
exit, this command exits the ADB shell.
Code:
exit
If any of you are having any problems, read the FAQ first before posting a question in this thread, happy pushing!
If you think any other commands should me added to this section, PM me about it.
Click to expand...
Click to collapse
Hi all and Sorry for my bad English.
I got a Kindle Fire hdx 7 3rd gen and i got it rooted everything was woking good. then i installed an apk called freedom and i used a function called "freecore" id restartedmy kindle and then it got a boot loop stuck, then i was reading that i need to do a hard reset, i charged my kindle fire full charge then press power and hold up volume up until i see the recovery mode with only restart kindle or factory reset options, so i did a factory restore and noting happen still on boot loop stuck i keep reading and i realized than i needed a custom recovery stock something i didn't installed when i rooted my kindle , i got adb installed on pc i tried kindle fire recovery and kindle fire unbrick tool but both software said waiting for device, still when i plug my kindle to pc i heard the sound that win 8 recognized it so please can someone help me or know a threat to a solution thank you .
Do you know what version of the Os you were running?
lekofraggle said:
Do you know what version of the Os you were running?
Click to expand...
Click to collapse
i downgraded 4.5.3 to 3.2.8 i think then updated to 4.5.2 to rooted
lekofraggle said:
Do you know what version of the Os you were running?
Click to expand...
Click to collapse
this is the thread i used http://forum.xda-developers.com/kin...lback-13-3-2-8-rollback-ota-captured-t3046204
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
lekofraggle said:
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
Click to expand...
Click to collapse
i tried command adb devices and it said device offline
That is odd. When I run the command with the device offline, it just prints a blank prompt.
lekofraggle said:
I am sorry, but if you did not enable adb first, you may be out of luck. Try opening a command prompt in your adb folder and type adb devices. See if it shows up.
Click to expand...
Click to collapse
ok i tried again now i got a message that said list of devices attached D0FCA0A04206008K offline
What happens if you try to push a file to the sd card?
lekofraggle said:
What happens if you try to push a file to the sd card?
Click to expand...
Click to collapse
this happened when i used push command
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\hector>cd C:\android-sdk
C:\android-sdk>adb push Copy.GBA/sdcard/
Android Debug Bridge version 1.0.32
-a - directs adb to listen on all interfaces for a c
onnection
-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.
-H - Name of adb server host (default: localhost)
-P - Port of adb server (default: 5037)
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 [-p] <local> <remote>
- copy file/dir to device
('-p' to display the transfer progress)
adb pull [-p] [-a] <remote> [<local>]
- copy file/dir from device
('-p' to display the transfer progress)
('-a' means copy timestamp and mode)
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 --list - list all forward socket connections.
the format is a list of lines with the followin
g format:
<serial> " " <local> " " <remote> "\n"
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 forward --no-rebind <local> <remote>
- same as 'adb forward <local> <remote>' but fail
s
if <local> is already forwarded
adb forward --remove <local> - remove a specific forward socket connection
adb forward --remove-all - remove all forward socket connections
adb reverse --list - list all reverse socket connections from device
adb reverse <remote> <local> - reverse socket connections
reverse specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
adb reverse --norebind <remote> <local>
- same as 'adb reverse <remote> <local>' but fail
s
if <remote> is already reversed.
adb reverse --remove <remote>
- remove a specific reversed socket connection
adb reverse --remove-all - remove all reversed socket connections from dev
ice
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-lrtsd] <file>
adb install-multiple [-lrtsdp] <file...>
- push this package file to the device and instal
l it
(-l: forward lock application)
(-r: replace existing application)
(-t: allow test packages)
(-s: install application on sdcard)
(-d: allow version code downgrade)
(-p: partial application install)
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] [-obb|-noobb] [-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 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.)
(-obb|-noobb enable/disable backup of any insta
lled apk expansion
(aka .obb) files associated with each applic
ation; the default
is noobb.)
(-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 and /vendor (if present) p
artitions on the device read-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, /system, /vendor (if present), and /data pa
rtitions will be updated.
- If it is "system", "vendor" 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:\android-sdk>
lekofraggle said:
What happens if you try to push a file to the sd card?
Click to expand...
Click to collapse
i did it again looks like i missed typed something now i got "C:\android-sdk>adb push Copy.file /sdcard/
error: device offline
C:\android-sdk>"
Does your device show up in Windows explorer or in device manager?
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
It could be that the drivers are not installed correctly, but at this point, I am just guessing. Sorry.
lekofraggle said:
Does your device show up in Windows explorer or in device manager?
---------- Post added at 06:24 PM ---------- Previous post was at 06:23 PM ----------
It could be that the drivers are not installed correctly, but at this point, I am just guessing. Sorry.
Click to expand...
Click to collapse
they dont show on windows explorer but in device manager i got:
kindle fire> Android Composite ADB Intercafe
Portable Devices> MTP USB Device
Okay, I do not think you have the driver loaded correctly. It is a long shot, but you could try uninstalling both devices (unplug your kindle first), then rebooting your computer and plugging your kindle back in. Hopefully, the drivers load okay. Then try adb again.
lekofraggle said:
Okay, I do not think you have the driver loaded correctly. It is a long shot, but you could try uninstalling both devices (unplug your kindle first), then rebooting your computer and plugging your kindle back in. Hopefully, the drivers load okay. Then try adb again.
Click to expand...
Click to collapse
the MTP USB Device got a little yellow triangle and on properties got this message "This device cannot start. (Code 10)
The process hosting the driver for this device has terminated."
Again, you have to remove it. Unhook your device, and uninstall them. Then, reboot and try to let it install.
lekofraggle said:
Again, you have to remove it. Unhook your device, and uninstall them. Then, reboot and try to let it install.
Click to expand...
Click to collapse
i did what told to do unhook it, unistalled and reinstalled then i got this when i push
"C:\android-sdk>adb push Copy /sdcard/
failed to copy 'Copy' to '/sdcard//Copy': Permission denied"
What about dab devices? Also, I think when you push a file, you need to make sure that the file is in the dab folder and the file type has to be valid. E.X.
adb push test.txt /sdcard/test.txt
Or, you could also try adb ls/
lekofraggle said:
What about dab devices? Also, I think when you push a file, you need to make sure that the file is in the dab folder and the file type has to be valid. E.X.
adb push test.txt /sdcard/test.txt
Or, you could also try adb ls/
Click to expand...
Click to collapse
a made a file inside adb folder called text and tried and again same message
C:\android-sdk>adb push text.txt /sdcard/text.txt
failed to copy 'text.txt' to '/sdcard/text.txt': Permission denied
C:\android-sdk>
also when i use adb root i can get into root and i did once adb fastboot reboot-bootloader and my kindle go into fastboot
C:\android-sdk>adb root
C:\android-sdk>adb devices
List of devices attached
D0FCA0A04206008K device
C:\android-sdk>