Database Develop

How To Use ADB Without SDK

Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479

Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot

jcnbama said:
Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479
Click to expand...
Click to collapse
Mini-adb comes with adb.exe, fastboot.exe and two adb .dlls needed to run adb in windows. So basically to run adb all that is required is 3 files. Also fastboot doesn't require anything except the executable. Mini-adb has been out there for about 2 years that I know of on androidforums.

fredericve said:
Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

You can install the Wugs nexus toolkit. It has all the features you need.

eksasol said:
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
That was not necessary on my debian Sid install. Yesterday I simply installed the packages, Co nected my nexus 7 and used adb sideload to flash the kitkat ota.
The steps seem to apply to Ubuntu precise. Maybe it is not necessary in newer versions.

[Q] HTC One M7 in boot loop, advice from other threads not helped.

Hi
I've been at this for a few hours now and I'm just getting nowhere. I know this is a common issue but I assure you I have read every other thread and tried everything I have seen.
I have a HTC One M7 on the UK network Three with CWM recovery. Previously it was running Android Revolution HD, I tried to install the other Android Revolution HD Google Edition and right at the very end when I was asked to install Superuser is where I started running into problems. As it stands, my device is in a bootloop. If I'm careful I can time it right and boot into bootloader. From here, trying to enter recovery just puts me back into a bootloop.
All my HTC Drivers are installed fresh as of today. If I run erase cache, get var or anything along those lines all I get is <waiting for device>. When plugged in the device displays in Device Manager with the following details. I'm on Windows 8.1.I can't post a screenshot so it's text.
Unknown USB device (device failed enumeration)
Device status: Windows stopped because this device has reported problems (code 43)
I can't even find a RUU for my device, if it would even help at this point. Here's a transcript of my bootloader info.
*** TAMPERED ***
*** RELOCKED ***
M7_ UL PVT SHIP S-OFF RH
CID-H3G_001
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Where do I go from here? Bootloader factory reset does nothing, trying to flash a ROM doesn't work because the device isn't recognised, etc. I'm totally lost. The only suggestion I've even found is that I might have more luck in Windows 7, but I only have one system which will take 8-9 hours to back up to an external HD and unless it was a 90%+ shot I want reinstalling Windows 7 to be an absolute last ditch attempt.
Is there anything I'm missing?

Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk

Harish_Kumar said:
Adb n fastboot drivers won't work with Windows 8.1 unless you are on hboot 1.55 or higher
You can try Windows 8 or Windows 7 but if you have ubuntu live cd
Try using it to sideload or push a rom
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've never used Linux but I'll make a live usb stick and try to work it out.

toyfights said:
I've never used Linux but I'll make a live usb stick and try to work it out.
Click to expand...
Click to collapse
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"

Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.

toyfights said:
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.
Click to expand...
Click to collapse
Cool
Sent from my HTC One using Tapatalk

Harish_Kumar said:
Sure
If you are planning to use ubuntu live cd or usb stick..try these
after booting from live usb
open the terminal and type these commands
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
these are needed to install adb and fastboot drivers
and next type this command
sudo gedit /etc/udev/rules.d/51.android.rules
notepad will be opened...copy and paste the below lines in it and save it
#Newman
SUBSYSTEM=="usb", ATTRS{idVendor}=="283b", MODE="0660", OWNER="martijn"
then place the adb folder on the ubuntu desktop
in order to navigate in to it...type this
cd ~/Desktop/adb
now you are good to go
you can use fastboot n adb commands
the only difference is that you have to use "sudo" infront of every command
like "sudo adb reboot bootloader"
Click to expand...
Click to collapse
Got it! Thank you so much.
In case anybody else finds this thread and is in a similar situation, here are my stray observations about the process.
Use unetbootin with Ubuntu 12.04. I wasted 2 hours trying to solve a weird error because YUMI makes live disks in an unusual way.
I couldn't get anything to go in the live disk Ubuntu without granting myself root. Sudo didn't make a difference, "sudo su -" was what got everything going.
I don't know if it made a difference but this advice led me to the official Ubuntu site and the Android SDK when I was trying to fix the YUMI issues and I used their content for the 51.android.rules, just because of the permissions and the vendor ID.
http://developer.android.com/tools/device.html
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"
is what I used.
Once I had ran through the great instructions here and granted myself root, all I had to run was "fastboot devices" which confirmed my device was being recognised and "fastboot cache clear" to enable the device to boot into recovery. After that I switched back to Windows and everything was fine.
IF ONLY BOOTLOADER HAD A CLEAR CACHE FUNCTION.
Thank you again, so much! Great advice.

How to get adb/fastboot working in linux for nexus devices

Hello everyone just thought i would make a thread of how to get adb and fastboot working for those linux users out there like me, especially those who are new to linux like me.
the thread for this is actually on xda
http://forum.xda-developers.com/showthread.php?t=2564453
let me know if the link works ok, its literally as easy as he said it would be in his thread just type or copy and paste the script (first one in thread) to terminal press enter and thats it adb and fastboot works flawlessly for me in linux.
THANK YOU @corbin052198 for making this an easy process for all us nexus/linux users :good::good: top job

setting up adb and fastboot is about the easiest thing you can do. it's a one line terminal command:
$ sudo apt-get install adb && sudo apt-get install fastboot
done. no guide or special tools necessary.

USB Device not recognized in fastboot

I get the error in the title over and over again. When my device is on normally, it is recognized fine. I have tried uninstalling the drivers in device manager, but even that doesn't work. Using Squabbi's toolkit crashes when I try to download the HTC drivers.
Any ideas on how to fix it? I have a 4.1.2 device with 1.44 hboot. Can/should this be updated?
Is it true that there are no drivers for Windows 8? If so, do you recommend a linux VM ?
Thanks

Ubuntu USB boot
Or a windows 7 machine.

SaHiLzZ said:
Ubuntu USB boot
Or a windows 7 machine.
Click to expand...
Click to collapse
To do what? Just whenever I need to use adb functions?

Bilge656 said:
To do what? Just whenever I need to use adb functions?
Click to expand...
Click to collapse
yup, HBOOT 1.44 doesn't work in Windows 8 or above.

Bilge656 said:
To do what? Just whenever I need to use adb functions?
Click to expand...
Click to collapse
ADB should still work. It works in recovery or OS.
Fastboot is what you won't be working on windows 8 and 1.44 hboot

Oh ok. Is there any toolkit for Linux? Any guides?

Bilge656 said:
Oh ok. Is there any toolkit for Linux? Any guides?
Click to expand...
Click to collapse
Here use this guide:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219​Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
If you get "no permissions ?????????" when trying to use adb, type:
Code:
killall adb
Disconnect the phone for a few seconds, then reconnect and type:
Code:
sudo adb devices
adb should now work as normal without the sudo prefix.
Click to expand...
Click to collapse

majmoz said:
Here use this guide:
​
Click to expand...
Click to collapse
Ok so I did all of that, but my device still is not recognized. It is not detected at all in my Windows 8 build as well as my virtual machine of Ubuntu.

Bilge656 said:
Ok so I did all of that, but my device still is not recognized. It is not detected at all in my Windows 8 build as well as my virtual machine of Ubuntu.
Click to expand...
Click to collapse
you have to boot linux from a usb drive or from a live cd, not like a virtual machine like virtualbox or anything similar.

alray said:
you have to boot linux from a usb drive or from a live cd, not like a virtual machine like virtualbox or anything similar.
Click to expand...
Click to collapse
I did that, and at first I plugged it in and it was recognized. Then after awhile, it stopped being recognized all together after some reboots.

adb issues in Linux

I've got 2 linux boxes sitting on my desk, one is running Arch the other Ubuntu 14.04. Both machines are able to detect fastboot mode if I boot it using the stock recovery but neither is able to connect using ADB when booted to system or recovery unless sideload is enabled.
I've seen plenty of posts of people using adb in linux so I'm just trying to figure out what I'm missing. Thanks

For adb when you're fully booting into stock or a rom, do you have adb enabled in developer options?
Sblood86 said:
or recovery unless sideload is enabled.
Click to expand...
Click to collapse
That is how it is suppose to behave. Adb is not active until you select the adb sideload option.
I'm on linux.

Sblood86 said:
I've got 2 linux boxes sitting on my desk, one is running Arch the other Ubuntu 14.04. Both machines are able to detect fastboot mode if I boot it using the stock recovery but neither is able to connect using ADB when booted to system or recovery unless sideload is enabled.
I've seen plenty of posts of people using adb in linux so I'm just trying to figure out what I'm missing. Thanks
Click to expand...
Click to collapse
You can dissect the Linux VM I'm using for adb.
i386 VM http://tinyurl.com/zok3o93
amd64 VM http://tinyurl.com/j75g5ju
It's a bare bones install. Installed only 2 packages, android-tools-adb and android-tools-fastboot, and grabbed the skia tar for adb 1.0.32.
I am running as root when I use adb.
If you happen to be using an x64 kernel, I saw mentioned for adb 1.0.32. One would need to grab the following packages for it to work.
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libstdc++6:i386 libncurses5:i386

thekrakah said:
You can dissect the Linux VM I'm using for adb.
i386 VM http://tinyurl.com/zok3o93
amd64 VM http://tinyurl.com/j75g5ju
It's a bare bones install. Installed only 2 packages, android-tools-adb and android-tools-fastboot, and grabbed the skia tar for adb 1.0.32.
I am running as root when I use adb.
If you happen to be using an x64 kernel, I saw mentioned for adb 1.0.32. One would need to grab the following packages for it to work.
dpkg --add-architecture i386
apt-get update
apt-get install libc6:i386 libstdc++6:i386 libncurses5:i386
Click to expand...
Click to collapse
Long story short I wound up bypassing the need for ADB in the first place. Sorry to have bothered people
I expect it was the fact that I hadn't actually found the option to enable ADB in the settings however.