Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache! I also (if this will help) have tried opening up the command prompt from the KFU tools and typed in fastboot -i 0x1949 oem idme bootmode 4000 and all it said was waiting for device and I tried this with the USB NOT the factory cable. I figured I just have to get my computer to configure it. I am pretty noobish when it comes to the Kindle, so any help would greatly be appreciated!
buckeyestilidie said:
Okay so I'm having problems trying to get my Kindle Fire fixed. I first need the drivers installed properly. I've installed them a million times from the install_drivers.bat in one of the KFU's I just don't remember which one. I've uninstalled everything and I'm starting fresh as I thought this would be easy and it's turning into a very large headache. Step by step would be beneficial as I'm very clueless. I've tried http://forum.xda-developers.com/showthread.php?t=2166668 but that doesn't give much help just tells me what to and not how to do it. I know exactly what I need and to do and I've googled for days and still can't find nothing. I have tried plugging my Kindle in with both a USB and factory cable and everytime I look in device manager it says unknown device (code 43). So let's start from here and hopefully I can resolve this headache!
Click to expand...
Click to collapse
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
soupmagnet said:
Your aversion to use the information available to you is a little disappointing.
Ignoring the fact that you have another thread where this problem is already being discussed, the "Kindle Fire for Beginners" guide, linked to in the FAQ thread that you mentioned, has information on how to properly install your device drivers. The FAQ thread also points to another resource that can help you figure out your device driver problem. If that isn't enough, there is information on where to go when you have exhausted all of your options and still cannot get your drivers working. You ask for a step-by-step guide...well...there they are. Somebody has already gone through all the trouble of doing that for you ahead of time.
Writing a step-by-step guide (again) to tell you how get your drivers working properly, takes a little more effort than just saying..."Do this, do that, then do this, blah blah blah. There is no "one, two" fix to get your device working again. You actually need to educate yourself a little to understand what's going on. It'd be one thing if you had at least some experience, and you tried to resolve the problem yourself and failed, then asked for help. But you're starting from nothing, with nothing. Asking for a step-by-step tutorial from someone at this point is like asking someone to teach you how to read when you don't even know your alphabet yet....that person would have to FIRST go through the trouble of teaching you the alphabet, and THEN teach you how to read.
If you used the information available to you, and you had a specific question about something that wasn't necessarily covered in that information, or if there was something in that information that you didn't understand, I'm sure you would find that there are lots of people around here that are willing to help you figure it out. Otherwise (and I'm speaking from experience), it is very unlikely that you would find anyone of appropriate knowledge to even put forth the effort.
That being said...
...as many people around here can attest, I am always willing to help those in need (even you), assuming those in need (you), are at least willing to meet me halfway first....but I'm not going to hold anyone's hand, and I doubt anyone else will either.
Click to expand...
Click to collapse
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
buckeyestilidie said:
You're acting like I haven't tried everything. Obviously if I'm asking for help I have tried everything and studied into it and failed. You can check out Droidrzr.com, I am very knowledgeable and insightful over there. I'm not just coming over here demanding answers, I've tried everything except the liveusb as my labtop doesn't support it. I am patient but I just want help as obviously I'm not doing something right. I have no problem to supply answers to any questions as I need to fix my dads kindle quick. So please I want to start fresh and figure out what it is I'm doing wrong.
Click to expand...
Click to collapse
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
soupmagnet said:
Believe me, I am sympathetic to your situation, but without any specific insight as to what's happening on your end, other than the fact that you can't get it to work, I have no choice but to assume you haven't done the necessary groundwork to educate yourself in what you need to resolve your problem.
Did you read the Kindle Fire for Beginners guide? Did you understand all of it? If not, what didn't you understand? Have you checked the hardware ID of your device in the device manager and made sure it is in your 'android_winusb.inf'? What have you tried? What haven't you tried? The same goes for any other guide, tutorial or tool that you have been directed to.
No one can see anything you're doing or not doing, so without the appropriate amount of information to give us a clue to the specifics to your situation (other than drivers aren't working), you're just wasting your time. Are we literally supposed to assume you've actually tried "10 million different ways" to get your drivers working? Or do you think it would be more beneficial for everyone to know exactly what you have tried so an appropriate solution can be suggested? You haven't even told anyone what operating system you're using.
Put yourself on the other side for a moment, and imagine someone came to the Driodrzr.com forums...and despite a wealth of information available to them, the only information you can glean from their situation after six different responses across two different threads, is that they have tried "10 million different ways" to get their drivers working, yet they are still unsuccessful. Would you automatically assume they read and understood all of the information available to them and actually put that information to use...all while paying close attention to detail and following all instructions to a 'T'? Call me skeptical...but I think you wouldn't.
[Edit:] In case you're wondering, this is a more appropriate way to present your problem...
http://forum.xda-developers.com/showpost.php?p=40447680&postcount=149
...it isn't perfect, but it at least paints a good picture for anyone who reads it to get a decent idea of what's going on.
Click to expand...
Click to collapse
Trust me I understand, I think I'm just frustrated from not being able to figure this out and yet it sounds so simple. I am running windows and I can't check my hardware ID's because every time I go into device manager it says unknown (for the Kindle device). I'm gonna try on another computer but if you can tell me why it says unknown and how to solve it I believe I'd be good from there.
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
soupmagnet said:
There could be a number of reasons why your device manager shows "unknown device". Your bootloader could be malfunctioning or you could just have the wrong information listed in your 'android_winusb.inf' file. It would be helpful to know what hardware IDs are listed in it.
It would also be helpful to know if there is any change in how your device shows up in the device manager when the factory cable is plugged in. On that note, where did you get your factory cable? Did you purchase it from Skorpn, or did you make it yourself? What happens to your device when you plug it in with the factory cable? We've already established that it sits at the Kindle Fire logo, but which one? Does it stay at one brightness, or does it go dim after a few seconds?
And I can tell you are running Windows by the fact that you have a device manager, but what version is it? What prevents you from being able to boot from a liveUSB on your computer? (BTW, this is required if your booloader is malfunctioning)
The more information like this that you can provide, the better chance you will have at getting your problem fixed. Paint a picture. Imagine you're explaining to a blind person next to you what's going on on your end.
Click to expand...
Click to collapse
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
buckeyestilidie said:
Okay so I went onto another computer and it shows Andriod phone then the ADB interface. I immediately became exuberated with joy! Now do I do fastboot? Can I use KFU to just hit the option to put TWRP on? I don't wanna mess nothing up as this is all the computers in my house lol. If I do fastboot how do I open up the commands for it? I know I must shift and right click on something I just can't remember what. Thanks for the patience with one man who's finally got something to look forward to when it comes to his Kindle! I also just used a simple USB cord not the factory cable.
Click to expand...
Click to collapse
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
I used a USB and it said offline in the KFU but it went to the menu to where I could hit options. I never tried the factory cable but I will when I get home. Also since I'm close to fixing this do you have an idea of what is the most stable ROM to put on this? I'm doing it for my dad so he's not into speed or processing anything. Just looking for a stable ROM that has good battery life.
soupmagnet said:
Plug your factory cable in to make sure the device is actually in fastboot. Does KFU detect your device while in fastboot?
Click to expand...
Click to collapse
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
buckeyestilidie said:
The FAQ just says I change the bootmode. I know I must shift right click on something to send those commands but I just can't remember what, do you know what I shift right click to send those commands to fix this Kindle? Also can I just send TWRP to the Kindle through those same commands? Also I read the FB guide and the codes USB\VID_1949&PID_0006&REV_0100
USB\VID_1949&PID_0006
popped up in the hardware ID's so I know it's in FB. I just need to know where I shift right click to enter these codes: fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
soupmagnet said:
If KFU can detect your device in fastboot , you can use it to install custom recovery, FFF, and/or change the bootmode respectively. It uses fastboot commands to do this when your device is in fastboot mode. When your device is booted normally or in recovery, it uses ADB commands instead.
But...
...if you were to enter the commands manually, the fastboot.exe(adb.exe) must be in the same directory from which you are entering the commands. You can either change to that directory using the 'cd' command at your command prompt, or you can open a new prompt in that directory by pressing shift + right-clicking on that directory, then selecting "Open command window here". Some versions of Windows don't support opening a command prompt in this fashion, BTW.
As for your question of what ROM is the most stable, it would be safe to say that all JB/CM10 based ROMs are quite stable, but CM10. If you want a ROM that has good battery life, you might want to go with a GB/CM7 based ROM, but they're not as nice to look at and kind of awkward to navigate....simple things like changing the volume can be a chore.
Click to expand...
Click to collapse
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
buckeyestilidie said:
My other computer I'm using doesn't support this :/ what can I do to get the KFU to recognize this? Also how do I change the bootmode?
Click to expand...
Click to collapse
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
soupmagnet said:
If KFU doesn't recognize your device, it's unlikely that fastboot will work anyway. You can confirm this by entering the following in the command prompt...
Code:
fastboot -i 0x1949 getvar product
...if it returns "kindle", you are good to install custom recovery, then change the bootmode.
Commands for installing custom recovery and changing bootmodes can both can be found in the "Kindle Fire for Beginners" guide.
If the previous command doesn't return a result, you need to fix your drivers.
Click to expand...
Click to collapse
I entered in a command prompt and It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
buckeyestilidie said:
It says 'fastboot' is not recognized as an internal or external command, operable program or batch file. I take it this means my freaking drivers aren't working :/ so since the kindle registers as Android ADB Interface what do I need to fix? I thought this was what I was aiming for?
Click to expand...
Click to collapse
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
Then I can run the kfu?
soupmagnet said:
NO. You have to change directories ('cd') with your command prompt to the directory containing fasboot.exe. I just told you that two posts ago.
Click to expand...
Click to collapse
My computer won't allow me to open a command prompt from the FB.exe though
buckeyestilidie said:
My computer won't allow me to open a command prompt from the FB.exe though
Click to expand...
Click to collapse
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
kinfauns said:
OK, so what are these commands?
To get started, click on the Start Menu to begin. Then, depending on the version of Windows, either use "Run…" or "Search" and type "cmd" to open up a command line window that will look a lot like...
{
"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"
}
The last line in this example is called a prompt and it's followed by a blinking cursor.
The prompt tells you where you are in the directory structure. When the "cmd" program first starts up, that location is your Windows user's home directory by default. In the above example, my username is "kinfauns" and my home directory by the same name is in the "Users" directory located on the "C:" drive. The "C:\Users\kinfauns" part of the prompt is the directory path and it uniquely describes the location of the home directory owned by the "kinfauns" user.
The blinking cursor indicates the program's readiness to accept a new command. Each time you execute a command, a new prompt/cursor will appear at the bottom, telling you that it's ready for you to type another.
Now type "dir" (without the quotes) and press Enter, and you'll see the names of all the folders in your home directory. The "dir" command just prints out a content listing of the directory indicated by the prompt. If you open up your home folder in Windows Explorer and look inside, you'll see everything in that folder shown in the list you got from the "dir" command. The "dir" command implicitly operated on the current directory shown in the prompt, but you can also provide an explicit argument to tell it what directory to list. For example, "dir C:\Users" lists all the users directories. Providing an argument after the command name will be important for the next command...
The "cd" command is used to change the current working directory. We need to get to the KFU directory, so we can use "C:\kfu" as an argument to the "cd" command. Type "cd C:\kfu" and press Enter to change to that directory. No output was provided, but the new prompt has a different directory path to confirm the "cd" command has executed successfully. You can try "dir" here to list the contents of the "C:\kfu" directory, but it's not necessary to first list it if you know what's in there already. In this case, we'll "cd" into the "C:\kfu\tools" directory, but you won't have to provide the full path. Since "C:\kfu" is already the current working directory, "cd tools" is equivalent to the "cd C:\kfu\tools" command. The one other key component to navigating the directory structure is the ".." directory. The ".." directory refers to the parent of the current directory, so "cd .." will take you back up to "C:\kfu" and another "cd .." will take you up to the "C:\" directory.
Now you'll be able to navigate through the directories and you should have a fair idea about how to construct a directory path (this will come in handy later). The fastboot and adb executables are in the "C:\kfu\tools" directory, so you'll have to get there using what you learned to be able to use them in the next section. There are just a few more tips that might come in handy...
Shift-right-click on/within a folder and select "Open command window here" to open a command line window with that directory path as the current working directory.
File/folder names or directory paths containing spaces must be enclosed in double quotes.
Drag and drop a file or folder from the Windows Explorer windows into the Command Prompt window. The complete, absolute path of the object will be pasted into the Command Prompt window automatically.
Utilize the "Tab" key to complete a file/folder name without typing it in its entirety (e.g. Try typing "cd C:\kfu\to" and then hit the "Tab" key).
For more information on Windows cmd commands, bleepingcomputer.com has a nice introductory tutorial and ss64.com has a full reference page of commands.
Click to expand...
Click to collapse
I seriously hope you'll learn from this and actually pay attention next time you read something.
soupmagnet said:
THIS RIGHT HERE is why I am so adamant that you read the information available to you and pay attention to what's being said.
The 'cd' command stands for "change directory". You use it to change the current directory of the command prompt (default is your User directory) to another directory. The correct usage of that command is...
Code:
cd
If you don't know the path of the directory you want to change to, right click on it and select "Properties".
If you still can't figure it out, type 'cd' (without quotes), enter a SPACE, then drag that folder into your command window. The rest should be self explanatory.
[Edit:] CASE IN POINT...Quoted directly from the Kindle Fire for Beginners thread
[/LIST][/B]
I seriously hope you'll learn from this and actually pay attention next time you read something.
Click to expand...
Click to collapse
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
buckeyestilidie said:
I changed the directory to the tools subfolder in the KFU folder. I tried typing the commands I told you 2 or 3 posts ago. It gave me 3 dots and I waited 10 minutes and nothing. Now what am I doing wrong?
Click to expand...
Click to collapse
Nothing. That's normal when changing bootmodes in fastboot. Rebooting will boot your device into that particular bootmode.
But simply changing the bootmode to normal (4000) isn't going to fix your device unless there wasn't anything wrong with it in the first place. You'll likely need to access recovery to fix the original problem.
soupmagnet said:
Q16: What does it mean when my device is stuck at the Kindle Fire logo?It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.
Click to expand...
Click to collapse
Related
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
I did it on my MBP. What problems are you having?
I did it on my macbook..
I also did it on my Mac. Like someone else said what specifically is the issue you're encountering?
there is a post in about using Terminal app from the market to do this and it works!
brianb7590 said:
I did it on my MBP. What problems are you having?
Click to expand...
Click to collapse
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
nitty917 said:
thanks, I cant get it to communicate in terminal,
i have no idea. i dloaded the sdk, dragged the adb from tools folder,
onto the terminal, it opens up all the adb commands but after that i cant type
nothing.
Click to expand...
Click to collapse
Don't drag it to the terminal.
I would navigate to the directory where you stored the SDK and go to the tools folder and run it that way or you search up how to set your PATH to include the tools folder.
nitty917 said:
tryin to get mac to adb to device, but cannot get it to work.
anyone have success? would like to test these nice roms out.
thanks
Click to expand...
Click to collapse
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
okolowicz said:
Like the others who have already replied, I also did it on my mac and was a complete noob. It was only through much trial, error, YouTube, and 3 other sites that I figured it out. Needless to say I'm now fluent in adb and would be happy to answer any questions you have since I was in exactly the same shoes as you last weekend. Below are the biggest things you need to know when you start:
1. When you plug the phone into your computer make sure you select "Charge Only." If you select "Use Phone as Disk Drive" you won't be able to write to the phone, only read. I ran in circles for a long time getting "Read-Only File System" errors and it was all due to having the phone mounted as drive.
2. Make sure you have USB Debugging turned on. After that, you should be able to communicate with the phone fine.
3. ADB - The instructions are nearly identical regardless of operating system but on a mac you need to add "./" (without the quotes) before adb commands. For example, lets say I have a file on my desktop called "Test_File.img" that I want to push to the root of the sdcard. On my Mac I would type "./adb push /Users/Bryan/Desktop/Test_File.img /sdcard/" (without the quotes of course) & (Bryan is my Username)
4. To avoid any issues make sure none of the folders or file names you are working with have spaces in the name.
Hopefully all this helps and does no lead to more confusion than when you started. Again, if there are any specific errors you are seeing post them here and either I or someone else would be happy to answer them.
Bryan
Click to expand...
Click to collapse
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
mocalve said:
If you're going to be using adb on a regular basis, and want to avoid typing "./" before each command, you can add the android sdk tools path to your .bash_profile file in your home directory. Something along the lines of:
export PATH=${PATH}:/path_for_ur_sdk_folder_location/android-sdk-mac_86/tools
Click to expand...
Click to collapse
That wont be saved. It goes away after every reboot.
Fixter said:
That wont be saved. It goes away after every reboot.
Click to expand...
Click to collapse
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
mocalve said:
True, if you enter it from the command line. But if you add it to the .bash_profile file , it will stick... at least on my Mac Pro it does...
Click to expand...
Click to collapse
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Fixter said:
If I add those entering nano .bash_profile and enter that command and the pressing Ctrl X and Yes it will stick?
Click to expand...
Click to collapse
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
mocalve said:
It should... although I use vi instead of nano. Regardless, after saving the .bash_profile, you'll have to fully exit the terminal application and restart for the path setting to take effect. After that, it'll be in effect every time you start terminal.
Click to expand...
Click to collapse
Nano is way cleaner. And yeah. It got applied.
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
dbc00per said:
ive tried everything i read in most of these forums, and i know im missing something so stupid, so feel free to point out the obvious. but i cannot or have not ever been able to issue a command using adb.exe ive adjusted path name to were my android sdk is located. i know that the adbexe. in the tools folder itself doesnt open but i cant seem to get it working from command prompt either. im rooted and i thought i was nand unlocked until i tried recently to flash fresh's latest rom. (hboot 0.79.0000.) im currently running fresh.3 and would like to update. currently i have clockworks recovery running in rom manger because everytime i use ra amons i cant get into recovery at all to flash fresh update. dos opens up and shuts down after running some unknown commands. Being a noob to android coming from the iphone im at a loss. consider myself tech smart i can follow and understand most things. ive jailbroken and rooted my two previous phones so not a total noob. i just want to be able to do this one task its like a brick wall ive run into and im at a standstill!!!!! anyy help anyone could offer would be greatly appreciated
Click to expand...
Click to collapse
This would be better suited for Q&A that being said post the commands you are issuing and the errors you are getting. This would help someone trying to help you. Good luck
Try posting in clear concise sentences and it will help as well. Your post is like reading a teenagers tantrum and it's hard to follow.
From what I gathered, you can't get ADB to work, even though you're attempting to run it from a command prompt but the command prompt immediately closes from some unknown commands. That makes no sense.
From your computer, in windows, browse to the Android SDK folder.
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
With your phone connected via USB and debugging mode enabled type:
adb remount
and press enter.
What do you get?
First off...wrong section, this belongs in Q&A
Anyways...
1) Go to Settings -> Applications -> Development -> Enable USB debugging
2) Make sure HTC Sync is installed. Link
3) Right-click My Computer and go into Device Manager (while your phone is plugged in), if you see any yellow flags or unknown devices, remove them.
Now unplug your phone and plug it back in.
4) Place the sdk folder on your C:\ and run command prompt in Administrator mode.
Type "cd " (don't forget the trailing space), do not hit enter yet.
Now try to physically drag the tools folder into the prompt window, it will type text for you.
Hit enter.
5) Type adb and it should work.
If it doesn't work, well, you're going to need to give us more details...especially since if you follow what I wrote above correctly there is no reason it shouldn't work.
Sirchuk said:
Hold down the SHIFT key, and RIGHT-CLICK the tools folder and then LEFT CLICK "OPEN COMMAND WINDOW HERE."
Click to expand...
Click to collapse
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Neotelos_com said:
Does that work in XP?
Click to expand...
Click to collapse
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Neotelos_com said:
Does that work in XP? I've never heard of that shortcut and it doesn't work on my current workstation.
Click to expand...
Click to collapse
Only works in vista and win 7
gx1400 said:
Oh gosh... i hope thats a work PC...
Its just a simple way to open up command window into that folder. Just Winkey+R, type 'cmd', hit enter, then navigate to the tools folder through command line. Hopefully you know command line well enough.
Click to expand...
Click to collapse
Yeah like I said "workstation", I don't call any of my personal machines "workstations".
Also, I'd hope I know command line well considering I just gave advice on how to run adb through it.
thank you I've just gathered more information here than searching for days
Anywhere else.
hi guys,,
love your forum....
simple NOOB question plzzzzzzzzzzzzz...
how do i get into fastboot,,,,
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1668159
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
My Kindle is never recognized by KFU . Here's what you need:
Android SDK
Working adb and fastboot
KFU
On windows 7 shift+right click in your KFU tools directory and click "open command window here"
Here are the commands:
adb devices (your device should be listed)
adb shell (make sure it shows up as root, there will be a #, if not su)
idme bootmode 0x4002
reboot
Then your device should be booted into fastboot mode
He could be having the same problem I had, no /system/bin/sh so the adb technique will not work. I had to make a factory cable, which got me into fastboot mode (but ROMS still are not applying right, that question is in another thread).
gdjy said:
i have a kf and installe dthe drivers and every thing but no fastboot no adb nor even the KF tookit can detect my KF.... just cant get it into fastboot mood..
Click to expand...
Click to collapse
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
SLOmtb said:
This is a shot in the dark, but have you checked that there is a .android directory under your user profile? Does it contain the adb_usb.ini configuration file? For some unknown reason the first time I tried, the install_drivers batch file didn't make the directory, so adb didn't initialize. Windows wouldn't let me make a new folder named .android so I had to go to the command prompt and make the directory myself using the old MS-DOS md command then copy the configuration file.
There is a section in Kindle Fire For Beginners that describes how to verify the drivers are loading. If you haven't seen it, it's worth the read.
Click to expand...
Click to collapse
Thanks for the KFFB plug. Just as an FYI, fastboot doesn't look at the adb_usb.ini file... adb is the only thing that looks at it.
gdjy said:
thanks for your reply.... i v been reading these to threads for very long time,,,, i just cant get the damn thing into fastboot mood... the KFU tool cant communicate with the device at all
i know im a noob but really need help
thanks
Click to expand...
Click to collapse
I just updated my fastboot guide (the second link I gave you) with details on how to get the hardware IDs and identify whether or not you are in fastboot mode. Take a look again and see what your hardware IDs are. If that doesn't help you, post a more detailed description of what you are doing, what the device is doing, what errors you get, etc. The more details you can provide, the easier it will be for your helpers to determine what's happening. Look at the sticky post at the top of this section.
i know this is also a stupid question, but how do i issue the "fastboot oem format" command? i tried partitioning my kf but it failed....
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
jma9454 said:
hey guys. I have a demo unit.
Now before anything else, I should say that I looked at all three other threads on demo units, and that didn't help.
I looked at ThePooch's alternate method, and it didn't work.
In KFU, it gives the output of what is in the picture.
and in Soupkit, it says "permission denied" when trying to install either FFF or TWRP (I can't remember which, but if this is important, I will find out).
Can someone shed some info on what to do?
More pics are available to those who ask.
Click to expand...
Click to collapse
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
I have witnessed one demo unit that was completely unrootable even with the use of a factory cable. So at the end it was only good for parts and the motherboard unusable.
soupmagnet said:
Use SoupKit to change the bootmode to fastboot, then install TWRP. See if that helps.
Click to expand...
Click to collapse
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
That`s pretty much what I experienced with the demo unit that would not root, it simply would not enter fastboot no matter which approach I took. I can take a look for you but I feel it`s pretty much a moot point if it wont enter fastboot. Power the device off, open a terminal
Code:
fastboot -i 0x1949 getvar product
hit enter, when it says waiting for device, plug the kindle in. if it does not enter fastboot and return product: kindle you are dead in the water.
jma9454 said:
This could be the VMWare problem that you were mentioning in the other thread. upon reboot, VMWare says something to the effect that it could not connect to the kindle because it is in use by another program. I will try USB-Ubuntu in a few hours, but I think it didn't work last night, if i remember correctly.
Click to expand...
Click to collapse
I've really gotta start reading the names on these posts
jma9454 said:
when trying to switch bootmodes, Ubuntu just reboots the kindle. It isn't able to get into fastboot. If I could figure out how to take a screeshot of this I would, but I don't know how.
Anyways, I forgoed that, and tried to just do the TWRP installation and this is what I got:
Verifying MD5 checksum...
openrecovery-twrp-2.2.2.1-blaze.img: OK
Checksum matched.
Installing openrecovery-twrp-2.2.2.1-blaze:
Please wait...
1122 KB/s (4972544 bytes in 4.324s)
/dev/block/mmcblk0p5: cannot open for write: Permission denied
Team Win Recovery Project has been installed.
Do you wish to reboot into recovery now?
-- any ideas?
Click to expand...
Click to collapse
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
In my opinion, your best bet would be to forgo the VM, forget about the dilapidated WinXP computer and figure out a way to boot your Win7 computer into Ubuntu from a USB stick. You are dealing with way too many variables to effectively determine exactly where things are going wrong.
I 'fixed' two demo KF's, messed up a lot on the first (lucky I didn't brick it).... On the second, I used a fast boot cable and installed TWRP, had a JB ROM on it in 15 minutes.
Try this.... Send TWRP to it using the command line, when it says 'waiting on device', open another window and get it to reboot in fastboot mode. On the first KF I found the utility would only put it in fast boot for a few seconds, but it was long enough to write TWRP if you did it this way.
Not sure why some won't work at all, maybe Amazon got smart on the demo units.
Larry
Sent from my Kindle Fire that thinks it's a Nexus 7
soupmagnet said:
I've really got to start reading the names on these posts
That's the tricky thing about ADB and shell scripts. I won't go into too much detail, but part of that has to do with how ADB handles the exit status. Typically in Linux, an error results in an exit status of 2 (sometimes 1 depending on the type of error). ADB tends to have errors come out with an exit status of 0, which is why it said TWRP had been installed, when in all actuality it hadn't. The reason TWRP wasn't installed is because you need to either have root privileges, or be in fastboot, hence my previous instructions to boot into fastboot first.
Click to expand...
Click to collapse
The above statement took place from USB boot, not VMware. Also, like I said, I attempted to set it into fastboot and it just booted regularly. I tried several times with different cables and ports with no success.
Sent from my Amazon Kindle Fire using Tapatalk HD
I will stick with my original idea no fastboot = no fun. You cant push FBmode manually because installation from unknown sources is disabled by default on a large percentage if not all demo units. Regardless if the device doesn`t enter fastboot not much you can do. Taking advantage of the small window of fastboot at boot is risky if the write time isn`t long enough to get it sent and written but it could be your best bet. IMO I would not attempt this with the bootloader only recovery no harm no fowl.
What are the odds of hard-bricking the Nexus 7 while rooting and istalling a custom kernel? And if it bricks, is there a way to fix it?
I ask this because I want to root it, but I'm really worried.
Also, how can you fix a soft brick?
I think you should really care of these questions if you somehow corrupt both bootloader and recovery. I don't really know, but bootloader isn't a thing that is modified during rooting or changing kernel. Just carefully read the thread about rooting programs, follow the instructions and everything should be ok. The most potentially harmful thing that can be done is corrupting the recovery. It can be solved if you have a computer with adb and drivers installed. Just a sшmple command and recovery is reflashed. Unlocking the bootloader is a kind of thing that doesn't really change anything so you couldn't boot or something. It just clears the storage and changes something deep inside. Flashing ROMS/Kernels is a kind of coping files and if something goes wrong you can always reflash it from recovery or with adb or some app from the rooting kit. And also you can always flash everything stock. Just read and think of what you're doing. Good luck.
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
LittleConfucy said:
Can you help me, when I type fastboot oem unlock in the command prompt, it says <waiting for device>. Any idea?
Click to expand...
Click to collapse
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
rtfpessoa said:
You probably have not configured devide ids for adb.
But probably the use of "sudo" should solve your problem.
Click to expand...
Click to collapse
So, what do I have to do?! Sorry, I'm a complete noob xD
LittleConfucy said:
So, what do I have to do?! Sorry, I'm a complete noob xD
Click to expand...
Click to collapse
Just run:
sudo fastboot oem unlock
rtfpessoa said:
Just run:
sudo fastboot oem unlock
Click to expand...
Click to collapse
It doesn't recognize sudo as a command
LittleConfucy said:
It doesn't recognize sudo as a command
Click to expand...
Click to collapse
Are you on windows?
If yes, are you on bootloader mode?
If not:
1-Power off
2-Power On + Vol. Down
Then you execute "fastboot oem unlock"
If it doesn't work try to use any of the auto tools that you can find all over XDA forums
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Do you have any idea where can I see the drivers that were installed on the computer?
Slavon-93 said:
LittleConfucy, as you haven't told us what OS you're using, I'll assume it's Windows 7 or 8, doesn't really matter. Go here, download, install, launch, press the big button on top named "Full Driver Installation" and read what it tells you to do. It's written clear enough to understand. Just will give you some tips.
1. To install adb drivers, you should enable camera mode. It can be done in Settings->Storage. Just click on 3 dots and go to the USB connection settings. Select the option with PTP in its name and uncheck MTP if checked. After that your device should be recognized properly.
2. This App had a bug some time ago. It downloaded drivers and couldn't find them later. The workaround is to copy c:\Program Files (x86)\WugFresh Development\data\drivers\universal_drivers\UniversalAdbDriverSetup7.msi and rename the copy to UniversalAdbDriverSetup6.msi. It'll help.
Click to expand...
Click to collapse
So I have to copy the file, paste it in the same directory, without deleting the previous file, and change its name?
Need help...
After I rooted, I opened BusyBox and it said:
"There was a problem opening a shell with root acces. This is either being caused by superuser/supersu or by a device that is inproperly rooted."
I downloaded root checker, and it says that it's not proprly rooted