Well this my first own post on General Section
I am sharing how to use the (ADB)
which seem many of us should have some basic on it
(FASTBOOT) will be added later on.
-SIMPLE & EASY-
Is a proper way to tell what wrong's and bug you encountered by a log
Requirement :
Click to expand...
Click to collapse
-Adb Driver for Xperia X8 or This Universal_Naked_Driver
-Adb files (Repacked for you)
-Android Version 1.6-4.1.1
Click to expand...
Click to collapse
Set Up
Click to expand...
Click to collapse
Install the Driver For Adb for your device (Example :X8)
Unpack the Adb Files To A Folder (Named Whatever you like Example: Adb) on local disk C: (Recommend)
Turn on USB debugging on your phone: Settings>Applications>Development>USB Debugging
Go to Start Menu and Search for CMD (Command Promt) (Run as adminstrator)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Prompt CMD with the location you extracted the ADB Files (Mine at C:/adb)
Therefore key in this
Code:
cd c:/adb
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Check Connected Device & Enable the Adb Server
Code:
adb devices
Wait for few seconds till the server is up and if you connection is working
Should show that the device name is there
If connection is offline should check whether build.prop has this line :
Code:
persist.sys.usb.config=mass_storage,adb
Add this line to build.prop if you need to do so
ADB Logcat
When able to have adb connection between device then you
can now do a pretty simple logcat
Code:
adb logcat > logcatfilename.txt
Replace "logcatfilename" with anything you like and shall log all over the text file
Can then stop logging just pressing Ctrl+C
Enable Access to System
If Encountered that your system not mounted
Code:
adb remount
If some still keeping error then need to boot cwm to adb
ADB Shell
Adb Shell Is A Little Advance So No Really Gonna Cover Up Here
Prompted by
Code:
adb shell
Checking Memory/Swap Progress
Code:
free
You can remove app/files by
Code:
rm -r /filelocation/filename.format
Replace " /filelocation/filename.format" with anything you want to remove such as latimime.apk so you replace with /system/app/latimime.apk
Adb Pull
Now You Should Know To Command using CMD
To Pull
Code:
adb pull /system/app/browser.apk
Replace "l/system/app/browser.apk" with location and file name you want to pull
Adb Push
Now You Should Know To Command using CMD
To Pull
Code:
adb push browser.apk /system/app
Replace " browser.apk /system/app" with file name(On the same folder of the adb files) & location you want to push that file into.
Adb Install
Should be same as pushing method but normally to data folder
Code:
adb install angrybird.apk /data/app
Replace "angrybird.apk /data/app" with file name(On the same folder of the adb files) & location you want to install into
Final :
I hope this Tutorial Is Clear Enough For Other's member which want to
learn adb.You can use this tutorial & i know there many more better adb tutorial
but i am just showing basic knowledge logcat and adb command that can easier
both developers and user.Any Comment & Suggestion can reply below.
I will fix/add if needed.Sorry for bad english & grammar
Credits :
Dev Whom Teached Me Basic Adb
1wayjonny For Universal Naked Driver
pswd
What password for ADB archive?
nikmaletz55 said:
What password for ADB archive?
Click to expand...
Click to collapse
steriod << Password Sorry for missed out
Fastboot tutorial when there's free time :cyclops:
I can't download the GingerLewa.
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
fastboot...i think we dont have fastboot
sgt. meow said:
@^
this isn't the appropriate thread.
@Steriod
didn't know our phones had fastboot protocol suport, or did you just make the guide in general?
Click to expand...
Click to collapse
fotak-x said:
fastboot...i think we dont have fastboot
Click to expand...
Click to collapse
i make this for adb for X8 & Other phone as well
i know there no fastboot but maybe usable for otheer phoness
Related
Hey, did a search but couldnt find a solution. I'm having problems getting my device to pull up in adb remount on Ubuntu. When I try remount it says no command 'adb' found sometimes or permission denied when it does work, I have root and USB debugging enabled on the devices (a Nexus One and G1). When I try adb devices I just get ?????????????? unknown.
Also, and I don't know if it's related, but in Eclipse, I can't get the SDK location loaded, I have the directory right, but when I hit Apply or OK nothing happens, it just doesnt load. So if I try to start a project I have no Build Targets to select from.
Any help would be appreciated. I have everything running fine in Windows but I'm fairly new to Linux I haven't used it in years. I'm running Ubuntu distro if that matters. Thanks.
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Hello,
The problem with linux having trouble with adb probably lies with a permission issue try adb kill-server && sudo start-server.
The other issue is most likely because you did not download any targets yet. goto windows in eclipse and select android sdk and adv, then at available packages or something like that download your target
i can't even get that far. i switch to my androidSDK/tools and then "adb devices" all i get is 'no command adb found'
I did the first couple times too, then I went to command and did:
su
<enter password>
cd
export PATH=${PATH}:<your_sdk_dir>/tools
then when I adb remount or adb devices it gives me the unknown device thing
but I think the next secret is here
http://forum.xda-developers.com/showthread.php?t=613217
in like the 3rd post. However I think the export PATH is a temp fix because the ~/.bashrc needs to be modified with the path settings and I have no idea how to do that. I just get lots of permission errors or file not found for everything I try, even with root. I'm just using Eclipse in Windows for now, and hopefully someone can help us out cause I'd like to work on roms but I guess I need to brush my Linux up first.
http://forum.xda-developers.com/showthread.php?p=5377103
i found some help elsewhere on the net, and posted it up at the end of this thread. they were having similar issues with the dream, apparently.
i also found this
that link there will probably get you hooked up
adb devices now has a readout!
and, you're right about adding the export PATH=${PATH}:<your_sdk_dir>/tools to
~/.bashrc
i think this command will do it. run in terminal
gksudo gedit ~/.bashrc
i just made a comment line that says
# android sdk export path
and another line underneath it that says
export PATH=${PATH}:/home/timmyd/androidSDK/tools
because that's where i have the extracted sdk
all good, i think. now, let's see what's going on ...
oh yeah, don't forget to enable usb debugging on the device itself.
settings>applications>development
allow usb debugging
screeny works at least
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cool, I'll try that out tomorrow.
timothydonohue said:
i'm with you. i picked up the android sdk tarball, and am a little lost too . i tried getting adb to work in windows 7, but i can't get that going either. dangit. if someone could put up some good reference material, it'd be appreciated
Click to expand...
Click to collapse
Hi all!!!!
I have a problem with my HTC Tattoo, can't connect the tatto with adb in ubuntu and eclipse Helios.
/android-sdk-linux_86/platform-tools$ ./adb devices
List of devices attached
???????????? no permissions
Thank you very much.
Hi, I have tha same problem with ????? and can't connect to eclipse my galaxy, so the solution is just use the instructions from the h**p://developer.android.com/guide/developing/device.html
I solve this problem with
1. Log in as root and create this file: /etc/udev/rules.d/51-android.rules.
For Gusty/Hardy, edit the file to read:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
For Dapper, edit the file to read:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
2. Now execute:
chmod a+r /etc/udev/rules.d/51-android.rules
Click to expand...
Click to collapse
The USB Vendor IDs foreach manufacturer
Manufacturer USB Vendor ID
Acer 0502
Dell 413c
Foxconn 0489
Garmin-Asus 091E
HTC 0bb4
Huawei 12d1
Kyocera 0482
LG 1004
Motorola 22b8
Nvidia 0955
Pantech 10A9
Samsung 04e8
Sharp 04dd
Sony Ericsson 0fce
ZTE 19D2
Click to expand...
Click to collapse
Hope to help you!
This has obviously been covered in DagentooBoy's thread - which is great.
http://forum.xda-developers.com/showthread.php?t=761045
But I tried it and it doesn't work, even with the SGS Unlocker, tried the WinXP (PC way) first.
The version I'm running is Android 2.1 update 1.
I get this when I try running it through the PC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sometimes when I turn my phone on I get asked to enter the SIM pin, but I hit DISMISS and get into the phone. The next screen says "Phone Locked", but I swipe and enter the phone.
Will buying an unlock code from one of eBay unlockers work or not?
I feel like I bought a brick here. lol
Anyways, any input would be greatly appreciated. I'm not looking to do anything else to it other than unlock and use it for now. While I'm fairly competent with doing this tech-stuff, the Android stuff is a step above for me, so I wanna take my time to learn this all.
It's my first smartphone after using a Nokia 6265i for the past 5 years.
http://en.wikipedia.org/wiki/Nokia_6265 lol
So for me this phone is a treat as is, if only I can get it unlocked.
Thanks for your help and input.
It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.
chui101 said:
It's because adb can't get to the file without root. Happened to me too. I just manually copied the nv_data.bin over to my computer using the standard usb mass storage and ran sgux on it.
Code:
C:\androidsdk\tools>adb shell
/ $su
#cp /efs/nv_data.bin /sdcard
#exit
#exit
then mount the usb storage, copy over the nv_data.bin to the folder with sgux.exe in it (i put mine in c:\androidsdk), then:
Code:
C:\androidsdk>sgux nv_data.bin
and with any luck you'll have it.
Click to expand...
Click to collapse
Okay, I understand a bit. but I'm not sure what all the coding is all about and how/what to do. You copied nv_data.bin from your phone to a location on the computer?
I set my Vibrant to mass storage and while it's not showing on MyComputer anywhere, the only thing that pops up is the microSD card with the movie on it.
Correct... instead of androidsdk it would be wherever you saved it..
Having one hell of a time accessing my phone via the computer.
It's connected, but no icon to click open or anything of the sort (inside MyComputer)
Ok, this is what I have on my screen now.
No EFS folder, no nv_data.bin, anywhere in the folders.
You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.
lralexl said:
You need to use root explorer or adb(maybe astro) for access to your internal system directories. Just pull the file using adb like chui mentioned. If you aren't familiar with adb then I suggest you read up in the Vibrant bible.
Click to expand...
Click to collapse
Wanna suggest a link to this almighty Vibrant Bible?
Well I just looked through it and there doesn't seem to be a thread specifically about adb file system actions.
Just open a command prompt and "cd" to your android sdk tools folder.
example: cd c:\sdk\tools
type:
adb shell
su
cp /efs/nv_data.bin /sdcard
exit
adb pull /sdcard/nv_data.bin /nv_data
that should get nv_data.bin into your tools folder under the folder nv_data. then just move the nv_data.bin into the sgux.exe folder
I'll try this now, thanks Iral.
Trying to type what you put, I can't remember for the life of me how to enter multiple command lines in command prompt. Hitting ENTER executes the first line. But I'm supposed to type all that out correct?
One line at a time
Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.
koooba said:
Well, I installed the SDK toolkit, updated Java, done everything possible.
Been diligent and patient with this, but this Galaxy phone is about to enter the Galaxy.
Just typing adb shell (the first command) and I get this.
Click to expand...
Click to collapse
Post the output of ls err ...
Code:
dir
Not following LQ, sorry?
koooba said:
Not following LQ, sorry?
Click to expand...
Click to collapse
The screenshot you've taken when you executed adb, go to the same folder (tools) and execute dir in MS-DOS window.
Need to see if adb.exe is there.
I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder
koooba said:
I hope this is the one you mean.
I reinstalled SDK into c:\androidsdk and this was found in the \platform-tools folder
Click to expand...
Click to collapse
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices
lqaddict said:
what happens when you connect your device to the usb port (usb debugging is enabled i presume), open the command prompt on your pc and issue
Code:
cd c:\androidsdk\platform-tools
adb.exe devices
Click to expand...
Click to collapse
This happens (seems like it's good)
Good,
now try
Code:
adb.exe shell
And what was the original post about ?
lqaddict said:
Good,
now try
Code:
adb.exe shell
And what was the original post about ?
Click to expand...
Click to collapse
lol ya.
Well it runs, but it seems to stop with a blinking cursor after the $
Hello all I am trying to cut my teeth on Linux. (UBUNTU 11.10) I have been able to install android sdk on the pc and I think I have everything set correctly but when I issue the adb devices command I get the following output:
List of devices attached
???????????? no permissions
I have already created the file named "adb_usb.ini" in the .android folder and it has the following 3 lines:
0x1949
0x2080
0x18d1
When I do a cat command on the adb_usb.ini file it returns the above lines so I believe it is correct.
I know it is something I am doing wrong but can anyone help point me in the correct direction.
Thanks
Edit Added Info: not sure if this will help but here is a screen dump of what commands I am using and what they return. Thanks Again..
[email protected]:~$ adb kill-server
[email protected]:~$ adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~$ adb devices
List of devices attached
???????????? no permissions
[email protected]:~$ cat ~/.android/adb_usb.ini
0x1949
0x2080
0x18d1
[email protected]:~$
Rodhargis said:
Hello all I am trying to cut my teeth on Linux. (UBUNTU 11.10) I have been able to install android sdk on the pc and I think I have everything set correctly but when I issue the adb devices command I get the following output:
List of devices attached
???????????? no permissions
I have already created the file named "adb_usb.ini" in the .android folder and it has the following 3 lines:
0x1949
0x2080
0x18d1
When I do a cat command on the adb_usb.ini file it returns the above lines so I believe it is correct.
I know it is something I am doing wrong but can anyone help point me in the correct direction.
Thanks
Click to expand...
Click to collapse
This post helped me...
http://forum.xda-developers.com/showthread.php?t=1475740
I'm guessing you haven't done the middle part of that post.
kinfauns said:
This post helped me...
http://forum.xda-developers.com/showthread.php?t=1475740
I'm guessing you haven't done the middle part of that post.
Click to expand...
Click to collapse
Thank You; That is a different link than the one I was working off and so I missed the middle part, I am pretty sure this will fix my issue. I will try and report back if it worked so my thread can be closed.
Thanks Again for pointing me in the correct direction.
Rod
Stop for tonight start fresh tomorrow
Thanks for your help but I have to be making some stupid mistake. been up for about 26 hours so need to hit the sack.
I thought I followed the command to the letter but when I added the rule to 51-android.rules and rebooted, from then on when I ran the adb devices command it would not return anything after the line "List of devices attached". once I removed the new rule I created it would return the line "???????????? no permissions"
So will try again fresh tomorrow.
Rod
Agree with above
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
just type
sudo adb kill-server then enter.
sudo adb start-server then enter.
adb devices
you will see your kindle fire serial number.
im useing linux and think the start (sudo) maybe different on windows.
hope this helps
Sent from my Kindle Fire using xda premium
Just a quick mention to say I had this issue and the link provided helped me resolve the issue so thanks for the response kinfauns.
Hello Everyone and Welcome to the ADB Multi-Tool thread by me
Why i created this??
I believe we are all tired of typing into cmd to launch adb commands
So i created this tool to simplify our daily live and time typing and sometimes, making eror while typing
Basically its just simple having to press numbers to sideload files then typing the whole sentence in cmd
Features of this ADB Multi-Tool
Has nearly all you need
ADB Install
ADB Push
ADB Sideload
ADB Pull
ADB Reboot and reboot recovery
*new ADB Logcat
*new ADB new file selector
Addon : Able to change promt font color
Coming features
Targeted for xperia devices with the ADB fastboot feature ( In progress testing )
Lots more unimaginable features comingggg
Screenies :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
ADB Multi-Tool v2
Thanks - Credits
To Google for providing info on bat commands and their adb.exe
Windows for their command promt
Think I left you out or this is a copy of your work? PM me
Tutorials?
Tutorial on how to use
Extract the folder in zip to anywhere
Open it up and start ADB Multi-Tool.bat
Firstly add your files into the root of the folder
You can either select the file by entering option 5
( For ADB pull only in next release ) Type the file name exactly when asked for instance nFc.apk ( Case sensitive and file extension .zip .apk or .xxx needed )
Hey press what u want to do with that file
Bravo it should says done
What is needed?
Your device drivers of course
Some brains
Changelog and FAQ
Code:
[U] Version 1 [/U]
Initial release
[U]Version 2[/U]
UI redesign
File selection made easier alot
Added logcat
F.A.Q
Q : Hey it says cant find 'x' to install but i was sure i typed the file name correct
A : Make sure the file is in the root directory and make sure u added the file extension behind x.apk
Q : Hey eror: device not found
A : Make sure your device adb debugging mode is enabled in your developer options and your phone is connected
Q : It says what xxxxx permission denied?
A : Well make sure ADB permission is enabled in developer option or your su app, allow unknown install in security too
Q : Promt fc when I try to install or push the file, well i was sure i selected the file before doing so
A : Yes you did, but i am sure the file u selected contains spaces eg google camera.apk
Rename it to googlecamera.apk and I am sure it wont fc
Q : Hey I launch ADB logcat and i pressed any key, why nothing comes out? How do I stop it?
A : Well logcat is running, unless it says waiting-for-device, then you have to check your drivers properly. To stop logcat just press ctrl+c
Find your logcat.txt in the folder
Well many more are coming soon, so stay tuned
I made this tool to make adb commands quicker and easier to carry out, as I use adb a fair bit. It's similar to this one but I wanted to include some different functions and put more focus on the hassle free installation of adb on various Linux distributions.
It's a simple script that has the most useful adb commands in a menu format. I also added an adb installation menu which automatically detects what system you have and installs the correct package and it's dependencies. Not every system is supported yet but I'll add more in time.
Code:
[I]I am not responsible for any damages caused by your use of this tool.
Please do some research if you are unsure of anything.[/I]
Features:
Installs adb and configures udev rules.
supports ubuntu, debian, mint, suse, redhat, fedora, centos, elementaryOS, Mageia
Adb over network
Manages files into organised directories
Reboot menu
Pull, push, sideload, shell
Logcats and system dumps
Install and uninstall apps
Unlock bootloaders
Remotely take screenshots and create screen recordings
Full adb backup and restore
More to come
Download Link
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
Extract file anywhere in your home directory
cd to the same directory as ezy-adb.sh
Open a terminal and change permissions with this command:
Code:
$ chmod 755 ezy-adb.sh
Run the script with:
Code:
$ ./ezy-adb.sh
Thanks to @raziel23x. I learned a lot from studying his apktool script.
Enjoy
Changelog
28/09/15
Initial release
29/09/15
Added diagnostic tools sub menu with dumpsys fuctions
merged log and log dump into diagnostic tools
30/09/15
Added option adb over network
Added option uninstall package
04/10/15
Merged reboot functions into a sub menu
10/10/15
v1.3
Script now scans for a connected device before executing commands
Date in (y,m,d,H,M,S) added to screenshot name
y, H,M,S added to date on screen recording name
Bug fixes
Minor ui tweaks
25/11/15
v1.4
Install adb now supports elementaryOS and mageia
Bug fixes
23/12/15
v1.4.1
Fixed derp on adb install
Art Vanderlay said:
I made this tool to make adb commands quicker and easier to carry out, as I use adb a fair bit. It's similar to this one but I wanted to include some different functions and put more focus on the hassle free installation of adb on various Linux distros.
It's a simple script that has the most useful commands in a menu format. I also added an adb installation command which automatically detects what system you have and installs the correct package and it's dependencies. Not every system is supported yet so i'll add more based on feedback.
Features:
Installs adb and configures udev rules.
supports ubuntu, debian, mint, suse, redhat, fedora, centos
Manages files into organised directories
Reboot menu
Pull, push, sideload, shell
Logcats and dump files
Install apk's
Unlock bootloaders
Remotely take screenshots and create screen recordings
Full adb backup and restore
More to come
Instructions:
Extract file anywhere in your home directory
cd to the same directory as ezy-adb.sh
Open a terminal and change permissions with this command:
Code:
$ chmod 755 ezy-adb.sh
Run the script with:
Code:
$ ./ezy-adb.sh
Download Link
ezy-adb.sh.tar.gz
Thanks to @raziel23x. I learned a lot from studying his script.
Enjoy
Click to expand...
Click to collapse
I've always wanted an easy way to install adb and config udev rules on Ubuntu but i just couldn't so i had to switch to BBQLinux. But now i don't have to :laugh: Thank you bro.
kirito9 said:
I've always wanted an easy way to install adb and config udev rules on Ubuntu but i just couldn't so i had to switch to BBQLinux. But now i don't have to :laugh: Thank you bro.
Click to expand...
Click to collapse
No worries Glad to help.
Nice work m8
Thanks buddy :good:
good job man
in this way it will not be necessary to rename screenshots
adb shell screencap -p | perl -pe 's/\x0D\x0A/\x0A/g' > ~/EZY_ADB/ScreenShots/$(date '+%Y%m%d%H%M%S').png
thanks
asmanao said:
good job man
in this way it will not be necessary to rename screenshots
adb shell screencap -p | perl -pe 's/\x0D\x0A/\x0A/g' > ~/EZY_ADB/ScreenShots/$(date '+%Y%m%d%H%M%S').png
thanks
Click to expand...
Click to collapse
Cheers. That'll make things easier
nice job man, thannks! Your tool makes my nerding easier :laugh:
Thanks, bro, It's Really Helpful