Ran "adb reboot bootloader and my kindle2 rebooted into fastboot mode, with the green and red light "stop light" on the screen. The Green light is blinking. The problem I am having is that my device comes up on my computer as Otter2-Prod-04 and I have no idea how to install fastboot drivers.
chris_m128 said:
Ran "adb reboot bootloader and my kindle2 rebooted into fastboot mode, with the green and red light "stop light" on the screen. The Green light is blinking. The problem I am having is that my device comes up on my computer as Otter2-Prod-04 and I have no idea how to install fastboot drivers.
Click to expand...
Click to collapse
Use KFAID and install the adb drivers that come with it.
If your device is showing up as stated... Fast boot drivers are installed.
What is your goal?
Sent from my Amazon Kindle Fire2 using Tapatalk 2
It comes up in device manager with a yellow triangle, I want to be able to utilize fast boot without a factory cable
Sent from my Amazon Kindle Fire2 using xda app-developers app
chris_m128 said:
It comes up in device manager with a yellow triangle, I want to be able to utilize fast boot without a factory cable
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
OK. Windows 7 or 8? What drivers have you tried?
Sent from my Amazon Kindle Fire2 using Tapatalk 2
mindmajick said:
OK. Windows 7 or 8? What drivers have you tried?
Sent from my Amazon Kindle Fire2 using Tapatalk 2
Click to expand...
Click to collapse
Windows 8, but i've been thinking of creating an ubuntu partition because it seems people have a lot less problems with adb and the sort with linux.
I've tried the kindle fire drivers from the sdk, and the kindle fire hd drivers that some people used to root their kindle 2. had no problem getting my kindle fire to show up with adb. I've tried editing a driver to add the hardware id's that come up with the driver.
chris_m128 said:
Windows 8, but i've been thinking of creating an ubuntu partition because it seems people have a lot less problems with adb and the sort with linux.
I've tried the kindle fire drivers from the sdk, and the kindle fire hd drivers that some people used to root their kindle 2. had no problem getting my kindle fire to show up with adb. I've tried editing a driver to add the hardware id's that come up with the driver.
Click to expand...
Click to collapse
Very strange as the adb driver and fast boot driver are one and the same..
I assume you turned off driver signing and installed them manually (if not, do so)
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
What's the issue?
You're in fastboot.
That's what you want, you're done.
If you THINK there is an error with your PC connecting to the KF2 in fastboot, then try stuff with ADB. You say you want fastboot but you already have fastboot enabled. There is nothing more you can do to.....get more....fastboot?
Now, if ADB is having issues, then you should post what kind of errors or issues you're having, and then hopefully we can help more. As of now though, it seems like you're already at where you want to be.
I've got the driver installed after turning off the signature checking thing.
I just thought I would be able to issue fastboot commands, whenever i try and do that I just end up with waiting for devices. Not a big deal , my device is working just fine so it's not like im stuck or anything. Just trying to further advance my android knowledge.
chris_m128 said:
I've got the driver installed after turning off the signature checking thing.
I just thought I would be able to issue fastboot commands, whenever i try and do that I just end up with waiting for devices. Not a big deal , my device is working just fine so it's not like im stuck or anything. Just trying to further advance my android knowledge.
Click to expand...
Click to collapse
What commands exactly? Can't help without info. AND what is the exact response?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
turns out i needed to add "0x1949" after fastboot in order for my commands to work lol
chris_m128 said:
turns out i needed to add "0x1949" after fastboot in order for my commands to work lol
Click to expand...
Click to collapse
That's why I asked. Glad you figured it out
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
chris_m128 said:
I've got the driver installed after turning off the signature checking thing.
I just thought I would be able to issue fastboot commands, whenever i try and do that I just end up with waiting for devices. Not a big deal , my device is working just fine so it's not like im stuck or anything. Just trying to further advance my android knowledge.
Click to expand...
Click to collapse
Hey man, can you help me? How did you install ADB driver? could you be more specific on this turn off signature checking? I'm using windows 7 and even I manually install driver and did everything that you did I still have the yellow triangle in device manager and cant be detected in adb that's why I can't sideload files.
melvsmeister said:
Hey man, can you help me? How did you install ADB driver? could you be more specific on this turn off signature checking? I'm using windows 7 and even I manually install driver and did everything that you did I still have the yellow triangle in device manager and cant be detected in adb that's why I can't sideload files.
Click to expand...
Click to collapse
you've probably already have them installed. in device manager, right click on the yellow triangle and click "update driver" when it asks you if you want to automatically search, choose "browse my computer for drivers", then click "choose from a list of installed drivers" scroll down the list till you see "kindle" click on kindle and the driver you want should be called "android composite adb interface" that's how i got mine to work
Related
Ok im posting in hopes to help someone else and myself.
DEVICE: 1st Gen Kindle Fire (D01400)
PROBLEM: Kindle quickly flashes stock logo then displays red screen.
I created this problem by using the wrong root tool (Qemuroot) [This tool is made for a Kindle Fire HD]
I bought a fastboot cable i hopes to use KFU/KUU to unbrick the device.
However Windows 8 only shows the device driver listed as Otter2-Prod-04 (Unknown Device) I proceeded to install the ADB drivers, even manualy assigned the device driver, and disabled driving signing and reinstalled drivers. (Drivers appear to install correctly however won't show up in connected adb devices.)
At this point im going to use SoupKit. I will post the outcome.
If you have had a similar problem or know of a fix which I have yet to research please let me know.
Thanks
Tested with Ubuntu linux using soupkit & firekit.
Both resulted in <Waiting for Android device> same in windows as well.
So I tried another computer also running windows 8, installed fresh SDK/Java/Drivers.
Once again had to force the driver to replace the unknown device "Otter2-Prod-04" now the device says its working in device manager yet nothing in ADB or fastboot.
I will add when I plug the device in using the fastboot cable it shows a red fastboot text and a stoplight green is flashing.
At this point im stuck and have reached the end of google. Yup thats right the very last page.
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
tmobile-repair said:
More hours put into this. I can issue fastboot commands. So this now turns into a question.
Is it possible to restore my kindle using fastboot?
Click to expand...
Click to collapse
You should be able to if you can push fff and recovery over and flash them via fastboot
Should enable you to have recovery back and work from there
Sent from my YP-G1 using Tapatalk 4 Beta
Well I killed my kindle.
Pushed the FFF via fast boot and now the device no longer powers on, no lights, no sign of life.
fastboot -i 0x1949 flash bootloader <name of firefirefire image here> which was u-boot
guess its time to cash in on my my rapid exchange at Best Buy
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
joshuabg said:
Or get a new battery
Sent from my Amazon Kindle Fire using xda app-developers app
Click to expand...
Click to collapse
New battery ? Can you explain never heard of this before. I was under the impression that I killed the bootloader.
I was just thinking that the battery may have died
Sent from my Amazon Kindle Fire using xda app-developers app
ah that better explains it.
Thanks
Hello all
I realize the one post below me is almost the exact same problem, but I am stuck. I just got my kindle hd 89 and I already have a red screen. Every option I try to use to get fastboot does not work, whether I'm using cmd and typing in the command, using KFFA, or KFHD 2.1. I think I ended up with a red screen by using FireFlash but without checking the right options. If it matters, I started with 8.4.6. I really want to unred-screen this, so any help would be appreciated! Thanks.
hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL
GermanJPL said:
hi beatmastermcfly,
I guess this will be a driver problem, for me win 7 64bit it works perfectly.
Have you ever tried KFHD_SRTv1.3-8.1.2 to start on another PC? Did you run it as an Admin?
You get a red screen when you try to SRT to enter fastboot?
mfg
JPL
Click to expand...
Click to collapse
I used KFHD_SRTv2.1- 8.1.4 and I am going to try KFHD_SRTv2.0- 8.1.3 , but the link to KFHD_SRTv1.3-8.1.2 in this thread appears to be dead. Anyone have a mirror?
And yes, the issue I'm having with KFFA, the SRT, and even when I am just trying to boot into fastboot via cmd, is that it says "waiting for device" and then when I plug it in it says "KindleFire" (in orange) for a second or two before switching over to the red screen.
I was able to do fastboot before the red screen showed up, so I doubt it has anything to do with drivers.
hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL
GermanJPL said:
hi beatmastermcfly,
I asked because I recently in a German Help - Forum have 3 different PC's tried it with a user (always bare OS with identical increments). Only after 1 week it has then eventually folded.
the Pc's have not accepted the Fastboot.exe for any reason.
mfg
GermanJPL
Click to expand...
Click to collapse
I do not understand what you are saying.
I will say that when I plug the Kindle in, my laptop makes the "device connected" noise followed quickly by the "device disconnected" noise and it even shows up in the device manager for the split second before it turns red.
What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
What exactly is the device that shows up in the device manager call itself before it disappears? And does it have a yellow triangle on it?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
At first it showed up under "portable devices" as an "unknown device" and I managed to uninstall the drivers in the hopes of re-installing them, and then the next time it showed up under "portable devices" as "jem-004..." etc. or whatever the code name for this type of kindle is. I think it just shows up as the category "other devices" now, but I do not have the kindle handy.
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Your drivers just saved my life dude. Thank you so much. Gotta figure out the next step now.
stunts513 said:
Depending on if it manages to stay connected long enough you might be able to install the drivers in my SIG, but I think windows cancels the driver install if it disconnects in mid install. If that's the case and running "fastboot -i 0x1949 getvar product" and then plugging the kindle in doesn't go into fastboot you may need to boot a ubuntu live CD and do this from a terminal since the drivers work differently on Linux, they load up immediately without you having g to install anything.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
oh but seriously dude running CM10.1 now and could not be happier thank you so much.
Your solution to fastboot and redscreen issue
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers
Hello I am very sorry to ask for help, I have this same problem and can help stunts513 beatmastermcfly, my kindle has a red screen and make everything after root, and the worst part is that my laptop recognizes it as unknown device which driver you downloaded work for you
:crying:
Dead Kindle Fire HD 8.9
Okay, due to my own errors while using fastboot on my KF, it no longer does *anything* when I try to turn it on. I can't reenter fastboot, since ADB no longer recognizes the device (which of course, it can't, since the device doesn't start). I mean, it does *nothing* (although the hardware is in great shape).
Am I, as I suspect, just dead in the water here? I have the recovery files, but without ADB or fastboot, I no longer have a way to load them.
Should I just start using the KF as a doorstop now? Or is there some obscure solution to this mess?
rogerlig
Someone correct me but figuring concludes that the red screen is because amazon blocks tablet when it comes to a stolen board or losses , my I get a tablet I did not say much , so that the repaired but through the serial number of a personal contact amazon and they said it was lost and I imagine blocked the operating system so I could not use the tablet
Please Help!
Meeperman said:
Hey beatmastermcfly,
I'm having the same issue you had with the red screen and fastboot not working.
Are you able to walk me through the solution you had with the the drivers that were recommended?
Did you end up using Ubuntu, or did you figure out how to do it in windows 7?
cheers
Click to expand...
Click to collapse
Did you ever find a solution? Thanks!
On a win7 x64 box you need adb (there is a quick version) installed. The kfhd drivers. USC disabled. AND MOST IMPORTANTLY YOU MUST RUN ADB FROM A COMMAND PROMPT ORIGINATED FROM THE ADB FOLDER. (shift+right click and select "run command prompt from here)
Did you ever get your kfhd 8.9" to work. Everything youve said so far is the exact replica of my kindle. I know its like 7 years later but this is still a problem for people
Juhpan said:
Did you ever get your kfhd 8.9" to work. Everything youve said so far is the exact replica of my kindle. I know its like 7 years later but this is still a problem for people
Click to expand...
Click to collapse
this is a COPY/PASTE of my own post. the files i specify are the exact names, just search this section of X-DA for them. SEE BELOW.
i had the same problem with the "red screen of death" as well. i found that if i installed the "Minimal ADB and Fastboot" and / OR (i did the minimal first.... ) KFHD_SRTv1.3.5 and RUN THE APP FIRST, then when it says "waiting for device" you then plug in the ALREADY OFF tablet it then WORKS!! says "fastboot mode" on the tablet. and it is listed in device manager also.
i got BOTH apps here at this board in this section.
WARNING: i run windows XP with all updates as of 10-31-2017 (pm me for info, 2 lines of text!! ) . NEWER windows versions have "permission issues". fixes are posted in multiple topics here in the Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2 section. READ THEM!!
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
z1326 said:
Unluckly i bricked my kindle fire hd 8.9.Now when i press the power button,after the yellow kindle fire logo flash,it will stuck on the red screen.And when i connect it to the PC,i got the red screen again.By the way,when the yellow kindle fire logo shows up, the PC could recognize the tablet but in less than 1 second the red screen will come out and the tablet will be disconnected from the PC as if the USB cable is pulled out.(i could hear the sound of disconnecting USB device.)
I also made a fastboot cable but it truned out to be invalid.Did i hard-brick the tablet? Is there any possibility to unbrick it? (I'm not a native speaker so sorry for my poor English)
Click to expand...
Click to collapse
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
These don't use fastboot. Use the regular USB and Has codes thread for 8.9" tablet for instructions to factory reset. Red screen on this is lack of bootloader.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Once the tablet is connected to the computer it will fall into red screen and become invisible to the computer in 1 second so the computer is not able to recognize the tablet.How can i install the necessary drivers?
BTW,you mentioned the instructions to factory reset,could you give me the link of the thread?
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I would suggest using a Ubuntu 13.10 live CD in your case since you never installed the fastboot driver previously. Makes things a lot simpler since you won't need to install drivers, only the fastboot command. Should be able to install it from the Ubuntu software center, just search for fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
I have opensuse installed in my PC but that doesn't work either. Connect the tablet with the computer and the red screen shows up then the connection breaks and the tablet become invisible to the PC,just the same situation as it is in windows.
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Yes but here's the thing, it's supposed to do that. You basically run in a terminal "fastboot -i 0x1945 getvar product" and after it says waiting for device you plug your kindle in while it's off. That way once its detected for a brief moment it sends the command and goes into full fledged fastboot. Never had an issue with it in Linux before, then again I have never red screened my kindle and mine's a 7" model so a fastboot cable would have worked on mine.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you for you reply.I'd like to know if I could use this method in opensuse?
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Should be able to as long as the kernel supports the device, anything modern should. I had native drivers in 10.04 of Ubuntu so it's safe to bet you have the kernel drivers. If you can't get it to work in suse, just try a live distro like I said, though I don't think there's a need to, but I have never tried suse before, I stick to Debian based distros.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I tried thay in suse but it didn't work.I think when the yellow kindle fire logo shows up the tablet is in fastboot mode but I'm just wondering why the tablet can't stay in fastboot after the screen truned into red.
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
So your suggestion would be
step1，Download a Ubuntu live CD image file，write the image into a usb disk，and reboot into the live CD.
step2，Open a terminal，input the fastboot command，then connect the tablet to the PC when the terminal says"waiting for device"
step3，Then the tablet should stay in fastboot and it is now possible to fix the bootloader and system with fastboot command.
Did I understand that correctly？
stunts513 said:
Because it's not supposed to... The 8.9" models don't work with a fastboot cable so instead they made it so it will briefly appear as a fastboot device when the boot loader initializes, and if a command gets passed to it while its briefly like this it gets told to go into full on fastboot mode. That red screen you're seeing is not it trying to go into fastboot, its just a messed up bootloader, but it should still be intact enough to reflash the bootloader to fix this. Weird to suggest this at this point but maybe try using an Ubuntu live CD and see what happens... I don't know why suse wouldn't work but maybe give it a shot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
And since my tablet is dead now， is it possible to install the fastboot driver in windows without the tablet？
It would be very difficult' unless you can get the driver into the driver cache but I haven't looked up how to do that, also on Ubuntu you will have to install the fastboot command, it should be in the Ubuntu software center, I'd give u the terminal command but I don't know the package name offhand.
Sent from my Amazon Kindle Fire HD using Tapatalk
Just out of curiosity have you tried KFFirstAide?
Sent from my KFTHWI using xda app-developers app
I'm stuck at a fastboot loading screen. None of the tool's I've used seem to work. I have tried KFU, KindleUnbrick, n2a's Root2Stock, nothing seems to work. I've tried accessing it via fastboot and adb both say that device not found or <waiting for device>. Now I have a jig that I've used with success with my samsung g3. However, how likely am I to make this problem worse... Any thoughts or tricks that I haven't found would be wonderful.
i attached a screen shot of what the device looks like:
sinisterrook said:
I'm stuck at a fastboot loading screen. None of the tool's I've used seem to work. I have tried KFU, KindleUnbrick, n2a's Root2Stock, nothing seems to work. I've tried accessing it via fastboot and adb both say that device not found or <waiting for device>. Now I have a jig that I've used with success with my samsung g3. However, how likely am I to make this problem worse... Any thoughts or tricks that I haven't found would be wonderful.
i attached a screen shot of what the device looks like:
Click to expand...
Click to collapse
Installed driver's from Kindle Fire Utility v0.9.9?
Sent from my XT912 using Tapatalk
Yes
sinisterrook said:
Yes
Click to expand...
Click to collapse
In Device manager>select unknown device or device with a yellow triangle>Update driver software>
browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
show all(uncheck show only compatible)>look for ADB interface or android phone
select yes to Ignore warning
may need to reboot both.
Sent from my XT912 using Tapatalk
Returns error code (10)
sinisterrook said:
Returns error code (10)
Click to expand...
Click to collapse
What does?
Sent from my XT907 using Tapatalk
sd_shadow said:
What does?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
upon assigning the driver it says that its non functioning with error code (10)
sinisterrook said:
upon assigning the driver it says that its non functioning with error code (10)
Click to expand...
Click to collapse
Try different pc
Sent from my XT907 using Tapatalk
I recently soft-bricked my KF2 while trying to install 2nd-bootloader on it (solid red screen). I just plugged it into my computer via a fastboot cable and it got to the fastboot screen perfectly fine. From here, I cannot access the device to recover it.
Any fastboot command gives me "Waiting for Device"
fastboot devices returns a blank line
It's listed in Device Manager as otter2-prod-4 and I can't seem to get any drivers working for it.
Does anyone know if there's anything I can do about this?
DoctorDelta said:
I recently soft-bricked my KF2 while trying to install 2nd-bootloader on it (solid red screen). I just plugged it into my computer via a fastboot cable and it got to the fastboot screen perfectly fine. From here, I cannot access the device to recover it.
Any fastboot command gives me "Waiting for Device"
fastboot devices returns a blank line
It's listed in Device Manager as otter2-prod-4 and I can't seem to get any drivers working for it.
Does anyone know if there's anything I can do about this?
Click to expand...
Click to collapse
Make sure you're using the -i 0x1949 parameter in your fastboot commands. If that isn't helping, we can continue with driver installation. Do let me know if you're using Windows 8+/10, as the driver installation process will require an extra step for those Windows versions.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Make sure you're using the -i 0x1949 parameter in your fastboot commands. If that isn't helping, we can continue with driver installation. Do let me know if you're using Windows 8+/10, as the driver installation process will require an extra step for those Windows versions.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I have same problem. But my pc do not recognize my kindle as otter2-prod-4.
Any Help?
bachmx said:
I have same problem. But my pc do not recognize my kindle as otter2-prod-4.
Any Help?
Click to expand...
Click to collapse
If you're using Windows 10, you need to disable driver signature enforcement in order to install the Kindle drivers. Here's a tutorial to do just that. After the reboot, install the drivers like normal and then reboot. After that, your kindle should be recognized.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you're using Windows 10, you need to disable driver signature enforcement in order to install the Kindle drivers. Here's a tutorial to do just that. After the reboot, install the drivers like normal and then reboot. After that, your kindle should be recognized.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
I did it. Then I installed drive download from here: http://forum.xda-developers.com/showthread.php?t=2544410.
But nothing work.
Please see attachments.