Related
I tried to root my kindle fire but failed... Then i proceed to do a factory reset from the kindle fire, after reboot I stuck on kindle fire screen.
I have already installed Kindle Fire TWRP.
under my kindle utility it shows my boot status as unknown.
please help!!! Many thanks....
I just hope can reset to its original setting.
If you can boot into TWRP kfu will recognize it.. if not then you should mount it in TWRP...
hi fiddlefaddle, thanks for your reply...
i tried to boot into TWRP but were unable...
what u mean by mount it in TWRP...
sorry i am a noob... hope u can explain to me further..
many thanks
hi fiddlefaddle
i manage to boot into TWRP...
can i know what should i do next in order be able to use my kindle fire again?
thanks...
Not to be rude but try searching for your answers.. I picked up a KF last night for my fiancée it was rooted but restored to stock rom.. I tried getting it to allow prime videos and hosed it up big time. I I was getting fire logos loops all kinds of madness but I hopped on xda did some research now her kf is working with prime video and side installed apps and ADW Launcher as well as stock kf launcher..
Sent from my GT-P7310 using Tapatalk 2 Beta-5
hi prasket...
I am sorry if i sounded like i did not do any searching or research on resolving this issue..
In fact i have been searching on the webby for the whole day looking for the answers and found many.. but none were able to work for me... It may be due to my limited capabilities in understanding and therefore i am seeking for help in this forum...
I believe the purpose of this forum is to share and help out everyone in any way possible.... Its good that you have bought a KF for your finacee but i dun see any rationale in boasting here what you have achieved... not everyone is able to resolve everything just by doing some research like you.
I am just a sincere noob KF user who is looking for some help... Appreciate if i can have some constructive comments instead... thanks
shaoqun said:
hi prasket...
I am sorry if i sounded like i did not do any searching or research on resolving this issue..
In fact i have been searching on the webby for the whole day looking for the answers and found many.. but none were able to work for me... It may be due to my limited capabilities in understanding and therefore i am seeking for help in this forum...
I believe the purpose of this forum is to share and help out everyone in any way possible.... Its good that you have bought a KF for your finacee but i dun see any rationale in boasting here what you have achieved... not everyone is able to resolve everything just by doing some research like you.
I am just a sincere noob KF user who is looking for some help... Appreciate if i can have some constructive comments instead... thanks
Click to expand...
Click to collapse
My suggestion would be to take some time out to read over the first two posts in this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
The first will help you get some basic understanding of how these pieces fit together. If you are using Windows, the second makes sure you have the device drivers installed correctly. Once you've done that, you'll want to set the bootmode on your device back to normal using KFU. Provided the Kindle Fire software is working correctly, you should be able to reboot and get it working normally again.
kinfauns said:
My suggestion would be to take some time out to read over the first two posts in this thread...
http://forum.xda-developers.com/showthread.php?t=1552547
The first will help you get some basic understanding of how these pieces fit together. If you are using Windows, the second makes sure you have the device drivers installed correctly. Once you've done that, you'll want to set the bootmode on your device back to normal using KFU. Provided the Kindle Fire software is working correctly, you should be able to reboot and get it working normally again.
Click to expand...
Click to collapse
ok noted... thanks kinfauns
If you're still having trouble, try using zombiepiratez's unbrick utility
http://forum.xda-developers.com/showthread.php?t=1428428
I had a similar problem and was able to fix it using the utility
So I really like the Android 4.0 ICS Rom that I put on my Kindle Fire.
But I also really wanted to keep some of the Kindle Fire's app such as Amazon Instant Video, and Kindle.
I know I can get the Kindle app from the Android Market, but there is no Amazon Instant Video app in there.
Is there a way that I can still get the Amazon Instant Video app while running ICS 4.0 Android ROM besides just running a ICS launcher on a Kindle Fire ROM?
If not, is there a way I can alternate between the Android ROM and the Default Kindle Fire ROM?
EDIT:
Queston 2:
So I can't get TWRP to work properly. Like... It doesn't feel like it's installed. The only way I can get TWRP to show up on the boot screen, is when I manually have to each time, use the KFU, Press 3+Enter, and then reboot my kindle fire that way, and THEN it'll just load TWRP. I never see the yellow Triangle for some reason. Any reasons why?
Currently running on 6.3.1 using KFU version 0.9.6
Not that I know of
---------- Post added at 02:30 AM ---------- Previous post was at 02:26 AM ----------
You want prime stay stock you want ics no prime that is how it is but you can alternate from a backup of each via recovery.
Keep a backup of both stock and ics on your SD card when you want to watch prime use ota root keeper to protect root and temp. unroot on your stock side always remember to restore root and delete superuser backup when your done . Always make fresh backups before returning to the other. Always do good wipes when moving back and forth because of the difference between the two systems as this can cause problems during restore. Ultimately its as big hassle and an be dangerous if you mess up or take an ota and loose root while on stock. Problems that I have had when switching lost game data particularly glu games, kindle books, market problems, bad backups, SD card space consumption . About your twrp and bootloader issue I would use smirkits scripts to update both of them starting with twrp http://forum.xda-developers.com/showthread.php?t=1500935 read carefully on how to apply these with root browser if you want help just ask for it in a new thread someone will be more than willing to walk you through it .
Your bootloader and recovery are the two things you don't want to make any mistakes on.
I'm pretty sure I haven't made any mistakes though. I've followed tutorial word for word, and even by videos...
What do you see when you boot your device do you see a white kindle with an orange fire? Or a white kindle with a blue fire? If you see the second one depress your power button a few times quickly till you get a tiny list of options at the bottom of the screen press your power button till it looks like --recovery-- that will put you into recovery. If you see the white kindle with the orange fire your bootloader is not installed.
Thepooch said:
What do you see when you boot your device do you see a white kindle with an orange fire? Or a white kindle with a blue fire? If you see the second one depress your power button a few times quickly till you get a tiny list of options at the bottom of the screen press your power button till it looks like --recovery-- that will put you into recovery. If you see the white kindle with the orange fire your bootloader is not installed.
Click to expand...
Click to collapse
I see a white kindle with a blue fire. Why would I put it in recovery mode?
projectdefy said:
Is there a way that I can still get the Amazon Instant Video app while running ICS 4.0 Android ROM besides just running a ICS launcher on a Kindle Fire ROM?
Click to expand...
Click to collapse
As it's been said before, you can only use VOD on the unrooted stock OS.
If not, is there a way I can alternate between the Android ROM and the Default Kindle Fire ROM?
Click to expand...
Click to collapse
Yes, it is possible to dual boot the Kindle Fire, but I wouldn't suggest trying it without doing some research first. And considering the second question of your post, I would suggest doing a LOT of research.
Queston 2:
So I can't get TWRP to work properly. Like... It doesn't feel like it's installed. The only way I can get TWRP to show up on the boot screen, is when I manually have to each time, use the KFU, Press 3+Enter, and then reboot my kindle fire that way, and THEN it'll just load TWRP. I never see the yellow Triangle for some reason. Any reasons why?
Click to expand...
Click to collapse
I would also suggest reading this guide to help you better understand the difference between a bootloader and recovery.
projectdefy said:
I see a white kindle with a blue fire. Why would I put it in recovery mode?
Click to expand...
Click to collapse
See above
I don't have Prime but I've purchased tv shows and rented movies on Amazon and I can see them on my Kindle running ICS through the Amazon website (changing user agent to Desktop on the browser settings) It works pretty well (accessing controls when in full screen mode is a little bit hard and messy but if you don't try to go back and forth in the movie you'll be okay)
I know is not the same as the stock video player but it works
So I might be getting a K Fire today and I'm wondering if this still holds true?
I already have a Galaxy Nexus so just being able to use ICS/browsing the internet isn't a big deal for me. I plan on using the device primarily for reading and video (whichever service is best - amazon, netflix, ect.).
Is the kindle app just as good as the stock interface? Would I loose much from the transition from stock to 4.0.4? I'm guessing that ICS offers a smoother interface and browsing but is that worth the switch?
matt30 said:
So I might be getting a K Fire today and I'm wondering if this still holds true?
I already have a Galaxy Nexus so just being able to use ICS/browsing the internet isn't a big deal for me. I plan on using the device primarily for reading and video (whichever service is best - amazon, netflix, ect.).
Is the kindle app just as good as the stock interface? Would I loose much from the transition from stock to 4.0.4? I'm guessing that ICS offers a smoother interface and browsing but is that worth the switch?
Click to expand...
Click to collapse
The Kindle app for Android is nowhere as good as the reader already on the stock rom. Seeing as all you're going to do is read and watch videos, stay on the stock rom or try MoDaCo.
OK, I have ready many posts and guides an am completely lost. This is my 12 year old sons Kindle Fire that he decided to "root". I am fairly computer savvy but this thing has got me baffled. He used "superoneclick" and now it tries to boot and stops at the kindle fire boot screen and goes no further. Any help on pointing me in the right direction would be appreciated. I do know this. The hard reset obviously does not work because I have tried that at least 100 times. My pc currently does not allow me to access it as a drive although it does show up. It sounds like a bootloader" problem? Again, please give me hand before I kill my son after telling him in advance not to do this.
Thanks
Forrest
Try and see if you can get KindleFireUtility to recognize your Kindle Fire
http://forum.xda-developers.com/showthread.php?t=1399889
Veeman, thanks I will try that and report back.
do you have fastboot?
type
fastboot devices in terminal and see if it returns your kindle number.
you are stuck in fastbootmode.
kfu will sort it out for you.
some more info would be of help.
what operating system on pc?
has your son got fastboot installed in sdk/tools or sdk/platform tools?
what stage was he at in the rooting process?
don't worry, has far as i know there is only one hardbrick issue at the moment, and that has to do with one type of recovery and doing a wipe/restore.
Sent from my Galaxy Nexus using xda premium
I understand your concern, and I don't mean to be out of line and tell you how to be a parent but...
If you're really computer savvy, you know that on the way there, you fudged some settings that made the computer unstable or unbootable. You installed programs, printers, a different way and had it not quite work out because you didn't follow directions.
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
What I would do? Work together with him to fix it. Show him what and how you're doing it, how you're asking for help (and that that's okay) and where to find what he needs to fix it.
You're not hard bricked, at least its unlikely, you're likely just stuck in fastboot which is not a big deal at all.
Just take it with a grain of salt. I know to when a kid breaks something it's "There goes X dollars" But sometimes, you have to break some eggs.
Good luck though.
Well, you came to the right place for guidance! I'm sure a forum search for "stuck in fastboot" would lead you and your son in the right direction. Unless there is a better way I'm not aware of, you will need to get adb up and running on a PC (which is most of the work). Then you will be able to get the kf out of fastboot by issuing commands from your computer's terminal/command prompt
But....
I think you should let your son do it... Especially if he plans on keeping his fire rooted. "Rooting" allows users to make changes to critical system files... On one hand this is really cool because it will allow your son to load custom ROMs (operating systems) and take full advantage of the kf's hardware....But, it will also make it very easy to royally screw things up.
So, if that's something he's interested in he needs to learn how to troubleshoot and fix things himself. You definitely came to the right place though... xda is a very sweet resource.
Goodluck!
http://forum.xda-developers.com/showthread.php?t=1668159
Update
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?
Firemancfd said:
Ok folks, thanks for all the input so far. We (my son and I) have worked on it and found KFU useful. We installed the latest update and it is now working. However, TWRP will not go away. We need to take this in for service so I need to reset everything. We have tried the wipe and install of the update several times it restarts with the blue kindle fire logo with the option for recovery. How do we get rid of this?
Click to expand...
Click to collapse
1. Download Kindle Fire Software Update Version 6.3.1
2. Rename the file to update.zip
3. Get in to TWRP and mount USB drive
4. Copy update.zip to Kindle Fire
5. Unmount USB drive
6. Do factory reset, then wipe system cache, and dalvik cache
7. Flash the update.zip
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Felnarion said:
My point is this: A 12 year rooting his kindle shows a level of intellectual curiosity that I think should be commended and encouraged. Any electrician, programmer, repair guy, anyone who does this kind of stuff will tell you; they learned the most when they screwed up.
Click to expand...
Click to collapse
True, but I think it's a tad different when you spend a couple of hundred dollars on something and specifically asked the lad not to do this one thing.
Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Try letting it sit while it "bootloops."
Might sound strange but I've had this exact same thing happen recently after a fresh install, and it loaded up back to normal after a handful of loops.
sbeddoesdesign, you are right i was upset not about the act but that he done it after i told him not to, then he lied to me about doing it. Either way, I have calmed down about it now and he is helping and participating. We are learning a lot together and its good dad/son time.
anomalya, i tried that and let it sit for an hour and no change.
FIXED
Thanks to all who helped. We finally got it to work correctly. Everyone was a big help and we appreciate everything.
I am glad that you got it working, but I am posting this for anyone else that can't seem to read or do a simple search. If you have the KFU all you need to do is have it running and restart your KF while connected the computer, and send the normal boot cmd when it first connects for those few seconds, and you are good to go, but seeing how too many people are to stupid to understand this, I believe that everyone should stop responding to them!!! We see this too often and everyone gives them this long work around...
kinfauns said:
3) Not all "stuck on bootlogo" problems are fixable with the KFU remedy you provided.
Click to expand...
Click to collapse
Are -any- such problems fixable with KFU? :silly:
Yeah, because 99% of the problems can be fixed by simply sending the command to start in normal boot you are offended and want to try and say I was saying something about you? If you are offended, then yu might be one of the people that can't seem to learn from the past!!!
---------- Post added at 06:46 PM ---------- Previous post was at 06:43 PM ----------
BTW, seeing how most of the issues that fall under this, have been fixed in the exact way I described, it adds to my credit!
Firemancfd said:
Tera Tike, thanks for the answer. I have tried that multiple times and the twrp blue kindle fire with boot options keeps coming back.
Click to expand...
Click to collapse
Blue Kindle Fire logo is FFF1.4a
Thread cleaned up and closed.
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory, BUT when I deleted the ROM, I deleted ALL ROM's including the stock ROM. I also managed to delete all my backups. I can boot my Kindle into TWRP but that is all. I purchased a factory cord from skorpn and am able to put my KF into fastboot mode but KFU will not detect the Kindle unless it is in TWRP. The ADB status is always offline if I try running KFU when in fastboot mode. I have installed all drivers, over and over and when I mount the SD card to USB it shows up on my computer as "KINDLE" BUT, I have no folders in my kindle except for TWRP. There is no /sdcard folder or anything. I am stuck and completely frustrated and I don't know what else to do. PLEASE HELP!!
Click to expand...
Click to collapse
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Sorry, but where do I enter these commands?
soupmagnet said:
Oh good times. Your sdcard either lost it's formatting or part of its formatting or some other similar situation. This is probably caused from not correctly ejecting or unmounting the sdcard before trying to write to it...but that's merely speculation on my part.
The answer to your problem can be found here:
http://forum.xda-developers.com/showthread.php?t=1949372
Good luck
[edit:] you can just skip ahead to printing the partition table and recreating & formatting the sdcard.
Click to expand...
Click to collapse
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
heatherrc77 said:
Sorry, but where do I enter these commands?
Click to expand...
Click to collapse
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
heatherrc77 said:
So, to be more specific...I'm not a completely technical person. I do research and read and then execute but the link you attached tells what commands to put in, but where do I put them in?
Click to expand...
Click to collapse
You need to download the Android sdk, then you can run adb from the command line.
Sent from my Amazon Kindle Fire using Tapatalk HD
heatherrc77 said:
Ok, so here is my deal. I rooted and successfully installed Jelly Bean onto my Kindle Fire months ago. After about a month or so, there was an .android error that kept popping up whenever it booted to the home screen. Since I couldn't do anything with it, I decided to delete the ROM and set it back to factory,
Click to expand...
Click to collapse
I know this isn't helpful now. But the original problem (I am pretty sure) had to do with the drivers with the audio. You probably had the volume all the way down, which causes the error you were receiving. If you mute it, that is fine, just don't have the volume down all the way.
----------------------------------------------
Sorry. I know this probably doesn't do you any good, but I thought I would let you know what I thought.
soupmagnet said:
Oh my.
Every ounce of my being desperately wants to be brutally honest with you...but I won't.
Even the most inexperienced of users has the foresight to answer that question on their own, so you are obviously in way over your head. My best advice to you is to find someone a little more technically oriented to help you fix your problem...but that's just a suggestion (albeit a strong one).
If for some reason that isn't an option for you, then you definitely need to educate yourself in a few areas before attempting anything you find here (this might take a while).
http://www.mahalo.com/how-to-use-command-prompt/
http://www.top-windows-tutorials.com/file-paths.html
http://www.techsupportalert.com/content/how-open-windows-command-prompt-any-folder.htm
http://forum.xda-developers.com/showthread.php?t=1241935
http://forum.xda-developers.com/showthread.php?t=1552547
Posts 1, 2, & 3
That should get you started.
And if all else fails
http://forum.xda-developers.com/showthread.php?t=1850038
Click to expand...
Click to collapse
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
heatherrc77 said:
I asked for help, I didn't ask to be belittled. I already stated I am not the most technical person, but when I set my mind to something, I do the research and I figure it out on my own. The last time I did this, was months ago and I haven't touched it since. Since then all of my research was wiped out because of computer problems and my PC had to be reformatted and my data was lost so now I am trying to get all my research back and excuse me for asking such a stupid question. I am doing this with my OWN Kindle to learn how to do it and I am not hurting any one else or their stuff. How else is someone supposed to learn without trying it?
I will say thank you for your time to help "educate" someone so "inexperienced".
Click to expand...
Click to collapse
I put a lot of thought into how I should respond to this post, so bear with what I'm about to tell you.
My previous post was not intended to "belittle" you, rather, wake you up to the reality that you might not be ready to take on such an endeavor. This is not an iPhone and it isn't as simple as plugging it in and pressing a few buttons. For new users, there is a high degree of risk involved in certain aspects of modifying the Kindle Fire, especially when it comes to repartitioning...which is what you'll need to do to get your Kindle working again.
My harshness is NOT out of ego or feeling "holier than thou". It is not to make myself feel better or to make up for some low self esteem. Treating people with kid gloves around here tends to give them a false sense of security that quite often leads to them getting into very stressful situations. Besides, a little "tough love" is better than indifference any day.
I created a thread in the General forum a while back, titled "**WARNING** You will BRICK YOUR KINDLE if you don't READ THIS FIRST!!!". The purpose of that thread is to warn owners of newer 2nd generation Kindle Fires of the DISASTROUS consequences of trying to modify those devices in the same way the 1st generation devices are. One would think, with a title like that, there would be very few people to make that mistake. Of course one would be wrong, as there are at least two individuals a week that were not prepared to deal with the situation at hand and did not give it the appropriate amount of respect, therefore their Kindles are completely worthless. Needless to say, if something I say is construed as rude yet prevents mishaps like that...so be it...and I'll consider it worth the hurt feelings.
And I agree, in order to learn, sometimes you have to get your hands dirty. But there is a big difference between tweaking some system files contained within a single partition and actually modifying partitions. And yes, you do have to start somewhere, but if you don't know that commands go in the command prompt (and I'm saying this respectfully), this is not the place for you to start. Go back, read through the links I gave you, and get a better foundation to work from before trying to fix your Kindle Fire. Not doing so, would do you a great deal of injustice.
No hard feelings,
And I wish you the best of luck.
hello.
I write this post because right now I'm desperate. my kinde fire was rooted and works great. I wanted to install an unofficial ROM and there came all problems.
first of all I want to say that I resort to this message because I've tried everything, but I did manage to save my device.
My Kindle was rooted and TWRP works well. I inadvertently left the device without an operating system. I forgot to put a rom after you wipe. After this, when the device booted, first came out the white and orange logo, then white and blue recovery and eventually returned to the first logo.
First I tried to recover it with the original firmware. I could not access the device via the file browser windows, so I copied the. zip with adb push. after several attempts I went to plan B, because I always got the same "error 7", so I tried to install the cyanogen rom, but I had the same fate.
After that, I was reading about fastboot, so I downloaded kindle fire utility. I think something went here even worse, because now TWRP gone.
I finally discovered unbrick kindle utility, but now my pc does not recognize the device. drivers are installed and kindle fire utility says "adb: online", but I can not access the device.
I searched a lot of information, but I think I am increasingly far from the solution, so I decided to write this post.
anyone can help me to recover the kindle? I'm desperate now. I'd like to have everything as before, I do not lose the root
thanks!!!
Same problem
Hi! i alredy have the same issue. I tried to change the room but something was wrong... I tried to get back and i used kindle fire utility too. I think it was the problem because now i can not turn on. did you find the way to fix it!??????? help i am desperate as you were...:crying:
KFU IS FOR KF1
(that is all)
I know...
fmkilo said:
KFU IS FOR KF1
(that is all)
Click to expand...
Click to collapse
Yes i know that was a mistake... the issue here is to fix it. Some good ideas could be great!!!
i.robert, i'm follow in the same problem.
fmkilo, can you help solve it?
:\
"Onemelia" says that probably ours kindle are ruined... i just know that FireFireFire.bin was the mistake. However maybe we can get in to the sd memory for build everything from base. Only if the mother board is not ruined too...
http://forum.xda-developers.com/showthread.php?t=2010353&page=2
fmkilo said:
KFU IS FOR KF1
(that is all)
Click to expand...
Click to collapse
This forum is full of people doing the same thing. Why do people keep using tools that will brick their device, even though there are other posts saying it will happen.
Frustrating.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
This forum is full of people doing the same thing. Why do people keep using tools that will brick their device, even though there are other posts saying it will happen.
Frustrating.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
chronicfathead, the problem has no solution? is there any way to recover the bootloader?
Finally, I got in touch with Amazon. I explained my problem and they will send me a new one because it was under warranty.
Finally, I got in touch with Amazon. I explained my problem and they will send me a new one because it was under warranty .
i will recieve it tomorrow
thanks very much for your help
I hope not to have problems like this in the future
.
dewars14 said:
chronicfathead, the problem has no solution? is there any way to recover the bootloader?
Click to expand...
Click to collapse
Hi. I was just commenting that a lot of people are rushing into doing things without reading, or even checking what model they have. Admittedly Amazon hasn't made it easy by advertising it as the Kindle Fire 2. All the recent posts in this section of the forum are from people bricking their devices, mainly because they did something wrong.
I don't know how the situation can be changed, apart from building some checks into the KF1 rooting/modding tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
Hi. I was just commenting that a lot of people are rushing into doing things without reading, or even checking what model they have. Admittedly Amazon hasn't made it easy by advertising it as the Kindle Fire 2. All the recent posts in this section of the forum are from people bricking their devices, mainly because they did something wrong.
I don't know how the situation can be changed, apart from building some checks into the KF1 rooting/modding tools.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
Ok. I have already received my new kindle fire 2. I was lucky it was under warranty. Now I have to return the old and noticing more if I decide to put a new rom.
thanks anyway for your help