Toolkit may be coming soon to you guys! - Kindle Fire Q&A, Help & Troubleshooting

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.

Related

[Q] Son in trouble with pissed off dad about bricked KF!

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.

Rooting kindle?

Okay I have been searching for hours, trying to root my kindle Fire. I installed the drivers as showed. Im showing up in device manager under android phone / android adb interface. When I run the kindle fire Utility It comes up and says ADB status Online, Boot status unknown. I have tried plugin right into the back of the computer with the USB cord thinking it was the hub from comments i read in another thread but no luck. I have also reinstalled the drivers several times, at one point restarting after every step and still no luck. Any help on this please?
You might have a kindle fire 2. Check your firmware revision in device info or about device or whatever its called in settings. If its 10.something you probably have a 2. It has a faster processor and more ram but it has a locked bootloader that no one has said they are actively working on as of yet. Hopefully someone will pick it up soon. It can be rooted and have Gapps installed but no custom recovery which means no custom ROMs. If you develop or know someone, give it a shot. I know there are at least a few people eager to have a full tablet.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
LegendaryCatalyst said:
You might have a kindle fire 2. Check your firmware revision in device info or about device or whatever its called in settings. If its 10.something you probably have a 2. It has a faster processor and more ram but it has a locked bootloader that no one has said they are actively working on as of yet. Hopefully someone will pick it up soon. It can be rooted and have Gapps installed but no custom recovery which means no custom ROMs. If you develop or know someone, give it a shot. I know there are at least a few people eager to have a full tablet.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply I never did get it to change, I went ahead and took a chance and rooted it anyways with the tool, everthing worked perfect. I now have it running android 4.1

[Q] Kindle Fire is completely blank, except for TWRP

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.

[Q] kindle fire unrecognized in windows. adb does not work. No SO. bricked

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

[Q] Accidentally formatted internal storage PLEASE HELP

So about two weeks ago, while installing a new rom, I managed to format my storage before flashing the rom. After doing that, there obviously was no rom to flash. Or anything else for that matter. My phone now can only boot into recovery mode. When trying to turn it on, it goes as far as the google screen showing the unlock icon. I would surely appreciate any help from you guys. Thank you in advance and I apologize for anything noobish i have or undoubtedly will say in the future.
By the way, here is my set up:
Verizon Galaxy Nexus
Windows Vista 32 bit PC
Again, Thank you
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
When i last tried that, ADB would not recognize my phone
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Fastboot, flash stock. If you're phone isn't being recognized, install drivers.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Click to expand...
Click to collapse
ADB does work on a custom recovery. You're right, he's having driver issues, he's just too lazy to search. THIS QUESTION has been answered a zillion times and is well documented in efrant 101 stickied on General section.
a manta wrote this.
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------
peikojose said:
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go read efrant 101 sticked on General section, please.
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
Of course, fastboot mode doesn't have ADB. Only fastboot.
a manta wrote this.
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
So, I installed Samsung's drivers, then went to adb and tried to sideload a rom, but was given the error: "device not found". I had my phone plugged in and booted into the recovery mode. I dont know what I'm doing wrong.
To the OP i really hope you get things sorted out. But some advice if you really do not know anything about your device, about rooting or how to use your device in conjunction with a computer then you need to do a lot more reading and research. Using ADB, Fastboot and being able to have your computer recognize your Gnex is all the first essential part of beginning to unlock the bootloader and rooting the device. So you should be very familiar with this unless you either had someone else root your phone or you used a root toolkit which is the reason why you don't understand what the steps may be or the wording. Toolkit are the worst to use just because of that reason. Also the fact that you wiped your internal memory also leads me to believe you don't know what you where doing because before it deleted it it asked you 'are you sure'. Please spend some time reading and learning educate yourself, do not expect anyone to solve it for you. Every rom, every guide and post on here always starts off by warning you that you are solely responsible for what you are about to do. Read, read and read again.
Sent from the future via Tapatalk 4
jaysondasher said:
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
Click to expand...
Click to collapse
fancy android lingo?
This 'lingo' that gets tossed around is the basic knowledge one should know when customizing (rooting/flashing/modifying) their Android device.
Would you go and start modifying the engine in your car without some basic understanding of how it works, or what the parts are called and located?
Why would you treat your electronic devices any other way?
That post tells me you didn't even read the damn sticky I was talking about.
If you had read this, you would understand the "fancy android lingo" by now. And @jaysondasher, I have another link for you, here.
Have a nice day.
Don't boot into recovery. Boot into boot loader mode. Power and both volume buttons. Then, using fastboot flash stock.
Sent from my Galaxy Nexus using xda app-developers app
was able to get it figured out. Sorry if I frustrated any of you, but thank you for your help.
Sent from my Galaxy Nexus using xda app-developers app

Categories

Resources