What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Badcatalex said:
What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Click to expand...
Click to collapse
Fastboot is the answer.
Badcatalex said:
What I did was flash recovery properly (after root, CWM) and accidentally hit reboot without an OS to boot to. Now it is stuck on the Kindle fire logo, but it only shows for a brief period of time (one second) then a black screen. What do I do now? Is it bricked? BTW, I was installing a unofficial version of Cyanogenmod 13 for "tate" and don't have a fastboot cable on hand, nor a soldering iron. :fingers-crossed:
Click to expand...
Click to collapse
Uhhh... I hate to be the bearer of bad news, but I'm pretty sure the 2013 model without the camera is NOT the 'tate'. There are various warnings about this, including Cyanogen's own wiki:
Be sure you have a 2012 "Tate" device and not the 2013 Kindle Fire HD 7" "Soho" device. The 2013 model does NOT have a camera. And it currently has no exploit for loading a custom recovery. Using the Tate exploit files on a Soho device will end with an unrecoverable brick.
Click to expand...
Click to collapse
Sounds like you've discovered the unrecoverable brick they speak of, when doing exactly what they say not to do. Your model sounds like the Soho.
Related
Hey geniuses, i have a KFHD 7". i ran the KFHD_SRT kit to downgrade my kindle to 7.2.3 na dgain root access.
i am proficient enough in cmd prompt to use adb and fastboot.
i have attempted to install:
2nd bootloader
TWRP
Kinology
CM10
and aosp
using fastboot i get no errors, everything installs and/or flashes correctly.
When i change the bootmode and attempt to boot recovery, i see the orange KF logo for a split second, then the screen shows totally red, with no reaction at all. all i can do is go back to fastboot and run the SRT to reload 7.2.3
i have followed several different guides (though there is little to no difference between them) i never get an error. i only ever get the red screen.
Has anyone else had this problem? the only red screens ive seen have been on devices that were not rooted or altered at all, and the devices is usually totally bricked (though most people dont know about the fastboot cable, so probably not)
can anyone give me a beginning to end walkthrough for ANY rom with s/w ver. 7.2.3 OR 7.3.1?
*edit* i did just realize that hashcodes 2nd bootloader says 8.9" only but every 7" rom page links me to that bootloader
*edit edit* i found and tried the 7" bootloader, and have the same problem
When you came from 7.3.1 a downgrade to 7.2.3 is not enough. You also have to downgrade the bootloader back to 7.2.3.
The 7.3.1 bootloader includes a fix that if you install freedomboot it will cause a redscreen due to the new verification Amazon put into their new bootloader.
Go to Hashcode's thread about the second bootloader for 7"
And read thoroughly, since you have the red screen, you will need a fastboot cable to fix it
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
dugoy13 said:
When you came from 7.3.1 a downgrade to 7.2.3 is not enough. You also have to downgrade the bootloader back to 7.2.3.
The 7.3.1 bootloader includes a fix that if you install freedomboot it will cause a redscreen due to the new verification Amazon put into their new bootloader.
Go to Hashcode's thread about the second bootloader for 7"
And read thoroughly, since you have the red screen, you will need a fastboot cable to fix it
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
Click to expand...
Click to collapse
Ah! that makes sense. i did try that that guide and the freedom boot wouldnt flash. it gave me the max. d/l size then failed listing "no error"
I will follow it again on 7.3.1 and post my results. Thank you for your help
Kffirstaide
I downloaded and ran the KF FIRST AIDE tool and it worked like a charm on all features, until i run bootloader + twrp install.
everything runs succesfully and it reboots to red screen of death.
i did do a factory reset first.
as much success as is had with that toolkit i thought for sure it would be a breeze.
if i have time today ill try the manual flash again
You still haven't flashed the 7.2.3 u-boot, that's why you get the red screen. You MUST flash the 7.2.3 u-boot file (the 7.2.3 bootloader, this will get rid of the red screen) before installing TWRP. It's found in Hashcode's bootloader thread.
semi-success
AH! man do i feel stupid. i didnt realize the toolkit d/g'd everything BUt the bootloader.
I am now running TWRP, but when i flashed the CM10.1 rom it boot loops. i have re-downloaded and reflashed.
Now im really just wondering if anyone else has this issue before i flash Kinology
kyleberry.graphics said:
AH! man do i feel stupid. i didnt realize the toolkit d/g'd everything BUt the bootloader.
I am now running TWRP, but when i flashed the CM10.1 rom it boot loops. i have re-downloaded and reflashed.
Now im really just wondering if anyone else has this issue before i flash Kinology
Click to expand...
Click to collapse
When you move from stock to CM10.1, you have to wipe and format EVERYTHING including the two caches (except the sdcard, of course). The reason lies with the kernel.
seokhun said:
When you move from stock to CM10.1, you have to wipe and format EVERYTHING including the two caches (except the sdcard, of course). The reason lies with the kernel.
Click to expand...
Click to collapse
i did. actually i believe i have found my error. there is a POST flash zip after the rom that i thought was the kernel alone.
im downgrading the kindle now, and trying again. otherwise ill give the kinology rom a try, though i was more interested in CM or paranoid
Does anyone know of a quick way to check the current bootloader version installed? (other than about device, which lists total rom ver.)
hello evrybody !
I have a kindle fire HD 7" and i have attempted to install:
2nd bootloader
Fireflash
TWRP
CM10
But... when i have try to install twrp with Fireflash a red screen is a appeared after the reboot.
I'm a noob and i'm a little panicked !!! Can you help me to unbrick my kindle, i'm ready to make evrything but i have only in my hand my kindle and the original cable.
Please XDA's community !!!
(And sorry for my english, i'm not american...)
Goldofaf said:
hello evrybody !
I have a kindle fire HD 7" and i have attempted to install:
2nd bootloader
Fireflash
TWRP
CM10
But... when i have try to install twrp with Fireflash a red screen is a appeared after the reboot.
I'm a noob and i'm a little panicked !!! Can you help me to unbrick my kindle, i'm ready to make evrything but i have only in my hand my kindle and the original cable.
Please XDA's community !!!
(And sorry for my english, i'm not american...)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2273638
Sent from a Kindle Fire HD running CM10.1 using Tapatalk 2
SUCCESS!
finally.
simple kfhd7 romming. (assuming you have a factory cable)
download KF First Aide from XDA and full downgrade to 7.2.3, then root.
run TWRP & bootloader option.
kindle should boot to red screen. if so, power off and reboot fastboot.
fastboot -i 0x1949 flash bootloader ../kfhd 7.2.3 bootloader
Thanks for all of your help
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
You have TWRP installed, right? Does your Kindle Fire logo turn blue while booting?
soupmagnet said:
You have TWRP installed, right? Does your Kindle Fire logo turn blue while booting?
Click to expand...
Click to collapse
i might be in the same boat...my kindle fire logo turns blue and gives me a msg at the bottom to press power button for boot menu
when i do i get normal boot,recover,and reset boot mode...when i click on one it just says booting and power button stays organish red for ever
Maybe you don't have your drivers properly installed
sent from my rooted kindle fire hd 7
Baconrind said:
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
Click to expand...
Click to collapse
If you have twrp installed and the blue kindle boot screen just hit volume down and use the side load feature. But if your fastboot is giving u a problem where u can't hit update driver I would assume it would be because windows is already searching for one still? If so tell windows to skip obtaining from windows update and it finish sooner so u can try to update it manually.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Baconrind said:
I screwed up installing CM10.1 forgot to put rom onto device and ended up in boot loop.
I got a fastboot cable but the kindle shows as Tate PVT and the update driver box is greyed out. Cant get fastboot or adb to recognise the device.
Is there anyway to recover from this
Thanks
dean
Click to expand...
Click to collapse
Hi Baconrind. Screwing one’s device is a good opportunity to learn new things. At least this is what happened to me and I’m glad I did. A couple of months ago I bought a new KFHD7. I spend "wonderful :laugh:" weeks as the happy owner of a KFHD7 until I started to discover the shortcomings of same, so I started reading xda-developers’ stuff to try to customise the device. First I rooted it to be able to install Google Play Store. The idea was to stay as close to stock as possible. Unfortunately I lost root with the first Amazon OTA update, then I decided to install a second bootloader, TWRP, etc. To do that I followed Hashcode’s method Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 7 but at some point I bricked :crying: my device. I was stuck at the Kindle Fire logo. I spent hours browsing through xda-developers and discovered that the first thing to do was to get a fastboot cable. I did not have the patience to wait for it to come from China or wherever they make them, so I found a couple of posts on the xda forum here and here. I made my own even my soldering capabilities are quite limited. I shut down the KFHD7 and plugged the “fastboot” cable to the PC and then to the Kindle, a couple of seconds later I could see the fastboot logo. Once I saw the fastboot logo I unplugged it and used the regular data transfer cable instead. Before I started the unbricking process proper I downloaded and installed this tool: KFHD_SRT_v1.3.5.-7.3. I followed the onscreen indications and could reset my KFHD7 back to its original state. Good luck.
Okay so I bricked it bad. We're talking BAAAAD. No boot, to any screen at all. you press the button and nothing happens. Nothing happens when you plug it into the charger either.
I was following a tutorial on youtube (its the first link you hit when you youtube "flash kindle fire hd android", by zedomax) and I got as far as this code:
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
Click to expand...
Click to collapse
and the moment I hit enter (after the reboot part), bam, It went black, and has not lit up since.
SO, gentlemen, how did I do this? how do I not do this again? And, anyone have any ideas on how to unbrick it?
Thanks
Do you have a Fire HD or Fire HDX?
noodles2k said:
Do you have a Fire HD or Fire HDX?
Click to expand...
Click to collapse
model x43z60
Kindle HD 16gb
slamthedeck said:
Okay so I bricked it bad. We're talking BAAAAD. No boot, to any screen at all. you press the button and nothing happens. Nothing happens when you plug it into the charger either.
I was following a tutorial on youtube (its the first link you hit when you youtube "flash kindle fire hd android", by zedomax) and I got as far as this code:
and the moment I hit enter (after the reboot part), bam, It went black, and has not lit up since.
SO, gentlemen, how did I do this? how do I not do this again? And, anyone have any ideas on how to unbrick it?
Thanks
Click to expand...
Click to collapse
You flashed a Jem to a Tate (KFHD 8.9 to a KFHD 7) Sorry to say that is a hard brick. Someday there may be a way to install the drivers but right now it's done. Sorry.
LinearEquation said:
You flashed a Jem to a Tate (KFHD 8.9 to a KFHD 7) Sorry to say that is a hard brick. Someday there may be a way to install the drivers but right now it's done. Sorry.
Click to expand...
Click to collapse
I figured. For future reference, is there a way to flash it to droid? How would I go about this next time?
I would use fireflash and check the box to downgrade the boot loader. There's a tutorial by seokhun in the kindle fire 7" android development forums that's stickied. Still kinda confused how those commands hard bricked it, you only flashed the kernel partition and the recovery partition, I figured the boot loader would at least show up and stay in a bootloop since those partitions aren't signed and they are the wrong versions. If you can return it for a new one I'd do that, just tell them it won't turn on and they should replace it if its under the warranty from time purchased still.
Sent from my Amazon Kindle Fire HD using xda app-developers app
thread moved
Moved to I hope is the correct kf forum.
stunts513 said:
I would use fireflash and check the box to downgrade the boot loader. There's a tutorial by seokhun in the kindle fire 7" android development forums that's stickied. Still kinda confused how those commands hard bricked it, you only flashed the kernel partition and the recovery partition, I figured the boot loader would at least show up and stay in a bootloop since those partitions aren't signed and they are the wrong versions. If you can return it for a new one I'd do that, just tell them it won't turn on and they should replace it if its under the warranty from time purchased still.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
He flashed fhd8-freedom-boot-8.4.3.img to a KFHD 7. Wouldn't this cause some problems or no? I know it's just the image but it can't do pushing it the same.
Hello, everyone!
Yesterday I tried to flash CM10 in my kindle fire (already running CM9).
I followed the Cyanogen Mod site (wiki.cyanogenmod.org/w/Install_CM_for_otter) instructions.
I downloaded Kindle fire utility 0.9.9 (from CM site), and started the process of updating TWRP. At some point of the installation, KFU rebooted my device in fastboot mode, and kept waiting an awnser from Kindle.
It was taking a bit too long, so I restarted the tablet. Now it keeps on the "Kindle Fire" screen forever, and don't respond to ADB anymore (the "adb device" command don't return anything).
I believe it is not bricked yet, because when we connect it to the PC, it does that connection sound. However, I can't reach it with ADB anymore.
Can Anyone give me an advice for this situation?
Thanks a lot !!
You got very lucky, kindle fire utility is not meant for second generation devices, usually using it results in a hard brick. The correct way to update twrp is to grab the latest version's flashable zip from the dev section for your device and flash it from inside twrp and reboot. If you no longer have the blue logo and it is a 7" device you will need a fastboot cable, if you do have a blue logo or this is a 8.9" device you won't need a fastboot cable to fix, but you still need to get it into fastboot mode to reflash some partitions back to stock to fix this unless you get a blue logo in which case you could probably just flash the recovery but from what you said I'm assuming you don't get the blue logo anymore. And only the 8.9" models tend to be detected briefly while passing the bootloader.
Sent from my Amazon Kindle Fire HD using Tapatalk
In fact, my Kindle fire is a 1st generation one! I had already used KFU to flash CM9 on it (before, it had stock OS) .
Do this fact help in any form?
And, about the cable, I will search one imediatly!!
Thanks for your reply!
O well then this is the wrong device forum on xda... If its a kf1 then I think fastboot cable will still apply to this. Not positive, kf1's aren't my specialty, while my mother has one I never did much beyond rooting and installing twrp. Flashed a Ubuntu touch preview os on it once but that's about it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Hi everyone so i was installing cm11 on my kfhd 7 some days ago and the installation failed. I was not able to use twrp to put the new cm files into my sdcard so i decided to flash my backups with fastboot, while on the process the cable disconnected from the kfhd and it turned of. After it turned off i tried to get to fastboot again. Now it is stuck at orange kindlefire logo and i cant get to twrp or fastboot it just stays there . Anyone knows what can i do? Thank you
If stuck on a yellow/orange kindle logo you will need a fastboot cable/adapter to fix. I recommend the team blackhat one hashcode mentions in his tut for 2nd bootloader.
stunts513 said:
If stuck on a yellow/orange kindle logo you will need a fastboot cable/adapter to fix. I recommend the team blackhat one hashcode mentions in his tut for 2nd bootloader.
Click to expand...
Click to collapse
Ok thank you i'll buy it