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.
Related
Looking to bring you guys into the action. I'm gonna purchase a kindle fire online on Monday and then make a toolkit on it.
Just a few questions.
You guys use Fastboot commands or no?
Ex: Fastboot flash recovery recovery.img, Fastboot flash boot boot.img
A personal question myself, since there is no removable battery, is there a button trick to shut it off if it freezes?
I have to put all this into consideration when I make the toolkit.
Thanks!
If you don't know what a toolkit is, look in my signature. Just don't look at the Sensation or MT4GS since I still have to update their UIs
Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here
HaiKaiDo said:
Yep you just hold the power button if it freezes and itll shutoff pretty much no matter what. Also please do bring tool kit here
Click to expand...
Click to collapse
Thanks for the reply! What show I know about the device? Anything in particular?
Why is it necessary to flash a different bootloader? (I should be reading on it now, but I'll get a better analysis on it when I order it)
The toolkit is gonna basically be like this but with a graphical user interface
http://forum.xda-developers.com/showthread.php?t=1399889
Will add other options as well, just gotta see how this works since it is different than HTC phones.
bump
help me out so I can help you guys out as well!
Theres already a toolkit
trter10 said:
Theres already a toolkit
Click to expand...
Click to collapse
Who said another one won't hurt? It's good to have choices. Would you rather use one ROM or have choices to choose from?
Sent from my HTC_Amaze_4G using Tapatalk 2
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
Can you explain what you mean?
Sent from my HTC_Amaze_4G using Tapatalk 2
jacewt said:
Drivers are a big issue for the tool kit we do have.
Sent from my Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
This is true.
Sent from my ADR6400L using Tapatalk 2
What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2
hasoon2000 said:
What's wrong with the drivers?
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Lets just say If you can get it to connect through adb you are a genius.
Sent from my ADR6400L using Tapatalk 2
the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium
I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM
Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium
If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium
While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.
build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.
Thepooch said:
build something that restores a kindle in an sbf like process to stock original correctly partitioned then you might have a tool that could rescue a whole bunch of people who have broken systems, bootloaders,recoveries and completly wacked out partitions then you will have a tool that will get used to death.
Click to expand...
Click to collapse
I just have to learn more about it first before I get into doing that unless there is a fix that I can look at.
soupmagnet said:
While I'm a huge proponent of the manual method of rooting/modifying the Kindle Fire, I don't think having programs like the KFU is a major problem. The only way Kindle Fire development is going to grow is with more users, even if those users are noobs looking to take the easy way out. The more popular the device becomes, the more likely experienced developers will jump on board.
There really isn't much you can do about people who refuse to follow directions or educate themselves before getting into trouble, other than complaining about it and posting stupid threads like "This is what you people sound like". It all comes with the territory, especially in a world where a mentally retarded two year old can jailbreak an iPhone and feel like a genius afterwards.
As long as people are still searching for the "any" key, I'll still be mumbling TSTFO and yelling HLMGIFY until my face turns blue but I'll be more than willing to put up with it to see this community grow and get some awesome development in the process. So yes, I say bring on the Toolkit, the worst that could happen is I get more fuel for my sick sense of humor.
Click to expand...
Click to collapse
First, I loved the link to the humor thread. I started laughing because we always deal with that!
Second, I agree. Manual method is the way to go for new users to learn in case anything happens. I just hate doing commands manually all the time so I automate them to make it easier on me.
I would need you guys to help out since you guys have way more experience than me with the Kindle (I'm gonna order it soon). As long as you guys don't mind, then this will definitely come!
Kheladu said:
If you use the KFU on your kindle to root everything should go well. You may encounter problems if you do it manually at least I did a little a bit others my have not. For the driver issue the KFU comes with drivers use them instead when your computer asks for the location. I wish you luck with the toolkit the more the merrier
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thank you sir! I'll see if I can get the drivers issue fixed.
androidcues said:
Fastboot works real well with the fire. Its a nice device to use with adb and fastboot.
The drivers are really finicky and once you get them set up....don't change anything with regard to your computer as far as your kindle fire development setup. The trick for me (windows 8) is to force disable windows driver signing protocol and to use the windows device manager and USB deview to get the kindle fire drivers established. I would not start off with the kindle fire utility kit or put that in the same directory as your kindle fire development file.
Its a great device and I think a new toolkit does no harm and promotes further development. I strongly advise using TWRP recovery and not clockwork mod as there's some unresolved issues with damaged emmc partitions causing brickedness. (See hashcodes thread with regard to cwm recovery for the 3.0 kernel)
That 3.0 kernel (by Hashcode) pumped massive growth into this device as we did not have hardware acceleration prior to that (outside of the Amazon forked build.)
Now I've no idea what a toolkit is but I'll help test drive anyhow. What's the other toolkit? Vashypoors KFU? That is a nice setup but IMHO people ought to be able to handle ADB and fastboot business before using that KFU or any other toolkit.
You asked about the bootloader? Great write up about why the stock image was replaced by FIREFIREFIRE by Pokey9000 I'll try to find it later but it should be one if the stickied threads here. You can't do a thing with the stock bootloader.
Edit --- I now know what you mean by a toolkit... I didnt realize you made one for the One-S. (nice work, that!!)
Now Im going to get a bit straightforward, dont get me wrong --- these toolkits are great, but they are akin to giving just about anyone on the street a loaded gun... toolkits give an absolute noob or a person who has absolutely no idea whatsoever what they are doing a false sense of security and they believe they have full control of the device where they clearly do not. You effectively give people the easy mind-numbingly-easy opportunity to change something on their device and then they have no idea what its doing or how to get out of any predicament. Thankfully, there are things called "Drivers-Education" and then a "Test" prior to all 16 year olds getting permission to operate motor vehicles!
IT WOULD be cool if you made your toolkit lockable which is unlocked only by the user successfully performing various executions of simple adb and fastboot activities.... i use these toolkits only when my keyboard is broke, or my hands are broke or otherwise occupied by children.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
No offense taken! Positive criticism at its finest! lol. You really gave me a lot of info and helped out. As I said earlier, I'm new to this. (Still didn't order the kindle yet) so I'm trying to gather all the knowledge so I have a heads up.
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
I'm gonna update the One S toolkit soon just so you know!
I did have users who had no clue start using the toolkit. The issues they had were not reading the Post I have on Bugs (A directory issue) and they say it doesn't work. The other issue was root (which I fixed) and flashing a GB kernel onto an ICS ROM. They didn't know what it was and thought it was mandatory (even though it is under the optional section) and soft bricked their phones. I removed kernels and if they want to flash a kernel, they have to do it themselves so they can't blame me or anything.
But thanks again for all the info!
smirkis said:
the device requires different drivers for adb/fastboot.
once u get adb working, and reboot into fastboot, it usually doesn't get seen by the PC. its one of the biggest issues and lots of people have them when rooting.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Will do. Thanks for the heads up!
tgamble160 said:
I used hasoons toolkit with my amaze and gotta say thanks.hasoon andcant wwait to see what you do fornthe kindle users too.
sent from my kindle fire running gedeROM
Click to expand...
Click to collapse
Glad you liked my Amaze toolkit (btw, I updated it a few days ago if you didn't check yet)
------------------------------------------------------------------------------------------------
Everyone, I would like to thank you all for all the info you have given me! Feel free to pitch in some links of anything or anything I should know about before I make the toolkit!
Honestly, an absolute majority of the problems stem from not having the proper drivers installed. With that out of the way, I'm sure there would be a lot less posts from people complaining about stuff not working.
hasoon2000 said:
...
I will user TWRP and not add CWM since we don't want anyone to have bad partitions. If you can, link me why the bootloader was replaced by FFF so I have an understanding on that please
...
Click to expand...
Click to collapse
kinfauns wrote an excellent "Kindle Fire for Beginners" (http://forum.xda-developers.com/showthread.php?t=1552547) which goes into the details of things like why the stock bootloader was replaced w/ FFF. Main benefits of FFF is that it kicks in a temporary fastboot, and also enables easy access to recovery.
In the above-linked document, look under the "How do I unbrick my Kindle Fire?" heading for details of the benefits of FFF's temporary fastboot and access to recovery.
Having been a flashaholic, tinkerer and dabbling themer type on my Moto Droid X for the last 1.25 yrs (with several soft-bricks along the way), the general concepts w/ the Kindle Fire were familiar but the devil's in the details. Thanks to kinfaun's guides and other posts in the forums here, I learned the Kindle Fire stuff more quickly and understand things a lot better than I probably would have otherwise.
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.
About 6 or so months ago I bricked my Kindle Fire in a rushed attempt to install ICS.
Basically instead of properly installing the firmware, I mounted the root, and dragged the new firmware files (extracted) onto the old ones, without changing permissions or anything.
I know I'm stupid, and details may be fuzzy since it's been 6 months. I've installed ubuntu on USB since I've read there are some methods to fix it from there, maybe someone with my exact problem in the past could help.
I really, really don't want to buy the recovery cable, so if there is some other way that would be sick.
Thank you for reading!!!
I just tried using soup kitchen, I don't know what I'm doing really but it says "ADB STATUS: ONLINE" that's a good thing right?
Hate to triple post, but I'm getting this error using every option.
I'm hoping the only way isn't to use the factory cable, what about the shorting method?
I am a defeated man. I have been on this site for about 10 months now, only now have I been a member the past well few minutes. I have tried for the past 5 months, actually by this point, 7 months, I have been gone on with a bricked Kindle trying to fix it myself, by reading posts and threads and programs. From Linux to Windows, back to Linux and to Windows again, I've gotten close but all attempts have failed. I'm not a person who likes to ask for help, but I got no other choice at this point as I just want to get it fixed and over with and back to normal.
So, here's some back-story on what happened my Kindle.
So I picked up my Kindle at the Target I work at when it went on clearnce for $129. Blah blah blah, month's later I got bored and rooted it and installed jellybean onto it, I got bored of it and reverted back to the orginal OS again. I wanted to go back, so I did the same process again to go back to jellybean. I again got bored and wanted to change it back. This time though I read a different process real quickly, and decicided I could figure it out by myself. I change my mind quit a lot as I like the technicality and simplicity it seems so I like to fool around with my electronics.
Anyways, what here's the important stuff. I had TWRP installed, so i went and I wiped my caches and system which I forget what forum it was from but it was a step, then me thinking what I needed to do, I wiped the partitions, and that's where everything went downhill. From there I went and knowing I messed up I tried to fix it and failed.
Taking some time off and coming back to it, I discover the Firekit LiveUSB, I failed to get that working so instead, I ran VMware and mounted the USB ports and what I needed to Ubuntu, which worked well suprisingly.
I figured Firekit would allow me to repartion the kindle and enable me to write to it, as even though I had access to the recovery menu, it would not allow me to write the stock OS since there was no partition to write it too. Continuing on, I went and failed multiple times. It was roughly around this point, where even with my factory cable or regular data cable, it wouldn't allow me to connect it to my PC and it would just read unknown device or problem installing driver. Even with the ADB drivers installed (or with them uninstalled) it failed to connect.
Revisting it a month later let me do the same and I failed. An attempt later it actually said it properly booted it, recovered it, erased TWRP and my recovery, and when I went to go get into it, it failed. Now I'm stuck in a boot loop, where it will boot into Kindle Fire with Android guy, then into Kindle Fire only, where it freezes. (does not give me the option to boot into different modes like it use to)
Revisiting now, I have run into the same problem but used the new Soupkit, which lead me to no progress at all.
Click to expand...
Click to collapse
I am at a lost here. I have tried many different steps and I am at a lost here. I just wish to get my kindle to stock OS that's my goal. I have tried many attempts and all have failed. Jokes aside, where do you guys think I should go from here? I do have the ability to troubleshoot or to provide details that are available to me.
Some further details.. I have a Windows PC, running Ubuntu on it via VMware. As well as an obvious bricked Kindle(Stuck in a bootloop with no recovery and the PC won't pick up the ADB that is installed leaving me at a lost to recover it). Additionally, here are a list of links I have used to try to fix it.
http://forum.xda-developers.com/showthread.php?t=1399889
http://forum.xda-developers.com/showthread.php?t=1602560
http://forum.xda-developers.com/showthread.php?t=1552547
http://forum.xda-developers.com/showthread.php?t=1428428
http://forum.xda-developers.com/showthread.php?t=1430038
http://forum.xda-developers.com/showthread.php?t=2192818
http://forum.xda-developers.com/showthread.php?t=1850038
Any help really or guidance what I can do at this point to get back to regular stock OS I would be very appreciative to that, I know that was a long read but thanks in advance.
All I can think: JTAG to force a write of the internal memory just find a stock image and JTAG it.
Nexus 4 CyanogenMod 10.1.0RC5
ryaniskira said:
All I can think: JTAG to force a write of the internal memory just find a stock image and JTAG it.
Nexus 4 CyanogenMod 10.1.0RC5
Click to expand...
Click to collapse
Interesting, I never knew you can JTAG it. I'm not all to fimiliar with JTAG'ing. And if it's anything similiar to how it is on the Xbox, I am not a fan of soldering anything(plus I lack the skill). I can seem to locate any information though on it. I'll keep looking though, thanks.
After looking into it, I can't seem to locate any place or information on it, also, what I did find (Though no information directly to the Kindle) was the Riff Box and similiar stuff, which I'm not dropping $200 that I don't have for a chance it may not work. Any other suggestions?
ScratchButt said:
Interesting, I never knew you can JTAG it. I'm not all to fimiliar with JTAG'ing. And if it's anything similiar to how it is on the Xbox, I am not a fan of soldering anything(plus I lack the skill). I can seem to locate any information though on it. I'll keep looking though, thanks.
After looking into it, I can't seem to locate any place or information on it, also, what I did find (Though no information directly to the Kindle) was the Riff Box and similiar stuff, which I'm not dropping $200 that I don't have for a chance it may not work. Any other suggestions?
Click to expand...
Click to collapse
For example if I bricked my phone I could send it in and get it JTAGed for like $60. Idk what your price would be though
Nexus 4 CyanogenMod 10.1.0RC5
---------- Post added at 05:42 PM ---------- Previous post was at 05:39 PM ----------
ryaniskira said:
For example if I bricked my phone I could send it in and get it JTAGed for like $60. Idk what your price would be though
Nexus 4 CyanogenMod 10.1.0RC5
Click to expand...
Click to collapse
http://goo.gl/5sknN
Here is a link having to do with your problem
Nexus 4 CyanogenMod 10.1.0RC5
ryaniskira said:
For example if I bricked my phone I could send it in and get it JTAGed for like $60. Idk what your price would be though
Nexus 4 CyanogenMod 10.1.0RC5
---------- Post added at 05:42 PM ---------- Previous post was at 05:39 PM ----------
Here is a link having to do with your problem
Nexus 4 CyanogenMod 10.1.0RC5
Click to expand...
Click to collapse
Thanks for the link, i don't have the Kindle HD that's the only problem, but I'll take a look at the jtag services, if I can find one for $60 or less, It's not too bad to do it rather than dropping $200 to get a new one. If anyone know's of a JTAG service for Kindle Fires, that would be awesome.
Hi all i know someone will not be happy i have asked this question that is probs one of the most asked on here from Nubs like me lol.... Basicly i recently got my rooted htc one m8 S-on back, i was planning to sell it so tried to remove the Root from the phone i have somehow managed to Brick it, its under HTC_001 it didnt have a main fw number so i did what others have and read it from the about software section on my phone wich give me 1.54.401.10....... Well i ended up download that one something went wrong either way now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy.... Sorry for the nub questions i did go abit out of my knowledge people say ADB on other forums, im not very clued up with it other than changing the recoverys ive watched youtube vids ect no joy Please can someone give me a Simple Tut or link to help me ive tried following threads and still got no joy http://forum.xda-developers.com/showthread.php?t=2701376 So now i ask the PRO'S please help lol
mikem2273 said:
Basicly i recently got my rooted htc one m8 S-on back
Click to expand...
Click to collapse
Got it back from where???
mikem2273 said:
Sorry for the nub questions
Click to expand...
Click to collapse
No need to apologize for the n00b questions. However, the huge run-on sentences are another story. Take some time to type a post with proper punctuation and sentence structure. It will make it easier for you to get you point across and for us to help.
mikem2273 said:
now im left with a phone that only goes into Hboot and i can access the recovery what is TWRP i can connect the usb and get onto my Sd card using mount but ive tried and tried to get no joy....
Click to expand...
Click to collapse
Tried and tried what? If you aren't specific in what you have done, what are we supposed to do, guess? Be detailed and be specific when asking for help.
You aren't in bad shape at all if you have recovery and can mount SD. Just put a software 1.x based ROM on the SD and flash it in TWRP.
---------- Post added at 01:48 PM ---------- Previous post was at 01:42 PM ----------
mikem2273 said:
people say ADB on other forums, im not very clued up with it other than changing the recoverys
Click to expand...
Click to collapse
Just use the XDA search function, and search "adb beginner" to find a number of good adb/fastboot tutorials aimed at just that, beginners.
But if you've used fastboot to install recovery, the other commands aren't any harder. Its just a matter of just knowing what commands to use for a given situation.
If you can mount SD, I don't even think you need adb. But its a very valuable tool to know, and can help in a lot of situations.
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
unable 2 load my one m8 to fasboot
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
nnamathy said:
pls, i av bein unable to access fastboot on my device; i cant unlock bootloader,s-off e.t.c......what can i do; i really need help...
d screen displays black with fastboot mode @ d lower left corner
Click to expand...
Click to collapse
Dude ..who are you talking too ?? your post is useless and makes no sense.
Start your own thread ... post an exact description of what you did and whats wrong along with pictures / bootloader / anything that might be of some help
mikem2273 said:
Thanks for the response, well i tried a stock rom im not sure where i went wrong tbh i put it on the internal sd and the file would not show up inTWRP i then had a back up and copied and pasted the files from the Stock rom into the back up and tried to install it and thats where it messed up i am crap at this kind of thing i rooted it no problem i thought unrooting would be easier, adb is a bit confusing with me if there was a way i could put a file onto my sd card in zip format and open it i just tried the original one i downloaded to get loads of red commmads saying
E;unable to stat '/and-sec/;555?.??/m?? and so on a load more random numbers
Sorry i am not very on ball with this should of just left it how it was lol
Click to expand...
Click to collapse
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Your lack of specificity also makes it crippling to try to help. What stock ROM, and where did you get it from?
If you got a stock nandroid, you then need to extract the files from the zip and place them in exactly the right folder, otherwise TWRP won't see it. And you do not use the TWRP "INSTALL" function with a stock nandroid, you use the "RESTORE" function.
A flashable ROM zip, in contrast to a nandroid, can be placed anywhere on internal storage or removable SD, and TWRP will see it and flash it using the INSTALL function.
Its very easy to push a ROM zip to the phone with adb. I already told you how to find BEGINNER tutorials on how to use adb. Don't expect to be spoonfed information that is already readily available on XDA. If you have a specific question regarding adb, ask it. Otherwise just saying "adb is confusing" is not going to help you.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
mikem2273 said:
Right update time...... so i have got the phone back working by flashing a new rom but my phone massively lags on boot up, i think my firmware files are corrupt i cant get wifi either ive red about fixes but all need S-off yet i dont want to pay 25 dollars is this the only way to do this ?? i cant put firmware files on my hone without the s-off such hard work and effort would rather pay someone to fix it lol
Click to expand...
Click to collapse
Your firmware files aren't "corrupt". They are just outdated, and don't match the ROM your flashed.
OTAs are available for your version. An option if you don't want to s-off, is to return to stock ROM and recovery, and OTA to update the firmware. It seems you are having problems installing the stock nandroids, but I think you just need to properly follow the instructions from the stock nandroid collection thread.
Otherwise, you are stuck running ROMs that are based on 1.x software. Running anything more recent will result in long boot times and broken WiFI, as you've experienced.
Dammit i know excatly where i went wrong and what you meant by you have to open the file up and adb the right files to the right places............ $%$% i have now fully ruined the phone i think i turn it on i get a White screen the phone then goes full black screen and does nothing...... i have connected the phone via usb to the laptop, the laptop notices the phone and usb i click on the phone in my computer nothing is there when it opens i have also gone onto adb and done the "adb devices" and it does not show on the list, is there anything i can do with this now, i am very gratefull for the help even though i haven't been specific and guessed my way through alot of it like a nob,
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
redpoint73 said:
You sentence structure (or lack of it) is still making it hard to understand what you are trying to tell us. If you can't even be bothered to type a proper sentence; how do you expect us to take the time to help you? Honestly, most other requests for help on this forum get much more response. I think many folks are just walking away from this thread without helping, because they can't understand you due to your writing style.
Click to expand...
Click to collapse
At this point I have to assume it's an inability to communicate clearly, not an unwillingness. You have a lot more patience than most for even trying.
redpoint73 said:
adb only works when booted into OS or in recovery.
Alternately, if you have an SD card reader, use it to load a ROM zip onto the SD from your computer. Then place SD in the phone, boot TWRP, and flash the ROM.
Click to expand...
Click to collapse
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Background: Rooted, S-Off (via Sunshine), , TWRP 2.8.1.0, was running CleanROM (on the 444 firmware) and tried installing Vanir 444. I did a factory reset and I'm pretty sure I might have went into Advanced and wiped System as well (from the reading I've done, I shouldn't have done that) ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted. When the phone went to reboot, it went to the usual white HTC screen, then went black and never moved past that point.
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do! If I missed any background or details, let me know and I'll elaborate.
TIA!
sigmaxaa said:
@redpoint73: I'm in his exact same position...hopefully, I can communicate this a little better...at least I'll try. LOL
Click to expand...
Click to collapse
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
sigmaxaa said:
As you advised in an earlier post, I held down Power/Vol up until the white HTC screen appears. I waited until the screen went black then held Vol down for several minutes but bootloader never came up.
Click to expand...
Click to collapse
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
sigmaxaa said:
My computer recognizes the phone when I plug it in, Windows explorer shows both "Internal" and "SD card", with Internal basically empty and SD card showing all my files. Since I can't get into bootloader, "adb devices" doesn't bring anything back.
Click to expand...
Click to collapse
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
sigmaxaa said:
Any suggestions you might have would be hugely appreciated - hoping to avoid having to head to a local Verizon store and see what they can do!
Click to expand...
Click to collapse
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
redpoint73 said:
I can't imagine it being any worse than the previous guy!
Seriously though, your post would have been better served in its own thread, or almost any other relevant thread. Couple reasons for this:
1) My experience, when folks say they are "in the exact same position", "I have the same problem", etc. they are in fact virtually never the exact same condition. There are far too many variables (M8 variant, hboot version, software/firmware version, how you got to the current condition, and many more) for your condition to be "exactly the same". And for that matter, when folks say they have the "same problem" it in fact is most often a completely different cause, and different fix. Do yourself a favor, and don't say "me too" when posting a problem.
2) The OP basically chased everyone away with his horrible diction. Help threads in this section normally get considerable traffic and assistance. I'm the only one helping this guy, because apparently I'm the only one patient enough to try to decipher his ramblings. By attaching your post to his, you've pretty much cursed your issue to obscurity as well.
If you got this from a post of mine in another thread, its (normally) accompanied with the statement that failure to get into bootloader is virtually always a matter of user error (not getting the timing right). Simply stated, if the screen still comes on, you can get into bootloader. So just repeat the steps until the bootloader screen comes up. You either didn't start pressing vol down fast enough; or let go of it too early (don't let go until the bootloader screen appears).
Once you get the timing right to get into bootloader, and from there recovery, we should be in good shape.
You can likely recover by transferring a known good ROM to the SD card, and just flashing from custom recovery. Or just restore your nandroid.
I doubt Verizon can help. And since the phone was put into this situation by your own actions (mods you performed) its really your responsibility to fix it, not theirs.
Click to expand...
Click to collapse
Thanks for the reply, I do appreciate it. I was able to get it working (after dozens of attempts) and you're absolutely correct...it's all in the timing.