Develop Bugs

[Q] KFU Brick? Step by step what I have tried

Here are the step by step things I have done. (I apologize in advance for mispelled words or wrong versions)
- My computer is operating windows vista. I used Kindle Fire Utility to root Kindle Fire on 6.2.2
- When 6.3.1 came out I upgraded KFU to 0.9.6
- I re-rooted and installed TWRP and FFF as wells as Go Launcher
- I then decided I wanted a stock Kindle Fire
- I did master reset under the options menu on the kindle. That took out Go Launcher. I was trying to unroot with out researching , so I thought if I went under TWRP and did a factory reset that would take care of it. (No need to yell for not researching, wife has done that)
- Now I’m locked at the white/orange kindle fire screen
- I still get the blue/white kindle fire screen to show up with v 1.4a in top right corner.
- I’ve tried normal/recovery boot, no luck there.
- I’ve tried holding power button 10-30 seconds several times, no go there
- Under device manager the kindle is listed as android phone and adb composite device (?) Not sure that’s the exact wordage but it’s the one with composite in it.
- KFU shows offline, unknown root status.
- While stuck at the white/orange screen I am not able to acces the Kindle Fire sd card
- If I go into TWRP I am able to mount the SD card and access on the computer
- I downloaded 6.3.1 from Amazon. Changed it to a zip file and put it on the sd card.
- I wiped cache and delvack (spelling?)
- When I try installing 6.3.1 zip in TWRP I get an error message.
- Do I need to wait for another amazon update?
- What else can I try?
- If I need to do line commands, please make it as basic is possible. I have read the beginners postings form kinfauns. Postings 1 & 2 made complete sense. Posting 3 went over my head.
- Command lines I have tried “adb devices” no devices are listed (it’s blank). “fastboot devices” nothing happens, “fastboot device” gives a lot of command options. Not sure where to go from there.

Sounds like your system software is broken if a factory reset in TWRP won't get it to boot normally.
What's the name of the zip file before you copy it over to the /sdcard? When you look at it with the Windows explorer, the file icon should look like a folder with a zipper down the middle of it. If it doesn't have that, you haven't changed the name of the file properly and the file suffix is wrong. Do a google search on changing the file suffix on Windows for info.
What's the error when you install the zip file?

kinfauns said:
Sounds like your system software is broken if a factory reset in TWRP won't get it to boot normally.
What's the name of the zip file before you copy it over to the /sdcard? When you look at it with the Windows explorer, the file icon should look like a folder with a zipper down the middle of it. If it doesn't have that, you haven't changed the name of the file properly and the file suffix is wrong. Do a google search on changing the file suffix on Windows for info.
What's the error when you install the zip file?
Click to expand...
Click to collapse
I downloaded the 6.3.1 file from Amazon's site. It had a long file name so I changed it to update. It has .bin followed behind it. I then right clicked on it, send to, compressed zipped folder. It does have the zipper folder.
I had the mount mode enabled through TWRP and copied it to the sd card and put it under the TWRP FOLDER.
Went back to the main menu in TWRP, install. Found the update file, started install. Started to install then stops. Can't remember wordage exactly, kindle is at home right now, but there's red letters that say error.

If I were you, I would install android sdk from google. then, use the sdk to install android tools and android platform tools. Make sure you installed to android sdk to the root file. Use twrp to reboot into bootloader. Plug in the kindle to usb. Then type this in (command prompt):
cd..
cd..
cd root
cd android-sdk
cd platform-tools
fastboot shell
reboot
Give that a try and tell me if it works.

gregory99mar said:
If I were you, I would install android sdk from google. then, use the sdk to install android tools and android platform tools. Make sure you installed to android sdk to the root file. Use twrp to reboot into bootloader. Plug in the kindle to usb. Then type this in (command prompt):
cd..
cd..
cd root
cd android-sdk
cd platform-tools
fastboot shell
reboot
Give that a try and tell me if it works.
Click to expand...
Click to collapse
I assume the first 2 "cd.." are to get me to the correct folders where android sdk is installed?

ewarhol said:
I downloaded the 6.3.1 file from Amazon's site. It had a long file name so I changed it to update. It has .bin followed behind it. I then right clicked on it, send to, compressed zipped folder. It does have the zipper folder.
I had the mount mode enabled through TWRP and copied it to the sd card and put it under the TWRP FOLDER.
Went back to the main menu in TWRP, install. Found the update file, started install. Started to install then stops. Can't remember wordage exactly, kindle is at home right now, but there's red letters that say error.
Click to expand...
Click to collapse
I think you had the .bin and then compressed it to. Zip that made it compressed it twice
You should
Download the kindle update
Open it up in notepad or something
Do save as
Save as update.zip
Then move it to sdcard/
Then flash in TWRP
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me

joshuabg said:
I think you had the .bin and then compressed it to. Zip that made it compressed it twice
You should
Download the kindle update
Open it up in notepad or something
Do save as
Save as update.zip
Then move it to sdcard/
Then flash in TWRP
Sent from my Kindle Fire using xda premium
if you find something I posted helpful please thank me
Click to expand...
Click to collapse
I did initially try just the .bin file without the .zip, but I couldn't find it. Once as a .zip file I could find it.
I downloaded 6.3.1 from Amazon's site again. I tried opening in notepad, but it locks up. Tried wordpad, my save as options: rich text format (rtf), text document, text document-ms-dos format, Unicode text document. Don't see anything for .zip

Are you able to get into TWRP?

Tera Tike said:
Are you able to get into TWRP?
Click to expand...
Click to collapse
Yup I am.

ewarhol said:
Yup I am.
Click to expand...
Click to collapse
Then mount as USB, copy over the file I sent you and flash. I take that you boot loader is okay too?

Tera Tike said:
Then mount as USB, copy over the file I sent you and flash. I take that you boot loader is okay too?
Click to expand...
Click to collapse
How do I know if the boot loader is okay?

Did you ever get out of TWRP after the fail attempt to install the factory Update?

Tera Tike said:
Did you ever get out of TWRP after the fail attempt to install the factory Update?
Click to expand...
Click to collapse
Yes. After fail I rebooted and got stuck at the white/orange kindle fire screen.

ewarhol said:
Yes. After fail I rebooted and got stuck at the white/orange kindle fire screen.
Click to expand...
Click to collapse
Then it should be okay. Is it version 1.4a? If not you should update to that version.

Tera Tike said:
Then it should be okay. Is it version 1.4a? If not you should update to that version.
Click to expand...
Click to collapse
1.4a White/blue kindle fire coloring

ewarhol said:
1.4a White/blue kindle fire coloring
Click to expand...
Click to collapse
Good...Where you able to flash that file?

Tera Tike said:
Good...Where you able to flash that file?
Click to expand...
Click to collapse
Leaving work soon and hopefully will try it in the next few hours

ewarhol said:
Leaving work soon and hopefully will try it in the next few hours
Click to expand...
Click to collapse
I see, Ok...

Tera Tike said:
I see, Ok...
Click to expand...
Click to collapse
THANK YOU, THANK YOU, THANK YOU!!!!!
THANK YOU EVERYBODY!!!!!!
BACK UP AND RUNNING!!!!
Tera Tike can I post the links you gave me? I have noticed others with similar issues as I have. I was going to start a new thread with the steps I took to resolve the problem.

Help
I got stuck in a nasty bootloop which Gregory was kind enough to help me out of by giving me the link to the Amazon Update. I was able to flash that and go back to stock. I then, possibly foolishly, thinking that I had lost root (did I?) ran the KFU utility which got stuck halfway through and now I am stuck on the white/orange kindle fire screen. Is there anyway to get out of this? I know, I suck. Your help and expertise is greatly appreciated.

Installing 9.6 drivers to root Kindle Fire

Hey there,
Long time lurker first time poster. Sorry I didn't post a hello thread, This forum has really helped me out with my Evo and Evo shift. I have never rooted them as I didn't have need. They served my purpose as is. Now I'm in new territory so I humbly ask you pros for help trying to root my Kindle Fire. The only reason I bought this was to turn it more into a tablet more like my phone.
I have seen and read just about everything I can find on installing the drivers and rooting this thing.
I have search here and found partial answers that end up turning into a different conversation and nothing has worked.
I'm on Win XP sp3 I am very computer savvy since I'm a software tester but I am stumped.
I set driver signing to ignore and I still get the unsigned error when trying to run install_drivers.bat.
You can't change the driver signing in the registry because it will just revert back.
When I plug it in to install it it shows up in the device manager as an Android phone with the Android Composite ADB Interface If I try and update the drivers it says the best driver is already installed.
I uninstall it and reinstall and point it to C:\Documents and Settings\Users\my profile name\KFU\Drivers\Kindle and it installs the same way as an android phone with the ADB interface below it.
Like I said. I have tried everything I have read and run.bat still shows as offline
Is the Android Composite ADB Interface mean the drivers are installed correctly?
I read one post someplace else that said if it said android phone to delete it.
Been at this for a week. Come home from work and spend hours trying over and over and there must be some bonehead thing I didn't do or a setting I didn't set correctly.
Please help

You can try a utility that I did for myself and others to root.
Basic Fire Utility[Expired]
Also goto %USERPROFILE%\.android and rename the file adb_usb.ini to adb_usb.ini.bk then rerun to driver install.
Also this should have been asked in the Kindle Fire Q&A.

Try this method:
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/

.Sometimes kfu says that the boot status is unknown even though it is just fine. assuming u havnt Try one of the options and see if the fire responds.
Sent from my Amazon Kindle Fire using xda app-developers app

Tera Tike said:
You can try a utility that I did for myself and others to root.
Also goto %USERPROFILE%\.android and rename the file adb_usb.ini to adb_usb.ini.bk then rerun to driver install.
Also this should have been asked in the Kindle Fire Q&A.
Click to expand...
Click to collapse
Thanks!
Mods please move to the correct forum. It was a little confusing when I saw all the kindle forums.
Do you have a how to for the basic fire utility? Do I need to remove all of the KFU stuff from 9.6 first? Sorry, first root. I installed the driver and now the DM says android phone,Amazon Kindle Fire ADB Interface.
Thanks again

Since you have the drivers installed do selection 3 to install FFF 1.4a then select 4 to install TWRP 2.2.0. Selection 5 will root and put basic Google apps.
The Basic Fire Utility copies the root/ gapps flash file to your device sdcard directory then boots you into TWRP. From there you flash the file... Choose Install, scroll under folders until you see Gapps+Apps.zip file and select it then swipe the blue button to the right to flash.
Thats it. Select reboot System and you are now rooted.
Sorry I am not very good at the instruction part thats why I just kept it to myself. But If you have more questions please let me know.

Tera Tike said:
Since you have the drivers installed do selection 3 to install FFF 1.4a then select 4 to install TWRP 2.2.0. Selection 5 will root and put basic Google apps.
The Basic Fire Utility copies the root/ gapps flash file to your device sdcard directory then boots you into TWRP. From there you flash the file... Choose Install, scroll under folders until you see Gapps+Apps.zip file and select it then swipe the blue button to the right to flash.
Thats it. Select reboot System and you are now rooted.
Sorry I am not very good at the instruction part thats why I just kept it to myself. But If you have more questions please let me know.
Click to expand...
Click to collapse
Thanks.
Even if it still says offline when I run the utility from the 9.6 download?
I couldn't find anything on sections 1,2,3 etc to follow in this thread and nothing on the download site besides the download link.
Thanks again

Mike Boucher said:
Thanks.
Even if it still says offline when I run the utility from the 9.6 download?
I couldn't find anything on sections 1,2,3 etc to follow in this thread and nothing on the download site besides the download link.
Thanks again
Click to expand...
Click to collapse
Sent you a pm.

Tera Tike said:
Sent you a pm.
Click to expand...
Click to collapse
Thanks
Didn't get a message that I had a PM. I need to check my settings.
Thanks again.

Make sure there are no spaces or special characters in your User name path. Also make sure C:/Windows/system32 is in your path.
Sent from my Kindle Fire using xda app-developers app

Tera Tike said:
You can try a utility that I did for myself and others to root.
Basic Fire Utility
Also goto %USERPROFILE%\.android and rename the file adb_usb.ini to adb_usb.ini.bk then rerun to driver install.
Also this should have been asked in the Kindle Fire Q&A.
Click to expand...
Click to collapse
Download link is bad.

I could not get this thing rooted. Tera Tike spent a lot of time walking me through it, but still nothing.
It would only boot into TWRP. He then offered to see if he could fix it for me if I sent it to him.
From all of our message interaction I didn't hesitate to send a new Kindle to a total stranger.
He had put so much time in trying to help me via messaging that I knew he was a good guy and I was right.
He fix it as soon as he got it. Had a corrupt partition. Most likely something stupid I did, and it's on it's way back ready to go.
Hail Tera Tike:good:

Good job Tera

Amazon Kindle Fire
I have recently gotten a amazon kindle fire, and i have been trying to install adb drivers so i can root it and flash recovery and it finally recognized it as (android phone) android composite adb interface and the other as kindle fire android composite adb interface but the one labeled android phone has the yellow exclamation mark and in general says this device cannot start(code 10) and says its not using resources because it has a problem.... (general details on missing driver is: Device type: android phone
manufacturer: google, inc.
location pci bus 2, device 0, function 0
i tried to install the google drivers again and it said the drivers already installed do you want to continue i hit yet and then it said it could not find the drivers... im getting really confused but i am very new to this and would love to gain more knowledge so if anyone can help you have my undivided attention. thanks.

[Q] TWRP backup hangs...what to do?

Using KFU v0.9.8 this evening, I was able to install TWRP v2.4.4.0 and FFF on my 1st gen KF, as well as to root it and install the GO launcher. I'm now interested in installing JB 10.1.
Before I do, however, I want to backup the device Using TWRP's backup feature, I am able to get to the point where it has backed up all 6 partitions. However, it appears to hang at "Updating partition details..." with the words "Generating MD5" at the top of the backup window. FWIW, I have tried it without MD5 and the same problem still happens but then it says "Backing up Android Secure" at the top.
Any ideas what may be causing this and a possible workaround? I'm hesitant to believe this backup will allow me to recover the KF later if needed.
Any advice is appreciated.
Many thanks,
Mumford67

Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Sent from my Nexus 7 using Tapatalk 2

asf58967 said:
Run smirkit and flash COT Recovery instead of twrp and your issues will magically disappear.
Click to expand...
Click to collapse
That worked perfectly! As it is, came to realization that KFU had never installed Superuser privileges anyway. Had to readjust the batch file to allow enough time for the Kindle to reboot so that it could install Superuser.
Now I'm running with CM's latest Jelly Bean build and all is wonderful!
Thanks for the help!
Mumford67

Same boat but your solution is beyond my experience
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
mebobbob said:
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
Click to expand...
Click to collapse
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...

mebobbob said:
Original KF, 6.3.2, KFU 98+, TWRP v2.4.4
I'm in the same boat, stuck at stuck at "updating partition details" TWRP v2.4.4 after seemingly successful backup.
I just used KFU to attempt root. Everything reported ok but there was no SU app listed in my Fire and Root Checker says i don't have root [like Mumford67]. Before doing anything else i decided to backup up everything [1296mb total, 3188mb was free]. TWRP reported 1255 MB TOTAL BACKED UP but now it's stuck there at "updating partition details".
I'm unfamiliar with smirkit and don't know what to edit in the .bat to allow more time to install superuser as Mumford67 described.
Right now my Kindle is on, stuck at:
[1255 MB TOTAL BACKED UP]
Updating partition details....
I really need some help, thanks
---------- Post added at 09:34 PM ---------- Previous post was at 08:55 PM ----------
I grabbed my kahonas and just forced a reboot. No idea if the backup is any good, not gonna risk finding out. I sideloaded superuser.apk from KFU folder and that went fine, got my root access.
My objective was simply to get root and backup apps+data for my kids' games before loading jellybean. So far so good...
Click to expand...
Click to collapse
Post back if you need help with anything.
Sent from my Samsung Galaxy SV using Tapatalk 3

I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Sent from my One V using xda app-developers app

thanks for continuous development, winging it for now
awidawad said:
I'm going to update KFU with more time to upload superuser and I will add an option for COTR. Hopefully I will see less problems like this.
Click to expand...
Click to collapse
being a half-assed informed newb I used KFU to install COTR by renaming the COTR img to twrp.img in the KFU recovery folder [made a twrp.ori]. COTR installed and did the trick so now I have a couple of different configurations/ROMs backed up to toy around with.
I'm sure if I took more time to learn how it all works there'd be a more straight forward way, but... haha

I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")

scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
To force reboot hold down the power button until it shuts off then power it back on. Also, if SU wasn't installed then boot to TWRP, the under the reboot menu select system and if SU isn't detected it will install it for you. Good luck!
Sent from my One V using xda app-developers app

here's everything i did, going fine now
scalywhisper said:
I am in similar situation. Mine is stuck at "backing up system". How would I force reboot? I am thinking no SU was installed. What can I do ? My wife will kill me if ive messed it up")
Click to expand...
Click to collapse
Generally, I had issues using the KFU 98+ but nothing insurmountable and definitely got everything done that i couldn't get done before!
Follow the KFU/TWRP instructions carefully, as i assume you've done.
Once you run KFU to install SU, your Fire is "ready" to be rooted even if it didn't install the SU app/apk. If you don't have root after running KFU, you can still sideload superuser.apk. With your Fire connected to your PC and ready for file transfers, copy superuser.apk found in KFU\files\ to your Fire. On your Fire, disconnect USB, browse to where you saved superuser.apk and install it. Run the app to establish SU access. Your rooted. Use a rootchecker app to confirm if you need to.
When I got stuck in TWRP, I forced shutdown by holding the power button until it turned off. When i powered back up, it booted fine all the way to Fire home screen. I had a backup of unknown quality because i was unsure if it finished.
To get a good backup, I used COTR [Cannibal Open Touch Recovery], found here
There's nothing wrong with TWRP, it's what I've used before but v2.4.4 simply wasn't reliable for me. The half-assed-but-worked-anyway method for me was installing COTR by using KFU. On your PC, in the KFU folder \recovery\, change the twrp.img to twrp.ori. Copy the COTR image into the same \recovery\ folder [CannibalOpenTouch-v2.1_otter.img downloaded from above link]. Change the COTR filename to twrp.img.
Now, with your Fire connected to PC, Run KFU and install TWRP - it will actually install COTR.
Now reboot your Fire to recovery, same method as you did for TWRP. Use COTR to run Nandroid [standard android backup tool]. works perfect.
This sounds really complicated but it really isn't too rough. Be patient, lots of reboots.
The backups are found in a \cotrecovery\ folder on your Fire. I copied them to my PC for safe keeping. I was able to go back and forth between original setup and new reset configuration fairly easily until I had everything the way I wanted.
To prevent Amazon from updating your fire and taking root away, see this article.
I did all this just because I screwed up my parental access PW on my Fire! only way around that is to reset to factory defaults. I wanted to backup app data [games and a few critical apps] to reload after reset. My kids would have been heartbroken to loose all their progress on a few games and I felt like an idiot for screwing up the password. all said it was worth it to restore root [lost it way back after an update]. I used Mybackup Pro to save apps+data online, GREAT app [requires root to save app data]. Its a regular app you run from Fire home and you can very selectively pick what apps and data you want to backup. Not the same as recovery mode backup, such as TWRP, COTR, or clockwork.
Good luck and I hope this roundabout method helps you if you're still stuck. While i was at it, i tried a few ROMs with ICS and Jellybean but didn't really like them on my Fire and really wasn't up to figuring out how navigate the systems. That's usually something i enjoy but simply not up for it. I'll just get a new tablet to toy with true Android versions! My rooted Samsung SII with stock ICS is fairly easy to configure and navigate.

I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?

jreink01 said:
I'm in the same boat, tried to backup on my ext sd and now its stuck at generating md5. How do I stop or cancel this safely?
Click to expand...
Click to collapse
May need to force, power off
Sent from my XT907 using Tapatalk

sd_shadow said:
May need to force, power off
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?

jreink01 said:
Tried that, the only thing that worked was a battery pull. I thought I would ruin my ext sd but it looks like everything is ok. I just backed up successfully to internal. How come it hangs up on the generating md5 on the external sd but not on internal?
Click to expand...
Click to collapse
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk

sd_shadow said:
Kindle Fire 1 doesn't have a removable SD card.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?

jreink01 said:
OK, thanks for trying to help.
---------- Post added at 10:15 PM ---------- Previous post was at 09:56 PM ----------
Update - I did a battery pull and it just seemed to reboot it. Nothing wrong with my external SD card that I can see. I can successfully do a backup on internal but everytime I try on external it gets stuck on generating md5. I have searched google but can't come up with anyone that has had the same issue on the g3. It's a sprint with model LG LG 990.Any help would be greatly appreciated. Just a thought, are there any other recoveries that work on my model g3?
Click to expand...
Click to collapse
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different

sd_shadow said:
This is a thread for the Kindle Fire 1, you should be asking in a thread for your device, because the answer maybe be different
Click to expand...
Click to collapse
Sorry, I typed in search g3 twrp freezing and this is what popped up.

I firstly tried to backup with TWRP on sd storage without luck, after 1,30h I give up and canceled that darn thing (the error says: "create tarfork process ended with error:255") and tried to backup on internal storage where it seems it work like a charm. Backup completed in 767sec.

Erased my Fire HD 8.9 - Can it be saved?

I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!

rebelduke said:
I was running Candy5 ROM ver. 2.5 and saw the thread for the 4.0 ROM. I downloaded it and Gapps and put it on the Fire HD. Rebooted into Recovery and into TWRP. That's when I did one of the most stupid things that I've ever done. I wanted a clean install from scratch. Unfortunately, I erased everything! When I realized what happened I rebooted and the screen goes through the two fire HD logos stopping at the last one. Is there ANYTHING I can do to get an operating Fire HD back up and running, Please!
Click to expand...
Click to collapse
Try to reboot into TWRP (press + hold volume up as soon as you see the first logo, keep holding till you see the TWRP curtain). If you are successful, copy a ROM zip into the kindle's internal storage (gapps are optional, but I recommend you flash them along with your chosen ROM), flash it, reboot, and cross your fingers.

Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!

rebelduke said:
Thank you. I'm making some progress. Your instructions got me into TWRP (ver. 2.8.6). Next step is to get the PC to allow copying of the ROM file. TWRP does recognize that there is no operating system installed. Thanks again!
Click to expand...
Click to collapse
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!

monster1612 said:
If you can't directly copy it, try adb sideload path/to/ROM.zip (enable sideloading in the advanced menu in TWRP first, or you'll get an error). Make sure you have adb drivers installed and working if your PC's running Windows. Good luck!
Click to expand...
Click to collapse
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.

rebelduke said:
Adb sideload worked with the Candy5 4.0 ROM. The Gapps zip failed due to the file size being too great. I can tackle that after the ROM is installed. Another stupid question - any idea where the sideloaded ROM zip file would be internally? I explored using the TWRP file manager and all I have is the directory structure - no actual files. I probably looked in 50+ folders and they were all empty. I think there must be hundreds of directories and subdirectories. I found one folder named sideload thinking I had it but no luck. Worst case I can open every folder and hopefully find the ROM zip file.
Click to expand...
Click to collapse
From the TWRP FAQ for the sideloading feature:
TWRP versions 2.8.2.0 and higher will stream the zip from your PC without storing it on your device. If you wish to store the zip on your device for later, you should not use sideload and instead use adb push or some other method to copy the zip to the device.
Click to expand...
Click to collapse
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.

monster1612 said:
From the TWRP FAQ for the sideloading feature:
Older TWRP versions used to store the zip file in /sdcard/sideload, but I think versions 2.8.2.0 and higher use it as a temporary buffer and delete the zip after flashing. If you're able to get Android up and running, then you should be able to connect it to your PC, copy the ROM and gapps zips over to the kindle without using adb, and flash the gapps.
Click to expand...
Click to collapse
Thanks very much for all of your advice and suggestions! I'm back up and running. The gapps package was causing an error 70 message. Once I found a smaller file it worked. It certainly was an excellent learning experience. Thank you again.

Es File Explorer issue

I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?

The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.

deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.

Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk

i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox

I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.

@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??

Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.

Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?

d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.

Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps

phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?

phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.

Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"

Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.