Related
Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Go to developer. android. com/sdk/index.html (take out the spaces - I still can't post links for some reason) and download the Android SDK for Mac. That same page also includes directions on how to get started with installation. You'll be using the Terminal within Mac OS X for ADB commands, so I would recommend getting comfortable with Terminal before jumping into the SDK. Unfortunately, you'll have to look this up because I couldn't even begin to explain everything, nor do I have the time. Hope the rest helps, though.
bftb0 said:
Perhaps you could say a few words about what you have tried already and where you are stopped.
I'm assuming you've downloaded and installed the Mac version of the SDK, yes?
On the phone, you need to turn on Settings -> Applications -> Development -> USB debugging (and may as well check "Stay awake", too).
I don't have a OS/X box, but on Linux you need to perform the *first* adb command as root... the first time an "adb" command is run (after a reboot) it starts up an adb-server process, and that needs to be priviliged enough to write to USB. (After that, you can run adb commands as any user, since those commands "talk" to the adb-server on your Mac, which in turn talks to the phone over the USB cable.)
bftb0
Click to expand...
Click to collapse
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Los-O said:
Yes I've downloaded and installed the sdk, turned debugging on and now im trying to flash the recovery image onto my phone and that is where im lost at because I don't know exactly what to do
Click to expand...
Click to collapse
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Nevertheless, if you want to rush into something, here is a step by step set of instructions which was current a couple of days ago. I won't vouch for it being 100% up to date with the latest and greatest images (either ROM or recovery), but it completely describes the process involved.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
bftb0 said:
Note that what you are asking (now) is completely different than what you asked about in your OP - in fact, OS X is immaterial, really, in light of what you just indicated. That suggests that you are in a hurry... if that is the case, I recommend you spend a couple days reading before you rush off and do something you might regret. It is evident from your response that you really have not been reading the threads here with much diligence.
If you are trying to flash a recovery image, that implies that your phone is already rooted; either that what you are trying it isn't going to work - you have to have a rooted phone to begin with before you flash a custom recovery image. At the moment, you can root your Eris only if it has a 1.5 (1.16.605.1 or 1.17.605.1) official Verizon/HTC release on it. This has been described if not a hundred times in the threads here, at least tens of times - you need to read some more.
Stock 1.5 --> Root (2.1) install --> Custom Recovery install -> recovery to custom ROM 0.3. That's what is working at the moment.
bftb0
Click to expand...
Click to collapse
I've already rooted my phone
Los-O said:
I've already rooted my phone
Click to expand...
Click to collapse
Well, then you should be on your way; the instructions for what you are trying to attempt are in that link I provided for you in answer to your question (which you purposely redacted when you quoted my post).
I understand that it's your first post, and I should give some leeway for that reason alone, especially since you might have gotten root without ever having used "adb" or "fastboot". (PB00IMG.ZIP method).
On the other hand, I think you can see my point. Please try to avoid wasting other people's time by providing them useful & relevant details of your situation so they can give you good answers. And reading some of the links adjacent to your own post which actually give exactly the details you are asking for might be a good idea, too.
You wanted to know "What are the directions to DisneyWorld?", but instead asked "How do I put gas in my car?" - when you already knew exactly how to do that. But don't take my word for it - reread your first post for yourself - it actually says nothing about what you are trying to do.
I don't know, maybe I got this all wrong, and you still don't have your phone talking to your OS X machine correctly with adb, and that's the source of the trouble. But then, there would be no way to know one way or another - you haven't really said.
bftb0
Download the android sdk and run this automator script.
20 Questions
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Once you have the android sdk unzipped, add the full path to the android tools directory to your path.
I just added the path to my .bash_profile.
For me it looks like this:
export ANDROID-SDK=/Users/Aaron/android-sdk/
export PATH=$ANDROID-SDK/toolsATH
Then I save and close my bash_profile and run the command, from the terminal:
source .bash_profile
This reloads the bash_profile into the shell. Then cd to your android tools directory. Once you get into the tools directory type the command adb. If everything is correct you should see a help menu spit out to the console.
If you need help with your bash_profile a simple google search will help you out.
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
taocow said:
hey bftb0,
just wanted to chime in and say thanks for that step-by-step. been wrestling with the same issues as the original poster and your walk through got it going. thanks for being patient.
taocow
Click to expand...
Click to collapse
los-O said:
bftb0,
thank you so so soo much for that last post, I think i've finally figured it out. and also thank you for your patience, i wish i could buy you a coke or something lol
Click to expand...
Click to collapse
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
bftb0 said:
taocow / los-O
Did you need to run the first "adb" command as root with "sudo" ? Let me know - and also mention the version of OS X that you are using; maybe it will help other Mac users if they read this thread. (I got the impression from reading a little bit that different releases of OS X might handle "sudo" a little differently - or have different device permissions for regular users.)
Also, in reviewing this thread, I have to say ... I acted like an a$$. And I should know better, I did IT for a while. If there is one thing I learned about dealing with people and computers, it's that it is extremely easy for a misunderstanding to occur, and especially if you are helping someone out over the phone or via mail/forum. Please accept my apologies.
bftb0
Click to expand...
Click to collapse
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get
"cannot stat 'recovery.img': No such file or directory" same for the flash image
but i put the files in the tools folder like the guide said to do...?
also im on OS X 10.6.2, but no i didnt have to use the "sudo" thing you were talking about, the "adb devices" command worked the first try. and dont worry about it, i understand where you were coming from. but apology accepted, though
Los-O said:
also now im able to install the recovery (thanks to you) but when i try and push the recovery and flash images i get "cannot stat 'recovery.img': No such file or directory" same for the flash image but i put the files in the tools folder like the guide said to do...?
Click to expand...
Click to collapse
That sounds like you are referring to the files by name, but they are not in the current directory where you are running the fastboot command.
The "pwd" command (Print Working Directory) tells you what your current directory is.
The "cd folder-path" command (Change Directory) allows you to change the Terminal/Shell's idea of where the "current directory" is.
The idea behind the PATH variable is that it is a searchable list (separated by ':' colon characters), so that you can be in a given directory with the files you want to manipulate, but the commands you use are in other directories. When you start a command by typing its' name, the Terminal/Shell app walks through that list of folders in PATH (from left to right in order), looking for that program by name.
That means that if you want to run a program ("proggie") that opens a file ("myfile") that is in the current directory you might type the command.
$ proggie myfile
(or $ proggie ./myfile )
... and as long as "proggie" was in one of the folders listed in your PATH, it would run, and find your file "myfile".
But, there is no requirement that you be in the same directory with your files, or the program that you are running (for instance "fastboot"). In those cases, you need to explicitly specify the complete path to your files or programs, so they can be found. For instance:
$ proggie /users/los-o/mystuff/project3/myfile
or, if "proggie" was not in a folder in your PATH, but you knew that it was located in /opt/tools, you could type the command
$ /opt/tools/proggie myfile
If your current directory contains the file "myfile", or
$ /opt/tools/proggie /users/los-o/mystuff/project/myfile.
Same deal with fastboot - you give it the name of the recovery file as the 3rd argument on the "command line"
$ fastboot flash recovery name-of-my-copy-of-the-recovery-file.img
bftb0
*Whew!* Ok thanks again bftb0 for all the help, I think im finally starting to get the hang of this adb stuff
u have a knack for teaching
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
excellent post...very helpful
Los-O said:
Can someone please help me, or point me in the right direction on how to setup and run simple commands through adb on a MAC? Yes, I've used the search, and yes I've searched all over the internet but I still cannot figure it out. Sorry for my stupidity lol
But any help would be greatly appreciated, thank you
Click to expand...
Click to collapse
I do everything on a Mac, so I would be the guy to ask. How far did you get? Have you unzipped the sdk to a folder?
Basically the difference between mac and others is that when others do a command like adb, we have to do ./adb This is true for other commands too. It's easy once you get used to it.
bftb0,
Thanks so much! Step 6 solved my problem
Thank you!!
bftb0 said:
Los-O:
You said "any help would be greatly appreciated." Maybe that will also include help from the surly folks, such as me.
You said you have "downloaded and installed the SDK". Let's start there. (Also, note that the Android SDK for Mac OS X is only for x86 Apple machines - stop right here if you are using an older PPC based OS X machine).
The Mac SDK is in a .zip file. I presume that means that you unzipped it somewhere on your hard drive, and that you can remember what the folder name/directory name is where you unpacked all those files. (From where I sit, that could mean that you used a GUI based tool, or something from the command line to unpack the files; but I am guessing.)
Here is a flowchart to help you with the steps.
(1) Have you successfully run the "adb" command from within a Terminal window? (Yes: goto (4), No: Continue)
(2) Do you know how to open a Terminal window in OS X? (Yes: goto (4), No: Continue)
(3) Have a look at this information about Terminal on OS X, and then
(4) Start a Terminal window up.
(5) When you type the command (followed by hitting the Enter key):
Code:
adb --help
at the command line, do you get a pageful of information about the adb command, or an error such as "command not found"? (Help Info: goto step (7), No: Continue)
(6) Add to your PATH the location of the SDK tools (including "adb"). For this step, you need to recall where you unpacked your .zip file. On my Linux box, the "adb" command (and others) are located in the folder at
/opt/android/android-sdk_r05-linux_86/tools/
where the part "/opt/android/" is the folder I unzipped them in. For OS X, surely the next folder name in the path is something other than "android-sdk-linux_86" - just poke around in whatever OS X uses as a file browser, and look for the "tools" folder underneath where you unpacked the files. Once you have done that, you should be able to type the full "path" to that (tools) folder in a command.
Let's suppose that the complete path to that "tools" folder looks something like this:
/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Then, for example, we would add this to the current terminal (shell) PATH using the following command:
Code:
export PATH=${PATH}:/HardDrive1/foo/bar/android-sdk_r05-mac_86/tools
Obviously, you would change the part "HardDrive...86" so it matches the complete path to the "tools" folder in the SDK which you unpacked onto your machine.
You can inspect the value of PATH for correctness by typing the command
Code:
echo $PATH
Now, go back to step (5) and keep at steps 5-6 until you are able to run the "adb --help" command successfully - that is, get it to print some help information. Don't close this Terminal window after you have the PATH set correctly - we are going to use it shortly.***
(7) Plug the phone into the USB cable and the USB cable into the computer
(8) On the phone, make sure that Settings -> Applications -> Development -> USB debugging is toggled on.
(9) In the terminal window from step (6), type the commands
Code:
adb kill-server
adb devices
You will see one of three things at this point after the "adb devices" command executes:
A. (this is what we want to see)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT9ABCDnnnnn device
If you see this, very good: adb has detected your phone and talked to it; continue to step # (10).
B. (not good - you probably need to run adb as the root user)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
???????????? no permissions
In this case, the "adb" command ran, and detected the presence of the phone, but does not have sufficient privileges to write to the USB device; whether or not this happens in a given flavor or Unix (e.g. OS X) depends on what user and group permissions are set on the device, and which "groups" regular users are in. Not having OS X in front of me, I can not predict; but the solution in this case is to run the command as the root user.
It is my impression that OS X has the "sudo" command for this purpose (read here); if that is the case, then you might want to run the commands
Code:
adb kill-server
sudo `which adb` devices
If sudo is not available to you, or not setup correctly, you might have to read this Apple Technical Note, or this one, or this one
C. (some other problem - no USB device is detected)
Code:
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Your on your own for this one - consult your local Apple OS X expert!
(10) Now you are ready to communicate with the phone using "adb" commands.
Note that running the "adb" command for the first time after your OS X machine is booted up creates a long lived adb "server" process. (You might see it in a "ps" command listing as "adb fork-server"). That process is what actually communicates with the phone. Any subsequent "adb" command first communicates with that "adb server" on your OS X machine, and then the server communicates with the phone.
Sometimes it goes stale or gets cranky after unplugging the phone too many times. Simply re-start if you want by doing a "adb kill-server" (any user can do this), followed by any adb command, keeping in mind the results from step # (9) above.
OK, whew! The desired goal was to get a recovery image loaded on to the Eris after it had been rooted - it is time to do that, as adb is working now.
See the Instructions by GrdLock here, in the section entitled "II. Installing Amon's recovery image"
bftb0
***The setting of the PATH when you use the Terminal app using the directions given in step # (6) only last for the life of a single Terminal session. If you want to make this change in such a way that it will be already set up every time you open a new Terminal window, you need to do this by editing a file in your home folder - either ".bash_profile" or ".bashrc" . (Different files names are used depending on which "shell" is used). Setting this up is an exercise left up to the interested reader.
Click to expand...
Click to collapse
Wow what a straightforward guide to helping me get this set up!! A million thanks! I don't even have an Eris, but what model of the phone you have is irrevelant to this guide...
Thanks again!!
Ok im new to this and I am haveing problems with ADK. I run XP. when i open ADK setup.exe it opens a cmd prompt. I can not type anything in this cmd prompt. Is this the wrong prompt or if it is right why can't I type in it. really driveing me nuts. if I can't get this to work I can't flash the custom ROM I want. PLEASE HELP.
ADK or SDK?
Sent from my Eris using XDA App
zach.xtr said:
ADK or SDK?
Sent from my Eris using XDA App
Click to expand...
Click to collapse
SDK sorry. moving to fast
I suggest doing a forum wide search on "sdk xp issue" or just "sdk xp", should find a bit to try. I use windows 7 so am not of much help. Good luck
Sent from my Eris using XDA App
I believe the command window you see appearing when you run the SDK "setup.exe" is an artifact of how the setup.exe program was compiled and linked. It is NOT the window you are supposed to be typing into, and it is normal for it to be unresponsive.
If you want a command window, complete the SDK setup instructions from whatever guide you are using, and then
Click on the Windows Start button
Select "Run"
Type "cmd" in that box and hit return
Up pops a command window; you can take it from there. If you have never used a command window before, you probably should do some reading to find out what they are about and the most commonly used commands (CD, MKDIR, PATH, DIR, etc)
bftb0
Ok got the cmd thing but the drivers I dowloaded won't let my computer see my phone. the driver it keeps defaulting to is My HTC
Okay, this guide is for users with less experience and want to overclock their Kindle Fire. This is for Windows.
This section is if you haven't installed ADB yet
1) You need to download the Android SDK
Android SDK: http://developer.android.com/sdk/index.html
2) Open the SDK Manager and install the SDK Tools and SDK Platform Tools
3) You need to add the ADB path. First find where you installed the Android SDK.The default is in C:\Program Files\Android\Android-sdk or C:\Program Files (x86)\Android\Android-sdk, you can check in the SDK Manager at the top, it will tell you your path. Then click on the start button, and right click on my computer and hit properties. Then on the left click Advanced System Settings In the next box at the bottom is Environment Variables click on this. Under System Variables find the variable that says Path DO NOT DELETE THIS VARIABLE! Hit Edit and at the the end put:
;YOUR ANDROID SDK PATH\tools;YOUR ANDROID SDK PATH\platform-tools
Then hit OK.
ADB install tutorial is now finished
4)Now we want to add the correct drivers. There are a couple of ways to do this, this is the way I do it. Again right click on My Computer, and click properties. Now in the top left corner is Device Manager click on this. Now find where it says Kindle and right click it. Click the drivers tab and then Update Drivers and then browse my computer for driver software. Then click, let me choose from a list on my computer and click adb interface, and then either a ADB Testing Interface, or fastboot Interface, both work for what we are doing.
5) The next thing you want is a kernel so download and put in the \platform-tools folder.
IntersectRaven's: http://forum.xda-developers.com/showthread.php?t=1382999
DoomLord's: http://forum.xda-developers.com/showthread.php?t=1372625
6) Plug your Kindle Fire into your computer
7) Open a CMD window. Hit start and run CMD.exe or search for CMD. Then type into cmd:
adb shell
idme bootmode 4002
reboot
8) Open another CMD and type cd YOUR ANDROID SDK PATH \platform-tools. Then type:
fastboot boot NAME OF KERNEL.img
9) Now your Kindle will reboot, make sure it boots! Now that you have verified that it works we are ready to flash it.
10) Shutdown your Kindle Fire.
11) Use your old CMD with fastboot, and type:
fastboot flash boot NAME OF KERNEL.img
12) It will probably get stuck in booting at this point. With the fastboot CMD type:
fastboot oem idme bootmode 4000
it will say waiting for device, do not close this CMD!
13) Now hold down the power button until your device turns off. Then turn it on again, and the command will register.
14) Let your Kindle Fire boot and enjoy your new kernel!
If this doesn't work please leave a comment, or if I forgot anything, I am kind of tired while writing this. I may add pictures later. Thanks!
All this does is boots the custom kernel a single time (which you MUST do to test it). You still need to flash it.
Sent from my Gingervolt-ed VS910 4G using xda premium
Sorry, I will add the rest soon, slipped my tired mind.
do we really need the whole android and java sdk ?
the only commands used is adb and fastboot.
woud'nt the tools directory of KFU be enough since it contains the necessary commands ?
furthermore the driver installation is a essential part for correct operation of adb and fastboot
and don't forget so say your how-to is for windows
I haven't looked at the KFU much yet, so I don't know. I added that it is for windows and removed the java sdk. And added how to flash the kernel.
Accessory mode suppot
Are any Fire kernels available that support Accessory Mode aka ADK.
The changes that need to be made to the kernel are available from Google. They are in the main 3.x kernel source tree and in the samsung source tree of the 2.6.35 kernel.
Hello there
I was using Windows 8 CP and I managed to use unsigned driver with bcdedit stuff
But with RTM i use the same thing about about testsigning
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
I used Double D on DDISABLE for CP it worked, but now with double D or even with
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
It does not start with test mode
And about the group policy, same stuff
Changed code signing for driver to enabled/ignore warnings, and still no game
this is a copy from my bcdedit
C:\Windows\system32>bcdedit
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {ae6e608f-e990-11e1-a01d-c0bf5e481f67}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 8
locale en-US
loadoptions DISABLE_INTEGRITY_CHECKS
inherit {bootloadersettings}
recoverysequence {ae6e6091-e990-11e1-a01d-c0bf5e481f67}
integrityservices Enable
recoveryenabled Yes
nointegritychecks Yes
testsigning Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {ae6e608f-e990-11e1-a01d-c0bf5e481f67}
nx OptIn
bootmenupolicy Standard
What am i doing wrong ?
tks !
http://www.pcpro.co.uk/blogs/2012/08/06/getting-older-drivers-to-work-in-windows-8/
[scroll down to "installing unsigned drivers"]
Hi
The problem with that trick is it because i use dual boot here and sometimes windows does not reboot proper with the test signing part
What is the proper way to actually make it permanent ?
The old way worked with CP but with RTM no go
tks
Apparently the BCD options aren't enough. You'd need to edit the group policy as well, per below. (This is a copy-paste job, I haven't had the occasion to installed unsigned drivers.)
# Return to the Start Screen, start typing gpedit.msc and hit Enter.
# Navigate to User Configuration (2nd node) | Administrative Templates | System | Driver Installation | Code signing for device drivers
# Double-click the policy and set it to Disabled.
# Restart your computer.
Hi
I did everything, including disabling that part too
And still no luck even by using easy bcdedit did not disable driver signing policy
tkd
Try this:
bcdedit /set {bootmgr} displaybootmenu yes
bcdedit /set testsigning on
bcdedit /set nointegritychecks on
If your driver is test signed, you should use the following to add the test cert into the local store:
certmgr.exe -add abc.cer -r localMachine -s root
If your system is capable of UEFI/secure boot and secure boot is enabled, you'll have to press F8 and select the disable enforcement option #7 manually each time you boot.
Or just hookup a kernel debugger and you can bypass all enforcement.
cristiano.orlando said:
Hello there
BLAH BLAH BLAH......
What am i doing wrong ?
tks !
Click to expand...
Click to collapse
do this...
1. Windows Key + R
2. Enter shutdown.exe /r /o /f /t 00
3. Click the "OK" button
remember the steps from here onwords as it will take you to the restart options and close your browser/apps
sooo where was we.?
4. You will now be on "Choose an option" screen
5. Select "Troubleshoot"
6. Select "Advanced options"
7. Select "Windows Startup Settings"
8. Click "Restart" button
9. System will restart to "Advanced Boot Options" screen
10. Select "Disable Driver Signature Enforcement" (number 7 on the list)
11. Once the system starts, install the drivers as you would on Windows 7
:good::fingers-crossed:
Cav3 said:
do this...
1. Windows Key + R
2. Enter shutdown.exe /r /o /f /t 00
3. Click the "OK" button
remember the steps from here onwords as it will take you to the restart options and close your browser/apps
sooo where was we.?
4. You will now be on "Choose an option" screen
5. Select "Troubleshoot"
6. Select "Advanced options"
7. Select "Windows Startup Settings"
8. Click "Restart" button
9. System will restart to "Advanced Boot Options" screen
10. Select "Disable Driver Signature Enforcement" (number 7 on the list)
11. Once the system starts, install the drivers as you would on Windows 7
:good::fingers-crossed:
Click to expand...
Click to collapse
not sure if you'd know or not but would this make my video card driver run better? if i were to revert back to the 7 driver?
i have an nvidia 9800 which ran perfectly on 7 but on 8 it crashes and restarts and some times gets blurry and shakey. nvidia just released the windows 8 driver which has only crashed once but still has the shakey blurry problem at times.
If that doesn't work, try this: http://www.ngohq.com/home.php?page=dseo
I used it to permanently disable signature checks and it works perfectly :good:
elfhater said:
If that doesn't work, try this: http://www.ngohq.com/home.php?page=dseo
I used it to permanently disable signature checks and it works perfectly :good:
Click to expand...
Click to collapse
But this is not for Windows 8.
I've seen tons of solutions that just do nothing or kill the driver after a restart.
So what is the solution that does actually works for Windows 8?
Any working solutions yet? I have the same problem with a sound card and custom drivers. (terratech aurion 5.1 pci with cmedia/dogbert drivers)
They work of I start up in advanced mode and disable integrity checks. But then when I reboot they don't work anymore. Tried all the above solutions.
Dr_Jefferson said:
Any working solutions yet? I have the same problem with a sound card and custom drivers. (terratech aurion 5.1 pci with cmedia/dogbert drivers)
They work of I start up in advanced mode and disable integrity checks. But then when I reboot they don't work anymore. Tried all the above solutions.
Click to expand...
Click to collapse
Try This.
Open a command prompt as an admin and type:
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
-Reboot-
-Install driver-
Admin command prompt again
bcdedit /deletevalue loadoptions
bcdedit -set TESTSIGNING OFF
FDisk80 said:
Try This.
Open a command prompt as an admin and type:
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
-Reboot-
-Install driver-
Admin command prompt again
bcdedit /deletevalue loadoptions
bcdedit -set TESTSIGNING OFF
Click to expand...
Click to collapse
Clearing the testsigning and disable_integrity_checks would do nothing except cause it to not load them after the first reboot, even if it did load them in the first place.
FDisk80 said:
Try This.
Open a command prompt as an admin and type:
bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
-Reboot-
-Install driver-
Admin command prompt again
bcdedit /deletevalue loadoptions
bcdedit -set TESTSIGNING OFF
Click to expand...
Click to collapse
When installing the driver it gives me an error. It says: "The non-Microsoft INF-file Doesn't include a digital signature."
The only time I don't get that message is when I boot in advanced bootmode with disabled signature checks and then install them. And in that mode the drivers work. But when I restart (even in test mode with integrity checks disabled) they don't.
Follow these steps
QUOTE=e.mote;32690034]Apparently the BCD options aren't enough. You'd need to edit the group policy as well, per below. (This is a copy-paste job, I haven't had the occasion to installed unsigned drivers.)
# Return to the Start Screen, start typing gpedit.msc and hit Enter.
# Navigate to User Configuration (2nd node) | Administrative Templates | System | Driver Installation | Code signing for device drivers
# Double-click the policy and set it to Disabled.
# Restart your computer.[/QUOTE]
This is a simple Step-by-Step guide on How To: How To: Root the Kindle Fire 7" HD, Kindle Fire HD 8.9" and Kindle Fire 2 with Windows - Noob (Simple) Version. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3. We attempt to keep this tutorial updated regularly - adding information from the end users experience. We have recently upgraded the storage servers to increase uptime, you now have two options for the downloads both are ad free. Option one is a Dropbox Storage Server and Option two is a Ubuntu One Storage Server, if one is under maintenance you may use the other download link. When you are done with the tutorial, please take the time to post feedback, this is very important to us - without your feedback, we have no way of knowing if we are doing our job. Finally, if you feel we did a decent job, please think about donating to us using the "Donate to Me" button - this is how we make a living, without your kind donations we would no longer be able to do this for a living.
Prerequisites:
1. Software: Windows XP, 7 or 8 Workstation 32bit or 64bit
2. Hardware: Free USB 2.0 or Greater Port
3. Kindle Fire HD 7", Kindle Fire HD 8.9" or Kindle Fire 2 7"
Note: Windows 7 and Vista users, please perform this fix before Rooting: http://forum.xda-developers.com/showthread.php?p=36373627
It is important that you use our Utilities since we have modified the ADB daemons plus we did little tweaks in some of the batch files. PLEASE USE OUR UTILITIES, WE ARE RECEIVING A NUMBER OF FAILURES CAUSED BY USING ANOTHER PARTIES UTILITIES. IF YOU FOLLOW THE STEPS BELOW, EXACTLY, YOU HAVE A 99% CHANCE OF SUCCESS.
Unplug the Kindle from USB.
A) Although the processes do not use Java directly, the software does call to some Java API's so we need to make sure Java is updated to the latest version. Please go to Oracle's site here: Java SE Development Kit 7u13 download and install Java SDK 32-bit or 64-bit. Reboot your computer after installing the Java update.
B) The first step is to get the ADB Driver installed. If you already performed this step and verified communication to the Kindle, move on to Main Step C
Note: Please remove any old or outdated drivers by following the instructions in Post #361 here: http://forum.xda-developers.com/showpost.php?p=37733595&postcount=361
The following ADB Driver was provided by Amazon and should install on most platforms (Windows XP, Vista, 7, and 8): Kindle Fire ADB drivers(Dropbox) or Kindle Fire ADB Drivers(Ubuntu One)
Note: Due to intermittent issues with the USB Drivers, we offer two versions. First try Kindle Fire ADB drivers.exe if this
does not open ADB Communication try the new updated KindleDrivers.exe
Please open an Administrative CMD Prompt and enter:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot the Computer to apply the above command.
Extract the Kindle Fire ADB drivers.zip to your desktop.
1. Unzip Kindle Fire ADB drivers.zip to Kindle Fire ADB drivers on your desktop.
2. Click windows start button.
3. Next choose Search, in the "Search programs and files" box type "cmd" (don't hit enter or search).
4. The program "cmd.exe" should be listed at the top. Right click that and select "Run As Administrator".
5. Navigate to the Kindle Fire ADB drivers.exe or KindleDrivers.exe using the DOS Command cd.
6. Next, the install will begin, allow the install to complete.
7. While the driver is installing. Go to the Kindle unlock if locked.
8. Pull down the upper bar. Select "More".
9. Now Select the "Security" Tab.
10. In Security is an option to: Enable ADB
11. Select "On" to Enable ADB on the Kindle
If not, We have an alternative driver here: usb_driver(Dropbox) or usb_driver(Ubuntu One)
Extract the alternative driver to your desktop and follow the install instructions at the bottom of this response
The alternative driver originates from the Android SDK and is universal for just about any Android device.
The alternative driver instructions are for Windows XP but can be used with Windows 7 and Vista.
Once we get ADB installed then let's plugin the Kindle to your computer USB to see if it initializes properly.
Once this driver has been properly installed you will see "Android Composite ADB Interface" under "Kindle Fire" in the Windows Device Manager which is located by Right Hand Mouse Click Computer, Choose Properties, then Devices or Device Manager. Expand the tree. Expand Kindle. This is where you will see "Android Composite ADB Interface".
Amazon Notes regarding this ADB Driver can be found here: Amazon ADB Notes
ALTERNATIVE DRIVER INSTALL (Vista/XP/Windows7):
Windows XP
To install the Android USB driver on Windows XP for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Hardware Update Wizard.
2. Select Install from a list or specific location and click Next.
3. Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
4. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
5. Click Next to install the driver.
Or, to upgrade an existing Android USB driver on Windows XP with the new driver:
1. Connect your Android-powered device to your computer's USB port.
2. Right-click on My Computer from your desktop or Windows Explorer, and select Manage.
3. Select Device Manager in the left pane.
4. Locate and expand Android Phone in the right pane.
5. Right-click Android Composite ADB Interface and select Update Driver. This will launch the Hardware Update Wizard.
6. Select Install from a list or specific location and click Next.
7.Select Search for the best driver in these locations; un-check Search removable media; and check Include this location in the search.
8. Click Browse and locate the USB driver folder. (The Google USB Driver is located on your desktop \usb_driver\.)
9.Click Next to upgrade the driver.
C-1) The next steps are used to Root the Kindle - Preferred Method (Automated Version)
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
Root Step 1: Download Kindle Fire First Aide: Windows 32-bit Version Or Windows 64-bit Version
Root Step 2: Using either 7-Zip or Microsoft Zip, unzip the KFFirstAide.zip to your C:\ Drive as C:\KFFirstAide
Root Step 3: With your mouse, open the C:\KFFirstAide contents by double mouse clicking the C:\KFFirstAide folder
Root Step 4: Find the RunMe.bat file. Right Hand Mouse click on RunMe.bat, select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Root Step 5: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Root Step 6: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Root Step 7: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Root Step 8: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Note: Do Not forget the semi-colen before the C:\KFFirstAide
Root Step 9: That is it! The software is ready. Next we get the Kindle ready to Root.
Root Step 10: Please check the Kindle under More + > Security - make sure ADB is ON. Leave it disconnected from USB.
Root Step 11: Launch Kindle Fire First Aide, if the ADB Driver is not installed, use Option 12 to Install the ADB Driver
Root Step 12: Make sure the Kindle is turned ON, plugged into the Computer USB and ready. Select Option 15 to Root the Kindle. If Option 15 fails to Root the Kindle, use Option 16.
Root Step 13: That is it! The Kindle now has Root, you may close the software.
You may view the Kindle Fire First Aide Forum Notes here: http://forum.xda-developers.com/show....php?t=2096888
C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version):
The problem "Device not Found" is usually driver related or ADB Security issue. Let's make sure ADB is enabled on the Kindle under Security - Enable ADB?
Open the Windows Task Manager. Review the Processes. "End Process" on any adb.exe running. If you installed the Android SDK, there is probably a PATH Statement pointing to the platform-tools folder. To avoid adb.exe start-up conflicts, temporarily rename the SDK platform-tools folder to platform-tools-temp.
Plug the Kindle back into USB if it is not already plugged into USB.
1. Download Root MANY ANDROID 32-bit!(Dropbox) or Root MANY ANDROID! 64-bit(Dropbox) to your desktop. Extract to your desktop. This package includes updated adb daemons.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the above utility batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Make sure the Kindle is still plugged into USB.
Root Step 1: Run RunMe.bat from Root MANY ANDROID! through a command window as noted:
Double Mouse Click and Open the Win32 or Win64 folder.
Next Single Left Mouse Click on the Win32 or Win64 folder tool-bar.
This highlights the Win32 or Win64 folder.
Note: Make sure none of the files within the Win32 or Win64 are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
RunMe.bat
Choose option 1, Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. If you are asked for an 'encryption password', enter the password you use to sign onto Amazon. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it may react VERY slow, this is normal - leave it alone. Immediately proceed to Step 1 again. If the Kindle reboot normally and appears normal, then proceed to Step 3 you are almost done.
Root Step 3: Download suchecker.apk from here: Root Checker Basic(Dropbox)
Root Step 4: Using Windows Explorer, move suchecker from the desktop to /Kindle/Internal Drive/Download
Root Step 5: Now go to the Kindle. Using ES File Explorer or Root Explorer, go to /sdcard/Download/suchecker.apk choose Install
Root Step 6: When the install has finished, go to your Apps. Launch Root Checker. When you check Root you will be presented with a "Allow" dialog box, be sure to Allow Root Checker. You should now see that Superuser.apk is working.
You should now have root AND if this is true your ADB communication is also functional.
D) Finally, let's disable the Amazon OTA (Over The Air) Updates so your hard work is not destroyed.
OTA Step 1: Open Kindle Fire First Aide - Select Option 14 to Disable OTA.
Note: You may still install the updates manually after you have read the install notes and know what to expect. The updates and manual install instructions can be found on Amazon Support here: http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_sib?ie=UTF8&nodeId=201016350
E) Finally drop to an Administrative CMD and enter:
Code:
bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF
Reboot the computer to apply the above command.
When you run Root Checker, the output should be similar to:
{
"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"
}
Next, move onto our How to: Install Google Play Step-by-Step Thread
:good::good::good::good::good:
how long is it suppose to stay at *daemon started successfully* ?
ADB Communication Issues
urbannerdmaeio said:
how long is it suppose to stay at *daemon started successfully* ?
Click to expand...
Click to collapse
Once you plug in the Kindle, it takes up to 2 minutes for Windows to detect it. So having said this *daemon started successfully*
Should not be displayed for longer than 2 minutes.
Where did you download the Utilities? From us or the developers? Our utilities use new updated adb.exe daemons
dated 11/05/2012 11:06AM
If the adb.exe has the correct date stamp, then make sure you are following our instructions on how to open a command
prompt. If you are following the instructions exactly then....
You must have Windows 7 which requires you to open an Administrative Prompt by choosing Run as: Administrator when
opening the CMD Shortcut.
Still nothing...
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.
ADB Communication Issues
urbannerdmaeio said:
I downloaded the files from this thread, minus the ADB drivers because my computer already reads it under the device manager.
I go to the start menu, search for "cmd", run it as administrator and launch RunMe.bat from it
and it reads this to me
http[semi-colon]//s9.postimage.org/bpzs9w8u7/Untitled_1[dot]jpg
and nothing happens to the kindle, no message to restore and if i press any key on the command prompt it doesnt do anything either.
Click to expand...
Click to collapse
Please verify the date of the adb.exe daemons. Reply back with the date if the daemon in Root_with_Restore_by_Bin4ry_v17Root_with_Restore_by_Bin4ry_v17 Stuff folder.
Next download this mini-test utility: https://dl.dropbox.com/u/54456659/ADB%20Update.zip to your desktop
Unzip ADB Update.zip to your desktop
Open the ADB Update folder on your desktop
Make sure the Kindle is still plugged into USB.
Double Mouse Click and Open the ADB Update folder.
Next Single Left Mouse Click on the ADB Update folder toolbar.
This highlights the ADB Update folder.
Note: Make sure none of the files within the ADB Update are highlighted in blue.
Next Press the SHIFT Key, next Right Hand Mouse Click
Choose "Open command window here"
A Command window will open, finally type
Code:
adb kill-server
adb start-server
adb devices
Respond with the results.
Never mind
results...
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.
fiddystorms said:
I was getting the same results as you earlier. The mistake i made was that i believed my drivers were good too because my PC was reading the device under device manager. This ended up being a bad assumption. I deleted the drivers and installed the drivers that are found in the Qemu Zip folder. The drivers there worked perfectly.
I am rooted w/Play & thats what made the difference.
Click to expand...
Click to collapse
I've tried this several times, I keep getting the exact same problem regardless of where I get the drivers from, or what computer I use. I'm ready to pull out my hair...
ADB Communication Issues
urbannerdmaeio said:
http[semi-colon]//s7.postimage.org/md0uwbkij/Untitled_2[dot]jpg
and the date for the adb file matches the date you said it should be
Click to expand...
Click to collapse
There is a problem with ADB Communicating to the Kindle.
What platform are you using? Windows 7?
Are you sure ADB is enabled on the Kindle itself?
When you go into Windows device manager, do you see any Yellow Triangles over the devices?
In the device manager, do you see "Android Composite ADB Interface" or ?
ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on
Woop, finally got it rooted! Thanks for the noob guide and your patience.
One more question tho, I can't find where this path is: /system/ect/security/otacerts.zip
I'd rather not have amazon get rid of my rooting and wipe all my google play apps once I get that up and running.
ADB Communication Issues
urbannerdmaeio said:
ive already uninstalled and deleted the drivers, then installed the ones from the Quem folder and it gives me the same "drivers were not installed blah blah" message everyone else gets, and so i unplug then plug back in the kindle and my pc reinstalls the adb drivers....
try to root again, and nope, nothing.
heres a screen shot of my device manager (WINDOWS 7 x64)
http[semi-colon]//s14.postimage.org/6t9oytl5d/Untitled_3[dot]jpg
& yes im 100% positive ADB is on
Click to expand...
Click to collapse
OK, everything looks good with ADB. Looks like we have a pesky Windows 7 issue. Windows 7 Command prompt is only User level by default and will cause these utilities to fail.
If you go into Programs > Accessories or Programs > Accessories > System Tools do you see the Command Prompt? Now Right Hand Mouse click over the prompt and choose Run As Administrator
Once the Command Prompt is opened navigate to each utility using the "cd" "cd.." "cd c:\" etc command.
Once you navigate to the Root_with_Restore_by_Bin4ry_v17 folder, you will be able to successfully run the batch file through the Administrative prompt.
Thank you
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you
Follow Up
Jayj0ka said:
Wow thank you for taking all of this time to put together a easy to follow guide in rooting the Kindle Fire HD. I plan to do this soon, just waiting on my scorpi0n cord, just incase I make a mistake. I am a total noob to android so I am looking forward to seeing some of the options with root. Again thank you
Click to expand...
Click to collapse
Thank you for the feedback. We are here to support you.
We monitor the Threads closely from about 10AM PST to 10PM PST USA GMT -8 so if you get stuck we'll be here for you.
prokennexusa said:
This is a simple Step-by-Step guide on How To: Root the Kindle Fire 7" HD. The main group steps are outlined with A, B, C while the sub-group steps are outlined with 1, 2, 3.
Click to expand...
Click to collapse
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you
Backup and Restore
Jayj0ka said:
Your guides are amazing can I request a how to backup and restore possibly, you offer so much information and support that really helps to break down and simplify the process for me.
Again thank you
Click to expand...
Click to collapse
Thank you for the feedback.
We are in the process of creating a How to: Backup and Restore the Kindle System Image
Give me 48 hours for this series. We are working on How to: How to: Install ICS Google Applications and Google Voice Noob (Easy) Version at the moment.
Hi, Excellent guide!
Will this work on Kindle Fire 2nd Gen (10.2.4)
Big thanks, all these How-To guides are great, bookmarked them all