Database Users

No touch screen after flashing system.img

I purchased a Kindle Fire HD 7 inch from a closing down sale attempted to flash a system.img to it to get it out of demo mode. Firstly i tried with the system recovery tool in these forums. I tried 3 different images, 7.1.5, 7.2.1, and 7.2.2. The last one causes the device to not even boot, the first 2 will boot to the start but there is no touchscreen so i can't do anything.
I've tried re-flashing the same images manually without using the recovery tool but it's the same situation. What has caused the touchscreen to not work and is it recoverable?
Thanks.

i had this problem too，you need to flash the other partions in addition to the system.img
if you cannot find them.try this : http://pan.baidu.com/share/link?shareid=140776&uk=906074556，its my backup without system for 7.1.5
Sent from my KFTT using xda premium

Hi, thanks for the reply, is it possible to tell me how to flash the other partition? I can't seem to find anything about it online. Also i don't know how to follow your link.
Thanks
EDIT: I worked out how to open your link. Silly me, i'll try it and see if it helps.
EDIT 2: THANK YOU SO MUCH! You fixed the problem for me, I'm very happy.

glad it helps.
Sent from my KFTT using xda premium

boot loop
longthinkzhang said:
glad it helps.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
hi do i just download file and is there then instructions to follow as i have same problem

bazm60 said:
hi do i just download file and is there then instructions to follow as i have same problem
Click to expand...
Click to collapse
download the file and extract them to ".img"
just change the two names in the code you used to flash the system.img
here is an example, when you are flashing the boot.img, use this:
Code:
fastboot -i 0x1949 flash boot boot.img
for more information：
http://forum.xda-developers.com/showthread.php?t=1930656

Newbie
longthinkzhang said:
download the file and extract them to ".img"
just change the two names in the code you used to flash the system.img
here is an example, when you are flashing the boot.img, use this:
Code:
fastboot -i 0x1949 flash boot boot.img
for more information：
http://forum.xda-developers.com/showthread.php?t=1930656
Click to expand...
Click to collapse
Hi this is all new to me. I did a factory reset and when complete touch screen would not work. I used the img restore from here. Now stuck on boot loop. So do you mean unzipp to this img file with system img in. And if so do I unzip all the other files. And then do I use the tool but write the command you have suggested. I am a bit baffled by this and have an expensive papper weight. Please a little more detail for a beginner. Thanks to all

bazm60 said:
Hi this is all new to me. I did a factory reset and when complete touch screen would not work. I used the img restore from here. Now stuck on boot loop. So do you mean unzipp to this img file with system img in. And if so do I unzip all the other files. And then do I use the tool but write the command you have suggested. I am a bit baffled by this and have an expensive papper weight. Please a little more detail for a beginner. Thanks to all
Click to expand...
Click to collapse
sorry for my bad english
have you flashed the system.img yet ? what's your system version before the boot loop?
you had a KFHD 7.2.2 or 7.2.3 and you flashed my .img files that belong to 7.1.5 , is that right?
if so , i would suggest you flash the 7.1.5 system.img now.
download it from here: http://pan.baidu.com/share/link?shareid=141429&uk=906074556 and then use the code below:
fastboot -i 0x1949 flash system system.img
when i said extract them to ".img", i meant that unzip them and you will get several ".img" files. >_<

boot loop
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working

Hmm......
i am sorry i am totally confused now and i donnot know how to tell you what to do in english. You may start a new thread and i believe somebody will help you.sorry again.
Sent from my KFTT using xda premium

bazm60 said:
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working
Click to expand...
Click to collapse
1. Download the File longthinkzhang showed me earlier.
2. Unzip all the files and put them somewhere you'll remember.
3. Create this folder C:\android-sdk-windows\platform-tools
4. Inside you need 4 files, (adb.exe) (fastboot.exe) (AdbWinApi.dll) (adbWinUsbApi.dll), they shouldn't be hard to find.
5. Put all the previously unzipped .img files in this directory.
6. Put the kindle into fastboot, open command prompt.
7. Type cd c:\android-sdk-windows\platform-tools
8. Type fastboot -i 0x1949 flash xxxx xxxx.img Replace the "xxxx" with the name of each file, example if it's dkernel.img type fastboot -i 0x1949 flash dkernel dkernel.img. Do the same for each file then reboot kindle and hopefully it works.

Solaris81 said:
1. Download the File longthinkzhang showed me earlier.
2. Unzip all the files and put them somewhere you'll remember.
3. Create this folder C:\android-sdk-windows\platform-tools
4. Inside you need 4 files, (adb.exe) (fastboot.exe) (AdbWinApi.dll) (adbWinUsbApi.dll), they shouldn't be hard to find.
5. Put all the previously unzipped .img files in this directory.
6. Put the kindle into fastboot, open command prompt.
7. Type cd c:\android-sdk-windows\platform-tools
8. Type fastboot -i 0x1949 flash xxxx xxxx.img Replace the "xxxx" with the name of each file, example if it's dkernel.img type fastboot -i 0x1949 flash dkernel dkernel.img. Do the same for each file then reboot kindle and hopefully it works.
Click to expand...
Click to collapse
So to reflash frome demo mode I need follow those steps? Right. How do I put it in fast boot mode? Do I need a cable or can I do it another way?
Thanks

Kindle Fire HD 7" Fastboot Mode
712m said:
So to reflash frome demo mode I need follow those steps? Right. How do I put it in fast boot mode? Do I need a cable or can I do it another way?
Thanks
Click to expand...
Click to collapse
712m,
Fastboot mode is enabled on the Kindle Fire HD 7" by using a "Factory USB Cable". You can order
one through the XDA User SkOrPn.
There are other cables out there but not the quality of SkOrPn, plus he is a really supportive member
of the XDA Community. Send SkOrPn a Personal Message with the Subject: Factory Cable Info Please
and include the ship to Country, nothing else (do not send him a long message about your problem). He
will reply with a PayPal invoice which you then place your shipping address, state, etc. After you place
the order he will send you support documentation that includes usage information. If you find yourself
backed into a corner, we offer free unlimited support and if you are really stuck we offer free phone
support, just send us a PM. We always post the results (solution) of the conversation on the XDA
Website so everyone can benefit. Get the cable, it is priceless. Then when it arrives, call us, we
will walk you through the restore step-by-step.

prokennexusa said:
712m,
Fastboot mode is enabled on the Kindle Fire HD 7" by using a "Factory USB Cable". You can order
one through the XDA User SkOrPn.
There are other cables out there but not the quality of SkOrPn, plus he is a really supportive member
of the XDA Community. Send SkOrPn a Personal Message with the Subject: Factory Cable Info Please
and include the ship to Country, nothing else (do not send him a long message about your problem). He
will reply with a PayPal invoice which you then place your shipping address, state, etc. After you place
the order he will send you support documentation that includes usage information. If you find yourself
backed into a corner, we offer free unlimited support and if you are really stuck we offer free phone
support, just send us a PM. We always post the results (solution) of the conversation on the XDA
Website so everyone can benefit. Get the cable, it is priceless. Then when it arrives, call us, we
will walk you through the restore step-by-step.
Click to expand...
Click to collapse
PM sent to SkOrPn

Follow Up - Feedback
712m said:
PM sent to SkOrPn
Click to expand...
Click to collapse
712m,
OK, great, this cable will make your Kindle Restore so easy. When it arrives, send us a PM,
we will be ready to help you and setup a phone or chat appointment. We are here 10:00am
to 10:00pm PST GMT -8. I will give my support staff a "heads up" so we are prepared to
get you online and restored quickly. We will supply you with a download link to download
clean system images. Do you want any options like Root, Google Play Store, Google
Applications, Go Launcher HD, Titanium Backup, etc. We can recompile the Image Files
to include these options, so when restored you will have a custom Turn Key Kindle.
All these options are free, just FYI.

Well now my kfhd is black doesn't power on. when I connect it with the SkOrPn cable and hold the power button I get the computer to some what see the device it flashes on and off as a omap444440.

Kindle Fire Factory Cable USB
bazm60 said:
thanks for your responce, will yes kfhd 7 it was on 7.2.2 i did a factory reset and the touch screen never worked so i used the img restore tool on here and flashe with v2 and other v1.3 did not work, it was with 7.2.1 which came with v1.2, now stuck in boot loop, when you say enter code where am i entering it, thanks
when i say tool from here i mean the KFHD system.img recovery tool
I NEED AN IDIOTS GUIDE ON HOW TO FLASH THE OTHER PARTITION
update. i have flashed it with your image and it now starts but touch screen not working
Click to expand...
Click to collapse
Solaris81,
Unfortunately when you attempt to flash the Kindle Fire HD with this method your
Kindle Fire HD will Brick, as you see. The problem is that you need a "Factory USB
Cable", this is mandatory. Contact SkOrPn to order the cable, please save yourself
more headachs and get the cable through SkOrPn do not buy it from Amazon, they
sell cheap Chinese cables that cause more problems than they fix. Once you get
the cable, send me a PM and we will supply you with the recovery image, step-by-step
on how to restore and if you need it we can supply phone support. Do not worry,
we will be here for you!

I got my SkOrPn cable and now it doesn't even power on now?Help

Kindle Fire HD 7" Dead
712m said:
I got my SkOrPn cable and now it doesn't even power on now?Help
Click to expand...
Click to collapse
712m,
Wow, I am sorry to hear this. Have you attempted to recharge the Kindle? Does the Kindle respond when you
plug in the charger? You should see a picture of a battery, anything? If no, you need to send it in for service.
Is the Kindle under warranty? If no, send it into our company, we have contacts at Amazon and may be able
to pull some strings to get you a replacement Kindle. If you need service, send it to our office:
Noob Series
Attention: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954
Main Line: (707) 774-5923
[email protected]

???
longthinkzhang said:
glad it helps.
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
question how do you flash them with no custom recovery?

help un-(soft)brick my nexus 7 - $10 paypal gift for ya!

I'm really struggling so I've got $10 paypal gift for you if you can walk me through fixing my nexus 7... It's currently perpetually loading the 4 circles after applying the 4.4 OTA update.
I've had CWM installed and rooted since I first got it when it came out. Applying the OTA updates for 4.2 and 4.3 were a breeze. I followed the same process this time and CWM displayed an error.
I still have access to CWM and the bootloader. USB debuugging is not enabled, and I have no way to enable it because I cant fully boot into the device.
Nexus 7 root tool kit doesn't work because ADB apparently cannot find my device when I follow all the steps and try and flash with a new ROM.
I believe I have the drivers installed correctly.
I can query the tablet by using ADB from the command line e.g. "adb devices" and my tablet shows up, but ONLY when I am booted into CWM. When I am at the bootloader, "ADB devices" shows nothing.
Other way around for fastboot...
I can query the tablet using FASTBOOT from command line e.g "fastboot devices" and my tablet shows up but ONLY when I am at the bootloader screen.
I have the official 4.4 image downloaded. I have been attempting to 'push' it to the device using adb from command line so I can just flash it again using CWM, but it appears I don't have permission. Every time I execute the command, I just get a flashing cursor (no errors). I have no backups stored on the device.
I can successfully open a shell on the device using ADB and query the directories etc, but I dont think my permissions are correct here either. Example... I can create new directories via "mkdir", but once I disconnect and reconnect, the directory I just created is gone. Prefixing the command with 'sudo' just gives me an error. I'm not that familiar with linux.
I've formatted the SDcard partition out of frustration, but that didnt help with permissions etc either.
Ordinarily I would love to sit down and work through this challenge, but I really don't have the time!
I will be at home in roughly 4 hours from now. If you are confident you can walk me through it step by step, PM me and we can hook up on GMail chat or something. I'd be delighted to gift you some cash on paypal becuase the only other alternative is me smashing the thing into 1000 bits out of anger :angel:

er043 said:
I'm really struggling so I've got $10 paypal gift for you if you can walk me through fixing my nexus 7... It's currently perpetually loading the 4 circles after applying the 4.4 OTA update.
I've had CWM installed and rooted since I first got it when it came out. Applying the OTA updates for 4.2 and 4.3 were a breeze. I followed the same process this time and CWM displayed an error.
I still have access to CWM and the bootloader. USB debuugging is not enabled, and I have no way to enable it because I cant fully boot into the device.
Nexus 7 root tool kit doesn't work because ADB apparently cannot find my device when I follow all the steps and try and flash with a new ROM.
I believe I have the drivers installed correctly.
I can query the tablet by using ADB from the command line e.g. "adb devices" and my tablet shows up, but ONLY when I am booted into CWM. When I am at the bootloader, "ADB devices" shows nothing.
Other way around for fastboot...
I can query the tablet using FASTBOOT from command line e.g "fastboot devices" and my tablet shows up but ONLY when I am at the bootloader screen.
I have the official 4.4 image downloaded. I have been attempting to 'push' it to the device using adb from command line so I can just flash it again using CWM, but it appears I don't have permission. Every time I execute the command, I just get a flashing cursor (no errors). I have no backups stored on the device.
I can successfully open a shell on the device using ADB and query the directories etc, but I dont think my permissions are correct here either. Example... I can create new directories via "mkdir", but once I disconnect and reconnect, the directory I just created is gone. Prefixing the command with 'sudo' just gives me an error. I'm not that familiar with linux.
I've formatted the SDcard partition out of frustration, but that didnt help with permissions etc either.
Ordinarily I would love to sit down and work through this challenge, but I really don't have the time!
I will be at home in roughly 4 hours from now. If you are confident you can walk me through it step by step, PM me and we can hook up on GMail chat or something. I'd be delighted to gift you some cash on paypal becuase the only other alternative is me smashing the thing into 1000 bits out of anger :angel:
Click to expand...
Click to collapse
Hi, er043...
Flashing a factory stock image is relatively straightforward... (if indeed that is what you're attempting to do)... but it will completely wipe the device, but as you say you've already done that, I don't suppose it matters.
There's an extensive guide here... http://forum.xda-developers.com/showthread.php?t=1907796
The essence of it is as follows...
The following assumes you're using Windows. It also assumes a WiFi only Nexus 7... if you have a WiFi & 3G Nexus 7, the factory image files listed below will contain an additional baseband/radio component and the names will be slightly different.
The files needed in the factory image (see my sig. below for download link) are buried under two layers of compression.
You'll need to unzip the .TAR image file twice... the second file may lack a file extension, just add a .TGZ or .TAR extension, and unzip it.
Once done, you should have the following files in a folder on your Windows desktop... (as mentioned previously, these files are for the WiFi only Nexus 7... if you have a WiFi & 3G Nexus 7, the names will be sightly different; 'tilapia' instead of 'grouper' and 'nakasig' instead of 'nakasi'... there will also be an additional baseband/radio component).
Code:
bootloader-grouper-4.23.img
flash-all.bat
flash-all.sh
flash-base.sh
image-nakasi-krt16s.zip (this, you do not unzip)
Copy these files into the same folder that contains your FASTBOOT.EXE (and ADB.EXE) files.
Shutdown the Nexus 7 completely. Boot it into the bootloader via VOL DOWN and hold, whilst holding, press POWER ON.
With the device booted into the bootloader, connect it to a USB port on your PC.
Open a command prompt window on the folder that contains the above mentioned files.
Type fastboot devices... if it returns a serial number, you have a working fastboot connection, and you can proceed to run the flash-all script. (.bat extension, if you're using Windows).
And that's it, really...
A couple of points though... when the bootloader is being flashed, BE CAREFUL not to nudge or disconnect the N7 from the PC. The Nexus 7 is at it's most vulnerable to being HARDBRICKED when flashing a bootloader. It's also a good idea to have a reasonable level of charge on the Nexus 7... no less than about 70% battery, I would recommend. Not good, if the device dies mid-bootloader flash!.
Sometimes, when 'system image' is being flashed, nothing seems to happen for quite a while. This has been reported many times here on XDA, and I've experienced it myself. If 'system image' hasn't gone over in 5 or 6 minutes, chances are your fastboot connection has died. If this is the case, disconnect from the PC, reboot the bootloader, (VOL BUTTONS to cycle to the RESTART BOOTLOADER option, POWER BUTTON to select)... reconnect to a DIFFERENT USB port on your PC... and start the flash procedure all over again with the flash-all.bat script.
Hope this helps... and good luck.
Rgrds,
Ged.

if all else fails
You can try nvflashhttp://forum.xda-developers.com/showthread.php?t=1927818

[Q] Slate 7 Extreme root,flash question

Hi, I am a happy owner of the HP Slate 7 Extreme which is basically the same device as you guys are using.I am still on the 4.2 Jelly bean since HP are not pushing over the air updates with our devices.I want to use the script from the development forum "[Script] [Utility] Nvidia Tegra Note 7 Kitkat Unlock BL, Restore, Recovery, & Root", I want to know if anyone has tried to use it with the Slate Extreme or if it simply should work on the Jelly Bean aswell. Thanks guys.

still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2

mofared said:
still have freeze/hang issue..
http://forum.xda-developers.com/showthread.php?t=2663449&page=2
Click to expand...
Click to collapse
What about the 4.3+ ?

crazyhacker202 said:
What about the 4.3+ ?
Click to expand...
Click to collapse
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later

mofared said:
i have not test that yet but i believe it should work because i have tested the 4.4.2 and 4.2.2 evga ROM from here using the cwm install from sdcard method..
http://forum.xda-developers.com/showthread.php?t=2627671
The only thing that puzzles me now is i am unable to perform a system recovery from HP update.zip using cwm.
http://h10025.www1.hp.com/ewfrf/wc/...en&cc=us&dlc=en&sw_lang=&product=6608632#N147
So right now i am stuck with 4.2.2 evga ROM all is good and functional.
I have read some post that by updating OTA fix issue in 4.4 but i have no idea on how to get the OTA update.
p/s: This is my first tablet and root attempt...
edit:
i found out that rootjunky has already released the 4.4.2 with 2.3 OTA i will give it a try and feedback later
Click to expand...
Click to collapse
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571

There was an individual who has received the 4.4.2 update from HP on his Slate Extreme over at the HP forums. I believe he stated he received 20 units donated directly from HP and was wondering why only 1 of them received the update. I believe the reason stated is that he most likely received a non-retail unit by accident. Not sure if he ever dumped the ROM or even knows how. I don't know either otherwise I'd try to contact him to get him to do so.

Re-write recovery partition?
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2

Belmichel said:
I did flash the modified update.zip but CWM doesn't give me the option to re-write the recovery partition. I go straight to "Install from sdcard complete". How is that re-write done?
*Update* All done - Had to select NO to questions on reboot (Replace recovery and root). Thanks so much - back to stock 4.2.2
Click to expand...
Click to collapse
See my HP Slate 7 Extreme Root post: http://forum.xda-developers.com/showthread.php?t=2850893

What am I supposed to open updater-script with?
---------- Post added at 03:47 AM ---------- Previous post was at 03:31 AM ----------
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
---------- Post added at 04:25 AM ---------- Previous post was at 03:47 AM ----------
I downloaded a script editor and deleted the first three lines of updater script but it still fails to flash.

Finally success!
Robo_Leader said:
First, nope, you'll still get freezing. I've tried all the ROMs.
Second, If you want to go back to HP's recovery, do the following:
Create a copy of update.zip and navigate to META-INF\com\google\android and open up updater-script
Delete the first three lines.
Transfer your new update.zip to your device and flash. Allow it to re-write the recovery partition.
NOTE THAT YOUR DEVICE WILL NOT ADVANCE PAST THE BOOT ANIMATION. THIS IS NORMAL.
Copy the original update.zip to a SD card and insert it into the device.
Now go to the HP recovery partition that now exists on your device and follow HP's restore instructions.
You're done, the stock 4.2.2 that came with your device is now installed.
Had to figure this out the hard way after I lost my original backup.
To the original poster, you can get it to work, but you need to make modifications to the script's fastboot commands (they will require "fastboot -i 0x03F0" before they will do anything) and you will need to setup your machine for ADB with the Slate 7 Extreme. It won't work out of the box, you can find support for that here: http://h30434.www3.hp.com/t5/Android-Tablets-e-g-HP-Slate-7/ADB-drivers/td-p/2574571
Click to expand...
Click to collapse
I have the 4450 extreme and one the things that was a little different- is that I had put the update zip on the sd card prior and it did the update on its own... WEIRD but acceptable! rooted and on 4.4.2- thanks man!

I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot (previously this): This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk (Previously this): The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip (previously this): A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt (previously this): A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.

It Worked! But...
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
I was able to unlock my bootloader using the above method and it worked. My s7e rebooted and everything was working normally. I loaded the bootloader again to go in and do a cache wipe and my 3 year old bumped into me as I was holding down the volume+ and power buttons. Now I'm stuck in ADX mode (black screen but recognized by my pc, have tried connecting to charger, volume+ and power, volume - and power, nothing works) . I've read that Advent has released adx files for the Vega Note 7 and you can use Tegra Note 7 Super Tools to restore the Nvidia Note 7. I'm wondering if I can use the update.zip file and the nvflash files from Nvidia to restore my tablet from ADX mode.
Any suggestions?

Mike-S, Thanks for the in depth how-to. I tried to sell my Extreme 4450 and the guy that I sold it to said when he received it was in boot loop. I got it back and it is indeed the one I sent him, however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling. I almost seems like the recovery was wiped... I can get to uploading from SD and have tried using your info to accomplish with no success. Any suggestions? I hate to smash it or try and sell if I can fix it.
Thank you in advance for anyone's help

som1special2 said:
however, now I have a bricked tab that doesn't even allow fastboot. I have, like others tried calling HP, tried installing per you instruction and finally considered just throwing away or selling.
Click to expand...
Click to collapse
Damn, I'm sorry to say that I'm unsure if i'll be able to help much or at all. All i can suggest is look and see if there is any pre-boot subsystem that connects to your pc via usb, similar to the mediatek "preboot mt65xx" which can sort of provide a last gasp chance of recovery.

help with ROM
Hi there,
Need desperate help. I followed the instructions here but ended up with no OS in the s7e. I kept on trying to install a signed ROM via ADB, it reaches 100% senidng but always failed inside TWRP. Not succesful even with CWM. I even tried installing from SD card but no success. Please help, thank you.

Anyone still around here?
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ

MGrad92 said:
Mike S ... not sure you (or anyone else) is paying any attention to this thread anymore (and the HP Slate 7 Extreme at this point is a fairly old device) ... but I can't get any of these methods to work and my S7E (model 4450) is basically useless right now. When cold (i.e. not booted up in prior 30mins or so), I can boot it normally, but within about 10mins, it will "crash" to the all-white HP splash screen and will never recover. Holding the power button just has it go through initial startup, get to the white HP splash screen, and sit there until the battery runs down. I haven't been able to root it yet, so the bootloader still shows "locked". What's ironic is that this device is really all I need -- I don't play high-end games and mostly just stream shows -- but now it's completely unusable. I'm not sure which is easier ... trying to get this to root or just buying something else?
So far, to root, I've tried towelroot and Cydia Impactor, but both of those returned errors as others have reported. I tried following the steps that Mike S put up here, but without my tablet being rooted, adb and fastboot don't even detect my device from the PC (though the PC detects it because I'm able to see it in Windows Explorer and drag files to the storage) ... so it seems like I can't even get to install CWM or anything further.
Maybe the right thing to do is just to dump the paperweight ... it used to work so well but about 6 months ago this stupid HP white screen crash started happening, and since then it's become a regular thing that only takes about 10 mins (at most) before it craps out. I can get to the bootloader and onboard recovery mode, but that doesn't let me load anything.
Not sure where to go next but any advice would be appreciated!
--AJ
Click to expand...
Click to collapse
Get your device drivers right (try androidsdk if it's still not getting recognised) and fastboot the stock system images (fastboot is not root dependent). By the way why were you trying those weird rooting methods ??? Just flash supersu from cwm/twrp and be done with it.

Thanks ... I'll try androidsdk. I actually am a root n00b and so I was trying to figure out the simplest way to go. I guess I guessed wrong! But of course before I can get that working I need the right drivers ... So I'll try that first. I was thinking the drivers were OK since my PC recognized the S7E when Android loaded (before it crashed to the white screen).

Couldn't get androidsdk to work
Hello again... I never could get androidsdk to work. My computer never recognized the tablet to be able to fastboot. *sigh* As much as I hate to give up, I don't know what else to do.... I might try another PC?

Looking for update.zip for S7E
mike-s said:
I didn't have any luck doing it this way. I ended up getting there by a slightly different avenue.
My s7e was totally non functional beyong fastboot and recovery mode being operational. I ended up downloading tegratools 2.2. Using the fastboot included in that I unlocked my boot loader with fastboot by the command
Code:
fastboot -i 0x03F0 oem unlock
(The '-i 0x03F0' is a code relating to the specific model, apparently without this the tablet will ignore your command. Please also remember that the unlock factory resets the tablet.)
It may be overboard again, but I also formatted all the system partitions
Code:
fastboot -i 0x03F0 erase boot
fastboot -i 0x03F0 erase system
fastboot -i 0x03F0 erase userdata
fastboot -i 0x03F0 erase cache
fastboot -i 0x03F0 erase preinstall
fastboot -i 0x03F0 reboot
I uploaded cwm recovery from the above version of tegratools to my s7e as it seems a bit more forgiving with signatures than the stock recovery. I used that to upload a version of update.zip with the "assert" lines removed from META-INF\com\google\android\updater-script. I also self signed the .zip to reduce the likelyhood of my upload being rejected by the tablet, it may not be needed, but I did it anyway.
Code:
adb sideload slate7update-signed.zip
when completing the firmware flash, apparently there is a common problem of the kernel not flashing correctly when recovery takes place and giving an "Error 7", this is the problem I think you solved by re-writing the unmodified firmware (but that didn't work for me)
Anyway I had to fix it by dropping back to fastboot and flashing it to "staging", which puts the kernel in a placeholder until the next boot, at which point the kernel will be written to the correct spot. Because of this writing to the correct partition, you will notice a quick double-boot as the updated kernel is written to the correct point in firmware.
Code:
fastboot -i 0x03F0 flash staging "c:\fastboot-s7e\blob"
I hope this helps.
Oh and to those curious, the beats version appears incompatible with the standard s7e, I tried modifying a rom in the same way as above and it just went to a blank screen. My guess is they've done some form of sanity check in the kernel, given that every "beats" version I've read about in tablets has been a software-only modification. I've not bothered trying to use the beats version rom with the s7e kernel, I'll leave that for someone else to try in greater depth as I'm just happy that I got everything working again.
references:
Fastboot: This is a copy of the twrp/cwm roms as well as fastboot & adb taken from tegratools 2.2 mentioned above.
SignApk: The java files and self signing certificate I used to sign the .zip file. It was actually a bit of a pain to find a working signapk.jar that had the valid certificates included, most were broken in one way or another when trying to sign on ubuntu 12.04.
slate7update-signed.zip: A signed copy of update.zip with META-INF\com\google\android\updater-script modified to remove the assert validation lines sanity checks, be careful with this, you could nuke your tablet if you use it on an incompatible bit of hardware.
guide.txt: A full how-to with a number of things I've omitted from this response.
To those wondering, I collated the above procedure from a dozen different links on a good four or five websites, including a number of threads here on XDA. Thank you to anyone out there that contributed to the information I found, you really made my day so much better in being able to recover my tablet.
Click to expand...
Click to collapse
Hey Mike, you wouldn't still happen to have that signed update.zip since you've don't have it on Dropbox anymore?

[GUIDE] Downgrade stock 6.3.3 to rootable 6.3.2

1. Download stock firmware 6.3.2 (latest KFU will get it for you)
2. Copy stock firmware to internal storage on Kindle Fire (boot up Kindle Fire and plug into your computer)
3. Download TWRP 2.2.2.1 from here. (thanks sd_shadow).
4. Download latest FFF using KFU
5. Put TWRP and FFF into a folder on your computer that contains fastboot.exe
6. Make a factory cable (google "make Motorola factory usb cable") or you can buy a premade one or an adapter. Here's an example.
7. Turn off your Kindle fire and unplug it from your computer.
8. Plug one end or your factory cable into your computer.
9. Open a windows command prompt from the folder with fastboot.exe in it.
10. While the Kindle Fire is turned off, plug in the other end of your factory cable into the Kindle fire. This should throw the KF into fastboot mode.
If you have created the factory cable correctly you should see the red Kindle screen but it should stay there and you should get a new driver install notification in Windows. Install the driver for the Kindle Fire bootloader.
11. From your Windows command prompt run these commands (substituting the names for whatever your TWRP and FFF files are called)
Code:
fastboot -i 0x1949 flash recovery twrp.img
fastboot -i 0x1949 flash bootloader fff.bin
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Now you should see the FireFireFire blue screen and you can push the power button to boot into TWRP. From TWRP you can wipe everything and install the 6.3.2 file you placed on the Kindle Fire earlier (if you want to flash a KitKat ROM like CM11 or others then you must re flash recovery with latest TWRP from here). After you are using 6.3.2 you can run latest KFU and it will work just fine.

A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip

sd_shadow said:
A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip
Click to expand...
Click to collapse
All really great points. I guess the purpose of the guide really comes down to showing you how to get into fastboot mode on stock firmware 6.3.3 because every software option that I tried to get into fastboot didn't work. They worked on 6.3.2 but gave write errors on 6.3.3. Only factory USB cable worked on 6.3.3
After that you're just best to go to a custom ROM to avoid all the auto-updating that you mentioned.

or my prerooted 6.3.3 zip
Sent from my DROIDX using Tapatalk

Blocking Updates On The Kindle Fire
Blocking updates on the Kindle fire is easily done once the device is rooted. Just download an Android Firewall App for the Kindle Fire. I used the DroidWall App as it was a Free Download. once installed, the DroidWall App has two methods of blocking connections to the net, White Wall and Black Wall. With the white wall you check the ones that you want to allow. With the Black Wall you check the ones you want to block. Two ways to the same result. I used the White Wall, fewer checks to block what you want and allow what you want to allow. I just went through the White Wall and checked the ones that I though needed to be allowed and it worked like a charm the first try. When checking blocks on the White Wall, make sure to not leave the pertinet block white to allow the blocking of all Apps. If you blocked the Netflix app, for instance, you could not watch any movies on Netflix. And believe me, when you have headphones or ear buds plugged into the audio jack, you could not find a nicer way to view movies without disturbing any one else. The only thing, to view netflex you have to have WiFi available.
Grampo
sd_shadow said:
A couple of points.
If you downgrade from 6.3.3 to 6.3.2 once you connect to wifi kindle will just download 6.3.3 update again, reinstall, and you will be right back where you started, or update will fail, and it will just reboot once an hour trying to install update. So I suggest if you want a rooted Kindle do not use a stock rom till a root method for 6.3.3. is found., or a way to stop updates.
The first time use install twrp with KFU, it will download latest, and install it, KFU will not check for updates to TWRP, it will just use the version in the recovery folder.
Once you have TWRP and FireFireFire bootloader installed, you have several options to update/downgrade TWRP... Flashify app (in rom), Fastboot.exe (in bootloader mode), Zip versions (install TWRP in TWRP).
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Fastboot.exe Files
There are a few options for getting Fastboot.exe, if you downloaded KFU you already have it, look in Kindle Fire Utility v0.9.9/tools folder, install SDK, or download adb-fastboot.zip
Click to expand...
Click to collapse

Before I invest in a "factory cable" ...
It would appear that following these 11 steps is my only option to go forward to modify/gain root access on my 6.3.3 Kindle 1st Gen.
Do you think this can be successful even though I kept getting a "ADB Status: Online / Boot status: Unknown" error while attempting to use KFU 0.9.9?
On my Windows 7 Desktop PC, First time plugged in - Device Manager shows up as "Other devices - Kindle with a yellow exclamation point and "Portable devices G:\"
After running KFU 0.9.9 "install_drivers.bat" - It shows as "Android Phone - Android ADB Interface" And "portable Devices" Disappears

[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
and
Flashing FFF and TWRP without Fastboot Cable
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
Lunarino said:
It would appear that following these 11 steps is my only option to go forward to modify/gain root access on my 6.3.3 Kindle 1st Gen.
Click to expand...
Click to collapse
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Do you think this can be successful even though I kept getting a "ADB Status: Online / Boot status: Unknown" error while attempting to use KFU 0.9.9?
Click to expand...
Click to collapse
don't use KFU to root or flash FFF/TWRP see [6.3.3] Flashing FFF and TWRP without Fastboot Cable
On my Windows 7 Desktop PC, First time plugged in - Device Manager shows up as "Other devices - Kindle with a yellow exclamation point and "Portable devices G:\"
Click to expand...
Click to collapse
drivers were incorrect
After running KFU 0.9.9 "install_drivers.bat" - It shows as "Android Phone - Android ADB Interface" And "portable Devices" Disappears
Click to expand...
Click to collapse
That is correct

Everything worked fine until I tried "Flashing FFF and TWRP without Fastboot Cable"
sd_shadow said:
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
and
Flashing FFF and TWRP without Fastboot Cable
---------- Post added at 10:19 AM ---------- Previous post was at 10:10 AM ----------
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
don't use KFU to root or flash FFF/TWRP see [6.3.3] Flashing FFF and TWRP without Fastboot Cable
drivers were incorrect
That is correct
Click to expand...
Click to collapse
Howdy I was very happy to have had excellent success with the preceding steps. Thanks again!
I then went on to the next step - http://forum.xda-developers.com/showpost.php?p=54124313
Or actually following along with the video - https://www.youtube.com/watch?v=OJwF26qlAyc (At about 5:44 of 8:59 still on pause on our older pc)
All went well until I attempted "fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img"
The command window reported "waiting for device"
I waited and waited then decided to take the dog for a walk while it did it's thing. That's when my daughter came home and restarted windows on me to log into her profile AND disconnected the KF and plugged it back into the wall charger!
Now win 7 device manager reports it as "Other Devices - Kindle" again and the KF screen just says Kindle in white and fire in orange static. Is that an indicator that it's stuck in Fastboot mode?
I told her that she just may have destroyed her KF making it a brick. Do we have any options to continue, restart or abort this operation?

Lunarino said:
Howdy I was very happy to have had excellent success with the preceding steps. Thanks again!
I then went on to the next step - http://forum.xda-developers.com/showpost.php?p=54124313
Or actually following along with the video - https://www.youtube.com/watch?v=OJwF26qlAyc (At about 5:44 of 8:59 still on pause on our older pc)
All went well until I attempted "fastboot -i 0x1949 flash recovery openrecovery-twrp-2.2.2.1-blaze.img"
The command window reported "waiting for device"
I waited and waited then decided to take the dog for a walk while it did it's thing. That's when my daughter came home and restarted windows on me to log into her profile AND disconnected the KF and plugged it back into the wall charger!
Now win 7 device manager reports it as "Other Devices - Kindle" again and the KF screen just says Kindle in white and fire in orange static. Is that an indicator that it's stuck in Fastboot mode?
I told her that she just may have destroyed her KF making it a brick. Do we have any options to continue, restart or abort this operation?
Click to expand...
Click to collapse
if there is no animation, then it should be in fastboot mode.
may need to reinstall drivers.

Kindle Fire Stuck in Fastboot Mode
sd_shadow said:
if there is no animation, then it should be in fastboot mode.
may need to reinstall drivers.
Click to expand...
Click to collapse
I have been able to fix the windows device drivers so that it shows up properly again.
I am unsure where to proceed from here now. Any guidance is appreciated.

Lunarino said:
I have been able to fix the windows device drivers so that it shows up properly again.
I am unsure where to proceed from here now. Any guidance is appreciated.
Click to expand...
Click to collapse
In command prompt
Fastboot devices
Should get something like 123456789
If yes retry the
Fastboot flash twrp command from before

Success!
We are all most fortunate to have such patient, knowledgeable and generous contributors in this wonderful community such as yourself!
:good:​Now she's got me searching for that list of compatible flash Roms here ... FUN-FUN-FUN
Is there a particular thread that someone may point us to please?

Tip: Don't use edit to add info, just quick reply, edits don't sent out notifications.
---------- Post added at 03:57 PM ---------- Previous post was at 03:56 PM ----------
[INDEX] Kindle Fire Development *REVISED*
---------- Post added at 03:58 PM ---------- Previous post was at 03:57 PM ----------
and quick replies just get added on, if no one else has posted

Root Kindle 6.3.4
Hi all,
is it possible to downgrade to 6.3.2 if the Kindle was upgraded to 6.3.4?
Thanks

sergio.afiliado said:
Hi all,
is it possible to downgrade to 6.3.2 if the Kindle was upgraded to 6.3.4?
Thanks
Click to expand...
Click to collapse
yes, any version of firmware can be installed at any time
Sent from my XT1254 using XDA Labs

[GUIDE] [6.3.3] 1st Gen Kindle Drivers, Rooting, Bootloaders & Recovery, and OtterX

[GUIDE] [6.3.3] 1st Gen Kindle Drivers, Rooting, Bootloaders & Recovery, and OtterX
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!

We need a new update for 2016
ajwgeek said:
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!
Click to expand...
Click to collapse
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you

ataraxioss said:
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you
Click to expand...
Click to collapse
no, this still works with 6.3.4
Sent from my KFFOWI using Tapatalk
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
there is one link to goo.im which is down
With the Fall of Goo.im I will be posting Mirrors OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my KFFOWI using Tapatalk

I've just tried it
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.

ataraxioss said:
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.
Click to expand...
Click to collapse
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk

reply
sd_shadow said:
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.

ataraxioss said:
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.
Click to expand...
Click to collapse
Factory reset doesn't unroot, just reinstall supersu app
Sent from my XT1060 using Tapatalk

So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
Click to expand...
Click to collapse
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.

thealy1234 said:
So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.
Click to expand...
Click to collapse
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs

sd_shadow said:
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs
Click to expand...
Click to collapse
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks

thealy1234 said:
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk

sd_shadow said:
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.

thealy1234 said:
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.
Click to expand...
Click to collapse
try OtterX bootloader and OtterX twrp from my post
OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my XT1060 using Tapatalk

The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...

thealy1234 said:
The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...
Click to expand...
Click to collapse
mount data is ify with OtterX, try adb push with OtterX twrp 2.7.1.0
---------- Post added at 01:11 AM ---------- Previous post was at 01:10 AM ----------
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...

After your help + plenty of head scratching I finally managed to install everything 100%.
Biggest hangup was before I realized this process wouldn't work on a USB 3.0 port....

I'm having an issue with being able to actually install drivers on my computer with Windows 10. I attempted to follow the guide but I am getting denied on an error with "bcdedit -set TESTSINGING ON".
"An error has occurred setting the element data. The value is protected by Secure Boot policy and cannot be modified or deleted."
Any advice for a workaround on installing the drivers?