I'm another noob that made the same mistake as the others in this post. Is there any chance of a fix for this coming along? Or should I just give up on my Kindle and bin it. Thanks.
[Q] Kindle Fire 2 completely bricked after flashing wrong bootloader.
- Thread starter jophish
- Start date
If it's any consolation, I contacted the Moderators, and they put a warning on the KFU thread to hopefully deter anything like this from happening in the future (not that someone won't try it anyway).
if only I can order one for cheap...
too bad I'm in Philippines and shipping cost is expensive...mindmajick
Account currently disabled
Kindle Fire 10.2.6
So is there a solution for completely bricked KF 10.2.6 or not, or do you know whether there is somebody out there that is working towards the solution?
Mine doesn't turn ON at all after I flashed FFF Gapps and Jellybean 4.2 using TWRP (cordless).
Any help appreciated peeps :good:
So is there a solution for completely bricked KF 10.2.6 or not, or do you know whether there is somebody out there that is working towards the solution?
Mine doesn't turn ON at all after I flashed FFF Gapps and Jellybean 4.2 using TWRP (cordless).
Any help appreciated peeps :good:
I got the same problem - Black screen, No light in the Led button etc.
But so fare i got it responding to OMAP4BOOT butI I need the right files and config to UnBrick it - but as long as I get the response, there is hope
I you figure that out - please tell me :laugh:
I got the same problem - Black screen, No light in the Led button etc.
But so fare i got it responding to OMAP4BOOT butI I need the right files and config to UnBrick it - but as long as I get the response, there is hope
I you figure that out - please tell me :laugh:
Interesting. I will have to look at this omap4boot when I get to a PC.
Sent from my MB860 using Tapatalk 2
I got the same problem - Black screen, No light in the Led button etc.
But so fare i got it responding to OMAP4BOOT butI I need the right files and config to UnBrick it - but as long as I get the response, there is hope
I you figure that out - please tell me :laugh:
Wew.. It's been a while since I bricked my kf2 device... Tried shorting trick again for the last time... But still no luck.... t.t
Any other ideas guys? hehe
saved me from hell!!!!! thnx guys
:laugh:
thank god i read these posts.....i was abt to flasf FFF on my Kindle fire 2!!!!!!!!!!!!! WHEW!!!!!!!!!!!
:laugh:well, when you say "my device turned on the sudden of ansd never went back on" perhaps. But when they see that you've tried to root your device most likely not.
Hi,
Me too - I have the Kindle Fire HD7 2nd gen and mistook the guide for the KF 2nd gen to apply to mine. Anyone had any luck salvaging this? I'd be fine if I got get into fastboot but can't even get windows to recognise...
J
The only way to fix a hard bricked kindle is to solder a sdcard reader to the emmc pins on the motherboard and flash the bootloader partition from linux, lsat i checked we don't have the pins mapped out for the 2013 kfhd so that method is not doable yet. I think someone was mapping them out but i don't remeber if its the 2013 model or not. Think they mapped some of them out though just not all. The omap flash(also known as shorting trick) method isnt going to work either so don't bother attempting it, we need a signed aboot file only amazon has and without it its imposible to flash the bootloader in that mode.
I find one solution - http://xdaforums.com/showthread.php?t=2415870
Is it only available solution for wrong bootloader on KF 2 ?
Is it only available solution for wrong bootloader on KF 2 ?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
I think you need a Factory cable to recover.
If you connect the Kindle to the PC and try adb devices in a terminal window, what do you see?
From the software version, you have KF2, as such you need to use the tools and ROMs from the KF2 threads. You could try to use the one click freedom boot and TWRP installer, to see if you can get that on.
From there you would probably have to push one of the 10.1 ROMs on, or the 10.2.6 recovery image, and then start again.
This seems to be happening a lot, and could be avoided if people read a bit more before using the wrong tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD1
Leave your Kindle plugged in for an hour using the normal cable, as it may be totally flat.
The attached diagram shows what pins need joining. If you can, make sure none of the other pins are shorting.
Hold the power button for 20 seconds, plug in your fastboot cable, power on the Kindle.
You should see some traffic lights on the screen.
If you can get fastboot enabled, you should be able to push the correct partitions back on using the partitions from the factory restore image, your backup files or from the recovery thread. Hope you get it running.
Sent from my Amazon Kindle Fire2 using Tapatalk HD1
You could have tried sending it back to Amazon, but you say you have opened it.
Sent from my Amazon Kindle Fire2 using Tapatalk HD1If it's any consolation, I contacted the Moderators, and they put a warning on the KFU thread to hopefully deter anything like this from happening in the future (not that someone won't try it anyway).1
The only way to fix a hard bricked kindle is to solder a sdcard reader to the emmc pins on the motherboard and flash the bootloader partition from linux, lsat i checked we don't have the pins mapped out for the 2013 kfhd so that method is not doable yet. I think someone was mapping them out but i don't remeber if its the 2013 model or not. Think they mapped some of them out though just not all. The omap flash(also known as shorting trick) method isnt going to work either so don't bother attempting it, we need a signed aboot file only amazon has and without it its imposible to flash the bootloader in that mode.
