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.
Hello,
I ´m waiting an answer to my problem posted here http://forum.xda-developers.com/showthread.php?p=42053547#post42053547, but I have another question to post here.
How can I fix the bootloop if I have the ADB disable (and I think the third party is disable to)? My KFHD is version 7.4.1.
I will thanks if somebody could give me some helpful idea!
Gustavo.
Hey Elgari, just saw your problem and actually answered you in two different places Basically you can't use adb. You can only use adb when you're in recovery or when booted. You'll have to go with fast boot. Can you get into fastboot or do you have a factory cable? If you can get to fast boot then you can use the kindle SRT tool from the development thread.
DroidIt! said:
Hey Elgari, just saw your problem and actually answered you in two different places Basically you can't use adb. You can only use adb when you're in recovery or when booted. You'll have to go with fast boot. Can you get into fastboot or do you have a factory cable? If you can get to fast boot then you can use the kindle SRT tool from the development thread.
Click to expand...
Click to collapse
Thank you very much Droidlt! I´ve read your answers and is clear: need a factory cable to go with fastboot. As device manager recognizes the KFHD as adb android composite ADB interface, I had hopes of not requiring the factoy cable. Had also read some posts suggesting that it was not necessary, but now I understand I need one!! Thanks again. I don´t have a factory cable but will try to buy or make one.
I supose the SRT is the threat post by Onemeila, isn´t?
I love my KFHD and would like to understand why! This setback makes me love her even more. Would know If it was something I made wrong or if it was and accident.
Finally I must apologize for writing my problem in more than one place, but I was really frustrated!!
Thanks once again.
No prob Yep just a factory cable. Just make sure your kindle is off, plug the factory cable into the computer and then your kindle. It will automatically boot up your kindle into fastboot mode. Then swap out the factory cable for a regular usb cable and run onmeila's SRTool, doesn't really matter which version you download, you can root them all. Flash whatever version you downloaded and you have a new kindle again :thumbup:
from my Viped out one x
What I make wrong?
DroidIt! said:
No prob Yep just a factory cable. Just make sure your kindle is off, plug the factory cable into the computer and then your kindle. It will automatically boot up your kindle into fastboot mode. Then swap out the factory cable for a regular usb cable and run onmeila's SRTool, doesn't really matter which version you download, you can root them all. Flash whatever version you downloaded and you have a new kindle again :thumbup:
from my Viped out one x
Click to expand...
Click to collapse
Hello Droidlt!
Well, I made a factory cable and put the kindle in Fastboot. I run option 1 of SRT and seems do the work: it begin with "sending systems, then Okay, after "writing systems, then okay and after it said finished, Welcome Back. But nothing changes!
I tried with option 3 to, and I tried changid the SRT folder to Plattform tools as I read on Onmelia´s threats. But same results.
My device manager recongnize my KIndle as Android ADB interface. I used the code adb shell su -c "reboot bootloader" and give me the results: device not found.
I make something wrong but I don´t figure what is it!!??
Thanks from now for any suggestion!
Hey Elgari, so did it boot up or no. What exactly did you see on the screen after you ran the SRTool?
Edit: Ahhh, I see what you did. You only need to use that command if the fast boot cable didn't work. Your fast boot cable did get you into fastboot though. Just unplug your kindle and reboot it. I think you're good.
DroidIt! said:
Hey Elgari, so did it boot up or no. What exactly did you see on the screen after you ran the SRTool?
Click to expand...
Click to collapse
The screen of the kindle never changes: always remains on Fastboot (in orange) with kindle fire bellow with small letters. In the PC I saw the menu first and then the others steps I´ve mentioned. Nothing else. Let me know if you need more information to try to help me.
It's late here but I'll be a few more minutes.
Elgari said:
The screen of the kindle never changes: always remains on Fastboot (in orange) with kindle fire bellow with small letters. In the PC I saw the menu first and then the others steps I´ve mentioned. Nothing else. Let me know if you need more information to try to help me.
It's late here but I'll be a few more minutes.
Click to expand...
Click to collapse
OK, go ahead and turn your kindle off by holding down the power button for 20 seconds, hit the power button again like you would normally then. It should boot up.
DroidIt! said:
OK, go ahead and turn your kindle off by holding down the power button for 20 seconds, hit the power button again like you would normally then. It should boot up.
Click to expand...
Click to collapse
I am exactly having the same issue, currently on Fastboot Screen and turned the kindle off by holding down the power button as per your instruction. After reboot it goes back to kindle Fire HD logo screen.
Pls advise.
DroidIt! said:
OK, go ahead and turn your kindle off by holding down the power button for 20 seconds, hit the power button again like you would normally then. It should boot up.
Click to expand...
Click to collapse
Thank you Droidlt! I did that and it returns to normal boot but it continues locked in boot screen: normal Kindle Fire Logo no matter how long I leave it turned on. I left all night charging plugged into the wall. I tried last night another thing. I run step 3 of Kindle Fire First Aide. Same things, it run all ok but no fix the problem.
Other comment is that when running step 5 of SRT my kindle screen changes to normal boot and in the pc the screen back to SRT menu doing nothing more.
I will ty now tu run again step 1 of SRT and I will keep you advised
EDIT 1
I run SRT (step 3 instead 1 because I think is better). Same results: stays in the initial screen with the logo of kindle fire with a kind of light passing through. I run step 5 to chek fastboot status and same results: the kindle changes from fastboot to normal but still stay in the initial sreen as described. I run step 6 and in the PC the screen said waiting for devices while kindle is in the screen described. I left 10 minutes and nothing changes. Now I turn off the kindle holding down power button for 20 seconds, wait 5 seconds and hit the power button again: same results initial screen with kindle fire logo, etc.
In my desperation being the kindle in this initial screen I just ran Kindle Fire First Aide to check ADB status. The results was I have ADB comunication !!! Its says "device attached D025A0A024421317" "It looks like ADB is enabled". But kindle is in the same screen . . .
EDIT 2
FIXED!!!!!!!!! Or I think its starting to be fixed!! Y run various steps of KFFA and finallly with option 25 (Restore from Kindle backup folder) and disabling OTA its seems to be fixed. I said its seems because its a backup from my previous status which was who has the problem of turn off by itself.
What do you think? I leave it like that and see what happens or I do anything extra?
Thank you again!!!
Elgari said:
Thank you Droidlt! I did that and it returns to normal boot but it continues locked in boot screen: normal Kindle Fire Logo no matter how long I leave it turned on. I left all night charging plugged into the wall. I tried last night another thing. I run step 3 of Kindle Fire First Aide. Same things, it run all ok but no fix the problem.
Other comment is that when running step 5 of SRT my kindle screen changes to normal boot and in the pc the screen back to SRT menu doing nothing more.
I will ty now tu run again step 1 of SRT and I will keep you advised
I run SRT (step 3 instead 1 because I think is better). Same results: stays in the initial screen with the logo of kindle fire with a kind of light passing through. I run step 5 to chek fastboot status and same results: the kindle changes from fastboot to normal but still stay in the initial sreen as described. I run step 6 and in the PC the screen said waiting for devices while kindle is in the screen described. I left 10 minutes and nothing changes. Now I turn off the kindle holding down power button for 20 seconds, wait 5 seconds and hit the power button again: same results initial screen with kindle fire logo, etc.
In my desperation being the kindle in this initial screen I just ran Kindle Fire First Aide to check ADB status. The results was I have ADB comunication !!! Its says "device attached D025A0A024421317" "It looks like ADB is enabled". But kindle is in the same screen . . .
Click to expand...
Click to collapse
Make sure your drivers are installed correctly for you too ipsearch. that could be the problem if not uninstall them and then reinstall.
CVanB said:
Make sure your drivers are installed correctly for you too ipsearch. that could be the problem if not uninstall them and then reinstall.
Click to expand...
Click to collapse
Thank you CVanB. I think its fixed by now!
Elgari said:
Thank you CVanB. I think its fixed by now!
Click to expand...
Click to collapse
No prob.
Elgari said:
Thank you CVanB. I think its fixed by now!
Click to expand...
Click to collapse
So you're booting now? I was thinking back on what I suggested earlier, and I actually should have suggested the 7.2.1 SRT version. I remembered that there are no options in the 7.2.1 version, it's older but it's all automatic, and therefore easier. All is good now though?
---------- Post added at 10:37 AM ---------- Previous post was at 10:24 AM ----------
Elgari said:
In my desperation being the kindle in this initial screen I just ran Kindle Fire First Aide to check ADB status. The results was I have ADB comunication !!! Its says "device attached D025A0A024421317" "It looks like ADB is enabled". But kindle is in the same screen . . .
Click to expand...
Click to collapse
This is good to know too, we all learn something This is the first time I've heard of a kindle being recognized by adb in a semi-booted state. I've had that with one of my phone's before but not seen it since (a couple years) :good:
---------- Post added at 10:40 AM ---------- Previous post was at 10:37 AM ----------
One other thing, if you need any help with rooting or anything or any other questions, myself or CVanB I'm sure too will be happy to help :good:
DroidIt! said:
So you're booting now? I was thinking back on what I suggested earlier, and I actually should have suggested the 7.2.1 SRT version. I remembered that there are no options in the 7.2.1 version, it's older but it's all automatic, and therefore easier. All is good now though?
Click to expand...
Click to collapse
In my last post I was editing and adding what was done to you had the whole "history"!
Now the kindle works fine but I have still plugged with usb to the pc. The problem I had before and was he origin of all the subsequent problems was that when unplugged and surfing internet she power off. Now I left it in version 7.3.1 and not going to upgrade to 7.4.0 in case that was the problem. In a little while I will unplug and see if it goes well.
I used SRT version 1.3.5.
We will see what happend. Thanks again!!
DroidIt! said:
[/COLOR]One other thing, if you need any help with rooting or anything or any other questions, myself or CVanB I'm sure too will be happy to help :good:
Click to expand...
Click to collapse
Yes, thank you!! I don´t know now if I´ ve root. I have super user but no have root checker. All previous times I root with KFFA . You suggest try something else if I need to re-root?
I have all my old apps backuped with Titanium, gradually I will recovering them. The others are in Amazon Cloud.
My fear is that one of those applications might be causing the original problem (if that can happen). Because I keep wondering if installing PPP Widget and plug my 3G modem could be the cause of the disaster!!
Elgari said:
Yes, thank you!! I don´t know now if I´ ve root. I have super user but no have root checker. All previous times I root with KFFA . You suggest try something else if I need to re-root?
I have all my old apps backuped with Titanium, gradually I will recovering them. The others are in Amazon Cloud.
My fear is that one of those applications might be causing the original problem (if that can happen). Because I keep wondering if installing PPP Widget and plug my 3G modem could be the cause of the disaster!!
Click to expand...
Click to collapse
I saw you mention PPP before, I had not heard of that so I just looked it up on the play store and now I get it. That could possibly be your problem, not certain but possible. Amazon modified stock android to such an extent that what may work on almost all other android devices may not work on the kindle. I would suggest to do everything else first: get your kindle exactly how you want it and then do a nandroid backup, and then if you still want PPP, then try it. Communications always seem to be kind of a sensitive issue with any smart device, so you just need to be really careful when you want to make modifications to the stock abilities of that device. So, like I said, I would just get your kindle where you want it, I'm assuming rooted, custom rom, etc., back it up and then maybe try PPP.
---------- Post added at 11:24 AM ---------- Previous post was at 11:16 AM ----------
Oh and I would just suggest that you check to see if you have root first before running any tools. That would be the place to start. I always use this app https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd It quickly and painlessly checks for root. As far as tools go, I would just say to use whatever is comfortable and familiar to you. If that tool worked good for you before then just keep using it. If you could just run the app I linked you to and then let me know if you have root or not, then we can go form there. Glad your kindle's alive again
Edit: just read your post again, if you have superuser, then you have root
Edit 2: I'm writing alot here, but oh well Do you have second bootloader + TWRP installed? That would actually be your next step. You can do that by following the instructions here http://forum.xda-developers.com/showthread.php?t=2128848 Once that's done then you can download any rom you want and go into recovery and flash. If you have an amazon prime account or like the amazon reading app that came with the kindle, I would suggest Kinology. If you don't really care about either of those things, then you can go with CM or one of the variants, they're all really pretty good. Anything else, just let me know
DroidIt! said:
I saw you mention PPP before, I had not heard of that so I just looked it up on the play store and now I get it. That could possibly be your problem, not certain but possible. Amazon modified stock android to such an extent that what may work on almost all other android devices may not work on the kindle. I would suggest to do everything else first: get your kindle exactly how you want it and then do a nandroid backup, and then if you still want PPP, then try it. Communications always seem to be kind of a sensitive issue with any smart device, so you just need to be really careful when you want to make modifications to the stock abilities of that device. So, like I said, I would just get your kindle where you want it, I'm assuming rooted, custom rom, etc., back it up and then maybe try PPP.
---------- Post added at 11:24 AM ---------- Previous post was at 11:16 AM ----------
Oh and I would just suggest that you check to see if you have root first before running any tools. That would be the place to start. I always use this app https://play.google.com/store/apps/...tcheck&feature=nav_result#?t=W251bGwsMSwyLDNd It quickly and painlessly checks for root. As far as tools go, I would just say to use whatever is comfortable and familiar to you. If that tool worked good for you before then just keep using it. If you could just run the app I linked you to and then let me know if you have root or not, then we can go form there. Glad your kindle's alive again
Edit: just read your post again, if you have superuser, then you have root
Click to expand...
Click to collapse
Yes I use root checker too but I don´t have installed it yet. As I don´t have now Google Play instaled then I download Root analyzer from amazon store (is free) and I have root access!!
I will install Google Play form KFFA. Did you agree with that?
Try...
Elgari said:
Yes I use root checker too but I don´t have installed it yet. As I don´t have now Google Play instaled then I download Root analyzer from amazon store (is free) and I have root access!!
I will install Google Play form KFFA. Did you agree with that?
Click to expand...
Click to collapse
Use: http://forum.xda-developers.com/showthread.php?t=2271909
He makes good quality and easy to understand guides and it goes through rooting, google play, flashing and more.
I would highly recommend this guide. Also, try flashing Hashcode's cm10 JB rom it 100% working. The link is in the guide.
Happy Flashing
Elgari said:
Yes I use root checker too but I don´t have installed it yet. As I don´t have now Google Play instaled then I download Root analyzer from amazon store (is free) and I have root access!!
I will install Google Play form KFFA. Did you agree with that?
Click to expand...
Click to collapse
There's a couple ways to skin this, you could either do like CVanB said or you can also go with Hashcode's method here http://forum.xda-developers.com/showthread.php?t=2128848 I used the Hashcode thread and it worked for me and CVanB used seokun's and it worked for him. I would say you could go either route really. If you go the Hashcode route, after you get that done then you just install a rom and they have gapps included, no need to install seperately :good:
---------- Post added at 12:24 PM ---------- Previous post was at 12:07 PM ----------
Oops, gotta correct myself. With CM10 you flash GPlay when you flash the rom :good:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
I lost root again, restored it with Bin4ry and disable updates using KFFA. The launcher works, but I can't get it to be the home button default and there is a lot of junk on there from when I had a freetime membership for my kid.
I would like to reset the device to factory and start over, what do I need to do? Looking at KFFA options 3,4 or 22 look like they would apply, I just wanted to find out what is the preferred method to accomplish this without screwing anything up.
Zuggel said:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
I lost root again, restored it with Bin4ry and disable updates using KFFA. The launcher works, but I can't get it to be the home button default and there is a lot of junk on there from when I had a freetime membership for my kid.
I would like to reset the device to factory and start over, what do I need to do? Looking at KFFA options 3,4 or 22 look like they would apply, I just wanted to find out what is the preferred method to accomplish this without screwing anything up.
Click to expand...
Click to collapse
Either 3 or 4 will work. If you don't remove OTA updates, the Kindle will get an updated pushed onto it and your root will break every time when the Kindle updates. So make sure to remove OTA updates using KFFA as well.
LinearEquation said:
Either 3 or 4 will work. If you don't remove OTA updates, the Kindle will get an updated pushed onto it and your root will break every time when the Kindle updates. So make sure to remove OTA updates using KFFA as well.
Click to expand...
Click to collapse
So I ended up using option 4 and a factory cable, for some reason it would not boot into fast mode via regular usb cable in KFFF. When it got done rebooting, I got a message asking if I wanted to use kindle or holo launcher (which I had previously installed).
That bit confused my, i thought that it would also have been deleted during the restore process?!!? Holo launcher & locker are installed and appears fully functional. Like i said before I would like to get this back to factory and start over. Superuser is on there also, did I forget a step or is there something additional that I need to do? I do not see any other apps other than what it came with.
It did take me to the set up process like on a new kindle.
Sounds like all it did was wipe the data folder. It has to go into fastboot to restore it to stock, if it doesn't want to do it during the process in kffa you can always use a mobile terminal on the kindle itself and type
Code:
su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Zuggel said:
So I ended up using option 4 and a factory cable, for some reason it would not boot into fast mode via regular usb cable in KFFF. When it got done rebooting, I got a message asking if I wanted to use kindle or holo launcher (which I had previously installed).
That bit confused my, i thought that it would also have been deleted during the restore process?!!? Holo launcher & locker are installed and appears fully functional. Like i said before I would like to get this back to factory and start over. Superuser is on there also, did I forget a step or is there something additional that I need to do? I do not see any other apps other than what it came with.
It did take me to the set up process like on a new kindle.
Click to expand...
Click to collapse
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.
stunts513 said:
Sounds like all it did was wipe the data folder. It has to go into fastboot to restore it to stock, if it doesn't want to do it during the process in kffa you can always use a mobile terminal on the kindle itself and type
Code:
su -c "reboot bootloader"
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
It was in fastboot, I used a factory cable to do so before I started KFFA. The screen said "fastboot kindle" or something to that effect.
LinearEquation said:
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.
Click to expand...
Click to collapse
That was my thought, to try it again, I just like to get other thoughts and opinions from those who are much more knowledgeable about andoid operating systems than myself. I will try another wipe tomorrow (option 3) and see if it has the desired effect.
LinearEquation said:
Did you use KFFA with a factory cord or a fastboot? When using KFFA, it is best to use a fastboot cord. Booting it into fastboot from USB can be done but I found it did not happen as often using KFFA. You can also use this tool here http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
You can also try your steps again and try number 3.
Click to expand...
Click to collapse
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
Zuggel said:
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
Click to expand...
Click to collapse
KFHD?
LinearEquation said:
http://forum.xda-developers.com/showthread.php?t=1951254 and he has a video at the bottom of this page http://androidcowboy.com/2013/06/how-to-return-kindle-fire-hd-to-stock/
Click to expand...
Click to collapse
LinearEquation said:
KFHD?
Click to expand...
Click to collapse
The link you gave me, that was the file name for the tool.
Zuggel said:
The link you gave me, that was the file name for the tool.
Click to expand...
Click to collapse
Oh gotcha. Yea, that's a System.img Restore Tool. Same idea as KFFA but a different method.
LinearEquation said:
KFHD?
Click to expand...
Click to collapse
Correct.
Zuggel said:
I tried option 3 twice with the same results. I am downloading KFHD and will give that a go tomorrow.
Click to expand...
Click to collapse
I tried to run the script myself and see exactly what you are talking about. I left a comment in Chris's thread. I'm sure he will give us the skinny on it.
Zuggel said:
I have a 7" kindle fire HD. When I first got it I rooted it with QemuRoot. I wasn't too worried about doing much, I just added halo launcher and the play store. Everything was good until the launcher quit working. To make a long story short, I had lost root and got it back via Bin4ry. Once again, was lazy and just installed the launcher and went about life.
Click to expand...
Click to collapse
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
LinearEquation said:
KFHD?
Click to expand...
Click to collapse
LinearEquation said:
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
Click to expand...
Click to collapse
I didn't need to root, I have a factory cable (assuming that was why I needed root to get into fastboot?!?). I tried KFHD_SRT_v1.3.5- 7.3.0 and it worked fine, except for some reason I could not turn on wireless. I am trying it again to see if it works out better for me. If not, I will try version 1.3.0
Zuggel said:
I didn't need to root, I have a factory cable (assuming that was why I needed root to get into fastboot?!?). I tried KFHD_SRT_v1.3.5- 7.3.0 and it worked fine, except for some reason I could not turn on wireless. I am trying it again to see if it works out better for me. If not, I will try version 1.3.0
Click to expand...
Click to collapse
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore. The fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. I never BS anyone one here. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
LinearEquation said:
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. Or at least research some threads on here. I never BS anyone one. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
Click to expand...
Click to collapse
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
LinearEquation said:
You need root to use the restore tool, not get into fastboot, like I stated. If you are not rooted, you can not use the restore tool listed. Use the USB cord to root and the fastboot cord to restore. The fastboot cord to restore to 7.2.3 so you have a matching boot.IMG. Then when flashing a 2nd bootloader and custom rom, you will most likely not bootloop or get a red screen.
I don't mind helping but you should read the help I offer before disregarding. I never BS anyone one here. I really suggest you read some topics on this or you might end up with a paper weight.
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
---------- Post added at 01:49 AM ---------- Previous post was at 01:46 AM ----------
Sent from my Kindle Fire HD 7 running 4.3 Paranoid Android using xda app-developers app
Click to expand...
Click to collapse
When I restored using KFHD, the image was already rooted, or so the title stated. When I replied I had already done what i replied about before I read your suggested route. It's still not right, so I am following your route and hoping the kids sleep long enough for me to finish it in one sitting!!
LinearEquation said:
OK, so here is how I worked it tonight. KFFA is a great utility but something hiccuped today. So here is the work around I just did.
First thing is root is needed for the restore utility to work. So root using this http://forum.xda-developers.com/showthread.php?t=2351201
Now you can restore to 7.2.3 and root (all one process) using KFHD System.img Restore. Choose the "KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery)" download here http://forum.xda-developers.com/showthread.php?t=1951254 This will root your tablet and give you a couple Gapps and Play Store.
Then use KFFA to "Disable Amazon OTA updates." Make sure to look for a Super User request right after you click to proceed so the process suceeds.
Now you can proceed with using the installed Play Store or installing a 2nd bootloadr/custom rom
This is the process that worked for me. Make sure you give the restore tool plenty of time to work. It can be done by booting your KFHD into fastboot by using fastboot commands or a factory cable. Here is a video concerning the restore tool listed https://www.youtube.com/watch?v=k-8lTMLCGfE
Click to expand...
Click to collapse
When I used Bin4ry, it added a second version of superuser to it (not sure if that is important or not), then I chose option 1 (Restore factory rooted with SuperSU) in KFHD. I now have a red triangle asking me to reboot or reset..
I ran option 1 with KFHD 1.3.5, back to working at least, only one version of superuser and the wireless is working. So far so good, and almost out of time right now.
Zuggel said:
When I used Bin4ry, it added a second version of superuser to it (not sure if that is important or not), then I chose option 1 (Restore factory rooted with SuperSU) in KFHD. I now have a red triangle asking me to reboot or reset..
Click to expand...
Click to collapse
You did something wrong. Your lucky you only got a red triangle and not a red screen. You need to restore again. When you are done, before exiting, clear the CASHE and data (think this is option 3 but confirm). You should already have root so use KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery.)
Always make sure ADB and allowing apps from unknown sources is turned on on your tablet. I always turn my tablet to never sleep or an hour so it stays away and turn the brightness up on the screen when modding. Every tool you use, reconfirm the settings are the same.
LinearEquation said:
You did something wrong. Your lucky you only got a red triangle and not a red screen. You need to restore again. When you are done, before exiting, clear the CASHE and data (think this is option 3 but confirm). You should already have root so use KFHD_SRT_v1.3.0- 7.2.3 (separate option for restoring factory recovery.)
Always make sure ADB and allowing apps from unknown sources is turned on on your tablet. I always turn my tablet to never sleep or an hour so it stays away and turn the brightness up on the screen when modding. Every tool you use, reconfirm the settings are the same.
Click to expand...
Click to collapse
It seems to be working great now. Updates disable, holo launcher installed and no more freeze ups (part of why I wanted to redo it). Thank you very much LinearEquation for your help once again. Now my 2 year old can go back to watching youtube and learning educational gem like saying WTF over and over (yes, mom loved that one..of course it was my fault).
Another reason why I wanted to restore it was that I had a freetime membership for a while, a ton of apps and books were downloaded but when the membership was canceled the apps remained it just said "you don't own this" when you tried to use it...very frustrating to a young kid.
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
Hey guys, I made an account.
So. I tried installing CM on my Kindle Fire HD 7" just now.
Basically how it went down is I got root via superSU, then went via FlashFire. For some reason only CM and superSU were installed, and opengapps wasn't.
So I decided to just redo the entire thing. Already had superSU working on CM, so I got FlashFire and just repeated all of the steps. Now, I also ticked "Wipe System Data" in the FlashFire "Wipe" step, which the thread (which I did not know about at the time, so I have that going for me) specifically says not to do. But I'm clever like that.
Anyway, afterwards I booted up to the wonderful AMAZON logo. I managed to get to an adb prompt via the 20+ power button thing, and then followed the recovery instructions from here:
Nevermind, can't post links since I'm a new user. Just Google for "reflective code installing cyanogenmod on amazon fire" if you're curious.
And uh, now the poor thing won't even start. Just a black screen with no LEDs blinking or nothing. I'm guessing the thing's just properly dead, now.
So, questions. Why is it actually broken this bad? As in, I know the steps I did were wrong (wipe system), but can anyone explain exactly why it got borked?
The adb command I used in the final step was just "adb sideload factory.img" and that should've been correct, no?
And second question. Anyone have experience reusing Kindle parts for other projects? Figured I might as well see whether I can salvage some of the parts for my RPi or something.
Also, I just ordered a 6", and I will probably try to install the same thing on it again. So expect another thread in a few days.
Cheers