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).
Hi all,
I'm new here, and I've been trying for the past few hours to root my Kindle Fire HD 7" so I can install a CM10.1 ROM and turn it into a google tablet. I've been searching the web for information, and I kept getting directed here so I decided I might as well join.
Anyway it seems the one method that works is the Bin4ry one, and I started following the instructions given on this site and others. However when I installed the driver, it said the installation was successful but when I clicked "Finish" a window popped up and told me the driver didn't install properly. Then I tried to execute the "Run Me" file, but it gave me this:
"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!"
Nothing happens on the Kindle Fire. But I checked the Device Manager, after I downloaded and installed a driver linked in a thread on this forum, it said the Kindle was USB-enabled interface. Anyone have any idea what the problem is, here? Thanks
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Ok did you enable usb-debugging in the kindle's security settings? If you have try opening a command prompt and CD into the directory of the adb command in binary's root tool, run adb devices and see if the kindle is listed.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Yep, USB-debugging is enabled. It's the same thing as enabling ADB, right? This is what I've done thus far. I'm running Windows 8, so I've disabled driver signature enforcement, and also installed the drivers. I've checked Device Manager---the system has recognized the Kindle as a Google Android ADB interface, and if I check adb devices in cmd prompt, the serial number of my Kindle is listed. Also created an adb_usb.ini file according to these instructions:
"open adb_usb.ini with notepad
(add on one line each!)
0x1949
0x006
save file."
The problem now is not that nothing happens on the Kindle when I run the root tool, I do get the option to restore data but it prompts me to enter a data encryption password. I researched this and a techleopard article said to enter my Amazon password, which I did but nothing happens. The data restore options (Restore or Do Not Restore) just grey out and the root tool just says "Running" for ever and ever. Tried some other root tools such as Quemp and Kindle Fire Utility, but neither worked and besides the more recent information I've seen have Bin4ry's as the only one that works on 7.4.6 which is the OS I am using.
EDIT: Okay, tried it again and for some reason this time the root tool ran successfully. I did a power reset, and ran a RootChecker, and it says it's rooted but I can't find the SuperUser app (the checker also could not find it). Was the root still successful?
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Probably though I am throwing a guess that only the such binary is installed, look in the /system/xbin folder and see if the such binary is there, if you want to to retry the process just delete that file. I was going to mention the encryption password is whatever your lock screen code is set to.
BTW don't ever use kfu to try to root your kindle, it will hard brick it. Its designed only for kf1's.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Heh, actually after a LOT of messing around, and perusing several articles across the web and on xda, I've got it working. KFU didn't brick anything, just didn't work. My only regret is that I now can't access the HD quality movies I'd bought from Amazon because Amazon only allows downloading to the Kindle and the Kindle only, and my internet isn't fast enough to stream HD.
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
damofitz said:
Hi, I have two Kindle Fire HD 7 inch, I think both are the older model. Until recently, one was bricked after i rooted but it started getting random restarts after being fine for months. I decided to try flashing a custom ROM, but due to following a YouTube video and not loading the ROM first before flashing, my fault as I mid heard the instructions, it died and I didn't know enough to reliase it could be fixed with a factory cable. I got a replacement and due to a **** up at Amazon, I managed to keep the broken one also.
I decided to root the newer one a few weeks in but months later it started having issues with dolphin browser constantly restarting, so I decided to buy a factory cable as a precusion and flash it to cyanogenmod. Everything went well so i dawned on me that I could fix the first one with my cable. I managed to fix with instructions from here and then flashed as well. Everything seemed to work fine until it started randomly restarting. Then it would get stuck at the blue kindle logo, would still allow me into twrp, so cleared dalvik and everything else and reflashed, it would load as newly flashed, but end up restarting again and eventually getting stuck at the blue logo again. I've seen a few threads with similar problems but couldn't find one that matched the circumstance.
So, my question, it this likely a hardware issue as it did get dropped once or twice in its short working life, or is it a software issue and something I could fix ???
Click to expand...
Click to collapse
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Did you overclock the processor?
stunts513 said:
i can take a few guesses at what would be causing a random reboot, i know dolphin can, i don't know why you would need to reflash to fix it though, thats very unusual unless maybe a filesystem error was causing it but it shouldnt have the same error everytime, i could suggest scanning the system partition for errors from recovery, i'd have to grab the command you'd need to run through adb. you dmesg would tell you if there were filesystem errors probably, mine was telling me about them so i finally got around to fixing them. i will mention i know dolphin can cause it to reboot randomly, i have had it happen before, i think it draws too much power trying to run it and causes the crash, not positive though.
On a side note you may want to rename the thread to 2012 kindle, the 2013 one is not rom-able, only rootable.
Click to expand...
Click to collapse
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Oh, and I haven't over clocked, I signed into play store and allowed it to download all my girlfriends crap so she could use it for a while while her galaxy tab goes into the shop as it has the red charging cross issue.
damofitz said:
Sorry, your right, its the 2012, I just noticed that the 2013 doesn't have a front camera. As for dolphin, I uninstalled a bunch of times with the same result, but I like it because the flash player works well once set up properly. It always starts off fine then gets progressively more unstable on my working kindle. I don't know much about adb, just the basics but have KindleFireFirstAid and other programs that used the fix permission errors. I haven't got round to trying them get though as the kindle normally wont stay on long enough.
When it was just rooted, the kindle would still restart so I was hoping that flashing might fix it in case it was something I had done wrong.
Click to expand...
Click to collapse
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
stunts513 said:
you mind booting it up into a os and running this from a command prompt?
Code:
adb shell dmesg > log.txt
you will need to have a command prompt cd'd into the directory of adb, so either in a kffa folder or srt folder will do, anything that came with adb really. if you don't know much about command prompt then do this: shift + right click the folder with adb, hit "open command window here", then run that command.
Click to expand...
Click to collapse
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
damofitz said:
I normally go from the SDK platform tools folder to check the device is coming up, does that work?
Click to expand...
Click to collapse
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
damofitz said:
Ok, i tried and it and it just shows the command line again. Have killed and restarted server but no difference
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb devices
List of devices attached
D025A0A024060MRL device
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>adb shell dmesg > log.txt
C:\Users\Kirsty\Desktop\SDK\sdk\platform-tools>
update: I have noticed that when plugged into my laptop, the Kindle will stay on indefinitely, but when I unplug or not long after, the Kindle then restarts, especially when im doing something like searching the web or opening apps, so could it be a power source problem?
Click to expand...
Click to collapse
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
stunts513 said:
i probably should have mentioned that the commadn i asked you to run was outputting the text into a file called log.txt in the same folder you ran the commadn in... plz post it as a attatchment. sorry for my stupidity.
Click to expand...
Click to collapse
No need to apologize. I left the table on all night and its still on this morning. The log is attached
damofitz said:
No need to apologize. I left the table on all night and its still on this morning. The log is attached
Click to expand...
Click to collapse
think the filesystem is ok not seeing any errors...another thing you could do is leave the device plugged into the pc with this running
Code:
adb shell "su -c 'cat /proc/kmsg'"
and whenever it reboots just copy and paste the last lines it outputted.
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
Hi, I'm new to this whole android thing. I got a Kindle Fire HD 7" it's rooted with SuperSU and Google Play store on it successfully!
My main issue is it seems many tweaks like a reboot after installation, but my power button is completely missing. I can plug the device in to turn it on, and open/close the cover to put it to sleep.
Are there any tweaks around where I can like slide to power down, or force reboot how you would if you were to press the power button?
Alternately, I'd also like to remove the ad lock screens and potentially install a live wallpaper on either the lock screen or the home page. And maybe have an actual android grid set up. I know you need a secondary launcher to do this kind of thing, but all the ones I looked at screamed brick, and I got a bit worried. Could anyone point me at some basic tutorials? (I've jailbroken my Ipad rather extensively, but this seems to be a bit more in-depth to the actual operating system)
ETA: I haven't Used QMenu Just the ABD Drivers and the Root_with_Restore_by_Bin4ry_v33
If this is the 2012 model with a camera you can flash cm 11 on it and use maromi's kernel, it has double tap to wake, and cm also has double tap corner to sleep.
There are apps in the Google play store for rebooting methods that I believe allow for reboot normally as well as to fastboot and recovery, I know CM's built in power menu has those option if you enable them, but then there's the issue of getting to them with a broken power button.
Sent from my Amazon Tate using Tapatalk
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Dovetail said:
It is the 2012, it has the camera with the clear slider to unlock.
I installed Nova Launcher off the G-play store, but yet again something needs to be rebooted! Hmph.
I'd love if you have any links to those store based power options, or to the CM 11 (is that a launcher also? what does "Flash" mean exactly? I've seen it around. ) The power button issue sucks, but I can't complain since it was a free gift!
I guess I can just run the battery down to reboot, but that is such a pain.
Click to expand...
Click to collapse
hehe wow this is a first, ok cm 11 is cyanogen mod 11. its a rom you can flash instead of amazon's original os, it is way faster and more up to date and is more like pure android. Flash basically means we are overwriting the system files and such that came with the device. It can have any launcher, set wallpaper, is already rooted and has alot of cool things like themes and performance options you can set, much better than stock amazon os. You seem quite new to the concept of flashing a rom though so i advise you to read the tutorial thouroughly and as long as you don't mess up you shouldnt need a fastboot adapter even though its always advised to have one anyways. Heres a link: http://forum.xda-developers.com/showthread.php?t=2271909
Let me give you some advice so you don't end up with a red screen brick. Make sure when you follow this that when you see the red text at the top of fireflash(you will understand this when you start this part) that you check that box off thats either to the side or above the red text, this is a vital step you must follow or you will need a fastboot adapter to fix. I also recommend grabbing the cm rom and its corresponding gapps ahead of time.
Feel free to ask questions.
Also if you install a launcher on amazon os you will need root and you must copy and paste the app into the system folder and set the permission to a certain way or it will bootloop. I think titanium backup has a convert to system app button that does it for you. Wallpaper doesnt defaultly work without my fix either.
Nevermind, it finally worked
stunts513 said:
Feel free to ask questions.
Click to expand...
Click to collapse
Thank you so much for being patient with me!
I had been doing the app thing, but it seems like such a pain to do that with every app. I removed the installer, it wasn't doing much of what I was wanting anyways, the CM11 sounds much more like what I'm wanting to get to.
I'll give the tutorial a good read through and update this post with any questions I have!
Question 1: "commonly associated .... higher without first flashing the Amazon OS 7.2.3 bootloader" With flashing the cm11 do I need to (or do you recommend I) first restore or go back to the 7.2.3 or can I continue with 7.4.8? I will obviously be making backups as it seems that's the only way to recover with a standard usb cable.
Question 1A: If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on. Is this the box you mentioned? It seems like this saves the hassle of going to 2.3 THEN flashing.
Question 2: "Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry," I used this method in the first place. I had some issues with the ABD drivers not being recognized but got them working when I used amazon's direct ones. Furthermore, when I did get rooted (I used an app to check that it was and since nova worked I assume it was correct) superuser wasn't installed. I went and installed superSU manually. will this be an issue? (things have asked for and been granted permission and show as such in the superSU app)
Question 3: I'm using my work computer which runs through a server. when I go to back up through cmd it says the folder will be in C: and to then transfer it. The server shouldn't matter, right? I guess I can always just do a search for the file name and it'll turn up somewhere.
Question 4: Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP I did find an app called "reboot" which allows me to reboot (shocking!) without the power button. Can I still use that app at this point?
Question 4A: Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache.After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot This section calles to wipe some sections, will this also wipe my apps? it calls later on to reboot again. If the first bit wipes the apps, then I wouldn't be able to reboot at this point. (aside of waiting for the battery to die)
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Answer 1: you don't actually need to downgrade the os, as long as the bootloader gets downgraded it is fine. So yes that was the checkbox I meant, believe it or not people have missed seeing it before because of the red text around it.
Answer 2: I think it will be fine, though I'm surprised you could root it with Amazon's drivers, theirs were kinda crappy.
Answer 3: I think this is OK, not sure how your setup is exactly. I don't see network issues being a problem.
Answer 4: you can still use the app. As to the wiping, yes you will lose all your apps, it is required to do the equivalent of a factory reset in twrp when coming from amazon os as the system apps leave some data left behind that causes cm to malfunction. You can install anything you had again from the play store or manually if you had apk's lying around. You can backup app data for games and such with titanium backup and restore it once you reinstall titanium backup in cm.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Thank you so much again! I'm excited! I'll let ya know how it goes.
Sweet and I thought I'd mention if you get confused on what cm 11 build to download, the unofficial builds are a little bit more dated now that the device is a officially supported cm device, I recommend the link that isn't under mirrors that goes to cyanogenmod's Tate download page. The URL has those 3 words in it so you will know it when you see it. The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon, the cool thing is whenever a update is available it can ota like a phone, I believe it will make you choose to install the update though. I was impressed by how it updates, just seemed cool to watch. Not positive if cm's updater notifies you when updates are available though.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
The m6 release is the stable release I recommend download instead of a nightly, I think m7 should be out soon
Click to expand...
Click to collapse
Firstly, when I go to back up through the command prompt I get this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\admnasst>adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot
0block.img"
'adb' is not recognized as an internal or external command,
operable program or batch file.
Am I missing some step? I do have ABD enabled on the kindle.
Secondly, on this site: http://download.cyanogenmod.org/?device=tate
am I wanting the download second from the bottom that says "snapshot" and ends with m6-tate
I would figure so, but I wanted to double check.
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
stunts513 said:
Yes that the right file, as to that command not being recognized it is because it expects you to have a copy of that command handy and in the directory the command prompt is cd'd into. For instance download my wallpaper fix in my signature and extract it, then shift + right click the folder and hit open new command window here, then try the command again.
I have and by itself laying around on a thread I made here on the forum but this works just as well.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
I ran the first line and it started. I'm going to do everything tomorrow when I have more time. I'll keep you updated! Thank you again for helping me, and being so welcoming.
https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot this was my favorite reboot app and it works well although I see your doing the custom ROM thing now.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
ROM toolbox has a quick-reboot option that is similar to respringing iOS, and it well let you create a launcher shortcut on your home screen.
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a Kindle Fire HD running Cyanogenmod 11<<<