Hi guys I'm new here but not to rooting Android devices and such. I had a XDA account back in the Windows Mobile 6.5 days but I have no clue what happened to it so I just made a totally new account. I have searched for this issue top to bottom and I cannot find a solution.
So for about 3 weeks now I've been having this problem with the Kindle Fire I got for christmas. It's not bricked, but I tried to switch to the AOSP stock JellyBean 4.2.2_r1 ROM from CM10.1/SGT7 version9. When I did this the kindle seemed to booted up fine, and when the setup process was done I had no Navigation Bar or a Status Bar, also causing the installer to malfunction and give an infinite installing screen (forcing me to reboot due to there being no Navigation Bar.). I thought to myself "OK I'll just reinstall CM10 and everything will be normal." Nah. The same problem was experienced when I finished the setup after reinstalling CM10. So I tried flashing an earlier version of CM10. No dice.
When I switched ROMs I made sure I wiped everything from System to Devlik. Still having the same problem. I have twrp 2.3.3.0 atm and I noticed that when I boot into twrp, off deck it says "E:Unknown File System: 'datamedia' " in the log. I also noticed that when ever I format something it says "Using rm -rf on......" So I decided to go and disable this as it might be why I'm having such issues. I went to settings and tried to disable this option but it wont let me disable it (as in it wont let me deselect the "Use rm- rf instead of formating?" option.).
When this happened I decided to look for an update for twrp to fix this issue. When I found the update to 2.4.4.0, it's only apparently able to be installed via fastboot. I as of now do not have a fastboot cable, nor can I make one. I would buy one, but money is a bit short. This also brings me to my next issue that I have searched to no end for.
No matter what drivers I install for my kindle Fire, my computer asks to install new hardware when I plug my kindle in. This is just for USB mounting. I haven't even tried ADB drivers yet. I can't mount USB storage in android or twrp. Twrp says "E:Unable to locate volume information for USB storage mode." When I am able to finally get some good drivers installed and working, only 30 seconds pass before they stop working and I'm not able to do anything. This forces me to transfer all files in ES file explorer over Wifi (which has to be installed manually by downloading the apk and copying it to the system/app folder and rebooting.).
After all this occurred I decided to go back to the stock Amazon OS and unroot to start from dirt. I went to Amazon's website and downloaded the 10.3.1 update for Kindle Fire second gen. It downloaded in .bin format so I just renamed the file update.zip and copied it to the root of the SDcard. After all that I booted into twrp and tried to install the ROM and it gave me this:
Installing '/sdcard/update.zip'
Checking for MD5 file......
Skipping MD5 check: no MD5 file found.
assert failed: is_substring("Otter2", file_getstring("/proc.product_name"))
E:Error in /sdcard/update.zip
(Status 7)
Error flashing zip 'sdcard/update.zip'
Udating partition details...
Once this happened I promptly searched the error on google. There was nothing exactly pertaining to this issue, so I searched the error in general and found that it happens a lot with ICS roms. They were all however errors that dealt with the system name being wrong but that's not exactly my problem is it? I even tried modifying the Update-script but that only gave me an infinite blue kindle logo screen.
If anyone can help me it would be greatly appreciated. This is my first run with any kind of tablet. I would like know how I can restore it back to the stock Amazon OS. If so how, I feel like I have tried everything.
Do you have a fastboot cable? First, I recommend that you get one.
Then, your best bet is to completely restore from stock and start over using the kindle fire restore utility in the development section.
Read my last post especially
http://forum.xda-developers.com/showthread.php?t=2035047
The update.zip isn't going to flash for you because of the asserts set in the updater script. Basically, once you flashed cyanogen your device no longer identified itself the same way.
The problem you have with formatting isn't a bug. You would be screwed if TWRP let you uncheck the box.
The E: thing is normal and not an issue..
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Do you have a fastboot cable? First, I recommend that you get one.
Then, your best bet is to completely restore from stock and start over using the kindle fire restore utility in the development section.
Read my last post especially
http://forum.xda-developers.com/showthread.php?t=2035047
The update.zip isn't going to flash for you because of the asserts set in the updater script. Basically, once you flashed cyanogen your device no longer identified itself the same way.
The problem you have with formatting isn't a bug. You would be screwed if TWRP let you uncheck the box.
The E: thing is normal and not an issue..
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Alright so I need a fastboot cable, and to restore to factory settings. I'm guessing TWRP would be gone when I do this right? Also Thank you. I think I'm going to stick to Amazon's OS for a while untill I can figure out the drivers.
Yes. Twrp will be gone.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I think the fact that CM10 changes the device name is the reason why I have so many driver problems. So I'm going to stick to Stock Amazon untill CM10 is on it's final release. Is there any way to change the device name back to the original? The only difference is a space between the names is Amazon Kindle Fire 2 and Amazon Kindle Fire2(on CM10).
The device name change doesn't effect the drivers. That only effects the update script. Once you are stock the device name will revert back
Make sure you have uninstalled all previous drivers for the kf.
Then make sure you used the drivers I suggest at the end of that thread.
99% of all the issues I see for this device are just driver problems.
--
Sent from my mind to your screen.
Are you sure that it doesn't? Because as soon as I installed CM10 all my drivers were suddenly incompatible.
Dwarphkin said:
Are you sure that it doesn't? Because as soon as I installed CM10 all my drivers were suddenly incompatible.
Click to expand...
Click to collapse
So you are probably using the Google device drivers from another phone or windows update or such. Cm10 drivers seem to work out of the box, but of you want both to work use my method.
The name change isn't what effects the drivers, it's the operating system that effects the drivers needed
When I first set up my system I couldn't access the devices USB Mount on stock but cm was OK. I went back and followed my own instructions... Now adb, fast boot and USB mounting works from both oses
--
Sent from my mind to your screen.
Related
I just got a refurb Kindle. I'm told it's 1st Gen, I believe it was SW version 6.3.2
I installed FFF and TWRP 2.5.0.0 and downloaded a couple CM-10.1-x ROMs.
Booted to TWRP. Stupidly, didn't take a backup. Installed the ROM. First it installs the ZIP. Then:
"Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Updating partition details..."
And then I have my Wipe Cache/Davilk, Home, and Reboot System options.
After selecting Reboot (or Wipe Cache/Davilk then reboot), I get the offset CGM boot animation... it just sits there forever.
I've tried a couple CM 10.1-x ROMs with no better success. I've also tried using the factory wipe option in TWRP before installing.
Any ideas out there? I can easily get into the TWRP interface again but haven't been able to fix this tablet.
someone else will have come along and make sure that what I say is true, but I think you need to turn off the "check for md5" when you flash it. first off, though, you need to wipe everything but your external storage or sd card, and also you need a Gapps package to install after the ROM.
sent from The Muffinator (it's a kindle fire running cm10.1)
using Tapatalk 4 beta, and loving it!
It doesn't sound like bayou wiped anything? Wipe /system /data and delvikcache like the above post says
Deleted. (Wrong thread)
Thanks guys, it worked now.
Although I had been wiping those categories with the exception of my first attempt, I think the first thing I'd done after reading online was enable a different formatting option under "settings" in TWRP. I think that was causing a problem, despite what I'd read online.
So to clarify: the procedure that worked for me is to keep that option UNCHECKED and do the wipes before the install. Thanks for the help.
Yet another case of someone who read the wrong instructions or failed to follow properly!
I've successfully rooted my Kindle Fire HD 8.9" and installed TWRP. I then put the zip file provided by Hashcode onto my device, wiped my cache and dalvik cache, and proceeded to install the new ROM.
After a successful install, I rebooted. It optimizes 65 installed apps, and then reboots again. An hour later the Cyanogen Mod logo is still spinning. I figured that was long enough to assume something went wrong. I powered down, went into TWRP and tried to mount storage so I could replace the Cm10.1 file with my backup files to go back to Stock. I'm receiving the following error when trying to mount storage though:
Code:
E:Unable to locate volume information for USB storage mode.
So I attempted using ADB Sideload, but at no point have I managed to get my Kindle recognized by the ADB server. I appear to be in some hell where my device still "works," but I have no way to put anything on it to fix it.
My last option appears to be fastboot. I am able to get into fastboot mode on the Kindle, though I don't know what to do with it. I'm familiar with all the other steps from my original Kindle Fire, but I never got this deep into it. Wanted to see if someone could give me some direction before I really break this thing.
Update: Alright, so between the FAQ (Item 11) and Hashcode's instructions on restoring backups I've managed to get my Kindle back to stock. I panicked and posted prematurely, so sorry for crapping up the forum. Shout outs to Hashcode and Soupmagnet for their posts.
Ok, so I'm very new to rooting, Custom Firmware, all of it. I decided to try to root my Kindle Fire. I got CyanogenMod on it, but now it won't connect to the computer. I want to get it back to the normal Kindle Fire OS. Please Help!
ActorfromMI said:
Ok, so I'm very new to rooting, Custom Firmware, all of it. I decided to try to root my Kindle Fire. I got CyanogenMod on it, but now it won't connect to the computer. I want to get it back to the normal Kindle Fire OS. Please Help!
Click to expand...
Click to collapse
Hello there! First a warning, this method will remove root access FFF and TWRP (Everything) so if you don't want that, this is not the method for you.
First you want to download the stock kindle rom http://www.amazon.com/gp/help/customer/display.html/ref=hp_navbox_kspot_fireupdate?nodeId=200790620
And then just follow the steps on this post from another XDA member - http://forum.xda-developers.com/showthread.php?t=1399072
And you should be good
EDIT - Wait do you mean you can't connect to computer with a usb, or internet or what?
JakeReis said:
Hello there! First a warning, this method will remove root access FFF and TWRP (Everything) so if you don't want that, this is not the method for you.
First you want to download the stock kindle rom http://www.amazon.com/gp/help/customer/display.html/ref=hp_navbox_kspot_fireupdate?nodeId=200790620
And then just follow the steps on this post from another XDA member - http://forum.xda-developers.com/showthread.php?t=1399072
And you should be good
EDIT - Wait do you mean you can't connect to computer with a usb, or internet or what?
Click to expand...
Click to collapse
I cannot connect my kindle to the computer via usb. I tried downloading the stock rom to the kindle itself, and TWRP cant find it.
ActorfromMI said:
I cannot connect my kindle to the computer via usb. I tried downloading the stock rom to the kindle itself, and TWRP cant find it.
Click to expand...
Click to collapse
Ok thanks. Just to clarify, roms should be still zipped (so file extension should be .zip) and placed in the main SD card directory. So if your browser is downloading it to another place you should probably move it.
JakeReis said:
Ok thanks. Just to clarify, roms should be still zipped (so file extension should be .zip) and placed in the main SD card directory. So if your browser is downloading it to another place you should probably move it.
Click to expand...
Click to collapse
so how do i do this from the kindle alone?
ActorfromMI said:
so how do i do this from the kindle alone?
Click to expand...
Click to collapse
Step 1) Download ROM from link provided.
Step 2) Download a file manager like ES file Manager, although if you are on CM you should have one already.
Step 3) Use the File Manager to move the file from download to your root of the sdcard, which is /storage/sdcard/
Step 4) Make sure its zip file. Sometimes you may download a bin file, and it won't work. Rename to .zip if its a .bin
Step 5) Go to TWRP and first wipe System, Data, Dalvik and Cache ONLY. Install the the zip file.
Step 6) Reboot
It may take 1-3 Minutes before you enter the Original OS, please note that you WILL LOSE ROOT, FFF, TWRP.
Sent from my Amazon Kindle Fire using Tapatalk 4
404-Not Found said:
Step 1) Download ROM from link provided.
Step 2) Download a file manager like ES file Manager, although if you are on CM you should have one already.
Step 3) Use the File Manager to move the file from download to your root of the sdcard, which is /storage/sdcard/
Step 4) Make sure its zip file. Sometimes you may download a bin file, and it won't work. Rename to .zip if its a .bin
Step 5) Go to TWRP and first wipe System, Data, Dalvik and Cache ONLY. Install the the zip file.
Step 6) Reboot
It may take 1-3 Minutes before you enter the Original OS, please note that you WILL LOSE ROOT, FFF, TWRP.
Sent from my Amazon Kindle Fire using Tapatalk 4
Click to expand...
Click to collapse
I followed every step, and when i tried to install, I received this dialog:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" l l
E: unknown command [err_string]
getprop("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Error flashing zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Updating partition details
I then went to Reboot System, and it said:
No OS Installed! Are you
sure you wish to reboot?
There was no other option, so I had to. Now, I dont even have CyanogenMod. I let it sit on Booting... for 15 minutes and nothing.
ActorfromMI said:
I followed every step, and when i tried to install, I received this dialog:
Skipping MD5 check: no MD5 file found.
assert failed: getprop("ro.product.device") == "blaze" l l
E: unknown command [err_string]
getprop("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Error flashing zip '/sdcard/update-kindle-6.3.2_D01E_4110520.zip'
Updating partition details
I then went to Reboot System, and it said:
No OS Installed! Are you
sure you wish to reboot?
There was no other option, so I had to. Now, I dont even have CyanogenMod. I let it sit on Booting... for 15 minutes and nothing.
Click to expand...
Click to collapse
Well, here is a thread I found that mentions the error (about 3/4's of the way down the page), and a potential fix someone had. Unfortunately it requires you to be able to connect your kindle to the computer to use kindle fire utility to work. Will it connect to kindle fire utility, or is that not working either?
http://androidforums.com/kindle-fir...474455-restore-kindle-fire-out-box-state.html
JakeReis said:
Well, here is a thread I found that mentions the error (about 3/4's of the way down the page), and a potential fix someone had. Unfortunately it requires you to be able to connect your kindle to the computer to use kindle fire utility to work. Will it connect to kindle fire utility, or is that not working either?
Click to expand...
Click to collapse
When I try to connect to the kindle fire utility, it says offline.
ActorfromMI said:
When I try to connect to the kindle fire utility, it says offline.
Click to expand...
Click to collapse
I'm running out of ideas, but is it possible to reflash CM? If you can, then there is still another way. You could download another rom directly from your device (like glazed ics for example) flash it, and then you could connect it to a computer to continue. I just flashed glazed ics today and it connects to hte computer with my old cell phone cable, so it should work for you.
JakeReis said:
I'm running out of ideas, but is it possible to reflash CM? If you can, then there is still another way. You could download another rom directly from your device (like glazed ics for example) flash it, and then you could connect it to a computer to continue. I just flashed glazed ics today and it connects to hte computer with my old cell phone cable, so it should work for you.
Click to expand...
Click to collapse
CM is not working, after trying to install the stock ROM. All I can do now is get to TWRP.
I dont how if this will give any more help, but I just tried it again, and there was a page I forgot to say. After i go to reboot, and it gives me the warning about no OS installed, it then asks me if I want to install SuperSU, and it says my device doesn't appear to be rooted. I hope someone can give me a solution to this, it is beyond frustrating.
ActorfromMI said:
I dont how if this will give any more help, but I just tried it again, and there was a page I forgot to say. After i go to reboot, and it gives me the warning about no OS installed, it then asks me if I want to install SuperSU, and it says my device doesn't appear to be rooted. I hope someone can give me a solution to this, it is beyond frustrating.
Click to expand...
Click to collapse
anyone???
ActorfromMI said:
anyone???
Click to expand...
Click to collapse
There is a "Mount" function in TWRP. See if it will let you mount your sdcard to USB and transfer a ROM to it.
soupmagnet said:
There is a "Mount" function in TWRP. See if it will let you mount your sdcard to USB and transfer a ROM to it.
Click to expand...
Click to collapse
nope. nothing.
ActorfromMI said:
nope. nothing.
Click to expand...
Click to collapse
As annoying as it is, your communication problem may be due to the drivers not being installed correctly. You may want to check your device manager to see if everything is connected. Furthermore, if you have access to your current OS, you may want to check the Developer Options, and confirm that you have debugging enabled. Depending on the drivers you installed to get ADB working, it is entirely possible that you could be able to communicate with the device while booted normally, but not in recovery.
If nothing else, TWRP should have a command line tool where you can perform simple tasks like renaming files from within recovery, and without the need for an ADB connection. You might want to look into that to see if you can find the 'update.bin' that you downloaded to your device (likely located in your "Download" folder), and rename it to 'update.zip' so it will be visible to TWRP for flashing (that is, assuming you really want to revert to stock).
soupmagnet said:
As annoying as it is, your communication problem may be due to the drivers not being installed correctly. You may want to check your device manager to see if everything is connected. Furthermore, if you have access to your current OS, you may want to check the Developer Options, and confirm that you have debugging enabled. Depending on the drivers you installed to get ADB working, it is entirely possible that you could be able to communicate with the device while booted normally, but not in recovery.
If nothing else, TWRP should have a command line tool where you can perform simple tasks like renaming files from within recovery, and without the need for an ADB connection. You might want to look into that to see if you can find the 'update.bin' that you downloaded to your device (likely located in your "Download" folder), and rename it to 'update.zip' so it will be visible to TWRP for flashing (that is, assuming you really want to revert to stock).
Click to expand...
Click to collapse
It recognizes the update, it just won't work
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: http://kindle-fire-updates.s3.amazonaws.com/update-kindle-6.3_D01E_4019920.bin, and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Also having trouble taking my KF back to factory...
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
BriteLeaf said:
I am also having trouble taking my KF back to factory specs.
I am using TWRP recovery.
Wipes go just fine.
Install gives me this error...
Skipping MD5 check: no MD5 file found.
assert failed: getprop ("ro.product.device") == "blaze" ||
E:unknown command [err_string]
getprop("ro.build.product") == "blaze"
E:unknown command [err_string]
E:Error executing updater binary in zip '/sdcard/kindle/update.zip'
Error flashing zip '/sdcard/kindle/update.zip'
Updating partition details...
I am trying to go back to stock because I am now having TONS of trouble keeping files running without them crashing. Also, every time I try to read a book now, the Kindle app crashes before it ever really opens. I have tried uninstalling that app, then reinstalling even. No help at all.
Any help in this matter would be HUGELY APPRECIATED!!!!
Thanks,
me
Click to expand...
Click to collapse
Yes I am getting almost the exact same error. I would really like a solution to this.
Ethanzh said:
Yes I am getting almost the exact same error. I would really like a solution to this.
Click to expand...
Click to collapse
So would I. I am glad that I am not the only one.
I am guessing...
I am guessing either us 3 are the only ones with this problem, or just no one wants to, or knows how to fix this problem =(
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Ixthusdan said:
If a flash does not complete, it has to be a bad download. Get the file again and push it to the sdcard via twrp. But if you are having trouble, why flash factory? If it is some corruption, flash a rom. Kindle store and reader fail because of the app, generally. Notice my device says Nexus 7? That is how to fool the kindle apps on a fully functioning kindle fire.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have redownloaded the flash from Amazon at least five times, all with the same results.
As far as pushing it to the sdcard via twrp, I guess I for one don't know how to do that.
As to why I would want to go back to factory with it, I guess for me, it is what I prefer.
Thank you for answering though. I do appreciate it.
Same here, fixed!
Ethanzh said:
Hi.So I used to have Cyanogenmod installed on my rooted Kindle Fire, along with FFF and TWRP recovery. I was not satisfied with the performance of Cyangogenmod, so I wanted to install the Stock Amazon ROM back onto the Fire. First, I booted into TWRP, and erased everything with the 'wipe' option (might not have been a good idea). I have downloaded the Amazon ROM from here: , and renamed the file 'update.zip'. I mount the Fire, and drag over the update.zip, and then I go to 'install' in TWRP and select the update.zip, but after I start it, the install just fails, seconds after it's started. There are a couple errors, such as "Error executing updater binary in zip '/sdcard/update.zip'". I have ADB installed, and Kindle Fire Utility, which detects the device as 'online', boot status 4000. I have tried install COTR recovery with KFU, but it hangs at 'Activating Fastboot (4002)'. I would really appreciate any help with this, because it would really suck if it turns out that I bricked my Fire. Thanks!
Click to expand...
Click to collapse
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks, trying this now.
TWRP 2.2.2.1 Worked
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
Thanks for the tip. Worked like a champ.
mpeterso said:
I had the same problem. I ended up reverting back to TWRP 2.2.2.1, which can read the update.zip properly.
I downloaded the older version from techerrata dot com --> twrp2 -->blaze-->openrecovery-twrp-2.2.2.1-blaze.img
I then used my fastboot cable and ran fastboot -i 0x1949 boot openrecovery-twrp-2.2.2.1-blaze.img.
This allowed me to run the older twrp, clear out my /system, and get back to stock.
Click to expand...
Click to collapse
I just get stuck at < waiting for device > on my command prompt. Where am I supposed to open the cmd?
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Bump
Having the exact same issue when using KFU it just hangs there on activating fast boot
Cronus3166 said:
I just wanted to say, after several hours of searching through Google and messing with my Kindle, this thread finally helped me fix it.
My biggest issue was, I was unable to flash any thing, even the twrp. So what I had to do was this,
I googled the twrp 2.2.2.1 blaze img as mentioned here, then I renamed it to twrp.img and put it in the folder inside KFU -> Recovery
My other issue was with my Kindle being stuck at the Boot Logo saying, "Booting" and I noticed through trial and error, before the kindle goes to try to boot (When you can select Normal, Recovery, Reset Boot) that if I kept pressing the power button to cycle through the options, I could keep the Kindle in a Fastboot mode so I could use the KFU to install the TWRP 2.2.2.1
After that it was simple, booted into twrp, mounted the drive and stuck the Stock Rom from Amazon on there and installed it.
So I really just wanted to say thank you to this thread and hopefully I can contribute a small bit to someone if they have my issue.
Click to expand...
Click to collapse
This worked perfectly for me. Felt a little weird sitting there repeatedly pressing the power button as KFU searched for my device, but it worked. Thanks.
I have a Kindle Fire 2011 1st gen. I got TWRP on it and had a hell of a time trying to get a ROM flashed or anything like that. I did follow a write up on here how to root it, and it worked. But it was still kindle and just looked like android. So i tried to flash CM11.... I accidently deleted the partition with everything on it, and flashed CW11 but i used OtterX, and it wont boot. I have a fast boot cable, but I cant get the PC to recognize its plugged in so i can get anything on it and try to flash again. What can i do? How do i fix this?!? Please help me!!
It was still kindle and just looked like android? All you're doing when you flash a rom is putting standard android on it, so it should look like android. If the fast boot cable you're referring to is a custom order "factory" cable it won't let you transfer a rom, the point of the cable is for bad issues that won't let you boot back into recovery. I'm guessing you didn't delete the partition since you're wanting to copy a rom over, you just formatted it and erased the rom file, correct? Use a standard usb cable, micro b, that fits the kindle. Plug it in. Boot the kindle into recovery. Find the option in recovery to "mount usb" or "mount mass storage". This will show it on the pc as a mass storage device you can copy a rom to. If however you did the otterx conversion, in other words you didn't just try to install an otterx rom on standard recovery and partitions, then you won't have the option of using the usb mount. You will have to go through the adb push method, which I don't remember, but there are other topics on this forum that explain how to access the adb (android debug) and use the push command as well as others. Good luck and if you get it fixed be more careful next time. If you aren't familiar with how to do these processes you can easily brick your device. Read research and read again to be sure you have all the steps down!
I have been up for HOURS trying to fix it. I used a Kindle Utility Tool and rooted. It Installed some google apps after SU... At this point when using usb the Kindle would show up in "my computer" so i put cm11 on it. Tryed to flash it and it wouldnt work. I deleted something and now all the OS are gone. It says it. When j try to boot it stays stuck on the screen. I can pick to boot recovery but even when i abd push roms. Cm11 and stock kindle os it wont flasb then because of E: partitions not there.
I dont have any idea whats left to try. I really tried everything i could find.!! Now it dosent show up on "my computer" anymore... its like. Gone gone!!!!
I need to figure out a way to get it to work. I need to find out how to add partitions first i guess.... i got twrp and thats like it... i cant get a boot.img to flash. Nothing....
I need some serious help. I gotta fix this atleast back to amazon kindle os before they find out i broke it. Lol
robles4242 said:
I need to figure out a way to get it to work. I need to find out how to add partitions first i guess.... i got twrp and thats like it... i cant get a boot.img to flash. Nothing....
I need some serious help. I gotta fix this atleast back to amazon kindle os before they find out i broke it. Lol
Click to expand...
Click to collapse
Which twrp version?
Sent from my XT907 using Tapatalk