Hallo Guys,
please help me.
I 've done a stupid thing. After i cant install twrp on kindle fire i just rooted it and flashed twrp.img with flashify.
So but after reboot my device i've got a red screen. I tried different unbrick tools but no one worked. The adb isn'T working anymore. When i plug and unplug my device from my computer the windows device manager doesn't recognize any hardware changes. So i can't install any driver cause the device isnt recognized anymore. I've already deleted all driver and reinstall them again. without succes.
I've already tried to hold power off buttom for 20 sek ... without succes.
When my device is of and i press power buttom. The kindle fire logo appears for one second than the red display comes out.
Please help me guys
if you have a red screen, likely do not have a kindle fire 1,
see Fire Index: Which Amazon (Kindle) Fire Do I have?
Sent from my KFFOWI using Tapatalk
Related
Hi guys,
I've already searched in the forum but didn't find a solution. I need your help.
I was trying to root my kindle fire 6.3.1 with KFU, I selected the option "Install permanent Root with Superuser" and I received an error.
My Kindle Fire was stuck (I suppose in fastboot) on the static logo "kindle fire" while booting.
Now, after some attempts with tools like Firekit and Kindle Unbrick Utility, my Kindle Fire no longer turn on if I press the power button. If I plug in with USB it flashes the Kindle Fire logo and then turns off then flashes the logo and so on in loop. It's no longer recognized by windows.
It seems that everyone that had a bricked kindle fire had installed FFF/TWRP, but I didn't so I don't know what to do.
I hope you'll help me to fix the problem!
Thanks, Riccardo
EDIT: the boot loop started after I let drain out the battery. Now I'm using the stock 1.8 amp AC charger to recharge the battery and the Kindle Fire is suck on the static logo!
Solved with http://forum.xda-developers.com/showpost.php?p=20619033&postcount=11
I have an original Kindle Fire rooted with CWM and after I did some app updates, something must have serious been affected by the changes. My Kindle Fire now immediately shuts off after first unlocking it. After shutting off it will reboot and attempt to load (shows the android robot with some blue prism thing) which will fail and show a yellow triangle with an exclamation point. I then have to hard reset the Fire to reboot it. I can get the Kindle Fire to boot back up again but only to shut itself off again immediately after unlocking.
I have attempted to restore the kindle fire through the kindle UI (when I can get it to stay on long enough) as well as restore it through the CWM prompts. Nothing seems to work.
To add insult to injury, the kindle also will not be recognized by my macbook. I have tried both through kindle and CWM mounting and have tried using multiple cords and multiple laptops. Sadly none of them will recognize the Kindle Fire so none of them will let me move an update.zip onto it.
I feel like I'm completely stuck, does anyone have any suggestions on what I could do? Also please let me know if there's any other information needed to help answer this question.
i rooted my kindle fire 1st generation and everything was working fine. there was an app available that i found that claimed it could flash a recovery onto the kindle however after running this the kindle fire was stuck on a red screen at boot. I purchased a factory cable and using kindle fire utility i tried to install FireFireFire. after it was finished the kindle had a pure black screen and the power button was green. nothing was happening so i held down the power button until the light went off. Now the kindle won't turn back on and when its on charge the power button does not light up.
what i've tried:
Running adb and restoring from a backup : kindle not found
Running kindle fire utility and changing boot mode : kindle not found
Holding down the power button for 30 seconds and resetting the device : no response
P.S all drivers are installed.
Any help would be greatly appreciated.
Hi,
Well I have had a kindle for a long time and I have successfully applied root to it many times... So this time my kindle was rooted (no problems there)... I tried the cynogenmod but for that I needed to install TWRP recovery... I used the kindle fire utility 2 master to install TWRP. Everything was going fine and then it asked to reboot the device I pressed enter and EUREKA!!!! the kindle turned with its logo but then quickly changed to the RED SCREEN... I didn't want to bother you developers so I searched for a fix... then I needed a Fastboot cable so I made one... So I plugged it in the computer and the Kindle came on with a screen with fastboot written on it and two lights one red and one green(blinking green)... So the next step was to find a program to unbrick it so I searched and downloaded the kindle fire first aide(image posted), kindle fire unbrick utility(image posted) but none of them worked. they both keep on saying " the system cannot find the path specified " (without the quotes) So I need your help I really miss my kindle and want it to live again.
P.S: If it helps when I connect the fastboot cable with my kindle and pc. in the device manager it shows up as otter-02-prod-04(image posted)
P.P.S : I really need your help .... the images can be seen on this thread " http://forum.xda-developers.com/general/xda-assist/kindle-fire-2nd-gen-bricked-red-screen-t2904472 "
This is my new post I tried a new link "http://forum.xda-developers.com/showthread.php?t=2304584"
but that didn't work either the command prompt stcuk on waiting for device please help
This is where my Kindle fire is at:
-Boots up using power button
-Displays Kindle Fire(orange) logo for about 5 secs
-Display goes blank for about 3 secs
-Loops in this manner indefinitely.
-Pressing Power & Volume Up during boot up puts into a specific mode where screen is blank and
PC would detect Kindle at Amazon Tate (In portable devices) and another device as ADB composite.
- When I run adb, it shows the device name and says unauthorized.
I have tried various methods, like plugging in HDMI cable, OTG mouse but there is no way to enable ADB on the tablet as there is no display.
-BTW, bootloader is locked on this tablet, I made fastboot cable but it doesnt work. I was never able to put tablet in fastboot
I basically bricked tablet by installing 7" ROM on 8.9" tablet. I dont know how it would break the tablet but it did. My tablet was rooted before I bricked it.
Tablet is worthless even if I fixed it but I am just curious if there is a way to fix it. Any help is much appreciated.
harshil22 said:
This is where my Kindle fire is at:
-Boots up using power button
-Displays Kindle Fire(orange) logo for about 5 secs
-Display goes blank for about 3 secs
-Loops in this manner indefinitely.
-Pressing Power & Volume Up during boot up puts into a specific mode where screen is blank and
PC would detect Kindle at Amazon Tate (In portable devices) and another device as ADB composite.
- When I run adb, it shows the device name and says unauthorized.
I have tried various methods, like plugging in HDMI cable, OTG mouse but there is no way to enable ADB on the tablet as there is no display.
-BTW, bootloader is locked on this tablet, I made fastboot cable but it doesnt work. I was never able to put tablet in fastboot
I basically bricked tablet by installing 7" ROM on 8.9" tablet. I dont know how it would break the tablet but it did. My tablet was rooted before I bricked it.
Tablet is worthless even if I fixed it but I am just curious if there is a way to fix it. Any help is much appreciated.
Click to expand...
Click to collapse
You installed a Tate Rom on a Jem and you don't know why it's bricked?
Sent from my ali using XDA Labs
I got so excited once I was able to finally root the tablet that I completely missed in the tutorial video that the ROM was for different tablet. Damage was done!
harshil22 said:
I got so excited once I was able to finally root the tablet that I completely missed in the tutorial video that the ROM was for different tablet. Damage was done!
Click to expand...
Click to collapse
Hello !!! I have the same issue. Could you fix it?