Related
My kindle fire bricked/wont boot and it gets stuck at the Kindle Fire logo with the letters. I downloaded the update and flashed it but it says
E:Cannot load volume/misc
E: error opening /sdcard/TWRP/BACKUPS/0000000000000000
E: Unable to stat '/sd-ext/.'
and cancels the installation...
It seems like I might have deleted some important files on accident when I had no clue what was going on, and ive also gone through many tutorials on how to fix this
I'm stuck and have no clue what to do, and if anyone could help I would greatly appreciate it
Could try...
Two things you could try. If you are still booting into TWRP, you could try mounting the USB/SD Card and then loading an image (like Barebones or whatever else works for you) and try again. Last time I got that same message, I didn't have the files unzipped to the root of the SD.
You could also try these instructions to take the Kindle back to stock and try again. Just make sure you have the correct update.zip on the Kindle. It will remove TWRP and take you back to stock, but then you can breathe easy and start again.
http://forum.xda-developers.com/showthread.php?t=1399072
Hope that helps.
So I was using these instructions from PC World to get ICS on my Fire...
it wont let me add the link but if you google "pc world kindle fire ice cream sandwich" I'm sure you will find it...
I have done everything to the point where it has you install FIREFIREFIRE from the Fire. When I hit the install and swipe it says
*Verifying Filesystems...
*Verifying paritition sizes...
...and then I get no success message. I found this recommendation from someone else who was having a similar problem:
figured out my issue, you have to change the bootmode to normal
•Navigate to the “tools” subfolder.
•Type the following commands, one at a time:
•fastboot oem idme bootmode 4000
•fastboot reboot
When I try to do this I get a message saying < waiting for device >
I am stuck. Can anybody help me out?
"fastboot reboot" doesn't work after you change bootmodes. Hold the power button until it shuts down.
The real problem is that I am not getting a success message when I try to install the FIREFIREFIRE zip. Any reason why I wouldnt get the success message?
[Edited:]Ignore
---------- Post added at 10:05 PM ---------- Previous post was at 10:02 PM ----------
Wait, don't do anything yet....
rwmoon said:
The real problem is that I am not getting a success message when I try to install the FIREFIREFIRE zip. Any reason why I wouldnt get the success message?
Click to expand...
Click to collapse
It doesn't give you the "success message" in the window where it outputs...
*Verifying Filesystems...
*Verifying paritition sizes...
The word "Successful!" will appear above the "Home" button. Look closely at the picture provided in the PCWorld article.
kinfauns said:
It doesn't give you the "success message" in the window where it outputs...
*Verifying Filesystems...
*Verifying paritition sizes...
The word "Successful!" will appear above the "Home" button. Look closely at the picture provided in the PCWorld article.
Click to expand...
Click to collapse
Yeah, I never have gotten the Successful! message. I am wondering if I should just move on and install the ROM or if that successful message is vital to continuing. Would like to not brick my fire if possible
btw these image verifcations to post are probably the hardest ones i've seen. have to refresh 7 or 8 times before I get one I can read.
You should download a new copy of FFF and push it to your sdcard to flash BEFORE you reboot. If for some reason the bootloader only halfway finished and you reboot, it will hard-brick your device.
Ignore everything I said prior to this.
---------- Post added at 10:14 PM ---------- Previous post was at 10:09 PM ----------
kinfauns said:
It doesn't give you the "success message" in the window where it outputs...
*Verifying Filesystems...
*Verifying paritition sizes...
The word "Successful!" will appear above the "Home" button. Look closely at the picture provided in the PCWorld article.
Click to expand...
Click to collapse
Thank you. I don't use the newer versions of TWRP so I had no idea. I just wanted to make sure he didn't screw everything up big time.
Well to be clear this is the step I am on:
Install a Custom Bootloader
You are well into the process now. Next, install the FIREFIREFIRE custom bootloader:
1. Take the FIREFIREFIRE Zip file and place it (still zipped) into c:\kfu\software. At this writing, the latest filename is called fff-u-boot_v1.4a.zip.
2. Copy FIREFIREFIRE into the Kindle Fire's /sdcard directory:
adb push C:\kfu\software\fff-u-boot_v1.4a.zip /sdcard/
3. On the Kindle Fire, press the Install button. Navigate to /sdcard if needed (you should already be there by default), and select fff-u-boot_v1.4a.zip.
4. Swipe to confirm. You should get a success message
I have actually already rebooted the device, the first time I didn't hit the power button and it booted right back to stock, the 2nd time I did hit the power button and booted into recovery. I just put the fire zip on my device a few minutes ago...should I push a new copy again?
I guess what I really need to know is if I don't get the message "Successful" on installing the custom bootloader should I go ahead and continue to try to install the ROM and Google Apps? Or do I have to get the successful message in order for the subsequent steps to work. Like I said, I have rebooted the device and everything still seems to be working. I guess I am not really sure what the bootloader does?
Thanks for the help guys.
rwmoon said:
Yeah, I never have gotten the Successful! message. I am wondering if I should just move on and install the ROM or if that successful message is vital to continuing. Would like to not brick my fire if possible
btw these image verifcations to post are probably the hardest ones i've seen. have to refresh 7 or 8 times before I get one I can read.
Click to expand...
Click to collapse
IMHO, I think you're probably OK.
That zip file contains the bootloader image and a corresponding SHA1 checksum. The script that flashes the image verifies that checksum to confirm that the file is consistent and has not been corrupted. If the checksum is inconsistent with the calculated value of the image, the flash will not proceed. In that case, it will have left the original bootloader in place.
If you want to be safe, follow soupmagnet's suggestion to re-download the FFF zip file and try it again. If I was in your shoes, I'd probably just go ahead and try rebooting it, but use the Reboot->Recovery option to make sure I get directly back into TWRP. If you see a blue/white kindle fire logo during that reboot, you've flashed FFF.
EDIT: If you see the bootlogo I mentioned above and it's able to get into the system software or recovery at will... you're fine. Just continue with the ICS instructions.
If you want to learn more about the Kindle Fire, what you are doing and why you are doing it, read this...
http://forum.xda-developers.com/showthread.php?t=1552547
LOL. Now when I try to push the ROM and Apps to the device it just says
error: device not found
Maybe it just wasn't meant to be tonight. Haha.
You have been really helpful. I appreciate it.
rwmoon said:
LOL. Now when I try to push the ROM and Apps to the device it just says
error: device not found
Maybe it just wasn't meant to be tonight. Haha.
You have been really helpful. I appreciate it.
Click to expand...
Click to collapse
You need to be booted into TWRP or the stock system software to be able to use adb push, but that's not the only way to copy the ROM over to the KF. You can mount the /sdcard with TWRP or even the stock system software and just copy it over from your computer. You can even just download it using the Silk browser... whatever it takes to just get the ROM zip file onto the KF. Then just boot back into recovery and install what you copied over.
Don't forget to download the appropriate GApps package and install that as well, so you can get access to Google Play. Read the instructions for the ROM you downloaded for information on what GApps package you need.
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.
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
Hello.
I have a KF 1st generation. I had rooted it some time back and then un-rooted it (thought I did?) and haven't had an issue. This week it started loading up and freezing on the Kindle Fire orange and white logo. I am able to boot it to Recovery which gives me Cannibal Open Touch screen and options. I did try a few of the options but still the same end result. After coming here and reading around I found a thread and I followed the directions since the original poster and I seemed to have the same issue. There are the steps I followed:
Step 1) Download MoDaCo Rom/Any other ROM BUT NOT ANY KITKAT ROM(COTR can NOT flash KitKat)
Step 2) Transfer your ROM while in recovery
Step 3) Do a preflash wipe
Step 4) Do a factory reset
Step 5) Go to 'Install -> Install from SD Card -> Folder where you put your ROM
Step 6) Click Install without Backup
Step 7) Boot Android
I downloaded [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire and made it to Step 5 using the 'Zip Flashing' option but I can't seem to flash or sideload or any of those options. While the Kindle is plugged into the computer I hear the noise and when I find my Kindle it has a Yellow Triangle with a !. I looked at the Kindle and it tells me I have no drivers and I am not able to drag and drop any files. Also, not sure if it matters but I am no longer using the computer used to root the Kindle.
the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk
sd_shadow said:
the rebooting is the new 6.3.3 update trying to install, but because you have custom bootloader/recovery install fails.
may need to install twrp recovery. but my prerooted 6.3.3 zip sbould install fine.
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:
Sunnywonder said:
@sd_shadow I appreciate the reply and the twrp file but can you lead me to the direction to getting them to the KF? I can plug the KF into the computer and it no longer gives me the triangle ! sign. I am unsure of the next step and don't wanna mess anything up with unnecessary stuff. Thank You again :good:
Click to expand...
Click to collapse
select mount option in twrp, then just copy to sdcard folder on pc
sd_shadow said:
select mount option in twrp, then just copy to sdcard folder on pc
Click to expand...
Click to collapse
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?
Sunnywonder said:
I have been trying to figure this out and searching but I can't seem to figure this out. I am uploading the screen I have on my KF and I don't know how to mount the file. I can't find a thread that will kind of walk me though it so if you know where I should go that would be great. I am uselessly pretty good with figuring things out so maybe I'm making this harder than it looks?
Click to expand...
Click to collapse
Can't remember if Cannibal Open Touch has mount options
may need to
Download a twrp.img from http://techerrata.com/browse/twrp2/blaze,
latest (24 June 2014) is openrecovery-twrp-2.7.1.0-otter.img
verify md5 check sum
Download ADB/Fastboot.exe Files from adb-fastboot.zip
Unzip adb-fastboot.zip
Copy adb/fastboot files (AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe), and twrp.img
to same folder like c:adb
reboot Kindle to Bootloader
Open command prompt (Start menu>all programs>Accessories>Command Prompt
Enter Commands
Code:
cd\adb
fastboot reboot-bootloader
fastboot flash recovery openrecovery-twrp-2.7.1.0-otter.img
fastboot reboot
kindle will reboot
When you see Press Power for Boot Options select recovery
In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage
On Pc open sd card folder and copy update-kindle-prerooted.6.3.3.v1.zip downloaded from post 1
once copy is complete, close folder, unmount sd card
in TWRP select Install select update-kindle-prerooted.6.3.3.v1.zip
Swipe to Confirm Flash
after flash is complete, wipe cache, select Back, select Reboot
May take a few minutes to boot first time
Victory!
First off TY for the time you took to get me to the finish line. :victory:
I will admit trying to mount was a nightmare. I couldn't figure out how to do it so after hours of playing around and trying to find anything to try I finally succeed by installing the Kindle Fire Unbrick Utility (again) and running KindleUnbrick.bat file and installing the TWRP that way. Once that worked (and believe me I didn't think it would work since I tried this a few times) and I yelled WOOT, I followed the rest of your directions from "In TWRP (Team Win Recovery Project) select Mount check sd card and tap mount USB Storage" and installed your prerooted 6.3.3 zip and finished off your directions and have myself my dear reading buddy back. I APPRECIATE deeply the time you took to get me back. :highfive:
I want to add for anyone who is looking though threads looking for help with the same issue. If you are trying to get the TWRP file on your Kindle download the Kindle Fire Unbrick Utility and then running the RUN file and follow the directions.
great, Glad I could help.
I have tried to use the Kindle Fire Unbrick Utility a few times, with little success.
I would only suggest it, if nothing else is working, but does work in some situations.