Database Develop

[Q] [ROOT]Kindle Fire HD 7.2.3 - I can't root

Hi everybody. I have a problem with rooting my kindle fire hd. I used this method Method1, Method2, Method3.
In first method all proces has been end sucesfull but my kindle nothing rooted (in superuser i don't see anything aplication.
In second method it's this same.
In third method I can't get permision to create data/local.prop
adb shell
[email protected]:/ $ echo 'ro.kernel.qemu=1' > /data/local.prop
echo 'ro.kernel.qemu=1' > /data/local.prop
/system/bin/sh: cannot create /data/local.prop: Permission denied
Click to expand...
Click to collapse
What I do wrong? I have two superuser apps on my kindle but anything don't get root permision to my es file explorer. I buy this few days ago and I never install before root to my kindle.Please help me.

I restore to factory settings, install root from method1 and now device has been rooter. I don't know why in first time i can't set root to aplication. Now all is ok. You can close this topic

Rooting KindlefireHD 7.2.3
hi,
after i have typed echo 'ro.kernel.qemu=1' > /data/local.prop
kindle told me i have no persmission to do it. But remove hide tmp folder i can be able
anybody can help how to continue?
thanks

Rooting KindlefireHD 7.2.3 - success
dagelo said:
hi,
after i have typed echo 'ro.kernel.qemu=1' > /data/local.prop
kindle told me i have no persmission to do it. But remove hide tmp folder i can be able
anybody can help how to continue?
thanks
Click to expand...
Click to collapse
okey. So, after dancing with ... :cyclops: i was able to get root in my kindlefirehd. Unconfortable was that all this magic i did from my Windows 7 I wasnt able to do it from my gentoo. Dunno still why.
So, about rooting process in windows -> First problem was that adb.exe from both methods (in archve archive) didnt see my Kindle device, despite of fact that kindle storage presented in My computer. Every time i run adb.exe its told me that please insert device or device not visible for ADB.
Then, adb.exe devices returned me only empty output lines.
This problem was fixed by download Andloir SDK tools and copy ADB.EXE from platform-tools to the both unzipped directories from these rooting methods.
After completed first method my kindle was very slow. Second methond with Qemu solved it somehow
So, now i can edit some files via simple built-in texteditor. Also, TitanimBackup now installed on my device.
Also, there is a one note about linux. Especial for gentoo distribution with hardened kernel. Something (dont know still what exactly, maybe PaX configuration) causing that adb returns error :
PHP:
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
If you run
PHP:
adb nodaemon server
it will show you exactly the reson what is wrong. In my case it was:
PHP:
error: Operation not permitted: cannot create input thread
.
Solving with command paxctl -m /path/to/file/adb
Hope somebody will found my note useful.

rooting kindle fire hd 8.9
I have tried all methods. Just factory reset and tried method 1,2 and 3 again. Method 2 give this message Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE] after the daemon loads. I am downloading the Android SDk to try and get the latest adb program. Maybe that will work. Any HELP!!:fingers-crossed:

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.
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 tbe 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 wsit 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 itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app

Thanks!
Hinzman420 said:
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.
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 tbe 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 wsit 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 itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
It worked for me! Thank you!

Try this man
http://www.oneclickroot.com/tablet/kindle-fire-hd/
Sent from my SGH-T989 using Tapatalk 2

Your welcome I too had a horable time rooting until I pieced this together. Glad it helped
Sent from my KFTT using XDA Premium HD app

Hinzman420 said:
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.
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 tbe 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 wsit 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 itand enjoy.
Pm me if you have any questions or just reply here.
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
I hear you about this being a nightmare. I'm pretty sure got all pre-req, adb drivers and i've checked adb devices and the device appears but i keep getting system/bin/sh permission denied message.
what do i need to fix?

Widodude said:
I hear you about this being a nightmare. I'm pretty sure got all pre-req, adb drivers and i've checked adb devices and the device appears but i keep getting system/bin/sh permission denied message.
what do i need to fix?
Click to expand...
Click to collapse
Try deregistering your kindle and reinstall java then try rooting again. Dont ask why but this worked for me.
Sent From My Kindle HD Running Kinology Rom

Did i brick my Kindle Fire HD?

Hi after rooting my kindle fire hd 7in. I got back to the regular menu and now the Kindle fire HD screen keeps flashing and running very slow with no pictures of any of the apps on the menu just the names and titles . Iv'e posted a picture of the main menu . Is there a way to fix this?
I can still swipe from screen to screen but very very slowly , I've also noticed i can type using the keyboard but very slowly.

BrandonLH81 said:
Hi after rooting my kindle fire hd 7in. I got back to the regular menu and now the Kindle fire HD screen keeps flashing and running very slow with no pictures of any of the apps on the menu just the names and titles . Iv'e posted a picture of the main menu . Is there a way to fix this?
I can still swipe from screen to screen but very very slowly , I've also noticed i can type using the keyboard but very slowly.
Click to expand...
Click to collapse
Wondering if this will help me :
So this worked for me with the Softwareversion 7.2.2 !
Step 1 use this tool http://forum.xda-developers.com/show....php?t=1886460 and use the normal method.
(the program will say that the process has not worked but this it all ok) now the Kindle is very slow
and the display is blinking.
Step 2 now you use the Quemu Method for the 7.2.1 version (http://forum.xda-developers.com/show....php?t=1893838)
That was all and now you should have root!! n
*Update: This works also with the 7.2.3 Software version i only used the 1 Step ( Root many Androids )
Can someone give me any insight before i use
Thanks

BrandonLH81 said:
Wondering if this will help me :
So this worked for me with the Softwareversion 7.2.2 !
Step 1 use this tool http://forum.xda-developers.com/show....php?t=1886460 and use the normal method.
(the program will say that the process has not worked but this it all ok) now the Kindle is very slow
and the display is blinking.
Step 2 now you use the Quemu Method for the 7.2.1 version (http://forum.xda-developers.com/show....php?t=1893838)
That was all and now you should have root!! n
*Update: This works also with the 7.2.3 Software version i only used the 1 Step ( Root many Androids )
Can someone give me any insight before i use
Thanks
Click to expand...
Click to collapse
Just remove your '/data/local.prop' and reboot

soupmagnet said:
Just remove your '/data/local.prop' and reboot
Click to expand...
Click to collapse
Im sorry im new at this where is this file : /data/local.prop file . I looked in the data file and didn't see anything related to local.prop?

BrandonLH81 said:
Im sorry im new at this where is this file : /data/local.prop file . I looked in the data file and didn't see anything related to local.prop?
Click to expand...
Click to collapse
That is the common solution to your problem. If the file doesn't exist, you may be looking at bigger problems. First, I would suggest (just to be sure) you run the following commands:
Code:
adb shell
su
rm /data/local.prop; reboot
If the problem persists, you may want to take the steps to install the 2nd bootloader, custom recovery, kernel, etc. and flash the stock Kindle Fire ROM available in the Dev section.

[Q] Kindle Fire 7" Root

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.

[Q] Kindle Fire HD Stuck Booting on TWRP Instead of Android

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

[S] How can I repair /system/build.prop ?

Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.

elRufo said:
Hello to everyone,
I was looking how to install Amazon Store on my Kindle Fire HD 2012 running CM11, when I noticed that I have to change something in /system/build.prop
I had troubles to edit this file because root privileges, so I copied it to emulated SD, then I edited it and copy again to its original path.
It seems than anything went wrong. The tablet gets stucked with "Kindle Fire" blue logo on the screen.
Notes:
My laptop (W7) doesn't recognize the tablet. ADB drivers are correctly installed (or, at least, it seems it). It tries to install "MTP USB device" but it fails before complete setup.
How can I repair /system/build.prop?
EDIT: Nevermind, I ****ed it up.
I have made a wipe of cache, davik and system with "team Win Recovery Project" and it screwed everything. It looks like it is erased, so I'll try to install a new CM version.
--
I know that I make mistakes writing in English, I'm Spaniard.
Click to expand...
Click to collapse
You can ADB sideboard onto TWRP. Easier than starting over.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
You can ADB sideboard onto TWRP. Easier than starting over.
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
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file

elRufo said:
Maybe it's a noob question, but... how I could do that? I had tried several times to install ADB drivers (W7) and it doesn't install correctly. Installer says that it can't write 0x1949 in users/MYUSER/.android/adb_usb.ini file
Click to expand...
Click to collapse
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk

stunts513 said:
To install the adb driver you need the drivers in my signature. I haven't seen people even messing with the adb_usb.ini file in a while. If you are trying to install it while in twrp and you still happen to see a MTP device then you will need to find a USB composite device in the device manager and if you have more than one, it's simple enough to find the right one, just right click one and goto details and then choose hardware id's, if one has a vid of 1949 then uninstall it and scan for new devices and it should pick it up correctly.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Right Click>Install (w/ Administrator rights)
My Windows 7 (x64) says "This install metod is not valid for this .inf file"
I tried to install original ADB under Administrator account and it looks like are correctly installed, but after that, my pc detects the Kindle Fire HD on "printers/other (and a picture of a mainframe as icon)", so I don´t have access to internal storage to copy CM11 rom and gapps zip.
Note: I own a fastboot cable, I don't know if it could be usefull in this case.

You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk

stunts513 said:
You don't install my drivers like that... open the device manager and if you see a device with a triangle next to it, right click it and hit update drivers, then point it to where you extracted them and it should install.
Sent from my LG-P769 using Tapatalk
Click to expand...
Click to collapse
Done! Thank you for your patience explaining something thousand times