Develop Bugs

can't get into settings after root

Hi, I rooted with KFF and now i can't swip from the top of the screen and i have no back arrow or home button. i was trying to remove root with KFF and bin4ry but no luck. Can somebody give me some instructions? Thanks

Rooting alone will not cause the type of problems you are describing. Have you installed a custom ROM, custom launcher, or any other alterations to /system that would require root privileges?

No 2nd bootloader. just root and i can't enable adb

Adb was required for root, it should still be enabled if you never were able to get into settings after root. Weird... If worst comes to worst u might have to reflash the system image, which on the bright side is prerooted. But I just don't see how rooting it could cause such a weird error, sounds like something got messed up with the systemui apk, and root doesn't modify that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

cubiche said:
No 2nd bootloader. just root and i can't enable adb
Click to expand...
Click to collapse
To remove "root", simply enter the following commands in a terminal emulator:
Code:
su
mount -o remount,rw /system
rm /system/app/Superuser.apk
rm /system/xbin/su
mount -o remount,ro /system
exit
But, be warned. If having "root" is not the source of your problem, as I suspect, and you have some additional changes to your /system directory that you've failed to mention, you will not only be stuck with the problem you had to begin with, but you will also not have root permissions or the adb connection you would need to fix your device.

He should be able to get it in fastboot though with the fastboot getvar product command if he plugs in his kindle when off after running it since a 8.9" model right? That would be useful even if adb is disabled.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I can get into fastboot with kff, but I don't know where go from there.

You can restore a saved system.img, but it will still be rooted when it's finished.

I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?

cubiche said:
I have a saved image from another kindle HD 8.9. I think it was 8.3.0. Will that work? Can someone will me through the process?
Click to expand...
Click to collapse
Code:
fastboot -i 0x1949 flash system system.img

Hey soupmagnet, thanks for the help. Is there a risk of bricking the tablet?

The risk is considerably lower than installing the 2nd bootloader.

How do I enter that line. From adb?

ok, i'm done but i'm stuck on the kindle fire screen.

Where did you get your system.img?
[Edit:] Nevermind. I forgot you already told us. Is it safe to assume you have a boot.img as well?

it was saved on my computer from a different hd 8.9. i saved it before frashing 2nd bootloader and twrp. should i also flash the recovery and boot?

yes i have boot and recovery.img

fastboot -i 0x1949 flash boot boot.img
That should fix it.

i flashed recovery, boot and system and still don't have the navigation buttons. system is still rooted, i assume because i flash a rooted system.img. i also have the stock-system, recovery and boot. do you think that will fix it?

I guess I assumed that's what you meant when you said you had saved images.
Unless you unpack, unroot and repack your system.img, it's going to be rooted either way because you have to have root permissions to save your system.img. But it seems beyond all logic and reasoning to think that having "root", which consists of two files that are completely independent of the systemui.apk and framework-res.apk, would have any effect on the navbar at all.
By all means, restore your stock images. I'm very interested to see if it has any effect.

[Q] Kindle Fire BRICKED (Stuck On Kindle Logo) No Susses in CMD

Hello, I Have a Kindle Fire 1st Gen. I Had CM 10.1 on it. I was attempting to put AOSP back on it for My Wife. I did I Noobish Move at 4 am half asleep, I Did NOT go into advanced mode in TWRP and uncheck DATA in the Wipe tab. So This Screwed me "Bricked" Message comes up in TWRP when rebooting, says ( NO OS ) . I have Tried Kindle unbrick utility with no success when clicking on "Stuck at Logo" in utility I get this Error ...> PIC Attatched!>
I then Tried Using android-sdk ( I have went in and edited the files that need to be edited in program files/android...> File_android_winusb as well as in .android folder in the appdata location) Along with CMD & I get a Error So far into the process of Resetting Kindle OS. Pic Attatched as well. It Seems Like I have something missing ?!?!?
I somewhat Suck at CMD, I don't have much experience with it, so Please go slow on me,when Giving advise....
Thanks In Advance!!

If you still have access to TWRP, use it to mount your sdcard to USB.

soupmagnet said:
If you still have access to TWRP, use it to mount your sdcard to USB.
Click to expand...
Click to collapse
I Tried That. I See the Device But when double clicking, It will not let me access it.

Butt Nugget said:
I Tried That. I See the Device But when double clicking, It will not let me access it.
Click to expand...
Click to collapse
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?

soupmagnet said:
Oh that's right, it won't work on 2nd generation devices.
Do you have your drivers installed? Are you able to send any adb commands (adb devices)?
Click to expand...
Click to collapse
My Kindle is a 1st Gen. I'm not sure If I understand what You are talking about when You say "send Commands/devices" If Your talking about in CMD I Get all the way to Seeing my Device Serial Number for Kindle. The when I type "adb shell" I get a error saying (Failed: No such file or directory <2> - ) You can see this in the screen shot I attached to this thread..

Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?

soupmagnet said:
Sorry, I looked at what forum this was in and got a little confused...silly me :silly:
Anyway, back on track...
You should not be receiving that error in TWRP. If you are, then something is seriously wrong with it and probably needs to be reinstalled. Other than that, I'm having trouble seeing where the problem is. (the pic shows that you're not in recovery, btw)
You clearly have access to adb, so...why aren't you using 'adb push' to transfer a new ROM to your sdcard to flash in recovery?
Click to expand...
Click to collapse
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver. So Sounds possibly what I tried is totally different from what Your asking if i done? If So, Could You Explain step by step thee method with new roms or send me in the right directions 2 a how to link or video? Anything I would appreciate GREATLY! :fingers-crossed:

Butt Nugget said:
I've Done searches and only found how to attempt recovery, typing in commands on pc's CMD Prompt while kindle is mounted to usb in twrp and typing commands in on CMD in pc I installed Android SDK and Device driver.
Click to expand...
Click to collapse
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.

soupmagnet said:
I have no idea what you're saying.
All you need to do is, boot into recovery (TWRP), use adb to "push" a ROM to your sdcard (adb push...), then install the ROM in recovery.
Click to expand...
Click to collapse
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?

Butt Nugget said:
I mentioned Earlier (say, the Drive of the device is :F) In My computer, When I click :F It states Cannot access (Drivers are installed for kindle). I'm asking How Can I Mount USB in TWRP and Put ROM File on sdcard when I cannot access it... I Do Not have a Micro USB OTG to USB 2.0 Cable to plug up to kindle with the files put on a external HD to complete this course.
Does that make more since?
Click to expand...
Click to collapse
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?

soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
I am attempting to understand what u are saying But I'm thinking ur not giving full step after step instructions OR this Version I have (v2.6.0.0) differs from Yours, Because there is No such OPTION as ADB PUSH..... I have ADB sideload (under Advanced Tab) which only wipes Cashe.. I've looked in every single area in TWRP and see nothing of anything You are talking about, other than "MOUNT" obviously.

soupmagnet said:
Try to understand what you're being told. I'm not saying anything about mounting your sdcard to transfer files to it so get that idea out of your head for a moment.
You need to boot into recovery and use the command 'adb push' to transfer a ROM to your sdcard, then flash it in recovery.
Now, does that make more sense?
Click to expand...
Click to collapse
While Searching Google for Help I seen this..> http://forum.xda-developers.com/showthread.php?t=2361144
I'm bout to install a Pc with Linux and try pushing it that way.. Have not tried that.

You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
You don't need Linux to run adb commands *face palm* While I am a linux enthusiast, all he's trying to say is boot into twrp, plug kindle into your PC, and open a command prompt, CD into the directory of adb and run "adb push pathtofile /sdcard/filename" this should push it to the kindle, though their might be something else u need for in prior to this I'm not sure, soupemagnet will probably post back if there is. BTW I don't know if u actually meant u were going to install Linux, but if you don't plan on using it after this or anything in the case u do decide to still use it for this, u don't need to install it, distros like Ubuntu let you boot into a full os from the CD so u don't need to install it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Stunt Thnx... You Helped breaking it down. I just used KFU and Fixed this within 3 minutes.. Thnx Man!:good:

[Q] KF2 Rooted with cm11 and kitkat running

My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James

getnby said:
My kf2 was working fine but I ran out of room to install apps. I deleted unneeded apps still not enough room. I booted into twrp did a full wipe and now I can't side-load any roms to install. Twrp shows no OS installed. It will boot into twrp fine but nothing else. I have a fastboot cable. My computer recognizes my kf2 as an adb device but I can't seen to get anything to load. Some of the commands in KFFAID work but not all. I am trying to load cm11 and kitkat back. Any help would be appreciated.
James
Click to expand...
Click to collapse
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp

didn't work
stunts513 said:
if sideload doesnt work then just do this, put the rom you want to flash and its gapps in the folder that adb is in, and run this while booted into twrp: adb push romnamegoeshere /sdcard/
then you can install the rom from inside twrp
Click to expand...
Click to collapse
Here is what happened. It said the device was not found. In the device manager it shows adb device under kindle fire.

Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk

No luck
stunts513 said:
Look on your task manager and kill every instance of adb.exe that you see and try again, I had that happen before when multiple instances were running. As long as it is in twrp then adb should work. If it continues to not work then uninstall the adb driver and if you see the MTP kindle device still there remove it as well, there might be a composite device that needs removing too, I find it a pita going between fastboot, recovery and whatever ROM os flashed if I use windows because of this, the drivers constantly have to be reinstalled when you change modes for me, hence why I avoid working with my kindle in windows and instead just use Linux. If you see any USB composite devices, check the hardware id's for a vid of 1949, if it has that then feel free to uninstall it. This may sound a bit complex, if you need more of an explanation just tell me.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
My computer only recognizes the kindle as an adb device in fastboot mode. I haven't been able to use any of the adb commands on it with any luck. It says device not found. This only shows in kffaid version 4.1.87-beta.

*facepalm* you don't use adb commands with fastboot, you use fastboot commands with fastboot. When it is in twrp it should have adb access though...
Sent from my Amazon Kindle Fire HD using Tapatalk

I think I have a driver issue. I forgot to thank you for your help. If I could send the zip rom and gapps I could get it back to where it was. Is there anyway to start all over from the original kindle OS at this point?
Thanks you

You coukd restore it in fastboot using kffa but it seems like unnecessary work. I would boot a ubuntu 13.10 live cd/usb and just attempt it from there since there won't be any driver issues.
Sent from my LG-P769 using Tapatalk

I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks

getnby said:
I tried Ubuntu 12.04 LTS and it was to much trouble. I will try Ubuntu 13.10. I will have to learn the commands to use it.
Thanks
Click to expand...
Click to collapse
these commands should do the trick assuming the repos are all active in the downloadable section of the software updates control panel.
Code:
sudo apt-get update
sudo apt-get install android-tools-fastboot
and after that the fastboot command will work but keep in mind to give it superuser privis with sudo or it probably wont work, i had forgotten that recently on my own pc since i don't deal with fastboot too often. ex: sudo fastboot -i 0x1949 getvar product

I had to work all weekend. I tried to get access through ubuntu 13.10. I used the commands you provided (sudo apt-get update). This command worked fine. When I used this command (sudo apt-get install android-tools-fastboot) It said I had to enable universe. I did some research and got that working and tried to use this command again (sudo apt-get install android-tools-fastboot) then this one worked fine. Then I tried the last command with my kindle in fastboot mode flashing green light (sudo fastboot -i 0x1949 getvar product ). The message was cannot connect to otter-2 ... device. Same thing I have been getting all along.
I think when I wiped the system I cleared all the software to connect to any external device. I don't know if I can even get access to restore the original OS. If you haven't guessed by now I an a noob. I think you realized that with my adb commands with fastboot enabled. I got the impression you knew when I saw the *facepalm* comment the the beginning of you post. When my kindle is booted to twrp my computer does not recognize it. My computer will recognize as an adb device when in fastboot mode. My computer will recognize it as a kindle (with a yellow triangle in the device manager) when it is trying to boot with the white and blue logo. I don't know what to do at this point. Here is a screen shot with adb side load from twrp.

Interesting, seems that data didn't want to mount. Have you tried adb from Linux while in twrp? Just run "sudo apt-get install android-tools-adb" to install the command, if you can get adb access at least then I may be able to help fix this depending on what exactly is wrong. BTW I didn't exactly think you were a noon with that facepalm, I just see people get that misconception a lot about adb and fastboot commands. What exactly did that fastboot command report back, I was surprised it was an error when I saw otter2 in the error considering that was what that command was sort of supposed to report back.
Sent from my Amazon Kindle Fire HD using Tapatalk

Here is where I am. See below. Now where do I put the file in ubuntu so I can access it from the terminal window. I am running ubuntu from a live CD. I tried the push command but it says no such file or directory. I told you I was a noob!
[email protected]:~$ adb devices
List of devices attached
0123456789ABCDEF recovery

Since adb is in a system path must out it in the current directory you are CD'd into, if you left the terminal alone it should be in ~ (the home folder of the Ubuntu account) so photo the home folder and drop it in there and run "adb push filename /sdcard/"
Considering that /data doesn't want to mount and that /sdcard os technically in /data, that command might not work depending on what's going on. I reccomend seeing if you can first and if not goto the months and mount /cache if its not mounted already, and they pushing a twrp update into it to try to reflash twrp, its small enough I think it should fit into the cache, though I don't think a ROM would fit.
Sent from my Amazon Kindle Fire HD using Tapatalk

I installed ubuntu on my laptop with windows 7. It seems to work better. I put the files in the home folder and the user folder. I mounted the cache and ubuntu said instead of unable to mount it was unable to access kindle now. Here is the terminal window results.
[email protected]:~$ sudo apt-get install android-tools-adb
[sudo] password for user:
Reading package lists... Done
Building dependency tree
Reading state information... Done
android-tools-adb is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[email protected]:~$ adb push cm-10.2-20130908-UNOFFICAL-otter2.zip /sdcard/
cannot stat 'cm-10.2-20130908-UNOFFICAL-otter2.zip': No such file or directory
[email protected]:~$

Um OK well the filenames are case sensitive in Linux so lookout for that. Also if it was in your home folder then it should have worked as long as you didn't CD anywhere else in the terminal first.
Sent from my Amazon Kindle Fire HD using Tapatalk

Problem Fixed
I fixed my problem. I had to restart my kindle into recovery mode and connect the fastboot cable to the computer and kindle before it booted into TWRP. At that point while booted into TWRP I used the push command in ebuntu terminal to sideload cm11 and gapps. After I loaded them I installed them with TWRP and rebooted. Now it is restored to where it was when I wiped it. I will not do the advanced wipe again.
adb push cm-11-20140202-NIGHTLY-otter2.zip /sdcard/
adb push gapps-kk-20131119.zip /sdcard/
Thanks for your help stunts513
Click to expand...
Click to collapse

Software Update Loop Bricked FireTV

OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance

LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.

rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again

LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.

rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T

LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.

rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?

Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot

roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???

OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?

The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.

schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.

rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?

schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.

rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.

Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did

Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.

rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in

I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.

Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT

Kindle fire 8.9 error updating binary in zip

OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!

kyleyarbrough said:
OK, I had my kindle running cyanogenmod 11. I was having problems with some apps running on it, root was acting weird. Root checkers said it was rooted, but some apps that required root weren't installing right.
Fast forward, I thought perhaps I needed to flash the new version. I got into recovery to run it and flash it and this is the error I have.
So all the forums said, just wipe it then it will work. Of course now I have no OS on the thing. TWRP is fine, but I can't use the tablet.
So some other forums suggested it's either a mounting to E:\ problem or a rooting problems. I can get in to ADB, I've pushed many different roms over and they all have similar errors.
All of the Root tools I can find require you to come in the front door. TWRP fails when it goes to 'fix permission' and every time I reboot says , 'root is gone, swipe to fix' but it's not seeming to stick.
Any ideas on how to make sure I can mount the new rom and get this back up and running.
As I said, I've tried many roms, directly downloaded from CM website: Download:
cm-12.1-20160129-NIGHTLY-d2tmo.zip (284.96 MB)
sha1: e461a1dc263d927de3b6748d3b877310e7b1fd39
Download: cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2tmo.zip (286.1 MB)
sha1: bfb989917775ff190b8b795d93c1e439ccf8a514
I'm running TWRP 2.6.0.0 and have a binary ADB driver of 1.0.31. I can ping 4.2.2.2 so I'm pretty sure since the issue is coming from the device itself, and the way it's erroring reminds me of other permission problems I've seen in other devices that it's a root issue.
Is there a simple command line ADB tool or something that I can use to validate/set root?
Thanks!
Click to expand...
Click to collapse
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs

monster1612 said:
Your TWRP version is out of date. Flash the 2.8.7.0 image from this thread, reboot into TWRP and make sure your TWRP version is now 2.8.7.0, and try flashing CM12.1 after that.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
HI! thanks for that advice. I wish I could. I've tried several methods, and although I can get into ADB shell, I can't access su:
besides kindle fire first aide and other batch files, I found some manual instructions:
http://forum.xda-developers.com/showthread.php?t=2277105
Here's what it tells me to do (among many other things): I realize this is just backing up stuff that doesn't exist etc, but it's indicative of the problems without having su.
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD8Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD8Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD8Backup]
but if I go into adb shell and type any commands, like just simple su:
I get /sbin/sh: su: not found
when I do whoami: I get root
but I get a funky prompt:
~#^[[61;5R
instead of a normal # root prompt.
So I'm kind of stuck because I can't really do anything without the su, and it says I'm root. So can I adb push over the files and mount the right drives or whatever to get it to recognize su. At that point I can install twrp, but i'm sure at that point my existing twrp will work too!
I can't seem to get it into fastboot mode either. When I adb devices it says I'm in recovery, not device and in TWRP it says no OS installed. So my only functioning loader is TWRP. (or however you put that more accurately).
I feel like with adb push working, I should be able to do something to get this back, but all the tools expect you to just push a button, not do it the hard way.
So long story short, if you can point me to a thread that tells me how to update TWRP or how to push SU over with ADB or anything that would be awesome. I"m not a complete turd at this, but I think I broke it using something like kingoroot instead of just using the bin4ry while I still had the cyanogenmod working somewhat. So I'm thinking that's why i got the funky prompt, and that's why my su is gone from where it should be.