[Q] Mac OSX - ADB - List of devices attached Blank - Kindle Fire General

I am running on a Mac (OSX Lion) and have installed android-sdk-macosx.
I am trying to connect to a Kindle Fire 6.2.2
However, this is as far as I can get:
Code:
bash-3.2# ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
bash-3.2#
As you can see, no devices show up.
I have tried switching cables, USB ports, reboot the device and my machine... banging my head against the wall.
Nothing works.
I have read about 29 pages of posts through this forum, and Googled it.
No dice.
Any suggestions?

would not use the sdk at all - if you use the mac/linux version of kfu you save a lot of time and space - you don't need to use kfu if you don't like to - but all commands you'll ever need are in the tools folder of kfu - it also includes drivers and setup scripts - maybe give it a try:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653

mkdir ~/.android
echo 0x1949 >> ~/.android/adb_usb.ini
ADB needs this entry to see the Kindle Fire no matter what OS you're on.

right - there is also a installation script for this included in the pack - install.sh if i remember right

took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help

as far as i know (don't own a mac) you have to call the commands with
./ from terminal window - eg ./run.sh

I also got the same error message at line 84 running the install script in OSX 10.6.8
-E

it's from eratosthene - give him a pm - i'm shure he can help you
http://forum.xda-developers.com/member.php?u=1616763

Try remove the usb driver from your device and re-install gain.

I use Kindle_Fire_Utility_MacLinux_0.9.2 3 with adb.mac
and its located right inside my root directory (not under users) step before.
I went to the files and I opened file called
install_drivers.sh
I did deleted everything behind -p and just dragged
the adb_usb.ini (its located in drivers) into that install_drivers.sh script and I hit save.
thats how it looks like
mkdir -p /Kindle_Fire_Utility_MacLinux_0.9.2 3/drivers/adb_usb.ini/adb_usb.ini
Than I just run adb.mac and all is operational
my kindle was rooted with burittoroot2
If you need those files send me a pm I have them in my dropbox.
somboonr said:
Try remove the usb driver from your device and re-install gain.
Click to expand...
Click to collapse
there is no uninstalling drivers like in windows.

line 84 SOLUTION
Incarnate609 said:
took the advice above and it's still not working for me. i have the same exact problem. when i try to run install_drivers.sh i get:
cp: drivers/adb_usb.ini: No such file or directory
Done!
logout
[Process completed]
When I run KFU i get:
/Users/donaldclark/kfu/run.sh: line 84: seq: command not found
please help
Click to expand...
Click to collapse
Regarding the "run.sh: line 84: seq: command not found", I found out that the "seq" command is not recognized with MAC OS... so I did a search and replace, replacing "seq" with "jot -". Now it works.
Reference: Search google for seq and mac

What worked for me.
I had the same problem after updated the sdk on my MacBook Mac OSX 10.6.8
cd to the tools directory (where android program is located)
run:
./android update usb
./android update adb
then edit the ~/.android/adb_usb.ini file and add 0x1949 as the last line (your previous adb_usb.ini file is overwritten by the above commands).

Related

[Guide] ADB with Galaxy S in Ubuntu *Updated 9-10-10*

I still see a lot of people having trouble with ADB in ubuntu, so here is quick guide for anyone still having trouble.
The guide is located HERE and also can be viewed on post #12
*Updated 9-10-10* Thanks to xipher_zero for his very quick and easy guide (Much better than my original).
Hope this helps some people having issues.
If I install unbuntu it overrides my win7 correct?
Sent from my SGH-T959 using XDA App
Oh my!! I've been searched for this guide for a long time Thanks you so much MR.the3dman
Wykedx
Oh boy... where to get started. You could install Ubuntu without overwriting your W7 installation. Then you would "dual boot" your computer. As it boots up, you choose which OS to load. Or of course you could install Ubuntu on a computer by itself.
You don't need to install Ubuntu just to use ADB. ADB runs on both Win and Linux. What is it that you are trying to do? If you just want to learn linux, then make yourself a live CD and you won't have to worry about overwriting any operating systems.
But this is not a linux forum. If this is something that you are interested in, then google is your friend.
if you are interested in trying ubuntu, you might check this out: http://wubi-installer.org/. or just run a LiveCD, as already suggested.
Do you happen to have a HTC??
My output of lsusb:
Code:
Bus 002 Device 002: ID 04e8:681d Samsung Electronics Co., Ltd
Shouldn't /etc/udev/rules.d/51-android.rules contain 04e8 instead of 0bb4?
And no, even that didn't help me. I'm on Ubuntu Lucid Lynx 64 bit.
fantasyzer said:
Do you happen to have a HTC??
My output of lsusb:
Code:
Bus 002 Device 002: ID 04e8:681d Samsung Electronics Co., Ltd
Shouldn't /etc/udev/rules.d/51-android.rules contain 04e8 instead of 0bb4?
And no, even that didn't help me. I'm on Ubuntu Lucid Lynx 64 bit.
Click to expand...
Click to collapse
Thanks for noticing that! I have updated the rules with the correct ones. I have an htc also and uploaded the wrong rules. I am also on Ubuntu Lucid 64 bit and this is what worked for me. I also have done this on my netbook which runs 9.10 so I am really not sure what the issue is then. Did you use ADB from the sdk or from the app inventor adb in the guide?
If I read correctly when browsing for this topic, your instruction is to drop in these rule files, and then run adb using sudo
When using sudo to run adb, it'll always work, regardless of what's in your rules file
If you have your rules file correct, you don't need to do sudo adb
Just adb will work fine
animefans said:
If I read correctly when browsing for this topic, your instruction is to drop in these rule files, and then run adb using sudo
When using sudo to run adb, it'll always work, regardless of what's in your rules file
If you have your rules file correct, you don't need to do sudo adb
Just adb will work fine
Click to expand...
Click to collapse
I did try this, I removed my rules and reloaded my udev folder then tried adb with sudo and it was a no go (I get nothing listed under the list of devices). Also the only way I could get adb to recognize anything without sudo was by adding a line in the rules making my user as the owner, but even still without sudo under devices I get ???????????? no permissions. With sudo and the rules everything works fine which is why I wrote the guide that way.
If you don't want to run ADB as root you can follow the steps in this post
http://forum.xda-developers.com/showpost.php?p=7282335&postcount=4 - FOR SAMSUNG ONLY DEVICES!!!
after you installed SDK.
I also have adb in my path so I do not have to be in the tools directory, and can execute it from anywhere
In my .bashrc file (if you are using bash shell)
Code:
export PATH=$PATH:/path/to/android-sdk/tools
Thanks the3dman for the guide. Unfortunately I am still having problems as when I run the sudo ./adb devices nothing is listed. I followed the directions step by step and also confirmed my Vibrant is in debug mode (also confirms on the phone it is in debug mode when connected via usb. I even rebooted everything again, double checked everything and still no devices listed. I am running Ubuntu 10.04 Any ideas? Thanks so much!
-mG
Four Step ADB installation in Ubuntu
Here is a simple guide without using custom debs:
1. Download the SDK:
wget dl.google.com/android/android-sdk_r07-linux_x86.tgz
2. Extract the archive to the current directory and move into the extracted directory.
tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86
3. Move the "tools" folder to your local system folder:
sudo mv tools /usr/local/share/android-tools
4. Create a symbolic link to the adb executable:
sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/
Done!
from a terminal type:
sudo adb devices (This will start the server and search for connected devices)
Are you running Ubuntu 64bit? If so you need to make sure that you have the 32bit compatibility libraries installed. From the command line run the following:
sudo apt-get install ia32-libs
This will allow you to run 32bit apps in 32bit mode. Not sure if this is whats causing your issue, but it might be worth a shot.
xipher_zero: Thank you, I followed your steps and it is working now.
Oh, I am running 32bit Ubuntu so that was not the problem.
lqaddict said:
If you don't want to run ADB as root you can follow the steps in this post
http://forum.xda-developers.com/showpost.php?p=7282335&postcount=4 - FOR SAMSUNG ONLY DEVICES!!!
after you installed SDK.
I also have adb in my path so I do not have to be in the tools directory, and can execute it from anywhere
In my .bashrc file (if you are using bash shell)
Code:
export PATH=$PATH:/path/to/android-sdk/tools
Click to expand...
Click to collapse
This is not working for some people that is what is being figured out. I am in the process of updating my guide and the new and better one should be up shortly.
xipher_zero said:
Here is a simple guide without using custom debs:
1. Download the SDK:
wget dl.google.com/android/android-sdk_r07-linux_x86.tgz
2. Extract the archive to the current directory and move into the extracted directory.
tar xvfz android-sdk_r07-linux_x86.tgz && cd android-sdk-linux_x86
3. Move the "tools" folder to your local system folder:
sudo mv tools /usr/local/share/android-tools
4. Create a symbolic link to the adb executable:
sudo ln -s /usr/local/share/android-tools/adb /usr/local/bin/
Done!
from a terminal type:
sudo adb devices (This will start the server and search for connected devices)
Click to expand...
Click to collapse
This version worked well also! Thanks its much shorter and easier than my method.
MrGibbage said:
Wykedx
Oh boy... where to get started. You could install Ubuntu without overwriting your W7 installation. Then you would "dual boot" your computer. As it boots up, you choose which OS to load. Or of course you could install Ubuntu on a computer by itself.
You don't need to install Ubuntu just to use ADB. ADB runs on both Win and Linux. What is it that you are trying to do? If you just want to learn linux, then make yourself a live CD and you won't have to worry about overwriting any operating systems.
But this is not a linux forum. If this is something that you are interested in, then google is your friend.
Click to expand...
Click to collapse
thanks for the response, and sorrry i didn't see this before lol,
what i am trying to do is be able to use adb, at the moment I can't seem to use it because my default.prop is not correct so i heard i have to use linux to be able to edit my default prop...when i try to adb push or remount i get permission denied and yet I have superuser permission and everything.
do you have to root your phone while being an administrator on the computer?
Wykedx said:
thanks for the response, and sorrry i didn't see this before lol,
what i am trying to do is be able to use adb, at the moment I can't seem to use it because my default.prop is not correct so i heard i have to use linux to be able to edit my default prop...when i try to adb push or remount i get permission denied and yet I have superuser permission and everything.
do you have to root your phone while being an administrator on the computer?
Click to expand...
Click to collapse
Try putting your phone in clockwork recovery then issuing the adb commands, and yes your phone has to be rooted.
Thanks for the excellent how to, however...
I've still got a problem:
after "sudo adb devices" (step 5) I always get this message:
List of devices attached
??????????? no permissions;
while "lsusb" gives me that:
Bus 002 Device 007: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
so how can I solve this?
(Kubuntu 10.10 is my current os)
RiverTam said:
I've still got a problem:
after "sudo adb devices" (step 5) I always get this message:
List of devices attached
??????????? no permissions;
while "lsusb" gives me that:
Bus 002 Device 007: ID 04e8:681c Samsung Electronics Co., Ltd Galaxy Portal/Spica Android Phone
so how can I solve this?
(Kubuntu 10.10 is my current os)
Click to expand...
Click to collapse
you'll need to edit a usb rule to "look" for the samsung phone. i forgot what file to edit and what to put in there, once i find the file, i'll post it from my laptop.
EDIT: lol, i found it.
http://forum.xda-developers.com/showpost.php?p=7343021&postcount=1

adb remount operation not permitted

Hey Guys,
I Clockwork3'd my Aria, but I wanted to update my sources (thread 730398) so I can get non market apps. When I follow the instructions in that post I get an error:
Code:
./adb remount
remount failed: operation not permitted
'adb devices' does show my Aria's SN, I'm su'd and I'm running in debug mode. I also chowned everything in the android sdk tools and its subdirectories.
Here's the question -
In searching, I found (thread 614645) that suggested ro.secure wasn't set properly, and sure enough if I do:
Code:
./adb shell
$ getprop ro.secure
1
$
Shouldn't applying clockwork have set that properly? Would the instructions at (thread 8041739 post 9 ) be the right steps to resolve this on an Aria?
Thanks!
PS - sorry I can't post direct links.
if you have all the drivers installed, it should work...
which OS are you using?? (Mac, Win7, etc)
dont rund SDK command in Clockwork, with phone on connect data cable and select "charge only" when asked.
the ./ command is used for Linux i think, i never got that command to work either. just go to the folder where SDK/Tools is located in CMD prompt or Terminal(depending on the OS) and run the following command:
adb remount
hope this helps a bit
I had a lot of issues with driver installs on Windows 7, so I'm doing this on a netbook with Ubuntu netbook remix. Also tried the reflash CD, similar issue.
Right, so with Ubuntu, and the cable my phone came with (have tried a few others just in case)
1. phone on and operational
2. plug in to laptop
3. phone gives happy USB connected and Charge Only notifications
4. fire up terminal window, and su
5. type ./adb remount
and I get the error above. If I do kill-server to refresh it, I get the demon starting successfully on port 5037.
Yeah, I was hoping I'd just missed something stupid. Should I need to modify the boot.img file outside of what Clockwork did?
My symptoms match those described in thread 685146 post #3, however, I've only applied Clockwork (which seems to work) not done anything else funky.
I have my windows 7 machine at the same point now -
adb remount gives 'remount failed: operation not permitted'
and
getprop ro.secure at the adb shell returns 1.
I think this means there's something wrong on the phone, if both machines act the same.
One other data point, I noticed the new Superuser Permissions app that installing clockwork gave me is asking to give superuser permissions to /system/bin/sh when I try to run the adb shell, but it doesn't trigger that when I do the adb remount.
Not sure what this means, any ideas most welcome - TIA!
steps here fixed it, thanks - http://forum.xda-developers.com/showthread.php?t=730398

[GUIDE] Root Kindle with 6.2.1 using JCase method

These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit

Guide: Simple sideload OTA update to KitKat

After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows *see end of post*). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers *see end of post*) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android platform tools from the SDK installed on your Mac:
http://developer.android.com/sdk/index.html
Note: the only platform tool you need to sideload is adb.
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/p....signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and tap the volume up button (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. Open a terminal window on your Mac and type "adb devices". Terminal will identify your nexus 7.
b. Type "adb sideload ". Don't forget the space.
c. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
* Windows 8.1 x64 drivers, thanks to sahilcc7: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Command not found
xdhall said:
After seeing so many people get hung up on complicated guides to manually update to 4.4, I thought I'd write the simple guide during my next bout of insomnia. So, no sleep tonight for me means a new guide for you. It's very simple, with only four steps: 1) download the OTA update, 2) reboot into recovery, 3) prepare to sideload, and 4) sideload.
Preamble:
I use a Mac. My Nexus 7 2013 is WiFi only (flo). This guide is written from that perspective.
It's just as easy to do this from any computer you'd like (e.g. Linux, Mac, or Windows). The commands are exactly the same. The only difference is the way you install the android SDK (+/- USB drivers) and open a terminal or command prompt on your machine of choice. Learning this is simple and necessary for ANY developing, hacking, rooting, unbricking on ANY ANDROID DEVICE.
Three things you need to have set up before starting
Other than being stock, the other items on this list are going to come in handy if you want to fully realize the potential of your nexus device, so take a minute and set it up if you haven't already.
1. NEXUS 7 2013, build number JSS15R, with STOCK ROM. The guide is written from the perspective of STOCK RECOVERY, but it's been done from TWRP (I swear to god). Yes, you can be any combination of rooted, unrooted, locked, unlocked, but if you're rooted, you should probably revert any changes you've made to system files before starting.
2. Up to date android SDK installed on your Mac:
Follow instructions here: http://developer.android.com/sdk/index.html
3. USB debugging enabled on your Nexus 7:
Settings, About tablet, tap build number a bunch of times to enable developer options, back out to settings, developer options, check USB debugging
THE ACTUAL GUIDE:.
STEP 1 (DOWNLOAD):
This is the second hardest step in this guide. You have to download the OTA, not the factory image, so, on your Mac, download this file: http://android.clients.google.com/packages/data/ota/google_razor/3a3951e8243c82bc01a620ab858f4454c8ebd65c.signed-razor-KRT16O-from-JSS15R.3a3951e8.zip
STEP 2 (REBOOT INTO RECOVERY):
a. Hold the Power and Volume down buttons at the same time to enter fastboot mode.
b. Find and select "Recovery Mode" using the volume and power buttons
STEP 3 (PREPARE TO SIDELOAD):
a. Connect your N7 to your Mac with a USB cord
b. While in recovery mode, hold the power button and volume up button down (this is the hardest part of the guide).
c. Select "apply update from ADB"
STEP 4 (SIDELOAD):
a. In the terminal window on your Mac, type "adb sideload "
b. Open a finder window and find the file you downloaded in step 1. Drag and drop it to your terminal window. Press enter.
VICTORY!
Click to expand...
Click to collapse
I downloaded the SDK file for Mac and set up the Eclipse app. However I get a "Command Not Found" when I try to type into Terminal? I appreciate seeing instructions for a Mac; thank you.
Make sure you're connected with a microUSB. Type "adb devices" in terminal to verify that you're hooked up.
Sent from my Nexus 7 using Tapatalk 4
Also, be sure there's a space between the word sideload and the file name that shows up after you've dropped the zip onto the terminal window.
Sent from my Nexus 7 using Tapatalk 4
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
---------- Post added at 02:24 AM ---------- Previous post was at 02:21 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
You can use Mini ADB and Fastboot Installer from xda too, just 2mb. I used it.
Sent from my Nexus 7 (2013)
bobng said:
That's another problem I'm having my files automatically unzip. I'm looking to find out how to stop that from happening.
---------- Post added at 02:21 AM ---------- Previous post was at 02:12 AM ----------
Found the reason files unzipping and fixed. FIle is downloading again and I will try your suggestions. Thanks!
Click to expand...
Click to collapse
In theory the first time you execute an adb command during a session in terminal you'll get the following echo:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Then it will execute your initial command.
I've added an adb devices command to the guide so if anyone reports a problem, they'll already know if they've been able to communicate across the microUSB cord.
Sent from my Nexus 7 using Tapatalk 4
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
bobng said:
I downloaded everything again and even though I deleted a program that aoto unzipped files the both unzipped. I connected the tablet and tried "adb Devices" and still returned -bash: adb: command not found
I've been at this for several hours. Google might even beat me with their installation at this rate.
Click to expand...
Click to collapse
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
xdhall said:
I believe you're missing a step or so when installing sdk. You likely need to edit your profile. I couldn't readily find it on the Google site, but here's an independent guide: http://m.androidauthority.com/how-to-install-android-sdk-software-development-kit-21137/. I expect the part your missing begins with step 4 under "Installing on Mac OS X; Installing the Android SDK"
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Thanks, I rarely use Terminal so will have to read up some more to get this working.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
I should be able to walk you through it tomorrow.
Sent from my Nexus 7 using Tapatalk 4
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
bobng said:
Thanks, I rarely use Terminal so will have to read up some more to get this working.
Click to expand...
Click to collapse
Basically you need to tell terminal where to find the bits of the various SDK programs by editing your bash profile. This is how terminal knows what you mean when you ask it to execute an adb or fastboot command. Let me simplify from the androidauthority guide. It takes three lines of code.
Open up a terminal window and execute the following:
Step 1: This step lets you edit the profile that tells terminal where to find executable binary files
Type and press enter:
Code:
vi ~/.bash_profile
Step 2: The step actually edits said profile
Type but don't press enter:
Code:
export PATH=$PATH:
Open a Finder window and find the folder "platform-tools" in the sdk folder (make sure you've put your sdk folder wherever you want it to live--if you move it later, terminal won't be able to find it). Drag and drop the folder on the terminal window. This time you DON'T want a space between the typed code and the file path.
Now press enter.
Step 3: This step saves your changes
Type and press enter:
Code:
source $HOME/.bash_profile
From now on, whenever you open a terminal window, you'll be able to use your sdk tools.
sahilcc7 said:
Thanks, guide worked great. Just the part where you select adb sideload - maybe state that you should hold power and tap vol up to select it. I got stuck there.
And for those with Windows 8.1 x64: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Those drivers worked.
Click to expand...
Click to collapse
Updated OP with the recommended tweak to the language and the link to the drivers. Thanks!
Sent from my Nexus 7 using Tapatalk 4
This worked for me without issue. I only had to install the proper drivers and after that it went smooth.
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
usage: vim [arguments] [file ..] edit specified file(s)
or: vim [arguments] - read text from stdin
or: vim [arguments] -t tag edit file where tag is defined
or: vim [arguments] -q [errorfile] edit file with first error
Arguments:
-- Only file names after this
-v Vi mode (like "vi")
-e Ex mode (like "ex")
-s Silent (batch) mode (only for "ex")
-d Diff mode (like "vimdiff")
-y Easy mode (like "evim", modeless)
-R Readonly mode (like "view")
-Z Restricted mode (like "rvim")
-m Modifications (writing files) not allowed
-M Modifications in text not allowed
-b Binary mode
-l Lisp mode
-C Compatible with Vi: 'compatible'
-N Not fully Vi compatible: 'nocompatible'
-V[N][fname] Be verbose [level N] [log messages to fname]
-D Debugging mode
-n No swap file, use memory only
-r List swap files and exit
-r (with file name) Recover crashed session
-L Same as -r
-T <terminal> Set terminal type to <terminal>
-u <vimrc> Use <vimrc> instead of any .vimrc
--noplugin Don't load plugin scripts
-p[N] Open N tab pages (default: one for each file)
-o[N] Open N windows (default: one for each file)
-O[N] Like -o but split vertically
+ Start at end of file
+<lnum> Start at line <lnum>
--cmd <command> Execute <command> before loading any vimrc file
-c <command> Execute <command> after loading the first file
-S <session> Source file <session> after loading the first file
-s <scriptin> Read Normal mode commands from file <scriptin>
-w <scriptout> Append all typed commands to file <scriptout>
-W <scriptout> Write all typed commands to file <scriptout>
-x Edit encrypted files
--startuptime <file> Write startup timing messages to <file>
-i <viminfo> Use <viminfo> instead of .viminfo
-h or --help Print Help (this message) and exit
--version Print version information and exit
Bobs-Retina:~ bobng$ -v -/.bash_profile
-bash: -v: command not found
Bobs-Retina:~ bobng$ export PATH=$PATH:/Users/bobng/Downloads/adt-bundle-mac-x86_64-20131030/sdk/platform-tools
Bobs-Retina:~ bobng$ source $HOME/.bash_profile
-bash: /Users/bobng/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$
I just upgraded to Mavericks, not sure if that makes a difference?
bobng said:
I tried your suggestion and as you can see Step 1 wasn't successful but I tried the rest the result is as follows:
Last login: Mon Nov 18 21:56:38 on ttys000
Bobs-Retina:~ bobng$ vi -/.bash_profile
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Aug 24 2013 18:58:47)
Unknown option argument: "-/.bash_profile"
More info with: "vim -h"
Bobs-Retina:~ bobng$ vi-/.bash_profile
-bash: vi-/.bash_profile: No such file or directory
Bobs-Retina:~ bobng$ vim -h
I just upgraded to Mavericks, not sure if that makes a difference?
Click to expand...
Click to collapse
You're using a hyphen where you need a tilda.
You typed: vi -/.bash_profile
It should be: vi ~/.bash_profile
vi space tilda forward slash period bash underscore profile
It might help to copy and paste the code from my post directly into terminal.
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
bobng said:
Thanks again, I see that it is a tilda now. I appreciate you sticking with me.
---------- Post added at 01:15 AM ---------- Previous post was at 01:00 AM ----------
OK, I got in trouble again. When I did Step 2 I got a message abowut not being found. I tried to copy and somehow moved it and couldn't get a prompt. So I tried to shut down and start over, not a good idea. Here is where I am now:
Bobs-Retina:~ bobng$ vi ~/.bash_profile
E325: ATTENTION
Found a swap file by the name "~/.bash_profile.swp"
owned by: bobng dated: Tue Nov 19 19:04:46 2013
file name: ~bobng/.bash_profile
modified: YES
user name: bobng host name: Bobs-Retina.local
process ID: 20981
While opening file "/Users/bobng/.bash_profile"
(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.
(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /Users/bobng/.bash_profile"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/Users/bobng/.bash_profile.sw
p"
to avoid this message.
Swap file "~/.bash_profile.swp" already exists!
[O]pen Read-Only, (E)dit anyway, (R)ecover, (D)elete it, (Q)uit, (A)bort:
Click to expand...
Click to collapse
Delete the swap file by executing the following:
Code:
rm -r ~/.bash_profile.swp
Don't forget the ".swp" at the end
Then start again
Here's what I did, I downloaded the the full image, some 400mb to
File i found in the forums here, I then rebooted into twrp, and installed from zip.
Boom.
All my apps were ok apart from the browser. I'm on 4.4, have new kit Kat features etc. Other than that, how do I know if I did it right?
Sent from my Nexus 7 using xda app-developers app

Cannot Revoke USB Debugging Authorizations

So I've come across a quirk that I haven't been able to resolve and haven't noticed before getting my G5. When I run
Code:
adb devices
on my computer with my phone connected, it shows my device but says unauthorized. I cannot seem to authorize my device. I have tried:
Revoke USB Debugging Authorizations (option not available in Developer Options)
Delete adb_keys in /data/misc/adb/ (No adb_keys file in the folder)
Create adb_keys file on my computer using the computers public key (Phone deletes this file on boot)
I realize this is more of a general Android question, but as it hasn't happened to me on any other phone, I wanted to see if anyone else was having this trouble.
Same boat here, haven't been able to fix the issue. I believe there's a testboot3.img floating around that fixes it. I downloaded it awhile ago as I keep a eye on everything for this device. But I don't know if it does and if you flash a new boot.img I'd think it would override it. I've tried your method as well.
I am also having this issue. Does anyone have a solution?
To update this for those that need it; this toolkit worked to fix this issue for me in Linux. I just hit the red block in the upper left that says "unauthorized device" when the phone was plugged in. Not sure what the kit did but then my phone finally asked if I wanted to allow the computer access. After doing that I finally got "authorized" when running "adb devices" in ubuntu.
https://forum.xda-developers.com/g5-plus/development/toolkit-moto-g5-plus-toolkit-root-t3605203
A fix if you are running Windows (or Linux)
I just found a fix that worked for me.
(Although i got the "unauthorized" status with the phone running as usual, I didn't get the same problem when in recovery mode.)
I followed instructions from this site but needed to change Linux commands to simliar Windows commands: http://www.neuraldump.com/2017/05/how-to-fix-adb-unauthorized-error/
If you are using Windows, you'll need to follow the commands below:
- First things first:
- Phone: Check if you have a file called adb_keys located at: /data/misc/adb/adb_keys. If you have it, i would recommend you to backup the file. (I didn't have it.)
- Windows:You'll need to have a file called adbkey.pub located at C:\users\UserAccount\.android\
- Boot into recovery mode.
- Plug your phone into PC.
- Open cmd and run adb devices. It would show "recovery" instead "unauthorized".
- Create a new file called adb_keys file on your PC:
Code:
type NUL > adb_keys
- Now you need to copy the contents from the adbkey.pub to adb_keys, the new file you just created:
adbkey.pub is located at C:\users\UserAccount\.android\
(Needless to say you need to replace "UserAccount" when running the command)
Code:
type c:\users\UserAccount\.android\adbkey.pub > adb_keys
- Upload the adb_keys file to your phone:
Code:
adb push adb_keys /data/misc/adb/adb_keys
- Reboot and run adb devices. It should be working now.
(Thanks to Tony, the guy who posted this fix in his blog).
need help please. Cant do it. I have that problem on my moto g5 plus. Dont understand this. Windows 10 pro computer.
Edit: I solved using the adb_keys from my xperia and using root explorer on my moto g5 plus and paste on data/misc/adb/adb_keys
Awesome! You may need to change permissions like I did from using root user within a debian chroot. Just like ssh keys....
From twrp recovery console.
chmod 0644 /data/misc/adb/adb_keys
chown -u shell /data/misc/adb/adb_keys
That got me authorized and running a root shell to spoof fingerprint before getting past first Hello page of setup
Yep, it works on my side as well on a Samsung galaxy Note 3, RROS 8.6.1, very good tip!:good:
@mnoguti
thank you, this fix my Verizon Note 4 issue with Smali Patcher not detecting my phone.
Thank you! My Galaxy S4 GT-i9505 also had this issue and your guide let me succesfully use adb normally again!
mnoguti said:
A fix if you are running Windows (or Linux)
I just found a fix that worked for me.
(Although i got the "unauthorized" status with the phone running as usual, I didn't get the same problem when in recovery mode.)
I followed instructions from this site but needed to change Linux commands to simliar Windows commands: http://www.neuraldump.com/2017/05/how-to-fix-adb-unauthorized-error/
If you are using Windows, you'll need to follow the commands below:
- First things first:
- Phone: Check if you have a file called adb_keys located at: /data/misc/adb/adb_keys. If you have it, i would recommend you to backup the file. (I didn't have it.)
- Windows:You'll need to have a file called adbkey.pub located at C:\users\UserAccount\.android\
- Boot into recovery mode.
- Plug your phone into PC.
- Open cmd and run adb devices. It would show "recovery" instead "unauthorized".
- Create a new file called adb_keys file on your PC:
Code:
type NUL > adb_keys
- Now you need to copy the contents from the adbkey.pub to adb_keys, the new file you just created:
adbkey.pub is located at C:\users\UserAccount\.android\
(Needless to say you need to replace "UserAccount" when running the command)
Code:
type c:\users\UserAccount\.android\adbkey.pub > adb_keys
- Upload the adb_keys file to your phone:
Code:
adb push adb_keys /data/misc/adb/adb_keys
- Reboot and run adb devices. It should be working now.
(Thanks to Tony, the guy who posted this fix in his blog).
Click to expand...
Click to collapse
Thank you so much, you saved my life

Categories

Resources