Related
Every since the root method came out, I've been trying to root my phone for hours and hours and I haven't been able to. Since this is a problem for quite a few other users, I figured we should have a thread just for this problem since the rooting thread is over 30 pages long at this point.
My problem is that I see the device in offline mode for a few seconds, and after that it displays an empty list again.
What I'd like to know from people who managed to root their phones, if they had to try something different from the instructions to get passed the adb loop step where you have to catch the device in offline mode? What OS are you running (Win, Mac, Linux and x86 or x64)? How many times did you try?
I got past the loop by hitting ctrl c as soon as it detected the device it worked for me. it seems if you let the loop continue and you get device not connected you have to try again. I was able to get this to work consistently twice.
Getting the adb portion of this is what took me the longest in the rooting process.
Had your same problem on Ubuntu
Had same problem on windows 7 64 bit
UNTIL:
installed pda net - then htc sync, then removed android device driver, then installed the (r3) driver from android sdk... the update you can download through their program.
After that it worked like a charm first time.
my best advice is to start running the loop just before you click recovery from the boot loader screen.
Once you got it, theres no need to be quick with control C - it stays there.
- Faylix / local
the PDANET program seems to mess with the offline loop thing.
Once I closed it, it goes through just fine..
The only problem im having is that im getting a E:Failid to verify whole-file signature when i push the update.zip
And also I've used both Windows 7 64bit and XP 32bit to no avail...
My guess is its all about the drivers. I must have mine all mixed up. I am stuck in loop with no device found either. I will try one more time with pdanet off but Ive tried on a pc without it too anyways.
Someone really needs to write an indepth guide like the G1 because drivers arent even meantioned in the guide and I know its a big part of it especially if you have had other android devices before with sdk plus adb. One thing I do notice is all of us with the loop issue have touble with the device showing in device manager. It displays android 1.0 instead of mts or adb whatever it supposed to be. If your device isnt recognized from hboot it wont make the proper jump into recovery. Hence the loop issue. Can anyone with root ellaborate this a bit more?
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
You are a godsend. Spent the last two hours trying to time this just right by doing Step 2 and 3 over and over and over. 5 minutes after reading this post - Hello, Clockwork.
Lol
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
I was having some trouble to, I found something else that I was gonna add but it was only on my end... I didn't have the same problem rooting my wifes. I will watch this thread and if I see any more posts I will drop my piece. Im glad someone else could post this before I could.
shinkinrui said:
@jnight
You're very close. I had this happen to me too. What's happening to you is the first try failed but the update.zip still got pushed to the SD Card. Here's what you do:
1) adb push ota.zip /sdcard/update.zip
2) Type in "push update.zip /sdcard/" on your computer but don't push enter yet
3) Choose "install update.zip" in the phone. AS SOON AS the green bar appears behind the letters, press enter on your computer.
If you miss the timing and don't see clockwork recovery, you NEED to go back to my step 1("adb push ota.zip /sdcard/update.zip") or it will continue to fail no matter how many times you try because you HAVE to start with ota.zip as the update.zip on the SD card. The trick is getting the phone to verify the signature from the ota.zip and replacing it with update.zip to enter the clockwork recovery. Once you're in clockwork recovery, it's a breeze- just follow the rest of the stickied root tutorial. Hope this helped
Click to expand...
Click to collapse
Thanks Man, I guess I was pressing the Enter button to fast...
Got past eveything except the "SU" it says "Permission Denied"
NM about this post for some reason it started working after I installed "Setcpu". Went in to Terminal emulator and it gives me the # just fine..
For some reason its just ADB that gives Permission Denied..
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
AngelsShadow said:
"Step 18.
adb install Superuser.apk (If this looks like it works, but says it cannot locate directories, make sure you can find your device using adb devices… If things still don't work, my best advice is to start over)
Step 19.
After Superuser is installed try to use adb to shell to your device.
adb shell
you will get a $
Then type su
Superuser should pop-up asking if you give permission, do so.
Your $ should turn into a #. If so, you have root."
Make sure you run this or you wont get SU rights, this programs needs to be installed to allow the SU rights.
Click to expand...
Click to collapse
Thank you thank you....
I've been repeating myself over and over regarding this...
It's the Number 1 issue why people can't Root & Flash to the ENGINEER Build!!
Still a no go
Marvin,
I am still getting the two device OFFLINE showing after going into recovery from hboot. I deleted ALL of the HTC SYNC software and drivers and ONLY installed PDAnet. I now can see the MY TOUCH SLIDE device when connected in hboot, unfortunately I still am having the same stupid problem. So since it's not showing android 1.0 anymore and still having the same problems, we might have to explore some other avenues. FOR THE LOVE OF ROOT SOMEONE PLEASE HELP US!!!
If you run loop and go to recovery and only see the device offline a couple times then it goes away, I do not think it is a driver issue at that point. As someone in the root thread explained, the loop is simply trying to catch the device in ADB mode as it's going into recovery. And then, randomly, it will "stick" in ADB mode. Now, I am not sure if there is a difference between our devices for those of us having trouble getting the ADB mode to stick.
Ok, I'm giving up. I have tried this hundreds and hundreds of times. I know I've followed the instructions the correct way (I've seen the video and read countless forum posts). This simply cannot be done on my phone. I am going to take it to the store and try to exchange it, perhaps for a black one.
Does anyone else have any suggestions?
as i posted in the other thread i was having problems trying to get adb "stick" open when i went from the bootloader into recovery so i went into the file explorer and right clicked on my computer then went to manage devices then went to the driver tab then clicked on update driver right before i went into recovery and this is what finally worked for me. the purpose wasnt to change the driver the purpose was to trick my computer into keeping adb open
Re: Getting passed the adb loop step
I had to hit power on phone and enter on pc at almost the same time to get it working. Then I realized that after you reboot, it boots back to your normal phone not recovery and then adb devices it shows up.
-------------------------------------
Sent via the XDA Tapatalk App
Re: Getting passed the adb loop step
Ugh none of these tricks have worked for me.. Still Stuck .. Maybe it's a computer issue.. Guess ill try a friends computer..
-------------------------------------
Sent via the XDA Tapatalk App
Maybe/hopefully someone will find a different/easier way to root these for those of us stuck here. I've also tried, exhausting many many things, everything from timing of hitting loop/recovery, all the way to almost completely breaking the ADB driver on my PC. This is thoroughly frustrating the hell out of me.
By the way, add "ECHO OFF" (without the quotes) to the top of the batch file. It makes it easier to see when it reads out the offline devices.
Re: Getting passed the adb loop step
If you go to settings then pc connection . What seeting should it be? Drive , sync, or charge?
-------------------------------------
Sent via the XDA Tapatalk App
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Did you do "adb shell" and then you tried more adb commands and got "permission denied" ?
If so, then that's because "adb shell" starts a command prompt session on your phone, and the adb commands need to be run on your PC, not your phone. So don't do the "adb shell" first.
So wait a second, you're saying that the wonderful wiki, either is in the wrong order, or requires me to follow the pc, and phone steps simultaneously? Because im running them from my pc. Which would be implied by my saying im following the wiki. Fyi, i meant the one on the g2, involving rooting the g2, on the xda-dev site. I've done this before, i know how to use adb. this is the first time i have rooted a g2. Don't mean to sound like a ****, but you basically didnt read anything i wrote.
The Wiki isn't in the wrong order. But IMHO it's very confusing that it shows a $ prompt when it shows "adb push" etc, because that makes it looks like it is run on the phone. But it's assuming you're running from Linux/Mac. On a PC the prompt for your adb commands would be C:\ or similar.
The Wiki doesn't tell you to run "adb shell"
So the answer to my question was yes, it works, but i had to wait 5 minutes to post this. I dont understand why there cant be a note that, unless you put adb into your path, cmd isnt going to recognize it unless its in the folder you're using. I feel no need to put a tool that i will use maybe once a year at most into path. also, when i just checked the wiki now, i noticed how the dollar signs had changed to c:/ ha ha. and sorry about the rudeness, at first it just seemed like you were making fun of me.
jenlow said:
Okay, so before i opened the adb shell from cmd, when i would type adb push, i would get adb is not recognized as an internal or external command. so, my solution of putting the adb tools into gfree, should work now once i cd to the gfree folder?
Click to expand...
Click to collapse
That's an issue with your path not being setup properly on your PC. You can adb adb's folder to the path to mean you can run it from anywhere. Otherwise you need to put the gfree tools etc in the same folder as adb, then cd to there and run the commands.
Or if the path is setup properly, cd to where the gfree tools are and start doing your "adb push" etc from there.
I have just edited the Wiki to show a "C:\" prompt for the stuff that's run on the PC, to try and avoid this confusion.
Did it work ?
jenlow said:
In the process of following the rooting wiki, had hella problems getting adb working. Got adb connected finally, got the money sign, tried first instruction, got adbermission denied. What could be the problem? Did a google search as well. I have the contents of adb tools, in the same place as g free, as it is completely impossible to start up adb shell, and then navigate to a completely different folder. Also, before moving adb tools, tried long addresses of the gfree stuff, same deal.
Click to expand...
Click to collapse
the "permission denied" thing... from the phone? Or from the computer? You know you need to be root in order to access the hardware, or at least set the permissions on the hardware to be accessible to your user account....???
And... you DID enable adb on the phone side, didn't you?
I used the Wiki and am now perm rooted. A few tips that may help you since they helped me to get it done. I opened a command prompt and noted the default path that opened. For me it was C:\Users\Ed . I used windows explorer to navigate there and open up the Ed folder and created a new folder in Ed that I named pr. This is where I unzipped both of the gfree zip files...into that same folder. When temp rooting and perm rooting, I simply opened up the command prompt, it opened to C:\Users\Ed and then I typed cd pr then I hit enter. That set me up to input the commands in the right place both times and it worked out just fine.
Another thing that I noticed. After temp rooting, I had to ctrl alt del to open up task manager and close down adb.exe (as noted in the instructions that appeared in terminal emulator). I couldn't load adb again until I closed it down and let it restart itself. When I entered the first command in the perm root process adb started up again by itself and all went well.
Good Luck! It is well worth it. I now have Cyanogen's latest stable build loaded along with the Google apps package that I found online.
Ed
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Root my phone!!! HELP
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
mannær said:
Hi Guys
I've tried root and my cell phone, but it is not. I've tried almost everything I have .. First I tried to root using the terminal emulator''''by typing different commands ..
Also, I tried the program''Visionary''but when I pressed the application so that it was held to root, but then the screen goes black, and I had to press the home button to get out of the situation ..
Also tried I saw another app called ''Universal androot'' and when I pressed root, then came the''Failed! No ~~~~~~~~~ Fu goo ..'' I also tried''app ''superoneclick I pressed the root, also came the''error: protocol fault (no status)''
What should i suppose to do, to fix this problem.. please reply
Thaaaanks!!!
Click to expand...
Click to collapse
None of those apps work with the G2 to perm root without extra steps. And in that case only Visionary. You need to check out the vision wiki page.
Ed thoroughly described how to make it work. I did the exact same thing he did and got it last night.
jenlow said:
OH! yeah, it did work. i thought i said that somewhere ha. I am currently running CM 6.1.1 now. I've decided that since the adb file, and necessary files are tiny i can just move them around to whatever i need to use adb for. Path editing should only be done by hand in linux And jesus CM has improved since i had it on my cliq. I'm like 90% sure i'm going to make a donation out of the school funds.
Click to expand...
Click to collapse
What method did you use to root your cliq, and did you still have 3G? I have stock motoblur 2.1 on it now, I have it for a backup phone (got a G2), but I would like to root it.
Good Morning to everyone (Germany ).
I´ve downgraded my DZ from the actual version to Froyo. Now i want to root it. I was searching for different manuals and all of them said that it´s necessary to check the Infocid. Unfortunately it doesn´t really work on my phone.
http://forum.xda-developers.com/showthread.php?t=905261
The first step seems to be clear. I type in the command and the phone restarts and powers up in the boot menu. But when I type in the second command line, the terminal says that this command was not found. Every files should be in the right folder i think, but it does not work. Do you have any ideas, what the problem might be? I don´t have i file called fastboot oem loader in my platform-tools-folder. Is that the problem?
Thank you very much.
Edit: Now i also found this Thread. http://forum.xda-developers.com/showthread.php?t=1140722 . But what does "set up on your computer" mean? Is it a programm? I got a fastboot folder in my platform-tools with 3 fastboot files for each OS. So: Do i have to rename the fastboot-mac to fastboot? Lot of questions, don´t want to brick it
...so you already downgraded succesfully to 1.34 wwe?
then i would use this guide for perm root:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
...if you get in troubles pm me
Solved, had to rename the command line to reboot-mac
Hi .. would really like some help as I got a replacement G2 and I need to return my broken phone back tmrw and would like to root it.
I actually rooted my first g2 using temp root/visionary about a year ago...
but now I can't seem to understand the wiki's or any guides on how to root my phone again. . help!
Tried the AMT way, says device is not connected
Currently trying to use this guide : http://forum.xda-developers.com/showthread.php?t=1107911
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
any help would be appreciated.. sorry I am a complete noob at this
ahan421 said:
I can't even get past the first step.. in the command prompt I get
"*daemon started successfully*
error: device not found
Click to expand...
Click to collapse
Do you have the HTC Drivers installed? Do you have Android debugging enabled on your phone? I don't know if it matters but I think your sdcard shouldn't be mounted when you connect it to your PC.
With the above things done, you should be able to type
adb devices
And it should list your device and its serial number.
You probably need to install drivers. I'm assuming you're using windows?
You can get the driver package here
You'll need to downgrade first with this guide
Then I recommend the wiki method to root
-Nipqer
I just downloaded the HTC drivers
i'm following the downgrade guide now
i downloaded the 2 files and put them in the platform-tools folder
already having trouble with the first step
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
> adb shell cat /dev/msm_rotator"
where do i type this command?
"> adb shell cat /dev/msm_rotator"
sorry if i sound like an complete idiot.. i have no clue what to do.
alright, i read through some of the adb for dummies
when i type in adb devices i do not see a serial number.. but i've installed the htc drivers already
is there something else i need to install? thanks
edit:* Yay i just got the drivers working, serial number is now showing!
edit 2: i had no idea what i was doing... somehow got through the instructions, downloaded some pda drivers, followed the guides and now my phone is rooted!
i felt like Neo typing in the codes... Thank you guys. Thank you XDA!!
Glad to hear you got it sorted out. Sounds like a good learning experience
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