Related
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
So you have adb installed correctly and you're able to connect to the device USB and read it in your device manager.... correct?
Check under device manager for Kindle Fire. Click and check if it says android adb interface.
Sent from my KFHD7 using xda premium
Yes I believe that the ADB drivers are installed on my system. I tried the ones from the "kindle fire abd drivers", "USB_drivers" and the SDK package when following the Amazon guide. But when I connect my kindle to the PC it Auto installs and picks a driver which I found is labeled an MTP driver. The kindle is only list as "kindle" (in lower case) under portable devices in the device manager.
I have tried to update the driver and point the device manager to look at the Kindle fire ADB drivers, USB_drivers or point it to the drivers in the SDK folders.
I have also tried uninstalling the device each time, installing each drivers and reconnecting the device (i have also just uninstalled the device, left it connected and tried to install the drivers that way but no difference) - however it still installs the MTP driver which is automattically assigned. If the devices is connected with each driver and attempting the "ADB Devices" list in CMD prompt the list of devices is empty.
I am unable to access the security options in the kindle as it is a demo unit, if you touch more nothin happenes.
SO in short yes the drivers are on my system but I am unable to force the kindle to use them. I think this is probably to do with the fact that I cant access the security menu (I think ADB is disabled).
The only thing I can think of at the moment is to get a normal Kindle Fire, connect it and install the correct drivers- Unfortunatly I do not have access to another Kindle Fire to attempt this.
Just now The kindle fire stopped responding when booting up, with a pop up stating Demo mode has stopped responding - with options to wait or close demo mode. I choose close demo mode, but after struggling to boot it fired up in demo mode again.
Anyone know how to force a crash on a kindle fire - this may open access to the security menu.
Hello again - Just an update in case any of this is useful
if I follow this guide http://forum.xda-developers.com/showthread.php?t=1923010
with this page which is linked there www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
The unit still installs as an MTP device. The best luck I have had was running the Install_drivers.bat file from the KFU utility which gives me an unsigned driver pop-up warning. when completed the system says it installes the google, INC, (winUSB)androidUSBdeviceclass (12/06/2010 4.0.0000.00000). However in device manager its still listed under portable devices as a kindle using the MTP driver. If I attempt to update and point the unit to the SDK altered files (using above guide) or the KFU drivers, it is still the same.
I am ready to pull my hair out LOL. But I am still pretty sure that the problem lies with not being able to access the security menu on the kindle.
Hey all another update with a bit of progress but I am stuck
I followed this guide - http://forum.xda-developers.com/showthread.php?t=1830108
and managed to get the Kindle recognised as a Android device after I had installed the google USB drivers
I then updated the drivers in the same way (The only driver it would accept was the one from the Qmenu folders).
Now the device is recognised as a kindle fire - when the window is expanded it states its a Android ADB interface.
I tried the advice in this thread http://forum.xda-developers.com/showthread.php?t=1927710 Bujt I cannot get the device to be recognised as an android ADB composit device.
(still shows as offline or does not appear under the ADB devices command, even though shown in device manager)
When updating the drivers as described in the guide, when I pick let me pick from list of device drivers I do have a "%compositADBinterface%, but no matter what I try once installed the device still reads as a kindle fire => Android ADB Interface. If I attempt the process again the "%compositADBinterface%" is still there.
Any ideas people?
I'm curious as to how you ended up with a demo version.
Open cmd... navigate to sdk\platform-tools\
type adb devices
Does it list a serial number?
Under Device Manager in windows, you should see it listed as Kindle Fire. When you expand that, it should show "Android ADB Interface"
If you see that then adb is installed. You may not be able to do anything without a factory cable. These guys on here should be able help you install a non-demo version on to your device.
Good luck!
Sent from my KFHD7 using xda premium
Hello again - thanks for the reply.
My friend worked in one of the stores that was recently a victim of the recession. I asked him how much they were selling the ex-demo stuff, the same evening he dropped by and handed it to me - He says his manager said he could take it .
Yes in Device Manager now the device is seen as a Kindle Fire and when expanded it states its an Android ADB Interface. I am a noob but from what Ive read so far this means the driver isnt correctly installed. As it should read "android ADB composit device"
Using the ADB devices command , it is blank under the list of devices.
Not sure if this helps, but if I right click the kindle in my computer and look at the properties, I can view the serial number there.
Looking into the factory cable options now
Again thanks for the help
stirky said:
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
Click to expand...
Click to collapse
stirky,
First, let me apologize for the delay in getting to your issue, we have been working on a new package for the Kindle
which can be viewed here: http://forum.xda-developers.com/showthread.php?t=2096888
Let us know what you think. Now to your problem. We have worked with the demo Kindles, they have security software
to eliminate program installation, even if you allow or turn on "Allow Installation of Programs". I do not understand how
someone what able to breakthrough the block since it is done at the OS Level. Maybe they hacked the Kernel? Anyways,
the task is not easy. What I would do is Fast a new system.img, boot.img and recovery.img using this software:
http://forum.xda-developers.com/showthread.php?t=2096888
If we need to flash the Kernel I will add that functionality too. What this will do is completely remove the Demo and
control/security software and turn the demo Kindle into a regular Kindle. We can ship the required Factory USB Cable
tomorrow. Read the post and send us a PM.
No worries about the delay in getting back to me! I was quite proud I finanlly managed to get it recognised on my system after trail and error.
First Question - I am now assuming that anything I need to do to this unit requires a Factory Cable? Am I correct?
. Now a note - Not sure if this helps. While playing around I did notice this little quirk.
After I had edited the google USB driver as mentioned in the above post, My system first recognised the device as an Adroid ADB interface under abndroid device. While checking back though my edit I noticed that I mistyped Composite. Rectified this and then re-installed as before. Now the devices is rocognised under Andoid Device as an Android ADB Composite interface. I then proceeded to up date the drivers agains from the Qmenu Drivers Folder. This makes the system list the device as a Kindle Fire and under this is states its now just an android ADB Interface.
I then had a brainwave and made an edit of this file and inserted the same edit as the google USB driver. This all installs fine. But still only recognised as an android ADB Interface under Kindle fire.
Does is have to be recognised as a composite device? or is a Andoird ADB Interface suffcient?
I assume I need a factory cable and will get one ASAP if thats the case.
Root and Google Play for Amazon 7" Kindle Fire HD Demo
stirky said:
No worries about the delay in getting back to me! I was quite proud I finanlly managed to get it recognised on my system after trail and error.
First Question - I am now assuming that anything I need to do to this unit requires a Factory Cable? Am I correct?
. Now a note - Not sure if this helps. While playing around I did notice this little quirk.
After I had edited the google USB driver as mentioned in the above post, My system first recognised the device as an Adroid ADB interface under abndroid device. While checking back though my edit I noticed that I mistyped Composite. Rectified this and then re-installed as before. Now the devices is rocognised under Andoid Device as an Android ADB Composite interface. I then proceeded to up date the drivers agains from the Qmenu Drivers Folder. This makes the system list the device as a Kindle Fire and under this is states its now just an android ADB Interface.
I then had a brainwave and made an edit of this file and inserted the same edit as the google USB driver. This all installs fine. But still only recognised as an android ADB Interface under Kindle fire.
Does is have to be recognised as a composite device? or is a Andoird ADB Interface suffcient?
I assume I need a factory cable and will get one ASAP if thats the case.
Click to expand...
Click to collapse
stirky,
That is perfect Android ADB Interface is sufficient.
Yes, you will need a Factory USB Cable. we do sell them and we are shipping a bunch tomorrow. I would ship it
to you Priority at no additional charge, just PM me your name, address, city, state, zip, phone and email.
You would get the cable in about 3 days. We sell the cables at our direct cost to all XDA Developer Members.
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
wukster said:
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Click to expand...
Click to collapse
wukster,
The Kindle Fire 8.9" does not need the Factory USB Cable, just use Option 10 in the interface. There is a known Bug in the Kindle Fire 8.9" Bootloader, if you get stuck in Fastboot, let us know, we have the fix.
Please wait until we do some updates on the software and then download it anytime after Monday 8:00am - we are doing critical updates for Kindle Fire 8.9" models.
---------- Post added at 01:09 AM ---------- Previous post was at 01:07 AM ----------
KindleFireGuy said:
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
KindleFireGuy,
Thank you for the support, for new users here is a link to the Kindle Fire First Aide software:
http://forum.xda-developers.com/showthread.php?t=2096888
Hi I dont want to hijack your thread or anything but i was wondering if you could possibly help me root my demo unit as well. This one is actually from my store but we dont keep the demos on display and would like to have it for personal use when its just 1 person in the store. (we are located in a mall so we often have just one person in the morning). I would really appreciate it if you could maybe walk me through the steps to get it recognized on adb. I have a KFHD 7". Any help or advice would be greatly appreciated.
Edit: Got it to read as "Android Composite ADB Interface" which I believe was the first step to making it work. I need a Factory Cable which from what I understand requires rewiring the B side (or the Micro USB side) of the cable so that the wire is connected to both Pin 4 and Pin 1. If so then I made a make shift one at work today and just need to solder it. Please advise if I have done anything incorrectly. I would also be interested in purchasing a factory cable from you, Prokennexusa, just in case I need it in the future or if I mess up on making mine.
Demo Kindle - Please Help
Hi
Please excuse ,my ignorance but I am struggling to get my kindle fire to work with the software I downloaded. I followed every step in the instructions and all seemed to be going well until I actually attempted to do anything with it.
I got the demo kindle from a shop clearance but cannot get the demo mode removed. I have a factory cable and the kindle goes into 'fastboot' mode with the cable but doesn't seem to behave any differently after the software states it is complete.
I have included some screen dumps of the messages I received, I apologise if I am just being dumb but I am lost?
I would be quite happy to just have a working kindle...I don't need android on it if this makes it more difficult......please help
Thanks in advance
Below is the message I received when I tried option 9 Display Fastboot status
************************************************
* OK Here We Go, We Are Beginning The Process! *
************************************************
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
*********************************
*Looks Like Fastboot is Enabled *
*********************************
Press any key to continue . . .
This when I tried option 12 Install Amazon ADB Driver
************************************************
* OK Here We Go, We Are Beginning The Process! *
* Please Make Sure The Kindle Is Disconnected *
* From USB During The Driver Installation. *
************************************************
Press any key to continue . . .
****************************************
*The Kindle ADB Driver Will Now Launch *
*Please Make Sure You Are Running This *
*Software As An Administrator Otherwise*
* This Process May Fail! *
****************************************
The system cannot find the path specified.
******************************************
*The Driver Install Was A Success! Please*
* Plug The Kindle Into USB Using The *
* Original USB Cable That Was Included *
* With The Kindle. This Is The Same USB *
* Cable You Use To Charge The Kindle *
******************************************
Press any key to continue . . .
stirky said:
Hey
I spent all night reading . . . . well pretty much every page on this forum. I am stuck - I am sure that if I had a normal Kindle Fire it would be rooted by now. I found the tutorial really easy to follow.
This demo unit automatically fires up in demo mode every time. A few notes that may help before I get into what I done. When using the swipe down menu, I only have a couple of options and cant get the the security settings (Im sure at this moment that ADB connectivity is disabled). I am unable to check which software this unit is running. If I try to get into the more option nothing happens, if you try to turn of parental controls the unit stated "this feature isnt availble in demostration mode". When connected in via USB - unit states its connected as media device, is listed as kindle under portable devices in device managers, and in my computer shows as a portable media player, with no contents if clicked on. If you check in the properties your can see a firmware version and a serial number but thats it.
This model has a Demo screen saver which kicks in if the unit is left idle for a few minutes, when it does is disconnects from th system then reconnects and is recognised again. If trying all this and ensuring the screensaver doesnt start still have no effect.
following this thread - http://forum.xda-developers.com/showthread.php?t=2069117
I have completed the windows 7 bug fix as here - http://forum.xda-developers.com/showthread.php?p=36373627
and attempting to install the kindle fire abd drivers or the USB_drivers the PC always states that I am currently using the correct drivers and the kindle is listed as "kindle" under portable devices.
I have also tried with the SDK package with the notes here - https://developer.amazon.com/sdk/fire/connect-adb.html
I have completed the actions in this videos also - http://www.youtube.com/watch?v=Khrxo0-NieM&feature=youtu.be
I have uninstalled the devices from my system numerours times but not matter which driver I try to install / force an update with. My system states that I am using the most upto date driver (MTP USB Device). I can uninstall the device from the system but I cant find any option to delete the drivers it auto assigns (wpdMTPdr.dll, winusb.sys, wudfrd.sys, wpdmtp.dll, wpdwtpus.dll). I would delted them manually but thought I would post here first - incase firther problems could arise.
Can anyone help with this issue, someone in this thread - http://forum.xda-developers.com/showthread.php?t=1828335&page=2
said they managed to do it, but didnt supply any info. I believe I have a driver and/or ADB connectivty issue.
At the moment I would just like to revert this Demo to a normal rooted kindle fire with the google play mod. If this isnt possible I would still like to root the device and just put an OS on there (jellybean seems to be the one of choice).
Thanks for reading this - and I look forward to the replies.
PS - The simple nood guide is by far the most informative and easy to follow guide that I have come accross. Had no problemn following the steps etc - like i said at the begging if this wasnt a demo model I am sure it would have been rooted by now. BIG BIG props to you guys especailly after seeing the lenght you go to helping people who didnt understand the guide! keep up the awesome work
Click to expand...
Click to collapse
stirky said:
Hey
This is My first post and im allittle nervous so......
My girlfriend was cheated out of some money when she bought a Fire Hd 8.9 from some girl. it turned out to be the Demo version.
I was able to remove the demo by going to the app store, it asked to set up wifi so i did that, loading file manager then going online downloading 1market app apk. they asked for permission to allow non market apk to be installed so i granted that.
then i went to amazon downloaded newest version of fire 8.9 placed it on update folder from my file manager.
then i downloaded adw launcher apk from 1market store.
This launcher allowed me to access device from settings and from there i updated my kindle fire. it removed the demo version and now running latest version and no demo.
I did all this after rooting the device but i see no way that this method wont work on non rooted devices.
Only difference is that there is no lock screen on the kindle. but besides that works great......
This answering questions thing is hard please dont ever make me do this again....
Click to expand...
Click to collapse
Root or reload KFHD 8.9
wukster said:
great thread... I just picked up the KF HD 8.9 demo unit myself... I have yet to install the SDK, but please let us know of any developments...
thanks...
Click to expand...
Click to collapse
Were you able to root or reload the DEMO unit to a regular tablet?
I have just purchased an 8.9 unit myself and have not seen anyplace for sure if these units can be reworked since ADB is not enabled.
Regards Jery
KindleFireGuy said:
Obtain a factory cable. Fastboot flash the system.img,recovery.img and boot.img. Then give me results. Use kindle fire first aid program.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
I have a kindle hd 8.9 demo, I do not know if this tool will help
lkmgfy said:
I have a kindle hd 8.9 demo, I do not know if this tool will help
Click to expand...
Click to collapse
I was able to get the demo 8.9 loaded with the regular Kindle software but, with a slightly different method.
I used Soupmagnet's restore image LINUX script that flashes a pre-rooted 8.9 Kindle version 8.1.4 image to the kindle using fastboot.
http://www.adrive.com/public/xvZeWC/KFHD8.9.restore.zip
While the rest of the demo unit is shut down, fastboot will work if the script is executed prior to plugging in the tablet.
The script will set waiting to see fastboot (waiting for device).
When the tablet is booted up, it passes briefly thorough a fastboot cycle and the script will catch it and keep the tablet in fastboot (pretty much as the KF 1 does). The script then loaded version 8.4.1 and success. You can then download the latest Kindle OS and loose root and be back to a stock configuration or continue and push 2nd bootloader, twrp,etc. and or new ROM.
Success of course depends on having the USB and ADB drivers loaded on LINUX (Using Soupmagnet's soupkit will do that for you).
You will have to try the soupkit again package and see if it will work for you. This package is intended for all kindles I believe.
I had all the drivers loaded using the first soupkit package and the drivers worked to see and communicate with the 8.9 tablet.
Original Soupkit:
http://forum.xda-developers.com/showthread.php?t=1850038
New "Soupkit Again"
http://forum.xda-developers.com/showthread.php?t=2162986
However, I installed the new "Soupkit Again" package over the first Soupkit package and while the drivers still work, I lost all access to the Soupkit utility itself (which is not used to restore the 8.1.4 image to the Kindle 8.9). A little off topic, but, I would like to know how to get my Soupkit utility back working. (The soupkit.sh script is missing after installing the new "Soupkit Again" over the original Soupkit).
Well my problem its different that the ones I've looked over the forum.
I get the cyanogenmod installed , and then I wait for almost 45 mins, with the cyanogenmod logo.
Then it suddenly comes with the new android unlock screen for like 1 second and then it begins again with the cyanogenmod.
But to resolve it, I just turn off the kindle go to teamwin boot and then just restore.
Then it becomes like factory settings..
But I can't get the cyanogenmod to work no matter what.
What I'm missing...
Did u check the cm 10.1 zip files md5 checksum before flashing it? You should always do this, you can do it in es file explorer by going to a files properties and calculating the md5. Compare it to the md5 from the post where u got it from, if its different then re-download it..
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
seekario said:
Well I downloaded everything from this post.
http://forum.xda-developers.com/showthread.php?t=2245335
and followed the instructions...
I don't really know what's the "md5 checksum"
I only rooted and did the 2nd-bootloader + TWRP 2.6.0.0 for the Kindle Fire HD 7
from this tutorial:
http://forum.xda-developers.com/showthread.php?t=2271909
But I don't recall seeing anything related with "md5 checksum"
Click to expand...
Click to collapse
Try downloading again, make sure file size is the same as the website says and md5 is the numbers in the description, just above the file or below, also try (make backup first) wipe cache, dalvik cache, data,system, flash rom , flash gapps, wipe internal, wipe dalvik, then reboot
stolen from my drunk kindle by Tapatalk 4
Well looks like I erased everything and it says I don't have a OS installed, but now the cyanogenmod zip its not in the sd card of the kindle.
So I have nothing to flash with, and it won't go to the locked screen.
But I'm stuck with the Team Win recovery project menu .
So its there anything I could do to copy the zip from my pc to the kindle so I can flash it, or even restore it so I can connect my kindle to my pc?
Thanks!
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Well Im going to look more info about that adb sideload.
Thanks!
stunts513 said:
Your going to have to plug it into your PC and use adb sideload to put the zip file on it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Guys so sorry to bother u guys again , idk why I have such a big problem following instructions today...
I have flash my android phones before, I tho this was gonna be just like it...
But I was following this thread and nothing so far..
http://forum.xda-developers.com/showthread.php?p=37594973
if u guys got anything I could use.
Thanks!
Eh well I was hoping for more specifics, but I will tell you what I can, because I haven't ever had to use adb sideload. First go into twrp and hit advanced, them hit adb sideload and swipe to start. If your device manager doesn't have the drivers installed for your kindle when its in twrp for adb, you will need to install them, if you have installed adb drivers before and are running the latest twrp version for kindle(2.6.0.0 I believe), then it should be pretty much plug and play, but if you are running an older version of twrp you will need to force install the adb driver for that device because it didn't have the same vendor ID as the kindle like the new twrp has. Usually I think u just have hit update driver and tell it to let u browse for the driver manually, then uncheck only show compatible device drivers( it says something relatively similar to this) and look for the adb driver, can't remember if its the adb composite device or a different one. If all goes well and u haven't got driver issues, which I hope you don't because I think my tut was a bit lacking for installing drivers, then u should goto a command prompt and CD into the directory u have adb in, it would be in the android SDK, or a utility like kffa, anything that comes with adb will do. Make sure to put the zip u are side loading in the same directory as adb.exe. after that just type adb.exe sideload zipfilename.zip. that should put it on your kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well I tried that a few times already the adb sideload.
and i just loads, and does nothing, I even waited for an hour, and wouldn't finish :S
So I just think the adb sideload its not gonna do it :S
Just in case u didn't understand whats my problems.
It won't boot up because it has no OS.
So I can't put anything in the sd or backup because I accidently erased everything... even the zip from my sd(cyanogenmod )
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
I will have to test out adb sideload on my PC to get a better understanding of whats going on, keep in kind I use Linux and not windows, so I don't have driver issues, though I guess you are past any issues that would occur with drivers. Just to validate while I check, but u did put the file u want to side load in the same folder as the adb.exe and you are sure u ran the command correctly? Just thought I'd mention windows doesn't show file extension by default, so make sure u add the .zip to the filename if you didn't already when u type the command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
seekario said:
Thanks for the fast response
So I'm guessing I'd have to put the" cm 10.1 in the same folder as the adb tools(where are 2 .exe fastboot and adb) just to make sure we are talking about the same thing lol.
But I think I did the command wrong.
because I got to the part of the cmd and running the adb, but then I get nothing when I try to push the file to the sd.
Just to make sure can u put the command again
this its the name of the .zip : cm-10.1-20130725-NIGHTLY-otter2
and this its where its located : C:\Users\seekario\Desktop\ADB-Tools
Thanks so much for your time also!
Click to expand...
Click to collapse
OK so type this: adb.exe sideload cm-10.1-20130725-NIGHTLY-otter2.zip
That command should work, just to make sure I'll mention it again, before u run the command, in twrp goto advanced, adb sideload, and swipe the thing to the left, afterwards run this command.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
So I put the command and now it says
*cannot read 'sideload' *
any ideas ? thanks!
south956 said:
Just download kindle fire first aide and run option to restore into stock 7.2.3 and there should be good as new( fast boot required )
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I tried that first, and to reboot into fastboot I have to be in the menu, but I have no OS so I can't load anything, it just stays in the kindle fire logo.
I can only access to the Team Win recovery project menu(TWR v2.6) :S
Thanks anyways!
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
south956 said:
Do you have fastboot cable?
stolen from my drunk kindle by Tapatalk 4
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Whoa whoa whoa whoa whoa, our device is under Tate not otter2, otter2 is for original kindle fire and not the HD which explains why your stuck in bootloop, find the cm10.1 in Hash codes forum and download that one
stolen from my drunk kindle by Tapatalk 4
Click to expand...
Click to collapse
I wish I had, I only have the original cable from amazon :S
I doubt anything can be done til you have fastboot cable, I heard people try adding certain lines in cmd but most say it doesn't work, so a sure fire way would be to either make or buy fastboot cable.
stolen from my drunk kindle by Tapatalk 4
I have buyed beginning frebruary a kindle fire hd 7 from amazon and rooted it, works very fine.
Now kindle makes update to 7.4.6 and the kindke is unrootet.
I thought, okay it´s must be easy to unrootet at again, but after 24 hours of frustrating, i need your help.
I´m mac user, i have dropbox with windows 32 bit, windiws 64 bit, adb driver doesn´t work here, i used over 10 times ago, no drivers works currently.
On the windows 7 64bit laptop, i have installed and uninstalled the drivers 20x times ago and every time i insert usb cable, the kindle works fine on windows, the device manager shows as kindle also i can use explorer to copy or move files from the intern sd card.
But if i activate ADB modus, the kindle is again under the device manager as kindle.
Root_with_Restore_by_Bin4ry_v33 doesn´t work, bat said every time demon load on port blabla but there is NOTHING after this message, nothing on the bat file or on the kindle, kindle doesn´t open a backup & restore screen.
The windows laptop said it´s PID 0007 (why??).
Every installation of the driver again (from this topic) said propertly not currelty installed, what is wrong?
Sorry for probably posting something that's very common. Everything I try doesn't seem to work and I don't know what to do. I have 2 7" Kindle Fire HD's that I have previously rooted(quite some time ago). My PC HDD crashed and burned recently and I was attempting to sideload some stuff on to them, and I can't seem to figure out how I was able to get the ADB Drivers to install correctly when I first rooted these. ANy help would be greatly appreciated...
Wrong Forum
I've requested that this thread be moved to 7" Kindle Fire HD Q&A, Help & Troubleshooting
The Kindle Fire HD 7 First Aide Tool has drivers,
but you should also see Windows Device Drivers and the Device Manager
note: written for original kindle but steps are similar
install drivers with First Aide, reboot pc, connect Kindle, update drivers in Device manager.
if that doesn't work, when updating drivers select drivers folder from First aide files, may need to uninstall old drivers, and reboot pc to get it to work.
Ok, thanks. Sorry about posting in the wrong forum. I'll take a look at the links provided. :fingers-crossed:
sd_shadow said:
Wrong Forum
I've requested that this thread be moved to 7" Kindle Fire HD Q&A, Help & Troubleshooting
The Kindle Fire HD 7 First Aide Tool has drivers,
but you should also see Windows Device Drivers and the Device Manager
note: written for original kindle but steps are similar
install drivers with First Aide, reboot pc, connect Kindle, update drivers in Device manager.
if that doesn't work, when updating drivers select drivers folder from First aide files, may need to uninstall old drivers, and reboot pc to get it to work.
Click to expand...
Click to collapse
you can use the ones in my signature, if on windows 8 you will need to disable driver signature enforcement first.
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
GogoplataMMA said:
I've tried a bunch of tutorials on here to fix this, but can't figure it out.
I was on my Kindle HD 8.9" running CyanogenMod 10.1, which it has for a year. Suddenly, I got some popup last night. It said there was a nightly build update in my notifications area, so I just clicked "OK" and let it do its thing. It installed for a little bit, all was okay... but now I cannot access my Android OS.
I went to turn my Kindle on after the update, but it keeps going to TWRP. What will happen exactly is it starts... orange letters... then blue letters... then restarts again to orange letters... then blue letters... then TWRP. Why does it keep going to TWRP? How do I fix this?
My Kindle can't even connect to the PC. I just either get "Unknown Device" or "Kindle" in my Device Manager, and mounting from TWRP does nothing.
Then I try installing the Android SDK to get the ADB on my machine, and I added the "Path" in my environment to the two tools folders, but nothing... same thing happens. Constant loop into TWRP. Driving me nuts.
The update it wanted me to install when I could still get into the Android OS was cm-11-20140420-NIGHTLY-jem. I thought maybe trying to connect my Kindle to my PC in order to open the drive, then pasting the cm-11-20140420-NIGHTLY-jem into a folder and installing again from TWRP would solve my problem, but I can't even get that far.
I'm at a loss. Please help.
Click to expand...
Click to collapse
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
stunts513 said:
boot into twrp, check what version of twrp you have. Then you may need to update your twrp to be cm 11 compatible if its not at latest version, current version is like 2.7.0.0(least it is for the 7", havnet check to see if that builds out for 8.9 as well), anyways check the device manager for a device with a yellow triangle next it, if you don't see that and you do have a adb interface showing up but adb doesnt detect it then uninstall the adb device and mtp device and search for devices, if it still doesnt work look for a component device with a vid of 1949 in the properties>details>hardware id's section, if you find it then remove it and scan for device. Windows is a pain in terms of drivers for the kindle in different modes. Once adb is working its as simple as pushing the rom with adb push. You may need to factory reset and/or wipe internal storage so i recommend backing up the data, i would assume the current bootloop has something to do with either no factory reset before going to cm 11 or selinux issues, but that would mean the kernel didnt flash in the ota which would be weird.
Click to expand...
Click to collapse
Now I'm all screwed up. Before I saw this message, I restored my Kindle back to when it was still running the factory default OS with root, then I shut it down to enter TWRP, and it appeared on its own, but it was installing some sort of update... and when the Kindle's factory default OS appeared, my root was gone. Now I am stuck on the factory default Kindle HD 8.9" on System Version 8.4.8. Man, I should have never accepted that update and just left it as it was. Ugh. Well, for right now, there's an entry in my Device Manager that says "Kindle Fire" and when you click the arrow to bring down the submenu, it says "Android ADB Interface." The Kindle is now working when connected through USB. Now... how do I go about rooting this thing and getting TWRP on it again, because it seems the entire thing got erased. Not having my ROM installed on this thing makes it mostly useless to me.
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Root with kffa or binary's root, think the newest version has different choices than the tutorial, use the old normal method. Last I checked it worked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I can't find anything. Download links are dead for KFFA. You have a link to get it through another source?
They are up and running when I click em. You were on this thread right?: http://forum.xda-developers.com/showthread.php?t=2096888
If that doesn't work you can always use binary's root.
http://forum.xda-developers.com/showthread.php?t=1886460
Use the old normal method if I remember correctly.
Sent from my Amazon Kindle Fire HD using Tapatalk
Nah, the link is dead here. Says the file was removed. There are other members in the forum asking as well for a new link.
I managed to get ADB working, and in Device Manager, I have "Android Device -> Android Composite ADB Interface."
I open CMD and type "ADB" and it scrolls a bunch of stuff, but when I type "ADB Devices" I get a list with nothing there. It's just blank.
I tried using BIN4RY Revision 33, using Option #1, but it just keeps bringing me to a "Path not Found" error of some sort.
It looks like all I need to manage to do now is get ADB to list my Kindle device before attempting the ROOT, but how can I do that?
I still wanna give KFFA a try, but no downloads anywhere, and I don't trust random 4Share and the likes, not that it's gonna fix my problem.
I'm close... I just need this damn ADB to list my Kindle device and I think I'll be okay.
Also, I want to say thanks for the help you've given me so far. It's greatly appreciated. :highfive:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb kill-server
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
i.imgur.com/gZrrqXm.jpg
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
No problem, i like helping people fix things.
Try uninstalling the device and letting it search for new hardware. This is more than likely a driver issue.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
GogoplataMMA said:
Oh, believe me. I tried that like 50 times. I think I'm just gonna make a virtual machine of Win7, completely clean install without all my drivers everywhere, and try my luck there.
Click to expand...
Click to collapse
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
From the administrator profile on your PC open a command prompt and type Bcdedit.exe -set TESTSIGNING ON then hit enter. Now restart your computer. This will disable Windows driver security enforcement. Then try to install the drivers in the device manager.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately, that didn't work. I'm pretty sure one or more of my drivers are interfering with the connection to the Kindle, but this is such an old OS with so many drivers, it's hard to tell.
Right now, I have a Virtual Machine of Windows 7 up. I plugged my Kindle in and I can instantly see it. I can even enter the internal storage! I'm currently installing the Android SDK for the ADB after installing the Java SE x86 version. Once I get ADB on it, I'll see if it lists my device now. Seems promising since the VM sees and allows me to already enter the internal storage, unlike my original Win7 OS.
EDIT #1: Great news! ADB now lists my device! Thing is... Root with Bin4ry Revision 33 does not seem to want to work. This is what I get...
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (14.12.2013) v33 =
======================================================================
Device type:
0) Xperia Root by cubeundcube
1) New Standard-Root (thx Ariel Berkman)
2) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
3) Old
4) Old-Special (for example: Sony Tablet S, Medion Lifetab)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Please connect Device with enabled USB-Debugging to your Computer
The system cannot find the path specified.
Doing a Backup first, please confirm this on your device!
The system cannot find the path specified.
Done!
Press any key to continue . . .
Click to expand...
Click to collapse
It doesn't give me a chance to do anything. All of that pops up as soon as I press enter. ADB and third party software is enabled on my Kindle. ADB even reads my device as:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
B0C9110232560198 device
Click to expand...
Click to collapse
I'm at a loss now. Any ideas?
EDIT #2: Success! The issue was I was using Root with Bin4ry Revision 33. I should have been using Root with Bin4ry Revision 30. That worked, and I am now ROOT. Mission accomplished. Now the next part of my mission... figuring out how to get TWRP on this thing.
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
Everything seemed to work until I get to Step 3. I'll enter the commands but it tells me that there is no such directory or something. Something about there not being any "stack." Can't recall. I wanted to ask on the thread there but the site isn't allowing me to post there.
adb push stack /sdcard/ is where the issue occurs. Everything else worked.
I'm at a loss, and the comments don't seem to help on that thread. Please tell me there is an easier method of getting TWRP on this thing.
ERROR:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push stack /sdcard
/
cannot stat 'stack': No such file or directory
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
GogoplataMMA said:
Well, trying to install TWRP is going very wrong. I'm using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2128175
ERROR:
Click to expand...
Click to collapse
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
LinearEquation said:
That tutorial is for the 8.9. You want the tutorial for the 7". http://forum.xda-developers.com/showthread.php?t=2218796
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
He's on a 8.9", he just posted in the wrong section. Use the fireflash method from seokhuns tutorial, just don't forget to check the box with red text near it or you will get a nice redscreen brick. Lemme grab a link
Edit: link grabbed! http://forum.xda-developers.com/showthread.php?t=2277105
I used FireFlash, followed the instruction... now I cannot get passed the first "Kindle Fire" logo when I turn the Kindle on. It just freezes at "Kindle Fire" as soon as I turn it on. I can't seem to do anything at all, and it won't connect via USB. Any ideas?
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You missed a check box somewhere. If it is indeed a 8.9" kindle this should be fairly easy to fix. Open the device manager and plug the kindle in while it is off, it should briefly appear as a jem device. While it briefly shows up you need to right click it and hit update drivers and navigate to where you would have downloaded and extracted the drivers in my signature, once you manage to install them you just need to run a "fastboot -i 0x1949 getvar product" with the kindle unplugged and off, and then plug it in once it says waiting for device. It should then go into fastboot mode where you can restore from kffa or SRT.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
It's not working... it won't read at all. Device Manager doesn't see the Kindle at all. And yes it is 8.9". I think it may be bricked now. ;'(
And all because of that stupid update... ughhhh. Sucks!
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You should try the command from a Ubuntu live CD/USB if is a lot easier to do from there, if it won't work from there then I would be convinced something may be wrong with the bootloader, but I don't see the bootloader as the problem because if anything it would have just been downgraded and I'm more inclined to thinking the bootimg is corrupted. That can cause odd behavior with the bootloader. Are you positive this is the 8.9" model and not the 7" model?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I switched over to my main Windows 7 OS and did what you said. I connected it and it showed for a brief moment in Device Manager, so I quickly loaded the driver and updated. But wen I type the command you gave me, it says <waiting for device>, so I plug it back in and... nothing. At all. Just sits there at <waiting for device>
I'd try Linux, I have several copies of different OS's, but I'm not very good at working with it or using Terminal... I can try that though, but no clue how I'd get ADB or the Kindle to read on it. :\
And yes, 100% it's the 8.9". The resolution is 1200p.
OK the command has to be run while the device is off and disconnected, once it says waiting for device, plug the kindle in and it should work if the drivers are working. Linux is really easy to use with a kindle, it has the fastboot and adb drivers built in natively, only thing you need is the fastboot command from the Ubuntu repos if you are using Ubuntu, believe they were added to the repo in 13.10.
Sent from my Amazon Kindle Fire HD using Tapatalk