Related
I have been playing around with my new Kindle Fire 2 and followed some instructions to flash Fire Fire Fire, however now it won't even power on.
I'm guessing it's a bad bootloader flash, I've heard Firekit can be used but that it is first generation only, is this true? If so is there any way of unbricking the Kindle Fire 2
Also will USBboot work - or is that also 1st gen only?
jburtn said:
I have been playing around with my new Kindle Fire 2 and followed some instructions to flash Fire Fire Fire, however now it won't even power on.
I'm guessing it's a bad bootloader flash, I've heard Firekit can be used but that it is first generation only, is this true? If so is there any way of unbricking the Kindle Fire 2
Also will USBboot work - or is that also 1st gen only?
Click to expand...
Click to collapse
Cool, you managed to put a bootloader on a device before a dev did!
Yes, you bricked it. What do you mean by it won't power on? If you see a red triangle, 5 power buttons presses to do a factory reset. If it's just....nothing, here you go!
http://forum.xda-developers.com/showthread.php?t=2035047
Should work. Not positive as I haven't bricked, but that's your best bet so far. Good luck!
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
plinders said:
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
Click to expand...
Click to collapse
Good luck to you two! Unfortunately Recovering a Bricked device takes more time and know-how than simply Rooting devices, so sometimes the users are really SOL when it comes to bricking. I hope we can get more methods like the Samsung thing and PSP pandora battery that makes devices un-brickable. One day hopefully. For now, best of luck!
If it works I would post in the thread I linked and let them know how it went or if you have advice for future people that end up bricking their Kindles!
plinders said:
Haha, I managed to do exactly the same. My KF2 isn't powering on either.
Basically, the screen stays black, the power led doesn't light up at all, no matter how often or how long I press the power button.
I've ordered a factory cable and I'm going to follow the guide iytrix posted as soon as it arrives through the mail.
Click to expand...
Click to collapse
A factory cable is not going to do anything at this point. You have written over the uboot which is needed to even get to fastboot. The only thing you can do at this point(which is a method used for original kindle fire but I would imagine the new ones have similiar components, and try this at your own risk cause I'm not 100% it will work) is remove the back, short the usbboot pad to get the device to power on through usb only, then load the original uboot with linux using usbboot commands. That should get you into fastboot where you can then flash original bootloader and recovery.img's depending on how far the process got.
This is not an easy fix especially if you thought using KFU was a smart thing to do. There is a lot more to it than the simple explanation above.
Just out of curiosity what would possess you, because I've seen more people than I would have thought do it, to even try using a utility that was meant for the original kindle fire. There has been so much talk about these new devices having locked bootloaders. The main use for KFU was/is to load a new bootloader.
gen 2 kindle fire won't turn on.
My 2nd generation Kindle Fire will not turn on. Bought for my daughter for Christmas. She turned it off one night and the next day it won't turn on. No attempts have been made to alter it. Went I connect it to my computer it is not recognized and my computer says the device drivers are not present.
Can anyone help? When I connect my Kindle Fire it is recognized. Thanks.
ballsnxs said:
My 2nd generation Kindle Fire will not turn on. Bought for my daughter for Christmas. She turned it off one night and the next day it won't turn on. No attempts have been made to alter it. Went I connect it to my computer it is not recognized and my computer says the device drivers are not present.
Can anyone help? When I connect my Kindle Fire it is recognized. Thanks.
Click to expand...
Click to collapse
That is typical of trying to modify the device incorrectly. Considering the nature of the device, I would say it's impossible for that to just happen on it's own.
What age is your daughter? How sure are you that no attempts have been made to modify the device?
got similar issues now too. after stucked in a bootloop, i read, that the u-boot.bin from the original Kindle Update should fix the bootloader. afterwards the reboot didn't worked and the device shut down. now i cant start it anymore. and the fastboot cable wont wake it up neither.
is it now definitly broken for ever?
HELP!
Hi dear friend, can you lend me a hand on this?? is there any guide I should follow to achieve what you just described before?? please... can you tell me?
onemeila said:
A factory cable is not going to do anything at this point. You have written over the uboot which is needed to even get to fastboot. The only thing you can do at this point(which is a method used for original kindle fire but I would imagine the new ones have similiar components, and try this at your own risk cause I'm not 100% it will work) is remove the back, short the usbboot pad to get the device to power on through usb only, then load the original uboot with linux using usbboot commands. That should get you into fastboot where you can then flash original bootloader and recovery.img's depending on how far the process got.
This is not an easy fix especially if you thought using KFU was a smart thing to do. There is a lot more to it than the simple explanation above.
Just out of curiosity what would possess you, because I've seen more people than I would have thought do it, to even try using a utility that was meant for the original kindle fire. There has been so much talk about these new devices having locked bootloaders. The main use for KFU was/is to load a new bootloader.
Click to expand...
Click to collapse
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
That kindle is hard bricked, there's a slight chance of fixing if it is flashing fastboot mode for a few seconds, but I give it a 10% chance of fixing. We can't fix omap4440 bricks because while we have the means to interface with that device, we need a signed xloader for the kindle to let us flash the other partitions. We can't get the signed xloader (believe its called xloader, might be called something else) unless someone at amazon or TI were nice enough to leak it and probably get fired in the process.
On another note is that android adb composite device staying there the entire time the kindle is plugged in? If it does then you may be able to fix the kindle, I haven't heard of omap4440 and the adb composite being there at the same before. I would guess that adb is the fastboot interface but usually it says Tate when drivers aren't installed and in this case it doesn't but still has an exclamation. I'm curious....
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Well, I wouldn't say 100% out of hope...
http://forum.xda-developers.com/showthread.php?t=2391047
Or you could try using "fastboot boot" to boot the bootloader. This takes barely less time so if the fastboot flash fails, try this.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Same exact problem, did anyone find a fix?
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Steveohookem said:
I have the same problem Word for Word just a few extra details: I did have TW RP installed and I had just recently installed Kinology which was working but I went Back into TW RP again to try to Flash CM and didnt have all the files I needed But went ahead and removed my OS somehow leaving me stuck in TWRP Trying to figure out away to get the files over to it. At some point it ended up in Fastboot mode and I fell asleep so it was running with just the Fastboot logo for several hours and I woke up and saw that it was turned back off at which point I attempted to reboot back into recovery (TWRP) but discovered it would only show Kindle Fire for <1 second then Fastboot <1.5 seconds and back to a black screen. If it's connected to the computer it will make a sound as if the device was recognized but then a strange sound I have not heard I guess meaning the device was not installed correctly; Then this is repeated not stop until a reset on the device is done just the correct amount of time where it doesn't turn back on but the sound stops on the computer and the KFHD screen stays off. I'm new to Android and rooting, etc. but in the last 45+days since I got this KFHD7 used, I have used XDA countless times for a variety of reasons and I intend to be a contributing member from this day forward, even if only in a very limited capacity. I have grown to respect the incredible work of Hashcode among others on XDA and being a noob to Android customization as well as these forums, I have been reflecting on my years being tied down by iOS devices; can't help but feel like I wasted so much time and money, trying to so the things that Android was already capable of doing. I think I may need to f-around and jailbreak my iPhone 4S pretty soon when I'm able to scoop up a real nice Android phone and leave ios behind for good like I should have done when I switched from the very first iPhone on Cingular Wireless!! But yeah sorry, um... Little long-winded on my first ever reply on XDA. I'll try not to make a habit of that. I was just wondering if anyone made any progress on this issue, and thought my 2¢ could potentially be helpful, disregarding all the ios b.s. My Kindle Fire is Hard Bricked and I'm keeping my fingers crossed that I can squeeze something out of that "10% chance for recovery." Thanks a billi.
Click to expand...
Click to collapse
When you remove your OS off any device without one to install, its like giving someone a car with no steering wheel. You now need to push a ROM thru TWRP using ADB. Try using the solution that helped me, which I provided to another user in this thread:
http://forum.xda-developers.com/showthread.php?p=45188927#post45188927
Sent from my Amazon Kindle Fire HD using xda app-developers app
---------- Post added at 06:10 AM ---------- Previous post was at 05:56 AM ----------
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
Creepy never seen that happen on either of my two KFHD7s. Have you tried uninstalling that driver completely? Or uninstalling those drivers thru "Device Manager" AND all others installed for /example the ones provided by Hashcode, then reinstalling them WITH the device still connected? Many times I've realized that these Kindle Fires love to have drivers juggled around. The fastboot cable I made at home using a Samsung USB does FBmode instantly. Try holding the power button for about 20 seconds while unplugged, make sure when you let go it doesn't power back on. If alls well, have the fastboot cable plugged in already to your computer, then attach it to the KF. See if that helps. If not, then believe it or not it might be a hardware failure if the screen goes black as you mentioned...
Sent from my Amazon Kindle Fire HD using xda app-developers app
r3pwn said:
Well, @stunts513, it also shows that a kindle fire is plugged in with adb enabled. So he might not be 100% out of hope.
It sounds like the bootloader does indeed work, but there is a small problem. I am not sure what that problem is, but if the fastboot logo even shows at all, there is a small chance you could get it up and running again. Download the kfhd7 bootloader provided by @Hashcode and see if you can "fastboot flash" it before the screen goes black. Type in the command and the second you see the orange kindle fire logo, hit enter. Keep in mind that it might work. I am not responsible if it ruins your device further. It shouldn't, though.
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
My bad the picture must have not loaded up last time, or I wouldn't have said that much. But more than likely he has a hard brick. Slim chance of fixing it though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
lizvx said:
I currently have a bricked kindle 7 hd and wanted to see if anyone could help me out with their expertise. A week ago I accidentally bricked my kindle and purchased the factory cable on ebay to try to fix.
At this point when I connect the cable, screen stays black.
If i press kindle power button, Kindle logo will briefly appear, followed by fastboot logo for split second and then goes black again.
There are so many posts on the website on how to fix a bricked kindle, but I'm unsure which one is the right solution in this case.
Also, my driver on the Device Manager connects and disconnects continuously. And for some reason, I'm showing OMAP4440 when I connect my kindle, which I assume is not correct.
What is my next step, or what do I download?
Please, if someone can help, I'd be very grateful. I've been without my kindle for over a week. Thank you.
Click to expand...
Click to collapse
hi guys from Italy, i have the same very problem...now is the end of Settember....any good news about?????????
Not very much, unless you wanna try hooking up your emmc to a USB card reader like kurohyou did and trying to flash the stock partitions from Linux, no there really isn't any new news. That's basically the only way we have to recover from a hard brick, and it still isntna perfected process, he got his kf2 to a soft brick state after un-hardbricking it, but he couldn't un-softbrick it yet, so he is currently working on that part last I heard.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Juls69 said:
Hello, I have the exact same problem with my KFHD7 and I was reading this thread with the hope that someone would have find a solution.
Is there a solution out there for this problem yet?
Click to expand...
Click to collapse
i think someone finished mapping the rest of the points out on the motherboard but i'm not positive, I'll have to find the thread but the only fix is to solder the kindles motherboard contact point for the emmc to a sdcard reader and hook it up to a pc running linux and flash the bootloader partition with the dd command. Keep in mind I'm referring to the hd 7 2012 model, i don't believe anyone has mapped the points for the 2013 model yet.
edit: foudn the thread: http://forum.xda-developers.com/showthread.php?t=2674737&page=3
use the tutorial for the kf2 or kfhd8.9" but use the contact points mentioned there, might take some researching to know what each of those corresponds to on the sdcard reader. Not everybody is up to soldering on their kindle to fix a hard brick.
Hello,
i found these Thread, because i have the same problems.During the boot the kindle shows the kindle logo then the fastboot logo and the screen goes black. But if use a fastboot-code at the right time, the kindle stay in the fastboot-mode. So i tried to flash the Bootloader and so from Hashwell. The output of fastboot says everythings ok, no errors, but my kindle doesn't leave the bootloop. What i done wrong? I read about the Kindle Fire First Aide-Kit, but i cant find an downloadlink, that still work.
Maybe someone of you can help with this problem.
Good evening scholars, I am at a end with my Kindle Fire. Below is an
exact account of what I was doing and thus the end state of what is now my Kindle.
I have a rooted kindle. Basic root, nothing significant like CynMod. The boot-loader is stock and all. The only thing I really
installed that is not stock is a different Launcher since Amazon's Launcher is just horrid in my opinion.
I was in Rom Toolbox Pro uninstalling Chameleon Launcher because I wanted to run
Apex Launcher instead. So I uninstalled it. At this point there is no launcher running.
I'm using Rom Toolbox as a console so-to-speak. Simply going from one program to the next without actually ever hitting
the home button. So I go to install Apex Launcher and it says installing. However, it didn't do anything at all.
The status bar never moved; simply stayed at 0%. SO! No biggie, I've seen this before. So to make sure it is not Apex or something
I go to the stock Amazon Launcher. I had a backup and tried to install it through Rom Toolbox. Same thing happens,
No response, idle status bar, etc, etc. So at this point I assume it is Rom Toolbox. So I hit the home key on the slide menu.
Well, I have no launcher currently installed so it did nothing. Go figure. So I decide to do a hard reset. So I hold down the power button.The Kindle shuts off and then my troubles started. I hit the power button and it doesn't pass the Kindle is upgrading notice.
So I do another Hard reset adding insult to injury...but, the same thing again. Turn it off again, plug it in to my computer and attempt a fastboot with the stock cable, same results occurred.
So now my kindle shows the standard Kindle Fire Logo at the beginning of the boot cycle and then stops at the Kinde is upgrading...Starting Applications... prompt. Like the link to the photo below.
h ttp://i61.tinypic.com/2s0eeer.jp g
I try rectifying this, reading several articles.
I tried utilizing the Kindle Fire First Aid, the KFHD SRT, even looking into the android SDK a little. But they either - A. Don't recognize the device or, B. Prompts for superuser. Seeing as how my Kindle barely boots how can I check for a superuser prompt?
I go went into my device manager and looked to see if windows registers the Kindle and it does. The device manager displays Hardware ID's indicating something is there.
USB\VID_1949&PID_0007&MI_00
USB\VID_1949&PID_0007&REV_0216&MI_00
I have my hunches on what the problems could be. But I've been working this for a couple days now and have become agitated.
I have never had to many problems with this type of stuff. I won't say I'm a noob at this kind of work however, I feel like it at this point.
Worst comes to worst I would crack her open. But that is risky business. I rarely touch the inside of my devices.
Any words of wisdom are most appreciated.
If you happen to have adb access I'm guessing there's a system app that needs to be chmodd'ed to the right permissions, or if you want you could run "adb reboot bootloader" (and do what I mention next after it's in fastboot mode), however if you have no adb access then you will need to get a fastboot cable and restore with kfhd SRT or kindle fire first aid.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
As I said before the Kindle does not respond when I use KFHD SRT or the Aid Kit.
That's because for those tools to work you need to already be in fastboot mode with the fastboot drivers installed. Have you managed to get into fastboot mode?
Sent from my Amazon Kindle Fire HD using Tapatalk
As of now what you see is what you get. All I get is a never ending boot screen. I see you made a comment about fast-boot drivers. I might be missing something in the equation. I'm going to retrace my steps and start from scratch. Hopefully I will be able to get this thing working.
Well, I cannot get my Kindle to boot into fastboot. Tried reinstalling ADB drivers and everything. Even tried using the First Aid with no luck. I think the boot loader might be damaged. I keep the kindle off, plug it in, try to initiate a fastboot through the KFFA, it dims and continues normal boot operations. Stopping with the Kindle is upgrading notification.
Those commands aren't going to work unless adb was ever active in the first place, you are going to need a fastboot cable to fix it, the bootloader is behaving just as it should BTW, so it is fine, once you get a fastboot cable it will tell the device to enter fastboot when it powers on, from there kffa should work just fine outside of probably having to install Tue drivers because of how finicky it is. The ones in my signature will surface when the time comes.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
navtis123 said:
[I put this message on the general Kindle Fire forum, and was told to move it here]
I have a Kindle Fire 5th Gen. A while ago I used rootjunky's supertools, apparently successfully: first downgrading the firmware to 1.2, then taking the first five options in the supertool (add google play store, root device, block OTA updates, remove lock screen ads, and install nova launcher). I added a few apps (SignBSL, SuperSU, Firefox, termux, wshell) and all seemed ok.
This all worked ok, including the wifi. Today I came back to the device after not using it for a while and found that when turned on it loops between the 'lock' screen and the 'fire' screen. I turned off the house wifi, and then found the looping stopped. Disabling wifi makes it start up OK; as soon as wifi is enabled it becomes unusable again. There is no problem with any other devices on the wifi, it is definitely the Kindle Fire that has the problem.
I can connect to the device through ADB, get a shell, and su in the shell. But I don't know what I'm looking for - I haven't done anything with Android before. My first thought was to look in /var/log, but I soon found that doesn't exist.
Can anyone advise how to go from here?
Thanks
Graham
Click to expand...
Click to collapse
I would not spend time trying to debug the WiFi issue. Given you have root + ADB access recover whatever personal files you need and then reload FireOS (preferably 5.1.2; 5.3.1 will also work) from the stock recovery menu. Fixing radio issues is akin to tossing sawdust in the transmission. It will likely come back to bite you later.
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
navtis123 said:
OK, I've gone back to 5.1.2 and repeated the process. It's all working again now, but since I don't know why it stopped working before am afraid it can just happen again at random - it's better to have a reason for things!
Thanks for the advice anyway.
Click to expand...
Click to collapse
navtis123 said:
Left it on for half an hour and its gone back to the original behaviour: on the screen saver, then the fire screen, back to the screen saver, then the fire screen. It doesn't stay long enough on the screen saver to open it and turn the wifi off, I have to get it to disconnect by taking it out of range or turning the house wifi off.
Click to expand...
Click to collapse
Rolling back to stock eliminated many possibilities and suggests the likely root case is hardware based assuming you (or Amazon) did not install/update any apps after restoring 5.1.2. Possible one of the chips is overheating triggering a boot loop. If the device is still in warranty Amazon will exchange it. If not you can attempt to load FireOS 5.3.1 (latest rootable version). Given the symptoms that should not make a difference but you have nothing to loose. Just don't go lower than 5.1.2 as device will brick.
Also try moving to a different location (friends house, coffee shop, etc) to see if the AP makes a difference. Not common but certain multi-band APs have been known to trigger device instability.
Hey Community!
So for years I've been flashing ROMs and stuff on my android phones. Recently I bought a Amazon Fire 7 5.th Gen and tried to downgrade it from 5.1.4 to 5.1.2 so I can use the SuperTool to do the root and other stuff.
But obviously I sideloaded a 5.1.2 FW that was not meant for my Fire 7. After the next reboot the screen remained black. Pushing the power button for more than 30 secs didn't help. Same with the button combination. Opened the backcover, removed the battery, let it sit for a minute and try again. Nothing
When I try to connect the Fire7 to my PC, Windows does the typical "device attached" aka "du-dum" sound. About 1 sec later I hear the "device detached" sound. This scheme repeats iteself in a unregular cycle. Sometimes the device gets attached again after 2 secs, sometimes after 10 sec.
Bought a Factory Cable. Connected it... nothing. So now I think i got a solid hard brick for 23 Euros (plus 10 € for the cable). My hope is gone, but maybe someone got another hint?
Thanks for your help!
I don't think the back cover for the fire 7 (2015) is removable. Are you sure you have identified the device correctly?
dustin66 said:
Hey Community!
So for years I've been flashing ROMs and stuff on my android phones. Recently I bought a Amazon Fire 7 5.th Gen and tried to downgrade it from 5.1.4 to 5.1.2 so I can use the SuperTool to do the root and other stuff.
But obviously I sideloaded a 5.1.2 FW that was not meant for my Fire 7. After the next reboot the screen remained black. Pushing the power button for more than 30 secs didn't help. Same with the button combination. Opened the backcover, removed the battery, let it sit for a minute and try again. Nothing
When I try to connect the Fire7 to my PC, Windows does the typical "device attached" aka "du-dum" sound. About 1 sec later I hear the "device detached" sound. This scheme repeats iteself in a unregular cycle. Sometimes the device gets attached again after 2 secs, sometimes after 10 sec.
Bought a Factory Cable. Connected it... nothing. So now I think i got a solid hard brick for 23 Euros (plus 10 € for the cable). My hope is gone, but maybe someone got another hint?
Thanks for your help!
Click to expand...
Click to collapse
NightCrayon said:
I don't think the back cover for the fire 7 (2015) is removable. Are you sure you have identified the device correctly?
Click to expand...
Click to collapse
- back cover on 5th gen Fire can be removed with a bit of 'encouragement'
- no unbrick solutions (yet) for the described scenario
- if still under warranty contact Amazon for a one time no-questions-asked courtesy exchange
Davey126 said:
- back cover on 5th gen Fire can be removed with a bit of 'encouragement'
- no unbrick solutions (yet) for the described scenario
- if still under warranty contact Amazon for a one time no-questions-asked courtesy exchange
Click to expand...
Click to collapse
"Encouragement" is the right answer
Gonna trie an exchange. I know the kindness of the support so I feel a bit guilty to ask for a refund for my failure. But lets see. TY for your answer