I have my nephews kindle fire hd 7 was using kffaide on it flashed it now when it boots up I get a red screen wipe across then it goes straight to fastboot and stays there is this a brick how can I fix this tried a few methods yes I have fastboot cable running windows 7 anyone how can I fix this to get kindle going again also I forgot to mention I have tried srt tool as well but still get red wipe then stuck in fboot mode nothing seems to work ahhhhhhhhhhhhhhhhh
You tried reflashing the bootloader? If you haven't then try that, but please remember to verify the bootloaders md5sum before flashing it or your kindle could end up worse off(it wouldn't power on).
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
You tried reflashing the bootloader? If you haven't then try that, but please remember to verify the bootloaders md5sum before flashing it or your kindle could end up worse off(it wouldn't power on).
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for answering im not a noob but can you explain more on what your saying as I don't want to be worse of than I am now thanks
kindle product soho-pvt-prod-07
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
my nephew got it for Christmas put a pin in it and locked him self out of it gave to me sort for him now I realise I have gone abut getting into it all wrong and now have this problem if you can help me that would be awesome I don't know how I can find out if it is a 2013 model????all I know is it was brought for xmas I will do some looking on the net honestly thanks for your time
stunts513 said:
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
my nephew got it for Christmas put a pin in it and locked him self out of it gave to me sort for him now I realise I have gone abut getting into it all wrong and now have this problem if you can help me that would be awesome I don't know how I can find out if it is a 2013 model????all I know is it was brought for xmas I will do some looking on the net honestly thanks for your time
stunts513 said:
I'm going to throw my kindle.... I just typed a very lengthy description and then a stupid tapatalk notification came up right next to the post button as I was hitting it and cleared my entire post... Anyways i thought at first that was a signature but if this kindle is indeed a 2013 model then your first problem was attempting to isntall 2nd bootloader and a custom rom, becuase thats not possible on the 2013 model, also would explain why srt and kffa wouldnt work, their images are incompatible, so before i post any further instructions, please tell me whether i am correct because if its a 2013 model i think i can help you fix it thanks to someone posting the images recently but you are going to have to manually fix this, not too difficult.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
im being told in another thread in xda it is indeed a 2013 model they our also saying to me about finding the images http://forum.xda-developers.com/showthread.php?t=2096888&page=325
Someone just posted the images today if I remember correctly, think he was going to verify their md5sum or something first so I might wait. This is the thread: http://forum.xda-developers.com/showthread.php?t=2650596
I would wait till they confirm they are all good before using them but I doubt it would make the device any worse since it isn't flashing the bootloader or anything, just the boot and system partitions mainly. I might modify the SRT script to use the new images and post my own SRT to help out. I'm in the midsts of debugging a ROM I'm working in so I'll only do it if I have some time free( like when I have questions to ask and there's no devs available to question). Might even tweak his script a bit, not sure how it works but I may add a md5sum checker to double check that the images didn't corrupt if it doesn't have one in it, I know nothing is more annoying than flashing your device back and getting a error from fastboot about size mismatch or something.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Someone just posted the images today if I remember correctly, think he was going to verify their md5sum or something first so I might wait. This is the thread: http://forum.xda-developers.com/showthread.php?t=2650596
I would wait till they confirm they are all good before using them but I doubt it would make the device any worse since it isn't flashing the bootloader or anything, just the boot and system partitions mainly. I might modify the SRT script to use the new images and post my own SRT to help out. I'm in the midsts of debugging a ROM I'm working in so I'll only do it if I have some time free( like when I have questions to ask and there's no devs available to question). Might even tweak his script a bit, not sure how it works but I may add a md5sum checker to double check that the images didn't corrupt if it doesn't have one in it, I know nothing is more annoying than flashing your device back and getting a error from fastboot about size mismatch or something.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for getting back to me and thanks for the time you have spent trying to help me I will look into this honestly thanks for the help m8 with this problem I have hopefully when I have a proper look a bit later on I may be able to get this brand new kindle up and running hope you don't mind if I get lost or stuck at any point I can send ya a message and you may be able to help if I get stuck as your knowledge seems far more than I know once again thankyou
i have the images how would I now apply them to the kindle I take it it will be with fast boot but how to apply them to get this kindle running again
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idk if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes result in hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
thanks
stunts513 said:
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idme if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes a hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for the info m8 and yeah I got a bit of knowledge with command prompt,thanks for the advice ill see what happens thanks again
you online now???question.
stunts513 said:
Something like putting it in fastboot and open a command prompt, now here's to hoping you have basic command line experience. I would recommend putting the images you downloaded into for instance the same folded as the fastboot command in SRT, or if you have another fastboot command that is fine as well. Idk if SRT defaultly put its images in the same folder as fastboot, but if it did feel free to deleted them to avoid confusion. Anyways for the commands, CD into the directory containing the fastboot commands that you placed your images in. Now I believe this is what you want to run:
Code:
fastboot -i 0x1949 flash boot stock-boot.IMG
Fastboot -i 0x1949 flash system stock-system.IMG
Fastboot -i 0x1949 flash recovery stock-recovery.IMG
Note that I am not positive on the file names but if it was incorrect just change the name in the command of the IMG file as it needs be. Wouldn't recommend flashing the bootloader unless you have to, bad bootloader flashes result in hard bricks so I avoid flashing it unless absolutely necessary, and also note boot is not bootloader, boot is the kernel+intramfs. Also don't flash the boot0block image at all. That contains that persons serial number, Mac address and other info, idk why he put it in there, its kinda personal.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
im running cmd with fastboot now to flash the images my question is if you can help flashed stockboot image okay next stocksystem that has come back as failed fastboot is now flashing stock recovery but it just seems to be sitting there any ideas on how long the process should take not sure if something is up and not sure this gonna work if stock recovery failed any ideas worried about unplugging or turning it off.
Weird, recovery is rather small compared to the system image, I wonder why it was hanging. I normally don't advise on pulling during a fastboot flash, but what else can you do if its hanging... I would just attempt again. If all the images are in a zip check the CRC listed, and I don't know exactly how to do that offhand, think it depends on the program you use, think some list it in a column, I use Linux a lot and I haven't ever checked crc's, I usually go by md5sums. Sorry I can't be of much help other then say try again, this is kinda the only images we have as if yet and the kfhd2 is kinda new territory sorta so we have to see if we can get it working like we did on the previous one, really shouldn't be any learning to it since it is just a modified version of the kfhd7".
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
Weird, recovery is rather small compared to the system image, I wonder why it was hanging. I normally don't advise on pulling during a fastboot flash, but what else can you do if its hanging... I would just attempt again. If all the images are in a zip check the CRC listed, and I don't know exactly how to do that offhand, think it depends on the program you use, think some list it in a column, I use Linux a lot and I haven't ever checked crc's, I usually go by md5sums. Sorry I can't be of much help other then say try again, this is kinda the only images we have as if yet and the kfhd2 is kinda new territory sorta so we have to see if we can get it working like we did on the previous one, really shouldn't be any learning to it since it is just a modified version of the kfhd7".
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
thanks for the advice ill see what happens ill keep going with it gotta suss in the end rooted a few tabs in the past got there with them in the end tanks for all you help so far
Related
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
microsynth said:
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=36647251
Sent from my KFTT using xda premium
It is not really bricked. Just wait, I will post a copy of setup wizard soon within an hour or two.
Sent from my KFTT using xda app-developers app
microsynth said:
Hello, So I'm new to the Android Operating system, a bit of a windows guy, but not so much for linux. I Rooted my Kindle Fire HD, got the apex launcher, chrome...etc... I was removing amazon stuff that i didnt want and I accidentally removed SetupWizard.apk I noticed my navigation bar was gone. Here's were the true stupidity comes in. I Deleted SetupWizard.apk, I then reinstalled SetupWizard.apk from a Galaxy something
Now when i turn on my device, it loads up, says "Setup Wizard has stopped" and contiunes to inform me this everytime I hit ok. Can't change any settings, and the device is not able to be switched into adb mode, but it is recognized as simply a kindle on my PC. Is there any hope?? if i could get to settings im sure i could figure something out.
Click to expand...
Click to collapse
Do you have a factory cable?
If you don't you can order one from skorpn
or you can make one if you know how to solder
Once you have it, it's easy to deal with your problem
AmrBanawan said:
Do you have a factory cable?
If you don't you can order one from skorpn
or you can make one if you know how to solder
Once you have it, it's easy to deal with your problem
Click to expand...
Click to collapse
That is the cable that came with the device right?
microsynth said:
That is the cable that came with the device right?
Click to expand...
Click to collapse
The factory cable is a little different. But, you may not need one.
Turn your device off and enter the following command:
Code:
fastboot -i 0x1949 getvar product
When you see "waiting for device" turn your KFHD on and that should put it in fastboot mode. In fastboot, you will be able to restore a stock "system.img" and repair your device.
soupmagnet said:
The factory cable is a little different. But, you may not need one.
Turn your device off and enter the following command:
Code:
fastboot -i 0x1949 getvar product
When you see "waiting for device" turn your KFHD on and that should put it in fastboot mode. In fastboot, you will be able to restore a stock "system.img" and repair your device.
Click to expand...
Click to collapse
Will this work without Adb mode, I cannot enable it at the moment
microsynth said:
Will this work without Adb mode, I cannot enable it at the moment
Click to expand...
Click to collapse
Fastboot and ADB are two completely different programs that work in completely different modes. As long as your drivers are in good working order, you should have nothing to worry about.
soupmagnet said:
Fastboot and ADB are two completely different programs that work in completely different modes. As long as your drivers are in good working order, you should have nothing to worry about.
Click to expand...
Click to collapse
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working? or should I try to turn it off and on again
microsynth said:
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working? or should I try to turn it off and on again
Click to expand...
Click to collapse
UMM...Where did you get this image that you restored to the device? What command did you use to flash it into place?
soupmagnet said:
UMM...Where did you get this image that you restored to the device? What command did you use to flash it into place?
Click to expand...
Click to collapse
Im using the software from the link above, In that I used step 3
microsynth said:
Im using the software from the link above, In that I used step 3
Click to expand...
Click to collapse
[Edit:] Never mind that. It's pretty obvious what happened in your case.
I'll quote the creator of the tool you used to restore your Kindle:
prokennexusa said:
WARNING! THIS TOOL CAN PERMANENTLY DAMAGE THE KINDLE IF IT IS NOT USED PROPERLY. DO NOT FLASH THE
KINDLE FIRE 2 IMAGE TO A KINDLE FIRE HD OR FLASH A KINDLE FIRE HD 7" TO A KINDLE FIRE 8.9" DEVICE. THIS
WILL CAUSE PERMANENT DAMAGE THAT CAN NOT BE REVERSED. ONLY FLASH THE CORRECT MODEL SOFTWARE
TO YOUR DEVICE.
Click to expand...
Click to collapse
soupmagnet said:
[Edit:] Never mind that. It's pretty obvious what happened in your case.
I'll quote the creator of the tool you used to restore your Kindle:
Click to expand...
Click to collapse
He has a KFHD 7" and he chose the correct restore option, What makes you say that?!
It is okay, Don't panic.
But you really need a fastboot/factory cable now, Once you have it,
Let us try something a little different, You now have 3 .img files in you backup folder in C:\KFFirstAide\backup, Correct?
Take those files outside the folder now they are in C:\KFFirstAide
Hold down Shift and right click anywhere in the folder
Choose Open command window here
Turn off your device and then connect the fastboot cable, The device should power up and then fastboot logo is displayed
Copy and paste these commands in the command prompt window
fastboot -i 0x1949 flash boot boot.img
Should say
sending...
okay (time)
writing...
okay (time)
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
AmrBanawan said:
He has a KFHD 7" and he chose the correct restore option, What makes you say that?!
Click to expand...
Click to collapse
I hope you're right...
microsynth said:
Ok, I have the computer at waiting for device, after downloading an image to restore. The Kindle is now black, nothing on the screen. Is it working?
Click to expand...
Click to collapse
...but, I've rarely seen this situation turn out for the better.
It was never actually confirmed what Kindle Fire HD he is using.
I've flashed my system.img dozens of times and I've never seen anything like he's describing. From what I've seen, and considering the system.img was sent, we're looking at two possible scenarios; there was a malfunction in prokenexxusa's software OR user error played a part in the the resulting outcome.
Of the two, it's generally safe to assume the latter.
soupmagnet said:
I hope you're right...
...but, I've rarely seen this situation turn out for the better.
It was never actually confirmed what Kindle Fire HD he is using.
I've flashed my system.img dozens of times and I've never seen anything like he's describing. From what I've seen, and considering the system.img was sent, we're looking at two possible scenarios; there was a malfunction in prokenexxusa's software OR user error played a part in the the resulting outcome.
Of the two, it's generally safe to assume the latter.
Click to expand...
Click to collapse
It is a kindle fire HD 7; 16 GB it was on 7.2.3.
So is it fixed?
Sent from my KFTT using xda premium
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Nikaroo said:
I apologize for yet another of these types of posts as I know there are a ton because I've been searching through them for a few days now. I can't seem to find a solution to my problem that works so hopefully someone can point me to the correct thread or help me directly. Here is my problem:
I have a Kindle Fire HD 7". I had successfully rooted the device, but then I went and screwed all that up by trying to mod it to get the android market (I, as a noob, changed a system value I shouldn't have - oops). After that, my kindle was/still is stuck on the System Recovery screen. The one where you can choose to reboot or erase all/reboot. Tried both, didn't work, got a factory cable from Skorpn (thank you!!).
I can now get my kindle to to show 'Fastboot Kindle Fire' on it's screen, but my computer doesn't recognize it as a Kindle. It shows it as 'Tate-PVT-08'. I found some threads on here about that and downloaded the drivers/installed them. The computer still does not recognize it as anything other than the tate thing. Grar. I have the android sdk stuff and the KFFirstAide. I'm using Windows 7 OS if it matters. But I do not know how to proceed without getting the dumb computer to recognize my device, so please help me out if you know how to do this. I'm about ready to throw the darn thing into the street and run it over multiple times with my jeep! It's been unusable for 6 months now! And yes, I'm a pathetic noob, and a girl to boot so keep that in mind... I apologize.
Click to expand...
Click to collapse
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
soupmagnet said:
User stunts513 has a driver install package in his signature & profile that you can use to get your drivers working properly. If that doesn't work, you may want to try other, non-Windows based options.
Click to expand...
Click to collapse
Thanks for the pointer - I think it got me a tiny bit further. After finding the package and 'fixing' drivers - woo-hoo - my computer is saying that the device is working properly now, I can see it as 'Kindle Fire' in my device manager. However, it still is showing up as 'Tate-PVT-08' under Devices and Printers, and it cannot be found (isn't communicating) with ADB. I feel like I'm missing something so small to be able to move forward and reflash this thing - it's so incredibly frustrating to not be able to find it. :/
I also have tried editing the adb usb file to include the 0x1949, having gone through the adb kill/start-server commands several times, which hasn't changed anything. Is there anything I am missing to get windows and adb to communicate with it? Or is my only option at this point trying 'non-Windows based options'?
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You don't use adb commands with fastboot, you use fastboot commands. I think at this point you said you have kffa, so try getting it to reflash the system image. I don't know the option number though.
Click to expand...
Click to collapse
Sooo, I feel even stupider now. I do have KFFA, so I tried to reflash the system image. It went through and gave me a success, although it did have an issue with erasing user data and cache. It said to disconnect from the computer/usb and power down, then restart. I did that and was super hopeful - it went through the boot screen a few more times than normal... but then BAM. Right back to the Kindle Fire System Recovery screen that it can't get past. Ugh. I must have really screwed something up on it.
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here. Going through that, I checked my hardware IDs, and one of the numbers are off, which according to the guide means that my Kindle isn't in fastboot mode (and this is while using the fastboot cable). If I use a regular USB cable, it doesn't show up at all anywhere. The more I research, the more confused I get. Everything seems geared towards fixing your device if it is stuck in a bootloop (mine goes through that and sticks at the recovery screen) or being able to get it into fastboot, which I cannot seem to do even with the cable. I guess I'm going to try to uninstall and reinstall the drivers for it again, but I'm starting to believe that whatever value I changed while in super user mode before my problems began are going to make it impossible to fix...
The hardware I'd should be 0x1949, and at this point I'm guessing maybe something is wrong with something in the data partition or you have a bad kernel. I don't know how to wipe the data partition from fastboot though. I don't know if kffa reflashes the boot partition, but you could always try that since a system reflash didn't work, or you could try reflashing the system image again, there's another tool in the android development section called kindle fire system restore tool, maybe it will work better for you. Here's the other tool: http://forum.xda-developers.com/showthread.php?t=1951254
Ignore the part about that adb command, that's only for of your kindle can actually boot up.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Nikaroo said:
Hmm. I just did some more digging on fastboot commands and found the fastboot mode guide on here.
Click to expand...
Click to collapse
Be very careful of what guides you use around here. Some of them (fastboot guide in particular) are made with the original Kindle Fires in mind, and can lead you to do irreversible damage.
I'll try that in the morning... I spent most of my day at this and need a break! Thank you so much for trying to help me out. I really appreciate any and all pointers.
I just bougt a Kindle fire hd 7", after flashing the 2nd bootloader i get bootloop (forget to check the stack override) but i don't have the backup because i couldn't go in fastboot.
There's a solution for this problem, i'm very anxious.
Thanks for the help and sorry for my bad english.
HylianHero
HylianHero said:
I just bougt a Kindle fire hd 7", after flashing the 2nd bootloader i get bootloop (forget to check the stack override) but i don't have the backup because i couldn't go in fastboot.
There's a solution for this problem, i'm very anxious.
Thanks for the help and sorry for my bad english.
HylianHero
Click to expand...
Click to collapse
First thing is to download the SDK package and set the environment up. Here is a great video tutorial https://www.youtube.com/watch?v=oaNM-lt_aHw This will allow you to use fastboot command which is what you will do to push the images you need onto the bootloader.
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Once your at this point, download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and either use it per the instructions or extract the files and CD from inside the folder and manually flash the 3 images via fastboot issuing these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
LinearEquation said:
To make sure your computer issue fastboot commands, open up a comand prompt as an administrator and type "fastboot -i 0x1949 getvar product" with no quotes and it should return Tate-xxx-xxx. If you don't get that response, do not move forward.
Click to expand...
Click to collapse
I don't get response.
Does the kindle logo ever turn blue?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Does the kindle logo ever turn blue?
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
Never, i get bootloop before turning.
I'll be honest I was a complete book at this first I couldn't use fast boot to save my life what so ever, I found a way where I didn't need to use fast boot commands and it was noob proof, quick question do you by any chance have a fast boot cable?
If so I'll be able to help you save your Kindle Fire
HylianHero said:
I just bougt a Kindle fire hd 7", after flashing the 2nd bootloader i get bootloop (forget to check the stack override) but i don't have the backup because i couldn't go in fastboot.
There's a solution for this problem, i'm very anxious.
Thanks for the help and sorry for my bad english.
HylianHero
Click to expand...
Click to collapse
You need a fastboot cord before doing anything else.
LinearEquation said:
You need a fastboot cord before doing anything else.
Click to expand...
Click to collapse
I don't have a fastboot-factory cable beacause the shipping time is very long and i'm worried about the customs.
Anyone knows a place that send this cable in europe quickly?
EDIT: Jserrano56, your method requires a factory cable, too?
@HylianHero
Europe...? Dude I got mine from eBay and it was here in 3 days, you'll need one no matter what, without it you have a brick, a paper weight, it's practically useless
Long shot, but maybe a final resort without a fastboot cable?
[How To]Fix Recovery Bootloop after installing twrp and 2nd bootloader
http://forum.xda-developers.com/showthread.php?t=2459498
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app
Jserrano56 said:
@HylianHero
Europe...? Dude I got mine from eBay and it was here in 3 days, you'll need one no matter what, without it you have a brick, a paper weight, it's practically useless
Long shot, but maybe a final resort without a fastboot cable?
[How To]Fix Recovery Bootloop after installing twrp and 2nd bootloader
http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
It's okay, the guide doesn't work (i can't go into TWRP) but i'm going to buy this cable.
So well recently i had been messing around with my kindle fire hd running 11.3 firmware and bricked it by messing with the system. I am currently stuck on the kf bootlogo every time i power on. i have purchased a factory cable from ebay, and when i plugged it into my pc it went straight into fastboot. im not really sure on what to do now. tried so many forums but nothing seems to work. please someone help me to restore to stock firmware or unbrick it. please guyss! will be so grateful!
thanksss
dave:crying::crying:
You need to flash a system image to it to fix it, unfortunately I don't know where to get hold of a 2013 one, but it should be fixable. The 2012 images wouldn't be compatible so don't bother with trying them.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
You need to flash a system image to it to fix it, unfortunately I don't know where to get hold of a 2013 one, but it should be fixable. The 2012 images wouldn't be compatible so don't bother with trying them.
Click to expand...
Click to collapse
Thanks for the really quick reply, but can you please guide me on how to do this?
Thanks so much!
davethebrave14 said:
Thanks for the really quick reply, but can you please guide me on how to do this?
Thanks so much!
Click to expand...
Click to collapse
You would run something like this
Code:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
but you will need the images and the fastboot command.
stunts513 said:
You would run something like this
Code:
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
but you will need the images and the fastboot command.
Click to expand...
Click to collapse
Thanks again man, but can you please provide the images and the commands, cant seem to find them anywhere. when you mean run the code, you mean using terminal right? sorry for all the hassle, kinda new to this whole rooting thing.
ps; will i be able to use KFFAIDE to help me? everytime i run a command, it says "device not reccognized" and similar quotes.
thanks mate for the help!
As far as I know kffa doesn't support the new HD model, and I don't know where to get images for it. If someone else with a rooted device would simply just dd a copy of their system partition and host it, it would be very useful... And yes you run it from a terminal/command prompt.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
As far as I know kffa doesn't support the new HD model, and I don't know where to get images for it. If someone else with a rooted device would simply just dd a copy of their system partition and host it, it would be very useful... And yes you run it from a terminal/command prompt.
Click to expand...
Click to collapse
So that means I would have to wait a while for someone to do a copy? that would be in, say a few months right?
stunts513 said:
As far as I know kffa doesn't support the new HD model, and I don't know where to get images for it. If someone else with a rooted device would simply just dd a copy of their system partition and host it, it would be very useful... And yes you run it from a terminal/command prompt.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
With the number of bricks this device has had, I'm suprised no one has done this already. If only I could get my hands on my mom's KFHD 2013..
>>>Sent from my homebuilt TARDIS running Android 4.4... or maybe it's a rooted Kindle Fire HD running CyanogenMod 11<<<
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
joeyx2 said:
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
Click to expand...
Click to collapse
ok well in either situation your going to need a fastboot cable/adapter, i recommend getting the blackhat adapter mentioned in hashcodes 2nd bootloader + twrp tutorial. Now for the other thing i need to know, is this a 2012 or 2013 model? (2013 has no front facing camera)
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
joeyx2 said:
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
Click to expand...
Click to collapse
Ok lemme grab 2 links you will need.
The thread i was talking about it this: http://forum.xda-developers.com/showthread.php?t=2128848
I personally recommend a custom rom over amazon os so that tutorial could be useful to you in the future should you decide to flash a custom rom on it. There's a link towards the top that goes to the site where you get the fastboot adapter.
Alright and secondly you will need this: http://forum.xda-developers.com/showthread.php?t=2096888
Read its instructions or you might have issues. Also when you plug in your kindle with the fastboot adapter it will show up as a tate device in the device manager, download the drivers in my signature and extract them somewhere on your computer, then in the device manager right click the tate device and hit update drivers and choose a place to search for them and choose where you extracted my drivers and it should install the drivers. If you are on windows 8 you will have to disable driver signature enforcement first though. Once drivers are working you should be able to restore with kffa.
well i ordered the fastboot adapter and it does go into fastboot mode but i have tried a few utilities and they all seem to blow right threw the process. its like it seeing the phone but not doing anything. the only thing i can think of is USB debugging was not turned on and that may be why i cant get it to act right. of course i cant turn it on cause i'm stuck at the logo so is there a way around that or is there a program like Samsung has called Odin that i can use to flash stock everything on?
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
joeyx2 said:
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Kffa was one of the links I sent you.... download and extract it. Shift + right click it's folder and hit New command window here. Then run that command I mentioned.
Sent from my LG-P769 using Tapatalk
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
joeyx2 said:
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
Click to expand...
Click to collapse
well the good news is that means fastboot is working, it only is called a tate device in the device manager initially, once you isntall th edrivers it will show up a s a adb interface which is confusing becuase you don't use adb with fastboot. Anyways you should be able to attempt manualyl flashing the device from that command prompt now using certain commands like
Code:
fastboot -i 0x1949 flash <partition name> imagename
so something like
Code:
fastboot -i 0x1949 flash system system.img
it could be that kffa failed to retreive the files or something so it dint flash, sometimes its download links don't work, try srt i think linear posted the link to it, it might actually work out of the box.