Develop Bugs

Frequently Asked Questions - Amazon Kindle Fire

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Amazon Kindle Fire[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: I have a new Kindle Fire (purchased after Nov 2012). What do I need to know first?
[/SIZE]You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!!​[SIZE=+1]Q2: I have an older Kindle Fire (1st generation). What do I need to know first?[/SIZE][GUIDE] Kindle Fire For Beginners​[SIZE=+1]Q3: How can I tell if I have a 1st or 2nd generation Kindle Fire?[/SIZE]If you have a software version of 6.3.2 or earlier, it is a 1st generation Kindle Fire. Anything after that is a 2nd generation Kindle Fire.​[SIZE=+1]Q4: Where do I find information on how to root the 1st generation Kindle Fire?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)​[SIZE=+1]Q5: Can I root the Kindle Fire without a computer?[/SIZE]No​[SIZE=+1]Q6: Is there a “One-Click” or scripted root method for the 1st generation Kindle Fire?[/SIZE][Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12) (Windows) - or - BreakDroid (Mac)
Be careful when using these tools and make sure you understand how to fix problems that may arise before attempting anything. Failure to do so will most likely lead to problems.​[SIZE=+1]Q7: Is there an easier way to root the 1st generation Kindle Fire?[/SIZE]Install custom recovery, then install a custom ROM. If you want a rooted version of the stock OS, install MoDaCo.​[SIZE=+1]Q8: What custom recoveries are available for the Kindle Fire?[/SIZE]Team Win Recovery Project (TWRP) - and - Cannibal Open Touch Recovery (COTR)​[SIZE=+1]Q9: Is there an easy way to install a different custom bootloader or recovery without using ADB or fastboot?[/SIZE][smirkit-v2.4][02/05]install recovery+bootloader COTR or TWRP​[SIZE=+1]Q10: Where can I find a list of available ROMs?[/SIZE][INDEX] Kindle Fire Development *REVISED NIGHTLY*​[SIZE=+1]Q11: What is the best ROM available?[/SIZE]What is considered to be the best ROM is always a matter of opinion. Just pick one and try it out to see if you like it. If not, try a different one. If you are looking to find the most popular ROM, you can search the development forum for the ROM thread with the most views.​[SIZE=+1]Q12: I just want to root my 1st generation Kindle Fire. Do I have to install FireFireFire?[/SIZE]No, but not having FireFireFire installed on a rooted device opens you up to the potential of serious problems in case anything goes wrong, and things will almost always go wrong.​[SIZE=+1]Q13: Where do I find information on how to unroot the 1st generation Kindle Fire?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)​[SIZE=+1]Q14: Where do I find information on how install ADB/fastboot drivers for the 1st generation Kindle Fire?[/SIZE][GUIDE] Kindle Fire For Beginners – Post #2 - & - Let's take some of the mystery out of getting ADB working in Windows​[SIZE=+1]Q15: I've exhausted all available options and still can't get ADB/fastboot to connect in Windows. What else can I do?[/SIZE]Soupkit
​[SIZE=+1]Q16: What does it mean when my device is stuck at the Kindle Fire logo?[/SIZE]It depends on which Kindle Fire logo you're talking about. If you're talking about the Kindle Fire logo that stays brightly lit without any change in brightness, it means the device is in fastboot mode. Just change the bootmode to normal or recovery and reboot. If you are unable to change the bootmode, then you need to fix your drivers. If the Kindle Fire logo you're talking about flashes and goes dim after being brightly lit for a few seconds, then your device is trying to boot normally to a malfunctioning operating system, likely caused by not wiping the data partition (factory reset) before flashing a ROM. If that's the case, you will likely need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall a ROM properly.​[SIZE=+1]Q17: What can I do that will fix 90% of all Kindle Fire problems?[/SIZE]Get access to custom recovery and reinstall a ROM, making sure to wipe the data partition (factory reset) first.​[SIZE=+1]Q18: Where do I find information on some of the various commands and how to use them?[/SIZE][GUIDE] Kindle Fire For Beginners – Post #3​[SIZE=+1]Q19: Where do I find information on how to use fastboot mode?[/SIZE] [GUIDE] Fastboot Mode​[SIZE=+1]Q20: How do I install a custom ROM?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)​[SIZE=+1]Q21: I need to get a ROM or file onto my Kindle Fire. What are the various methods of doing so?[/SIZE]You can download the ROM or file onto your device via the Internet. You can use an app like Wifi File Explorer to transfer the ROM or file to your sdcard over wifi. While booted normally, you can mount your sdcard as a USB storage device and transfer it from your computer. If neither of those options are available, you can use ADB to push the ROM or file to your sdcard or use the “Mount” function in custom recovery to mount your sdcard as a USB storage device and transfer it from your computer.​[SIZE=+1]Q22: What can I do if I am unable to mount my sdcard to USB in recovery?[/SIZE][HOW TO] Fix "Failure to mount" sdcard, system, data or cache​[SIZE=+1]Q23: I like the stock OS but is there an easier way to install Google Play, Google Apps, Disable OTA updates, change wallpapers, etc., rather than doing it manually?[/SIZE]Install MoDaCo while in recovery​[SIZE=+1]Q24: Where do I find information on how to restore the Kindle Fire to it's original unmodified state?[/SIZE][HOW-TO] Root / Install a ROM / Unroot / Revert to Stock (A KFFB Supplement)​[SIZE=+1]Q25: I tried to restore the stock OS and now my device is stuck at the Kindle Fire logo. What happened?[/SIZE]It is most likely that you forgot to wipe the data partition (factory reset) in recovery before flashing the stock update.zip. As a result, you will need a factory cable to get into fastboot so you can reinstall custom recovery and flash the update.zip properly.​[SIZE=+1]Q26: What is a factory cable? What is it used for? How do I use it?[/SIZE]A factory cable, not to be confused with the OEM USB cable that comes with the Kindle Fire, is a USB cable made to emulate a Motorola factory programming cable. With the Kindle Fire, it is an easy way to access fastboot mode, especially when no other options are available. To use it, while plugged into your computer, simply plug it into a Kindle Fire that has been completely powered down.​[SIZE=+1]Q27: Where do I find information on making or purchasing a factory cable?[/SIZE][Info]Making/Using a Factory Cable - or - SkOrPn ​[SIZE=+1]Q28: What needs to be wiped when installing a ROM?[/SIZE]When installing a minor update to a ROM, it is generally considered safe to just install the ROM without wiping anything. When installing a major update or a different ROM altogether, you must, at the very least, perform a factory reset in custom recovery, which wipes the data and cache partitions. Not doing so will usually result in major problems.​[SIZE=+1]Q29: I tried to install a ROM and now my device is stuck at the ROM's boot animation. What happened?[/SIZE]It is most likely that you forgot to wipe the data partition (factory reset) in recovery before flashing the ROM. If you have FireFireFire installed, you can use the power button at startup to access custom recovery and reinstall the ROM properly. Otherwise, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall the ROM properly.​[SIZE=+1]Q30: Is it true that letting the battery die will reset the device and fix whatever problem I'm experiencing?[/SIZE]NO!!! NO!!! NO!!! NO!!! The flash memory storage of the Kindle Fire is capable of holding data without ANY power until your grandchildren's grandchildren have their own grandchildren...probably even longer. Not to mention, a dead battery will cause much bigger problems than you ever had to begin with, on top of the problems you had to begin with. Whatever problem you're dealing with, it is always best to avoid letting the battery die at all costs.​[SIZE=+1]Q31: Why is my boot logo flashing every 5-10 seconds?[/SIZE]You have a near dead battery. The most effective way fix it is to power the device down by holding the power button for 10 seconds, plug the device into a power source, then IMMEDIATELY hold the power button until it shuts off again. If it shuts off and stays off (no display, no led), let it charge for at least half a day. Otherwise keep trying, or get another battery.​[SIZE=+1]Q32: My Kindle shows the boot logo for 20-30 seconds and either goes to a black screen or reboots itself.[/SIZE]You either don't have a ROM in place or your ROM is seriously malfunctioning. If you have FireFireFire installed, you can use the power button at startup to access custom recovery and install a ROM . Otherwise, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then install a ROM.​[SIZE=+1]Q33: When my Kindle Fire boots, a message keeps popping up, preventing me from doing anything, how do I fix it?[/SIZE]This is either caused from not wiping the data partition (factory reset) in recovery before flashing a ROM or you installed an app that is incompatible with the Kindle Fire and it is causing problems. If it the latter is true, use ADB to access the shell and locate and remove the offending app. Otherwise, if you have FireFireFire installed, you can use the power button at startup to access custom recovery and reinstall the ROM properly. If not, you may need a factory cable to get into fastboot mode so you can access or (if needed) install custom recovery, then reinstall the ROM properly.​[SIZE=+1]Q34: My Kindle Fire does not power on or show any outward signs of life; no display, no sound and no LED when plugged in. What does this mean?[/SIZE]There was a problem while installing a custom bootloader, or the bootloader partition was, in some way, compromised and the device was shut down before it was fixed. If the device is a 1st generation Kindle Fire, you have to use Firekit or usbboot along with the shorting trick to reinstall the bootloader. If the device is a 2nd generation Kindle Fire, unfortunately there is nothing you can do about it.​[SIZE=+1]Q35: I have a question about a particular ROM but I can't post in the Development section. What can I do to get the help I need?[/SIZE]The Development forum is for sharing ideas on development. If you have a question about a particular ROM, ask it in the Q&A section. Contrary to what some may believe, the Developers of this community are very aware of questions being asked in the Q&A section, especially when it comes to their ROMs.​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.​

reserved

reserved - just in case

Nice job Soup

[Edit:] Tapatalk acting stupid again

Hi guys I no longer own a KF1 I have a KF2. But I am wondering if anyone would be able to confirm that /sys/class/leds/led-green exists? I am planning on building an app that connects up to your notifications and allows for the use of the charger light as a notification light. And of course it will require root
Sent from my Amazon Otter2 using Tapatalk

see op
Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Click to expand...
Click to collapse

sd_shadow said:
yes it's there, charging is orange, charged is green, please start a new thread if you need more info.
see op
Click to expand...
Click to collapse
Ok thanks. I talked to hashcode and he said he might be adding that feature anyways so I guess I wont finish the app. Thanks anyways
Sent from my Amazon Otter2 using Tapatalk

NEED HELP......
i have a kindle fire hd that i rooted to kit kat no problem but now im trying to help my mom she has a 1st gen kindle fire with 6.3.3 on it, i know its a first gen cus i bought it for her brand new when it came out. so im trying to install jelly bean on it or maybe even kit kat but everything i see is for the 6.3.2 firmware and earlier could use a little help here maybe with downgrade to the 6.3.2 or figure out if there is a anything for the 6.3.3 firmware.. thanks

Please read first...
If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.
Click to expand...
Click to collapse

cavila1988 said:
i have a kindle fire hd that i rooted to kit kat no problem but now im trying to help my mom she has a 1st gen kindle fire with 6.3.3 on it, i know its a first gen cus i bought it for her brand new when it came out. so im trying to install jelly bean on it or maybe even kit kat but everything i see is for the 6.3.2 firmware and earlier could use a little help here maybe with downgrade to the 6.3.2 or figure out if there is a anything for the 6.3.3 firmware.. thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1859851
head here.
there are some kitkat rom for kindle fire. take note that there is a new development for kindle fire:
read THIS and THIS, please read carefully and throughly.
as for otterX partition there are two type of partition.. larger system partition (smaller data partition), and smaller system but larger data partition.
as for file system there are ext4 and f2fs..
choose which one you want to use first, and then ask or if you already know, download the correct bootload, recovery, and ROM that support it.

hello,
-I have bootloader v2.05, otterx mode, twrp 2.8.3.0,
- i wiped everything else,
-now I can't mount SDcard (TWRP)(unable to find storage partition to mount to USB) , ADB is 'unauthenticated' mode and can't transfer ZIP to flash any ROM
Please help: how to transfer ZIP / flash ROM via fastboot / change ADB into recovery mode so I can use push/pull
Any solution will work.
Best,

For1n said:
hello,
-I have bootloader v2.05, otterx mode, twrp 2.8.3.0,
- i wiped everything else,
-now I can't mount SDcard (TWRP)(unable to find storage partition to mount to USB) , ADB is 'unauthenticated' mode and can't transfer ZIP to flash any ROM
Please help: how to transfer ZIP / flash ROM via fastboot / change ADB into recovery mode so I can use push/pull
Any solution will work.
Best,
Click to expand...
Click to collapse
Do not use this as a general help thread.
---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------
see [How To] Fix Otter X Install Errors, Partition sizes, Unable to Mount System...

The every Kindle with firmware 6.3.2 and under is a 1st gen is slitghly outdated. 6.3.3 was released to the 1stgen.

MineMasterHD said:
The every Kindle with firmware 6.3.2 and under is a 1st gen is slitghly outdated. 6.3.3 was released to the 1stgen.
Click to expand...
Click to collapse
6.3.4
see 2015 - update-kindle-6.3.4_D01E_4120220 by sd_shadow

[Q] entire system wiped no os stuck at screen

recently while "toying" with some system files (which i shouldn't have) i deleted my kindle fire package installer thinking that i could still use my
google play installer well i was wrong . so long story short i wiped my system using twerp now ever time i run at 4000 (normal boot) im stuck at title screen and cannot connect to usb.
Key notes:
1.I have twerp
2.my entire system is blank from what i know (although it has title screen and basic boot)
3.im stuck on title
4.i have a usb cable for it (not factory cable)
5.im scared as hell

Unless you have FireFireFire (blue Kindle Fire logo) installed, you need a factory cable.

jetfire245 said:
recently while "toying" with some system files (which i shouldn't have) i deleted my kindle fire package installer thinking that i could still use my
google play installer well i was wrong . so long story short i wiped my system using twerp now ever time i run at 4000 (normal boot) im stuck at title screen and cannot connect to usb.
Key notes:
1.I have twerp
2.my entire system is blank from what i know (although it has title screen and basic boot)
3.im stuck on title
4.i have a usb cable for it (not factory cable)
5.im scared as hell
Click to expand...
Click to collapse
If you used KFU to flash TWRP and root then it is my understanding that you have FFF. Excuse me if this is a silly question, but why not just mount sdcard in recovery, place a ROM on your internal storage, and gapps, and then flash both of them after doing the necessary wipes? You may lose some if not all of your data, but at least you Kindle will be fixed
Let me know if you need more detailed instructions.
Sent from my Kindle Fire with Tapatalk 2

SwoRNLeaDejZ said:
If you used KFU to flash TWRP and root then it is my understanding that you have FFF. Excuse me if this is a silly question, but why not just mount sdcard in recovery, place a ROM on your internal storage, and gapps, and then flash both of them after doing the necessary wipes? You may lose some if not all of your data, but at least you Kindle will be fixed
Let me know if you need more detailed instructions.
Sent from my Kindle Fire with Tapatalk 2
Click to expand...
Click to collapse
It may have taken me ages to reply to you, but that is indeed what I did I was like :"how did I not think of this " lol I may be late but thankyou.

jetfire245 said:
It may have taken me ages to reply to you, but that is indeed what I did I was like :"how did I not think of this " lol I may be late but thankyou.
Click to expand...
Click to collapse
Glad it worked for you

Do you have to install BOOT MENU every time before you update a Custom ROM?

Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Boot Menu MUST be installed BEFORE installing this ROM or you will brick your Fire TV. Boot Menu and ClockworkMod are NOT the same thing.
You MUST first have installed Pre-Rooted ROM version 51.1.4.0 at some point before installing this version. You don’t have to downgrade to 51.1.4.0 if you are running a newer pre-rooted ROM. You just can’t skip from 51.1.3.0 or older straight to this version.
md5sum: de2ab7f2d3072e10d3e592b73ca52750
Released: 4/15/2015
Click to expand...
Click to collapse

Neo3D said:
Do you have to install BOOT MENU every time before you update a Custom ROM?
http://www.aftvnews.com/roms/
Click to expand...
Click to collapse
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now

will4958 said:
If I remember right, you only have to install the custom boot menu when applying either of the most recent updates. However, if you downgrade back to an older update that doesn't require the menu and decide to go back to the one of the newer updates, then you have to re-install the custom boot menu. I think it's only a requirement for the last two updates that're at the top of the list in the updates thread, the ones listed below don't require the custom menu. I know from experience that after install the custom menu and then the latest update, then going back to the build I was on before that, I lost the menu. Either way, though, just make sure you install the custom menu BEFORE applying the latest update, otherwise you'll get stuck on the Amazon logo screen, and the only way to get into recovery mode is to do the Fire TV version of the three finger salute: Alt+Shift+Print Screen, I think, and keep doing it til you get to recovery. I apologize in advance if I confused you a little, sometimes I get a little informative and ramble, kind of like what I'm doing right now
Click to expand...
Click to collapse
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?

Neo3D said:
I had Boot Menu previously installed but didn't reinstall it again before updating to this latest Custom ROM and now my AFTV is in a boot loop. I also noticed that the Boot Menu is now gone?
Is there anything I can do to fix this?
I can go into Recovery using the three finger salute, thanks!
But what do I do next?
Click to expand...
Click to collapse
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.

will4958 said:
Cool. Glad you were able to get back in there. When it happened to me, my arms got a little sore from having to smash the keyboard so much, but the keyboard is a little on the stiff side, so it didn't take much. Anyway, at this point you want to restore a backup you hopefully made, install the custom boot menu, then install the new update again. On the chance you don't have a recent backup, or any backup handy, just install any the last version you were on that didn't require the menu, reboot to make sure it took, install the custom menu, flash the new update, then reboot. That should get you back up and running.
Click to expand...
Click to collapse
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?

Neo3D said:
Thanks! Unfortunately, I didn't make any backups of before when it was working.
How do I copy the Custom ROM zip file onto the AFTV?
Click to expand...
Click to collapse
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.

will4958 said:
Since you're only able to get into recovery mode at this point, you'd have to copy the ROM to a flash drive. If you have a USB hub, preferably a powered one, plug the flash drive into the hub, along with a usb/wireless keyboard if you have either. The Fire TV should automatically detect the flash drive as long as it's formatted with a Windows file format. At that point, installing the update is just like doing it from the Fire TV itself, but since you're using a flash drive you'll want to select the install from USB option. I forget exactly what it's called, but you'll know it when you see it. The only thing that'll pop up will be the custom ROM you copied to the drive.
Click to expand...
Click to collapse
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).

Neo3D said:
So, I copy my zip file onto a USB drive and plugged it into a hub into the AFTV. However, I can't find any option to access the USB drive from inside Clockwork?
When I go into /sda1/ it doesn't actually show the contents of the USB drive. I'm using the same USB drive that I normally have plugged into the AFTV (for downloading videos from Genesis).
Click to expand...
Click to collapse
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you

will4958 said:
Your flash drive has to be formatted to FAT or NTFS, both of which are Windows file system formats. Once you plug the drive into the Fire TV or hub, it will automatically detect it. Give it a few seconds to do so, then select Install zip. On the next screen you'll see the usual methods for installing a ROM, but now you should also see an option that says Choose zip from USB, or something similar to that. Once you choose it, the next screen should show the zip file for the custom ROM you placed on your flash drive, but the drive has to be formatted as a FAT32 or similar Windows file system drive for the Fire TV to see the drive. And yes, I know it sounds a little silly considering the Fire TV runs on a version of Linux, but that's technology for you
Click to expand...
Click to collapse
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/

Neo3D said:
Here are the options that I see?
Choose zip from /sdcard
Choose zip from last install folder
Install zip from sideload
My recovery is version: 6.0.5.1.4a
http://www.aftvnews.com/recovery/
Click to expand...
Click to collapse
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.

will4958 said:
Yeah, it looks like it's not detecting your flash drive. Did you format the drive to something like FAT, FAT32, or NTFS? If not, it won't detect the drive, and you won't be able to install the ROM from the flash drive. Also, if the drive is already plugged in, you could try pulling it out then reinserting it again. But like I said, none of that will work if the drive isn't formatted properly.
Click to expand...
Click to collapse
Yes, it is NTFS?

Neo3D said:
Yes, it is NTFS?
Click to expand...
Click to collapse
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.

will4958 said:
I'd say if it's not detecting it with that format, try formatting as FAT32. I just checked a drive I've used before for the same thing, and it's formatted as FAT32 and it still has a recent update on it I tried before.
Click to expand...
Click to collapse
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?

Neo3D said:
Thank you! I will try that.
So, I guess I should have re-installed BOOT MENU before upgrading the custom ROM.
It kind of doesn't make sense to have to re-install BOOT MENU if you already have it running before upgrading?
Click to expand...
Click to collapse
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.

will4958 said:
I can't remember the reason the custom boot menu requirement before applying the new update, but it does give you a couple different options when booting. Can't remember what they are, but the logo looks cool. As far as having to reinstall the custom boot menu, though, it's only a requirement for the two newest updates on this forum, and the way the thing is programmed it's made to look for that custom menu when booting. It only takes a couple minutes to install the menu, and after that you're back to watching Netflix, playing Dead Trigger, or whatever.
Click to expand...
Click to collapse
Yea, it was confusing whether or not the BOOT MENU needed to be re-installed before EVERY new update when you already have it installed and working.

i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)

aHcVolle said:
i did not install the bootmenu again when i did update from 1.4.1 to 1.4.3 nor from 1.4.3 to 1.5.0.
I just installed the zip file via recovery.
Why dont you boot to recovery and adb push the update .zip file to your internal storage? IIRC adb is enabled in recovery,
(since you seem to be having problems with the usb drive)
Click to expand...
Click to collapse
Yea, I didn't think I had to either since my BOOT MENU had been installed and working....but I got stuck in a boot loop after upgrading??
I ended up using SIDELOAD to push a zip to the AFTV: https://www.youtube.com/watch?v=dWXHD7PlaQc
Thanks!

Update without using PC

So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?

Slayerkodi said:
So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?
Click to expand...
Click to collapse
What are you on now? 3.x or 5.0.0? If you're on 3.x, I'm not completely sure your idea will work. If you're on 5.0.0 it might.
Weird stuff happens between major build numbers.

I'm now on 5.0.2, what about somehow running windows or Linux from my phone and connect adb that way would it work? I could otg to otg or otg to USB, just not sure it would work

Depends on if TWRP can flash partitions that updates need to flash. I believe TWRP will just flash system, vendor and boot.
Slayerkodi said:
So my laptop broke a while ago and I now have no way of updating without losing root which is not an option for me. So I've tried using android to android TV adb/fastboot commands over network but android to android adb doesn't seem to work at all. So while digging on what I could possibly do I've come up with an idea but not sure it will work. I have the nvidia shield TV (1st gen) 16gb version currently on 3.3, rooted with twrp installed. I found this:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
So my idea is to use these instructions to install the hacked twrp (Darcy) and then install update ota from there and then install root? Will this work?
Click to expand...
Click to collapse

Yeah Ive been trying all night - tried with running Linux on android which worked well, I installed adb tools, run the server, connected with otg and USB and 'adb devices' shows nothing attached. I got network debugging to connect but I know that's pointless as it won't have WiFi connectivity once its in recovery where its needed to push twrp. Maybe one day

So went and borrowed a mates charger and all good now but I'm planning to get rid of my laptop and the only thing holding me back is this process of rooting and installing twrp, if I could do this on the shield itself or us another android device to push commands this would be a big help as then I really don't need a laptop at all

First, update TWRP to the unofficial version (latest), you can then download the OTA and supersu .zip in your phone and copy them to an external usb flash drive with an OTG usb cable/adapter.
You can check in your phone the files inside the compressed OTA package.
First do factory reset (if 16 gb model i would also wipe media)
Flash OTA from TWRP
Flash supersu right after (if you get an error that you cant write to data or similar then a reboot to recovery is a must)
Cross fingers to succesfully reboot to twrp again, then flash supersu and reboot system.
Root is systemless, be carefull to not do another factory reset or you'll wipe root too.
If twrp is gone, you must use a Windows machine because Nvidia provides fastboot drivers for when shield tv is booted up in bootloader or fastboot mode. Haven't seen linux drivers for that.
ADB is not really of much help or use but fastboot is. In case TWRP dissapears then the only way is flashing it back with fastboot and to boot into it from command line too.
I've installed Full Android Nougat on my 2015 shield tv and have gone back to stock and then again to full android. I also wanted to find a way to not be dependant of a pc/laptop, unfortunately there isn't one yet as far as i know. Also if you forget and do a factory reset from settings then root will be gone and no way to easily boot into TWRP again, you'll again need fastboot.
I have done enough tests and everything i mentioned i have done it myself or has happened to me and eather way or another I've find myself always having to use my laptop.
Enviado desde mi Moto X via Tapatalk!

lavero.burgos said:
First, update TWRP to the unofficial version (latest), you can then download the OTA and supersu .zip in your phone and copy them to an external usb flash drive with an OTG usb cable/adapter.
You can check in your phone the files inside the compressed OTA package.
First do factory reset (if 16 gb model i would also wipe media)
Flash OTA from TWRP
Flash supersu right after (if you get an error that you cant write to data or similar then a reboot to recovery is a must)
Cross fingers to succesfully reboot to twrp again, then flash supersu and reboot system.
Root is systemless, be carefull to not do another factory reset or you'll wipe root too.
If twrp is gone, you must use a Windows machine because Nvidia provides fastboot drivers for when shield tv is booted up in bootloader or fastboot mode. Haven't seen linux drivers for that.
ADB is not really of much help or use but fastboot is. In case TWRP dissapears then the only way is flashing it back with fastboot and to boot into it from command line too.
I've installed Full Android Nougat on my 2015 shield tv and have gone back to stock and then again to full android. I also wanted to find a way to not be dependant of a pc/laptop, unfortunately there isn't one yet as far as i know. Also if you forget and do a factory reset from settings then root will be gone and no way to easily boot into TWRP again, you'll again need fastboot.
I have done enough tests and everything i mentioned i have done it myself or has happened to me and eather way or another I've find myself always having to use my laptop.
Enviado desde mi Moto X via Tapatalk!
Click to expand...
Click to collapse
Ive found myself in that situation, no root, and no way to boot to twrp, after a while searching, found that theres a keyboard combination that reboots the shield (also works on ouya, nexus, maybe standard android?), and pressing this same key combination one or three times after the reboot, as soon as first logo shows, boots the shield to recovery
Combination = alt + print screen + i (no root, no adb required, was a life saver)
Edit
Usb keyboard required (maybe 2.4ghz keyboard might work to) , as theres no bluetooth/wifi during boot
Edit
Well actually, folks can test the initial reboot with a bluetooth keyboard, just wont be able to use the key combination during boot, and im pretty sure if the shield reboots, then the 'boot to recovery' aspect should work too(with usb keyboard)
Edit
Curious to know if this also works on the 2017 model

Would it be possible to downgrade from Nougat 5.1 back to Marshmallow 3.3?

savagepagan said:
Would it be possible to downgrade from Nougat 5.1 back to Marshmallow 3.3?
Click to expand...
Click to collapse
I wouldn't recommend that. I've seen like 5 users that have soft and hard bricking their Shield doing so.
If you flash full recovery images or OTA that contain and flash MM or a different model bootloader you will brick your device.
Enviado desde mi Moto X mediante Tapatalk

What you could do... Is before updating to Nougat. Make a hard backup of your SSHD (Sorry 16Gb Users), following the first Page of the SSHD to SSD Migration Threads.
And then just use that to roll back. It will also save your arse in the worst nightmare scenario. When you having just attempted to roll back to a lower version, and then find yourself with a Brick.

Unbrick Fire TV Stick 4K. Help!

Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!

Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
I think this is where I would start. Hope it helps.
https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459

Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
Hi, I am facing the same issue, did you manage to get it fixed??

Simpson84 said:
Hello! I was trying to clone one Fire TV Stick 4K to another. I've backup with TWRP from one FireTV Stick 4K next partitions: System, System Image, Vendor, Vendor Image, Data, Boot. Then was trying to restore all of them on another stick with changing backup folder serial number and when another FireTV Stick 4K has been rebooted it stuck on the FireTV logo ((( And I don't know what to do with it know.
I was trying to flash Fire TV Stick 4K (mantis) Prerooted Stock Images [6.2.6.8_r1] but receive an error "Failed to mount '/vendor' (Invalid argument)"
Could you help, please? Thank you!
Click to expand...
Click to collapse
I had the same problem in the past before, try flashing the original stock rom in TWRP and reboot. Rerun the exploit and push this zip file to the 4K Fire Stick.
Original Stock Rom: https://drive.google.com/file/d/1-8Md0W6V7UNKkGb1uS2WfIKjjevEEaN7/view?usp=drivesdk
Also if you're having problems pushing the zip, try adb shell, twrp sideload, then adb sideload (the zip file). It'll say copying system image unconditionally along with the vendor images so you shouldn't get the failed to mount vendor anymore and the brick will be gone. Let me know if you have any questions.

Got the same problem. Did this work?
---------- Post added at 04:43 AM ---------- Previous post was at 04:14 AM ----------
Can you also help me with some of the terminology used here - for example on phones I have rooted in the past, I have used backup/restore and install many times but I am not sure how to do this "try adb shell, twrp sideload, then adb sideload (the zip file)".
On the advanced menu of TWRP I see Copy Log, File Manager, Terminal and ADB Sideload. When I choose the last on the list,ADB Sideload the screen gives me another failed to mount /vendor message with "Starting ADB sideload feature, which I am not sure what to do with any of this section of TWRP and if TWRP is to be used rather than a PC to do this. Thanks

theflashfromthecw said:
I had the same problem in the past before, try flashing the original stock rom in TWRP and reboot. Rerun the exploit and push this zip file to the 4K Fire Stick.
Original Stock Rom: https://drive.google.com/file/d/1-8Md0W6V7UNKkGb1uS2WfIKjjevEEaN7/view?usp=drivesdk
Also if you're having problems pushing the zip, try adb shell, twrp sideload, then adb sideload (the zip file). It'll say copying system image unconditionally along with the vendor images so you shouldn't get the failed to mount vendor anymore and the brick will be gone. Let me know if you have any questions.
Click to expand...
Click to collapse
I resolved the problem after sleeping on the problem and found you can use the Install option to restore the factory image even though you get the same /vendor error initially.
I'd still like to learn how to issue ADB push and ADB commands to this stick considering the only way I can see to get to the TWRP menu is to use a mouse via an OTG USB connection and that blocks a PC from connecting and supplying mouse support at the same time - unless I'm really missing something.

Donphillipe said:
I resolved the problem after sleeping on the problem and found you can use the Install option to restore the factory image even though you get the same /vendor error initially.
I'd still like to learn how to issue ADB push and ADB commands to this stick considering the only way I can see to get to the TWRP menu is to use a mouse via an OTG USB connection and that blocks a PC from connecting and supplying mouse support at the same time - unless I'm really missing something.
Click to expand...
Click to collapse
How did you get the factory image onto the stick? I'm stuck with no recovery on the stick currently and ADB is not recognized in TWRP.

I plugged the Windows formatted USB stick in the PC (eFat works for read like this but has problems with backing up to it but you are OK reading off an eFat), downloaded the zip file to the stick., plugged the stick into the powered hub where the mouse is plugged in and the hub is powering the AFS through an internal or extra OTG, powered off and back on the stick which booted to TWRP, clicked cancel to get TWRP Menu, clicked Install, clicked Select Storage, looked at the file sizes of all the storage options and selected the one that matched the total capacity of the stick, then opened the folder where the zip restore file was, selected the full zip restore image and slid the slider to the right with the mouse to begin install. I then saw the text going across the TV screen stating which directories were being restored, then it stopped, then I selected the option to wipe the two caches and clicked the reboot option and the the firestick rebooted with no TWRP menu this time but back to the black and white menu, then to the orange over white background where the device takes a long time to go through its initialization sequence and then after a few minutes it boots back into the option to pair the remote, sign on and do all that stuff again. I did a complete initial configuration again and checked out the quality of the restore by signing in and poking around, then got up my nerve and applied the exploit once more.

Hi! I have exactly the same problem as @Simpson84. I've cloned the 4 partitions (system image, vendor image, data and boot) from one 4K stick to another (same model) via TWRP backup / restore, and now the stick which I've restored into is stuck at the black screen with with fire tv logo (does not reach the white and orange screen boot with the 3 dots). I have access to TWRP and I've already tried everything I could remember:
- flash stock images (update-kindle-mantis-NS62* - tried with several versions)
- wiping cache, dalvik and data
- flash rooted images
- re-run exploit again
- rename backed-up partitions from win to img and flash with fastboot
However, the result is always the same. The normal boot does not get past the black screen with white logo.
Does anyone know any other possible solution?
Thanks!

rpmuploads said:
Hi! I have exactly the same problem as @Simpson84. I've cloned the 4 partitions (system image, vendor image, data and boot) from one 4K stick to another (same model) via TWRP backup / restore, and now the stick which I've restored into is stuck at the black screen with with fire tv logo (does not reach the white and orange screen boot with the 3 dots). I have access to TWRP and I've already tried everything I could remember:
- flash stock images (update-kindle-mantis-NS62* - tried with several versions)
- wiping cache, dalvik and data
- flash rooted images
- re-run exploit again
- rename backed-up partitions from win to img and flash with fastboot
However, the result is always the same. The normal boot does not get past the black screen with white logo.
Does anyone know any other possible solution?
Thanks!
Click to expand...
Click to collapse
Redo the unlock process.
Then format data (type "yes) and then push your rooted rom and magisk back to mantis /sdcard.
Reflash
Wipe dalvik and cache
Reboot
Don't rename any partitions just let kamikiri do its work

rpmuploads said:
Does anyone know any other possible solution?
Click to expand...
Click to collapse
If you can get into twrp, maybe try the 'format' data option, type yes, then wipe system/vendor, cache, dalvik, then install the kamakiri.zip and the latest stock rom followed by magisk.

Many thanks both to @Bertonumber1 and @Sus_i
I tried your suggestions but the 4k stick keeps stuck at the black and white logo. I have another two 4k sticks, one for android development and testing and another one for the living room, so I don't really need it. I just wanted to fix it for the challenge and because it seems that there's nothing wrong on the hardware side.
You can see in the attached images my attempt to recover.

rpmuploads said:
Many thanks both to @Bertonumber1 and @Sus_i
I tried your suggestions but the 4k stick keeps stuck at the black and white logo. I have another two 4k sticks, one for android development and testing and another one for the living room, so I don't really need it. I just wanted to fix it for the challenge and because it seems that there's nothing wrong on the hardware side.
You can see in the attached images my attempt to recover.
Click to expand...
Click to collapse
Looks almost ok from here.
Only thing to remember is that you've to flash magisk behind the stock rom, as the last step just before the reboot... If you flash Magisk infront the rom, Magisk gets overwritten during the stock boot image flash.
In case that won't help, I would flash the kamakiri GPT-fix from here:
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
NOTE: There have been multiple reports of devices with serial numbers containing VM190 or higher being shipped with DL-Mode disabled in BROM. These devices cannot be unlocked using kamakiri. These devices do not show up at all on USB when...
forum.xda-developers.com
Extract the two files from the zip in the kamakiri folder, make sure that the gpt-mantis.bin file goes to the bin folder... then run this using the fireISO:
./gpt-fix.sh
(you need to short again).

Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.

rpmuploads said:
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.
Click to expand...
Click to collapse
Unfortunately, there isn't a lineage rom for the 4k.
Have you tried to install a rom + magisk behind the gpt-fix?
If yes, I can't think of a reason why the stick won't boot at this point.

rpmuploads said:
Thanks @Sus_i. Indeed I'm always flashing the rom first and then magisk.
I've shorted the stick again and ran successfully ./gpt-fix.sh but it's still stuck at the black and white logo.
Probably I'll try to install the LineageOS to see what it looks like.
Click to expand...
Click to collapse
You may try returning the stick to stock,
fire stick 4k - return to stock?
Hello, can anyone link me to where I will find the windows drivers for the Firestick in fastboot mode? I have followed the above and entered fastboot which can be seen here: However powershell doesn't display and connected devices and I am...
forum.xda-developers.com
lock the bootloader again and do the whole process over.
I had this problem before with mantis and the only way I could get it to work again (Unlocked/Rooted) was by locking it down back to stock, letting the stick do all the ota updates :
Then after doing the short process over.
Adb Push to /sdcard
6.2.7.1 prerooted (or a rom of your choice)
Magisk 21.1 zip
Install prerooted first
Then flash magisk
Wipe dalvik/cache
Reboot
It's a pain in the ass and a long way to go but it workes in my case anyway. If your sticks not working then it's worth a shot

Thanks @Sus_i. Yes, I've tried to install a rom + magisk behind the gpt-fix, but it is still stuck in the black and white logo.
Thanks @Bertonumber1, I'll try your suggestion and I'll let you know.

Bertonumber1 said:
You may try returning the stick to stock,
fire stick 4k - return to stock?
Hello, can anyone link me to where I will find the windows drivers for the Firestick in fastboot mode? I have followed the above and entered fastboot which can be seen here: However powershell doesn't display and connected devices and I am...
forum.xda-developers.com
lock the bootloader again and do the whole process over.
I had this problem before with mantis and the only way I could get it to work again (Unlocked/Rooted) was by locking it down back to stock, letting the stick do all the ota updates :
Then after doing the short process over.
Adb Push to /sdcard
6.2.7.1 prerooted (or a rom of your choice)
Magisk 21.1 zip
Install prerooted first
Then flash magisk
Wipe dalvik/cache
Reboot
It's a pain in the ass and a long way to go but it workes in my case anyway. If your sticks not working then it's worth a shot
Click to expand...
Click to collapse
Thanks @Bertonumber1, I tried your suggestion, locking the bootloader again and doing the whole process over, but it still doesn't pass the b&w logo. I've attached step by step images.

@rpmuploads
Just curious, have you tried to boot the stick without the otg stuff? Powered via the orig. usb cable/power supply?

Sus_i said:
@rpmuploads
Just curious, have you tried to boot the stick without the otg stuff? Powered via the orig. usb cable/power supply?
Click to expand...
Click to collapse
yep , id second that .....its the only thing else that i can see stopping your 4K booting up as everything else seems bang on.