Develop Bugs

i wiped OS ,please help me.

i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.

adeeb101 said:
i spent 3 days trying to fix my kindle but i couldn't
first i rooted my kindle ,then by mistake i wiped OS,so the kindle stuck on logo.then i login recovery mode and installed the new version 6.3.2
but now i lost the root and it still stuck.
i tried many times with many ways but i almost lot the hope.
Click to expand...
Click to collapse
You need a factory cable.

soupmagnet said:
You need a factory cable.
Click to expand...
Click to collapse
the problem is i''m not in USA ,its not available here
is there another way to fix it?

adeeb101 said:
the problem is i''m not in USA ,its not available here
is there another way to fix it?
Click to expand...
Click to collapse
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).

soupmagnet said:
You can make one yourself with a little skill and/or ingenuity, or you can check with @SkOrPn (I believe he ships to all over the world).
Click to expand...
Click to collapse
thank you i'll see what i can do

wait a minute, I rooted mine with a stock micro-USB cable

adeeb101 said:
thank you i'll see what i can do
Click to expand...
Click to collapse
Since I already see this coming, I'll go ahead tell you where you went wrong and how to avoid it in the future.
First off, there's really no need to "root" your Kindle Fire. The steps required to root the Kindle Fire involve installing custom recovery (TWRP in this case) to gain temporary root permissions so you can push Superuser.apk and the SU binary. However, all custom ROMs come pre-rooted, so rooting beforehand is unnecessarily redundant. Even if you wanted to keep the stock OS, there is a stock based ROM called MoDaCo that will give you what you want while saving you pretty much all the work of having to do whatever you wanted to do with a rooted stock device anyway.
Second, with custom recovery already installed, the only reason to install the 6.3.x software update from Amazon, is to revert the device to 100% stock (i.e. no root, no recovery, no custom bootloader). Where you failed is in attempting to install the update.zip without first doing a factory reset in recovery. The resulting problem will leave you with a device that has no working shell, and therefore no ability to change bootmodes or install custom recovery again.
The factory cable (mentioned earlier) puts the device in fastboot mode where you can reinstall custom recovery, custom bootloader, and change bootmodes using fastboot commands (or some script based utility), then you can use custom recovery to properly install a ROM of your choice (remembering to factory reset). It should also be noted, that you should never wipe anything in custom recovery until you have successfully used it to create a backup. Be sure to save your system partition at the very minimum, and you can always go back to delete it afterwards.

[Q] Need to get back to stock, no TWRP or recovery.

I'd like to preface this by saying I read the FAQ and did some searching here, but couldn't spot anything that sounded like my problem. I've half got an idea of what to do, but I'm quite confused and feel like some stuff needs clarifying. I apologize if this is more common than I realize, cause if it is I'm sure y'all are sick of answering questions like this.
---
I got a used Kindle Fire from a friend that came with CM10 on it. I wanted to use it for reading, but the Kindle android app was recently broken by Amazon so I reluctantly reverted it back to stock (I really liked having a tablet, but I've got a phone for that stuff and I needed an e-reader). The very next day they fixed the app so I decided I should load CM10 back onto the Kindle. Now, I flashed CM10 onto my phone last year and it was a painless process so I figured it'd be the same here. Somehow in the process I completely messed things up.
From stock FireOS, I used Kindle Fire Utility to flash TWRP on my Kindle, then from there installed CM10 again. What I didn't know, was that CM no longer comes with gApps preloaded. I had no clue, as when I flashed it onto my phone it had all the gApps on there. So I google it and find out I need to flash gApps on there. Here's the problem: I can't boot this thing into recovery. Somehow TWRP was lost in the process. I enabled developer options in the settings, then enabled the option to choose reboot into recovery in the power menu but when I choose it, it just reboots into CM10 again. I'm not sure how I'm supposed to revert back to stock or flash gApps in if I can't get to TWRP again.
It's clear this has gotten way over my head.
Summary:
* Have a kindle w/ fresh install of CM10 on it.
* No gApps and can't boot into recovery.
* I think TWRP might be gone somehow.
* I want to either return to stock or get TWRP back safely and gApps flashed on here.

You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.

themetalman said:
You need to boot back into Kindle Fire Utility and install the boot loader FireFireFire to boot into recovery.
Click to expand...
Click to collapse
I can't seem to get KFU to recognize my plugged in Kindle. IIRC when I first used KFU, when it recognized the Kindle it displayed "ADB Status: Online" and "Boot Status: 4000". Now it's ADB Offline / Boot Unknown.

I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.

TheSMP said:
I've been told elsewhere that I need to locate a stock recovery image and load it up using terminal emulator since it appears my recovery was broken. Where might I find one for my Kindle? I perused the various stickied threads / guides around here but did not see one.
e: Would it be against the rules re: buying/selling if I offered whoever helps me get this fixed $10? Haha.
Click to expand...
Click to collapse
I have used the download and the bottom of this page to repair a bricked kindle fire.
Link: http://n2aos.com/
Then go back into kindle utility and reinstall TWRP and firefirefire.
You might also want to look at this site. He has great tutorial videos. Link: https://sites.google.com/site/tomsgt123/all-videos/kindle-fire

[Q] Kindle Fire 8.9 Stuck on static boot screen.

Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?

Hmm, off flashing from fastboot should typically work, since you were attempting to flash cm 10.2 I have to ask something because I am slightly uncertain of this myself, but did you ever get twrp running at one point before all this happened, and second if so did you ever wipe any of the partitions or try to flash the ROM?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Unfortunately no. I was never able to get into TWRP as the blue logo has never appeared. Directly after my first attempt at this I rebooted and got the red screen or wall of fire. I "fixed" that by reflashing stock boot, bootloader, recovery, and system image partitions to 8.1.4. Yet instead of a working device I now have either a boot loop or a fixed orange logo. I have gotten the device into stock recovery once (haven't been able to reproduce this result) but it shutdown while the process was underway(About half way??). I have also gotten the device to boot into a animated logo that then proceeded to a data corruption screen, but before I could even read the entire message the device shut off and began another set of boot loops. It looked like a amazon stock os prompt screen. Before this even began I had a normal Kindle fire that I had rooted. I forget what software version it was on before all of this unfortunately.

Sounds like the system image is slightly corrupted or something if the os had that kind of error about data corruption but you said the md5's march so that is weird. You try reflashing the boot partition again since reflashing system didn't work? This is frustrating, mainly because with out adb access from a decent recovery I have no Linux commands to work with, if worst comes to worst I think there's a way to reform at the system partition from fastboot but I wouldn't go for that just yet, I don't know the command offhand but if you did the wrong one I think there's a way it would clear all data on all partitions which would be very very bad. I'll ask hashcode what he thinks cause this is weird.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

I have tried flashing all partitions before. Will try again soon. Also, I have another piece of information as well even if it isn't relevant. I originally bricked my Kindle at first, flashed the wrong bootloader. So I bought a for-parts Kindle (Same model) that had a busted screen and took out its motherboard and placed it into my device. Then I rooted the stock os on the new MB and the rest of the story is already in this thread. It still charges and fastboots but nothing other than a static orange boot screen so far. Thank you for helping me out on this; really hope that this can be fixed.

Thinkwithportals said:
Hello,
I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick. Being as inexperienced as I am, I took the risky road and did not back up my device before attempting this... Lesson learned (Spent days on this problem when a back up takes minutes...) Currently, I can access fastboot and flash files but nomatter what I end up with a similar result of a static boot screen (Orange). I have tried KFHD System.img Restore Tool (Here) many times on different machines. I have tried KFFirstAide and it refuses to let me download from the server and thus aborts re-flashing the kindle. I have tried manually flashing 8.1.4 system, boot, and recovery images again with no results (As well as cleared the cache and userdata each time). I have downgraded the bootloader to 8.1.4 using the file given in Hashcode's Guide to install TWRP (Here). I have flashed these files from a Windows, a Mac, and now a Linux PC. Currently the Kindle is staring at me with a Kindle Fire Orange static boot logo. It is recognized by a computer for about 1-2 seconds after I first hit the power switch(I can catch it in fastboot here). Then it disappears and sits idly at the boot logo. Sometimes it reboots and then repeats the process, sometimes it just stays this way until I turn it off via hard reset.
I check the MD5 sums on each of the files and none of them have been corrupted while downloading. So now after looking through every forum I can bear, I come here. Am I missing something simple? Or is my device a devil spawn that refuses to return to stock images?
Click to expand...
Click to collapse
"I have recently attempted to install the 2nd bootloader, TWRP, and CM-10.2 mods on my Kindle FIre HD 8.9 and ended up with a bootlooping brick."
I have the same problem but when I try fastboot mode the computer wont even find the device

Alrighty, well. I woke up this morning and decided to re download all of the system, boot, and recovery image files. I flashed them to the device and it again boot-looped for about an hour. I set it up next to me and started reading through the forums for repair via soldering eMMC to SD card reader. I look down and what is starting back at me? A fully working Kindle waiting in initial setup for input... Yet within about a minute it is back into the old boot looping game again. Hardware problem? A short maybe???

possibly or maybe it has a bad emmc chip.
Sent from my LG-P769 using xda app-developers app

Hm, well I think I might just give up on this MB then. I am considering looking into my hard-bricked motherboard and using Kurohyou's pin-out. Even if my soldering skills are a bit rusty.
Thank you anyway for your help. I will report my progress in the other thread from here on out.

Careful not to melt the contact pads, I just ruined one of my Xbox 360 controllers today unsoldering a trigger, cheap parts.... Long story short controller falls in dogs water bowl, circuit board goes in rice, rice gets stuck under a trigger, I ruin controller unsoldering trigger... Least I have 4 more. But anyways yea careful, I suggest at least an st7 tip and not to let it get to hot, read someone else managed to melt a contact on a kf2 I think it was.
Sent from my Amazon Kindle Fire HD using Tapatalk

[Q] Am I bricked now? -no boot-no recoveryTWRP

I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.

KoBRaQ said:
I'll try to make this as short as possible. My CM10 Linaro had been crashing a lot lately when browsing pages and I decided to put a more current rom on the KF1 instead of troubleshooting and cleaning it up. I saw that there are now KitKat roms available so I tried to flash a CM11 SGT7 rom and after it would never get past the FFF symbol and just kept rebooting to that. After reading it looked like maybe my TWRP and FFF maybe were too old (TWRP 2.0) so I thought I would just put an older ICS or JB rom back on it and upgrade it later after a full charge. Probably would have been fine if that is what I had done.
Right before flashing an old image I saw a post about a new flashable TWRP, bootloader and recovery for OtterX that I could (I thought) flash using my existing TWRP then I would be able to use the KitKat image I already had on the Kindle.
All of this above may have been bad logic but here is where I am at,
I Installed the newer TWRP,Bootloader from the OtterX KitKat page and on reboot everything looked okay, I got the new bootloader and could double-tap to get into the menus to change file system etc, but when I select "recovery" from the menu it never loads into TWRP recovery. Just keeps booting over and over. I can'r seem to use anything from the KF Utility (reinstall older 2.0 TWRP)because the Kinldle doesn't stay USB connected long enough to run any ADB commands (When it does briefly connect it is seen as an ADB device, but then reboots\disconnects before I can do anything).
SO now, no bootable ROM, Otterx bootloader and apparently no way to get into TWRP or connect as ADB.
If anyone has any suggestions to help get my Dumba$$ out of this I will gladly donate to your cause.
Click to expand...
Click to collapse
Did a little more research.Guess I should try a fastboot cable maybe?

connected for a split sec is all KFU needs to send reboot to fastboot mode command.
Did you try rebooting kindle few time while running KFU?

I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.

clifford25501 said:
I have the same problem. KF detects as TI Board. No boot or adb. Battery is charged. Also power led is not working. Any advices? Also i try to connect with fastboot cable. Nothing changed. Device manager just for second detects TI Board.
Click to expand...
Click to collapse
which windows version 7, 8...?

I try on win xp and win7. First it was detected as OMAP4320 but after driver installing its detects only as TI BOARD. This happaeds after installing otter x bootloader and tpwr 2.7.0.0. I live it for a night because i couldnt install driver for otterx fastboot. When i check device on the morning it was in this state and do not power on.

Not bricked, but no idea the state it is in? "perfectly android" screen.

Years ago my daughter loaded "perfectly android" rom on this tablet. Recently it no longer boots.
Model 3HT7G
Turning on, you get the Kindle Fire in orange, then screen flashes and you see Kindle Fire in Blue.
Then a strange strip of color down the left side.
Then it sits on a "perfectly android" screen and blanks the screen every few seconds.
It does this until you hard power it down.
Anyone know how to remove this custom ROM and put something modern on there? The "perfectly android" website exists still but most of it doesn't work.
I have a link in email from them where she bought the software back in 2016 the file was called "Perfectly-Android-CM12-HD89-Installer.exe"
The install notes mention TWRP but not the version and the filename suggests Cyanogen Mod does it not?
Thanks in advance for any assistance.

seems stuck in TWRP screen loop. the screen I see is just some custom TWRP logo screen from whatever my daughter installed years ago.
ADB nor fastboot seem to respond.
I do see the Kindle in device manager, I installed the SDK and ADB drivers.
Fastboot always just reports <<waiting on device>>
Tried two different USB cables
Any thoughts on how to un loop it?
Best guess is the recovery image is corrupt?

OK, after many attempts I finally got it in to fastboot boot mode, did the recovery steps in the threads on here and I'm back to a fully functioning stock 8.1.4 install (I think that is the image that it recovered to, I can check if it matters the exact stock version).
What is the latest stable modded ROM released for these gen tablets? I think it had CM12 on it before based on the file names.

denathor said:
OK, after many attempts I finally got it in to fastboot boot mode, did the recovery steps in the threads on here and I'm back to a fully functioning stock 8.1.4 install (I think that is the image that it recovered to, I can check if it matters the exact stock version).
What is the latest stable modded ROM released for these gen tablets? I think it had CM12 on it before based on the file names.
Click to expand...
Click to collapse
There isn't really a stable rom for the Jem 8.9. It's mostly nightlies available
Best I used was temasek 13.1 from android file host.
However most of the roms have bugs so I reverted to pre-rooted stock.
I then just Debloated the latest stick rom and installed nova launcher.
After that I binned it and bought a Samsung galaxy tab a 2016 as the Jem was painfully slow