Develop Bugs

Kindle Turns On Then Off

Hey!
Lately I kept on playing with my kindle until the battery reached 0.
So I charged it but its stuck at the yellow Triangle and it turns off after a second or two.

Your problem is invaluable to the continued efforts of the developers.

Hey Im looking for a proper answer.

JoshuaLintag said:
Hey Im looking for a proper answer.
Click to expand...
Click to collapse
Maybe youll find a proper answer....in the proper forum...aka not the DEVELOPMENT forum ;D

Reported so it could be moved to the proper thread so you wont get flamed q&a
Sent from my Kindle Fire using Tapatalk 2

Help!
Anyone?
Adb does not detect it.

Sadly I am in the same boat! I am not getting anything to work.

http://forum.xda-developers.com/showthread.php?p=25400963
http://forum.xda-developers.com/showthread.php?p=25598837

THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps

JoshuaLintag said:
THANKS!
BUT ADB DOES NOT DETECT IT.
sorry for caps
Click to expand...
Click to collapse
Did you happen to READ THE LINKS GIVEN TO YOU?
not sorry for caps
Your battery is near dead. You probably won't get anything to connect at this point without a factory cable. Which you would have known by READING THE LINKS GIVEN TO YOU.

I couldn't even charge mine

Okay, (even though I know this has been covered in the link I gave you) I'll be nice considering the possibility of a language barrier.
You need to get a factory programming cable (which I've said) so you can get into fastboot. Read about the factory cable and it's purpose here:
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
...and here:
http://forum.xda-developers.com/showthread.php?p=20317299
Then learn how to fix your drivers in case that's also contributing to the problem:
http://forum.xda-developers.com/showthread.php?p=23747671
Pay attention. The fix for this requires installing a new bootloader which (if you aren't careful) can PERMANENTLY brick your device.

Thanks for the links, btw.
I'm 13 and I don't know about making a factory cable, the steps on the links
is quite complicated. And Maybe risky.

Your only option then, would be to get a fastboot connection to flash the new FFF 1.4
This you may need to do several times to get it to work, if it works at all.
Make sure you know how to use fastboot
With the Kindle turned off, enter the following command:
Code:
fastboot flash bootloader /path/to/FFF1.4.bin
When you see "waiting for device" turn your kindle on.
If the installation takes place, all you need to do at that point is plug it into the wall charger.
If after several tries it still doesn't work you may want to try fixing your fastboot drivers. http://forum.xda-developers.com/showthread.php?p=23747671
Otherwise, a factory cable is your only option.

oh crap.
I think it's really dead.
It doesn't work, my computer won't detect it and it won't even show up
on device manager when I turn it on.
sorry man

[Q] Might be bricked.

I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.

And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.

Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?

I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!

How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.

Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed

Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?

Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.

To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034

soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.

Can you boot into recovery? Do you know how?

soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore

Guess I will be buying a new one.

TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.

soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.

fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109

soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.

fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375

soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.

Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".

[Q] [Bricked] Kindle Fire, Please Help

Hello, I bricked my kindle fire by flashing a update.zip file because I wanted to return to stock. I wiped everything from cache to system and now my Kindle Fire just hangs on the KF screen.
I tried using KFU, FireKit, and I can get into adb but I can't access the adb shell and I can not get into fastboot.
Any help would be appreciated. And I don't know if my battery is even charging either. The battery is dead. Thanks.

I'm having the same problem except I soft bricked mine. :c It doesn't even show up on ADB.

I literally just had this exact problem, and the ONLY thing that actually worked was buying a factory cable from SKORPN. After I got it, all I had to do was plug it in and used the Kindle fire utility to install FIREFIREFIFE and boom, it worked like a charm.
Sent from my Amazon Kindle Fire using xda premium

Mine doesn't even show up on my PC or ADB [Kindle Fire Utility]. What should I do? :c Point me to a utility that will fix it?

Joey117225 said:
Mine doesn't even show up on my PC or ADB [Kindle Fire Utility]. What should I do? :c Point me to a utility that will fix it?
Click to expand...
Click to collapse
Even if your computer won't recognize the Kindle fire, it won't matter. The factory cable made by SKOPRN is specially made for your computer to recognize it, but it won't say that it has recognized it. By the way, there is no utility that will unbrick your fire, and trust me I have tried. The only thing that actually worked was buying a factory cable. It's only 12-13 dollars and if your fire ever gets bricked again, the cable will save the day. Almost always.

Pls try reinstalling the drivers.. I have attached the steps below: It should help
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen

kishorev said:
Pls try reinstalling the drivers.. I have attached the steps below: It should help
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
Click to expand...
Click to collapse
I did all that, besides I can't get past step 2 because it says ADB is offline. Even with the drivers installed it shows up on the computer. What am I doing wrong
EDIT: I got it to activate ADB but still won't go on fastboot or anything. Atleast I got somewhere but now what? It won't even start up lmao. Why did I ever have to install CM9 on my device without installing FireFireFire
EDIT again: LOL I just broke it even more now it doesn't get past the Kindle fire screen, now what? Atleast I have a reason to take it to best buy now, the last time I went I said it was a hardware issue, now I can say it won't get past the kindle fire screen. Maybe I can take it back there and see if they can do anything xD
EDIT again: Good news, it's broken enough to get a new one! So I'm gonna get a refund and see how this goes c;
EDIT: Fixxed it without returning. No worries

Joey11746 said:
I did all that, besides I can't get past step 2 because it says ADB is offline. Even with the drivers installed it shows up on the computer. What am I doing wrong
EDIT: I got it to activate ADB but still won't go on fastboot or anything. Atleast I got somewhere but now what? It won't even start up lmao. Why did I ever have to install CM9 on my device without installing FireFireFire
EDIT again: LOL I just broke it even more now it doesn't get past the Kindle fire screen, now what? Atleast I have a reason to take it to best buy now, the last time I went I said it was a hardware issue, now I can say it won't get past the kindle fire screen. Maybe I can take it back there and see if they can do anything xD
EDIT again: Good news, it's broken enough to get a new one! So I'm gonna get a refund and see how this goes c;
Click to expand...
Click to collapse
EDIT: Leave the new one stock.lol
EDIT again: Leave the new one stock.lol
Sent from my Amazon Kindle Fire using xda app-developers app

Joey11746 said:
I did all that, besides I can't get past step 2 because it says ADB is offline. Even with the drivers installed it shows up on the computer. What am I doing wrong
EDIT: I got it to activate ADB but still won't go on fastboot or anything. Atleast I got somewhere but now what? It won't even start up lmao. Why did I ever have to install CM9 on my device without installing FireFireFire
EDIT again: LOL I just broke it even more now it doesn't get past the Kindle fire screen, now what? Atleast I have a reason to take it to best buy now, the last time I went I said it was a hardware issue, now I can say it won't get past the kindle fire screen. Maybe I can take it back there and see if they can do anything xD
EDIT again: Good news, it's broken enough to get a new one! So I'm gonna get a refund and see how this goes c;
Click to expand...
Click to collapse
Just so you know, your device was never "broken". You just don't know what you're doing. But I agree with the previous post. Until you have a better idea of how the Kindle Fire works, leave it stock.
---------- Post added at 04:25 PM ---------- Previous post was at 04:19 PM ----------
[Edit:] And this constant practice of breaking one's own device and sending them back to Amazon despite knowing that it violates the terms of the warranty, is probably one of the biggest reasons Amazon locked down the new Kindle Fire HDs and probably every subsequent device moving forward.
The old saying, "You made your bed, now sleep in it", definitely applies here.

[Q] KF Gen 1 Boot Loop KFU

Hey guys, I've been lurking pretty hard the past couple days and can't find a thread that addresses my question, so here goes:
I have a 1st gen Kindle Fire that I don't sue and wanted to put a ROM on it. I grabbed KFU v0.9.6, used the install drivers bat, then I believe I ran permanent root with superuser and TWRP recovery install. This all worked, I used TWRP to create a backup, restored my kindle to factory, and then I put the latest Cyanogenmod rom on it and installed that. This is the point that I'm at now, where I can start my kindle and it boots, but I can't get into recovery mode (I didn't install FireFireFire because I didn't know what it was) and so it boots from the kindle logo to Cyanogenmod, where it hangs as long as I keep it powered on. I've tried reinstalling drivers and running KFU in hopes I can get adb shell to recognize it, and although it does say it's "Online", the boot status is unknown, so it isn't able to reboot it, and adb shell just doesn't recognize it, although adb devices does.
I hope that all made sense, let me know if I need to elaborate on anything or post any screen shots, as I'd be glad to, I just don't know what you need. I'm hoping I haven't bricked it, and that there's some way to get the kindle file system recognized or something, but I haven't been able to figure it out on my own.
Thanks for the help, and again feel free to ask for any sort of info/screenshots.
(Windows 7 x64, Kindle Fire 1st Gen, KFU v0.9.6)

Never Mind

Try KFUBU.
I believe that its not bricked. Try using Kindle Fire Unbrick utility. Pretty neat and easy to use..
I think you should have installed FireFireFire and used the latest KFU, though. Just an opinion.
Anyways, try out the Unbrick Utility. I can't post links here as I'm a new member!
Hit "Thanks" if I helped!

Yea, that's what I figured. I think I had a tutorial from when KFU didn't need firefirefire? I could be making that up. Anyway, thanks for the idea, I'll hopefully try that in the next hour, otherwise I'll be back in a week since I'm gonna be out of town.
Thanks!

[Q] Kindle Fire is not recognized by PC, even in TWRP

Okay, let's get this party started. I rooted my Gen1 Kindle Fire a few weeks ago and installed Cyanogenmod, CM11, I think. It worked pretty well. Kinda sluggish, but it's an old tablet so whatever. At one point or another, I had to turn the tablet off and restart it after a few days. And then it broke completely. Still not entirely sure why, but that's not why I'm here. Rebooted to Recovery, and the next five hours were filled with failed install attempts, factory resets, full wipes, and mounting. I stopped doing all of this and went to bed at about 1 AM, so it was all kind of a blur unless state-dependent memory kicks in tonight.
Flash forward to this morning, I get back to work on my Kindle Fire and find that, much to my dismay, I can't mount it. Not even in TWRP. I used to be able to, but now I can't. At first I thought it was the computer, so I went to another computer, and that one didn't work either. No biggie, I'll just use ADB to sideload an OS and then I'll be able to transfer files on there. I install the new OS and the Gapps, but it still won't connect. The next 12 hours at this point are spent googling and trying everything.
So now I'm here. I'd say it was because I damaged the USB port, or wasn't using the proper cord, but I've been using the same cord I always use, and every time I hook it up, it says it's installing drivers, but that installation eventually fails. When I go to Device Manager, The F drive under Portable Devices is usually missing, and the failed kindle driver is under Other Devices.
Now, I could just use ADB, but it's just kind of a pain and needlessly obtuse compared to simple drag and drop, and I'm a little worried at this point because, as previously stated, it won't even mount in TWRP.
If I weren't desperate, I wouldn't have made an account to beg and annoy you fine folks for help, but I've looked everywhere else and can't seem to find anything.
Thanks in advance.

Which bootloader? Have you tried Fastboot commands?
Sent from my XT862 using Tapatalk

sd_shadow said:
Which bootloader? Have you tried Fastboot commands?
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?

Imasargent said:
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?
Click to expand...
Click to collapse
Some people worked very hard to prepare guidance material for beginners like you. So you just have to allot your time and attention reading that.
I am sure this post might help you to deal with kindle drivers:
http://forum.xda-developers.com/showthread.php?p=23747671

Imasargent said:
Well, I believe I'm using FireFireFire, but what fastboot commands would I be looking for, exactly?
Click to expand...
Click to collapse
Fastboot devices
Fastboot reboot
Sent from my XT862 using Tapatalk