Related
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Zponds360 said:
i have a Kindle Fire HD 7" with the system version of 7.2.1 and i wanted to ether put ICS or even Jelly bean on it so that i could have that Android Interface instead of the Amazon book self thing which im not very fond of and also have the Play Store. I spent all of yesterday, not exaggerating, all of yesterday trying to root my device. So i watched all the videos on you tube and read a ton of threads about it here at XDA and i just dont know what im doing wrong.
So first i download the Kindle Fire Utility (KFU) and installed the drivers(in device manager it showed my kindle fire and under it Android Composite ADB Interface), then plugging in my device i ran the "run" batch file. and the red command prompt pops up and it brings up the menu and at the bottom it says "ADB Status: Online, Boot Status Unknown" so i tried changing the boot mode to normal or fast boot,just changing it at all would have been nice but it always just stays as unknown. i tried hitting 1 to change to different boot mode but it would just reboot with no changes. then i tried entering 2 "installing permanant root with superuser" and twards the bottom of the screen its says rebooting device into fast boot mode, installing FFF, waiting for device. and it reboots and thats it, it doesnt go anywhere from there. so then i went to "6" extras and then "1" install google app / Go launcher which actually did work i have the Play store and Go Launcher (it says installed but its no where to be found on the device) and i also tried all the other options on the main menu, install TWRP, CLOCKWORKMOD and FFF and they all say missing directory and my kindle reboots and it says waiting for device and thats it nothing happens
SO i gave up with that method
so then i tried using the SDK -> ADB-> platform tool command prompt method and typed everything perfectly just like the threads and videos said to and still its like i got no where. i typed everything in just as shown and it seemed to be working but at the end it didnt work ether. i wish i had more specifics of what i typed in and what it said back in the command prompt but i did this yesterday so its gone now. i Dont know what im doing wrong and its very frustrating
(keep in mind im a noob and simple terms would be appreciated)
Click to expand...
Click to collapse
WARNING!!
Firstly your Using a Kindle Fire HD. That is different to the Kindle fire. Even with root I dont think your gonna be running Jelly Bean just yet. You will probably brick the device if you use a standard Kindle Fire ROM!!!!!!!!!!!!!!!!!!!!!
Ok first download and Install the Android SDK. Put it where its easy to find. I use c:\ . Once thats done open SDK manager and tick next to Android SDK Platform-tools and click the box for Install packages.
Once thats done See this page: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
This gives the most stable ADB I have found.
OK next see this thread. This is automated root. http://forum.xda-developers.com/showthread.php?t=1893838.
If that still doesnt work (It didnt for me and others). Watch this Video. http://youtu.be/CYDBoTtdvcE This is the manual method. For a bigger look at the code see this page: http://www.redmondpie.com/how-to-root-amazon-kindle-fire-hd-7-8.9-on-android-4.0.4-ics/
On this page the open quote looks like a tilde EDIT thats actually a grave accent...I always called it the tilde key. Its not just use the KB apostrophe ( ' ) wherever you see a quote!
Hope this helps and I hope I dont get into trouble for posting external Links. Just trying to help!
Hello guys!
I just came on this awesome forum and I would like to stay active here
So, I got my Kindle Fire HD 7'' recently and yesterday I tried to root it but I failed ( some problems that said : Permission denied ) and I left it there. Today, I turned it on and the status bar and the sidebar with home etc has been disappeared. I tried a lot of things , but with no success. I have installed file manager but I can't find something that could be useful to restore my Kindle. I just want to get on the menu "Device" and press the button that format in factory settings my Kindle. Can someon help me, please?
If you're using gmail, turn off notifications. They interfere.
Sent from my DROID BIONIC using Tapatalk 2
No, I haven't any Google app. Can, someway, restore to the factory settings? I have installed,as I said, an file explorer.
Guys! Need some help here! Just tell me how to restore my Kindle is the basic settings ( factory )!
eliac7 said:
Guys! Need some help here! Just tell me how to restore my Kindle is the basic settings ( factory )!
Click to expand...
Click to collapse
Do you have a fastboot cable? Do you have root?
Sent From My Rooted Kindle HD 7"
No, I don't have a fastboot cable. What is that?
And no , I don't have root.
eliac7 said:
No, I don't have a fastboot cable. What is that?
And no , I don't have root.
Click to expand...
Click to collapse
Ok i would suggest buying a fastboot cable (factory cable) you can find one on amazon for like 3$ but first lets see if we can get that thing rooted maybe it will bring it back to where you need it. Follow these directions exactly and should get it rooted.
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter. Sdk being a new folder you created. Put files in sdk folder
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when the screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wait till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate it and enjoy.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Ok i would suggest buying a fastboot cable (factory cable) you can find one on amazon for like 3$ but first lets see if we can get that thing rooted maybe it will bring it back to where you need it. Follow these directions exactly and should get it rooted.
First things first lets get your sdk and drivers setup correctly.
1. Download the sdk package from here http://developer.android.com/sdk/index.html#download
2. Open the file you downloaded and take the sdk folder and the sdk manager file and copy it to you hard drive. C:/sdk** C Being the hard drive letter. Sdk being a new folder you created. Put files in sdk folder
3. Now you need to open up sdk manager and go to tools menu and select manager addon sites. Now select user defined sites tab and select new and enter this site. http://kindle-sdk.s3.amazonaws.com/addon.xml and click ok.
4. You need to click the following boxes to install the packages you need. TOOLS, ANDROID 4.0.3 (api 15), and EXTRAS. Then click install packages to install them.
5. Now you need to install JDK from here http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
6. Now you need to install your basic java from here http://www.java.com/en/download/index.jsp
7. Now you need to install kindle fire hd adb drivers from here http://forum.xda-developers.com/showthread.php?t=1890413
8. Now shut down your kindle and connect your kindle to your pc and let it boot all the way and unlock the lock screen.
9. Now you need to run this tool https://dl.dropbox.com/u/54456659/Root_with_Restore_by_Bin4ry_v18.5.1.zip
And select option 1 and on your kindle when the screen pops up asking to restore go ahead and tap on restore.
10. When your kindle restarts the lock screen should turn black and look funny ( if this does not happen then run the tool again untill it does) Now unlock the lock screen.
11. Now you need to run this tool https://dl.dropbox.com/u/54456659/Qmenu-v2.5.zip and select option 1
When it says press enter to proceed make sure you wait till it fully boots and you unlock the lock screen before continuing to next step. Once all steps are completed you should have root.
Open superuser to activate it and enjoy.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Thank you very much for the instructions. I will try and I will let you know.
Can you link with me a cable from Ebay?
eliac7 said:
Thank you very much for the instructions. I will try and I will let you know.
Can you link with me a cable from Ebay?
Click to expand...
Click to collapse
Just let me know even if you just get root and dont get the nav bar we still have some options.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Just let me know even if you just get root and dont get the nav bar we still have some options.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
So, okay, I installed all the things and I am going on the step to open the RunMe.bat and then I choose the option 1. Then, it scans to get my Kindle, but can't find it. Now, the thing is that I can't know if the Kindle has opened the ADB as I can't go in the Sytem etc.
I attached a picture of my Kindle ( to understand which things have been disappeared )
eliac7 said:
I attached a picture of my Kindle ( to understand which things have been disappeared )
Click to expand...
Click to collapse
Ok my next question is have you called amazon? They have an excellent return policy. Just tell them this happened after their update and play stupid about root or anything of that sort and you should have a brand new one in a few days. Or your gonna have to get a fastboot cable.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
Ok my next question is have you called amazon? They have an excellent return policy. Just tell them this happened after their update and play stupid about root or anything of that sort and you should have a brand new one in a few days. Or your gonna have to get a fastboot cable.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Can you help me with restoring my Kindle? C'mon! There will be a way to restore it from File Manager!
Without root or knowing if adb is enabled. There's not much i can do for you. The only other thing you can try is unplug your kindle ,reset your pc, wait till it boots, then plug kindle into pc this will power on your kindle. Then go into device manager and under kindle when you open that branch it should say android composite adb interface. If not you can try to update drive and choose the option that lets you choose what driver to install. Then search in program files/amazon and install drivers from there. But without knowing if this kindle has adb enabled its kinda hard to help you. But if these do install and it does shows up as android composite adb interface. Then try the rooting process again steps 9 - 11. If you cannot get steps 9 - 11 to work your only other choice is to get a fastboot cable ( factory cable ) and use the kindle restore tool from this thread http://forum.xda-developers.com/showthread.php?t=1951254KFHD System.img Restore Tool and follow downgrade to 7.2.1 section.
Hinzman420 said:
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
Υes, I had enabled it before get this.
P.S.: Do you have TeamViewer?
What is team viewer?
Edit: i just installed it on my kindle. If you cant get it to root send me your id and i can try to help.
Sent From My Rooted Kindle HD 7"
Hinzman420 said:
What is team viewer?
Edit: i just installed it on my kindle. If you cant get it to root send me your id and i can try to help.
Sent From My Rooted Kindle HD 7"
Click to expand...
Click to collapse
You don't have PC to help me out?
Yes but i run my pc all time from my kindle my wife ussually ties up the pc. But i can still help i have team viewer on my kindle. If not ill put it on my pc.
Sent From My Rooted Kindle HD 7"
It can find it , so ADB is turned on on the Kindle! Next step?
Plug it into your pc and go to the device manager on your pc and tell me what it says when you open up the kindle branch of your devices
Sent From My Rooted Kindle HD 7"
Hello everyone....
I have a kindle fire HD 7" 7.4.6
I rooted and added TWRP with 7.2.3 bootloader
I installed CM11 Kitkat the ROM is a bit buggy but nice.
I tried to go from kitkat to kinology which allows use of Amazon and Google services.
But flashing failed.... I can't seem to get kinology to work.
This is the set of walkthroughs I used.
To root & add TWRP. I used a rootjunkie YouTube video ( can't post link)
To install cm 11:
also a rootjunkie video
knowing this, I tried installing kinology using this walkthrough:
Original kinology page.
No luck, does anyone know how I can move my system to kinology?
please help,
Thanks to all in advance
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
OK, 2 things, one you didn't mention if you factory reset when trying to goto kinology and I believe that is a must. Second, you are probably going to have to wipe internal storage with a command from an adb shell to clear the xattrb's from the data partition that cm 11 has set as last I checked kinology uses a stock amazon kernel or something close to Amazon's kernel, and ipamazon,s kernel didn't support selinux so it presents problems going back and forth between those 2 ROMs. BTW wiping internal storage means anything on your sdcard goes bye bye. I will have to go grab the command you will more than likely need to run so gimme a moment.
Edit: I'm lazy tonight, here is a link to a post I made with the commands to run in it: http://forum.xda-developers.com/showthread.php?p=49408371
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Ok first, thanks for the reply. Second, yes i did do a wipe before the install.
I am going to go check out your link now and see.... ill keep you posted.
Thanks again....
Quick question.... can the process in your thread be done through fire flash 11? ( i am an absolute noob at this, so it may be a silly question...)
i can follow along as to what must be done, but i dont feel comfortable doing a process without a guide.....do you know of any threads with a walk through for this?
There aren't any tutorials for this as far as I know, I got this command from Hashcode in the irc, just run the command mentioned above from a command prompt (while in recovery) while cd'd into a utility that came with a copy of adb, like my wallpaper fix for example that's in my signature. If you don't know anything of command prompt like what CD commands normally I would say read up on basic command prompt because its very simple, but because of a nice trick I remembered recently you can avoid the CD command, just shift + right click the folder with adb in it and hit "open command prompt here", then run the command I posted (while in recovery).
Sent from my Amazon Kindle Fire HD using Tapatalk
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<<<