Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
pgautraud said:
Hey everyone I totally screwed up my new KFHD and I would love some help. I tried to root it a couple days ago with the KFSOWI all in one tool and it seemed to work for a few minutes. SuperSU installed correctly and installed its binary but when I tried to use the root explorer in ES File Explorer it said that it failed so I opened up SuperSU again and it told me it needed to install the binary again as if it wasn't rooted. It failed to install it and Root Checker told me it wasn't rooted so I tried to re-root it with the same KFSOWI tool.
This is when it got messed up. The tool said it rooted successfully again but when I tried to boot it up normally (I had been using a factory cable to get into Fastboot) it got stuck on the Kindle Fire logo screen (the white one not the orange one). I thought maybe it was a problem with the root so I tried to unroot it with another tool and ever since then it briefly shows a red screen at boot and then stays on the Fastboot logo. I've tried holding the power button down for 20 seconds, restoring the firmware to stock (got an error about system.img saying that it wasn't a sparse file), and restoring to an older firmware. None of this has made any difference.
I read somewhere that the red screen is a sign of a missing bootloader but if that's true how do I get back to the stock bootloader? I had 11.3.2.2/7.4.8 installed before all this happened if that helps. I'm willing to try anything at this point. I would like to at least be able to use the Play Store but if I have to stick to stock FireOS I'll just endure it. If you have any questions ask away! Thank you all for your help.
Click to expand...
Click to collapse
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
stunts513 said:
ok first ting i wanna ask is what do you mean 11.3.2/7.4.8, because 11.x.x is for teh 2013 and 7.x.x is for teh 2012 kindle. Also red screen doesnt mean you are missing the bootloader, if you were missing that the device wouldnt even turn on. That error you got when trying to restore the device is probably part of why its not working, probably need to fix that to fix the device, it never reflashed the system partition when it errored and said that the image was not sparse, which is a bit odd in itself considering how the method we use to fix it works.
Click to expand...
Click to collapse
I have the 2013 version, I just bought it from Amazon two weeks ago and it said the firmware version was 11.3.2.2. I had said 7.4.8 because whenever I searched for a way to root 11.3.2.2 the most recent information I could find talked about 7.4.8 so I thought they were the same thing. So is there a way for me to sparse the system image? Or are there system images out there that are sparsed? If you have a tool that you prefer over others I would love to try it.
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Try this, I think this was the thread I was looking for and if its the same one you posted a link to then my bad because I'm half asleep.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
What am I supposed to try?
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Wow I was half asleep after all I didn't post the link... Lemme get my bearings and retrace my line of though.
Edit: here's the link I was intending on posting: http://forum.xda-developers.com/showthread.php?t=2685090
Weird thing is i remember copying the URL for the thread, Idk why I never pasted it.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the link! I actually tried the newest version of his tool and it works up until it says "waiting for boot..." I assume it means it's waiting for a normal boot but since I can't get it to boot past the Fastboot logo (even with a normal cable or no cable at all) it never gets any further. Any suggestions?
Sounds like the bootimg needs to be reflashed. Sometimes a bad bootimg causes it to kick into fastboot upon boot.
Sent from my Amazon Kindle Fire HD using Tapatalk
Related
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
I'm not sure really how to help, but if you can describe the last thing you were doing prior that will help people diagnose it. Were you rooted? Or trying to root? Did you try to modify any system files?
I have the same problem. I was rooted. I was trying to copy the vendor apk into system/ app folder. I think I accidently made copy of app folder, it said app copy then froze. I clicked system restore. did nothing.
Are you able to reach the system with adb shell at all? or not? If not, I think you are stuck sending it back to Amazon for repair/replacement. If you can, you should be able to use the same method you used to root to get /system RW again, and try to fix it up.
I don't know how to use ADB. I used the one click root method. My computer isn't recognizing the device when plugged in. Is there a step by step guide on how to fix it or will it be possible in the future?
If its not recognized, then its unlikely that adb will work. If I had a bricked device though...I would start reading and trying to get that working. If you really don't feel confident in messing around and trying to fix it, call Amazon and ask them to send you a new one.
neut401 said:
my kindle fire hd is caught in a bootloop with the only options being to reboot it or reset it to factory defaults. neither fixes it.
please help, it'd be greatly appreciated!
Click to expand...
Click to collapse
what do you do so that KFTT state in bootloop?
can you take screenshot? or take a picture?
I am having the same problem.
any luck fixing it?
Hi, I am in the same situation. Here in Spain we have the KFHD since 4 days ago.
I rooted it correctly via ADB. I installed google play and installed several app's apparently without difficulties. The issue came after putting the Go luncher HD apk on system\app. After that I rebooted the device and appeared the two luncher options. So everything ok. I was moving around my new luncher and everything was ok, but suddenly the device rebooted and I had the same issue here explained. Bootloop and no factory default possible. Of course just rebooting didn't solve it. I have to say that the last thing I was doing before the sudden reboot was modifying permissions from SU. Maybe it's related, so don't touch anything from there. ADB was not working any more so very few things to try...
Amazon accepted a replacement (I just said what happened but not why) and now I'm waiting a new one.
Hope this can help.
Regards,
If you're willing to do a little work, you can try this recovery method: http://forum.xda-developers.com/showthread.php?t=1951254. Personally, I would just send in the device to be replaced, and not tell them the exact circumstances of how the problem happened. Amazon's generally pretty good about returns and replacements while you're still within warranty.
I shouldn't have restored factory defaults
I am in the same issue
The main mistake I made was selecting "Reset to Factory Defaults"
This automatically turns off the debug mode and with it stopped any communication between my PC and the Kindle Fire HD 7". Even the Factory cable I bought for £3.19 didn't help. The driver shows like it is installed correctly and my Kindle shows Fastboot on the screen when connected, but there is no communication.
I only got it for Christmas and I've goosed it. I am now hoping Amazon will be sympathetic and believe that it just started looping itself without me modding it.
When you reach the fastboot screen unplug factory cable and insert the usb that came with it. Then check your drivers to make sure they are Installed properly. Then use system Img restore tool to restore, follow directions exactly
Sent from my KFTT using XDA Premium HD app
Hello All! I was messing around with App Quarantine and ended up bricking my KFHD (not sure what I did because I was still messing around with it.) My KFHD is rooted but I didn't install TWRP or any type of recovery program. Is there any way for me to unbrick this or am I stuck with a fancy paper weight?
Ichigo said:
You guys should check the 1st gen. Kindle Fire Forums for similar problems and solutions.
Android>iOS... Android FTW!
Click to expand...
Click to collapse
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
[email protected]@dog said:
Lord NO! Any Kindle with the letters HD after Fire have nothing in common. Anything run to access the system or modify it will guarantee a permanent brick with NO WAY OUT.
Click to expand...
Click to collapse
Technically, the factory cable will still work, even if there are ways to know that you shouldn't do some things (like number 4 in the thread in my signature).
Ichigo said:
Way to bump an old thread.
Click to expand...
Click to collapse
It was sort of a failed attempt, so what the heck.
So I got the Red Triangle, and I can choose reboot your kindle (which doesn't solve any problem) and Reset to Factory Defaults. Is there any way I can access my kindle folders from the computer. I have some important documents which I don't want to loose
Nope, but that won't matter, because you probably just need to reflash the system partition to fix whatever you did. What exactly did you do before this happened?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Actually I did nothing. The only thing I noticed is that it was low in space for some while. Out of sudden it froze, I closed the tablet and then that message showed. So what do you recommend? Do you have a link with the recommended step. You say I might be able to save my personal data?
I tried one time to root... half year ago. But I gave up, I had a bad tutorial... I don't think I made changes to the system.
rajavan said:
Actually I did nothing. The only thing I noticed is that it was low in space for some while. Out of sudden it froze, I closed the tablet and then that message showed. So what do you recommend? Do you have a link with the recommended step. You say I might be able to save my personal data?
I tried one time to root... half year ago. But I gave up, I had a bad tutorial... I don't think I made changes to the system.
Click to expand...
Click to collapse
A red triangle is just a soft brick. This should be a simple enough fix in regards to what can happen. A red triangle means that the Kindle is, for one reason or another, not booting into the software.
You will need to make or buy a factory fastboot cable so you can access the bootloader. This is the only thing you can do at this point. When you get that cable follow these instructions/tutorials
First you need to restore using KFHD System.img Restore Tool located http://forum.xda-developers.com/showthread.php?t=1951254 This will have you restored with root access.
That root will break when Amazon does an OTA update unless you use Kindle Fire FirstAid to "remove OTA updates." You can go ahead and use it to install Goggle Apps/ Play Store as well. Find that here http://forum.xda-developers.com/showthread.php?t=2096888
Then you can install a 2nd bootloader and TWRP if you want. http://forum.xda-developers.com/showthread.php?t=2271909 and http://forum.xda-developers.com/showthread.php?t=2128848 are both a way. One flashes and one uses ADB commands to pus/pull.
Then slap a ROM on that bad boy. Most of them are found after one of the tutorials listed. About 2/3rds down through the tutorial. http://forum.xda-developers.com/showthread.php?t=2271909
If you get stuck in TWRP without a ROM or a bootloop then use Stunts fix to get a ROM pushed onto TWRP http://forum.xda-developers.com/showthread.php?t=2459498
Here is a great help thread where the 2nd bootloader and TWRP write ups are simplified a bit. I recommend a read of that too http://forum.xda-developers.com/showthread.php?t=2347170
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Hyperiunn said:
Hey, I recently rooted my Kindle Fire HD and everything was working great, until I installed an Xposed tweak that caused my Kindle to start boot looping and then thereafter I went ahead and screwed it up even worse - by messing with various fastboot methods to get it working again. Yeah... I should have just left it as it was, I know...
I've read about how there are signature checks whenever the Kindle boots up which I'm assuming I don't have anymore. So, I'm curious if there is anyway to come back from this? From what I've read, if I had backed up the partitions, technically I should have been able to restore them - but unfortunately here we are.
I've also downloaded the latest update from Amazon 'update-kindle-11.3.1.0_user_310084920' and after converting it to a zip file, there is a 'boot.img' and a 'recovery.img' which I would assume would have the signatures already within them, but no system.img. Is there anyway for someone to create an exact backup of that file, or is that not possible right now without a second bootloader?
I'm honestly really unsure of what to do here, I've tried a myriad of different approaches and still it looks like this is a bad brick... However I do hope someone out there has a solution, I'd love to get this device working again.
Oh and what happens whenever I start it up, is that I just get the Amazon Kindle Fire Logo (Pure White), without any changes. It doesn't turn gold with the animation or anything.
Click to expand...
Click to collapse
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
The 2013 Kindle Fire HD is not setup for Xposed yet. There is no bootloader access yet therefore there is no way to recover yet. You have two options at this point. Wait until there is a bootloader exploit or contact Amazon for an exchange.
The only things available are root, remove OTA updates and remove lock screen ads. Even Google Play is only for window shopping at the moment.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Fastboot
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Hyperiunn said:
Nah nothing so far for the 2013 unfortunately. I don't think there's been much interest in this model as of yet.
Click to expand...
Click to collapse
I've been interested. Unfortunately, my mother won't let me touch her new 2013 Fire HD. Still, if you can find someone who's rooted and not bricked, maybe they could backup their boot, system, and recovery .imgs for you and post them for you. And since they're already rooted, you would be too (someone correct me if I'm wrong). If I could get a temporary root or find a way to remove root later I would back them up for you.
The system restore tool for the 2012 Fire HD flashes the boot, recovery, and system partitions. Theoretically, the same tool would work, but only if you replaced the .img files with the ones for the 2013 Fire HD.
Gamingmayr said:
As long as you can boot into fastboot-mode nothing is lost. (if you can't -> buy a fastboot-cable. it is much cheaper than a new Kindle. They cost about 15$).
I used this useful tool. It just flashes the old system, boot and recovery on your Kindle. (all files are included in the downloadable zip file).
This tool was very useful for me and saved my Kindle very often (I am a real flashoholic...). Maybe there is something like this for the new 2013 KFHD too?
Click to expand...
Click to collapse
There is no confirmation that a fastboot cord even works with the 2013 model nor are the stock images available yet. The 2012 KFHD and the 2013 KFHD do not use the same images.
---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------
Hyperiunn said:
For anyone wondering, xposed actually works perfectly with a good number of modules, but don't install Xthemeengine, that'll cause the bootloop.
Click to expand...
Click to collapse
It won't work on the 2013 Kindle fire HD yet though. Since that is the topic here I guess that narrows it down to this tablet not all the others don't it.
Fastboot cable works just fine with the one I have.
Ok, so I'm a noob when it comes to this stuff, but I have managed to root my Kindle Fire HD 7" and I installed the Google play store, so I was happy thus far. Yesterday I lost root and couldn't figure out why. Today I noticed that my Kindle had done an update from 7.4.6 to 7.4.8 and I'm wondering if this is why I lost root? If so, how can I fix this to get my Kindle back into root? Like I said, I'm a noob and don't want to screw up my Kindle messing around with stuff when I don't have a clue. Any advice would be of great help, thanks in advance.
Oh yeah, I should add this information: I get this pop up from Superuser, "There is no SU binary installed and Superuser can not install it. This is a problem"
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
masterndentske
stunts513 said:
Yea when it updates it clears the system partition where the su binary is stored, you need to reroot it. Never heard of a 7.4.8 update, but if it is a new one and you can reroot it then you can just downgrade it with kindle fire first aid by sticking it into fastboot with a simple "adb reboot bootloader", think kffa will do it for you though.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
cautiousone said:
" Never heard of a 7.4.8 update, but if it is a new one and you can reroot it " Hmmmm, the way you worded that makes me feel like I might be stepping into uncharted territory if I try to root it again and I don't like the thought of that. I'll think about it and maybe give it a try tomorrow after I get some sleep and my head is clear. Thanks for the advice, I really appreciate it.
Click to expand...
Click to collapse
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
blackeyeX2 said:
I had the same problem starting yesterday. My Kindle upgraded to 7.4.8 and any app requiring root stopped working, namely Google Play Store, SuperUser, ... I used KFFirstAide to re-root the Kindle and all is working so far.
Click to expand...
Click to collapse
:good: Awesome, thanks for passing that on to me, I'm going to give it a go and see what happens. I'll post a status update later today after I've had a chance to thoroughly test it.
:victory: Well I got it to root again and reinstalled google play with no issues to report, all went well. So is there a way to stop Amazon from updating my Kindle in the future? Now, the next task is to get a second boot loader on it, although I don't have a fastboot cable, so I'm kinda chicken, hahaha. But I'm feeling confident now, so maybe I'll give it a shot tonight. Wish me luck... A big thanks for the help, I guess I just needed some reassurance on re-rooting the thing and I'm happy.
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
kindle fire hd 7.4.8
same thing happen to me so I tried getting adb to work witch it didn't that well, so I downloaded the update .bin file from amazon and edited it useing winRAR just added SuperSU to /system/app then changed a few things in kindle first aid then used a fastboot cable to upload the custom update so my kindle is running v7.4.9 witch I changed it to because it didn't work any other way. i'll make a video
dEADwEIRD said:
I'm having this issue also. Same update, same loss of SU + Play store.
I can't get my kindle to root like before though. It says it was successful but my fire becomes extremely laggy, no icons appear, where the navigation swipe is there are slightly darker vertical lines and the only way I've fixed it is by factory restore.
How are you rerooting???
I can't remember how I rooted in the first place, I only remember that I had massive issues getting GP store on and used this KFFA which is what I'm now using to reroot.
http://forum.xda-developers.com/showthread.php?t=2069329
Any suggestions would be massively appreciated
Click to expand...
Click to collapse
I just followed the same steps as I did the first time I rooted it, I used KFFA. But this time around some of the actions described didn't happen, like Superuser didn't ask for permission as it did the first go around and a few other little things, but I just took it slow and easy and it came out working fine. Also I used KFFA to install GP, it also skipped a few actions, but I just have it a little extra time to do its thing and it works perfectly. I saw a fix for the laggy screen and icons issue somewhere, I think it's in KFFA? I would have to double check that when I get home to be certain.
stunts513 said:
Just make sure you downgrade the bootloader first, if you don't use the fireflash method then I recommend making sure to check the md5sum of the bootloader before downgrading it so you don't end up with a paperweight.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up on that, I've held off on doing it until I have more time to research it. I like to feel somewhat comfortable going into it and not totally freaked out. Thanks again, you guys are great around here.
Sorted.
I rooted using The Bin4ry Method and using KFFA to bring all the other systems back on line.
is anyone having problems with ADB and fastboot on 7.4.8?
Because I tried rooting using KFFA that didn't work I kept getting errors so I tried using fastboot to flash the recovery using this code
Code:
fastboot flash recovery recovery.img
I get "device not found" or when it dose work i get "failed to flash" (something like that) but i have the adb drivers installed would there be different ones for 7.4.8? When I type
Code:
fastboot device
it finds the device it just dosn't work when I want to flash
and only half the adb commands work
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
"... I used KFFirstAide to re-root the Kindle and all is working so far."
I tried using bin4ry's root, which is how I originally rooted my kindle, but it did not work.
I am pleased to say that KFFirstAide was able to restore root.
Thank you xda for pointing me in the right direction!
stunts513 said:
You have to have it with a special parameter telling it what the kindles vendor id is so it should look like this...:
Code:
fastboot -i 0x1949 flash recovery recovery.IMG
Try that.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thank you!!! i got root access by flashing with twrp recovery witch you can get more info at
http://forum.xda-developers.com/showthread.php?t=2128848
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
gregcavaretta said:
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
Click to expand...
Click to collapse
Thank's, KFFA not recovered and Bin4ry work only after turn off adb / usb debugging
Ciao dal Max
gregcavaretta said:
Thank you!!! i got root access by flashing with twrp recovery witch i downloaded at
http://teamw.in/project/twrp2/79
on my other kindle i used Bin4ry root witch work but i had to turn off adb/usb debugging and turn it back on during the process because it wouldn't find the device if i didn't
you can download Bin4ry here
http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
wire55 said:
Holy ****!!! Your kindle works after flashing the recovery IMG that was for the kf1???
Sent from my Kindle Fire HD 7 running PAC-man
Click to expand...
Click to collapse
stunts513 said:
wtf????? that was a twrp image for the kf1, that should have broken more than it fixed on a kfhd.
Click to expand...
Click to collapse
I posted the Wrong link i'm truly sorry if you messed up your kindle fire
Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?
Did you have amazon FireOS version 5.0.1 or 5.1.1?
If you had 5.1.1 then flashing 5.0.1 will brick it. And will cause your preloader to endlessly cycle as you describe. That "5.2.2" file Awesomeslayerg links to in his thread is 5.0.1, he really should have changed that post since anyone on 5.1.1 following his instructions will be hard bricked.
hAtE NeVeR dIeS said:
If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
Click to expand...
Click to collapse
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).
blueberry.sky said:
Did you have amazon FireOS version 5.0.1 or 5.1.1?
Could you have had 5.1.1 but accidentally flashed 5.0.1? That will cause your preloader to endlessly cycle as you describe.
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).
Click to expand...
Click to collapse
Before I flashed to CM12.1, I came from fireos 5.2.2. So I flashed Firmware 5.2.2 back.
Well, looks like I have to send the tab to amazon...
"5.2.2" is just the file name. We normally refer to it as FireOS 5.0.1, that is name amazon uses & system update menu displays. And it causes less confusion. I don't know why Awesomeslayerg uses "5.2.2" instead of 5.0.1.
hAtE NeVeR dIeS said:
I Installed CM12.1 using the flashfire method.
Click to expand...
Click to collapse
Did you ever try twrp? FlashFire is in beta & can be buggy. If you have 5.0.1 then you should really use twrp.
I downloaded the file linked in the post. Maybe It happens because I wiped everything before flashing the firmware and not after.
Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.
Awesomeslayerg said:
Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.
Click to expand...
Click to collapse
No problem dude. Things can happen so everything is alright. I am totally aware of that you are not responsible for damages that happen to the devices. Amazon is sending a new one. If i have to pay for this, its my problem not yours. You dont have to apologise.
But it will be great if you edit your thread and write in there, that the firmware you postet isnt fpr the 5.1.1. bootloader to prevent other users from making such a mistake.
hAtE NeVeR dIeS said:
Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?
Click to expand...
Click to collapse
I
think many people have this problem and I am of those
I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.
stewie2806 said:
I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk
sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thank you sir
I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices
FireBill said:
I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices
Click to expand...
Click to collapse
Won't let me create a scatter file on 5.0.1 stock, see attachment.
Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.
percussionking said:
Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.
Click to expand...
Click to collapse
Thanks, I appreciate you trying. It's always worth a shot
Can someone trying creating scatter file for 5.1.1? Maybe it works...hopefully it works.
Sent from my Moto G 2014 using Tapatalk
@lost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1
Kramar111 said:
@ost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1
Click to expand...
Click to collapse
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.
FireBill said:
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.
Click to expand...
Click to collapse
Thanks for trying that. It seems to be worse than I thought. I know it's probably going to be unlikely that we find a way to unlock the boot loader. So I guess we really need a OEM firmware file. Can anyone pitch in on that?
Sent from my Moto G 2014 using Tapatalk
I also bricked my Fire
Hi All,
I also bricked my fire while trying to downgrade to 5.0.1. Has anyone flashed ROM using any tool on bricked fire?