r/kindlefire • u/[deleted] • Aug 28 '12
So I modified/updated Kindle Fire Utility
So after everyone has been having trouble with KFU and TWRP lately I decided to look into it as part of my massive "Android Rooting Extravaganza" (Sure that name works, this week I've completely overhauled my guide on the GNexus and wrote one for the Nexus 7, after this it's on to the Toshiba Thrive). Turns out on XDA someone added unbricking tools to KFU, which I thought was damn nifty. So I took that, cleaned up the menus and also updated the TWRP link to be 2.2.2.1 instead of 2.2.0, which I hope fixes some issues.
I'm calling this an "Unofficial" KFU 0.9.8. If you want a changelog from 0.9.6:
Added Unbricking Tools for various scenarios
Cleaned up Unbricking Menus to look like the rest of KFU
All in one Root/Bootloader/Recovery Install
Updated TWRP from 2.2.0 to 2.2.2.1
Install FIREFIREFIRE Extended
I'm going to work more on it this week, but for what I feel will be deserving of KFU 1.0 will have
Flash Stock ROM (useful for people wanting to sell I imagine)
any other features people would like added?
And without further ado, here is my "Unofficial" KFU 0.9.8"
Edit: Oh and yes I know I should credit people/ask permission for code usage. Right now I'm more concerned with pushing out a good product and frankly would rather ask forgiveness than permission. I'm not even getting karma for this.
Edit 2: If anyone asks why I'm working on the Kindle Fire when really the KF2 or whatever is coming out. Practice. I've not really worked too much with Android on the command line or developing apps like this and I prefer to work with something more mature first.
Credit:
Full credit of TWRP goes to Team Win for releasing an awesome tool! Good job guys.
Vashypooh on XDA for the initial 0.9.6 KFU
Chat_Ghosty for inspiring me when he added the Unbrick tools
eldarerathis for making FF Extended
Zombiepiratez for writing the Unbrick Utility
Hashcode for FFF
1
u/Duh_Ogre Aug 28 '12
Giving me an error while trying to root saying "MD5 did not match. Aborting and deleting local content. The directory is not empty."
1
Aug 28 '12
When did you download it? I've updated it at least five times since I uploaded it.
1
u/Duh_Ogre Aug 28 '12
Just within the last hour or so
1
Aug 28 '12
Which command were you trying to input?
1
u/Duh_Ogre Aug 28 '12
First I was trying to do the all in one. Then I just tried the root w/ superuser. Gave me the same thing
1
Aug 28 '12
Yup, running into the issue now myself. I'll debug it. I'm about to head home for work so I might not be able to take care of it for an hour or two. If you want to work with the official KFU it'll work just fine, I'm just trying to fix it and this is definitely beta at the moment. But I appreciate you testing it out!
1
u/Duh_Ogre Aug 29 '12
Any update on the MD5 issue?
1
Aug 29 '12
That's fixed along with a host of other issues. I'm actually trying to upload my "final" version right now. The only feature that didn't get in is revert to stock, which is easy enough to do manually anyway and carries more risks than you'd think to do through a computer (I've soft bricked my KF so many times these past couple days...)
1
Aug 29 '12
Okay, finally finished uploading it. I've called it 0.9.8 now.
1
u/Duh_Ogre Aug 30 '12
Not sure what happened, but it's working now lol. I used the 0.9.7 earlier, it still acted funny, but decided to say what the hell and install the rom. Installed just fine.
1
1
u/Nivuahc Aug 29 '12
Wow. So, I think I might be screwed...
I wanted to go back to stock but I could not get TWRP to launch. I currently have gedeRom installed so I ran KFU and tried to install TWRP.
The best I can get, right now, is for my Kindle to start the loading of gedeRom (the screen with the alien like dude and the blue background) but no further. My Kindle is recognized by my computer during this sequence but I cannot seem to get it to install a thing.
It always tells me that the folders can't be found, etc.
I've tried to tell it to reboot into recovery but this is what happens; The KindleFire logo comes up, the Kindle shuts down, it comes up again, shuts down again, over and over about a dozen times... and I'm back to the gedeRom loading screen.
Same thing happens when I try to tell it to boot in Fast boot or Normal.
How fucked am I?
EDIT: When I originally installed gedeRom I installed TWRP and FireFireFire but it's almost as if those no longer exist
1
Aug 29 '12
Okay, have you tried to tell it "reset boot mode" or whatever the third option is? Try that, and then let it attempt to boot. If fails try to manually tell it "Normal Boot", do the same reset and then try recovery. You're getting SOMETHING so the tablet should be recoverable.
1
u/Nivuahc Aug 29 '12
I've tried all of the boot mode options. :/
1
Aug 29 '12
Okay, when you connect it to the computer, does it every tell you "ADB Status: Online" or "Boot Status: XXXX" where XXXX is some number?
1
u/Nivuahc Aug 29 '12
Yes, once it gets to the gedeRom load screen
1
Aug 29 '12
Okay, good, good. Hm, my guess is that your gedeROM file was corrupt or somehow failed to install entirely. Oh... how long do you wait before you think it's bad? Five or ten minutes isn't abnormal for a first install
1
u/Nivuahc Aug 29 '12
I've been running gedeRom for a couple of months. This is a recent development. And it ran last night for about a half hour before I gave up and went to bed.
1
Aug 29 '12
Ah, okay. So you HAD gedeROM installed, then went into the KFU to try to reflash TWRP. While you have the KF plugged into the computer, turn it on, don't let it get to the gedeROM loading screen. It should be in fastboot, try to install TWRP again. If after a few times it doesn't recognize it... what does Windows devices show?
1
u/Nivuahc Aug 29 '12
Tried all of that.
It isn't recognized at all until it gets to the gedeRom load screen and, only then, Windows Device Manager shows it as an Android Composite Device under the "Android Phone" listing.
I tried re-installing the drivers using KFU, I tried installing the drivers with the Android SDK...
1
Aug 29 '12
Okay... you're PROBABLY going to start needing the command line soon. I want you to first do this:
First connect your Kindle Fire to your computer and let the drivers install (WARNING: You must use USB 2.0, the Kindle Fire doesn't like rooting through USB 3.0). Then navigate to the [your user name]/.android folder. Edit the adb_usb.ini0 file, adding the following line of code at the end:
0×1949
0x18D1
The 0x18D1 appears to be a catch all. Also I know you probably did this, but check these:
Find the folder where the SDK was installed and open the google-usb_driver folder (C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver). In that folder, find the file android_winusb.inf and add the following code to both the [Google.NTx86] and [Google.NTamd64] sections:
;
;Kindle Fire %SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006 %CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Once checked, hook it back up.
→ More replies (0)
1
Aug 28 '12
Thanks, I hope this helps out some of the people that were having problems and prevents future ones.
1
-2
1
u/yakkafoobmog Aug 28 '12
I'm going to try this out tonight. Does it work on Windows 7, or should I use my wife's old XP laptop? Because I've read that XP works better for this, but I'm not sure on how true that really is.