Develop Bugs

[Q] Can't get KF to root

What I'm using:
Kindle Fire v6.3.1
KFU v0.9.6
Android Composite ADB Interface driver v7.0.0.1
I'm using a cable that I had on hand
I've tried moving the KFU folder to C:\KFU and I've uninstalled and reinstalled drivers several times but I can't get this thing to root.
Below is the process log of installing permanent root from KFU. Every time I have run this, I get the notice about fastboot using a different device than ADB. Device manager shows Android Composite ADB Interface and not "Kindle" or "Amazon". I was able to manually install the Superuser.apk. When I run the command adb root, I get the message "adb cannot run as root in production builds".
Any help would be appreciated.
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
3219 KB/s (510876 bytes in 0.154s)
The kindle has been told to reboot in Fastboot Mode.
twrp.img has been found.
fff.bin has been found.
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
sending 'bootloader' (243 KB)... OKAY [ 0.066s]
writing 'bootloader'... OKAY [ 0.054s]
finished. total time: 0.121s
Installing TWRP...
sending 'recovery' (4856 KB)... OKAY [ 1.226s]
writing 'recovery'... OKAY [ 1.436s]
finished. total time: 2.664s
Setting Recovery Bootmode.
... OKAY [ 0.663s]
finished. total time: 0.664s
rebooting...
finished. total time: 0.001s
Please wait...
<idme> write 4000 to offset 0x1000
341 KB/s (22364 bytes in 0.064s)
Attempt to remove root checker.
mv: can't rename '/system/bin/check_rooted': No such file or directory
Please wait...
Installing Superuser.apk
Error: Could not access the Package Manager. Is the system running?
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
Press any key to continue . . .

You don`t have to root it just flash this rom from my instructions http://forum.xda-developers.com/showthread.php?t=1923010 all roms are rooted as long as you have fff and twrp simply just flash the rom.
---------- Post added at 07:46 AM ---------- Previous post was at 07:27 AM ----------
Just start from the section first backup and flashing rooted stock.

Before I do this, I just want to make sure that the data is not wiped and I need to create a physical image of the device with the data as is. I'm particularly interested in preserving the state of the internet history. Also, once flashed can I revert back to stock?
Thanks for your guides, they are very helpful.

No harm will come to your existing data, no wipes are needed to apply Modaco over your present system. Always make a backup prior but you will find if you follow my instructions that nothing has change except that you`re rooted and have Gplay in your apps. As far as reverting back to unrooted stock or flashing update.zip do a full wipe of everything but your sdcard most often users fail to do this resulting in soft brick.

[Q] Can't get fastboot even with cable.

Windows 7, completely fresh installation, plug powered down kindle fire in with fastboot cable and just boots regularly. I cannot figure this out at all! Please help.

Update
Okay, so I was able to switch back to an ubuntu system and here is what I have:
I can enter fastboot mode and perform operations. Following the twrp - second bootloader guide results in a boot loops and I am unable to get past the orange kindle fire logo, it doesn't do anything at all.
Under linux does anyone know what I need to do to get this thing working again!? I have never had so many problems with a device! Ahhh, wish I hadn't tried to add wallpapers.
The issues started when I tried to push framework.odex and services.odex and it didn't go.

Solved
Okay, for anyone running Ubuntu like I was and stuck in a boot loop here's what I did:
Download stock recovery.img and boot.img.
Download KFHD_SRT V ??? tool or any other stock system.img.
Flash the three files using fastboot, then reboot will give you all stock restore.
sudo fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 66.375s]
writing 'system'...
OKAY [ 62.345s]
finished. total time: 128.720s
sudo fastboot -i 0x1949 flash recovery recovery.img
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 1.488s]
finished. total time: 2.098s
sudo fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.628s]
writing 'boot'...
OKAY [ 1.046s]
finished. total time: 1.674s
sudo fastboot -i 0x1949 reboot
rebooting...

[Q] Kindle Fire 2 won't boot or charge

Earlier this week my daughter handed me her Kindle Fire saying it was hanging on boot and did not seem to be charging.
Background
Originally purchased as a Kindle Fire I replaced the motherboard when the USB socket broke away and it could not be soldered back (pad was missing). I purchase and fitted a replacement motherboard from the US and on arrival it turned out to be a Kindle Fire 2 motherboard.
The only differences apart from the faster processor and more RAM was that the socket for the ambient light sensor was missing. Anyhow I fitted the board and all has been fine for a year.
Symptoms
When switched on it displayed the battery symbol displayed so it was plugged into a 1Amp charger and left overnight. The next morning it was displaying the standard orange Kindle Fire boot logo no animation.
I disconnected from the power supply and did the 20 second power button reset. When it was powered back on each time the orange Kindle Fire logo was displayed with no animation and there it would stop. Disconnected from the power it would stay in the state for over an hour making me think that the battery had a reasonable charge although the charging light never actually went green. Eventually it would go back to the critical battery state as seen initially.
I have repeated the overnight charge process and reset several times with the same results. Whilst plugged in the amber charge light was displayed but never went green.
At this point I decided that it must be because it was not getting past the bootloader and as a result it was not reaching the proper state to be able to charge properly. So I thought it might be a problem with the software and decided to re-flash everything (maybe the battery had died during OTA update I thought) and I purchased a factory/fastboot cable.
I used the tools and images in the KFFirstAide several times using the 10.2.1 and 10.2.3 images (example shown below). But each time the results where the same after a reset the device would either go straight to the static orange Kindle Fire logo or show the battery symbol apparently charge a little at some point boot to the orange Kindle Fire logo.
At this point I am thinking it is a problem with the battery but before I go and spend £30 on a device where I have already replaced the motherboard for $50 and I want to be sure there are no other options, the current used price on ebay seems to be around £50-70 for a similar device.
My daughter is happy to give up on it but my curiosity is piqued and I want to know what is actually wrong and are there any more diagnostics.
I am unix fluent (software developer for 28 years, my first linux distro (slackware was on 40 x 3.5Mb disks!) so if necessary I could switch to using linux tools if that helps.
Is it worth checking the battery with a multi meter?
Code:
C:\Kindle Fire Restore\10.2.3>fastboot -i 0x1949 getvar product
product: Otter2-Prod-04
finished. total time: 0.004s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
target reported max download size of 486539264 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.234s]
writing 'bootloader'...
OKAY [ 0.047s]
finished. total time: 0.312s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash boot 10.2.1\boot.img
target reported max download size of 486539264 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.515s]
writing 'boot'...
OKAY [ 0.905s]
finished. total time: 1.420s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash recovery 10.2.1\recovery.img
target reported max download size of 486539264 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.905s]
finished. total time: 1.420s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash system 10.2.1\system.img
target reported max download size of 486539264 bytes
sending sparse 'system' (465730 KB)...
OKAY [ 17.940s]
writing 'system'...
OKAY [ 51.563s]
sending sparse 'system' (312222 KB)...
OKAY [ 12.293s]
writing 'system'...
OKAY [ 35.334s]
finished. total time: 117.161s
C:\Kindle Fire Restore>fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [191.877s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.127s]
erasing 'cache'...
OKAY [ 76.959s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.140s]
finished. total time: 269.108s

Hard Bricked Kindle Fire HD 8.9 jem BC09

Hello,
I've hardbricked a Kindle Fire HD 8.9 jem BC09 which was running 8.5.1 before it became a paperweight.
I successfully rooted the device with Bin4rys method, at which point I followed cyanogenmod's directions on installing the bootloader(otter2 CM install instructions on their website)
I verified the MD5 checksum for the bootloader before proceeding.
Here's the results of my mishap:
Volume in drive C is Windows7_OS
Volume Serial Number is 3A6D-6FAB
Directory of C:\Users\User\Downloads
10/10/2015 03:17 PM <DIR> .
10/10/2015 03:17 PM <DIR> ..
10/10/2015 02:29 PM <DIR> Old DLs
10/10/2015 03:17 PM 8,349,292 otter2-freedom-boot-10.4.6.img
10/10/2015 03:17 PM 8,349,292 otter2-twrp-2.6.3.1-recovery.img
10/10/2015 03:13 PM 232,908 otter2-u-boot-prod-10.2.4.bin
04/29/2007 06:12 AM 591,872 WinMD5.exe
10/10/2015 03:15 PM 268,376 winmd5free.zip
5 File(s) 17,791,740 bytes
3 Dir(s) 370,367,225,856 bytes free
C:\Users\User\Downloads>fastboot -i 0x1949 flash bootloader otter2-u-
boot-prod-10.2.4.bin
< waiting for any device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.020s]
writing 'bootloader'...
OKAY [ 0.040s]
finished. total time: 0.060s
C:\Users\User\Downloads>fastboot -i 0x1949 flash recovery otter2-twrp
-2.6.3.1-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8153 KB)...
OKAY [ 0.437s]
writing 'recovery'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 flash boot otter2-freedom-
boot-10.4.6.img
target reported max download size of 1006632960 bytes
sending 'boot' (8153 KB)...
OKAY [ 0.452s]
writing 'boot'...
OKAY [ 0.562s]
finished. total time: 1.014s
C:\Users\User\Downloads>fastboot -i 0x1949 oem recovery
...
OKAY [ 0.000s]
finished. total time: 0.000s
C:\Users\User\Downloads>fastboot -i 0x1949 getvar product
< waiting for any device >
Click to expand...
Click to collapse
At the point where I attempted to reboot into recovery, the device became completely bricked. No response to power on, etc.
As I've been browsing for the past hour it seems to me that this device is virtually unbrickable aside from sending it to Amazon. I have contacted "Chris" at [email protected] and am awaiting his response. In the meantime, if anyone else has any ideas of how to proceed please let me know!
Regards,
siriu5

You can check following options:
1. Send back to Amazon (If it's under warranty).
2. Replace the mother board (You can get at $50 online).
3. Follow this thread: http://forum.xda-developers.com/showthread.php?t=2581124 . (only if you are good at SMD soldering).

You reported this as a bug on the cyanogenmod wiki ( https://jira.cyanogenmod.org/browse/WIKI-194 ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
https://wiki.cyanogenmod.org/w/Install_CM_for_jem has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.

PsychoI3oy said:
You reported this as a bug on the cyanogenmod wiki ( ) and though the text mentions 'jem' several times, you linked to the otter2 install page.
x has files for the jem (as kfhd8) in 'step 2'...
I don't know how to fix the device but perhaps knowing that the files flashed were for the "Kindle Fire 2nd gen (otter2)" instead of the "Kindle Fire HD 8.9 (jem)" will help someone else in the debugging process.
Click to expand...
Click to collapse
Yeah, I just caught this. Definitely my own mistake. My problem was I google searched "cyanogenmod install kindel hd fire gen 2" and tried the first link that showed up. Dope.
Anyone want a bricked KFHD2? I'll send if you pay for shipping. Cheers!

Fire TV 1 bricked (bootloader unlocked)

I tried an software update to the newst prerooted image from rbox but unfortunatelly installed Magisk V20 directly after it (without reboot).
After reboot my Fire TV 1 stopps now at the first white Amazon logo.
Fastboot via USB-A-to-A is working
dḿesg shows the follwing:
[10671.732229] usb 1-2: new high-speed USB device number 44 using xhci_hcd
[10671.887334] usb 1-2: New USB device found, idVendor=1949, idProduct=0401
[10671.887339] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10671.887343] usb 1-2: Product: FireTV
[10671.887346] usb 1-2: Manufacturer: Lab126
[10671.887348] usb 1-2: SerialNumber: xxxxxxxxxxxx
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
This is strange since I unlocked the bootloader years ago.
Is there hope for my Fire TV 1 or did I finally brick it?
Update:
"fastboot getvar unlocked" gives me:
"unlocked: "

veeroohre said:
This is strange since I unlocked the bootloader years ago
Click to expand...
Click to collapse
Magisk won't work on the first fireTV
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.

Sus_i said:
Flash a clean boot.img (the unlocked one in the prerooted rom zip) with fastboot onto boot partition.
Click to expand...
Click to collapse
Would love to do that, but as mentioned I get the error message "flashing not allowed for locked hw".
I read that sometimes fastboot is the problem and not the hardware. Could that be? I'm on Ubuntu LTS 18.04.

You need to reflash the boot. Extract the boot_unlocked.img from bueller-5.2.7.3-rooted_r1.zip and flash it from the command line when you have the FireTV connected with the USB A-A cable.
fastboot flash boot boot_unlocked.img
EDIT: Here's my thread about it: https://forum.xda-developers.com/fire-tv/help/warning-attempting-to-flassh-magisk-16-t3778096

Sizzlechest said:
fastboot flash boot boot_unlocked.img
Click to expand...
Click to collapse
As I wrote, unfortunately this does not work:
< waiting for any device >
target reported max download size of 805306368 bytes
sending 'boot' (6460 KB)...
OKAY [ 0.206s]
writing 'boot'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.217s
Any other ideas?
Update:
Under Windows "fastboot devices" is not listing anything.

veeroohre said:
When I try to flash something I get the following message:
target reported max download size of 805306368 bytes
sending 'recovery' (9544 KB)...
OKAY [ 0.303s]
writing 'recovery'...
FAILED (remote: flashing not allowed for locked hw)
finished. total time: 0.314s
Click to expand...
Click to collapse
Maybe try 'fastboot boot recovery.img' instead of a flash.
veeroohre said:
Any other ideas?
Click to expand...
Click to collapse
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
If yes, you may be able to follow this Guide.
Take a look here too.

Sus_i said:
Maybe try 'fastboot boot recovery.img' instead of a flash.
Click to expand...
Click to collapse
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
Sus_i said:
Connect the box via usb a-a cable to linux, boot the box and watch out if any mounted partitions pop up.
Click to expand...
Click to collapse
With "fdisk -l" no partition shows up.
I think my box is dead :crying:

veeroohre said:
Doesn't work:
Code:
downloading 'boot.img'...
OKAY [ 0.304s]
booting...
FAILED (remote: Restricted command
)
finished. total time: 0.312s
With "fdisk -l" no partition shows up.
I think my box is dead :crying:
Click to expand...
Click to collapse
It seems so.
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill

Sus_i said:
Writing a new boot.img to the fireTVs eMMC via hardware mod is probably a solution, but that's a bit overkill
Click to expand...
Click to collapse
You're right. I thought about it, too. But too expensive and time consuming for such an old device. Probably I'll buy a new one. Although I hate to dump hardware which in principle still works .